Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #5395

S

Simon Brown

Personal blog · codingthearchitecture.comprogrammingdesign

Simon Brown's personal blog at codingthearchitecture.com covers programming and design. Since 2010, 15 different Hacker News readers have linked it 20 times, most often “Distributed big balls of mud (2014)”. No feed was found, so read it on the site itself.

No feed foundVisit the blog
20mentions?
15HN people?
2010–2022first – last linked?
Links on Hacker News per year · peak 3 in 2011

Too few sampled comments (4) to say how often HN recommends it.?

Why HN links it

HN readers link Simon Brown's blog for software architecture writing on cognitive load, package-by-component organisation and microservices versus monoliths, along with his conference talks.

Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Most-linked posts?

  1. Distributed big balls of mud (2014)
    4 people · 5 mentions · first linked 2014-07-06
  2. Today's software developers are the ivory tower architects of tomorrow
    2 people · 2 mentions · first linked 2018-02-09

What Hacker News says?

  1. Being able to keep the system you are working on in your mind with sufficient but excessive detail is key. Keeping the system in all is parts "as simple as possible and as complex as necessary" (that is my engineering philosophy) is what make se all the difference. I used to think: since I am smart I am going to write something more complex because I can manage that. Wrong. For the smart and dumb engineer a simpler…

    Comment linking /2014/07/06/distributed_big_balls_of_mud.html

    on “Forget monoliths vs. microservices: cognitive load is what matters”
  2. Submitted Distributed big balls of mud (2014) as a story · 48 points

    HN discussion
  3. Microservices are not to scale organization even if some organizations used them in this way. There is a big problem with this way of scaling. The sense ownership becomes the sense of defend your castle (team's microservice code) from invasion (external developer that are trying to add features or fix bugs). Microservices were also presented as a solution for encapsulation. But if you cannot write good encapsulated…

    Comment linking /2014/07/06/distributed_big_balls_of_mud.html

    on “Give me back my monolith (2019)”
  4. Submitted Software documentation as a guidebook as a story · 11 points

    HN discussion
  5. There is a great talk on this by Simon Brown http://www.codingthearchitecture.com/presentations/sa2015-mo... https://www.youtube.com/watch?v=h_rBDIC51C4

    Comment linking /presentations/sa2015-modular-monoliths

    on “Microservices”
  6. Submitted PaaS for Java Developers: Coding the Architecture as a story · 3 points

    HN discussion
  7. gumoro · 2017-07-05Recommends
    Higher cohesion and modularity. I'm glad to see this in an article for JavaScript projects. Here are a few articles for Java projects, that go in more details (I think the concepts still mostly apply to JavaScript projects): http://www.javapractices.com/topic/TopicAction.do?Id=205 http://www.codingthearchitecture.com/2015/03/08/package_by_c...

    Comment linking /2015/03/08/package_by_component_and_architecturally_aligned_testing.html

    on “A set of best practices for JavaScript projects”
  8. Submitted Layers, Hexagons, Features and Components as a story · 2 points

    HN discussion
  9. Submitted Today's software developers are the ivory tower architects of tomorrow as a story · 2 points

    HN discussion
  10. Submitted Today's software developers are the ivory tower architects of tomorrow as a story · 2 points

    HN discussion
  11. Submitted Visualising and documenting software architecture cheat sheets as a story · 2 points

    HN discussion
  12. Submitted Modular Monoliths – Coding the Architecture as a story · 2 points

    HN discussion
  13. Submitted Distributed big balls of mud as a story · 2 points

    HN discussion
  14. Submitted Where are the software architects of tomorrow? as a story · 2 points

    HN discussion
  15. Submitted Architectural constructs as a story · 2 points

    HN discussion
  16. Submitted Introducing Structurizr as a story · 1 points

    HN discussion
  17. Submitted Distributed big balls of mud – Coding the Architecture as a story · 1 points

    HN discussion
  18. Submitted Software Architecture for Developers - v1 of the book is published as a story · 1 points

    HN discussion
  19. Submitted Jitter - The forgotten performance metric as a story · 1 points

    HN discussion
  20. Submitted Collaborative Design as a story · 1 points

    HN discussion

Search all of HN for codingthearchitecture.com