dtanzer<p>Technical debt - Just crappy code or a conscious decision?</p><p>In my opinion, we should not call every code that is bad "technical debt" (And, AFAICR, <span class="h-card" translate="no"><a href="https://mastodon.social/@GeePawHill" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>GeePawHill</span></a></span> recently wrote we should retire the term completely) Unfortunately, most people use the it like that...</p><p>See more here: <a href="https://videos.devteams.at/w/rgmPEaa82vRWWpcs2bS51N" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">videos.devteams.at/w/rgmPEaa82</span><span class="invisible">vRWWpcs2bS51N</span></a><br><a href="https://social.devteams.at/tags/software" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>software</span></a> <a href="https://social.devteams.at/tags/design" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>design</span></a> <a href="https://social.devteams.at/tags/bonsai" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bonsai</span></a> <a href="https://social.devteams.at/tags/technicalDebt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>technicalDebt</span></a> </p><p>Or, if you prefer watching videos on youtube: <a href="https://youtu.be/OyCgOjLN1nE" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">youtu.be/OyCgOjLN1nE</span><span class="invisible"></span></a></p>
eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.
Administered by:
Server stats:
216active users
eupolicy.social: About · Profiles directory · Privacy policy
Mastodon: About · Get the app · Keyboard shortcuts · View source code · v4.4.1
#technicaldebt
0 posts · 0 participants · 0 posts today
Jennifer Moore 😷real-life effects of LLMs in tech workplaces
Boris Vulikh<p>A term to remember:<br>Cognitive debt, a condition in which repeated reliance on external systems like LLMs replaces the effortful cognitive processes required for independent thinking.</p><p>We shouldn't worry only of the technical debt, but also cognitive debt when over-relying on the LLMs.<br><a href="https://fosstodon.org/tags/technicaldebt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>technicaldebt</span></a> <br><a href="https://fosstodon.org/tags/cognitivedebt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cognitivedebt</span></a></p>
.:\dGh/:.<p><a href="https://mastodon.social/tags/JAVA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JAVA</span></a> <a href="https://mastodon.social/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Programming</span></a> <a href="https://mastodon.social/tags/Shit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Shit</span></a> <a href="https://mastodon.social/tags/Piss" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Piss</span></a> <a href="https://mastodon.social/tags/Coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Coding</span></a> <a href="https://mastodon.social/tags/Code" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Code</span></a> <a href="https://mastodon.social/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoftwareDevelopment</span></a> <a href="https://mastodon.social/tags/ShitDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ShitDevelopment</span></a> <a href="https://mastodon.social/tags/VibeCoding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VibeCoding</span></a> <a href="https://mastodon.social/tags/VibeCode" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VibeCode</span></a> <a href="https://mastodon.social/tags/Scala" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Scala</span></a> <a href="https://mastodon.social/tags/FuckThisShit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FuckThisShit</span></a> <a href="https://mastodon.social/tags/TechnicalDebt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechnicalDebt</span></a></p>
Doc Edward Morbius ⭕<p>When I hear about AI-based programming, I think back several decades to a time when I was dealing with a hairy set of data, and I wrote a pretty complex bit of code generating an even more complex bit of SQL. I don't remember now if it ended up proving useful or not, though I think it did. But that's not the point.</p><p>The point was when I came back to it after a few months ... I couldn't figure it out at all. Neither the generator, nor the generated code.</p><p>And <strong>I HAD WRITTEN IT</strong>. Myself, from scratch, sorting out what I wanted and how to get there.</p><p>There's a principle in programming that debugging and maintenance are far harder than coding. Which means you should never write code that <em>you</em> are <em>too stupid to debug and maintain</em>. Which is precisely what I'd failed in my anecdote.</p><p>And of course, Management, in its infinite wisdom, typically puts far greater emphasis on new development than on testing, or Heavens Forefend!!! <em>maintenance</em>. So all the brightest talent (or so perceived, at any rate) goes to New Development.</p><p>(There's a great essay from about a decade ago, "In Praise of Maintenance, which you, and by "you" I mean "I", should really (re)read: <a href="http://freakonomics.com/podcast/in-praise-of-maintenance-rebroadcast/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">http://</span><span class="ellipsis">freakonomics.com/podcast/in-pr</span><span class="invisible">aise-of-maintenance-rebroadcast/</span></a>).</p><p>With AI-based code generation, presuming it works at all, we get code that's like computer-chess or computer-Go (the game, not the lang). It <em>might</em> work, but <em>there's no explanation or clarity to it</em>. Grandmasters are not only stumped but utterly dispirited <em>because they can't grok the strategy</em>. </p><p>I can't count the number of times I've heard AI referred to as search or solution without explanation, an idea I'd first twigged to in the late 2010s. That is, if <em>scientific</em> knowledge tells us about <em>causes</em> of things, AI ML GD LLM simply <em>tells us the answer</em> without being able to show its work. Or worse: even if it <em>could</em> show work, that wouldn't tell us anything meaningful.</p><p>(This ... may not be entirely accurate, I'm not working in the field. But the point's been iterated enough times from enough different people at least some of whom <em>should</em> know that I tend to believe it.)</p><p>A major cause of technical debt is loss of institutional knowledge over how code works and what parts do what. I've worked enough maintenance jobs that I've seen this in all size and manner of organisations. At another gig, I'd cut the amount of code roughly in half <em>just so I could run it in the interactive environment which made debugging more viable</em>. I never really fully understood what all of that program did (though I could fix bugs, make changes, and even anticipate some problems which later emerged). Funny thing was when one of the prior Hired Guns who'd worked on the same project before my time there turned up on my front door some years later ... big laughs from both of us...</p><p>But this AI-generated code? It's going to be hairballs on hairballs on hairballs. And at some point it's gonna break.</p><p>Which leaves us with two possible situations:</p><ul><li>We won't have an AI smart enough to deal with the mess.</li><li>Or, maybe, we will. Which as I think of the possibility whilst typing this seems potentially even more frightening.</li></ul><p>Though my bet's on the first case.</p><p><a href="https://toot.cat/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a> <a href="https://toot.cat/tags/AiProgramming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AiProgramming</span></a> <a href="https://toot.cat/tags/Hairballs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Hairballs</span></a> <a href="https://toot.cat/tags/WarStories" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WarStories</span></a> <a href="https://toot.cat/tags/Maintenance" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Maintenance</span></a> <a href="https://toot.cat/tags/TechnicalDebt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechnicalDebt</span></a></p>
M@<p>🚀 NEW: February 2025 Engineering Leadership Reading List!</p><p>Key themes: AI's role in engineering management, companies streamlining management layers, and younger workers avoiding middle management roles. Plus: a fresh look at technical debt - is bad code more like an unhedged call option than debt?</p><p>Read more: <a href="https://quantumfaxmachine.com/blog/qfm055-engineering-leadership-reading-list-february-2025" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">quantumfaxmachine.com/blog/qfm</span><span class="invisible">055-engineering-leadership-reading-list-february-2025</span></a></p><p><a href="https://masto.ai/tags/EngineeringLeadership" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EngineeringLeadership</span></a> <a href="https://masto.ai/tags/TechManagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechManagement</span></a> <a href="https://masto.ai/tags/TechnicalDebt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechnicalDebt</span></a></p>
Jörg Seidel<p>Sieht so aus als wäre die <a href="https://det.social/tags/Friedensdividende" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Friedensdividende</span></a> in Wirklichkeit <a href="https://det.social/tags/TechnicalDebt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechnicalDebt</span></a> gewesen.</p><p><a href="https://det.social/tags/schuldenbremse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>schuldenbremse</span></a> <a href="https://det.social/tags/ukraine" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ukraine</span></a> <a href="https://det.social/tags/russland" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>russland</span></a> <a href="https://det.social/tags/usa" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>usa</span></a></p>
Thomas Fricke (he/him)<p>Utility says its equipment may have started a small blaze that erupted during January’s LA<br> firestormhttps://apnews.com/article/california-wildfires-socal-edison-hurst-fire-cause-1204b0bd207a01aa41dc617d6edc0ff2</p><p>If you don't remove <a href="https://23.social/tags/technicaldebt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>technicaldebt</span></a> it will kill you. This is the <a href="https://23.social/tags/ot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ot</span></a> version of the <a href="https://23.social/tags/California" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>California</span></a> <a href="https://23.social/tags/Wildfire" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Wildfire</span></a> s</p>
Miguel Afonso Caetano<p>Although the survey didn't ask what kind of technical debt the respondents had to deal with in their jobs, I bet that one of the main causes of this technical debt is a lack of documentation. In other words, companies need to hire more technical writers and value the ones they do hire as experts in their field :) Furthermore, no kind of AI will be able to solve this lack of documentation. Why? Because documentation is made to be read and understood by humans. That's why! </p><p><a href="https://tldr.nettime.org/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoftwareDevelopment</span></a>#Programming <a href="https://tldr.nettime.org/tags/TechnicalDebt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechnicalDebt</span></a> <a href="https://tldr.nettime.org/tags/Coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Coding</span></a>: "According to the Workplace Satisfaction Survey, 80% of professional programmers are unhappy. One in three respondents actively hates their job, while almost half survive in survival mode. This leaves only 20% of those who claim to be somewhat happy. Although programmers are well-paid and often able to work remotely, many are still dissatisfied. Why is that so?</p><p>While developers are generally well paid, this year’s survey showed that software engineers’ salaries are decreasing. As an example, the median salary for PHP developers is relatively low, at $49,000 per year. This is a decrease compared to previous years, and only those who combine programming skills with entrepreneurship achieve significant financial success. <br>(...)<br>Technical debt is the number one cause of developer frustration. Working with imperfect systems demoralizes programmers, making it difficult to do quality work.</p><p>The pressure to meet deadlines is often extreme in the IT industry. Developers are under pressure to complete tasks as fast as possible in order to earn as much income as possible. Increased pressure in the workplace leads to unrealistic expectations and burnout. Changing jobs often can provide temporary relief by increasing income, but they end up in similar stressful situations and in new companies."</p><p><a href="https://shiftmag.dev/unhappy-developers-stack-overflow-survey-3896/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">shiftmag.dev/unhappy-developer</span><span class="invisible">s-stack-overflow-survey-3896/</span></a></p>
Scott Williams 🐧<p>I just deleted 1,372 disks from Google cloud and 7 project spaces.</p><p>(Yes, this was intentional. It's a lifecycle script I wrote to clean up things that are beyond SLA.)</p><p><a href="https://mastodon.online/tags/DevOps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DevOps</span></a> <a href="https://mastodon.online/tags/GoogleCloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GoogleCloud</span></a> <a href="https://mastodon.online/tags/TechnicalDebt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechnicalDebt</span></a></p>
InfoQ<p>Identifying <a href="https://techhub.social/tags/TechnicalDebt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechnicalDebt</span></a> is crucial for understanding how today’s decisions can shape tomorrow's challenges.</p><p>In this <a href="https://techhub.social/tags/InfoQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>InfoQ</span></a> <a href="https://techhub.social/tags/podcast" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>podcast</span></a>, Shane Hastie chats with Dustin Thostenson about practical techniques for recognizing and addressing technical debt.</p><p>🎧 Listen now: <a href="https://bit.ly/3zJ3rpG" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">bit.ly/3zJ3rpG</span><span class="invisible"></span></a> </p><p><a href="https://techhub.social/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoftwareDevelopment</span></a> <a href="https://techhub.social/tags/DeveloperExperience" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DeveloperExperience</span></a> <a href="https://techhub.social/tags/Teamwork" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Teamwork</span></a> <a href="https://techhub.social/tags/Culture" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Culture</span></a> <a href="https://techhub.social/tags/Agile" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Agile</span></a></p>
InfoQ<p><a href="https://techhub.social/tags/TechnicalDebt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechnicalDebt</span></a> is often used as a metaphor for communicating the long-term implications of architectural decisions & trade-offs to stakeholders.</p><p>But is it always accurate? The Technical Debt metaphor is misleading because much of the so-called debt never needs to be, and in fact isn’t, repaid.</p><p>For a deeper dive into this perspective, check out the <a href="https://techhub.social/tags/InfoQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>InfoQ</span></a> article by Pierre Pureur & Kurt Bittner. </p><p>Read now: <a href="https://bit.ly/3ZpFP44" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">bit.ly/3ZpFP44</span><span class="invisible"></span></a> </p><p><a href="https://techhub.social/tags/SoftwareArchitecture" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoftwareArchitecture</span></a> <a href="https://techhub.social/tags/Agile" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Agile</span></a> <a href="https://techhub.social/tags/MVA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MVA</span></a> <a href="https://techhub.social/tags/MinimumViableArchitecture" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MinimumViableArchitecture</span></a></p>
InfoQ<p>🤔 How did <a href="https://techhub.social/tags/Meta" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Meta</span></a> develop & launch the <a href="https://techhub.social/tags/ThreadsApp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ThreadsApp</span></a> in just 5 months?</p><p>Spoiler: They reused key parts of Instagram! Discover the inside story in this <a href="https://techhub.social/tags/CaseStudy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CaseStudy</span></a>!</p><p><a href="https://techhub.social/tags/InfoQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>InfoQ</span></a> article by Zahan Malkani: <a href="https://bit.ly/3MbQDLa" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">bit.ly/3MbQDLa</span><span class="invisible"></span></a> </p><p><a href="https://techhub.social/tags/SoftwareArchitecture" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoftwareArchitecture</span></a> <a href="https://techhub.social/tags/Threads" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Threads</span></a> <a href="https://techhub.social/tags/TechnicalDebt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechnicalDebt</span></a> <a href="https://techhub.social/tags/reusecode" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>reusecode</span></a> <a href="https://techhub.social/tags/SoftwareCraftsmanship" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoftwareCraftsmanship</span></a> <a href="https://techhub.social/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoftwareDevelopment</span></a> <a href="https://techhub.social/tags/Agile" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Agile</span></a></p>
Miguel Afonso Caetano<p><a href="https://tldr.nettime.org/tags/DX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DX</span></a> <a href="https://tldr.nettime.org/tags/DeveloperExperience" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DeveloperExperience</span></a> <a href="https://tldr.nettime.org/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoftwareDevelopment</span></a> <a href="https://tldr.nettime.org/tags/TechnicalDebt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechnicalDebt</span></a>: "Most developers attribute their time loss to tech debt or insufficient documentation, while leaders point to under-staffing, the expansion of the developer role, and the amount of tech knowledge needed. Not only does this create frustration among developers, but it also means leaders are likely to fix the wrong issue. The consequences are a larger gap in the issue and potentially wasted resources.""</p><p><a href="https://www.atlassian.com/blog/developer/developer-experience-report-2024" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">atlassian.com/blog/developer/d</span><span class="invisible">eveloper-experience-report-2024</span></a></p>
Miguel Afonso Caetano<p><a href="https://tldr.nettime.org/tags/Culture" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Culture</span></a> <a href="https://tldr.nettime.org/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a> <a href="https://tldr.nettime.org/tags/BigTech" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BigTech</span></a> <a href="https://tldr.nettime.org/tags/TechnicalDebt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechnicalDebt</span></a> <a href="https://tldr.nettime.org/tags/Hacking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Hacking</span></a> <a href="https://tldr.nettime.org/tags/CyberSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CyberSecurity</span></a>: "Culture is increasingly divorced from national identity in our globalized, fragmented world. On the positive side, this decoupling can make culture more inclusive of marginalized people. Other groups, however, may perceive this new status quo as a threat, especially those facing a loss of privilege. The rise of white Christian nationalism shows that the right still regards national identity and culture as crucial—as potent tools in the struggle to build political power, often through anti-democratic means. This phenomenon shows that the separation of cultural identity from national identity doesn’t negate the latter. Instead, it creates new political realities and new orders of power.</p><p>Nations issuing passports still behave as though they are the definitive arbiters of identity. But culture today—particularly the multiverse of internet cultures—exposes how this is increasingly untrue. With government discredited as an ultimate authority, and identity less and less connected to nationality, we can find a measure of hope for navigating the current transition in the fact that culture is never static. New forms of resistance are always emerging. But we must ask ourselves: Have the tech industry’s overwhelming surveillance powers rendered subversion impossible? Or does its scramble to gather all the world’s data offer new possibilities to hack the system?"</p><p><a href="https://www.schneier.com/blog/archives/2024/06/the-hacking-of-culture-and-the-creation-of-socio-technical-debt.html" rel="nofollow noopener" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">schneier.com/blog/archives/202</span><span class="invisible">4/06/the-hacking-of-culture-and-the-creation-of-socio-technical-debt.html</span></a></p>
Richard Griffiths<p>Ignoring existing technical debt while transitioning to <a href="https://mastodon.ie/tags/Agile" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Agile</span></a> can severely impact project velocity and team morale. Prioritizing and managing technical debt is essential. <a href="https://mastodon.ie/tags/TechnicalDebt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechnicalDebt</span></a></p>
Dirk-Jan Swagerman<p>My talk "How (not) to sell technical debt" is online!</p><p><a href="https://www.youtube.com/watch?v=iSj1DY34HJI" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">youtube.com/watch?v=iSj1DY34HJ</span><span class="invisible">I</span></a></p><p>I gave this talk November 8th 2022 online to the dutch system architecting conference of bits & chips</p><p>I talked about ‘software essentials for executives’ to help executives avoid costly mistakes and ‘executive essentials for engineers’ to provide engineers with a few pointers that may help executives make better decisions.</p><p>A boost for reach would be appreciated!</p><p><a href="https://systems.social/tags/LegacySoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LegacySoftware</span></a><br><a href="https://systems.social/tags/TechnicalDebt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechnicalDebt</span></a><br><a href="https://systems.social/tags/SocioTechnical" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SocioTechnical</span></a></p>
TrendingLive feeds
Mastodon is the best way to keep up with what's happening.
Follow anyone across the fediverse and see it all in chronological order. No algorithms, ads, or clickbait in sight.
Create accountLoginDrag & drop to upload