Software Architecture Pitfalls and How to Avoid Them

Re:Software Architecture Pitfalls and How to Avoid Them by feoren on Thursday December 21, 2023 @11:18PM (#38730891)

Highlight all the code you have written / are responsible for. Have you highlighted just one single project that gets deployed as one unit? Then you have a monolith. Monolith doesn't mean you never talk to other services; it means you only own one.

[ Parent | on HN ]

Re:Software Architecture Pitfalls and How to Avoid Them by randomdata on Thursday December 21, 2023 @11:27PM (#38730938)

My coworker highlighted just one single project that gets deployed as one unit. I have a second hobby project I work on at home of which I also take ownership. He is building a monolith, I am not? Even though we are working on the exact same project?

Um. Okay. So, just so I am clear, the advice here can be rephrased as: "Save a matter of life or death, don't have hobbies"?

[ Parent | on HN ]

Re:Software Architecture Pitfalls and How to Avoid Them by feoren on Friday December 22, 2023 @12:03PM (#38736129)

I think you know what I meant. If you want exact definitions of words, study math.

[ Parent | on HN ]