@diana The dishwasher and washing machine would be CI/CD or some kind of automation I suppose in this metaphor. And we know how much we let dishes and laundry pile up. Show me your kitchen sink! 😅 #TechDebt
How well do #OpenSource and #FOSS projects deal with #techdebt ? I've talked to a few people that say it's a struggle as reducing techdebt isn't seen as "fun" so much harder to attract contributors.
I'd expect this would be easier for larger projects.
> #AI code assistants like [#GitHub#Copilot] are very good at adding code, but they can cause “AI-induced #TechDebt.”
>
> “Fast code-adding is desirable if you’re working in isolation, or on a greenfield problem. But hastily added code is caustic to the teams expected to maintain it afterward.”
>
> In other words, more quantity doesn’t always lead to better #quality.
How much does bad tech practices and loads of tech debt cost you? Or does tech debt have a value? Looks it has a value contrary to some in higher offices thinking it doesn't. Maybe a bit of network isolation could have helped too.
"The infographic we’re releasing today shows the raw numbers of how cloud and geographic factors impact API performance and shows the cost of living with poor-quality APIs." -- #DavidONeill
Monday morning, the peak time for requests and issues. One of the things I try to avoid on #Linux servers is using external repositories for installing specific package versions. Just a while ago, a developer asked me to install the php module for #PostgreSQL on an (old) #Ubuntu server with an external php repository. Even though the server is being decommissioned, this is a temporary operation for migration. Unfortunately, I had to tell them that the packages are no longer available because that repository no longer provides them. Tech debt always comes knocking sooner or later.
I wish I could go into detail about how f**ked up finance and payment providers are but that's covered with NDAs...
Granted most of it is just absurd #TechDebt and shitty tacked-on solutions like #3Dsecure and #PSD2 that never solved the core issues whilst bricking enough stuff that a complete redesign would've been more useful and economically...
@davew the @nodebb team discussed this just today when planning out our roadmap. One #techdebt item was renaming some bespoke html attributes to standards compliant "data-x" attributes. We pushed it back because even though custom attributes (sans data prefix) breaks html validation, there's no way it will ever be purposefully broken.
With Google at the helm they really DO have the power to decide one day that backwards compatibility doesn't matter, and that could irreversibly harm the web.