Lots of interesting articles, rather than spam each one as an individual topic here's an omnibus thread: Case studies in rearchitecting Architecture for generations Rearchitecting after...
Lots of interesting articles, rather than spam each one as an individual topic here's an omnibus thread:
What do you think is the most interesting article in this issue, other than the one you wrote? What's the most "haunted forest" codebase you've personally worked on? If you were starting a project...
What do you think is the most interesting article in this issue, other than the one you wrote?
What's the most "haunted forest" codebase you've personally worked on?
If you were starting a project from scratch, what principles would you try to follow to prevent your beautiful clean greenfield codebase from turning into a haunted forest?
Protobufs are good for server-to-server but a pretty awkward fit for browser code, though, due to types not supported by JavaScript like 64-bit integers. And last I looked, no serialization format...
Protobufs are good for server-to-server but a pretty awkward fit for browser code, though, due to types not supported by JavaScript like 64-bit integers. And last I looked, no serialization format beats JSON in a browser due to native support for it. So, there are a variety of protobuf mappings to JSON and a standard, impractical one.
Lots of interesting articles, rather than spam each one as an individual topic here's an omnibus thread:
Case studies in rearchitecting
Architecture for generations
Rearchitecting after acquisition
Illuminating the grid: Here’s a look at the challenges facing the software powering our electrical grids—and some of the proposed solutions
The rise of nanoservices
A monorepo renaissance
Architecting privacy: How to protect user data at every layer of a web application
Interview with Nick Woods: The former lead architect of Apple’s iCloud Photo Library talks infrastructure, privacy, and system design
Software architecture at scale: Leaders at Foursquare, Hulu, and Twitter discuss early architecture decisions, downstream effects, and architectural philosophies
Systems analysis through postmortems
Exit the haunted forest: Enough is enough with that thicket of code impeding nearby work, trapping the unwary, discouraging the inexperienced, and exhausting veteran developers
A primer on functional architecture
Ask an expert: What’s the best way to upgrade an outdated codebase?
Plus one that I submitted to ~space since it seemed to fit in well there:
https://tildes.net/~space/m63/how_nasa_relies_on_resilient_software_running_on_redundant_hardware_to_make_up_for_physical_defects
I hadn't heard of Increment, thanks for the link! I'm a sucker for that print edition.
What do you think is the most interesting article in this issue, other than the one you wrote?
What's the most "haunted forest" codebase you've personally worked on?
If you were starting a project from scratch, what principles would you try to follow to prevent your beautiful clean greenfield codebase from turning into a haunted forest?
Protobufs are good for server-to-server but a pretty awkward fit for browser code, though, due to types not supported by JavaScript like 64-bit integers. And last I looked, no serialization format beats JSON in a browser due to native support for it. So, there are a variety of protobuf mappings to JSON and a standard, impractical one.