14 ms·
Build your career on dirty work
- hcks 4y agoAbsolutely! But then why even work in software? There are a lot of much more impactful, dirtier jobs out there! You should maximise your impact and utility by being a garbage man. You may even do it for half the salary: even better utility for the community!
- hollerith 4y agoNot only did Steve Jobs contribute more utility to the community than 100 garbagemen, but also most of the people who collaborated with or reported to him did, too.
- RyanShook 4y agoI agree with the premise of dirty work being more valuable. The trouble I see with the recommendation for taking on-call work is that it’s too easy to get “stuck” in that role without the tools to improve the process. There will always exist some amount of dirty/on-call work and reducing it is usually a business logic issue not a code issue. Maybe if you’re at a high-growth company you have the tools at your disposal to fix the process.
- namenotrequired 4y agoIn that case, just working to get the on call team the resources it needs to fix the underlying issues sustainably would be a very valuable contribution
- collsni 4y agoThis works, I can say so from self experience. Found that my company had a wealth of tech debt and powered through it for years. Super challenging to fix what others can or won't , tons of experience gained in the process.
- chrchang523 4y agoThis works, but I'd add the following: always keep your eyes open for "dirty work" that you seem to enjoy more than most other people. That represents an opportunity to make disproportionate contributions. Relatedly, you should prioritize building good working relationships with others who specialize in different, complementary types of "dirty work".
- jmyeet 4y agoThe truth is that what you actually do at work doesn’t really matter. The important thing is how your work is perceived and that is a function of how well you are liked which itself correlated with common background, cultural similarity and essentially innate quality of trustworthiness (there’s research on this). Let me give you an example of how this can play out. Say you do the dirty work no one wants to do. These are are all possible outcomes: - you get stuck with that and it becomes expected of you - people feel that area still sucks so you didn’t have a lot of impact - people really value your impact - you’re viewed as having initiative and tackling hard problems - you’re viewed as not tracking org priorities and instead doing work nobody cares about - you get more opportunity to work in high profile projects because of your efforts - you get less opportunities because you’re too essential in your dirty work - you get less opportunities because you’re viewed as not working in what’s high impact - you will get no credit for avoiding a catastrophic failure that didn’t happen. Worse, people may wonder what you’ve been doing (y2k anyone?) All of these narratives can be constructed from the same set of facts. Part of this relies on your ability to communicate. A bigger part is networking. But the biggest factor of all is whether or not they like you. EDIT: fixes as per comments below. Thanks!
- Noumenon72 4y agoBased on your last sentence, I think your first paragraph's "is not a function of how well you are liked" should not have the "not".
- Noumenon72 4y agoAlso, I think "not tracking org properties" should be "not tracking org priorities".
- cgh 4y ago> - you will get no credit for avoiding a catastrophic failure that didn’t happen. Worse, people may wonder what you’ve been doing (y2k anyone?) This is so true it hurts. I worked for years at a certain Silicon Valley BigCorp on a low-level networking library with one other guy. We of course had bugs but we managed them and delivered on time. It was therefore assumed that our library was "easy" (it wasn't) and the buggy deliverables that made up other parts of the application were "hard" (they often weren't). So the folks who eventually delivered the buggy libraries got the recognition while we toiled more or less in obscurity. It was a bitter lesson in the importance of self-promotion.
- Animats 4y agoThe first seven years of my career were spent mostly fixing crashes in a mainframe OS. When I first came to California, there were two piles of crash dump printouts six feet high waiting for me. Gradually I worked down the pile, and time between crashes went from hours to months. Then I got into high-security operating system development for DoD, which led to proof of correctness, networking, and other theory. The aerospace company was happy to hire someone who'd been deep inside a major operating system and had fixed that many crash-type bugs. I was happy to pivot to the problems of designing reliable and secure systems.
- nnadams 4y ago> The lamentable work that many people avoid are great places to look for high impact, low hanging fruit. Agree with this. When it comes to succeeding at work, especially at a big corp, I've always said something similar: after responsibility is abdicated, opportunity remains. Being annoyed at the present is often a position of power in the software world. Suddenly you have motivation to drive change and a bit of knowledge to get started. Of course you need the time and the freedom to use that. One way I try to spend time doing the dirty work is by over-estimating. It's taken many years to really learn this, but I now over estimate tasks by quite a lot. This helps me not feel rushed, feel good when I deliver early, and gives me time to look around and improve something. Reflecting on previous tasks and what was annoying or oft repeated has helped me improve my process.
- tokinonagare 4y ago>One way I try to spend time doing the dirty work is by over-estimating. It's taken many years to really learn this, but I now over estimate tasks by quite a lot. I'm only 4 months into the industry and I felt like a slacker for figuring out this trick. Now I feel better about it thanks to your comment :)
- andreimackenzie 4y agoHow estimation is marketed matters, too. Don't let your stakeholders think of it as an over-estimate. It's an estimate that considers the needs of the full software development lifecycle: automating tests, developing monitoring, refactoring to clean up old tech debt, etc.
- galoisscobi 4y agoMakes sense. It also must be nice to convey the dev lifecycle factors that go in to estimates. Where I work refactoring is a trigger word and we are advised to never say the word when talking to management and it must never show up in any planning material/meetings etc. Someone made the mistake of including refactoring efforts in their plans and they were asked to scrub it out.
- scrotiemcboogs 4y ago> We’ve been to the fucking moon y’all, we can figure out a way to halve our Series-A-sized support queue. Favorite quote from the article. ____ I think the concept of dirty work is important but isn't always as fruitful of a pursuit as the author makes it seem. There are plenty of cases of dirty work success stories, but there are just as many stories of automated runbooks that never end up being used or documentation never read. What's important is to understand high signal dirty work. Listen for what is truly causing pain within a team or across teams and begin to pull on that thread. Talk to the stakeholders. Understand the ins and outs of the problem. Then go down the rabbit hole of getting hands dirty.
- nnadams 4y ago> Understand the ins and outs of the problem. Then go down the rabbit hole of getting hands dirty. Yes, I think this nuance is somewhat lacking from the article. Do not sign up for every on-call shift or only do QA work all day. That's how you can become "that person," and you'll just watch your team expect that from you. If you're early in your career, my suggestion is do different kinds of dirty work, switch it up as much as possible. Get a feel for as many as different things as possible. Then you'll be better prepared to leverage that knowledge, and you'll know when it's worth going down that rabbit hole.
- scrotiemcboogs 4y ago> If you're early in your career, my suggestion is do different kinds of dirty work, switch it up as much as possible. Spot on. This is massively important. Not only will you build a better picture of systems as a whole, but you'll also discover what is interesting and not interesting to you. Finding that out early on is invaluable.
- ForHackernews 4y ago> We’ve been to the fucking moon y’all, we can figure out a way to halve our Series-A-sized support queue. Who's 'we', kemosabe? I guarantee none of the overpaid yaml jockeys at my adtech firm have ever been involved in anything that flew to the moon.
- ttpphd 4y agoThis runs exactly counter to the site reliability engineering guide that the Google folks put together. Grungy toil work is bad for the worker and bad for the organization.
- cgh 4y agoOne of my first jobs out of school was implementing internationalisation libraries for an application that ran on Windows and a variety of Unixes (AIX, HP-UX and Solaris, if memory serves). It was predictably horrible and understandably no one with actual work experience wanted to do this tedious labour. In the course of my work, I found and reported/fixed various bugs in other parts of the application and built a certain amount of credibility in the eyes of my coworkers despite being so fresh-faced, mainly because I was in this particular trench alone. It showed me the value of tackling the ugly stuff as a chance to control one's micro-destiny, so to speak. That said, if faced with that particular task now, I'd delegate it to a new grad in a flash.
- weatherlite 4y agoBuild Your Burnout on Dirty Work
- swivelmaster 4y agoI did something like this back when I worked at a fast-growing startup that was eventually acquired. I built shiny new features, sure, but I also reviewed every line of code from before I joined, found major problems, refactored them and documented best practices so they could be avoided in the future, and made sure that the founder/CEO was aware of my work every step of the way. I was promoted to lead the team a few months later. To be honest, I found refactoring and cleaning up tech debt to be just as fun, if not moreso, than building new features. And the user-facing results spoke for themselves: Less bugs and faster response times. Everybody wins.
- ilaksh 4y agoRight now I am solo (and barely getting by) so I am currently following the "Build Your Business By Doing Every Single ____ing Thing Yourself" model.
- orwin 4y agoI don't think i have the same career goals as the author, so not everything apply to me. But he On call/support advice is golden, even if your aim isn't to become the best/most irremplaceable engineer in the company. Doing support and being on call for emergency (as long as the days you're on call are well defined and you're paid OT for it) is the best way to understand what the company/team is selling, how to debug the worst code the comapny wrote and why it was written like this. I probably don't have as much experience as other engineers here, but i've been at 4 different companies, and i became usefull way faster when i was put on support first.
- seanhandley 4y agoI’m from Lancashire in the UK and we have a saying here: > Where there’s muck, there’s brass.
- ISL 4y agoI'm generally on-board with the thrust of the article, but deep-dive volunteering for on-call work should be regarded with caution. Only do it if it is properly compensated and your time is valued (vacation days to compensate for your lost utility, for example). If you're on-call and want to do anything outside of cell range or want to be unconditionally available for family or friends.... you can't.
- bitL 4y agoTypically those companies requiring on-call periods give their employees pagers to keep during vacations...
- cratermoon 4y agoAt the top of my resume, I have "Polishes old code", and in the key skills says "Working with legacy/heritage code". I've never had a problem finding work.
- ourmandave 4y agoThat's why I always start green field projects with already obsolete tech stacks. You're welcome.
- cratermoon 4y agoThere are many aspects of code that make it "legacy", but "obsolete tech stack" is only one, and certainly not the most important one.
- wwarner 4y agoSry there is no way at all to have high impact working on GDPR. The only way to have high impact is to make a lot more money than you’re paid, which is totally possible if you focus on solving real problems for customers. In other words, don’t be a cost center, be a source of revenue.
- cnorthwood 4y agoThere are more ways to quantify impact than money.
- derfabianpeter 4y agoInteresting perspective that I’d like to challenge. Many European companies now face a future in which they’re banned from using US cloud services due to GDPR. Fixing that problem seems like having high impact.
- bigcat12345678 4y agoThe problem is that Dirty Work requires an order of magnitude more time and dedication to get the deserved recognition. It's not that you fixed one person's mess, and you'll get a praise in the next perf cycle. You almost always need to show the majority of the team at least 3 times that you saved their asses. Then finally you can demand your work to be recognized. And right, even if everyone recognize your achievement, you still need to ask.
- friedman23 4y agoIf you do this, you get pigeon holed into this kind of work.
- davewritescode 4y agoThis is 100% absolutely not true
- rzzzt 4y agoPerhaps parent is talking about their own experience. What does that mean for the percentage of true-ness?
- MisterKent 4y agoThe title is a bit misleading. The author is advocating getting rid of dirty work by solving the problem. This can mean starting by doing the dirty work, i.e on call to identify the problems. Fixing them is what he is advising people build their careers on. This is definitely something I have advocated for, and recommended to other people. I'll add that a lot of the work that is referenced here is good at 80% done and only marginally better until it takes a giant jump at 100%. Code coverage is a good example of this, getting from 0 to 80% code coverage is good. Getting to 95% code coverage is slightly more useful. Getting to 100% gives you leverage to find dead code, have actual confidence is things, prevent new features and code from not being tested (previous person go to 95% coverage, so a new feature might not dip the gate), and removes a lot of arguments around "I'll add tests later". I've seen similar patterns with things like on call incident queues for hitting 0 incidents. And automated alerts becoming so reliable that engineers don't dismiss them as noise etc.
- mkl95 4y ago> So you’re in the on-call rotation, now what? Make pages approach zero. You can do it. Trust me, you can make pages trend towards zero. Many have done it on teams at the highest-scale companies in existence. How about people own up to their mistakes instead of relying on random Joe who happens to be on call to fix it? I have been burned too many times by write only code written by some coworker who wants nothing to do with it. This is not just an on-call issue btw. > Apologizing to angry customers This is a terrible idea. Just because a customer is angry it doesn't mean you should apologize. SaaS customers are angry all the time because some 3rd party integration is returning a 5xx error.
- dvtrn 4y agoHow about people own up to their mistakes instead of relying on random Joe who happens to be on call to fix it? I have been burned too many times by write only code written by some coworker who wants nothing to do with it. This is not just an on-call issue btw. Sorry for my french but Jesus fucking christ, thank you. I was being woken up constantly at last job due to a bug in the application because I was the Devops guy and this is exactly how I was treated. I spent weeks finding contributing causes to frequent failures. Gathered all the evidence I could find and begged for a fix, I scheduled calls with the product team; I poured over documentation and diagrams “this is the problem, this is inherent to the way these requests are being made, until it’s fixed we have no choice but to throttle the app”. I recorded a ticket each time I got paged and linked back to the team who owned the feature. What was infuriating in the end was finally being told that they knew about the problem long before I brought it up and even HOW to fix it; it was just consistently being deprioritized by people who had the means to influence the decision on “fix this” or “write new shit”. Eventually I just suppressed the application in PagerDuty and stopped waking up whenever it would fail. SLA slipped, customers complained, I find myself in a meeting being asked very aggressively “what’s being done about this and why are you ignoring PagerDuty?” I said I wasn’t ignoring PagerDuty and presented a log of 20 something tickets I created linking back to the original “Please fix this request”. I told my leadership “I’m not the one ignoring this problem, I have been trying to get this addressed and prioritized for months”. Laid off a month later. It’s becoming a growing reason why I want out of Ops and never want to return to it: companies hiring Ops people and treating us like the kitchen sink for work the company is too lazy to actually address and properly prioritize through staffing, planning or both.
- CSMastermind 4y agoI'm not sure "dirty" work is the right framing here. I'd consider those problems "hard work". They aren't neglected because they're perceived as less interesting but often because they require knowledge or abilities that many engineers don't have and aren't willing to put in the work to learn.
- zeroth32 4y agoReally bad advice! Hard work does not pay, corporations are not meritocracy. About 15 years ago, our corporation had orphaned project. Entire team of 5 developers quit without notice (found other job). Horrible code, no documentation, no tests, no spec, not even build system (was on one of the developers laptop). There was important deadline 6 months away. I stepped up, worked 16 hours a day four couple of months, eventually got project back on track, and trained new team. As reward I got put on PIP (performance improvement plan) and eventually got fired. Problem was: - I worked for other division, for my manager I was dead weight. It was sort of emergency reassignment and paper work never got ironed out. - I mostly worked from home, come to office barely. Some coworkers thought I left. Not keeping appearances was main excuse for getting me PIPed. - My project was 1 month behind the schedule. I missed the important deadline. - Senior manager who initiated my work quit, leaving me behind. I am not sure what is the lesson here. But now I work in remote job, where I can do all my weekly work in about two hours. Way happier now. Edit: this was official assignment from very senior manager within company. I saved them a lot of money on fines!
- willio58 4y agoAppearances are soo important in jobs, much more than quality of work. This is why fully remote jobs are so great, people are on a more even playing ground.
- agumonkey 4y agoI'm trying to find books about strategics and tactics used in work groups.
- whiplash451 4y agoThe lesson is : watch your own back. Communicate to people about what you do and (more importantly) what you are not doing and last, never take double assignments. Seems like you trusted your company a lot more than you should have.
- bluedino 4y agoBad management/company, not bad 'hard work'
- rdtwo 4y agoI think this is partially true but it’s important to make sure the garbage is on fire before cleaning it up. If you clean it up before it’s on fire you just become a lowly garbage man. If the garbage is on fire and you positioned yourself to clean it up you are a hero and take credit. If you are a really corporate pro you wait till the fire is mostly put out then sweep in for the photo op.
- vyrotek 4y agoThis advice in comic form. https://twitter.com/_workchronicles/status/1314436905501511681 https://twitter.com/_workchronicles/status/13144369055015116...
- rdtwo 4y agoI’m going to print this out and hang it on my wall
- mjr00 4y ago> I think this is partially true but it’s important to make sure the garbage is on fire before cleaning it up. Yeah. Especially true as the article mentions tech debt as an example. Too many times I've seen overeager developers early in their careers insist that the most important thing in the world is rewriting the old service written in C++/ASP/whatever, without respecting the fact that the old service has been dutiful performing mostly without issue for years, and the only time it comes up is the one time per year someone needs to go in and spend two weeks adding a minor feature or bugfix.
- dasil003 4y agoYou summed up my reaction to the article perfectly. Anyone working in a large company can easily point a half dozen problems off the top of their head. This is especially true of software engineers who are detail oriented by nature. Lots of these ideas will overlap and find common cause, but some will be conflicting. At the end of the day, focus and alignment is needed to avoid chaos. Therefore, it's best to go about these things incrementally, building awareness along the way, and ensure you have executive sponsorship commensurate with the investment you are making. The narrative should be designed to resonate with as many people as possible. If you miss the socialization process you will mostly get a big shrug at perf review time.
- danwee 4y agoI don't avoid on-call for the reasons the article states. I avoid on-call because I don't want more money in exchange of my free time.
- honkdaddy 4y agoI spent the first part of my career following this kind of advice, working as hard as I could, and chasing some mythical prestige I thought would make me happy. Now I make $320k, work remotely about 20h/wk, and have never been happier than I am right now, checking boxes and fixing bugs as a senior engineer on a minor product team at FAANG. I don’t care if I ever get promoted, maybe I will, I probably I won’t. I get great feedback from my managers and I have a friendly relationship with my coworkers, most of whom are happily chomping at the bit to get promoted next cycle. I realized during the pandemic how much better the world outside the internet is, and now I spend my spare time hiking mountains, painting murals, playing in a crappy cover band with my high school buddies, and eventually finding a wife to settle down with. I refuse to believe I’ll spend my time on my deathbed wishing I’d written more code and spent less time outside; life is just too damn short. I’d like to give the exact opposite advice of this author - find an easy, comfortable, well paying job and fill the rest of your life with things that actually matter. I truly believe you’ll be happier for it.
- dicriseg 4y agoIt's good work if you can get it! [0] But most people out there, even software engineers, aren't going to make 320k with minimal effort. I do agree with the overall idea that you should define "enough" for yourself, and slow down to enjoy life once you get there. [0]: https://www.theonion.com/if-i-had-one-piece-of-advice-for-todays-youth-it-would-1819584709 https://www.theonion.com/if-i-had-one-piece-of-advice-for-to...
- draw_down 4y ago
- dangus 4y ago> find an easy, comfortable, well paying job and fill the rest of your life with things that actually matter. I think that's kind of what the article was about: raising your career status high enough so that you can get one of those nice jobs. You can't just pick a $320k job off of the job tree, that's almost 5 times the median household income. Without having marketability, the task of finding an easy, comfortable, and well paying job is advice akin to "just win the lottery, that'll cover your expenses."
- baobabKoodaa 4y agoThe author mentions documentation as an example of dirty work that you could grind as a way to "build your career". Personally I enjoy writing documentation and I make an effort to write documentation in every project I work in, and I'm yet to see a single project where that work would have been valued. Nobody cares if you write great documentation. It's not a way to "build your career". I stopped reading the article at this point.
- dharmab 4y agoI have had the opposite experience. At every job I've had other than the first I've been praised for my documentation and it has opened up many opportunities for me.
- number6 4y agoAre there some advice you can give for writing good documentation
- dharmab 4y agoThe biggest piece of advice I can give is keep it short and put more important information up front. Every doc should start with a one-sentence plain language description of the thing's purpose and context. Pascal once wrote in apology "If I had more time, I would have written a shorter letter". Be exactly as detailed as necessary and no longer.
- luisgvv 4y agoCheck out https://diataxis.fr/ https://diataxis.fr/ I think this "documentation framework" has helped me a lot to write precise docs and how to structure everything regardless of the platform
- number6 4y agoThanks — took the day to work through it. Really cleared some things up conceptually
- ur-whale 4y agoI strongly disagree with the advice given in this article. Two main reasons: 1. This is essentially advice someone who puts his career ahead of everything else that matters in life, i.e. I'm happy to eat shit as long as it advances my career. If that's what you really want from your life, more power to you, but that's probably not for everyone. 2. Not everyone will have the skill level to fit that profile but if you happen to have been gifted with the luck to work on stuff for which you are truly passionate, you will both tremendously enjoy going to work every day *and* advance your career effortlessly. This article sounds like a recipe for early onset depression. Everyone will have to regularly perform shitty, unpleasant work in their career, but unless you balance it with some amount of creative, fun and rewarding work, you're going to be miserable, and by way of that, not be very performant.
- karaterobot 4y agoIn my experience, people who lean into doing dirty work just end up doing more dirty work. It's a recipe for being invaluable to the team, but not a recipe for career growth: they want to keep you around, but they want you to continue doing the dirty work. The best of career growth advice I've seen work consistently is: be working on a profit center rather than a cost center. You can be the best employee in the world, but if you're on an unsexy, money-losing area of business, you will likely watch people get promoted around you, because they worked on the thing that gets all the attention. Doesn't matter if their contribution to the success was insignificant, or that the one project was necessary for the other to succeed. It's just the halo effect of being on a winning team that does it. Yes, it makes no sense, and it's not rational nor fair, but that's how business often works.
- strikelaserclaw 4y agoI wish i could upvote you a thousand times. The path to a good career is focusing on the right stuff and digging deep. Think about where you work and what the most important products are at your company and what skills you need to become a valuable contributor there and move in that direction even if you are very far away from there currently. If you have 0 interest in the most valuable products at your company and you still want a good career, then move to a different company.
- bitL 4y agoBasically, "don't get pigeonholed". It's similar to data engineers thinking they will do real ML some day and their data job is just temporary...
- mjr00 4y ago> It's similar to data engineers thinking they will do real ML some day and their data job is just temporary... Hah yeah but this is just the reality of ML. "Engineer who only codes up awesome new ML algorithms" isn't a real job. For every 1 person coming up with exciting new algorithms, there's 500 people dealing with data pipelines, cleaning, maintenance, and operations. A while ago I got hired by a large SF tech company as a "machine learning engineer" and my team spent nearly all of their time writing Javascript web wrappers on top of scikitlearn. Thrilling stuff.
- Ragingweb 4y agoI built my career as a software engineer exactly like this. Learned all the pain points in mid corps/ corps and went on taking work in the "gutter". On call, learning rare languages (like COBOL), or unusual file formats (like AFP) and db admin (oracle especially) are parts of my tool belt to open black boxes and rebuild or refactor. But as mentioned before, this kind of work pays if you're freelancing, not as an employee, since you rarely get any kind of advance if you are providing meaningful groundwork. But you also need a lot of soft skills to be able to get information to provide the work, unentangle a spaghetti mess or simply get access to a specific server or codebase.
- Tade0 4y agoI would be careful with such statements. Some years ago I figured it would be a good idea to specialize in converting Angular 1.x applications to Angular 2+ - considering the former was supposed to be sunset eventually and nobody wanted to touch this with a ten foot pole this sounded like a good plan. Bottom line is: garbage projects attract garbage management practices. Projects I worked on in no particular order: I: 1. I fix some longstanding bugs. 2. Client is happy and wants more. 3. Client gets back to us with new stuff and imposes a non-negotiable deadline because the marketing campaign already went. II. Contract in Switzerland. Financially very good, but the company that sent me there didn't manage to figure out our accommodation, among other things. I lost 5kg due to malnutrition because I had to figure out my housing situation by myself. Also COVID put a wrench in those plans. III. Random offer that matched my experience. Wasn't too bad until I found that the client company sees us as first and foremost "a cost" and won't bother to keep us updated on important decisions. One key information regarding our deadlines was obtained by our tech lead by accident because he was called to an unrelated meeting.
- TrapLord_Rhodo 4y agowhy are you letting clients impose deadlines? That's your job to tell them.
- Tade0 4y agoNot my call. This was a client of the company I was contracted to at the time. As to why they did this: refer to the "bottom line" section of my previous comment.
- jpollock 4y agoThis does work. At least it works for me. There is a difference between doing a crappy job and solving a crappy problem. This is the difference between "toil" and "eliminating toil". https://sre.google/sre-book/eliminating-toil/ https://sre.google/sre-book/eliminating-toil/ Toil isn't valued very highly. It feels good to do it, but it is fundamentally repetitive make-work. Removing the work is where the value is. The value is in scaling yourself, allowing your employer to see productivity improvements, and get more out of the same staff. The value is in helping your employer climb "Charette’s Risk Escalator".
- bitL 4y agoDirty work often leads to burnout, which is a career killer, so please don't build your career just on dirty work.
- wnolens 4y agoThe right advice for the beginning of your career. But a recipe for being stuck at SDE2 unless you move towards high visibility work with a more direct line to new revenue (not just reducing costs)
- fanuelworku 4y ago
- fanuelworku 4y ago
- SamPatt 4y agoGood piece overall, but "only boring people are bored" isn't true when talking about their jobs. Especially when you're doing work beneath your ability, it can be boring and there's no reason to pretend otherwise. Your spare time is a different story.
- whatarethembits 4y agoI actually like this kind of work sometimes, I can get it done quickly and work on my own projects or learn something new with extra time
- hilariouswhip 4y ago> Trotsky later claimed that Stalin amassed power as a bureaucratic mediocrity, but it was actually Yakov Sverdlov, assisted by Elena Stasova, who ran the Party machine. Stalin was not a born bureaucrat at all. He was a hard worker utterly dedicated to politics; indeed everything with Stalin was political, but he worked in an eccentric, structureless, unbureaucratic, almost bohemian, style that would not have succeeded in any other government, then or now. Lenin’s trust was won in the bank robberies and intrigues of the early years and, later, on the battlefields of the Civil War: Stalin was hardly in his office before 1920. Young Stalin
- WastingMyTime89 4y agoThere is no secret recipe to career building. You can do great doing dirty work. You can end up nowhere working on trendy things. It's all about rebounding and using what you have learned to move forward. The most impactful thing I have ever done for my own career is having an idea of what I wanted for an horizon a bit longer than just my next job and being very open about it. There are plenty of people around you who have vested interest into helping you and can't if they don't know what you are looking for.
- black_13 4y ago
- deleted 4y ago[deleted]
- semireg 4y agoColonoscopies. I build the software equivalent of colonoscopies. Everyone needs it at some point. Everyone hates it. When it’s done you want to forget about it. Until next time … My nasty niche is label printer software. If I search my support tickets for “love” it’s mentioned in a ticket almost every day. That’s how much people hate label printing. Not shipping labels. I’m writing about custom labels, spreadsheets, date formatting, dynamic hide and show of text, swapping images, auto-shrinking text. The stuff of nightmares. People love an elegant solution, and they are willing to pay for it. God bless the rear end of hardware!
- lmeyerov 4y agoConversely, I think this is one of the best ways to come up with startup ideas. Learn intimately why dirty work is the way it is, figure out sw to solve it internally, and once that works pretty well... replicate externally. RE:Folks discussing limited career growth, if in a startup that's growing vs stagnant, these kinds of areas will likely be one of the areas will need more people+leadership as the company grows. Let's say you automate half your work but then the company has 5X growth. Before they'd need 5X more of you, though now the company "just" needs 2.5X of you. So you still get the ability to hire 1-2 more on your team. And that's just math if you're purely a cost center vs revenue driver. If you actually can help drive customer growth etc with your team, even more growth to be expected.
- rubicks 4y agoI did this. I'm paid well. I also catch all the Hell Tickets. It works for me.
- keithalewis 4y agoJust be sure to sit on their porch after you do it.
- throwawaydfg 4y ago
- dev_0 4y agoIs Security a dirty work?
- kthejoker2 4y agoThere's an old corporate haha only serious saying, "If you want something done, give it to the busiest person you know." Walk into any startup or 2 pizza team and ask who does the dirty work, there's always someone. The question is why is it someone instead of everyone? It's because enjoying doing dirty work requires certain personality traits, and two of those traits (people pleasers and inability to delegate) ensure the dirty work is forever diverted in one direction. No comment on whether careers are built on such things.
- iamcrazyyounus 4y agoDirty work will help you burn out. I actually enjoy this type of work because I can complete it quickly and use the extra time to work on my own projects or learn something new.
- scarface74 4y agoThis is some of the worse advice I’ve seen on HN in a long time. The type of work the author is recommending will at most keep you middling along in your career. If you do ever want to get BigTech compensation they want you to be able to show “scope” and “impact” at anything beyond a Level 2 engineer. They also expect you to have some system design chops.
- angarg12 4y agoI like the take that "dirty work" might be unexplored space where impactful, relatively unexplored work can be done. However I reject the notion that simply doing dirty work will help you to advance your career. Since the author says this has worked for them, let me give a counterexample: when I was a start-eyed new joinee in my current company, I was always down to do dirty work. Are builds broken? lets fix them. Do we have open tickets? Let's resolve them. Of course I also took it a step further. I wrote a proposal to untangle the ungodly mess that our builds had become and keep them good moving forward. I asked my manager to let me run an experiment fixing customer issues, and I did a writeup with my findings (positives) and recommendations moving forward. This attitude had two unintended consequences. First, the rest of the team stopped doing dirty tasks altogether. Hey, why fix the build or this flaky test? angarg12 will take care of it. I influenced the team's attitude, but in the opposite direction than intended. Second, when I started to have conversations about promotion, all of this work didn't matter. I wasn't ready because I didn't have 'enough impact' or 'enough scope'. My documents went unread, my recommendations ignored. So if career progression is your upmost priority, first understand well what your company values, and if/how dirty work connects with that.
- haspok 4y ago> all of this work didn't matter Sorry to say this, but sometimes this is just true. As a newbie it is easy to think that a state of no bugs, no open tickets and 100% documentation and test coverage are the most valuable things a development team can strive for. But this is rarely the case. In most cases, it is just not worth it. Developer time might be better spent elsewhere. Just because a work is dirty it does not make it automatically valuable.
- cafed00d 4y ago> The Dirty Work Theory: The lamentable work that many people avoid are great places to look for high impact, low hanging fruit. One person's KTLO is another person's promo project. It's fascinating how much a project can be glorified in one-company and is dismissed at another. I had the (not necessarily thaaatt) strange path of working at Amazon to going to work at Siri/Apple. When I was at Amazon, "client" work was not sexy; rather sharding a database is what all the magic-makers did. So, as a newly hired Java/Backend engineer at Siri, my first project, which I pitched for, was sharding our database for operational efficiency. Yay! Win! But, after about a year of that work, my manager (who's happy with my work) says ".. to get you promoted, let's get you on some more customer impactful work, where we can get you to demo some user facing features...". So, I dive head-first into the challenge on learning Swift/iOS stack and accelerate our team's services to run on-device; winner-winner-promotion-dinner! Nobody at Siri wanted to touch the old server code. All the glory of WWDC+features+new_device_handouts were going to the folks working on client. The senior engineers who'd been around for decades across the industry were working on the client. They'd still fix server bugs nobody else could handle though. At Amazon, all the rockstar sr engineers had worked on services/distributed-systems for decades. But yeah, senior engineers (rockstars or otherwise) don't stick around at Amazon. They tend to leave after 2 years; weird. That 18th month at Apple was the biggest learning so far in my career: someone's view of a KTLO project is another person's view of doing god's glorious work.
- tpoacher 4y ago"Most advice is basically people mistaking correlation for causation." ~ Leo Polovets (some datascience guy on twitter)
- beginnerZ 4y agothanks,the article is helpful for me
- chester_the_dog 4y agoThis strategy can lead to career stagnation. Good software engineers should be willing to accept unpleasant assignments, like analyzing and fixing bugs under pressure. Fixing bugs in other people’s code be difficult and stressful, especially if there is a critical failure in code that is already in production. If you are consistently being asked to perform emergency fixes on code you did not write, then the company has a big problem. If management doesn’t have a plan to fix the fundamental problems then you should find a new job, or you will wake up one day and realize that you just spent the last three years fixing other people’s mistakes.
- chester_the_dog 4y agoYou don't get to be head chef by being the best dishwasher.