News for hackers. Stuff that matters.
Re:Software Architecture Guide by vikingcaffiene on Saturday August 24, 2019 @11:29AM (#20787680)
Thanks for this. The initial wave of hate on this post had me worrying that we are collectively forgetting the lessons of the past. This industry continually re-invents the same concepts over and over again and just re-brands them. Once you recognize that, the writings of Fowler & Co become highly applicable to many scenarios.
Re:Software Architecture Guide by sidlls on Saturday August 24, 2019 @12:19PM (#20788004)
Is this because what they've written truly works or is it because they've simply managed the same thing as the loudest engineer in the office, at larger scale?
Re:Software Architecture Guide by vikingcaffiene on Saturday August 24, 2019 @01:06PM (#20788314)
Well HN knows a thing or two about the latter ;)

It’s because I write better software in a team setting when I apply the techniques and philosophies of Fowler & Co. The biggest complexity in software is people. Coordinating them, navigating egos, and leveraging their experience levels. It’s a hard problem and the place where I see the most consistent system problems.

IMO Fowler is just providing accessible common sense strategies for dealing with that complexity.

Re:Software Architecture Guide by atoav on Saturday August 24, 2019 @01:52PM (#20788574)
Interestingly enough this social factor is also the hardest to deal with in other scenarios (expeditions, film crews, multi-party-projects, ...)