Software development quotes
From my experience, successful KPIs follow the following six rules: Rule 1 – A KPI should be measurable. Don’t settle for boolean ‘yes or no’, or something amorphous that you can’t measure. Let’s say that you want to get into fitness. Let me ask you, what does ‘getting into fitness’ …
Before writing code to solve all but the most trivial of software problems, a software engineer should write a tech spec. Some software engineers may regard writing specs as unnecessary process that gets in the way of the agile approach. The point of a tech spec is not to impede …
It’s beyond time we reexamine the post-incident question of luck, and I submit: asking “how we were lucky” in an incident retrospective is not only a waste of you and your colleague’s time, it is distractingly detrimental to post-incident analysis.
The majority of failures you will see will actually be good ones – mini failures as decisions are taken by those who are less experienced. These are good because the process facilitates quick decisions, by those who need them, and more importantly, it facilitates transparency and rapid identification of failures …
I’ve been fortunate in my recent roles, having built up enough track record, that the organization leadership has trusted me, allowed me the time and space to do this type of work. With that trust comes a high expectation and responsibility to deliver, so to sustain it you need to …
At the beginning of a Tetris game, you start with an empty game. It’s like the very beginning of a coding project when there is nothing yet. Then blocks start to fall down. The way you position each block has an impact on the rest of the game. If you …
