#technicaldebt — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #technicaldebt, aggregated by home.social.
-
ARGH!!!
Diese vermaledeiten SC/SC Patchfelder machen mich noch kirre!
Ratet mal, welche Kabel ich nicht mehr in ausreichender Laenge habe.
Tausche gerne gegen ST/ST auf SC/SC. Brauche SC/SC auf LC/LC, 7m.
Hmpf...
#network #sysadmin #networkadmin #technicaldebt #oeffentlicherDienst
-
ARGH!!!
Diese vermaledeiten SC/SC Patchfelder machen mich noch kirre!
Ratet mal, welche Kabel ich nicht mehr in ausreichender Laenge habe.
Tausche gerne gegen ST/ST auf SC/SC. Brauche SC/SC auf LC/LC, 7m.
Hmpf...
#network #sysadmin #networkadmin #technicaldebt #oeffentlicherDienst
-
ARGH!!!
Diese vermaledeiten SC/SC Patchfelder machen mich noch kirre!
Ratet mal, welche Kabel ich nicht mehr in ausreichender Laenge habe.
Tausche gerne gegen ST/ST auf SC/SC. Brauche SC/SC auf LC/LC, 7m.
Hmpf...
#network #sysadmin #networkadmin #technicaldebt #oeffentlicherDienst
-
ARGH!!!
Diese vermaledeiten SC/SC Patchfelder machen mich noch kirre!
Ratet mal, welche Kabel ich nicht mehr in ausreichender Laenge habe.
Tausche gerne gegen ST/ST auf SC/SC. Brauche SC/SC auf LC/LC, 7m.
Hmpf...
#network #sysadmin #networkadmin #technicaldebt #oeffentlicherDienst
-
ARGH!!!
Diese vermaledeiten SC/SC Patchfelder machen mich noch kirre!
Ratet mal, welche Kabel ich nicht mehr in ausreichender Laenge habe.
Tausche gerne gegen ST/ST auf SC/SC. Brauche SC/SC auf LC/LC, 7m.
Hmpf...
#network #sysadmin #networkadmin #technicaldebt #oeffentlicherDienst
-
Tired of running bundler-audit, Brakeman, RubyCritic and Skunk one at a time and then stitching the output together by hand? We built a Claude Code skill that runs 9 Ruby analysis tools and rolls them into a single tech debt health score across security, dependencies, coverage, complexity and maintainability. It's open source.
-
Tired of running bundler-audit, Brakeman, RubyCritic and Skunk one at a time and then stitching the output together by hand? We built a Claude Code skill that runs 9 Ruby analysis tools and rolls them into a single tech debt health score across security, dependencies, coverage, complexity and maintainability. It's open source.
-
Most of Your Tech Debt Is Free, by (not on Mastodon or Bluesky):
https://piechowski.io/post/most-of-your-tech-debt-is-free/?ref=frontenddogma.com
-
Most of Your Tech Debt Is Free, by (not on Mastodon or Bluesky):
https://piechowski.io/post/most-of-your-tech-debt-is-free/?ref=frontenddogma.com
-
Most of Your Tech Debt Is Free, by (not on Mastodon or Bluesky):
https://piechowski.io/post/most-of-your-tech-debt-is-free/?ref=frontenddogma.com
-
Most of Your Tech Debt Is Free, by (not on Mastodon or Bluesky):
https://piechowski.io/post/most-of-your-tech-debt-is-free/?ref=frontenddogma.com
-
Most of Your Tech Debt Is Free, by (not on Mastodon or Bluesky):
https://piechowski.io/post/most-of-your-tech-debt-is-free/?ref=frontenddogma.com
-
Ever tried explaining dependency rot to someone non-technical? Libyears gives you one number: how many years behind your gems are. We measured popular Ruby projects and one hit 548.7 libyears, over 2,000 releases and 71 major versions behind. Fewer dependencies means less to rot. Measure it before it bites. https://go.fastruby.io/717 #Ruby #TechnicalDebt #DependencyManagement
-
Ever tried explaining dependency rot to someone non-technical? Libyears gives you one number: how many years behind your gems are. We measured popular Ruby projects and one hit 548.7 libyears, over 2,000 releases and 71 major versions behind. Fewer dependencies means less to rot. Measure it before it bites. https://go.fastruby.io/717 #Ruby #TechnicalDebt #DependencyManagement
-
Before you touch a Rails upgrade, find out which files will bite you first.
Skunk scores every file by churn, complexity, and test coverage so you know exactly where manual QA is worth the time.
Pair it with `next_rails` to dual boot two Rails versions at once and watch the deprecations surface. All free, all open source.
-
Before you touch a Rails upgrade, find out which files will bite you first.
Skunk scores every file by churn, complexity, and test coverage so you know exactly where manual QA is worth the time.
Pair it with `next_rails` to dual boot two Rails versions at once and watch the deprecations surface. All free, all open source.
-
““The biggest challenge is documentation being out of sync with the API that’s available,” says Sundaresan. “Docs being out of sync is actually a worse problem today since we release much faster.”
While working at Microsoft, he found some Azure command-line interfaces (CLIs) had more than 1,500 commands. CLIs and APIs change with new versions, and new parameters are often added without updating the corresponding documentation. To his point, a 2024 APIContext study found that 75% of production APIs don’t match their specification files. This mismatch can break integrations and applications.
Knowledge decay also creates substantial rework. “The challenge is everywhere,” says Sundaresan.
“Back when I worked at eBay, engineers would get moved around all the time,” he says. Much of the work relied on consultants, who would move on to the next job once a project was complete. This led to substantial duplication, as later developers would struggle to understand the original code and decide to redo it or change large portions of it.
He estimates that only 15% to 20% of code is newly written, while 60% to 65% involves modernization, migration, and maintenance. Whether it’s out of sync documentation or opaque code bases, that one missing link can result in significant wasted effort. “You can get 99% right, but then the 1% that you get wrong can appear as a huge time sink.””
https://leaddev.com/ai/how-to-avoid-knowledge-decay-in-software-engineering
#TechnicalDebt #SoftwareEngineering #Documentation #TechnicalWriting #SoftwareDevelopment #AI #LLMs
-
““The biggest challenge is documentation being out of sync with the API that’s available,” says Sundaresan. “Docs being out of sync is actually a worse problem today since we release much faster.”
While working at Microsoft, he found some Azure command-line interfaces (CLIs) had more than 1,500 commands. CLIs and APIs change with new versions, and new parameters are often added without updating the corresponding documentation. To his point, a 2024 APIContext study found that 75% of production APIs don’t match their specification files. This mismatch can break integrations and applications.
Knowledge decay also creates substantial rework. “The challenge is everywhere,” says Sundaresan.
“Back when I worked at eBay, engineers would get moved around all the time,” he says. Much of the work relied on consultants, who would move on to the next job once a project was complete. This led to substantial duplication, as later developers would struggle to understand the original code and decide to redo it or change large portions of it.
He estimates that only 15% to 20% of code is newly written, while 60% to 65% involves modernization, migration, and maintenance. Whether it’s out of sync documentation or opaque code bases, that one missing link can result in significant wasted effort. “You can get 99% right, but then the 1% that you get wrong can appear as a huge time sink.””
https://leaddev.com/ai/how-to-avoid-knowledge-decay-in-software-engineering
#TechnicalDebt #SoftwareEngineering #Documentation #TechnicalWriting #SoftwareDevelopment #AI #LLMs
-
““The biggest challenge is documentation being out of sync with the API that’s available,” says Sundaresan. “Docs being out of sync is actually a worse problem today since we release much faster.”
While working at Microsoft, he found some Azure command-line interfaces (CLIs) had more than 1,500 commands. CLIs and APIs change with new versions, and new parameters are often added without updating the corresponding documentation. To his point, a 2024 APIContext study found that 75% of production APIs don’t match their specification files. This mismatch can break integrations and applications.
Knowledge decay also creates substantial rework. “The challenge is everywhere,” says Sundaresan.
“Back when I worked at eBay, engineers would get moved around all the time,” he says. Much of the work relied on consultants, who would move on to the next job once a project was complete. This led to substantial duplication, as later developers would struggle to understand the original code and decide to redo it or change large portions of it.
He estimates that only 15% to 20% of code is newly written, while 60% to 65% involves modernization, migration, and maintenance. Whether it’s out of sync documentation or opaque code bases, that one missing link can result in significant wasted effort. “You can get 99% right, but then the 1% that you get wrong can appear as a huge time sink.””
https://leaddev.com/ai/how-to-avoid-knowledge-decay-in-software-engineering
#TechnicalDebt #SoftwareEngineering #Documentation #TechnicalWriting #SoftwareDevelopment #AI #LLMs
-
““The biggest challenge is documentation being out of sync with the API that’s available,” says Sundaresan. “Docs being out of sync is actually a worse problem today since we release much faster.”
While working at Microsoft, he found some Azure command-line interfaces (CLIs) had more than 1,500 commands. CLIs and APIs change with new versions, and new parameters are often added without updating the corresponding documentation. To his point, a 2024 APIContext study found that 75% of production APIs don’t match their specification files. This mismatch can break integrations and applications.
Knowledge decay also creates substantial rework. “The challenge is everywhere,” says Sundaresan.
“Back when I worked at eBay, engineers would get moved around all the time,” he says. Much of the work relied on consultants, who would move on to the next job once a project was complete. This led to substantial duplication, as later developers would struggle to understand the original code and decide to redo it or change large portions of it.
He estimates that only 15% to 20% of code is newly written, while 60% to 65% involves modernization, migration, and maintenance. Whether it’s out of sync documentation or opaque code bases, that one missing link can result in significant wasted effort. “You can get 99% right, but then the 1% that you get wrong can appear as a huge time sink.””
https://leaddev.com/ai/how-to-avoid-knowledge-decay-in-software-engineering
#TechnicalDebt #SoftwareEngineering #Documentation #TechnicalWriting #SoftwareDevelopment #AI #LLMs
-
““The biggest challenge is documentation being out of sync with the API that’s available,” says Sundaresan. “Docs being out of sync is actually a worse problem today since we release much faster.”
While working at Microsoft, he found some Azure command-line interfaces (CLIs) had more than 1,500 commands. CLIs and APIs change with new versions, and new parameters are often added without updating the corresponding documentation. To his point, a 2024 APIContext study found that 75% of production APIs don’t match their specification files. This mismatch can break integrations and applications.
Knowledge decay also creates substantial rework. “The challenge is everywhere,” says Sundaresan.
“Back when I worked at eBay, engineers would get moved around all the time,” he says. Much of the work relied on consultants, who would move on to the next job once a project was complete. This led to substantial duplication, as later developers would struggle to understand the original code and decide to redo it or change large portions of it.
He estimates that only 15% to 20% of code is newly written, while 60% to 65% involves modernization, migration, and maintenance. Whether it’s out of sync documentation or opaque code bases, that one missing link can result in significant wasted effort. “You can get 99% right, but then the 1% that you get wrong can appear as a huge time sink.””
https://leaddev.com/ai/how-to-avoid-knowledge-decay-in-software-engineering
#TechnicalDebt #SoftwareEngineering #Documentation #TechnicalWriting #SoftwareDevelopment #AI #LLMs
-
We refreshed how we run static analysis for clients. It now leans on RubyCritic for complexity and churn, SimpleCov to surface well-worn files with thin coverage, and Brakeman for Rails CVEs. Five repeatable steps, all open source, no proprietary dashboard in the loop.
-
We refreshed how we run static analysis for clients. It now leans on RubyCritic for complexity and churn, SimpleCov to surface well-worn files with thin coverage, and Brakeman for Rails CVEs. Five repeatable steps, all open source, no proprietary dashboard in the loop.
-
@nobsagile oh dear 😂 der letzte Refactoring-Sprint, den ich einmal als PM/PO drei Monate im Voraus vereinbart hatte, wurde abgesagt: Am Rande eines 1+1 richtete mir die dienstjüngste Agenturentwicklerin aus, dass die Agentur ja in KW x und y Sommerurlaub macht. Laut Tailwind-Bundle ist die Webanwendung, um die es ging, just dieser Tage exakt drei Jahre auf dem technischen Stand von vorm Sommerurlaub 🤭
-
@nobsagile oh dear 😂 der letzte Refactoring-Sprint, den ich einmal als PM/PO drei Monate im Voraus vereinbart hatte, wurde abgesagt: Am Rande eines 1+1 richtete mir die dienstjüngste Agenturentwicklerin aus, dass die Agentur ja in KW x und y Sommerurlaub macht. Laut Tailwind-Bundle ist die Webanwendung, um die es ging, just dieser Tage exakt drei Jahre auf dem technischen Stand von vorm Sommerurlaub 🤭
-
@nobsagile oh dear 😂 der letzte Refactoring-Sprint, den ich einmal als PM/PO drei Monate im Voraus vereinbart hatte, wurde abgesagt: Am Rande eines 1+1 richtete mir die dienstjüngste Agenturentwicklerin aus, dass die Agentur ja in KW x und y Sommerurlaub macht. Laut Tailwind-Bundle ist die Webanwendung, um die es ging, just dieser Tage exakt drei Jahre auf dem technischen Stand von vorm Sommerurlaub 🤭
-
@nobsagile oh dear 😂 der letzte Refactoring-Sprint, den ich einmal als PM/PO drei Monate im Voraus vereinbart hatte, wurde abgesagt: Am Rande eines 1+1 richtete mir die dienstjüngste Agenturentwicklerin aus, dass die Agentur ja in KW x und y Sommerurlaub macht. Laut Tailwind-Bundle ist die Webanwendung, um die es ging, just dieser Tage exakt drei Jahre auf dem technischen Stand von vorm Sommerurlaub 🤭
-
@nobsagile oh dear 😂 der letzte Refactoring-Sprint, den ich einmal als PM/PO drei Monate im Voraus vereinbart hatte, wurde abgesagt: Am Rande eines 1+1 richtete mir die dienstjüngste Agenturentwicklerin aus, dass die Agentur ja in KW x und y Sommerurlaub macht. Laut Tailwind-Bundle ist die Webanwendung, um die es ging, just dieser Tage exakt drei Jahre auf dem technischen Stand von vorm Sommerurlaub 🤭
-
Nearly two years of staggered Rails upgrades across multiple apps, and the scoreboard for a 500-person publicly traded company: infrastructure costs down 5 to 10 percent, faster product development, and better engineer morale. Their words: more stable, moving faster, costs going down. https://go.fastruby.io/pf2 #RailsUpgrade #TechnicalDebt
-
Nearly two years of staggered Rails upgrades across multiple apps, and the scoreboard for a 500-person publicly traded company: infrastructure costs down 5 to 10 percent, faster product development, and better engineer morale. Their words: more stable, moving faster, costs going down. https://go.fastruby.io/pf2 #RailsUpgrade #TechnicalDebt
-
I'm manually editing a Python file on a deployed host to fix a known problem in the library that was installed via pip.
It's fixed the problem, telemetry is reporting in. But I feel unclean.
-
I'm manually editing a Python file on a deployed host to fix a known problem in the library that was installed via pip.
It's fixed the problem, telemetry is reporting in. But I feel unclean.
-
I'm manually editing a Python file on a deployed host to fix a known problem in the library that was installed via pip.
It's fixed the problem, telemetry is reporting in. But I feel unclean.
-
I'm manually editing a Python file on a deployed host to fix a known problem in the library that was installed via pip.
It's fixed the problem, telemetry is reporting in. But I feel unclean.
-
I'm manually editing a Python file on a deployed host to fix a known problem in the library that was installed via pip.
It's fixed the problem, telemetry is reporting in. But I feel unclean.
-
Struggling with tech debt?
Quick fix: name it, place it, decide it:1️⃣ Reckless + Deliberate = landmine
2️⃣ Reckless + Inadvertent = skills gap
3️⃣ Prudent + Deliberate = calculated bet
4️⃣ Prudent + Inadvertent = learningFix landmines first, log the rest!
-
Struggling with tech debt?
Quick fix: name it, place it, decide it:1️⃣ Reckless + Deliberate = landmine
2️⃣ Reckless + Inadvertent = skills gap
3️⃣ Prudent + Deliberate = calculated bet
4️⃣ Prudent + Inadvertent = learningFix landmines first, log the rest!
-
With my apologies to Sun alumni (and my thanks to @NanoRaptor for the inspiration).
-
IT Cost Reduction Often Destroys Long-Term Value.
The cheapest technology decision is often the most expensive business decision. #CIO #Leadership #DigitalTransformation #TechnologyLeadership #BusinessTransformation #ITStrategy #ExecutiveLeadership #BoardLeadership #Innovation #Technology #DigitalStrategy #FutureOfWork #BusinessValue #Cybersecurity #EnterpriseTechnology -
IT Cost Reduction Often Destroys Long-Term Value.
The cheapest technology decision is often the most expensive business decision. #CIO #Leadership #DigitalTransformation #TechnologyLeadership #BusinessTransformation #ITStrategy #ExecutiveLeadership #BoardLeadership #Innovation #Technology #DigitalStrategy #FutureOfWork #BusinessValue #Cybersecurity #EnterpriseTechnology -
IT Cost Reduction Often Destroys Long-Term Value.
The cheapest technology decision is often the most expensive business decision. #CIO #Leadership #DigitalTransformation #TechnologyLeadership #BusinessTransformation #ITStrategy #ExecutiveLeadership #BoardLeadership #Innovation #Technology #DigitalStrategy #FutureOfWork #BusinessValue #Cybersecurity #EnterpriseTechnology -
IT Cost Reduction Often Destroys Long-Term Value.
The cheapest technology decision is often the most expensive business decision. #CIO #Leadership #DigitalTransformation #TechnologyLeadership #BusinessTransformation #ITStrategy #ExecutiveLeadership #BoardLeadership #Innovation #Technology #DigitalStrategy #FutureOfWork #BusinessValue #Cybersecurity #EnterpriseTechnology -
IT Cost Reduction Often Destroys Long-Term Value.
The cheapest technology decision is often the most expensive business decision. #CIO #Leadership #DigitalTransformation #TechnologyLeadership #BusinessTransformation #ITStrategy #ExecutiveLeadership #BoardLeadership #Innovation #Technology #DigitalStrategy #FutureOfWork #BusinessValue #Cybersecurity #EnterpriseTechnology -
Inheriting a #Rails app you've never seen?
-
Inheriting a #Rails app you've never seen?
-
🔗 Rewriting Bun in Rust
https://bun.com/blog/bun-in-rust
#memory #rust #ai #technicaldebt #migration -
🔗 Rewriting Bun in Rust
https://bun.com/blog/bun-in-rust
#memory #rust #ai #technicaldebt #migration -
🔗 Rewriting Bun in Rust
https://bun.com/blog/bun-in-rust
#memory #rust #ai #technicaldebt #migration -
🔗 Rewriting Bun in Rust
https://bun.com/blog/bun-in-rust
#memory #rust #ai #technicaldebt #migration -
🔗 Rewriting Bun in Rust
https://bun.com/blog/bun-in-rust
#memory #rust #ai #technicaldebt #migration -
Overbuilding Before Core Value is Proven is a common mistake software companies make. This way the company can achieve better positioning and avoids technical debt to a point.
More mistakes:
https://www.softwareantifragility.com/p/skeletons-as-a-service-part-1-startups
-
Overbuilding Before Core Value is Proven is a common mistake software companies make. This way the company can achieve better positioning and avoids technical debt to a point.
More mistakes:
https://www.softwareantifragility.com/p/skeletons-as-a-service-part-1-startups
-
Rails apps rarely die because of a single incident.
They die in a thousand small frictions: slow deploys, flaky tests, gem updates nobody touches. The fix is steady, not heroic. 60,000+ hours of FastRuby upgrade work, distilled.
-
Rails apps rarely die because of a single incident.
They die in a thousand small frictions: slow deploys, flaky tests, gem updates nobody touches. The fix is steady, not heroic. 60,000+ hours of FastRuby upgrade work, distilled.
-
Rails upgrades without a roadmap turn 6-week jobs into 9-month projects...
Two devs, 10-15 days of analysis, 40-90 prioritized tasks, best and worst-case estimates. Get a roadmap based on real experience (60,000 dev/hours upgrading Ruby and Rails!)
-
Rails upgrades without a roadmap turn 6-week jobs into 9-month projects...
Two devs, 10-15 days of analysis, 40-90 prioritized tasks, best and worst-case estimates. Get a roadmap based on real experience (60,000 dev/hours upgrading Ruby and Rails!)
-
AI - especially agentic AI - is inadvertently creating more technical debt. But there are a few steps one can take to help mitigate the situation.
https://www.markloveless.net/blog/2026/7/2/ai-and-technical-debt
-
AI - especially agentic AI - is inadvertently creating more technical debt. But there are a few steps one can take to help mitigate the situation.
https://www.markloveless.net/blog/2026/7/2/ai-and-technical-debt
-
AI - especially agentic AI - is inadvertently creating more technical debt. But there are a few steps one can take to help mitigate the situation.
https://www.markloveless.net/blog/2026/7/2/ai-and-technical-debt
-
AI - especially agentic AI - is inadvertently creating more technical debt. But there are a few steps one can take to help mitigate the situation.
https://www.markloveless.net/blog/2026/7/2/ai-and-technical-debt