This is how I work in my career. Some of these are counter-intuitive and require explanation.
Shipping code wins. On schedules: Picking an arbitrary deadline is often moreefficient than carefully planning things out. I've spend 20 years decrying this, but if you add up the time you spend planning, negotiating schedules, then executing, it's less pain if you just work-to-deadline and throw features overboard in the process.On teams: A disciplined team of professionals cultivating mutual trust will outperform a team of talented jerks. There are exceptions, but only if you're writing the Linux kernel or something requiring 10x insights daily.On technology selection: Always pick the technology 1 step behind the bleeding edge, because it's mature and documented For example, when everyone was going to Rails, use Spring MVC. This will reduce your technical risk profile in every single case. Treat everyone as though they might be your boss someday.Code only exists if it…
Having just ended my second trip through The Five Love Languages by Dr. Chapman, there are things I really wish I could get through my thick skull.
Apropos: We just got through Valentine's Day and the occasion seems right.
1. Being "In Love"Ends
I remember my friend Dannah my freshman year. She was one of the strongest women I'd ever met. She had the grit and determination of her military dad, a sharp wit, and a heart as big as Dayton, Ohio. But there was one thing.
Dannah was terrified that her hometown beau, Tom, was going to "fall out of love with her." They'd been in love for years, and with distance and experience, it seemed like that ooey-gooey feeling of "love" was going to stop.
Well...it did. The thing idiots like us didn't realize was: IT ALWAYS STOPS.
Chapman argues in his book that the "in love" feeling that consumes you and spackles over every bump in your relationship might last about 2 or so years on average. …
I'm not a program manager, project manager, team lead, architect, business analyst, sytems analyst, or whatever other term means "Doesn't code anymore."
I make my living by telling machines what to do so the company I work for can make money (alot of it) and pay me money (a little of it, but an obscene amount still).
As I sit here, I'm 2 days away from ending a three year stint with one team, and picking up with another within the same company. The reasons aren't complicated, but it's impolitic to go into them. Suffice it to say, I've been looking around for about 6 months internally and it took about a month to get through the transition. Monday is 'Go' day.
So I ponder: How many more of these do I have in me?
If I think really hard--then give up and look at my CV--I have had these jobs professionally: IT support (scripting, custom apps) for a group of 200 mechanical engineersProgramming a Ja…