News for hackers. Stuff that matters.
Re:Software Architecture Guide by goto11 on Sunday August 25, 2019 @08:49AM (#20792665)
I think there is some tribalism at play. Fowler and friends are writing about enterprise architecture. HN is probably more oriented towards startups which haven't yet reached that kind of challenges and constraints (and in most cases never will), and who feel superior to the dinosaurs. And then there is is the "computer scientists" who think software development should be based on proofs rather than experience and results.
Re:Software Architecture Guide by sidlls on Sunday August 25, 2019 @12:54PM (#20793975)
And then there are people like me. I've worked in big enterprise software departments (a huge homeowners insurance tech company, big banking, government contractors), "companies" of three people including myself, and some in between. Currently I'm at a 500-ish person company that is not quite enterprise but not really a start-up.

My experience is that "Enterprise Architecture" creates as many problems for the business as it solves for technology practitioners attempting to solve problems in a huge battle royale of competing departments. I think it often helps cement and provide feedback loops for the causes of the problems seen in large enterprise systems.

Re:Software Architecture Guide by goto11 on Sunday August 25, 2019 @02:10PM (#20794486)
This is where I get confused. Are you criticizing a particular architecture, or architecture in general? Is it even possible to have a system without an architecture?
Re:Software Architecture Guide by james_s_tayler on Monday August 26, 2019 @04:07AM (#20798159)
The Winchester Mystery House does exist in software somewhere.
Re:Software Architecture Guide by JeffGrigg on Monday August 26, 2019 @10:00AM (#20799901)
Even the Winchester Mystery House has architecture. Pretty good architecture. It's still standing, in spite of earthquakes. She bought it in 1884.

Now it has some fairly odd "features" based on her very eccentric "requirements." Doors that open into walls. Stairs that "go nowhere." Very expensive windows that look out at brick walls.

But given her odd sense of "requirements," it's the house she wanted!

Re:Software Architecture Guide by blub on Monday August 26, 2019 @09:08AM (#20799550)
The word enterprise is not included in the article, which makes it a generic article about architecture.

Experience and results are better then nothing. Where are the author's results?

Based on which project experience was the article authored? Without knowing such things, we can't distinguish what kind of outcome will the proposed ideas result in. After all, good results can be good on many dimensions.