News for hackers. Stuff that matters.
Re:Society's Technical Debt and Software's Gutenberg Moment by jiggawatts on Saturday March 25, 2023 @11:06PM (#35310373)
As an external consultant every time I see this scenario it’s always a group that is too busy digging with shovels to learn how to operate the backhoe.

Literally just last week I was showing several dev teams how to cut days out of their troubleshooting time by using an APM that can capture debug snapshots from production. Combine with source indexing during builds and code versioned with the Git commit id and you can jump to the line of code with the issue in about a minute. You’ll see the stack variables and everything. This is possible even in a distributed microservices monstrosity.

It takes like a day to wire this up.

“We’re too busy for that today, there’s an issue in production!”

Re:Society's Technical Debt and Software's Gutenberg Moment by plugin-baby on Saturday March 25, 2023 @11:11PM (#35310400)
What’s an APM? Bingle are not helping.
Re:Society's Technical Debt and Software's Gutenberg Moment by JudsonStevens on Saturday March 25, 2023 @11:17PM (#35310446)
APM generally stands for Application Performance Monitoring - an example is DataDogs APM module[1].

1 - https://www.datadoghq.com/product/apm/

Re:Society's Technical Debt and Software's Gutenberg Moment by adrienthebo on Saturday March 25, 2023 @11:16PM (#35310437)
Re:Society's Technical Debt and Software's Gutenberg Moment by bottlepalm on Saturday March 25, 2023 @11:15PM (#35310431)
The millions of lines of tech debt combined with the pace our company moves and volumes (high tech manufacturing) would blow your mind. It’s thunder dome.
Re:Society's Technical Debt and Software's Gutenberg Moment by brundolf on Sunday March 26, 2023 @12:21AM (#35310898)
Yeah. I think many or most large established codebases/software stacks could be an order of magnitude or two simpler (making them an order of magnitude or two easier to iterate on, in terms of both time and number of devs needed)

But the reality we've discovered is that there's a constant gravitational force pulling most dev orgs to keep increasing complexity, forever, much faster than the actual product increases in complexity. We can avoid this at the individual level, maybe the team level, but at this point it feels unavoidable at the company or industry level