As we all turn off for the long Easter weekend to contemplate, all I have for today are best wishes for you for Easter.
Wishing you Easter filled with blue skies and scrumptious chocolate!
Easter is a time to rejoice, be thankful, be assured that all is forgiven, so life extends beyond the soil of the earth.Byron Pulsifer
While we reflect and rest, here are the top three posts from this blog over the last 6 months.
Staying technical as a software engineering manager
I have my own strong opinion in this matter. The opinion is – being an engineering manager stops working once you stop being hands on. You are still a manager, but with each passing week of not jumping to hands on issues, you get further away. It becomes harder and harder to understand engineers. Up to a point where you stop being an engineering manager. You just can’t do it anymore.
A pragmatic take on Principal Engineering – Part 1
As I was reading an interesting book by Christopher Alexander – A Pattern Language: Towns, Buildings, Construction (1977), it hit me. Software engineering should not be that much different. One, it should have some people who create a vision of the work to be completed, and then work hard to create a language by which most of the other people in the enterprise would communicate. Two, software products should have some kind of a technical pattern language.
This is how one of my favourite authors describes what leads to deprioritizing quality. I was wondering myself – what leads to it? What is making it difficult for organizations to recognize Quality? Why attempts to make everything efficient usually result in death to quality? Is the unicorn of achieving efficiency without loosing on quality possible?
Thanks and see you in a week!