This is a somewhat specific detail, but it comes up a lot, so I wanted to pull it out. If you run a bunch of 5 Whys, you’ll find that a lot of times, the developer who made the first-order mistake (forgot to copy configs from QA to Prod, or deployed two apps out of order, or whatever), will say “Look, this was totally my fault, I screwed up, that’s the whole story. I’ll be more careful next time.”
The very short summary of which is: We’re going to fix this problem by being less stupid in the future.
Which, well, you can guess how that’s going to turn out.
Why do some developers at strong companies like Google consider Agile development to be nonsense? Most points resonate — particularly this one:
10. Simplicity–the art of maximizing the amount of work not done–is essential. – Most teams simply don’t spend enough time on this. A sense of urgency often overrides careful planning. The problem here is careful planning makes things get done faster. During the planning stage it feels like you’re not getting anywhere, but you are setting up for a quick sprint. This setup is often overlooked, and we end up with not only complicated software, but complicated development habits, complicated code, and generally poor software design. This slows down maintenance and new development, as we try to fit into poorly designed structures that become ingrained and impossible to improve.
Lessons learned from scaling a product team. Great read — lots of details about product definition workflow and team composition to crib from.
Startup equity benefits your boss, not you. Why you should be extremely cautious about VC-fueled rocket ships.
Management is the care and feeding of the invisible. You’re doing your best when it appears the least is happening. I love the thrill of the last month of a release as much of the next guy, but I suspect the reason we’re yelling at each other, working weekends, and feeling the depressing weight of compromise is because we’re surrounded by Malcolm events [, seemingly insignificant events that are intent on screwing you in an unlikely way.]
Michael Lopp — Managing Humans
Remote work: an engineering leader’s perspective. Great read with practical tips.
Essays from Peter Thiel’s Stanford class on startups. In a nutshell, freely available material like this is why I am a college dropout. Every essay is worth reading — queue up your Pocket. I particularly appreciated this one on markets, competition, and monopolies. (via Spittle)
How much should a custom WordPress website cost? Excellent piece by Brian Krogsgard — every paragraph rings with truth.
What I’ve learned so far about consulting work:
- Harvest feeds the OCD time tracker inside of me.
- Creating proposals is a huge time suck.
- There’s so much room for automating all of this.
10 Things We Forgot to Monitor. Great list from Bitly.