Technical debt - How to make it with one button
ฝัง
- เผยแพร่เมื่อ 24 มิ.ย. 2024
- Term technical debt is often being used between tech and non-tech people, and both sides seem to have different attitude towards it. I tried to visualize what it is, and what are the consequences if it is forgotten in the system.
Interested in learning real-life PHP design patterns?
➡️ www.ApplicableProgramming.com/
If you are interested in programming courses related to web, please visit www.applicableprogramming.com/ to view courses where we show the problem, then we try to solve it the hard way, and then we show how we can benefit from proven solutions.
➤ LINKS
➡️ Private "Applicable Programmers" facebook group / applicableprogrammers
➡️ Discord server / discord
➡️ Other tutorials: www.ApplicableProgramming.com
Timestamps:
What is technical debt (00:00)
How to control technical debt (07:39)
Great video 👍
Thank you Rieltork. Do you make technical debt on purpose? :)
Why I do I feel that our team is dealing with this right now? Lol .. and why are we using Yii2 🤔
Hehe, yeah, story of our life... In my previous job, the CTO actually took tech debt quite seriously and actually worked with it regularly, which is the first time i've seen someone do it on a "larger scale"
I was watching this with a big smirk on my face. Not only a problem in IT you know... Lately my bosses have implemented procedures and guidelines to "quote unquote" solve some overdue problems. Quick and dirty and without proper knowledge so it barely works. So they add more rules and projects and implementations to solve the new problems, which bring new problems and so on. Long story short: I'm drowning in paperwork and nothin gets done.
I think I'll sneak this video in in a meeting. They won't understand the IT part, but they'll get the gist
Guess why I made this video :) I had to explain this over and over and over to people in different positions and different roles.
I even tried to keep technical part to a minimum so that the video is more universal, and considered some non technical example like a car, but.. I think that people regardless of their role should have at least a minimum of tech understanding and be able to follow the presentation.
Do you have any idea what you can do at this stage to mitigate the problem?
@@ApplicableProgramming Sure... About a week ago I just stopped doing all these extras and went back to square one. Sometimes a little anarchy doesn't hurt.
When trying to explain this to people I think the main problem is not that people don't understand technical debt but that they don't really listen, as it's about some (vague) problems and (possible) consequences in the future that will affect... someone.
It doesn't feel like "your" problem. Sure, the developer might know what awaits him but a Sales Manager will brush it off as a problem for the IT department. Unless you can make it personal and ask how he will keep up the sales next year and deal with angry customers. Maybe his bonus will go down. Maybe HR is using the software as well and it'll become personal if they won't be able to use feature X anymore because of patch A and B to correct C and D. Are they prepared to do overwork so people can get their paycheck on time? Is the company prepared to spend that extra money for overwork? And on extra's to keep clients happy? And on the dozens of patches?
I found out it helps if you can make people understand that it's not just someone else's problem. If they are personally involved they start to listen and are much more open to debate in finding proper solutions. Not saying it's guaranteed, but it's a good start.
Hence the anarchy part. I need to get their attention first.