Friday DevOps Fun
Technical Debt...
#devops #meme #fun #humor #fridaydevopsfun #fridayhumor #technicaldebt
Friday DevOps Fun
Technical Debt...
#devops #meme #fun #humor #fridaydevopsfun #fridayhumor #technicaldebt
You probably heard of #TechnicalDebt, but what about #TechnicalCredit? This article introduces the concept and gives some examples how software architects can prepare for likely future changes: https://cacm.acm.org/opinion/technical-credit/
(Thank you @paigerduty for sharing this.)
How WebAssembly Crushes Technical Debt, by (unattributable):
The Perils of 'Vibe Coding': A Call for Code Comprehension
In the age of AI-assisted programming, a new trend called 'Vibe Coding' threatens the integrity of software development. This practice encourages developers to rely on AI-generated code without unders...
https://news.lavx.hu/article/the-perils-of-vibe-coding-a-call-for-code-comprehension
@ajn142 @mttaggart For sure. But having seen our GPOs, I don't want my fingerprints anywhere near that unless it's applying to everyone at this point.
@SeanCasten @koen_hufkens
Nope, those #MAGA #DOGE #Mump believers aren't saving money. They're creating #TechnicalDebt (and/or Organisational Debt) that will have to be paid in the future. By deaths, by illnesses, by bank or stock crashes, whatever.
Some IT people work in an environment of fear. They’re afraid to do routine system maintenance that might take the system down for awhile.
The crazy thing is, scheduled maintenance downtime will be less impactful than unscheduled emergency downtime.
The solutions are to have upper management fully supportive of system maintenance, and a smoothly functioning change management process that includes mechanisms for incorporating patches and updates into the workflow.
If you WORK FOR a company with a culture of fear surrounding routine system maintenance downtime, do yourself a favor and look for a new job.
If you OWN OR MANAGE a company with a culture of fear surrounding routine system maintenance downtime, do yourself a favor and call me. I can turn it around.
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!
#SoftwareDevelopment#Programming #TechnicalDebt #Coding: "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?
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.
(...)
Technical debt is the number one cause of developer frustration. Working with imperfect systems demoralizes programmers, making it difficult to do quality work.
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."
https://shiftmag.dev/unhappy-developers-stack-overflow-survey-3896/
I just deleted 1,372 disks from Google cloud and 7 project spaces.
(Yes, this was intentional. It's a lifecycle script I wrote to clean up things that are beyond SLA.)
Next time someone tells you that piece of code is only temporary, remind them that the Eiffel Tower was built as a construction experiment in 1889. #TechnicalDebt
#DX #DeveloperExperience #SoftwareDevelopment #TechnicalDebt: "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.""
https://www.atlassian.com/blog/developer/developer-experience-report-2024
Doing some pro bono work for an NGO that lost its funding for their IT / #TechSupport / #SysAdmin person some years ago. Things are a mess, and getting worse, so I explained that they're experiencing Technical Debt.
One of the workers, a bit overwhelmed with all the extra IT work they have to do themselves, misheard and said "Oh yes, I'm definitely experiencing Technical Death!"
I think that's what I'm calling it from now on.
#Culture #AI #BigTech #TechnicalDebt #Hacking #CyberSecurity: "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.
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?"
When new junior #developers are hired to maintain my 10 years of #technicaldebt, and they’re like: “what is this shit?” and I’m like:
One of the more subtle factors in the creation of technical debt is lack of professional growth. For example, a Network Administrator doesn’t continuously learn, has no mentor, and resists new technology and systems out of fear of the unknown. A lack of self-confidence. They stick with what they know, and the network doesn’t advance. In the larger analysis, this isn’t JUST the Net Admin’s fault – it’s also the CIOs fault, for not building growth opportunities into the Net Admin’s career path. The company’s network doesn’t grow and develop because the people in charge don’t grow and develop.
Never stop growing and learning. Don’t wait for others to give you opportunities to learn. Take charge of your personal development.
I'm so grateful for the room full of folks looking to deal with their #TechnicalDebt this morning at #phptek, thank you!
My slides are available at https://stevegrunwell.com/slides/technical-debt, and the README for the slides include links to all sorts of resources (including the Adapter Pattern blog post I mentioned: https://stevegrunwell.com/blog/adapter-pattern)
Developer tells me the new table they just created is 'temporary' and will only be around for a week or two.
I should also receive the ownership deed to the Brooklyn Bridge any moment now...