I've worked at various tech companies: from "traditional" shops and consultancies, through an investment bank, to high-growth tech firms. I've also talked with software engineers working at startups, banking, automotive, big tech, and more "traditional" companies. This mix had a healthy sample of Silicon-Valley companies and ones headquartered outside this| The Pragmatic Engineer
Monday is election day! Back in December 2019, I wrote a set of suggestions for the next GC Chief Information Officer. In the same tradition, here are some suggestions for the next Minister of Digital Government. Digital government work – and public service reform, which is what it ultimately is – isn’t really a newsworthy election topic. It’s near and dear to my heart, though, and I’d love to see more conversations about it from public servants, politicians, and the public alike. W...| sboots.ca
A couple weeks ago, I was able to tune in to FWD50, an annual Canadian digital government conference. One of the themes from the first day onwards was this concept, that government institutions are tech companies without realizing it. Just like “every company is a software company”, public sector institutions need to think differently about how they work, and what leadership they have, in order to be successful today.| sboots.ca
“Agile” gets mentioned enough in digital government work that can sometimes seem like it applies to everything: is anything not agile? But there’s a deeper meaning behind it that’s easy to miss: adding agile practices without removing established, “waterfall” processes that slow a team down is a recipe for frustration. Being agile means choosing one approach over another, and deliberately prioritizing what you spend your time on.| sboots.ca
As a public servant trying to get something approved up the hierarchy, the simplest definition of blockers versus enablers might be a “no” or “yes” at each level. In practice, however, the time it takes to receive these – and the quantity of approvals required – are bigger structural factors, regardless of how positive or supportive individual approvals are. This post dives into organizational blockers as a concept, with some potential strategies to mitigate them.| sboots.ca
Leah Lockhart captures in a profound way why government systems and software tend to be so bad. Bad government software – the user-hostile, complicated, enterprise systems that public servants everywhere are accustomed to – trains public servants to have low expectations of government software systems. Then, as they progress over time into leadership roles, they make IT decisions based on the low expectations they were trained to expect.| sboots.ca
One of the terms that comes up often in digital government work is “shipping”, or getting things out the door. Let’s take a look at why shipping is important, why it’s so hard, and ways to make it easier.| sboots.ca