Just had a talk with my manager who wanted to know why I removed a feature from an application we had. This removal had been discussed WITH THE MANAGER several months prior, but apparently they hadn't written a little note or anything down about it.

I told them we had discussed it earlier. They didn't believe me. They checked the project technical specifications that said it _should still be there_. I told them we talked about it previously. They told me to prove it, so I go looking through the commit history.

Lo and behold:

- Commit <hash> authored 4 months ago.
- Update to specifications, asked for by <manager>

Eat it.

I had the opportunity today to FINALLY say "I told you so" to a coworker. It was such a cathartic experience, I'm still basking in the afterglow.

So, what's the process for starting to create your idea? I have one, I've given it a minimal amount of thought, a very high level overview, the purpose and some features that I want. Probably just a free service because it's (probably) not anything too serious. So what now? Market research or just start typing? Planning architecture? This is my first time that I've had an idea I think is worth pursuing. What have you all done?

Needing to teach myself M$ InfoPath because of legacy business code. What better way to learn than getting the feet a little wet first!

Public Service announcement:

If one of your co-workers asks: "Hey, do you have a sec?"

DO NOT reply: "Yeah, I have tons of secs"

Sincerely,
Someone who doesn't think before they speak

I never thought I was a highly opinionated person (read: elitist) until I realized it bothered me that my coworker prefers low-profile rubber dome keyboards to mechanical ones. I'm going on a journey for personal growth this week.