05 / Blog
Practical thinking on business software.
Plain-English notes on software decisions, delivery and technical leadership.
Showing 97 to 108 of 110 articles
Page 9 of 10
Technical Debt: How to Find It and Decide What to Fix
Learn how to identify, record and prioritise technical debt by the delivery cost, operational risk and future work it affects.
What Is SaaS Application Development? From Idea to Operation
Follow the decisions involved in planning, building and operating a SaaS application, from its first workflow to security, billing and support.
The technical risks boards should ask about earlier
Security, compliance, supplier dependency, technical debt and delivery risk explained in business language.
Moving from Fragile Spreadsheets to a Secure Custom Web Portal
How to move a vital business workflow from Excel or Google Sheets into a secure web portal without losing data or disrupting the team.
Agile Software Development: Build in Small Steps Without Losing Control
Learn how agile software development uses small usable releases, real feedback and clear priorities without losing control of scope, quality or ownership.
What Is Docker? Containers, Images and Compose Explained
Understand Docker containers, images, Compose and storage through one practical business application, including the limits Docker does not remove.
How to manage external developers and agencies without losing control
What leadership teams need in place to keep suppliers accountable, protect quality and reduce technical risk.
12 App Features That Are Easy to Forget Before Launch
Twelve overlooked app features that protect user work, reveal failures and make a mobile or business app easier to support after launch.
Scaling SaaS from £1m to £20m ARR Without Breaking the Product
Learn what must change as SaaS grows from £1m to £20m ARR, including product focus, tenant operations, onboarding, billing, reliability and retention.
How to ship faster without creating technical debt
Why good technical leadership protects momentum without pretending trade-offs do not exist.
Software Design Patterns: Solve the Repeated Problem, Not the Diagram
Learn how software design principles and Strategy, Factory, Adapter and Observer patterns support safer change without needless abstraction.
Software Architecture: Make the Difficult Decisions Before They Become Expensive
What software architecture means in practice, which structural decisions matter, how to avoid needless complexity and how to record trade-offs before change becomes expensive.