In the first of a series exploring infrastructure fundamentals, Brenden addresses the most frequently asked questions about what's really happening under the hood with complex pipelines and AI/data systems, bringing the cloud to life.
What will the state of AI be like in a year's time? Here are Mike Veerman's predictions of what major things will happen next in AI
I recently encountered a issue with MySQL query performance. A particular query would perform very badly in production, but perform very well in the testing environments.
Outdated myths about developers—like “they hate meetings” or “only care about code”—create friction, missed context, and rework. Learn how to build healthier collaboration across engineering and product.
For small teams without a designer, v0 is a game-changer. The cost justifies itself by letting you explore and validate ideas in minutes rather than days.
I switched from Cursor's BugBot ($40/month) to Claude Code for code reviews. Setup is straightforward in VS Code, and Claude's bug detection has been notably better. While it still flags null reference checks like most AI reviewers, the difference in catching actual bugs is significant.
Building a thriving remote-first culture takes more than allowing people to work from home. Discover how hiring for ownership, embracing asynchronous work, and saying no to misaligned projects creates a sustainable remote future.
Shiny frameworks promise magic, but like cheap non-stick pans, they scratch, peel, and end up in the bin. Boring technology, like stainless steel, isn’t sexy, but it lasts for decades if treated well. The lesson? Build for the long haul, not the quick thrill.
AI is not replacing developers, but it is replacing developers who refuse to use it. The real skill lies in how well you steer, validate, and challenge the model. Fundamentals matter, but today’s best engineers treat AI as an amplifier, not a crutch.
