13 ms·
The Human Cost of Tech Debt
- flukus 10y agoStuff like this is why I wish you could review the companies code before joining. Getting hired, discovering how bad everything is and then starting the job hunt again is awful for everyone.
- bunderbunder 10y agoYou should insist on a chance to speak to your potential colleagues without anyone listening over your shoulder.
- flukus 10y agoI don't think that would help. A lot of them are oblivious to better ways of doing things so they don't realize the problems. Others are just suffering from stockholm syndrome.
- deleted 10y ago[deleted]
- convolvatron 10y agoand a lot of the are so desperate for a helping hand out of that dank hole that they will put on quite a song and dance. How much interesting work is going on, what an interesting, interested and supportive group it is..
- hashkb 10y agoIf any candidate had done this at a place I was unhappy, I'd have told the truth. Honestly, a lot of candidates are drinking kool-aid by the time they walk in the door.
- katpas 10y agoAt interviews people get asked the classic, what's your biggest weakness question. As well as asking them to describe a typical day I always ask an existing employee what the worst thing about their job is. People often try to give a company approved reply but the underlying tensions with the tech/management/process are very difficult to hide.
- peterbotond 10y ago...then the companies having bad code will make a few good ones for show. Interview is like first date both parties try to impress without mentioning the critical (i could have said important too) parts.
- flukus 10y agoWell you'd want to be reviewing the code you're going to be working on. If they bait and switch like this then they should expect high turnover.
- pc86 10y agoIf you're not interviewing with anyone on your team directly they may not have access to whatever you'll be working on. That doesn't make it a bait and switch.
- brandall10 10y agoFor most job offers I've gotten I've asked to review the source code post-offer. I've even done this in a couple interviews -- can't recall ever being denied. In one particular instance I came back to review the code for a product that required a level 3 security clearance; the hiring manager happily complied, letting me spend over 2 hours alone studying the code on a workstation in a side office. One reason I passed on that position was due to the code being more spaghetti than I would have preferred.
- 20andup 10y agoI like your idea. I would also like to add one I learnt through experience. I usually meet with the team on a casual event outside the office before accepting any offer. I find that its a very good way to find out about the team dynamics. A lot of warning signs about management can be easily spotted within half an hour of talking to them. A big warning sign is usually high turnover.
- iamcreasy 10y agoThat's an excellent idea. How to ask about it cordially?
- pc86 10y ago"I'd love to see some of your code while I'm here."
- brandall10 10y agoInside of an interview, what usually happens is we get into a discussion of the architecture of the product I'd be working on. Then I pepper questions about the codebase itself, and after a few questions I'll say "Wow, that sounds interesting. Mind if I take a look?" Post interview I'll talk to the hiring manager and express how much I enjoyed meeting with the team and love the product, then ask if it would be alright to stop by to take a closer look at the codebase, watch how the team works in action, just be a fly on the wall.
- collyw 10y agoI would love to do that as well. But its taken me a while to understand our current system, and the code itself isn't bad, its just some really poor high level design decisions that have led to a lot more of it than is needed. 2 hours in it still looked decent to me.
- ThrowMeAway314 10y agoI recently became CTO of a company with two moderately successful SaaS products. The second one is a fork of the first, but has been maintained by more competent people than the original product. Both are still monuments to technical debt. About 4 million lines of PHP code, written by underpaid, sometimes not well meaning, freelancers and students over the span of 8 years. The CEO wrote a large part, but stopped learning new techniques around 2004. I'm bringing competent and well paid people in through my network and try my very best to give them as much freedom as possible, I allow and encourage greenfield modules/services that run on separate and new infrastructure for anything that is possible to be rewritten in the timeframes, but the larger part of the job is still mind numbing to my team and that makes me question my wisdom. If anyone has tips on how to steer such a ship in a direction where the work is less frustrating for my devs I'm very open for advice.
- jestar_jokin 10y agoCheck out the book "Working Effectively with Legacy Code", by Michael Feathers[0]. I believe the basic approach is to write tests to capture the current behaviour at the system boundaries - for a web application, this might take the form of automated end-to-end tests (Selenium WebDriver) - then, progressively refactor and unit test components and code paths. By the end of the process, you'll end up with a comprehensive regression suite, giving developers the confidence to make changes with impunity - whether that's refactoring to eliminate more technical debt and speed up development, or adding features to fulfill business needs. This way, you can take a gradual, iterative approach to cleaning up the system, which should boost morale (a little bit of progress made every iteration), and minimises risk (you're not replacing an entire system at once). I've used this approach to rewrite a Node.js API that was tightly coupled to MongoDB, and migrated it to PostgreSQL. [0] https://www.amazon.com/Working-Effectively-Legacy-Michael-Feathers/dp/0131177052 https://www.amazon.com/Working-Effectively-Legacy-Michael-Fe...
- adam77 10y agohave the team come up with a list of achievable meaningful milestones (eg. 'eliminate use of nasty obsolete library X'), ensure some time is spared to progress them; it'll become clear if the team is net paying off or accruing also, find someone who thrives on eliminating crap and let them get stuck in
- deleted 10y ago[deleted]
- sigsergv 10y agoThe human cost of unpaid tech debt.
- sigsergv 10y agoMost articles about technical debt should actually be about technical default. Tech debt is a good technical management instrument, it's just need to be paid and everyone involved must understand that. Delaying payments is as bad as delaying regular finance debt payments.
- techterrier 10y agoCompletely agree with this sentiment. Not all tech debt is bad - and it's often inevitable. I wrote some stuff about this notion: https://medium.com/@MostlyHarmlessD/on-technical-debt-7bac65edf349 https://medium.com/@MostlyHarmlessD/on-technical-debt-7bac65...
- coderot 10y agoThis article hits close to home! What should be done in a company that's basically committed every error you could commit? What's an engineer to do? Just switch jobs? I joined a company a few years ago that had hit a wall with its tech stack after 8 years. They brought in a new technical lead who convinced everyone to approve a "rewrite everything from scratch on new stack" approach (even though it rarely works). 2 Years and $40-50m later: - The thing's nowhere near done. Customers all still using old legacy product that's not been updated in 2-3 years now since resources were diverted to rewrite - 88% of the eng org has turned over - current eng org doesn't know how 20-40% of the codebase works - customers have caught on and started leaving en masse - Rest of company has turned over as well as they realized nothing useful was going to come out of engineering for years more if ever It's a bit confusing. What the heck should we do at this point? I take some solace in knowing that I've seen firsthand what NOT to do in situations like this.
- flukus 10y ago> What should be done in a company that's basically committed every error you could commit? What's an engineer to do? Just switch jobs? Sometimes that's all you have the power to do. Why are customers leaving en masse if the old product is still functioning? It sounds like the rewrite got stuck in the pattern where it has to do 100% of the original and then some. Just like a new product, a rewrite has to hit that MVP mark, just not as urgently. They also have to be able to throw out the cruft and not import every bad idea from v1.
- MichaelGG 10y agoMaybe competitors are providing a better product, so customers leave? It's hard to make a new version of a product that does less. Features were presumably mostly added for a reason, and customers probably use them. Removing them is a hard sell.
- flukus 10y agoIf there are better alternatives then sticking with the current technical debt may be a non-option as well. >Features were presumably mostly added for a reason, and customers probably use them. Removing them is a hard sell. Trying to make everyone happy is one of the big drivers of technical debt, a lot of stuff that gets added just to get that one critical contract. Sometimes you can refactor to better handle these variations that weren't anticipated, but sometimes you can't and you have to evaluate the complications versus that one customers business. You say this most often in businesses that practice sales team driven development.
- simula67 10y agoI wonder if it is also the case that if the code quality is high, people are happy and they stay. This means fewer openings are available in those teams. Therefore, if you take a new job, it is more probable that the code is bad and there is a revolving door of developers who have tried to make it better, failed, left and created an opening for you. The vicious cycle of bad jobs.
- Fuxy 10y agoAs I currently work at a company in this exact situation I can confirm it is very true. And to validate the article even more I am currently searching for better opportunities where I can work with better and more modern technologies.
- pc86 10y agoThere's a big difference between "better and more modern technologies" and a fragile, brittle code-base that is difficult to change. They are not necessarily related to each other, either.
- Fuxy 10y agoNot if it's written PHP and went through the hand of multiple developers in its early days when standards were less well defined. Coding in PHP has become a lot better over they years but if you have the misfortune of having to maintain legacy code it' s pretty much guaranteed to be a bad time. No MVC, no templates, no PDO hell it's one step removed from the early days when everything was in 1 big file and nobody seems to be bothered by it or willing to budget time to rewrite it and eliminate the technical debt incurred every time you need to modify it.
- whack 10y agoHonestly, I would get bored working at a place where everything is "easy". I actually enjoy the challenge of working on awful code-bases, and trying to improve upon it, while still preserving the functionality and not breaking anything. That said, if I had to work with awful code and I wasn't allowed to touch it or make it better, I would definitely leave in a heartbeat.
- boothead 10y agoThis is a great article. I've also seen tech debt exacerbated by poorly implemented agile practices. One of the worst projects I worked on kept kicking the can down the road because of a misguided idea that everything should be a customer deliverable. So not only were we forced to work with crap, but we were disempowered from making it any better! It was a nightmare, motivation and team cohesion was non-existent and yes, turnover was very high!
- clifanatic 10y ago> everything should be a customer deliverable And everything should be delivered in a 100% predictable timeframe and that predictable timeframe should be about a day.
- gearhart 10y ago> To tie this back to the tech debt metaphor, think of someone with mountains of debt trying to explain being harassed by creditors. It’s embarrassing, which is, in turn, demoralizing. Seems that a more apt use of the analogy would be "think of someone with mountains of debt trying to explain why they can't afford to do the same things as their colleagues"
- jcbeard 10y agoBad management, oversight, and architecting returns bad code. Often team leads know better, but are driven by deadlines and the lack of a skilled workforce (with little time to train them) to produce a product. Of course this leads to turn-over...eventually. People will work for a year, realize that nothing they want to accomplish will happen quickly because of resourcing, then they'll run away. I really don't agree that the human cost of technical debt is a new concept. It's foremost in my mind when I think about giving tools to employees to add new features. Well written article, but not really anything new.
- ddebernardy 10y ago> For a manager, a code base high in technical debt means that feature delivery slows to a crawl, which creates a lot of frustration and awkward moments in conversation about business capability. For a developer, this frustration is even more acute. Nobody likes working with a significant handicap and being unproductive day after day, and that is exactly what this sort of codebase means for developers. The very same holds for managers and teams in companies that need to deal with organizational debt: https://steveblank.com/2015/05/19/organizational-debt-is-like-technical-debt-but-worse/ https://steveblank.com/2015/05/19/organizational-debt-is-lik...
- blunte 10y ago"They know that they’re going to have to manufacture endless explanations for why seemingly simple things take them a long time." This is what kills me. You can't say to the boss, "Your beloved senior dev built this arcane and fragile system, so everything I do takes forever." Instead you have to find diplomatic/meaningless explanations for why you're moving so slowly.
- quantumhobbit 10y agoI've found that I can win over my immediate superiors with low level grumbling about real technical issues in the code base. They eventually internalize the state of the code base and have realistic expectations for how long things will take. The key is to diplomatically voice all your WTF moments, and have a boss technical enough to get it. Problem is their bosses still think that the spaghettified joke that is the internal framework we have to use is manna from heaven and would take a very dim view of anyone caught trashing it in the open.
- michaelfeathers 10y agoI'm convinced that the issue overall is lack of transparency about design quality. In an org with non-technical leadership, technical staff should periodically present assessments of their systems' readiness for change. Non-tech people need to understand technical debt and see how it changes over time. In my experience, companies with technical founders tend to have cultures that handle this issue better.
- richmarr 10y ago> ...lack of transparency about design quality Totally agree. Technical debt isn't a problem as long as the team has good communication & low levels of political behaviour. IMO articles like this that paint Tech Debt as a universally negative thing (without trying to balance the view, or mention the context in which the tech exists) do more harm than good. Update: Recommend reading "5 Dysfunctions of a Team" for guidance on improving communication and reducing political behaviour in an organisation.
- 10y ago
- FollowSteph3 10y agoThe concept of technical debt is easy to convey to management, the hard part is conveying the scale of the debt because it's an abstract value. You don't have x units of debt. And because there's no actual value to measure it's easy to keep adding it on, it's easily viewed as the same debt. To give you an analogy imagine you have a credit card. As you spend you increase your debt but you never get to know want your balance is. All you know is how much you pay per month. In fact even that number would be blurry and fluctuate. That's what management sees from their perspective. As a result it's easy to keep adding debt because it had no real value, you don't see that you're $1000, $10k, $100k, etc in debt, just that you have to pay something each month. Yes each month you have less to spend but it's a lot less than you spent that month. Last month you had to pay $100 but this month it's $101 and you don't have to pay that $50 one Ike hit. The extra $1mth is easier. You kinda forget that in a year it's now an extra $2-$3/mth. And again you never see your balance, so you don't know how much you have in debt. Your spouse keeps saying your way in debt but you have no idea of the scale. It's very easy to increase your debt this way. Unfortunately I don't have an answer as to how you can value the technical debt so that the business people can appreciate the scale. I don't think as developers we can even measure it ourselves accurately, it's more of a feeling, a scale if you will.
- caente 10y agoCopying my comment from the OP > Analysts and project managers might account for technical debt when discussing slipped deadlines. No they won't, you cannot quantify technical debt, it's a metaphor. I completely agree with the rest of the post. But "technical debt" is not a cause, nor a valid metaphor to share with management. Other bad metaphors are "building" and "architecture". We are not building anything, we are only writing algorithms that computers will follow. When we write down those algorithms, we are also encoding the inner workings of the company. The true knowledge of how a company works is not only in its documentation or in the heads of their employees, it's also in its automated processes. The automated processes are the reason why a company can be competitive nowadays. People need to be able to understand those processes, those algorithms, from the code, documentation is never enough, and is never up to date. The code is the primary source of information. If it's not legible, if it becomes arcane knowledge, a black magic that only a consultant can "fix", then the company grinds to a halt, it withers and is crushed by competitors. Be careless about the code quality is not about the suffering of the developers, it means that you are burying vital knowledge of your company, and eventually no employee, no consultant, will be able to dig it out. If we are trying to figure out how to deal with managers who don't care about the company, but only about absurd deadlines that their managers gave them, then we need to start pushing back, start saying NO. Politics are unavoidable, and often necessary, not all decisions can be made because technical reasons, but we need to start imposing the reality of the code, you cannot rush it, our you are killing yourself.
- clifanatic 10y agoAs much as I love the metaphor, it's been quite a while since I first noticed the "eye-twitching" among non-technical management types whenever the term "technical debt" comes up. I can almost hear them thinking, "oh, boy, more spoiled programmer bullshit for me to deal with".
- ubercode5 10y ago"If you’re not already familiar with the concept of technical debt" ohh how I envy thee.