Insights
Technical articles on languages, databases, serverless platforms and the awkward realities of keeping systems moving.
Showing 10–18 of 71 articles
How startup culture can create speed, ownership and closeness to customers, and how to retain those strengths as a company grows without normalising burnout, vague decisions or layers of corporate process.
Read articleHow to reduce noise in software engineering across code, pull requests, planning, monitoring and communication, so teams can spot meaningful change, make sound decisions and spend less time sorting through low-value activity.
Read articleWhy smaller pull requests are easier to review, test and release, how to split work without losing the thread of a feature, and when a larger coordinated change is the safer choice.
Read articleA practical guide to common software-development ticket types, including user stories, bugs, spikes, technical stories, chores and incidents, with guidance on choosing the right type and writing each one clearly.
Read articleWhy a developer salary benchmark needs context, and how underpaying a software team can increase hiring cost, attrition, delivery risk, lost knowledge and the price of future change.
Read articleHow to choose system-design patterns from real product constraints: clear boundaries, data ownership, synchronous and asynchronous coordination, resilience and gradual change.
Read articleA practical introduction to PostgreSQL and SQL: creating tables, selecting and joining data, safely changing rows, transactions, indexes and the habits that keep application queries understandable.
Read articleA practical reading of the twelve principles behind the 2001 Agile Manifesto: early value, useful feedback, technical quality, sustainable teams and adaptation without ceremony for its own sake.
Read articleA practical guide to layered, hexagonal, vertical-slice, modular-monolith, service, event-driven, CQRS and migration patterns, and the constraints that justify each one.
Read articleStart a conversation
A feature that needs shipping, an ageing service that needs attention, or a deployment that has become harder than the code. Talk to us about your problems.