If you think that technical debt is scary, wait until you get to see your sec debt. Don't let the hacker penetrate your doors and locks. Start with continuous threat modeling at copi.owasp.org
How? Read all about it and how to threat model the cloud at: https://dev.to/owasp/no-need-to-fear-the-clouds-play-owasp-cumulus-d6g
Out with the Old: A Spring Cleaning for Your Code
From tech debt to framework fatigue, here’s how to refresh your stack for the cloud-native era.
https://myfear.substack.com/p/out-with-the-old-a-spring-cleaning-for-your-code
#Java #TechDebt #SpringCleaning
Rule of thumb: If someone is building an API that has "smart simplifications" to make it look nice & compact, then they are just creating future tech debt.
From the archives:
“Web Design as a Process” in Charts: Maintenance, Decay, Tech Debt, and Big Bang Launching:
"Show don't tell" of federate #FOSS code & apps doesn't work well in environment where we need "Show don't tell" of #OpenStandard specs to make progress. Especially if the specs are so vague that each code implementation thrown in the cauldron of #ActivityPub #fediverse installed base is known to only add #ProtocolDecay and #TechDebt.
In #Commons #CommonSense makes #CommonsSense: Don't introduce the opposite of #interoperabily when in pursuit of seamless interop.
We need both forms of showing.
"since standard software engineering is a subset of the skills needed in machine learning engineering, more familiar software engineering tech debt is just a subset of the space of possible ML tech debt. "
Matthew McAteer
https://matthewmcateer.me/blog/machine-learning-technical-debt/
I had so much fun chatting with Robby! Some spice in this episode with unpopular opinions on maintainable code. Listen to find out the topic of our next argument 
#MaintainableSoftware #OpenSource #TechDebt
https://maintainable.fm/episodes/julia-ferraioli-capturing-untold-open-source-stories
Line must go down! Maintenance weeks are over![1]
Software maintenance, large scale refactoring, creating/improving documentation, deduplicating code are some the most boring & thankless tasks, but also so essential, especially on projects of the scale of https://thi.ng/umbrella (with almost 4100 source files)
Yesterday was #ReleaseFriday, most prominently featuring new major version & expansion of https://thi.ng/geom (and its 20+ support packages) — I will write about it more in coming days.
Part of this major release cycle also included a repo-wide round of various cleanups, incl. updating & reviewing 425 code snippets in doc strings and preparing them for extraction[2], fixing links in docs, enforcing naming conventions for package internals across all 190+ packages, deduplicating and refactoring internals in dozens of projects, updating examples, building tools to generate diagrams for readmes etc.
These have been some intense few weeks, but I'm super glad it's all done (for now)!
Happy coding! :)
[1] The hours of tech debt auto-calculated in this diagram are a bit pointless (completely OTT and containing alot of false positives), but the graph still nicely shows the effort & progress involved... Btw. the chart is from here:
https://codeclimate.com/github/thi-ng/umbrella
[2] Wherever possible, code examples/snippets in project readme's and docstrings embedded in source code can be extracted into their own source files via https://thi.ng/tangle and then run directly (e.g. via https://bun.sh). You can find more info in this section of the main readme:
Join @PLUG Thursday night to chat about types of tech debt and how to tackle them.
Tech debt is necessary infrastructure with insufficient support.
Tech debt can come due at any time.
Unnecessary infrastructure can suddenly be necessary.
https://gettogether.community/events/55007/east-valley-meeting/
19:00 AZ time ( UTC -7 ) in #BigBlueButton
Tbh I'm not enthusiastic about a #Mastodon #hardfork. Not necessarily because of the #techdebt or even because it's technically inferior to other #ActivityPub implementations (which are both true), but because I cannot be sure if that new fork is going to adopt the same attitude as Mastodon in choking the rest of the #fediverse with its proprietary extensions and #EmbraceExtendExtinguish / #EEE.
I'd rather not have the uncertainty. Either start from scratch like #GoToSocial is doing or help the other two mainstream AP families which are #Misskey and #Pleroma. That's the only way we can ensure no implementation overwhelmingly dominates the fedi. :seija_coffee:
#fediversemeta
RE: https://hachyderm.io/users/jenniferplusplus/statuses/112355187216928083
@dectentoo So true! A team ignoring #techdebt is just another poorly led #featurefactory. An "#agile" feature factory, is still a feature factory.
Such a product will become an unmaintainable monster. We need more education for CEOs & CFOs to see at least the financial drawbacks of such a #productmanagement.
In some companies agile is putting product development at risk. They implement blindly an agile framework, focus on conducting ceremonies and ignore topics like discovery or tech debt.
"The Video Game History Foundation says that about 87% of all commercial games written prior to 2010 are now unavailable. This is a failure of our field. We're in a moment in time when people spend their adult life making one game, and 5 years later it is unplayable because of DRMs, system complexity."
excerpt from https://100r.co/site/computing_and_sustainability.html via @xyhhx
I finally got around to ordering the 32GB of ram for the MSI Phantom, it arrived today and it's installed.
Now it's running at between 30%-40% instead of mostly 80%. It's depressing that everything is so inefficient.
I'd like to imagine I'm not the only one who struggles with the desire to create, share, and upkeep things that I've previously shared. This feels more acute when it's a tool someone else might use.
I've been coming to grips with this "personal tech debt", not sure what else to call it and wrote a post about it [1]. I would love to hear how others deal with this, especially those working on small FOSS projects that are "scratch your own itch".
[1]: https://shom.dev/posts/20240119_tech-debt-for-personal-projects/
I'd like to imagine I'm not the only one who struggles with the desire to create, share, and upkeep things that I've previously shared. This feels more acute when it's a tool someone else might use.
I've been coming to grips with this "personal tech debt", not sure what else to call it and wrote a post about it [1]. I would love to hear how others deal with this, especially those working on small FOSS projects that are "scratch your own itch".
[1]: https://shom.dev/posts/20240119_tech-debt-for-personal-projects/
Mima-sama 
