31
TeamTopologies
A model that helps people design effective teams for software development.
Martin Fowler
A website on building software effectively
- Popular posts
- 84
- Total points
- 17,806
- HN comments
- 10,168
- Rank
- #33 personal
Visit martinfowler.com → On Hacker News Jun 2009 – Oct 2026
Software Engineering 66Career & Management 20Tech Industry & Business 15AI & Machine Learning 13Society, Policy & Culture 10Systems & Performance 8
32
Building Boba AI: Lessons learnt in building an LLM-powered application
A series of patterns for building an AI co-pilot application.
33
A Guide to Threat Modelling for Developers
Threat modeling is a risk based approach to cyber security requirements analysis.
34
Ship / Show / Ask: A modern branching strategy
Ship/Show/Ask is a branching strategy that helps teams wait less and ship more, without losing out on feedback.
35
On Pair Programming
A guide to effective pair-programming
36
Microservices and the First Law of Distributed Objects
In P of EAA I said "don't distribute your objects". Does this advice contradict my interest in Microservices?
37
Conway’s Law (2022)
Systems are constrained to follow the communication patterns of their designers.
38
DataLake
A Data Lake is a store that hold raw data as a source for data scientists to explore ways to gain information. It should not be accessed by end-users or used for system integration.
39
The Learning Loop and LLMs
How continuous learning shapes effective software development with LLMs
40
GUI Architectures (2006)
Describing the way architectures for UIs have evolved over the years, in particular the many and often misunderstood definitions for Model-View-Controller.
41
The consequences of task switching in supervisory programming
the future of senior developers, junior developers, more on cognitive debt, DevEx versus AgentEx, the role of IDEs, consequences of task switching in supervisory programming
42
Understanding Spec-Driven-Development: Kiro, Spec-Kit, and Tessl
Notes from my colleagues on AI-assisted software delivery
43
One Line of Code That Compromises Your Server
Demonstrating how a weak session secret can allow an attacker to take control of a server
44
DSLs Enable Reliable Use of LLMs
Why Domain-Specific Languages and good abstractions make LLM code generation reliable and reviewable.
45
Domain Logic and SQL (2003)
A long-form article entitled: "Domain Logic and SQL"
46
Data Fetching for Single-Page Apps
Five patterns to help Single Page Applications fetch data from remote sources
47
CQRS: Command Query Responsibility Segregation (2011)
CQRS (Command Query Responsibility Segregation) is the notion that you can use a different model to update information than the model you use to read information
48
Sacrificial Architecture
Sometimes it's a good thing to be writing code that you expect to throw away in a couple of years time.
49
Microservices
Defining the microservices architectural style by describing their nine common characteristics
50
The LMAX Architecture (2011)
LMAX is a retail financial trading system that can handle that can 6 million orders per second on a single JVM thread. The business logic runs in-memory surrounded by disruptors using event sourcing.
51
Is Design Dead? (2004)
The rise of agile methods (particularly XP) makes some people wonder if there's any role left for software design. I argue that this change shifts from planned to evolutionary design.
52
Event Sourcing (2005)
Capture all changes to an application state as a sequence of events.
53
Why are good developers so wary of agentic development?
Good developers’ caution about agentic development comes from knowing that built isn’t the same as working in production.
54
OrmHate
Object-Relational Mappers get a lot of hate from people who misjudge the complexities of the task.
55
Two Hard Things (2009)
There are only two hard things in Computer Science: cache invalidation and naming things -- Phil Karlton (bonus variations on the page)
56
Snowflake Server
a bliki entry for Snowflake Server
57
Mocks Aren't Stubs (2007)
Explaining the difference between Mock Objects and Stubs (together with other forms of Test Double). Also the difference between classical and mockist styles of unit testing.
58
Feature Toggles
Feature Flags can be categorized into several buckets; manage each appropriately. Smart implementation can help constrain complexity.
59
bliki: Bounded Context
Don't try to build a single, unified model for a large domain. Instead DDD advises us to divide such a domain into many bounded contexts with explicit relationships between them.
60
Continuous Integration
Every developer integrates their work into mainline at least every day.