I don’t consider my daily routine to be involved in “software development” per se, even though I spend the majority of it writing code. I’m not sure what other name to give it, but after a recent on-site stint at a real software development company, these principles now have applicable context to me and I find it really interesting. In my particular line of work I’m working on one project until it’s done and then I’m on to the next. The feature set is defined during design and I’m responsible for implementing it until a subsequent phase comes to our inbox. That’s not the case when it comes to software development, there’s a lot of strategy when it comes down to the details, and that strategy can have devastating effects on your company year over year.
Get my newsletter
Receive periodic updates right in the mail!