23 ms·
Can't be fucked: Underrated cause of tech debt
- lnxg33k1 3y agoI tend to consider bullshit any point that finds somehow acceptable thinking that people is lazy, in this society, in this world, on this planet, ffs we have to work 40 hrs per week per decades and rest after reincarnation, and you want to talk about laziness? Let's talk about how any bit of mental energy is extracted to built other's wealth and then when you are too old to do nothing other than watching work in progress they just spit you out when I am supposed to fix tech debt? if every week there is another functionality going out that needs to be done yesterday? Do you think that I have to do it in my free time? Why should I even bother existing
- qup 3y agoBeing not-lazy in your work is not the same as working lots of hours.
- bluefirebrand 3y agoNo, this is absolutely not true. Laziness is not working hard. What you're talking about is something else. Sloppy or Careless work maybe? But not lazy. If you're working 40+ hours a week you're definitely not lazy.
- Proziam 3y agoMost people consider low-effort to be lazy. You can absolutely put in a lot of hours, but be putting in near-zero effort. This results in sloppy or careless work, but the root cause is the laziness of the person.
- winwang 3y agoI agree. I see it all the time. Huge amounts of hours being wasted "working hard", and running away from answering the real questions which would double the (positive) output in half the time. That said, I think "laziness" is only a small part of the answer. It seems to me that it's usually about an emotional response. Kind of like procrastination. The hard questions hit hard. There's a real good-feeling self-satisfaction from putting in hours of sweat.
- ryandrake 3y ago> I agree. I see it all the time. Huge amounts of hours being wasted "working hard", and running away from answering the real questions which would double the (positive) output in half the time. I think a lot of times we are put in boxes, and our roles are pretty heavily constrained, such that we do not have the power to "answer the real questions." Raise your hand anyone who's had this conversation with their manager: Manager: "Dev, I'd like you to take more responsibility, be transformational, be a 'force multiplier' for the team!" Dev: "OK, let me make major architectural decisions without having to get approval from three levels of managers." Manager: "Uh, wait..." Dev: "Let me hire and fire, and build up a team of direct reports." Manager: "Hold up..." Dev: "Give me a budget to spend on tools, training, contractors, and so on." Manager: "Whoa, whoa, whoa.. I didn't mean that transformational..."
- johnnyanmac 3y agoNot quite that extreme but yea. I've had those conversations. > Working on X but Y is a blocker > Okay, I can do some work with Y to help get unblocked > No we'll let A (on a different team, maybe a different contracted studio) deal with it, here's tiny widget Z to work on in the meantime Sometimes it means well, sometimes it feels like they don't value your expertise nor care about fostering growth. And sometimes it's just politics (especially when working with multiple different companies and contractors and all that).
- Proziam 3y agoLazy is a convenient catch all for "This person lacks the emotional fortitude to do the work when the option of not doing the work presents itself." There are a million reasons/excuses for people to be lazy depending on perspective. Personally, I view people with this trait to be productivity vampires that I avoid like the plague regardless of their reasons (which in my experience are 99% excuses and 1% genuine hardships).
- bluefirebrand 3y ago> This results in sloppy or careless work, but the root cause is the laziness of the person. If someone is producing a high volume of low effort work, they are not lazy. What they are is not disciplined, or not skilled. If someone is producing low volumes of high effort work, they are similarly not lazy, they are highly skilled and maybe a perfectionist If someone is producing high volumes of high effort work they are a either a one of a kind savant or they are lying about the volume or effort. If someone is producing low volumes of low effort work, then maybe we can call them lazy.
- Proziam 3y agoYou forgot the most common case: Someone skilled produces low volumes of medium-to-high effort work because they are the sort of person who would rather browse social media, or engage in office gossip, or play "call a meeting to discuss" games to avoid having to do the boring work. If someone is "undisciplined," more often they are just lazy and are engaging in avoidance behaviors. Humans with serious executive function issues are a tiny (super tiny) minority of the workforce.
- ferbivore 3y agoWhat's the difference between "lazy" and "serious executive function issues"?
- Proziam 3y agoEmotional vs Medical. A person struggling with narcolepsy doesn't fall into the same bucket as the person who just wastes time at work so they don't have to do work.
- deleted 3y ago[deleted]
- johnnyanmac 3y ago>Someone skilled produces low volumes of medium-to-high effort work So based on the table they are skilled, right? Are you suggesting that they are a savant in disguise and that they can produce high volumes of high effort work if they weren't "lazy"? if the work is considered medium-to-high effort by the organization, your opinion on if it's avoiding "boring" work (which can still be low or high effort) is irrelevant. >If someone is "undisciplined," more often they are just lazy and are engaging in avoidance behaviors. IME it's because the employers don't trust nor want them to work on the high effort work. So either the business's most profitable software is the most boring, or the candidate is too junior (alternatively, the position and responsibility is simply filled or not valued) >Humans with serious executive function issues are a tiny (super tiny) minority of the workforce. Likewise, humans who can do "productive" creative work for 80 hours a week consistently, for years, is also a super tiny minority. At the end of the day, "lazy" is relative and we haven't even established a baseline for what is/isn't lazy. So this conversation won't go anywhere. All we established in your lens is that taking breaks or doing non-technical work (meetings, even gossip depending on the line of work) is not productive in your eyes.
- hightrix 3y agoSome people consider themselves to be "working" while browsing HN or reddit while they are "on the clock". That is being lazy while working.
- shaneoh 3y agoI wonder how you measure balance between being lazy vs. not lazy by this definition? I agree with you, but it's not like it's feasible to remain full-on focused on coding or meetings or documenting for 8 hours straight each day.
- hightrix 3y agoReally good point. There's a big difference in checking HN in the 10 minutes between meetings vs spending 4 hours after noon reading and replying to threads.
- rewmie 3y ago> Being not-lazy in your work is not the same as working lots of hours. You've just provides your personal assertion on a non-definition. Do you actually have an alternative definition that does not imply working lots of hours?
- adrianmonk 3y agoYes, work a normal, reasonable number of hours (let's say 40), but while you're there, give it your best. The point is that hard work doesn't imply excessive hours. If it did, that would mean anyone who doesn't put in excessive hours is lazy, which isn't true.
- default-kramer 3y agoFrom the article > I routinely come across developers who are the real deal: they’re conscientious and judicious in an unwavering way. They set a standard for themselves and do not compromise on it. Whether that’s a deliberate thing or whether they’re just built that way, it’s humbling to witness. If there’s a flaky test, they investigate it and fix it. If there’s a bug they spot in the wild, they make a ticket, and maybe even fix it then-and-there. If a new feature doesn’t gel well with the existing code, they refactor the code first rather than hacking the feature in. They’ll dive as far down the stack as necessary to get to the bottom of something. None of these things are necessary but great developers know that if they don’t address a problem early, and properly, it will only cost them more time in the long run. [... and more.] This sounds like a great definition of not-lazy, and it does not mention long hours anywhere. My anecdotal experience is that I usually only have 20-35 not-lazy hours to give per week; any further hours per week are much less potent. Right now I'm working 24 hours per week and I think my employer is getting a great bargain: they don't have to pay me for hours that would likely be lazy.
- lelanthran 3y agoYeah, but that diligence takes time, and now you have to work on extra hours to keep up performance metrics with the rest of the team.
- yetihehe 3y ago> when I am supposed to fix tech debt? Try to lie about how long will it take. Just today I finished* 1-month almost total rewrite of firmware for one of devices at my work. It started as a 1-week small rewrite of part of communication module for a small bug and was scheduled as that. But I've got chill PM and coworkers who will appreciate that now we can actually fix some 8yr old bugs in legacy parts of that code. * well, now some testing of edge cases and another round of fixes but at least remote code updating works so we can ship those devices... Edit: "Lie" is call to action here, there were some misunderstanding in comments. Previous start of my comment was "Lie. ..."
- Chabsff 3y ago> But I've got chill PM ... Have you considered that perhaps your personal perspective is not exactly representative of large swathes of the industry and that many (if not most) workers do not have the agency and/or leeway to place place themselves in a comparable situation? I wouldn't be so cut-and-dry with your assertion that the parent post is "lying".
- Jtsummers 3y ago> I wouldn't be so cut-and-dry with your assertion that the parent post is "lying". yetihehe is not accusing the parent poster of lying, they're telling them to lie. To claim the work will be X (just the feature, perhaps), and then slip in the extra work (tackling tech debt and other issues), and letting the work schedule "slip" (which they can do because they have a "chill PM").
- yetihehe 3y agoExactly, thanks for putting it so clearly.
- yetihehe 3y agoI didn't call him a liar, I told him that he should lie about what he does. Sometimes you need a little lie about how long will it take and ship good code a little later than bad code on time. > Have you considered that perhaps your personal perspective is not exactly representative of large swathes of the industry Yes. HN is place for ALL kinds of people, sometimes they are not even programmers. Many tips are not applicable to everyone here.
- hombre_fatal 3y agoThat's how I burned out of software. On a mature project in a small team, the only tickets left were hard bugs that nobody wanted. The kind of bugs where you can invest days and have nothing really to show for it except crossing out some suspicions. Or maybe incorrectly crossing one out and then going on a wild goose chase until you circle back to it in a week, flustered. You're expected to commit all of your mental energy to these tickets day after day, and then once you finally triumph and solve the bug after coffee or amphetamine binges, you turn in the code, close the ticket, and you're expected to immediately work on the next ticket. You don't get a real break. But you can mentally rest at the start of the next ticket since nobody expects instant results. But now it's been a couple days and people are asking you what you've been doing so far—you must be blocked, right?—but you've barely started and you're pressured to invent small lies and excuses about why you're behind, each one risking yet another slip of the mask. And when you need some time off the most, it's when you're the most behind of all and people have begun to notice, so taking the time off doesn't even seem like an option.
- vegetablepotpie 3y agoAgile solves a lot of these problems.
- danwee 3y agoHow so? If there are boring bugs to be fixed, someone will need to fix them regardless of the methodology used.
- Humdeee 3y agoEureka! If only it was this easy...
- reflectiv 3y agoWhat kind of stupid statement is this...no it certainly does not. But humor me with an explanation, please...
- vegetablepotpie 3y ago
- swatcoder 3y agoSome of us really are lazy, though. But we set ourselves up in contracting or solodev where our time isn't being managed by a JIRA jockey between meetings. Clients and customers see us as efficient, but it's really just a matter of being so lazy that we don't let technical debt pile up on us and make us have to actually work hard later on. You can get away with it in corpo-coding too, but you need to earn some freedom and have the right team members around you.
- sad_robot 3y agoBut what would the world be if you didn't produce more surplus value for the stakeholders and investors?! I would never understand people who go the extra mile like OPs heroes for some random corpo. You go the extra mile to develop your skills and leverage this new expertise into higher salaries or escape the rat race altogether.
- mvdtnz 3y agoDevelopers are paid handsomely for those 40 hours. Much more than most other professions. I for one am tiring of the laziness of some developers I work with, and I don't even consider myself particularly diligent.
- Trasmatta 3y agoThe funny thing is that burnout can still happen regardless of how much compensation somebody gets.
- layer8 3y agoYou seem to be working at the wrong company.
- TaylorAlexander 3y agoI did a startup for five years that absolutely ruined me. Burnout on top of burnout for years on end. Now I work for an engineering non profit and I work 20-30 hours a week, sometimes less, and money is real tight but I’ll tell you - there’s just no way I can work more hours. I actually have a little time for side projects, and bike rides, and I never ever work weekends. Hell I don’t work Tuesdays either except on rare occasions. I absolutely love my job. It’s my dream job. But it’s not worth killing myself over. We have one life to live and I’m going to fucking love it.
- sokka_h2otribe 3y agoI think I might be a couple years behind you but I found your msg inspirational
- sokka_h2otribe 3y agoThat wakeup from 6 years of stress to <<one life, don't want to be driven this way [burnout way] anymore>>
- TaylorAlexander 3y agoIt takes time to find the right fit. Biggest thing is, when looking for a new job instead of negotiating the best salary, negotiate the right hours. 9/10 places will say “no thank you” if you say you must be allowed to typically work 25-30 hours a week. The place that says okay is a place that won’t push you. Consider the open source world. They will appreciate paying a lower annual salary and still having a dev focused on their work, and they don’t need all the extra overhead (meetings, etc) of a 40 hour week. Also working in open source (as I do) feels really good. You’re not making some rich asshole richer, you’re focused on helping the users.
- johnnyanmac 3y ago>9/10 places will say “no thank you” if you say you must be allowed to typically work 25-30 hours a week. The place that says okay is a place that won’t push you. How do you find such places? I've been very curious about part time software work but knowledge online seems to suggest that freelancing is the only route there. Funnily enough, I wanted to find such a job precisely so I could make my own stuff on the side, which will inevitably involve some signifigant open source contributions due to my tech stack. I've thought about simply being a paid member and essentially double dipping, but that route seems even rarer.
- marmaduke 3y agoI multiply every estimate by at least 3x and often add an order of magnitude, especially when I haven't done it before. when it takes less than I guessed, I use the time to resolve tech debt (or maybe leave early to enjoy the big blue room).
- marmaduke 3y ago> Why should I even bother existing? you should bother existing to push back against economic forces that push us to work too much and feel bad that we aren't working more. you should exist to teach your colleagues that taking the time to consider the broader implications of your work is important. you should exist to contribute your opinions to communities like this one. you should exist to eat chocolate and walk your dog (if applicable). you should exist to listen to Alan Watts lectures on YouTube. You should </ran out of tokens>
- infinitezest 3y agoThis comment inspired me, then made me laugh, then made me very, very sad about the trajectory of human civilization.
- lr4444lr 3y agoHave kids. It'll put things in a different perspective what it means to work 40 hrs./week.
- robocat 3y ago> is extracted to built other's wealth You are blaming the system S. However we have counter-examples where the problem P occurs outside of the system. If P occurs without S then possibly S is not the cause. Admittedly untangling causation, sufficient and necessary is difficult. The article itself appears to be a counter-example that is non-commercial: where problem P occurs without system S. I think it is worthwhile investing time to work out for yourself when to honestly blame commercial constraints, and when to recognise other root causes. Blaming the system by default is unhealthy IMHO.
- onthecanposting 3y agoI suppose you can move to Venice Beach sleep outside and just queue up for the soup kitchen a couple times and shoot up all afternoon.
- Jpoliachik 3y agoWe each have a limited number of fucks to give. It’s more a decision of how to spend those - what is worth my mental energy.
- 000ooo000 3y agoYep, and when the organisation wishes to spend its 'fucks to give' in a way that aligns with how I think they should spend their FTG, I will be willing to spend more of my FTG. Until then, we're both spending the absolute minimum FTG; I like to keep my FTG for things that replenish my FTG.
- he0001 3y agoAt any given point in time, there is always more work to do than time to do things. That’s why there are managers.
- Trasmatta 3y agoExcept managers usually just make more useless work that you also don't have time to do
- justin_oaks 3y agoUnfortunately many development managers have no visibility into technical debt and are more than happy to dig everyone down deeper in debt. And those that do know about the technical debt will often say "We'll fix these issues after the release" which is either a bold-faced lie or they believe it even though it never happens.
- ipaddr 3y agoIf tech debt is important it will show up in a ticket. If not at some point a rewrite will happen. Prioritizing tech debt is something the ticket creators decide.
- happytoexplain 3y ago>If tech debt is important it will show up in a ticket. That's like saying "everything is well-understood and well-planned".
- ipaddr 3y agoYou raise the issue with the decision makers but if they decide not to prioritize it I wouldn't personally take responsibility. Tech debt is project debt not developer debt
- peheje 3y agoor a product with millions of users is scrapped, happened at my org.
- klysm 3y agoThis is how you get tech debt worded as users stories that don't make any sense, with confused PMs that don't know how to prioritize it vs features because the affect on the product is not clear.
- Guvante 3y agoMy viewpoint on tech debt as someone who does try to do it right is tracking is what is important. It doesn't take more than a couple minutes to throw up a task about an issue you see. That issue then becomes the tech debt. Leadership is responsible for prioritizing tech debt and ensuring a certain burn down of that debt. Note that sometimes you burn down tech debt by deciding you won't do a thing, that is perfectly fine as well. The point of the tech debt song and dance of log, verify, handle is to give a second pass at "not right now issues". Sometimes your instinct was wrong, there wasn't a need for X, othertimes it was right for reasons that weren't in your headspace. Most importantly some amount of "I can't do this now" work is actually important. But if you don't take the time to look at it you won't find it.
- oldpersonintx 3y agonot sure what he's on about, 100% of the tech debt I have experienced is from people doing too much rather than too little my advice to future coders is to try to put your entire project into a single file...you'll have to drop every bright idea, abstraction, layer, etc just to make it palatable...and the world will thank you
- digging 3y ago> my advice to future coders is to try to put your entire project into a single file...you'll have to drop every bright idea, abstraction, layer, etc just to make it palatable...and the world will thank you My advice to future coders is to never do this. Clearly we don't work in projects or IDEs that are in any way similar.
- augustk 3y ago> 100% of the tech debt I have experienced is from people doing too much rather than too little “The tactical tornado is a prolific programmer who pumps out code far faster than others but works in a totally tactical fashion. When it comes to implementing a quick feature, nobody gets it done faster than the tactical tornado. In some organizations, management treats tactical tornadoes as heroes. However, tactical tornadoes leave behind a wake of destruction. They are rarely considered heroes by the engineers who must work with their code in the future” A Philosophy of Software Design. John Ousterhout
- footy 3y agowhat kind of projects do you work on where this is reasonable? The only projects I've been able to reasonably keep in a single file are small (<250ish LOC, maybe even 500 depending on language) hobby projects.
- ryandrake 3y agoNot a huge Steve Jobs fanboy, but I always liked his quote[1] about craftsmanship, sweating the details, and giving a fuck: “When you’re a carpenter making a beautiful chest of drawers, you’re not going to use a piece of plywood on the back, even though it faces the wall and nobody will ever see it. You’ll know it’s there, so you’re going to use a beautiful piece of wood on the back. For you to sleep well at night, the aesthetic, the quality, has to be carried all the way through.” I think software as a whole suffers greatly from this "well, I got it barely done, technically fulfilling the requirements, so my work is over" attitude. 1: https://www.goodreads.com/quotes/445621-when-you-re-a-carpenter-making-a-beautiful-chest-of-drawers https://www.goodreads.com/quotes/445621-when-you-re-a-carpen...
- quacked 3y agoI appreciate this analogy, but Jobs made this work by creating a leadership culture that was obsessed with quality and craftsmanship. By all accounts he would regularly refuse to ship hardware and software that wasn't up to his standards and fired people for not building things to the right specifications. In contrast, most of us work in organizations with the exact opposite leadership mentality, namely "get your work done as quickly as possible so we can sell more product, and fudge whatever you have to to make it through quality testing unscathed".
- deleted 3y ago[deleted]
- mattgreenrocks 3y agoThe best reason to do great work as much as you can is intrinsic satisfaction you get from that. Also, think longer-term: if you can program well enough, then you can write great software quickly which is a huge asset when making your own thing and selling it. It is quite rational to optimize for your own wellbeing in these ways even in orgs that are not fully conducive to long term careers.
- toss1 3y agoYup. For so many reasons, from a mentor of mine: Quality Is It's Own Excuse. If you can do it better, do it better.
- kunalgupta 3y agoenergy is finite
- MoreQARespect 3y ago>Sometimes, I just CBF. I spent months (part time, of course) building out an end-to-end test system for my open source project Lazygit, and every day I think of all the regressions that system has prevented and how much harder it would be to add that system now given how many tests have been written since. I know for a fact it was worth the effort. So why haven’t I added end-to-end tests to my other project, Lazydocker? Because I CBF. Building end to end tests is hellishly annoying and a huge amount of work if the tooling to do it just isn't there. There needs to be better drop in default frameworks for building them.
- pradn 3y agoYou basically need to allocate a whole developer’s worth of time to maintain end to end tests. If you’re lucky, they will also have time for your integration tests.
- FalconSensei 3y agoI haven't yet seen this on my professional life (12+ years). There's always a few engineers that want to fix tech debt and improve code quality, but we have to fight with PMs to be able to, because is not new features, experiments, etc...
- rglover 3y agoA guy in my co-working space had a good term for people who introduce technical debt out of laziness: "come on, man, you're being a buddy fucker."
- theptip 3y agoWorth calling out that open source / hobby projects are very different from 9/5. If you are writing code for fun, then avoiding the “ugh field” is perfectly fine. If you are being paid, then “can’t be fucked” is not, in general, an acceptable excuse. (At very least, not in any teams I have run.) I think people often feel pressure to “do it right” when building hobby projects, which can lead to maintainer burnout; unless you are being paid there is no obligation to engineer with safety tolerances. Artisanal hand-crafted code is fine in that case.
- Helmut10001 3y agoI my perfect world of self-hosting, I take all the time I need to implement features and reduce tech dept over very long time spans. Sometimes, a migration from one service to another, or from one type of doing things to another, takes a year or more. During this time, both options run indefinitely alongside each other until I decide that it is time to deprecate something. This is very gratifying. I have reduced tech dept continuously and I see progress. Where I needed 2-4 days per months to manage things, I am down to 1 hour; and this hour is often adding and experimenting with new features. I say "perfect world" because: - everything is under my control, I worked hard to reduce my dependencies - I have only about 10 people to care for, and they largely stay the same - I have no other goals than time reduction and liberty; both go hand in hand I am not sure this is possible in companies.
- shadowgovt 3y agoEspecially on hobby projects, sometimes you do something on one and not another because you really did it to learn, not to have the end result. If building a test framework was fun once and isn't fun again, I don't fault the builder.
- xwdv 3y agoThis isn’t unique to tech debt. It’s all debt. Many people can’t be fucked to pay certain debts. Medical bills? I don’t give a fuck, if my insurance didn’t cover it you’re shit out of luck. No I’m not logging into some website and putting in a credit card to pay. I don’t got time, and I don’t give a fuck. And some go further. Student loans? Can’t be fucked to pay. The interest keeps growing and wipes out any progress you make on payments. So fuck it, don’t pay. There’s even exercise debt. People let fat build up in their bodies to unhealthy levels, and they know they should pay down this debt to themselves before it kills them, but they just can’t be fucked. They stay fat. The best way to deal with debt, is to never take the debt in the first place. In all my years, I rarely see tech debt get paid off. What is more common is the team declares bankruptcy and builds up an entire new project to replace the one that was indebted. Worse, if you do pay tech debt off, it encourages taking on more debt in the future since there is a precedent for it getting paid off. It makes your tech credit score go up.
- esafak 3y agoSometimes the debt gets canceled with the project. Or the customer keeps using the product regardless of deficiencies.
- syndicatedjelly 3y agoAnd just like actual debt, there are times where it does make sense to use debt to finance something else. Want to develop a small project on a local server? Maybe it's worth it to make the proof of concept on a raspberry pi and decide whether it's worth it to invest time into AWS.
- SillyUsername 3y agoI'm in tears at that ironic FP on the link
- sbjs 3y agoHey Jesse, hope you're doing well man. You and I talked about this topic a bit in the past, and since then I've had a little more insight into these issues: 1. Burnout happens when we don't believe in a cause or our belief in it is unjustified, whether we realize it eventually or intuitively understand it without it being conscious yet. In all three of these cases, the reality is just that it's not worth doing in the bigger picture. Obviously, the question of why something is worth doing is complex. I'll admit that there's plenty of reasons for doing things that we ourselves aren't aware of for a long time. I had a passion and almost obsession for solving software problems for decades, and I didn't know why, but I just followed the flow throughout it all. Eventually it led to a short-lived career, and the only concrete result of it so far is immaculatalibrary.com, but there's also the extremely in-depth knowledge and understanding of logic that I gained from it all. Honestly I'm able to continue to work very steadily on immaculatalibrary.com, making incredible progress in the past month alone, without any burnout, because I fully know that it's worthwhile, even without explicitly being able to describe why. Countless reasons for writing software are purely insufficient. Money, fame, solving problems we think are huge, inflating our egos, etc. Fortunately I have no following for my pet software project, so none of these things cloud my vision, and I'm able to focus on it for what it is, and for its only clear and immediate end: publishing and digitizing certain public domain books I find useful and think other people should also. 2. Burnout also happens when we realize that we're building a mansion on top of a pile of garbage. When my site was written in Jekyll or Node.js + Express.js + Postgres + Pug or any other technology I experienced with, it was incredibly hard to move forward and make real progress. I had already resolved to maintain the website indefinitely, but I gave up on it intermittently when I made it too difficult for myself to make literally any changes to the website, sometimes for months on end. The solution for me was to start from absolute scratch, examine the principles of how I wanted to write the site, build it slowly according to that, re-examine these principles regularly in light of what I had already made and how it was working out, and evolve and update my method accordingly. And honestly, during most of the past 2 years, I had a website building app that I am not proud of at any of those iterations. But I am proud of what I have now. And it's very possible that I won't be proud of it in the future for what it is now, in the same way. But that doesn't quite matter. As long as I'm proud of it in the moment, and happy with it, while admitting to myself that it's an evolving WIP, and knowing full well that this is always going to be a dynamic process for myself, then it's good enough for the purpose it has. But that's just the nature of software. It's never finished, but it can be finished in the moment for the job you need at that moment, as long as you examine what the job is and what it should be. The only way I've solved burnout for myself is making sure that the source and destination are satisfactory to me and that I'm fully honest with myself and open to the facts.
- whb101 3y agoThere are some misunderstandings in these comments. This is 100% normal for individual programmers. Motivation, effort, energy, willpower, whatever you want to call it: it's finite. The draw of an organization is that it gets more done than individual programmers. The catch is that in gluing things together, there are cracks, and things fall through them. It's the responsibility of the COO, HR, product managers, etc. -- anyone getting their salary from the organizational stuff and not the technical stuff -- to make sure there are processes in place to address those cracks. To make sure someone has to "BF." Increasingly, at every place I've worked, they just offload those to individual engineers and designers. because they're hard to measure with respect to the bottom line or OKRs. The company suffers and engineers burn out because you can only "BF" on extra little tickets and tasks that fell through the cracks for so long without getting paid more.
- add-sub-mul-div 3y agoFor most of my career I opportunistically cleaned up tech debt without being asked, because I wanted to. I felt ownership. Now that I'm in a Jira-based job with micromanagement and no autonomy I don't do a single thing I don't have to do. Discretionary effort used to be the bread and butter of my career. Now the bureaucratic and social project management overhead required for any change makes things too annoying to be worth doing if I don't have to. I don't care if the product works long term, I don't care if the company succeeds long term, I just do my tickets until I find the next job.
- clnq 3y agoIt's interesting how the companies creating this culture often pride themselves on culture and think they're doing it right.
- HappyDaoDude 3y agoIt is like restaurants they say their ingredients are "fresh". If you have to specifically call it out, there is something wrong.
- 5350-uiop-1130 3y agothe whole "culture" thing is managers wanting to show upper mgmt that their team is happy (even if they're usually not) because they know deep down if their team is not happy or doesn't smile for the photos it looks bad on them. or like "mental health and wellbeing" its a bunch of empty gestures that make no attempt at actually addressing the issues of your work (low pay, long hours, stress, pressure so on..)
- clnq 3y agoIn some exceptional companies that is not the case, and there is really an effort made. But rarely in large companies.
- rapfaria 3y ago"Never ask permission to refactor" has caused so much trouble in my career, specially because folks think they - somehow - have an enlightened path to good code. They don't - it's just easier than reading and trying to understand (which they don't)
- OJFord 3y ago'Aussie slang'? Is the author Australian and assuming it's regional, or American say and it's not in the vernacular there and assuming it's specifically Australian? (It's attributed to Urban Dictionary, but not listed there; just with the addition of 'I' which has a different definition not mentioning Australia.)
- f33d5173 3y agohttps://www.urbandictionary.com/define.php?term=cant+be+fucked https://www.urbandictionary.com/define.php?term=cant+be+fuck...
- zubairq 3y agoI think CBF may actually be a term for mental overload.
- renewiltord 3y agoFunny. In many recreational sports at the low level, there's a similar sort of effect. You can just be better by always choosing to reach for the ball. I've noticed something a lot of successful people do is they always operate at that level. I only do when I'm feeling good: well-rested, ate recently, stress levels moderate. But I've practised at it and I'm getting better. For things you care about, it's always worth taking the shot.
- ike2792 3y agoThis piece just seems like clickbait. In the real world of corporate software every decision involves triage. A sane developer asks themselves if the value added by doing it perfectly vs just good enough is worth the hassle and extra time, and often it isn't. Do those "CBF" decisions sometimes come back to haunt us? Of course, but the solution isn't to try to be a "perfect" developer that never releases anything to production b/c they're constantly optimizing.
- ilaksh 3y agoMost if not all of our decisions are actually subconscious. When you just can't be f*****, it means that some circuit in your brain just doesn't think it's worthwhile to do the refactoring or tests or whatever it is. That circuit could be right in that the payoff is often not actually worth the effort, when viewed objectively and holistically. For example, if you literally spend two months working on end-to-end tests and it in fact does save you three whole weeks of work in terms of debugging or whatever over the course of the next six months, that doesn't add up. I think there are some common extremes. On one hand, the business side often forces engineers to take on tech debt that really is the wrong tradeoff. On the other hand, many engineers may spend time creating a sort of idealized factorization and large test suite that in the end really isn't going to pay off. And part of that is actually just because they are worried someone else will find a nicer code organization or another test to write and judge them for not doing it.
- DanielHB 3y agonot everything is just ROI. Morale and motivation is a huge issue when you feel what you are delivering doesn't meet your standards, even if your standards are higher than they need to be. I would say this is actually the biggest problem with tech debt, the damage to morale that it causes.
- T-zex 3y agoThe relationship between you and your job is very personal. What works in your situation does not necessarily apply to others. I find it similar to having kids. Most of adults have them, but the impact they have on their lives is so different. It all depends on financial situation, support from the rest of the family, friends, health situation.. In many cases this is not a different league, but an entirely different game with different rules and goals. The article calls the lack of pro-activeness a CBF, but that is a symptom and not a cause. The fact that you CBF might not necessarily be a problem with you. It could be that you are in a different frame of reference compared to some other people who "do things perfectly". Maybe moving maximum amount of Jiras into a done state is valued more than delivering this excellent refactoring. Maybe skipping unit tests and dropping feature branch to testers is perceived as a more pragmatic approach. Maybe your perfect commit will be unrecognizable a couple months later, because company is "moving fast". People with great jobs in great companies will not understand this and call it laziness, procrastination or any other thing that will put you at blame. Just like people with great families will not understand what it means to have abusive parents. Software development is about processes, but often developers have no say in setting up those processes, there is no feedback loop. Some naive manager will push to maximize some theoretical metric. In some cases you can adapt, circumvent certain obstacles, but sometimes you just CBF.
- wwarner 3y agoIn less colorful language, you might say that the result is not worth the effort. You can put it even more sharply -- you have an idea of what to do, but it's just not a very good idea. The right reaction (yeah you! in the mirror!) is to generate some more consequential ideas.
- dceddia 3y agoMan, the negativity in here is unreal! I just wanted to chime in and say thanks for writing this, and I feel seen. It describes my daily feelings to a T. I see open source projects with their great test coverage and their principled refactors, and some days I am that person too! I’ll get a burst of Do It Right energy and just knock out a ton of nice well-built stuff. And then one day all of that energy vanishes and, like the author, I CBF. Tests get skipped, code gets bolted into places I know aren’t great, and I just overall start paving the way for something I know Future Dave won’t thank me for. And even though I’m seeing it happen in real time, I don’t have the energy/motivation/whatever-it-is to get back into an inspired Do It Right mode. (And this is all for software that I write and sell on my own.) It was inspiring to see that the author is the creator of Lazygit. If you’re reading this, dude I LOVE lazygit so much. I’ve turned friends onto it who love it too. In my mind you’re in the category of open source maintainers who somehow always manage to Do It Right.
- jesseduffield 3y agoAuthor here, this made my day! Sounds like you and I share similar experiences with motivation. I'm glad you like lazygit, hopefully I can continue to keep it in high esteem :)
- DanielHB 3y agoJust want to drop by and say I use lazygit as well. It is an amazing tool, thank you!
- lambersley 3y agoAs a Dev Manager, please don't "fix it then-and-there." I've found that developers are great at fixing problems but terrible to prioritizing work. After all, its not their responsible to set priorities. The 'fix it then-and-there' on even a small issue has the potential to completely derail a project. Tech debt though, has to be treated with similar reverence to feature development.
- jquast 3y agoI do like to call the large amount of TODO items i find in business codebases as “TO DIDNT”, always some comments about what we know should have be done, but some alternative or smaller solution was done instead. Sometimes TODO comments describe a strict deadline, they read almost like apology letters!
- xtracto 3y agoAah the feeling of masd closing a HUGE list of tickets as ABANDONED in the jira board of a 6 year old startup. Most likely 70% of th e ticket owners don't even work here anymore
- tetha 3y agoOn the other hand, there is value in being lazy in the right places. Like, in our first configuration management, we were strict and anal about testing everything. Add a new property for a config file? Needs a unit test for the default value, needs a unit test for overriding the value. This resulted in so many dang tests, so it was great, wasn't it? Eh. You kinda change one default value and 32 tests across multiple cookbooks fail and it's a big hassle. So you stop changing and improving things. In our new configuration management, we're much more coarse about testing. Setup a consul server, setup a patroni cluster, see if the patroni cluster elects a leader and ships archives to pgbackrest. If it does, the important 90% of the system is probably setup right. Maybe check that a few important metrics are shipped via telegraf and filebeat looks at the right logs, too, that'll be 95% - 99%. The other 90% going wrong after that won't be caught in tests anyway because they tend to be based on business needs in prod. Once that works, why bother testing that ansible can write a variable into a file if the template is changed? Maybe if there is some computation in there, but more often than not, these computations are hard to setup correctly in a test environment, so eh. This is similar to how someone gave me shit years ago about not writing tests for the initial configuration loading and dynamic module loading of a custom application server. The thing is, if I break this in a way I didn't catch, it will break QA and every single local test as soon as I push that and many people will yell at me.
- indigoabstract 3y agoMaybe another way of putting it would be "the thrill is gone". Most us started out with a lot of enthusiasm for programming, but for some it slowly eroded along the way or the novelty wore off. To me, it's a mystery why some people can maintain their passion in the long run, for some it's on and off while for others it completely dies at some point. I also find it funny that Australians felt the need to turn the "can't be bothered" expression into something slightly stronger, if the author is right about this.
- zerbinxx 3y agoI dunno, I’ve never been head-over-heels passionate about writing code, though I’ve been at it for 15 years now and I still get quite a kick out of it in the right circumstances. I tend to gravitate towards bug fixing, integrating work others have done or improving it slightly, testing, deployment/monitoring automation, etc. I’ve also 100% had lulls where I just hate it and cannot be bothered to do my job or do it well, I think it ebbs and flows with what you’re being asked or required to do.
- indigoabstract 3y agoI think I'm the other way around. I love coding new stuff, but sometimes I dread fixing bugs, especially if I don't have an immediate hunch about the issue and end up investigating for hours or days for a fix. But I feel fortunate that I still enjoy programming for the most part (though not as much as 20 years ago) and haven't had too many situations where I had to force myself to do something that I would rather not.
- black_13 3y ago[dead]
- xyzelement 3y agoVarious debt has different "interest rates" and the skill is to pay off the high interest ones as the expense of 0-rate ones. I have a closet in the basement where when I did the vinyl plank floor, I ran out so the planks don't quite go to the back of the closet all the way. Problem? Yes? A bit ugly? Yes. But in reality the problem is 100% of the time covered by boxes and anyway I can live a happy life in this house for decades and not be affected. That's 0% tech debt. On the other hand if my gutters are clogged, there's interest on that because the longer I wait the costlier it will be to deal with since clogged gutters can lead to basement leaks or gutters themselves detaching. Or, if my stoop is broken, that's not just an eye sore but I keep tripping on it, the faster I fix it the sooner I stop tripping. That's a high-interest debt that should be fixed asap. In engineering, a high-rate debt could be some architectural thing that slows down the development of every single feature. You want to quickly pause features to pay this down so everything can move faster. On the other hand, some file that you never touch having some shitty code or lots of TODOs may be a very low interest debt since in practice you never touch it or are otherwise not bothered by it other than knowing that it's ugly - like my closet floor. Engineers make two mistakes around this - fixing zero-interest debt when there's more important things to do on one hand. On the other hand, when they say "oh, product management/leadership didn't sponsor our tech debt fixing" - it's often because we fail to articulate the real cost of that problem - explaining that it's high rate and how it's costing you.
- Bognar 3y agoI love this analogy, interest rates on tech debt. It's such a natural extension of the phrase tech debt and succinctly gets a point across. I'm gonna have to steal that and start using it at work.
- munificent 3y ago> It's such a natural extension of the phrase tech debt and succinctly gets a point across. The metaphor of interest was the whole reason that Ward Cunningham initially coined the term "tech debt": "Technical Debt is a metaphor, coined by Ward Cunningham, that frames how to think about dealing with this cruft, thinking of it like a financial debt. The extra effort that it takes to add new features is the interest paid on the debt." https://www.martinfowler.com/bliki/TechnicalDebt.html https://www.martinfowler.com/bliki/TechnicalDebt.html
- Vinnl 3y agoOne thing that I've gotten better at, but still find hard, is tolerating CBF in others, when doing code reviews. I'll still call out that something would probably be a good idea (e.g. adding another unit test), but I'll coat that in layers of "but I also understand if that's too much of a hassle". Half the time folks will still make (something close to) the requested change. The other half they indeed CBF and just merge it as-is. In those latter cases, I'll be slightly disappointed, but I'm also consciously telling myself that honestly, it's often a fine reason, and if it's really important, I can still consider doing the work myself.
- deleted 3y ago[deleted]
- osigurdson 3y agoI personally don't even like the tech debt analogy as the term "debt" invokes a psychological reaction which can become a distraction. There are really just three things: 1) existing code that does not need to change, 2) existing code that should change and 3) non-existent code that should exist. Yay for 1 and are we working on 2 or 3 today?
- samus 3y ago> As I continue my journey as a developer I learn more about myself, and one of the things I’ve learnt is that my motivation ebbs and flows. I’ll have a good run, inhabiting the persona of the developers I look up to, however imperfectly, until I once again find myself with the constraint that trumps all the extrinsic constraints of the project at hand: a deficiency of motivation. I believe this is the key insight here, and behind every rockstar developer there's just a person that probably has a lull from time to time as well.
- michaelteter 3y agoI recognize a lot of the author's feelings. Some of us are apparently built to be fixers, solvers, and supporters. We are the elves at night that are not seen, but problems that would have happened without us now don't happen. And a problem that doesn't happen is a problem that's not noticed. However, that drive to make things better eventually gets bogged down by the apparent lack of care or concern by many other people which leads to more new problems that often shouldn't exist. At some point, you step back and say, "Perhaps if I stop making things better, collapse will come sooner and then people will wake up and decide to pay more attention to their actions and outcomes." Technical debt is sometimes an intentional trade-off between short term and long term goals. There are times when we would agree that we can cut some corners or not plan for certain expected futures because our time is precious and limited. When such decisions are weighed before taking action, technical debt is acceptable. But when people are either too inexperienced or simply don't care, the tech debt is just wrong. What's even more demotivating is watching inferior tools become the most successful, especially as those tools seem to attract the kind of developers who don't see or don't care about software and system quality. These are the people who, when you show them an alternative approach (which has less risk or long term cost - and even without much additional upfront cost), they inevitably say, "Why would you do that? This works fine." And so you end up with 200 line functions, horribly tight coupling everywhere, copy/pasted blocks of code everywhere, etc. Another demotivator is when key decision makers are too comfortable with "how it has always been done" and are unwilling to grow to the new challenges and company size. You could hustle and deliver proof of concepts which show how company wide shared architectures would reduce effort across most teams (silos) while increasing reliability of systems... and ease of employee migration from one team to another. But after doing things like this and making traction perhaps 1 in 10 times, you eventually decide it's not worth trying. CBF. Meanwhile, the same tech leader is constantly harping about our need to hire more engineers. So clearly, the answer is not work smarter, but throw more people at it and build more variations of tech debt. (When a new engineer is faced with maintaining a debt-ridden legacy project, they don't stick around long.) I'm sure every profession has some version of all of this, but our seems especially nasty in this regard. I used to balk at the idea of professional certifications before one could be a software engineer, but now I think it would be worth it. Everyone should have to understand and demonstrate more than just passing Leetcode challenges to work in this field.
- wolverine876 3y agoThe solution is to apply the right tooling to the right task, to maximize ROI: * The DIR (do it right) tooling, which always is in limited supply, is best for building things that have a high lifetime impact. It could have direct impact; it could be a gear in the foundation of many future products. * The CBF tooling is for low lifetime impact work. Inevitably, because you are human, you'll use your CBF tooling at times. Know when that is happening and apply it to the right project: For example, the quick script to clean and transform some unique data. In other words, the advice in life is always the same: Know thyself.
- w10-1 3y agoThere are two main aspects of misperceiving difficulty/opportunity. The first relates to feedback clarity. For someone at 98% in a class or life, the few next things are easy to see and focus on, and are typically small delta's from the global maximum. But at 60%, there are many things to fix and many directions to local maxima. Someone who can make headway from 60% is far more skilled than someone who makes improvements from 98%. Their adaptive function is much more complex and comprehensive. (I would also argue they create more social value to go from 60-75%, but that depends on output utilization.) It's roughly same with the range of early-late stage companies, with 40%-95% clarity. The second aspect is, well, dependent co-arising: you're adapted to the difficulties you've had, so you can tolerate or solve them better than most -- leading you to prefer those situations over new ones, even though the new ones are objectively better. In a sense, you're maximizing your activation rather than benefit. It's a bit of a trap since any detachment requires de-activation, which is (a) opposite of what you previously valued and not exciting, and (b) typically confronts one with the exported costs of one's prior focus. A benefit of recognizing misperception is to counter it where it reduces value. CBF is essentially the saturation state for incentive vs difficulty, where no additional incentive or ease will induce further activation. This is actually the goal state of bureaucratic organizations working via validated processes or people minimizing cost/maximizing slack at work. So: not always bad, but certainly not exciting. The answer is to step out of the equation. Have other engaging activities (or businesses) such that time/resources wasted in one is quickly pruned to shift time/resources to others. Do this enough and you can't be trapped, because you're familiar with the hype/deflate cycle of coming and going. You might also be less daunted when struggling at 60%, and less full of yourself when sailing at 98%. Because these switches entail incommensurable decisions, they exercise what might called be your moral core, you identify a bit less with your roles, you can approach new tasks and new people with openness, and you might spend more time just being.
- langsoul-com 3y agoTrue, I can't be fucked dealing with tech debt. It's long, boring and has several layers of hell you'll only find out when starting the work. If someone else does it yeah cool, nice. Otherwise it's too much work.
- LoganDark 3y agoDoesn't this just... describe ADHD? Pouring tons of effort into personal projects doing things that you CBA to do for anything else? not being able to prepare minimum repros because reporting the bug itself was the most that you could manage? eh. My case of ADHD in a nutshell.
- zerbinxx 3y agoI don’t think that’s really ADHD. It’s a motivation/interest issue (and maybe it’s not really an issue) and it can be fixed by factors like choosing to pursue fewer things, focusing on your day job, or prioritizing certain things over others. It might be ADHD if they’re not functional at any of it, but it certainly doesn’t sound like it, and from my experience with people with ADHD, many are actually dysfunctional to the point of needing medication to get anything meaningfully done.
- LoganDark 3y ago> from my experience with people with ADHD, many are actually dysfunctional to the point of needing medication to get anything meaningfully done. I didn't have medication for the majority of my life and I got plenty done. I just had a certain degree of executive dysfunction that's hard to describe, but manifested itself as basically losing every hobby whenever I got bored (which is not supposed to happen nearly as much). I didn't even know it was a thing that just happened to people (and had a name like ADHD) until about a year ago. I seriously just thought I was lazy or "couldn't be fucked". So it could totally be ADHD, speaking as someone with severe ADHD who also did not know it was ADHD for quite a while.
- angarg12 3y agoMuch of CBF can be explain simply through rewards and incentives. See, when I joined my current company, I was full of energy and I did BF. I fixed broken builds. I made our abandoned test suite green. I refactored our deployment pipeline. I hunted down the root cause of bugs and fixed them. But then I noticed several things. First, rather than encourage people to behave like me by example, they did the opposite. Why fix a broken build when I would come along and do it? it turns out doing shit work just gives you more shit work. Also the guy does hack jobs got promoted ahead of me because he is a master of optics and presents his work much better than it is. And look at how fast he delivers! it doesn't matter his code keeps causing problems in prod, by then he has moved on to another project and it's someone else's problem. Oh, and that junior guy than I spend several hours a week helping makes more than me, because we hired him in 2022 when we were desperately throwing money at people, but I didn't get a raise in 2023 despite an "exceeds" rating because you know, it's tough times and we need to buckle up. Listen, I love what I do and I want to excel at it, but is it any wonder and CBF? At the end of the day I work for a salary. If my efforts aren't rewarded, or sometimes actively punished, my motivation goes down the drain. Sure, part of it we do for ourselves, but at some point you have to question who is really benefiting from the situation.
- RHSman2 3y agoWhen we only work for a salary we’ve lost sight of what it means to be alive. Move on, go somewhere you deserve to be. Find your people.
- rawbert 3y agoThis is just wrong if you despise the concept of paid work at all. I spend these 8 hours a day because I am forced to. I need to pay for food and shelter, for my kids education and all the other stuff. If this wasn't the case I would give a fuck and spent all the time with my family, play video games and just live from day to day. Choosing an IT-career is just the least evil for me.
- RHSman2 3y ago
- crvdgc 3y agoMaybe slightly missing the main point here, but I find documenting your compromise is a good trade-off (TODO: BF later). Make a note in the comment or PR, create a ticket for it, but leave it for another day. It takes little effort. Writing things down helps you reassess your choice. And it serves a good starting point for future revisiting. It also keeps you honest (certain culture promotes a pretence of perfection). Even if it becomes someone else's problem later, they'll be grateful for the explicitly. The tech debt will occur anyway, so you might as well make it visible rather than invisible. Knowing what you owe is the first step of repayment.
- jesseduffield 3y agoI completely agree
- ChatGTP 3y agoI personally think this attitude is 100% natural. Computers were always sold to me as assistance and aids in order to automate tasks so I can enjoy my life more. I think this not giving a fuck attitude is directly part of this. If the thing works, it'll probably do and I can go back to enjoying the sunshine rather than sitting in some dank cubicle trying to be awesome.
- Williams121 3y ago[dead]
- Narcie 3y ago[dead]