An amazing tour de force compiling one of python’s core tools black to C using mypyc. There seems to be a lot of activity right now around compiling python code into different targets and also in distributing compiled binaries through python packages.
“Stripped of their original purpose, this is what so many Scrum events have become: a series of actions performed by rote.”
A lot of it has become theater and sprint planning may be one of the worst things any organization can do.
Lots of teams try to dogmatically implement scrum without looking at their team and goals. There are lots of alternative ways of doing things most of which will be more agile, not less.
It has been a while coming that for most workloads sqlite is more than good enough and at the same time also has a lot of operational benefits to offer. I never could believe all the hoops you have to jump through to get a postgres/mysql to run.
“People have 250 percent more meetings every day than they did before the pandemic,”
Lots of people default to meetings for everything they want to get done which leads to the negative effects listed in the article but is also a severe indictment of their competence and flexibility.
That’s nothing short of an amazing list of time management techniques geared specifically towards helping engineers achieve maximum impact.
- Defend your time
- Pay yourself first
- Defend others’ time
- Clearly designate interrupt-driven work
- Clearly designate low-leverage work
- Communicate with candor
- Prioritize ruthlessly
Become good at these and there are no limits to what you can achieve.
Lots of examples here by Intercom about how to enable teams to ship as fast as possible and at the same time also as safely as possible.
- Be available after shipping
- Ship instrumentation first
- Use feature flags
- Ship to a small subset of traffic
- Ship the “read” path first
- Document and share your plan and actions
Lots of good bits about learning to write in this despite the weird formatting in Substack.
Momentum definitely is magic and I’d add that you get it by focusing on tempo.
“Declaring a feature that’s in customers’ hands “done,” without monitoring, or with flaky tests, or tons of highly redundant code, or other obvious pending work, doesn’t magically get that work done. That work will always be there. It’ll just show up as surprises in your Maintenance Roadmap at an unknown date, when your team has mentally moved on and stopped thinking about the feature.”
Finish things, do them properly. Make problems go away.