The secret to getting promoted

The secret to getting promoted
7 minutes by Bjorn Roche

Getting promoted is less about ticking boxes and more about earning trust. Decision makers tend to decide emotionally first, then use the evidence to back it up. Focus on what builds trust in your specific situation, whether that means making your work more visible or staying out of office politics. Meet the formal requirements, but know that trust is usually what seals the deal.

Still writing tests manually? Meticulous AI is here
sponsored by Meticulous

Most teams are forced to make the tradeoff between better coverage and more maintenance effort. But top engineering teams like Notion, Dropbox, Wealthsimple and LaunchDarkly have discovered a new testing paradigm. Built by ex-Palantir engineers, Meticulous creates and maintains E2E UI tests that covers every edge case of your web app - without any developer effort, making it the only tool to improve both product quality and dev velocity.

The unreachable engineering managers
4 minutes by Anton Zaides

Highly responsive managers unblock their teams faster and keep projects moving. When technical managers become hard to reach, engineers stall, make poor decisions, or waste time finding workarounds. The fix starts with treating responsiveness as a core duty: reply quickly, organize your channels, and delegate ownership where possible.

Shell had six years to prepare. I had four months.
12 minutes by Phil McKinney

Leaders keep getting blindsided by crises they could have seen coming. Shell survived the 1973 oil embargo because its teams had already thought through that exact scenario before it hit. HP has cycled through six CEOs in 25 years, each time scrambling under pressure instead of preparing in advance. The real lesson: do the hard thinking while you still have time, because once the clock starts, the options you never built simply do not exist.

Bias toward action
13 minutes by Addy Osmani

Moving fast isn't about skipping steps — it's about building safety nets that make frequent, small changes survivable. Fast teams use feature flags, good monitoring, and practiced rollbacks so that being wrong stays cheap and fixable. Error budgets replace debates about speed versus reliability with clear, shared rules. Start with one service, make deploying boring, and let the results speak for themselves.

Engineering maturity is all you need
11 minutes by Govind Krishna Joshi

Building reliable AI apps isn't about picking the right model or prompt tricks. It's about engineering discipline: documentation, testing, observability, and evals. Teams that skip these foundations can demo well but fall apart in production. The real goal is building a system that lets you discover what works through fast, structured iteration, because in AI development, that learning loop is everything.