22 ms·
Hard-to-swallow truths they won't tell you about software engineer job
- konschubert 3y agoMeh. It's not that bad. Legacy codebases can be fun. If you have a good team, your meetings will be meaningful or you will cut them.
- shmde 3y ago> Legacy codebases can be fun. "Legacy codebases" and "fun" should not appear in the same sentence.
- wrzuteczka 3y agoDiscovering how a large system works can be fun. Even if a codebase is old, but the design is good, it can be gratifying.
- wkjagt 3y agoI've always liked working in legacy code bases. It's like doing archeology. Seemingly bad code maybe didn't start out as bad code, but was made bad over time because of historical reasons (last minute product changes, time pressure, local changes without understanding the bigger picture). It can be very rewarding to make sense of it. And it makes you realize that any code you write yourself will be legacy code soon too, and someone else will need to be able to make sense of it again.
- supriyo-biswas 3y agoIt depends. The thing about inheriting an older, undocumented codebase is that it often blows up in ways that you least expect; even drawing assumptions about how a function works based on its name can be problematic.
- Tainnor 3y agoOr when you remove some "unused" code, only to find out that it was somehow used by reflection and your IDE can't even figure that out because the framework you're using was discontinued in 2010. Also of course, there's no test for that.
- konschubert 3y agoSometimes bad develops wrote bad code, but with a good team, you can do a fun cleanup! It’s all about the team.
- kagakuninja 3y agoI've worked on plenty of legacy code over 37 years. It all depends on the management environment and how bad the code is. Sometimes legacy code is like being mired in quicksand.
- toast0 3y agoLegacy in business just means it's a real product/process that has customers and/or makes an important output. Otherwise, if people didn't like it for whatever reason, they could just stop doing it. It's great to be working on something that's useful and important.
- Tao3300 3y agoYeah, a lot of greenfield projects fail, and the road to that failure is fraught with pain and burnout. Cities are legacy projects, colonies are greenfield. Both have their pros and cons.
- Ocerge 3y agoI've grown to appreciate legacy code more than greenfield. It's real code that makes money (hopefully) and solves problems. Code is bad? Well, it's probably for good reason as real-world problems are messy. Also a lot less analysis by paralysis.
- atleastoptimal 3y agoThe rate at which this stuff happens is proportional to the average age of employees at the company
- nik736 3y agoThis is exactly what I noticed as well.
- ilikerashers 3y agoI always refer to this paper when I think about advising graduates: https://blog.pragmaticengineer.com/software-engineering-salaries-in-the-netherlands-and-europe/ https://blog.pragmaticengineer.com/software-engineering-sala... There are different problems in different orgs with different value adds. You can be super busy firefighting for a company that doesn't value your work or calm, well-paid but unchallenged in another. Also the same general pattern of learn -> earn -> own applies in tech. Learn your trade, milk it for a number of years to setup your life, own your own consultancy/company.
- yodsanklai 3y agoSome truth but this seriously lacks nuance. Not all colleges or companies are equal.
- osullip 3y agoOverall, I think this article is good. I've been in the game a long time and there is not much here I would disagree with. "Working in software engineering often means long working hours. Most of the time, you are glued to a computer screen, with little work-life balance." For sure this is true. The younger you are, the easier it is to deal with and be amazingly productive. As you get older, life creeps back in and you get a bit of balance. When you get to my age it becomes less about screentime and more about problem solving. Something I am very happy about. As a career, it's 8 out of 10.
- gipp 3y agoEh that's one of the least universal ones in there. I've worked in tech for a decade now across 6 positions in 4 companies and I have never had any complaints about WLB. If anything, I frequently feel like I'm getting away with something when it comes to how little I can actually get by with doing if I want to.
- donatj 3y ago> College will not prepare you for the job I'm on the fence. Not initially, sure. But there are embedded lessons that click later. I was ten years into my career before I needed to write a b-tree or a double ended linked list, but when the need arose I was very grateful for having the ability to recognize it, and the familiarity to act on it. Some things I learned such as the wonderful value of pure functions just didn't click for about as long. I'd done a ton of Scheme in College and at the time it was nothing but a frustration "Just let me mutate state, this is dumb" it wasn't until I had years of tracking down what the heck was mutating state in a giant old code base that I learned to appreciate functional programming.
- Manfred 3y agoIt's also very valuable to have a shared frame of reference with colleagues so you can communicate more efficiently. Saying things like "this is like backpressure" instead of having to explain the entire concept is very valuable.
- throw555chip 3y agoI'm not degreed, been working with and for PhD's, people with and without degrees for 3 decades including several stints at valley startups and never heard anyone use the term backpressure outside of a mechanical engineering context.
- Manfred 3y agoIt's a term in queuing theory: https://en.wikipedia.org/wiki/Backpressure_routing https://en.wikipedia.org/wiki/Backpressure_routing
- mordae 3y agoDo you need college for that, though? I don't have one and still know how to implement a double-linked list, trees, tries, hash maps and what to test for when implementing binary search[^1]. Just keep your eyes open. [^1]: https://blog.research.google/2006/06/extra-extra-read-all-about-it-nearly.html https://blog.research.google/2006/06/extra-extra-read-all-ab... If anything, I miss the linear algebra drills the most.
- franze 3y agoYou do not create clean code for others, you create it for your future self. And he/she will appreciate it.
- 0xfab1 3y agoFuture maintainers, who could be you. It has happened to me a few times, and I thanked my past self every time. It doesn't even have to be clean code. Sometimes I'll even settle for understandable code. In my experience, however, few people care about this. My most common comment in code review is "add doc" or "add explanation"
- m000 3y agoTrue. But you should also write it for your fellow developers/engineers. If the culture among engineers in your job discounts the value of clean code, you're probably entering a world of pain. Sure, you should not obsess over clean code, as it does not directly produce value. You should also not expect your manager to understand its value. But if your fellow engineers frown upon efforts to improve code quality, start looking for your next job. The mental drain is just not worth it. Esentially, where the clean code is appreciated, mediocre engineers/developers will eventualy acquire "guru" status, just because they happened to be hired a year or two earlier than the better ones. And will often be unfriendly to anyone "threatening" their status.
- Gazoo101 3y agoWithout knowing the exact expectations of the people the author spoke to, I'd imagine lots of the misconceptions are on-point. One personal exception for me was how university (not college) prepared me for my future in software engineering. The courses I took quite often involved group projects of 2-3 people completing work cooperatively. Undoubtedly this was - by far - one of the best and closest to real-work experiences I had during my earlier education. Compromise, discussion, division of labor, and a healthy bit of experience with individuals who'd prefer to be part of the project credits but ideally do as little of the work as possible.
- fjfaase 3y agoAfter being a software engineer for over 30 year, I agree with all the points. I have come to the conclusion that being a software engineer is one of the hardest jobs. Also because your often confronted with your weaknesses. But that also gives you room to grow. I also have come to realize that being a software engineer, changes how you view the world, because it forces you to think deeper about problems. The problems behind the problems. In sense that alienates you from all those people who do not have to deal with hard problems, are not used to think deeply about problems. And there are a lot of those kind of people in the world, at least a lot that use their voice. But in the end, I never regret becoming a software engineer, and I also realized that it has profoundly shaped who I have become.
- bashwizard 3y agoAnd then you switch to security from being a developer and the imposter syndrome hits you in the face like a truck and you'll realize how easy it was being a developer.
- workfromspace 3y agoAs a person who recently did this, I am greatly interested in hearing more on this subject from you (or anyone else).
- s5300 3y ago[dead]
- dudul 3y ago> software engineer is one of the hardest jobs. I chuckled. How can someone write this with a straight face?
- francisofascii 3y agoIf you think it is easy, it is because you have a talent for it and have years of experiance. People who are mental health professionals, teachers, doctors, CEOs, all have what I consider harder jobs, but do you think they would want to switch places and be a software developer 40 hours a week? They would think it is too hard.
- askonomm 3y agoThis actually describes the job pretty well in my opinion, as someone who has been in this field for over a decade now. Not everybody is cut out to be a software engineer, and the "day in the life of" youtube videos where they never do any work and just eat all day of free food and socialize just paint an inaccurate picture of reality, making the job seem a lot more glamorous and easy than it is.
- tomaytotomato 3y agoI generally find I write perfect clean code in my own personal projects, however at work my colleagues keep complaining about it ;)
- bradfa 3y agoYou will almost certainly experience a layoff in your first few years of post-college work. You may or may not be affected directly by the layoff, but either way your first layoff experience makes an impact on you. You will watch others around you who may have even been great at their jobs lose their jobs for no fault of their own. It sucks. When a layoff happens to/around you, TALK ABOUT IT WITH YOUR PEERS! Every one of your peers will be having feelings. Engineers are not good at talking about feelings. But OMFG seriously, when that first layoff happens just drop everything you're doing, grab a pile of people you work with and go out for a long lunch right away and then talk about wtf just happened. It makes the situation less bad and will help you get back to being productive much quicker. Your boss won't mind, and if they do, they're a horrible person.
- LoganDark 3y ago> if they do, they're a horrible person Very bad gamble if you need the job and a bunch of people just got laid off. If you can afford to move jobs, you would have done it already after the layoff.
- bradfa 3y agoMy first internship in college, on my last week, my entire organization got laid off. We all went out to lunch at 9am, none of the engineers went back to the office that day. My first job after college, I was there for 6 years, we had I think, 11 layoffs in organizations I worked in, the first one was less than 6 months after I joined. My 3rd job after college, I was there for 5 years, we had at least 3 different layoffs. In all cases the managers were completely understanding about the mental impact of the layoffs, both for those directly affected and those who kept their jobs and would need to pick up the work of the departing. Never once did I see a manager expect any work to be done the rest of that day after a layoff was announced. If you ever work for a manager who isn't compassionate during a layoff, I'm sorry, that sucks.
- LoganDark 3y agoI don't think I'll ever have the privilege of working for a manager. Getting a job in the first place is actually the hardest job of them all, even in the US.
- Tknl 3y agoI think the point with regards to clean code is somewhat changing. As companies and their clients adopt process certifications such as ISAE, static code analysis reporting is slowly becoming a requirement for the release process, driving measured code quality improvement and directly tying it to business outcomes. I feel like some other points are also less severe in technology oriented companies focused on cloud native, continuous delivery and that manage based on the DORA metrics.
- geraldwhen 3y agoIt is extremely easy to disconnect from work. Turn off your laptop and live your life. I find that those who are chronic workers have very little going for them in their personal lives. I challenge everyone who feels overworked to work 1 hour less this week, then an extra 1 hour next week. See how far you can go before anyone even notices or cares. It’s farther than you think.
- gopher2000 3y ago> It is extremely easy to disconnect from work. Clearly that's not the case for everybody. Don't assume that your reality - and what works for you - is universal truth.
- bigstrat2003 3y agoConsidering that the author of TFA assumed (wrongly) that his inability to disconnect from work is a universal problem, I don't think it's fair to criticize the comments here for just following his example.
- dools 3y ago> I find that those who are chronic workers have very little going for them in their personal lives. Yeah having kids fixed that for me
- fjfaase 3y agoI often find myself at totally random moments thinking about problems related to work. It is often at times that I have been away from the laptop, that solutions pop-up in my mind, for a nasty problem. Often it is form of attacking a problem from a different direction. For me turning of my work laptop is not enough to disconnect from work. Most of the thinks that I worry about while being at home are not about technical aspects but about non-technical aspects of the job: dealing with managers, colleagues, and project organisation.
- martinclayton 3y agoSame here. I have no trouble "closing the laptop", but I can't stop my mind from problem solving. Fortunately for me I don't have any of the "soft" concerns you mention. The practical side is clear: close the laptop. But on the mental side I do wonder where the right balance is. I've recently started to forget about work at the weekends to the extent that - usually late on a Sunday - I suddenly remember I have to be at work the next day, which is an odd sensation. Probably just getting old(er).
- guappa 3y agoOnce a coworker spent 4 weeks arguing with me that his code was fine because "the test was green" before I touched it. The test contained a "return true" before the actual test. After writing countless emails to convince him to fix his code, and wondering why they wouldn't just fire him and save everyone else some time, the CTO announced that the guy was now promoted to team lead. :) His code is not elegant, it barely works, requires constant full rewrites, is an endless source of segmentation faults, deadlocks, sleep() in the main thread and whatnot. The only skill you need to get promoted is to laugh at the jokes of your boss and schedule meetings to demo your n-th rewrite of the same thing. Estimates are important. I've overheard a team lead claiming they are completely impossible. How long does it take you to go to the store? Yes you might die in the process and take ∞ time, but one normally considers common inconveniences in this. A senior who can't estimate isn't a senior. Of course at work I've heard a team lead say "I did my part, I have no idea when they will implement it" (not the same team lead I mentioned before). > It will be almost impossible to disconnect from your job I learnt that very early on. In my first full time job, my boss got mad at me for arriving at the office at 9:05, unacceptably late. So precisely when my hours were done I'd stand up and leave. > talk directly to them, be professional but not mean, and tell them what and how they can improve And then get reported to HR… my advice is to be the 1st one to do the backstabbing and complain that it is impossible to work with them. > Get used to being in meetings for hours Working from home helps… one can cook and build lego during meetings.
- siva7 3y agoRemember Rule 10: Soft skills over technical skills. I'm sure the team lead has some qualities.
- chasd00 3y agoI told a guy I mentor this once. You can make a career out of only knowing the right people and you can make a career out of only knowing the right things. The situation you want to be in though is knowing the right people AND knowing the right things. That’s where the real money is.
- guappa 3y ago
- nicexe 3y agoI mostly agree with the points but I hard disagree with point number 3. Clean code makes the project more easily maintainable. We generally try to keep a standard in code quality (and I would say 98% of the codebase we touch is well written). We also try to schedule refactoring rounds (but that doesn't always happen because of time constraints).
- Clubber 3y agoHe didn't say clean code was bad, he said nobody cares about your clean code. I assume he meant outside the development department.
- sanderjd 3y agoThat isn't true either though. Sure, they don't care about it as a first order thing, but they care about development not slowly grinding to a halt over time. And writing well structured code is one of the things the software side of the house does in order to do a better job delivering on that desire from the business. If nobody on the technical side has the credibility or trust to make that case, then that's a problem.
- Clubber 3y ago>Sure, they don't care about it as a first order thing, but they care about development not slowly grinding to a halt over time. Most only care when it affects them or sales, not when devs are asking to allot time to clean up code or pushing off a release to fix wonky stuff. In my mind that's not caring. That's like people care that they can't walk up stairs without huffing and puffing, but not enough to actually diet and exercise. That's not actually caring, that's really regret. I'm fortunate though, my company gives a lot of credence to dev.
- sanderjd 3y agoThat situation sounds to me like the problem of the development org not being trusted by the company's leadership when they say "this will slow down short-term initiatives but speed up long-term ones".
- gumballindie 3y ago> Meetings are an important part of the software development job. Imagine the folks building the Linux kernel or other popular, successul, and mission critical software projects sitting in meetings all day long. I genuinely think that meetings are the only way management can justify their existance and therefore commercial projects consider them as an "important part".
- pjc50 3y ago> Imagine the folks building the Linux kernel or other popular, successul, and mission critical software projects sitting in meetings all day long What do you think LKML is? It's a big continuous asynchronous meeting.
- yakubin 3y ago"asynchronous meeting" is an oxymoron.
- gumballindie 3y agoI suppose if we redefine words everything is everything.
- siva7 3y ago>> I genuinely think that meetings are the only way management can justify their existance and therefore commercial projects consider them as an "important part". reply Wait until you join management at some point in your career.
- gumballindie 3y agoI did. And held few and to the point meetings. I could see how non technical managers were struggling, and that’s how i know that some are simply clueless and serve no purpose within orgs. I managed a somewhat small number of devs - roughly 40, some distributed.
- quietbritishjim 3y ago> There are a lot of formulas on how to do estimates, and everyone has their own rules. I also have my own rules. The actual way to produce estimates can be found in the excellent book Thinking Fast and Slow by Daniel Kahneman: you have to consider a previous project (or, better, several of them) of roughly similar in size and scope, and use that as an anchor for this estimate. You're allowed to add or remove a bit because of a slight difference in complexity. But the golden rule is never to say that this other project doesn't count because, although it seemed similar at the start, it encountered unexpected problems. That's the whole point! If you haven't worked on a project that large (or kept good enough notes about how long it took), well, tough luck, you can't produce an estimate, any more than someone who doesn't know any software dev at all can. Looking back at a project with this in mind I was surprised to find the distribution of subtasks (into 3 big buckets of "main complex logic", "simple GUI", "reports/presentations") was roughly equal rather than about 80% on the first one as I suspected. There's no way a rule like "add 40%" can help you with something like that. The book discusses a great example where they were preparing a university syllabus to teach various biases, including the underestimate bias and this very technique to avoid it, and they still underestimated how long it would take to prepare the course (even after being given information about how long previous courses took to prepare!).
- kqr 3y agoAnother recommendation in the same vein is How To Measure Anything by Douglas Hubbard. And Superforecasting by Tetlock. Estimation/forecasting (same thing different emphasis) is a problem we know quite a lot about, and we know how to train people to issue calibrated estimations. The first step to learning anything is figuring out how to get feedback on your performance. For estimation, probabilistic estimations are the way: https://two-wrongs.com/verifiable-software-development-estimations.html https://two-wrongs.com/verifiable-software-development-estim...
- ClumsyPilot 3y agoThese aren't hard to swallow at all - how about this: Good requirements do not exist - Writing good requirements is months of work -you have to interview business stake holders, ask challanging questions, you ahve to involve industry experts and have developers think, not code. Its safe to say this almost never happens. Agile is an insidious ruse - its popular because it frees management from having to commit to planning and discovering requirements. However management still expects engineers to provide them outputs of waterfall - accurate estimates, architecture, etc. CV driven Architecture is common Engineers have a complexity addiction and feel inadequate and impotent if they are 'just building' something simple. So simple projects get bloated to inckude Kafka, kubernetes or some other buzzword of the year. Instead of discussing business problems and missing requirements, engineers prefer to discuss technical complexity. So they often commit to adding technical complexity before they've understood business complexity. Then when they hit business conolexity, they have no mental capscity or bandwidth left to address it Communication between business and Eng is usually broken To arrive at good design decisions, one person needs to have great understanding of business and technology. In most projects, this person does not exist. Design is riddled with qeustions like 'Do we really need to have feature X, it doubles complexity but only 5% of users would even care". To even understand that, business needs to communicate commercial information to developers, or developers have to educate business. This rarely happens, and so these decisions are usually not even identified
- rob74 3y agoThe point about "incompetent people" is a bit harsh. "Competence" is rarely boolean - some people are smarter, some are less smart, but may have other qualities (e.g. being more thorough), some may not be that familiar with a certain technology etc.; that code you have to work on may look the way it looks because it had to be adapted several times to changing requirements without enough time to refactor it properly, not because the person who wrote it was incompetent. There are already enough young developers leaving university full of self-confidence thinking they are God's gift to the job market, so maybe a word or two about giving people the benefit of doubt before classifying them as incompetent is in order. That's not to say there aren't really incompetent people, but you should avoid jumping to conclusions too early...
- quietbritishjim 3y agoMaybe, but the people I have worked with have been pretty heavily bimodal, especially by the senior level - many people in the "competent" bucket varied a bit but generally produced workable code (maintainable as well as works now). But there is a distinct class of senior engineer that produces awful code that is hopeless to work with later. Most frustratingly, it does actually work for the current task so those outside the system will only see problems with the later devs to work on it.
- Aeolun 3y ago> But there is a distinct class of senior engineer that produces awful code that is hopeless to work with later The longer I work on stuff the more I worry this is me. I thought it was the code coming before me, but the code after seems just as error prone.
- BigJono 3y agoThere's a really easy way to tell. If I say something like "I've got my sales history in a database and need to graph how many widgets I've sold over time", do you start thinking about concepts and code, or do you start drooling and typing "npm database npm graph npm widget..."?
- pjc50 3y agoIn the words of Terry Pratchett, "It’s indoor work with no heavy lifting". And it pays astonishingly well. Which are useful things to remember when it sucks a bit.
- Clubber 3y agoA mentor once told me, "If you get frustrated, just go to the bathroom. When you are done, remind yourself you just got paid $10 to take a poo."
- bsenftner 3y agoThe last point is the most important one, last of course, as our industry does not respect communications, despite it being the main cause of all our irrational management deadline issues.
- r366y6 3y agoI couldn't agree more with this list. While I was at university,I used to imagine software engineering job like a place where like minded people talked all the time about algorithms,new technologies etc. A place where senior engineers would guide/mentor you, where you could take time to create the best code/solutions... :D For me, discovering that soft skills often are more valuable than tech skills was a huge wake up call.
- moffkalast 3y agoWell it is kinda like that, if you have a software engineering job at a university lab haha. But even there there's usually heavy politics.
- skeedle 3y agoThe points in this article match what's in the book "Poems for Software Developers". https://www.amazon.com/dp/B0CMNR4G39 https://www.amazon.com/dp/B0CMNR4G39 Like the article says, you'll probably not get a greenfield projects, you are going to spend a lot of times in meetings, and you aren't going to just be left alone to code. You will have to work with people on a team. Knowing the technical aspects of programming is one challenge, but another challenge is coordinating the effort of developers to drive to a goal, on time, and according to requirements. That coordination effort is a lot of what the experience working as a software developer is all about.
- deniscepko2 3y agoMostly agree, but i think the more seniority you get in your company the less you will deal with these issues and of course changing jobs helps. So basically you might encounter all of these but not necessarily. And starting from scratch and college is basically the same point
- onetimeuse92304 3y ago11. Perception is reality. Ideas mean nothing if you can't sell them. Providing actual value to the company means nothing if you can't sell it. You will work with people who cause more damage to the company than they bring benefit but are good at selling it. It does not matter what you think about what you are doing, it only matters what other people think. If you can be good technically and be a good communicator, the world is your oyster. 12. Most developers are very wrong about what would bring value to their managers. If you think you are underappreciated for your good work, there might be potentially very simple things that you could change that you aren't aware that could make you much more successful. Your manager might care less about how elegant your solution is but might remember you were two days late with it because he had to explain to his boss why the entire feature got delayed. Every situation is different and there is nobody on your team to help you -- you are responsible for reading the situation and making what is important. -- And regarding: > 10) You will profit more from good soft skills than from good technical skills I would add more. You will profit more from learning an orthogonal skill or field. You can be good developer by just being able to gather requirements and implement them. But you can be extremely valuable, sought after specialist if you know how to do those things AND ALSO know some other field not commonly considered by developers.
- Aeolun 3y agoIn regards to 12, there is a really good article out there somewhere about doing what makes your manager happy, not doing what he asks you to do.
- onetimeuse92304 3y agoOh, agreed on that. I would say doing what your manager needs rather than what he/she asks you to do is a senior-level trick. You need to be experienced to be able to pull it off successfully.
- ibejoeb 3y agoAbsolutely. Become and expert in something, and then make software to solve problems in that domain. That's how you get rich.
- Tade0 3y agoI think college prepared me for some of those things. Group projects were a standard thing throughout most of my time there and they introduce you to the messiness of teamwork. I still recall one semester during which I was in two group projects with another guy and we negotiated who'll be slacking off and who pulling their weight in each of them so that everyone passes. One friend of mine is still holding a grudge against a mutual friend of ours who was extending the deadlines given to him to deliver his part until it was too late. I got top marks in a project where two guys just took over seeing that me and the forth guy were incompetent. I took one for the team when our lecturer said that he won't be giving top marks to everyone, so we need to decide who loses 20% of their points - I volunteered because I knew he personally disliked my choice of technology (NodeJS - we had complete freedom in that project with regards to platform/language) and I just needed to pass. Overall a learning experience.
- baz00 3y agoI'd just like to comment on these points on a 30 year perspective... Point 4 - incompetent people. They are great. When they fuck up, which they do often, you can save the day by simply being average. Just make sure people know that you saved it. Point 5 - meetings are great if remote. You can sit there muted on a zoom call for hours tweaking with your bike or playing games on your other computer. Point 6 - estimates are always wrong so don't put too much effort into it. What people value is how long you spend making up lies so spend some time on it! Point 8 - Uncertainty. Let other people handle that and hang themselves with it. That's what software architects are for. Be there to clean up the mess afterwards or at least complain about it. Point 9 - Eventually you do become able to disconnect from your job. One day the fucks just run out. Embrace that early on and save yourself a lot of stress. Point 10 - The only soft skill is politics. Any sufficiently large organisation employs many politicians. The best way to deal with politicians is analyse the factions and stay neutral. No one can drag you to their side then. There is a missing point though: objective one is getting paid. Anything else is secondary. If they stopped paying you how much of a shit would you give about all the other concerns? There you go now you understand. Nothing matters so don't get too wrapped up in it or upset about it.
- hardware2win 3y ago>Point 5 - meetings are great if remote. You can sit there muted on a zoom call for hours tweaking with your bike or playing games on your other computer. You dont have to tell people about it...
- baz00 3y agoWhat is valued is presence and contributions. That doesn't necessarily require attention for the entire meeting. I'm not going to live forever so I would rather expend that wasted 80% on something that I value. The outcome of the meeting is always the same!
- nextlevelwizard 3y agoSounds like you are part of the problem
- nikolayasdf123 3y agoso true.
- ptero 3y agoWhile many points are true (but IMO not all) I would not see all of them in a negative light. Especially for a new grad just starting in the field. For example, yes, you will likely work with existing codebases, but in most other professions you will work within established constraints, not all of which are fun, etc. On the flip side, a good knowledge of software engineering offers excellent money and opens a lot of doors. Want to live and work in Europe for a few years? Take 3 months (unpaid) off to surf and recharge? Negotiate remote options? A good software engineer is likely to manage those with some negotiation and planning. Not many other professions would allow that today. My 2c.
- mypastself 3y agoThe bullet points in the article are reasonable enough, but almost every explanation is questionable. I’ll just address one. Soft skills are indeed very important, and sometimes more so than technical skills. However: > Technical skills are the ones you can learn easily. With different projects, you can understand a particular programming language. You can learn its syntax, pros and cons. It's just a matter of practice. Technical skills are not just about programming language syntax. I wonder how long the author’s been in the industry (apparently “a lot of years”) or how narrow his role is, that he’s never had to learn completely new concepts or paradigms. And even the soft skills section is bizarre. What can I learn about utilizing my soft skills from the author’s list of all the times they thought a colleague was unhelpful or “toxic”? Weird article.
- demondemidi 3y agoI’d say OP has 5-7 years. Because if you have both soft and technical skills together you stop writing code after about your first decade and start solving much larger problems.
- davewritescode 3y agoThis is bad advice in many organizations. The best architects I've ever worked with were excellent coders and kept up to date with everything even if only 10% of their role involved writing actual code. It's very hard to be a technical leader without credibility.
- atq2119 3y agoIndeed, I see a big difference between developers in my team based on their general reasoning and discrete math skills. How capable are they of abstractly interpreting code in their head? Are they used to thinking about how to prove something is correct? Are they used to thinking in terms of graphs? That sort of thing. Those are technical skills that seem pretty difficult to learn.
- charles_f 3y ago> I wonder how long the author’s been in the industry (apparently “a lot of years”) 8y, most likely including internship. His resume is on the blog. I wondered as well and checked.
- nfRfqX5n 3y agoThis stuff could roughly apply to any job
- kossTKR 3y agoMost problems today stem from scale? A big org of with 100% non technical people and 100% technical people where the sweet spot was the small game studio from 25 years ago, nerds, but social, tightly knit, experts but generalists because of size, close to each other, and pretty small.
- 1270018080 3y agoReads like a chatgpt article. Nothing new or insightful or hard to swallow.
- FranzFerdiNaN 3y ago> You have to put in extra work while you are in college. Code more projects besides homework and seminars. Do some volunteering. Learn about business domains to prepare for the job that awaits you. lol yeah, or you do not do this and just get paid to learn all this shit on the job.
- mberning 3y ago3) People and businesses usually won’t value your “clean code”. 4) You will often work with incompetent people. Especially in larger organizations. Pretty well agree with everything else.
- lnsru 3y agoSounds very nice. Nobody talks, that highly paid jobs attract all levels of psychopaths. And nobody teaches to work with or under them. Then you go into psychogames asking if I am insane or something wrong with this workplace. If you’re lucky - you leave early and healthy. If not - end in some fancy mental health clinic. Already mentioned layoffs. My older colleagues went through these too. But really only when the company was going bankrupt. We have now lifestyle layoff rounds to prepare companies for future challenges. Some dude in completely healthy and profitable company decides to throw away 5% or 7%. Job security is gone. At the end you’re a row in payroll’s excel.
- sergioisidoro 3y ago"Nobody gives a f** about your clean code" Absolutely false. And you'll know this as soon as you need to change or maintain your own code. Even if you're a purely cynical person who does not care about your team members, or the future developers (and you're just optimising for business outcomes) you have the incentive to save yourself a lot of pain, as well as embarrassment when customers ask you for something and you need to say no. I would, at minimum, rephrase that point to "Do clean code for you (and for your colleagues), not for some abstract virtue of writing clean code"
- politelemon 3y agoLooking at the paragraph that follows that headline, they are already making similar points.
- pnut 3y agoA less charitable interpretation is that "Nobody gives a f* about your clean code, because if you're dealing with code, you're a nobody in the business"
- RcouF1uZ4gsC 3y agoThese kind of essays are needlessly negative. In terms of being relatively accessible, well paid, safe, interesting work software engineering is probably one of the best jobs ever in the history of humanity. Yes there are downsides, but IMO they are relatively minor and pretty similar to what people in any other field experience - incompetence from coworkers, office politics, too much time talking and not doing, and the concern for the bottom line of some ideal of perfection or craftsmanship. In addition, for most jobs that require college, what you learn in college is only the foundation and you will need to learn a lot on the job (see for example residency for doctors, flight hours for pilots, clerking for lawyers, etc) In exchange, you get a relatively well paid job that only requires a 4 year degree (if that) to land an entry level job. There is a vast opportunity for increase in pay either through experience or starting your own company. In addition, if you want to start your own company, it is one of the easiest fields with much smaller regulatory and capital requirements compared to almost anything else. It is not just well-paid work, it is interesting work. Lots of people, including me, find software engineering fun and fulfilling. There is just something amazing about creating something cool. Many of us like this so much, we have non-work side programming projects of our own. Software engineering also offers some of the best work-life balance potential of almost any high paying field. And again, compared to other high paying professions, it is much easier to get into. Although people complain about interviews, they are less stressful than trying to get into medical school or law school and there are a lot more entry level programming jobs than medical school and law school headcount. It is also much more accessible than anything in entertainment or media. So in summary, like everything else in life, it is not perfect. However, currently, it is one of the best, most accessible careers, possibly in the history of human civilization.
- djtango 3y agoIn TFA, author uses a swimming analogy and it's alright but for me I find martial arts is the most relatable analogy and so many of Bruce Lee's thoughts are applicable... A lot of what you will learn in a degree is like doing your katas. They're fun to learn but many (if any) of the moves are too situational and abstract that you'll rarely get the chance to apply them. And when you do, you may forget about them in the moment under pressure. But learning those techniques in a safe environment you'll have a chance to develop some finesse and also have good technical foundations. But there's no replacement for actually getting field experience by sparring/fighting. A seasoned brawler/street fighter will seem uncouth and may have some unorthodox habits but they will be more successful in the day to day than most theoreticians who aren't out there applying what they're learning. Some Bruce Lee quotes I like wrt software engineering... Adapt what is useful, reject what is useless, and add what is specifically your own. If you spend too much time thinking about a thing, you’ll never get it done. Before I learned the art, a punch was just a punch, and a kick, just a kick. After I learned the art, a punch was no longer a punch, a kick, no longer a kick. Now that I understand the art, a punch is just a punch and a kick is just a kick
- throw555chip 3y ago> A seasoned brawler/street fighter will seem uncouth and may have some unorthodox habits but they will be more successful in the day to day than most theoreticians who aren't out there applying what they're learning. That reminds me of my favorite Bing Bang Theory scene, on the way to Comic Con their car breaks down. Leonard asks if anyone knows anything about automobile engines. Everyone (theoretical physicists or astrophysicists) raised their hands enthusiastically. Then Leonard asks, OK, does anyone know how to repair an automobile engine? Everyone lowers their hands.
- SlapnutsGT 3y ago9 - I’ve been doing this so long and this gets harder and harder. I’m at the point I’m so severely burned out I’m planning early retirement to get out of this industry all together. For me what makes it even more worse is I didn’t get into this field until I was in my 30s. Beforehand I drove a forklift in a warehouse, I was in the military, then an electrician, and finally a electronics repair tech afterwards. Those fields the disconnect was passive, didn’t even have to think about it. Software you have to jump through mental hoops to remove yourself and that’s just as exhausting as the job itself. I dream of a job working at a garden center or maybe driving a forklift again. This field sucks.
- rubyfan 3y agoI think a lot of this is good advice even for people outside of software engineering.
- lr4444lr 3y agoPretty good piece. All new devs should be lucky if they find an org that is exempt from even 1 or 2 of these problems.
- alkonaut 3y ago> The user doesn't know how the codebase looks Technically true. But the user knows when code is in a poor state. A poor C codebase in a security critical area users will find out about. It will crash, need critically patching all the time etc. If a game engine has a messy code base (Say, they have two slightly different renderering subsystems which makes things clumsy) then people will notice because the games will be late, buggy, cancelled whatever. For most users though it's that the software is slow, costly, buggy, doesn't get new features quickly and so on. And you can't really tell the reason why. But users DO notice it. Managers certainly notice it. Any manager should recognize a situation where you spend 80% of your time on bugs/regressions, while new features get less time, and take much longer than aticipated to implement. And any manager should instantly recognize that this is invariably due to a poor-looking codebase. Not poor communication, not (other than indirectly) because of bad developers, not poor tools, not anything else. Just messy code.
- braza 3y ago> You will rarely get greenfield projects If only I had known that one earlier. I was fortunate enough to work only on greenfield projects for my first fifteen years as a software engineer. However, at some point, I was brought into a brownfield project [1] for maintenance, support, and bug fixes. The difficult part was not related to things like clean code, architecture, and so on, but to the lack of consistent thought processes around the choices made, as well as the fact that there is a lot of tacit knowledge in people's heads that aren't documented, and how arbitrary convoluted things can be, especially if foliks wants to ensure their own employability through manufactured complexity. It took me at least three years to realize that new technology is the exception rather than the rule. [1] - Brownfield project it's something that has something green still but starts to be muddy and swampy.
- Joel_Mckay 3y ago1. Most academic institutions were never intended to subsidize corporate training costs. While this line sometimes gets blurred these days, one must assume you are learning basic skills 80k other people already have. 2. The primary HR issues I’ve seen is a lack of humility, inexperience, and people entering the field for the wrong reasons. Financial motivations are fine and all... but giving a toss about what you do is important in the long term. There is zero correlation between degree level and productivity… Indeed, some kids get by on social media with an army of Googling friends to try and game through challenges (think of a Borg-cube that assimilated a planet of smug morons.) 3. Some people are cultists, and firmly believe success is bestowed on the truly deserving. In some ways they are partially right for a cog-in-a-machine proprietary process position. However, the range of skills needed grow exponentially as the organization shrinks, and rapidly deprecates people not willing to show any initiative. 4. Your work is likely naive garbage at first, and while management doesn’t know any better... your peers do. Expect to be hazed until one can contribute coherent work. Yes, you will be working on projects that match your skill-set, and if you don’t clue in your career will be a short one. 5. Assume you are the dumbest person in the room, and be pleasantly surprised when you are wrong. Some folks have literally met 80k people just like you, and whatever cleverness you think is original... is often just tedium in another perspective. 6. Your loyalty will not be rewarded. The industry will not suddenly develop integrity, but it is rather a personal boundary you choose after seeing peers exploited. Good luck. =)
- kiviuq 3y agono one cares about providing value to users. We could create value without making profits. People care about profits nothing else. So, no I think your sole purpose as an employee is to make other people rich, as in any other profession. But there are worse fates in life than writing code for money.
- ChrisMarshallNY 3y agoWell, I liked they used MonkeyUser comics. I feel those guys "get it." Sort of like a more tech-relevant Dilbert (without the racist screeds). I was a software engineer for a long time, and a "first line" manager, for a long time. Most of the points are correct, but some did not apply, in my company. For one thing, I worked for a Japanese corporation, and clean code was a really big deal to them. I had a project canceled, once; partly because the code wasn't up to snuff. If you work for a Japanese company, get used to meetings. They absolutely love meetings. Especially in-person meetings (rack up those frequent flyer miles!). That said, I really enjoyed the job. It taught me to write Quality code (which means absolutely nothing, for most tech companies), and they treated me and my team with respect. That's not something that you'll get, in most modern tech companies, and it meant a lot to us all.
- justincredible 3y ago[dead]
- esafak 3y agoWhy do they love meetings? I assume you mean managers love it?
- ChrisMarshallNY 3y agoIt's an artifact of their consensus-based decision-making process (they have lots of process). Meetings are a crucial part of obtaining and expressing consensus. It can get pretty crazy, but they get things done. Whenever we look at the way that another culture does stuff (not just other nations -other companies, as well), we tend to look at it through the lens of "That's not something I could do!". We need to remember that their culture is acclimated to doing things the way they do it; for better or for worse. They actually can have a difficult time, adjusting to the way we do things in the US. We had a liaison that wanted to help things be more "agile," so our infrastructure/process guy suggested daily morning standups (you know, informal, 15-minute meetings in the morning). He turned that into once-a-week 1-hour sit-down meetings before lunch on Fridays, with a rigorous format.
- throwaway_08932 3y ago> Sometimes you don't know the whole story. I have seen some cases where a person just can't do their job properly. They are burdened with tons of tasks and doing work for 2 people. Never mind people who are just starting out -- I think many people on HN could really benefit from this perspective.
- jameshart 3y agoSo his ‘downsides’ amount to: 1) you’ll learn more in the first six months than you learned in four years of college 2) you’ll be trusted to contribute to large complex important systems 3) you’ll be measured on your results 4) real ability will help you stand out and succeed 5) you’ll get to collaborate with loads of different people 6) your work will have direct business impact and visibility to senior management 7) you’ll spend most of your time solving hard puzzles 8) you’ll have tons of freedom to define your own path and role and find how to contribute 9) your work will be so compelling your mind will keep working on it after hours 10) the role balances technical and people skills and rewards those who can combine those aspects. > Conclusion > Software development is not a dream job. Speak for yourself. I’m having a blast.
- psiops 3y agoIndeed, reading these hard-to-swallow truths actually restored some excitement about being a dev for me!
- nisa 3y agoI'm with you but it depends on the company - I was responsible to keep it running for the customers and my boss thought it's better to let me churn out useless work that he can bill instead of fixing the issues or simplify the process (at least internally). I even proposed that he can just bill the same or more hours for the customers for me but I need to automate that shit or I'll go insane. Didn't happen. As soon as I realized that I quit but I burned out pretty badly trying to make it work because I liked the team and the product. Be careful and watch out where you spend your energy and time.
- dvcolgan 3y agoI appreciate this positive spin on the list. There is usually a silver lining.
- nunez 3y agoLove this reframing.
- ozim 3y agoI think software development “is not a dream job” as people outside think it is. Most of the time people think you get paid for sitting behind the screen. Which is also true and might be hard for some types of people on its own. But a lot of people don’t want to be measured on results, don’t want to deal with learning new stuff on the job, having responsibility for something complex that might break at any time quite often for reasons totally not in their control. I like my software dev job and I also would not switch but I can see how it is not a dream job.
- jampekka 3y agoI was lucky to figure this out before it was too late. I was studying for CS masters and worked as a software developer for ten or so years from quite a young age and started noticing I hate most of it, and it was just getting worse. I love programming, but vast majority of software development isn't programming even if you work as a "programmer". It's a constant bureaucatic fight with piles of horrible codebases and technologies and bad ideas (that aren't even yours). I switched to academia and now I actually get paid to program. Not ridiculously like most white collars, but still unreasonably. And I don't have to turn into a badly fitting mindless cog for the prime hours of my life.
- greenthrow 3y agoThis is a pretty good article and I suspect a lot of it applies to almost any job. Replace software engineering with accounting or electrical engineering or whatever and it's probably all still true. Working with other people can be difficult, soft skills and kindness are what make it less difficult. Find places where the culture is a good fit for you and where the interviews focus heavily on behavior. Also, work on yourself. There's a lot of toxic attitude in this post and even more so in these comments. Stones and glas houses come to mind. You don't have to be apathetic in response to the realization that politics is a major thing at higher levels in bigger organizations or that estimates will almost always be wrong. That's like not enjoying sunny days because eventually there will be bad weather. Very silly.
- analog31 3y agoThe thing that struck me was that the points would ring true for virtually any profession. Yet most young people migrate the transition into the working world OK, and even thrive. The one unique thing about coding might be the intractable problem of estimation.
- lloeki 3y ago> As in every job, you will sometimes have incompetent people in your environment. Working with them is very frustrating. They waste so much time and create a toxic environment. On top of that, they are extremely unproductive. That is not even the worst case. There are incompetent people out there that look like they are productive. An example: once we had to implement a bridge to an API to some piece of software from some third party vendor that one of our customers used. This started with authentication. Of course they didn't use OAuth or anything like it but their homegrown bastardised version: you authenticate with a username + password - nope, not a refresh token - and it hands you a temporary token that you then use to hit the API until it expires. Of course it didn't hand you expiration time so you'd have to do requests until they failed, at which point you did the login dance to get a new temporary token. Of course it didn't fail with a 403 or any other status code or in-band information you could use: everything failed with a 500 and an empty body. But that's not even the worst part. Of course there was no HTTPS, so everything went in clear over the interwebs. Not to fret, they thought of that: they implemented encryption. Oh, before you ask no they did not use a Authentication header or anything remotely like it, for the login phase they had us pass username+password on a GET request query string, with values encrypted. Of course they did not use anything cryptographically reasonable that you could find off the shelf, instead choosing to shoot themselves in the foot with using the OpenSSL API to come up with their own thing. So they picked the worst possible thing ever, ECB - If you have no idea how bad ECB is, click the following link and let it sink for a moment that you're looking at the ciphertext. https://en.wikipedia.org/wiki/Block_cipher_mode_of_operation#/media/File:Tux_ECB.png https://en.wikipedia.org/wiki/Block_cipher_mode_of_operation... Of course they provided documentation with three code examples (C#, Java, PHP) so as to implement it. Of course each one of these four had gaps covered by the others, yet the overlaps had none of these four things agreeing. Of course the code for the statically typed languages did not even pass the compiler. Of course the code examples were ostensibly copy pasted from StackOverflow, and then further butchered (with localised names). Of course the actual server implementation was a fifth thing that disagreed with the four above. So the easiest way was to "simply" MITM their official Flash client and brute-force-reverse-engineer the payloads, tuning OpenSSL arguments until your code produced the same output as what you intercepted. In a twist of irony, this being ECB helped. And no they did not use anything like public+private keys, DH, or even a PSK, however fancily implemented. See, values were encrypted for every payload, but how do you make the API server understand your first request ever: the login? Of course you would not send the username and password in the clear over the web! So it has to be encrypted! So you encrypt it and stuff it as a value in the query string! But now how does the server which has no idea what the key is can decrypt it? Easy! Base64 the key and pass it as a second query parameter! Now auth is encrypted and the server can decrypt it! To hell with "PS" in "PSK", that's for losers! Of course, somewhere, someone got accolades for having implemented that API in record time complete with full documentation and examples, ready for folks like us to peruse. Of course we had to vigorously defend ourselves for being comparatively unproductive in front of two CEOs (including ours), a CTO, a contractor, and an employee that implementing a client to this API is taking us more than an afternoon, and that, glossing over the details about the fitness of ECB, it was a stupendously pointless loss of everyone's time when the API vendor required us to pass the key in cleartext alongside the encrypted payload, a fact that probably still eludes all of them to this day.
- crabbone 3y agoI don't think the learning how to swim analogy is good. Where I live it's mandatory for children aged 5 and above to take swimming lessons and to test out at some point. So, there's a lot of involvement with this subject. Anyways. Theoretical part helps. Doesn't guarantee that you learn how to swim, but is a necessary component for you to learn well. College CS education is just outright harmful. Not only does it not give you practical knowledge, a lot of what is being taught is outright wrong. If we stretch the allegory of swimming lessons, it would be like if in these lessons, while only teaching the theory, the instructor told you that breathing underwater is possible, if you try hard enough, or that diving and landing flat on your belly is the way to dive. Another aspect that I find really upsetting about college CS education is that it focuses on inconsequential, transient issues, at the same time completely ignoring important ones, and, at the same time, not investing any effort into trying to systematize knowledge. There's very little effort (or non whatsoever) put into building advanced concepts from first principles. Often times links necessary to connect several concepts are missing and the students aren't even told that these concepts are somehow related, or even if they are, then there's "magic" in derivation which is never explained. A typical example would be how in automata theory the course usually ends with building some very simple programs using Turing machine, and the closest next link in understanding programming languages is learning some modern elaborate programming language like C or Python. College CS education is way overdue for a fundamental revision, and I wish CS had its own Bourbaki...
- vegetablepotpie 3y agoGreat list. Ten years in, I have to say I completely disagree with #6 though. My 2c, never give estimates. They are a trap. As a developer, if you give an estimate, it will be questioned, second guessed, and then negotiated down to 1/3rd of its former self. Then when you do the work, it always takes twice as long as your original estimate. The whole dance of estimation only succeeds to indoctrinate developers into the political environment of the organization, it turns developers into mini-managers over their own time and perturbs their productivity. Software engineering as a discipline has to move away from developer estimates. If you’re articulating the work that needs to be done, estimating the work, then doing the work, the only function of your boss is to report on your execution. The demand for developer estimates are a consequence of managers trying to turn themselves into highly paid messengers with no skin in the game. I’ve seen what that does to developers: late hours and weekend work, horrible diet, stress, weight gain, divorces, it’s ugly stuff. Don’t let it happen to you. Have your boss make the estimates. They have access to resources you do not have. They can look at past performance on similar projects, they can look at actuals. That’s their job. They need to do it. If they ask you for an estimate, “how long would it take to do x?” never start by saying “it would take about …”. Ask a question, something like “what do you mean by x?” Or “have you considered y, is that something we should be concerned about?” etc. keep doing that until you’ve gotten your boss to the edge of their knowledge. How they react will be telling. You end up providing more value in the long run because instead of giving your leadership a false sense of security, you’ll be educating them about execution risk and setting your projects up for success by setting up future conversations to be constructive. If you do fall behind, you have ammunition to fall back on in meetings “last month I asked about x, because I was concerned, and now that concern has come up.”
- beardedwalleye 3y ago#2 and #3 are a bit at odds with each other. I certainly get tired of coming back to the same problematic code that's difficult to read and maintain. I appreciate others (and myself) for writing clean code.
- chasd00 3y agoI skimmed the bullets and pretty much agree with all of them. I’ve been doing software dev for 25 years or so so have been around the block a few times. There’s a lot of good to go with the bad though, sometimes you meet incredible people who you just stand in awe of and other times you get to have a huge impact on someone and get to watch them blossom into something great. But yeah, the most painful is you rarely get a greenfield project, most of the time you’re bolting on features to a shotgun shack of a codebase and praying for the best.
- usernamed7 3y ago> sometimes you meet incredible people who you just stand in awe of and other times you get to have a huge impact on someone and get to watch them blossom into something great. i can verify this was my experience at my last startup!
- foobarxyzzy 3y agoI would also add: - stay humble. you are inherently no better than the guy who cleans the floors, even if you are paid more - your benefits package may rise very rapidly but it will hit a plateau unless you begin caring deeply about a domain other than mere software. You will need to start getting serious about something like finance, healthcare, automotive, etc
- BigJono 3y ago> - stay humble. you are inherently no better than the guy who cleans the floors, even if you are paid more The guy that cleans the floors is doing a useful job, and doing a better job of it than I could do. The other programmers on the other hand...
- presentation 3y agoRE estimates it’s not about the time selected, it’s about managing expectations. People need to know what they can expect from others in order to collaborate, the skill is in knowing when and how to communicate in the framework you’re working in, so that everyone you’re working with has reasonable expectations. You can get it wrong plenty so long as you manage people’s expectations well.
- Bluescreenbuddy 3y agoApproachability and emotional intelligence have been two of my greatest weapons in IT, not my technical skills. Humans are and always will be creatures of emotion, not logic. It sounds corny but I usually strive to be the guy people would enjoy having a beer with.
- edw519 3y agoI have another (more fun) way to say almost the same thing as OP: https://eddiots.com/ https://eddiots.com/
- lawgimenez 3y agoMobile development back in 2010-2014 is just full of greenfield projects and I am just so lucky to be part of it. Every month it feels like someone has a great idea of an app. There were no reviews back then in Play Store (formerly named Android Market), same with iOS, app store does not yet had a very strict review.
- moribvndvs 3y agoAlleged Agile purists and Scrum Masters with a MEDIUMTEXT worth of Alliance certifications in their email signature who prattle endlessly about SWAGs, cone of uncertainty, “it’s _just_ an estimation”, tee shirt sizes, etc. will corner you with a demand to give the number of days it will take to do x with no necessary details or requirements, make you play planning poker with some other equally bewildered chump, ignore that and write whatever number they already had in their head into the roadmap which will be several months short of your guestimation, and then chastise you and your team for not delivering what they wanted even sooner than that, and before you’re even done they start “knowledge transfer” and “switching to maintenance mode” so they can whisk you off to another equally fucked project; get ready for it. It’s one big partially dysfunctional cargo cult where your toughest career problems are less frequently technical but political, interpersonal, and organizational.
- justaman 3y agoMBAs and cert-chasers make the worst managers/scrum masters. Give me a former dev who had to code less because they got carpel tunnel or a hacker with only one book on agile methodology any day.
- schoenobates 3y ago> your toughest career problems are less frequently technical but political, interpersonal, and organizational. I feel this statement is spot on.
- exabrial 3y agoI disagree about the clean code. It’s what defines engineering vs ‘mere development’. Spending time on design up front and doing the smallest thing that could possibly work allowed you to move very quickly later. THAT gets noticed by management, and if you preach it long enough they buy in. Clean code is nothing more than just making sure a code base is fully consistent in its structure, self similar, or crystalline in its structure. Basically no cowboys or egos allowed: everyone writes things in the same manner and style, so everyone can understand it. It takes a lot of maturity from devs to do this and a lot of code reviews. I first saw this coding technique on a medical codebase that tested drug interactions, and later on a very much ununamed defense code base. Whatever the standards are ends up being s bit arbitrary, the actual value is ‘everyone does one thing’.
- jelkand 3y agoAre these hard to swallow? It feels like the author is pushing a particular tone when stating facts (with maybe a couple debatable points) that any software engineer would agree with.
- ibejoeb 3y ago>I pause Slack notifications after working hours. I disable them on weekends. "I go home at the end of the day" -2010
- thanatos519 3y agoThis is what makes co-op programs so great! They solve problem 1, allowing you to encounter these truths over time in the real world before you graduate.
- chx 3y ago> College will not prepare you for the job no, it will not, it has a completely different role, the other name "University" gives you a very strong hint about it: what you learn in university is a universal way of thinking, of acquiring knowledge. The dirty secret is it doesn't matter at all whether you learn this by studying human anatomy or the stars blinking above. By the time you leave aside from very basic stuff your specific knowledge will be outdated anyways for multiple reasons. And your assignments are irrelevant to any job you will take, the primary criteria for your teacher when choosing assignments is the ability to grade you fairly and easily on a task with a known complexity. And there's no fast way to do this. We do not know how. There are a few, extremely few people who seem to be born with a mind honed to this but most people are not Terence Tao :D and actually need the five years of university to get there.
- danielovichdk 3y agoI have been doing software professionally for nearly 25 years. Even if the points the author lays out are very true, don't you ever take them in as being true for you. One thing I have learned in all these years is that you can rule your own narrative in your job. And when patient, factual and not backing down when demanding answers on 'why', you will find out fast if you are made for being part of an often labour heavy workforce. Fact is that what the authors lays out, is not at all special to software engineering jobs. All industries are like that. We are not special in any way. And it starts by telling yourself that you are not special, but that you differ yourself by having a qualitative integrity - though that will take many years to get and always be in process.
- red-iron-pine 3y ago> Fact is that what the authors lays out, is not at all special to software engineering jobs. All industries are like that. We are not special in any way. And it starts by telling yourself that you are not special, but that you differ yourself by having a qualitative integrity - though that will take many years to get and always be in process. Aye, a lot of the OP points sound like any white collar job. I've supported OT roles in Aviation and Railroads, and this sounds more or less like any engineering role I've seen.
- awill88 3y agoThere’s some good points on here that I might share with some tutoring students, esp about greenfield and how that’s really a coveted thing in a social setting of engineers. I do think the tone should be worked on so it is less.. bleak. Like, I don’t really remember being nervous about how long something would take me, unless I was concerned it was impossible to do to begin with. I also didn’t have to deal with thinking about the job all the time, because I was doing it, which is a tongue and cheek way of saying if you want to succeed, work life balance might look different to you than to the peer next to you.
- sanderjd 3y agoThe greenfield thing is always funny to me - I really struggle with greenfield projects :) I don't like being faced with a blank page.
- SirMaster 3y agoHmm, Been in software development for 13 years not and I don't really agree with most of these. Maybe it's common, but I'd say certainly not a guarantee.
- beej71 3y agoI had 20 years in industry from tiny startups to megacorps, W2 and contractor. Now I'm an instructor at a state university. So I've seen all sides. :) Re point 1, you'll learn a lot in the first few months in your job. The old adage that you'll learn more in the first 6 months on the job than you did in all of college has been around at least since I graduated nearly 30 years ago, and almost surely existed for decades before that. But you can't spend four years learning to learn and have zero impact from that. If you got through college and the only thing you have to show for it is a diploma, you didn't do it right. The author is correct that it's not everything you need. But it's only four years and it's tough to prepare a student for every single possible work environment on the planet. The only real option is a foundation, and they pick up the rest using their learning skills when they hit real life. Also, re "So don't get overly attached to your clean and elegant code. Focus on shipping the feature on time and bug-free." There's an interplay between all these concepts that I don't think the author acknowledges.
- ConnorMooneyhan 3y agoNot to mention you might have to work on projects that are mostly divorced from programming entirely, like making plugins work together in WordPress.
- redleggedfrog 3y agoI take issue with #3. The clean code is for you. Future you. You will be substantially more productive if your code is clean. You will end up being the "rockstar" (groan) because you can implement 2, 3, 5, 10(!) times faster on your clean code than your peers. I am living proof of this. And then when your managers and company realize you're the cash cow you can ask for absurd raises and get them. You are going to be hard pressed to do this with crappy code bases.
- sanderjd 3y agoNot just future-you, future-everyone-on-the-team. And in my experience it isn't true that nobody in leadership appreciates this. I think it's easy to make the case that it is worth investing today to make it less burdensome for a team in the future, which may or may not contain the current team members, to evolve the software being written in the moment. This makes sense to everyone in a business, because the same is true of any business process. "Clean code" is not the only way to accomplish this; processes and documentation are other things you can do. But I also think it's easy to make the case that writing comprehensible code actually has the best lifetime return on investment. It isn't hard to do - indeed, it's often easier to ship working features with well-structured code, and it requires less future toil than documenting a process that requires working around poorly structured code. But of course often times there is a tipping point where further tinkering with making code "clean" is no longer net positive. But I think codenames that tend toward I dunno, maybe 95% cleanliness provide good value to an organization.
- throw4847285 3y agoDo other careers have such a vast gap between the platonic ideal and the actual lived experience? The way most people talk about software engineering, you'd think they were some kind of open-source warrior building entire applications from scratch when really they're on the Cancel Prime Membership Button Obfuscation Enablement team at Amazon. I think people like to role-play doing the job before it was professionalized because then it sounds less like you're a cog in a machine.
- perlgeek 3y ago> Do other careers have such a vast gap between the platonic ideal and the actual lived experience? In the past few years I've got the impression that when I go to a doctor with a slightly unusual symptom, they are very much lost. It seems the average GP learned a whole lot at University, and 20 years later treats the same 50 common things (colds, cuts, high blood pressure, you name it) and doesn't really remember all the quirky and exciting stuff from uni. I'd guess that the more academic the education is, the more likely you fall into that pattern.
- Balgair 3y agoI've interfaced with a fair few MDs in the US behind the scenes, so to speak. The site nearly every MD in the US uses is called UpToDate: https://www.uptodate.com/login https://www.uptodate.com/login It's not really for laypeople, so you can't poke around in there (check your alumni benefits though, many associations have subscriptions). But, to give you an idea, the site is pretty much a diagnostician. You can just plug in symptoms, patient history and demographics, and it'll give you nearly everything that you need to know. Lots of best practices, research papers, summary papers, testimonials, etc. It's effectively an AI for MDs, and it's good. What I'm trying to say is that your first instinct is correct: The MDs that you're going to really are in fact idiots that can't even be arsed to use a web form.
- buildbot 3y agoNot sure why people are downvoting this - my partner is an MD and uses uptodate literally every few hours, when she's at home - I'm sure it's higher at the hospital/clinic. Some Doctors are checked out/lazy/make assumptions, just like everyone else.
- somsak2 3y ago#10 should be near the top. hugely important
- qez2 3y ago[dead]
- meling 3y agoI think I’m one of those professors that actually do try to stay (somewhat) up to date with what the industry is doing. Sadly, the SE industry in my area (mostly consulting companies) isn’t keeping up to date, so they complain why we don’t teach our students C#.
- neonsunset 3y agoUsing C# is staying up-to-date (because it is by far the best language if you want to be able to go both high and low level with terse syntax, and it runs everywhere too).
- yieldcrv 3y ago> I put quiet hours on my mobile phone for my business emails I just don’t install the email profile on my phone My job can send me a second phone just like they send me a second computer, so I can turn that off too
- perlgeek 3y agoThere's one source of bugs that the author doesn't mention: time, and how our understanding shifts with it. Sometimes the understanding of what a business object (or one of its attributes) represents sometimes shifts, over the course of several years. Sometimes, that shift is suble and easy to miss, like that it used to represent a desired state, and now more often represents an observed state. Sometimes, other ways to manage some objects come about, and of the original use cases of an object or table, only some (formerly niche) use case remains. Sometimes our use of language drifts, for example when a third-party tool is introduced that uses similar but not-quite-identical vocabulary. All of these can lead to formerly correct behavior now being obviously wrong. Sometimes it's hard to remember the context of the original implementation, and you ask yourself why anybody in their right mind would have done what you did back then.
- freeplay 3y agoI've been a SWE for about 10 years. Here's my pros and cons: + Compensation is insane. I don't think there is anything else in the world I am qualified to do that would pay me nearly as much. - Deceptively long hours - Constant deadlines that are often solely dependent on you. If you are at the senior level or higher, there are often features that depend only on you. If you miss a deadline, several people up the chain will most likely know about it. There is no one to share the "shame" with. It's all on you. + Flexible schedule. Every place I've worked has been very accommodating (usually to the point of not caring at all) of family obligations, doc appointments, start time, etc. - Constant objective changes. Speaking from FAANG, things are constantly changing. You could be months into a feature, priorities shift, and they shelf the whole thing. Not to mention the re-orgs. Overall, I feel very fortunate to have this career. I often see folks my age grinding away at some soul sucking job and my gratitude intensifies. However, it's not all sunshine and rainbows. The nap pods and ping pong tables are just a recruiting tool, not part of day to day life.
- throw555chip 3y ago> Compensation is insane. What? > Speaking from FAANG Oh.
- hotnfresh 3y agoComp's not insane in the rest of the industry, but is just about the only non-management route to the 1960s-1990s style middle class that remains. It's a lot of money compared to median income.
- madeofpalk 3y agoEven outside of FAANG the pay is still quite generous, at least from my experience in.... US/AU/UK/etc You get paid so much for relatively so little. Housemate was a chef who's work was so much more demanding physically and worked stupid hours, and was paid a fraction compared to developers.
- throw555chip 3y ago
- netbioserror 3y agoI dodged all of this hard by taking an interview with a smaller engineering-adjacent company. A lot of these points seem like the reality when working at a gigantic conglomerate that doesn't take its software arm very seriously. Mine does because the software analysis is the core product. 1) All of my previous practice and my Master's-level statistics and signals processing prepared me well for this job. 2) Out of the gate, my boss gave me free reign to greenfield replace a lot of old tools. 3) My clean code and the documentation around it is needed, because obfuscated and undocumented code is what previously shot this company in the foot, and is what I was replacing. 4) Everyone in the software part of the company is competent; the only issues come from outside our department. 5) We have one one-hour weekly meeting to talk progress and potentially connect on important points. Everything else we discuss as needed. 6) Estimates are rarely needed because I made the right choice of languages and tools. I can make changes or add features same-day or within a couple days. One longer-term project I'm on has no deadline; it's needed, but not urgently. 7) My choice of language and tools makes bugs easy to track down. Most of my issues are solving for engineering edge cases. 8) Not that I'm always certain, but uncertainty is never really an issue here. 9) I hard disconnect from my job, and my boss wants it that way. Nobody has my email or phone number. When I go home, I go home. 10) I've had soft skills my whole life, so I've never run into that issue. I didn't get the fabled six-figure starting salaries people everywhere seem to be chasing, but I've concluded those aren't truly real and were driven by $2 trillion money-printing valuations. If anyone is curious about my tools, I use Nim to analyze signal data and output analysis and reports; it's a CLI tool that puts out standardized data formats, which can be invoked by server scripts whenever needed. Most of our systems have already been overhauled to use it as the crux of our data analysis. I replaced a lot of old deliberately obfuscated C and PHP.
- taylorbuley 3y ago> It's just an empty protocol to prove their purpose of existence in the company. Sounds like he came from a pretty bad development environment. I am sad to think this is what he communicated to young developers. These meetings can help to surface problems, provide a shared space to refine work as a team, create a plan against available resources... All of this helps developers move faster and ship more frequently.
- wnevets 3y ago> 3) Nobody gives a f** about your clean code #3 should be that your definition of "clean code" is almost certainly wrong.
- booleandilemma 3y agoIf you believe 3 is true, then 7 will be true.
- NewEntryHN 3y agoOP needs to change companies.
- dkarl 3y ago> 3) Nobody gives a f** about your clean code This is true most of the time, but assuming your boss and coworkers are doing their jobs well (which is why it's not true most of the time) people will regularly communicate the things that are helping or hindering in their work. Of course, you might find that your perfectly clean code isn't as helpful as you expected, depending on what you see as "clean." You'll learn that people care about how quickly they can understand and use your code, and whether they can make changes without worrying about breaking things. That's all they care about, and that's what "clean" is supposed to serve and accomplish.
- jebarker 3y ago> whether they can make changes without worrying about breaking things In my experience no coding standards or cleanliness can prevent this. The only sure way is testing on commit/PR. EDIT: A common failure mode I've noticed is that people only test the functionality they've added and not other parts of the system that may be affected.
- dkarl 3y ago> In my experience no coding standards or cleanliness can prevent this. The only sure way is testing on commit/PR. I think that's an issue with how people define "clean." It isn't just about surface aesthetics. Think of a cooking appliance that looks "clean" in its design, that might win a designy design award, but accumulates gunk in hard-to-reach crevices because it was only designed to look clean, not designed to be kept actually clean.
- jebarker 3y agoFair enough - it may be that I've never experienced "real" clean code. But I've worked with many good engineers and seen this problem repeatedly. However, no matter how unclean the code is a rigorous test suite will find many regressions.
- kinonionioa 3y agoA modular architecture will prevent changes to one system from breaking other systems.
- lars512 3y agoThe majority of them are forced by a person who is organizing them because that's the only "work" that that person is doing. This a pretty cynical and unproductive way to think of meetings, management, and the essential task of coordinating people's efforts. Isn't it also your responsibility, increasing with seniority, to make sure that the team's time is used well?
- karmakaze 3y agoI don't consider any of these to be 'facts'--I'll save you the click (unless you're curious): TL;DR 1) College will not prepare you for the job 2) You will rarely get greenfield projects 3) Nobody gives a f*** about your clean code 4) You will sometimes work with incompetent people 5) Get used to being in meetings for hours 6) They will ask you for estimates a lot of times 7) Bugs will be your arch-enemy for life 8) Uncertainty will be your toxic friend 9) It will be almost impossible to disconnect from your job 10) You will profit more from good soft skills than from good technical skills Conclusion: Software development is not a dream job.
- cooljacob204 3y agoHonestly sounds like the author has only worked at toxic places. I can't relate to half his points. Software development certainly is a dream job for me.
- karmakaze 3y agoPersonally this is still my dream job and has been for 40 years. The only one that's had any impact was 'incompetent people' (if they're in charge/lead), in which case I've switched teams or companies. As for (3) or (7) if you value a job well done as do your peers, then it's its own reward and I only care that I'm given (or can make/take) the time to do a better job than management knows is good for the company.
- codr7 3y agoIt's not a bad job if you have what it takes, but the reason we're paid a lot of money is that many couldn't force themselves to do it even if they wanted to. There's a lot of responsibility, uncertainty and frustration. Very often we're doing something that no one did exactly the same way before, which means there are no clear answers and no one to delegate responsibility to. Maybe not so much in a junior position; but the more senior you get, the more of that you'll have to deal with. I agree about soft skills, learning to communicate well and deal with other people is a big part of it. Half the job is really more about diplomacy than technology.
- elteto 3y ago> It's not a bad job if you have what it takes, but the reason we're paid a lot of money is that many couldn't force themselves to do it even if they wanted to. You make it sound like we toil away every day, almost as if we were breaking rocks or hammering iron. We don't. We have cushy and sedentary jobs that many could do and even more would die to have. Most LOB software development is not special and not that complicated. We don't create unique works of art in every project we work on, although the occasional piece of code does tickle the brain. There are many software developers working on much more complex things (compilers, OSs, high-performance computing, firmware, rockets, etc) but those are in the minority. And I firmly believe that anyone with enough training and experience can write OS code, or compiler code, or firmware, etc. > There's a lot of responsibility, uncertainty and frustration. I'm not going to say there isn't because there's certainly a lot of that, but it's a small price to pay for how good we have it. We also, as an industry, don't deal with more or less BS than other white-collar, office jobs. I recently had a conversation with a friend going through her (medical) residence: 12+ hour shifts several days in a row, combining hospital work with lectures. Nurses have it even worse. We (software developers) should be very grateful.
- manicennui 3y agoOur jobs might not be physically demanding, but many of us are mentally exhausted every day. I don't work an insane number of hours, but the expectation is always that I'll figure out a way forward with limited information and a team comprised of both competent and incompetent people who mostly want to be told what to do. In the vast majority of software engineering jobs, writing the actual code is trivial.
- charles_f 3y agoIts good to share your experience with new comers, I agree with some of it, there's a lot of stuff that's debatable, and I struggle to present my own experience as "truth" to begin with. > As someone who spent a lot of years in this industry Amazon calls qualifiers like "a lot" "weasel words", because they hide the information into a subjective expression. I had to go to the authors resume to understand what's "a lot" and it seems that it's 8 years. That's certainly more than average when you consider that the number of devs double every 5y, but I don't consider that "a lot". I have more than double that, and I still don't call that "a lot". I still have massive realization about work every now and then, which prevents me to establish "truths" given that it's all just perception. Side note: I tend to disconnect a little as soon as someone starts a sentence with "as a X", because they're trying to use their qualifiers as proof of what they say. > College will not prepare you for the job I feel like my own college prepared me well. > The majority of software engineers hate meetings. But remember that your job is also to communicate about things openly and proactively. I hate most meetings because they're useless. Half of the meetings I go to exist because a) someone does not like reading so they want me to read the status I gave in an email b) cargo cult c) because its more convenient for a single person to waste everyone else's. It's great that we can have meetings, some are productive, but in a software company that ships software, protecting the time of people who actually write the software seems like a good idea. > Nobody gives a f** about your clean code In the companies you went to, maybe. I give a f** about clean code, because once in a while I am gonna get called at night because stuff's broken, and I don't want that to be because of your shitty code. (also, I rarely saw a college graduate produce clean code, it seems to be something that you need to have experience to do). > You will profit more from good soft skills than from good technical skills There's truth in there, it's important to develop your communication and presentation skills. To be fair a lot of my graduate year at college was around that so, once again, I felt prepared. Saying that you will benefit more from that than tech skills is against a stretch that will vary based on where you are at on both sides, and generally speaking it pays more to be good at what you are being paid for. > It will be almost impossible to disconnect from your job Strong disagree, and I don't think that this is a message you should transmit. Funnily I think I pivoted my point of view on that topic around the experience level of the author. I think it's a tendency of your early years, when career is your priority, to always prioritize career. Later, when you find other things you enjoy, disconnection from work is entirely possible. Don't take your computer when you leave for vacation. Be strict about not communicating after hours. Dont reply to your phone (I don't even have work emails on my phone). If you really love your job and spending more time in it is your hobby, go for it. If that's not the case, learn to disconnect.
- photochemsyn 3y agoThis is distorted thinking at best: > "This may be a shock for some new folks, but it makes perfect sense. As a software engineer, your primary task is to generate value for users. Writing code is just a step that accomplishes that goal." No other engineering discipline thinks this way. An aviation engineer's primary concerns are that the thing they're building is (1) safe and (2) efficient. Whether or not that product is profitable will depend on marketing and competition at a whole other level. It's NOT the engineer's primary concern. This is also true for electrical, chemical, civil, etc. engineering. If there are a lot of software engineers that think this way, all that means is that the discipline is still in its infancy and hasn't adopted the kind of engineering standards that others have had to over time. Maybe the kinds of standards and regulations applied to sellers of electrical devices should be applied to every company that sells software?
- yoyohello13 3y agoI have never encountered a profession that complains as much about their job as Software Engineers. I've worked many jobs in my life: restaurants, construction, teaching, IT Support and so far the best one has been software development. Every job has its annoying BS. I get it's not for everybody, but at least I get to solve puzzles all day instead of digging post holes or dealing with shitty customers.
- spir 3y agoPete Davidson joked that depression is a rich person's condition because it implies you have a life you shouldn't be depressed about. Same with software engineers?
- tstrimple 3y agoI know mental health issues and suicide attempts correlate much more strongly with folks lower on the socioeconomic ladder, but when I was poor I was too busy to be depressed in the same way I am today. Now my life is far easier, yet also somehow much more depressing.
- PH95VuimJjqBqy 3y agohaving grown up extremely poor, I agree with this sentiment. But it's also more than that. I hate using this word but I think it applies here. Poor people don't have to the privilege to stop and whine. - When I was a teenager I had a flat tire and the spare was flat. I knew of a tire shop a few miles down the road so I pulled the tire off my vehicle and walked it the several miles to the shop. The shop was closed because the guy had called in sick. It was another 15 miles to town, so I started the walk. Thankfully someone took pity on me and picked me up after a couple of miles. - When I first graduated college I didn't have a working vehicle but got a job miles from the house. I would leave around 3am and walk for 5 hours to be there at 8am, then hitch a ride home. I did this until I could afford a bicycle, which I had for about a month before someone stole and I was back to walking. - I know a woman who recently (w/i the last 2-3 years) was talking about how when her vehicle broke down one night she ended up having to walk 12 miles back into town. For poor people there's this hard wall where if you stop it's akin to laying down and dying, the results are catastrophic. So you do what you must. People who are not poor often don't understand how it is that someone can't or won't take the time to talk to a therapist about trauma. They can't afford it either in time or money.
- croes 3y agoHard-to-swallow truths? I thought that's just common knowledge.
- kevinsync 3y agoI would encourage anybody interested in a professional career (in anything) to zoom out and keep in mind that almost every profession is ultimately about providing service. You will primarily work with (and for) other human beings, inside your organization and outside. The measure of your success is often perceptive, coming from a boss, a coworker, or a client, and it may not directly correlate with your perception of what you may or may not have personally invested into the solution. Software engineering is philosophically no different than plumbing -- sometimes the job is designing and implementing a plumbing system in a new building, other times it's diagnosing the source of a leak and fixing it, many times it's clearing literal feces from a pipe. Your value is not just extracting those turds, it's often being calm, competent, compassionate, timely and communicative while doing so. It comes from perseverance for solving the problem to the customer's satisfaction. It also comes from defusing situations with angry / incompetent clients, disaster projects, and resolving chaotic situations. Your role is to help reduce friction and solve problems for a person or organization in need. That you're writing software is purely coincidental; it's but one of many deliverables you provide throughout the course of your career. The rest are "soft" -- insight, support, quality, reliability, trust, consistency, charisma, general likeability as a human being, etc. If you're doing this for a job, you're going to have to deal with a lot of people, a lot of arbitrary constraints, a lot of bullshit, and a lot of bureaucracy that have nothing to do with writing software. The same argument could be made for law, medicine, engineering, hospitality, cooking, fashion design, driving a taxi, street performing, drug dealing, sex work, you name it. That's just the reality of work! If you're more interested in making art, do that instead (or both at the same time), but try to understand that there's a marked difference, and they serve separate, necessary roles in life :)
- GMoromisato 3y agoWell said. It took me an embarrassingly long time to realize this. Part of the problem is that many software engineers never get to talk to the actual users who are benefiting from their work. Or if they do, it is only when they complain about bugs or missing features. Now that I'm a consultant, talking directly with customers, I can see the excitement in their eyes when I solve a problem for them. It's usually a trivial piece of code that any junior engineer could do, but it solves a real problem that they've struggled with.
- mannyv 3y agoIn addition, a huge amount of the time you spend will be trying to figure out what the code is actually supposed to do.
- freeone3000 3y ago>software development is not a dream job If your worst complaints are that you have to work with others, that solving the problem matters more than how you do it, and you have to sometimes have a pointless meeting, I don’t think any job will work for you. High wages, good conditions, medium social status, high bargaining power, and you get to do something you love. It is the best job available.
- btbuildem 3y agoThis reads like a person who has walked past a couple of turns in the road from the starting point, and is looking back to describe the totality of a grand journey to the his naive uninitiated inferiors. Kid, you're just at the beginning.
- ram_rar 3y ago> Nobody gives a f* about your clean code There is more nuance to this. Soft engs need to realize what stage of product and business lifecycle they are working on. Most importantly, get into the mindset individual contributor not just a programmer [1] (highly recommend reading Patricks blog on this) 1. If you're building 0 -> 1, the focus is shipping early and faster. This is not the time to crib about SLOs and chaos testing. I'm not saying these things are not important, but very likely they are way down the list. 2. Once you have crossed the chasm and have a mature product or platform that product engineers rely on. Then reliability, fault tolerance SLOs etc matter a lot more. This is the phase, I'm more concerned about using the right abstractions and ensure tech debt is managed well. 3. Product is in KTLO mode - In this phase, you could probably spend quarters LARPing on making things better and afford to work on things that very likely have diminishing returns. Nobody gives an eff about your clean code, if no customers are using it. [1] https://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-programmer/ https://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-pr...
- deleted 3y ago[deleted]
- toomanyrichies 3y ago> The user doesn't know how the codebase looks. The user just sees what features that product is offering. So don't get overly attached to your clean and elegant code. Focus on shipping the feature on time and bug-free. This is a slippery slope. True, the user doesn't see the code. But they do see the feature set (or lack thereof), and the speed at which you're able to update that feature set to suit your customers is a function of how easy the code is to change. In turn, that ease of changeability is a function of how easy it is to read, maintain, and reason about. Focusing on "shipping the feature on time and bug-free" is good, but at the extreme it can lead to the mentality of "I'll fix the tech debt later", with "later" being indeterminate. Which is when the old saw about tech debt being like credit card debt starts to bite one in the ass.
- wly_cdgr 3y agoI love the idea of shipping a "bug-free" feature before the heat death of the Universe, it's beautiful to have noble ideals like this.
- ornornor 3y agoBecause there is no middle ground, right? It’s either perfect code that will never ship or unmaintainable code that gets shit done. Besides if you let “we’ll fix it later” take hold, you eventually end up shipping features after the heat death of the universe while also having unmaintainable code. The best of both worlds.
- wly_cdgr 3y agoThere's definitely a middle ground, it's just not very close to where product imagines it is
- winrid 3y ago11). Despite excitement and encouragement to learn, after 10 years of learning, staying employed at the same salary level becomes harder, not easier. :) There are outliers... but I would say on average ageism hits most of us. Being a specialist is a must at that point (if you want $$$).
- omginternets 3y agoIf you're a junior dev, I'd urge you consider that there is a difference between software engineering and the digital factory. The author seems to work in the latter. IME, the people who say such things as "college won't prepare you for the job" or "CS doesn't matter" are invariably the ones who find themselves grinding away at REST endpoints and becoming embittered.
- kagakuninja 3y agoCollege absolutely does not prepare you for any software job, unless you are some kind of ivory tower architect that can tinker in a lab with no need to ship products or work with other teams.
- omginternets 3y agoSpeak for yourself. There are few things more practical than a good theoretical grounding when your job is to: 1. design and implement a database 2. design and implement a p2p consensus protocol 3. design and implement a programming language 4. train and validate an artificial neural network 5. reason about concurrency etc. At some point, we really need to start distinguishing the kind of programmer who writes REST endpoints all day from the one who engineers the systems other programmers treat as an abstraction. Both are respectable jobs, but the former is closer to plumbing than engineering. The former is also less well-paid, has less job security, more on-call duty, less intellectual substance, less technological innovation (but arguably more commercial innovation), more grunt-work and a lower barrier-to-entry.
- kagakuninja 3y agoOK, 99% of devs do not do items 1-3. I have never worked at a FAANG, but most of them are doing grunt work, from what I have read. Furthermore, taking a database course in college might involve building a toy DB, I will argue that it is not at all comparable to building a new DB from scratch. The theory is helpful, of course, but it is just an introduction, unless they are doing serious post-grad research. And it isn't just "plumbing" jobs like REST. The same thing was true when I worked in game development, or consumer apps. Back in the 90s we did have to occasionally write a new data structure or something, now it is off the shelf.
- reactordev 3y agoThe soft skills section has some great examples of where the author lacks his/her own soft skills. Some folks, during stand up, just want to get on with their day. They will say things (Like George Did, "I helped so and so all day") just to keep it moving. Doesn't mean they truly believe what they just said, they just want to get back to work. Sometimes, people will do things, things that seem like they are incompetent or don't care, but really that is your own bias (Why did they not help me when I needed it?) and make you look like not the team player. Instead, you should have gone to "George" and said, "Hey, thanks for looking at that issue, I managed to solve it with Michael's help, here's how we fixed it." Lead by example. Lead with empathy. Maybe George spent only 5 minutes with you because he has deadlines and doesn't have the communication skills to say "Hey Bob, I'd love to help you, really I would, but I have this hard deadline for this feature I'm working on and it's stressing me out because I can't solve this edge case". Use your words, explain your thoughts, people will be WAY more receptive and will want to work with you. Again and again.
- cheriot 3y ago> 10) You will profit more from good soft skills than from good technical skills Related to this, your customer is not the company's customer, it's your management chain. It took me an embarrassingly long time to internalize this. The stories executives and managers tell each other is what decides you career trajectory. What is their priority and how will they judge the outcome?
- jdeaton 3y ago> your customer is not the company's customer, it's your management chain Another: some coworkers will have spent so long in large corporations that they've internalized the pathological dynamics of large organizations as universal truths.
- cheriot 3y agoYour customer isn't going to decide salaries, promotions, or who gets laid off. Here's your universal truth: focus on the person whose decision affects your outcome. If you work for people that will see and reward your focus on the user, that's great, keep it up.
- justin_oaks 3y ago> Because if you promise to deliver it by Tuesday and you run into some problems, you won't be able to fulfill the promise. Instead, if you accept Friday as a deadline, and you finish it by Wednesday, you can deliver it 2 days earlier. Or you can deliver it on Friday. I once had a boss that taught me an important lesson. Some other party (business unit or company, I can't remember) asked for some work to be done. He said for me to not work on it right away. I said I could get it done in a couple hours, so why not do it right away? He said it was to manage expectations and not give the other party everything they want right away or they'll come to expect it. Edit: I also wasn't to start it right away because the work may not get done at all. Some of it was to delay to determine whether the work was even necessary. And some of it was to push back to ensure that we're not ALWAYS giving in to every demand.
- reactordev 3y agoIf you're reading this, this is what not to do. Plan your work, expectations of delivery should be on those milestones of sprint releases or whatever yard-stick you are using for planning. Simply doing work as fast as it comes in is a sign that you have no planning. No road map. No future outlook of feature sets. You are flying by the seat of your pants. This isn't a lesson to learn, it's an anti-lesson. Yes, don't work on things right away and deliver right away as your "customers" will expect it, but why is that a bad thing? Why can't you easily deliver features when they are ready? Why is this boss giving you such bad advice?
- deleted 3y ago[deleted]
- justin_oaks 3y agoI may have oversimplified it. There were certainly other factors at play in the boss's mind. The other part of it was to not do extra work for the third-party when that work wasn't specified in the contract. If you do extra work every time you're asked then it'll quickly be abused. You don't want to seem like a contract stickler, but you also don't want to bend over backwards either. It's something to keep in mind.
- Tistel 3y agoas a 20+ year developer, this is excellent. One of the bigger leaps for me (which the author mentions) was going from toy CS assignment projects where I wrote all the code and knew it inside and out to huge multi year projects with hundreds of developers. It was a giant spaghetti code of math heavy C/C++. I was always surprised it worked at all. You don't even know where to start to add some feature (don't panic!). Some highlights where comments above a particularly tricky function was something like: "do not change this, you think you understand it, but, you don't. move along" and something like: "In Graecia antiqua, pueri tui similes in extremis rupibus remanserant mori." (latin for "In ancient Greece, children like you were left on the edge of cliffs to die.")
- pyrrhotech 3y agoHere's another good one. You almost certainly will never make it to the upper class with this career, no matter how well you perform, unless you transition to management and climb to VP+ in a large company or start your own company. You can be comfortable as an engineer, but it's not the gold mine lots of folks think it is.
- askafriend 3y agoWhat income level would you say is upper class?
- pyrrhotech 3y agoI would say upper class is about net worth, not income, and probably top 1% or so would qualify
- otalp 3y agoMost Big Tech engineers are in the top 1% net worth for their age
- deleted 3y ago[deleted]
- g9yuayon 3y ago> College will not prepare you for the job My personal experience says that this is a misconception: https://www.reddit.com/r/programming/comments/267s49/comment/choppne/ https://www.reddit.com/r/programming/comments/267s49/comment... My college taught me essentials that carry me until this day. Actually, I didn't even know how to use a computer before I got into college, yet I was very well equipped when I graduated. What I was taught was harder and deeper than what I worked on when I started in IBM WebSphere, so getting good at my job, at least to a certain degree, was no big deal. Day-to-day tasks are really not that hard. What's really hard is solving unseen problems, for which the college education becomes really helpful. >> The college will prepare you for some basics, but what most of the colleges teach is so far away from day-to-day jobs I depends on what "basics" means. I'd argue that what we need in a job can be easily learned on the job, like a programming language, domain knowledge, CSS this or framework that. What's hard to learn systematically and intuitively (still possible, of course) are fundamentals: matrix calculus for you to understand the basics of deep learning; stochastic process to truly understand diffusion models, OS fundamentals + CPU architecture + parallel programming techniques to truly optimize a complex program, deep understanding of distributed systems to design modern stateful systems, deep understanding of mathematical statistics to come up with new ML models, programming paradiagms so you can learn any programming language easily, end-to-end understanding of how to write a compiler so that you can write a descent compiler or interpreter when you really need to design a DSL instead of thinking YAML + Jinga is the best thing in the world. The list can go on and on, and such fundamentals are really hard to learn systematically on the job. Case in point, a colleague of mine used to mention how he learned distributed system in his college: his professor would ask them to read a paper before each class, and then the professor would ask them deeper and deeper questions, give them historical context, and challenge them with all kinds of corner cases. How many people could get this level of drilling outside of college? Another example, in the software engineering classes that I took, we learned a lot of things about formal verification: temporal logics, infinite automata, abstract interpretation, model checkers based on OBDD and on SAT, and etc. So now learning TLA+ for my work is really a delight. I couldn't imagine I would be able to learn all the maths behind formal verification on the job, as I wouldn't have access to professors and TAs for questions, there would be no one to distill a 500-page book into its essences, there would be no seminars for us to discuss papers, there would be no well-designed projects that came with professors' feedbacks, there would be no carefully chosen problem sets that were possible to solve yet thoroughly challenged me...
- Elucalidavah 3y ago> You will *profit more* from good soft skills than from good technical skills The rest of the truths I'm more or less okay with. But this one, no: in large orgs, people with good "soft skills" will profit more *to the detriment of the projects*.
- black_13 3y ago[dead]
- wolfspider 3y agoThe time you spend on projects is, according to what the PM tells sales, two weeks for a feature and three weeks for bare minimum requirements new product. Outside of that your own company will guilt you into some feeling of inverse wage theft where you make up for it by donating your free time. Realistically, three months to build an app you can demo is tight but those are competitive timelines and you want to be competitive don’t you? AI I’m sure has skewed this towards less effort to meet those timelines (I hope). Another hard to swallow truth is that sometimes you are just given a project there is no optimal solution for because you were meant to fail at it. Usually it’s a problem client or impossible task. The more skilled you are the more likely it gets assigned to you. Developers that get to cherry-pick all of their assignments are also the ones that get to lie about their time allocations on projects (to add insult to injury). If you are a new hire you will be doing a lot of their work for them so climbing up the ladder takes a lot of humility. Most devs super concerned about other people’s mistakes usually cause a ton of problems themselves and this concern is directly related to all the things they are actually hiding/covering up in reality. It’s not uncommon to find that the Super Saiyan coder is actually keeping a proverbial building from falling down with a toothpick but they are very concerned about the formatting of everybody’s code. Younger developers think, by default, everything is crap but they don’t even bother to hide any of their screwups and they have the energy to keep screwing up for a long time and at an accelerated pace. This, ironically, does mean more money for the company so hiring a lot of young developers is good for the bottom line and makes customers seem very engaged.
- zafka 3y agoThis article restated a lot of the downsides of being a "software engineer", but the real highlight was the cartoon. "How many duck size horses are you willing to fight" LOFLMAO
- AtNightWeCode 3y agoThis biz have basically driven me insane. Some comments. The problem with time estimates is that you often have to estimate not what to do but a vague vision of something. We want it to be easier to do X. How many hours? I agree with what to promise. The problem here is that you will get pressured into bad decisions. Somebody might say that it's just a new button. It is never just a new button. The joke, junior devs work with coding, senior devs with people is true. Many coders quit coding after some years and go full time into management positions. At some companies that is expected and you are being looked down upon if you are "still" coding. Clean code does not really tell if a solution has good architecture. I have seen horrible solutions that use clean code and great solutions that have mediocre code. Management typical just want new features. Prepare to be called in to help resolve issues related to bugs that has been known for months but not been prioritized. Third-party companies are not your friends. Be prepare to work with people that will straight up lie about things. Also be prepare to work with colleagues that does the same thing. People will try to take credit for your work. Management people are experts in this field. But the worst thing is also the best thing about being a coder. You have to to keep up and learn new things. The biz is crazy fast. It is easy to challenge yourself. The amount of new cool stuff coming out is just amazing.
- robbywashere_ 3y agoWhattaya mean, the 5 round 60 minute leet code 'technical questions' with 5 minutes left for any questions never prepared me for this!??!
- inlined 3y agoI feel like Cal Poly SLO prepped me for “real programming” relatively well. The software engineering major has a year long capstone program building software for a real company. I built a scriptable GPS emulator for Trimble. I was also required to do a work study to use software engineering to the benefit of someone other than software engineers (I worked on real estate).
- l0b0 3y agoSounds like some bitter lessons from some pretty bad workplaces. Not everywhere is this bad, people. Expect to change jobs a few times before you find a good fit.
- GuB-42 3y ago> Working in software engineering often means long working hours. Most of the time, you are glued to a computer screen, with little work-life balance. > The job demands an online presence, sometimes even after work hours. This often leads to stress and limited personal time. Maybe in the US. But in France, where I live, it is absolutely not the case. You may have long working hours if that's your thing or if you are working in a particularly toxic company. But most people I know just disconnect outside of work hours, this is even protected by law. Before the pandemic, in many cases you simply couldn't work after hours as you weren't allowed to take your stuff back home and the office was closed. The drawback of being a software engineer in France is that the pay is much lower than in the US, by all metrics. For the rest of the article, I think it is accurate.
- escapedmoose 3y agoIn the US it varies between companies, but it’s not all that difficult to avoid places that expect extra overtime, or to say “no” when it’s requested in most cases. Eventually they stop asking you, ime. I’m unsure whether declining has a negative impact on one’s career.
- mirnoc 3y agoA lot of these are applicable (in the general sense) to jobs in many other industries as well. But I'd still rather be a SWE because the compensation doesn't really compare.
- chrsw 3y agoAlso, don't get too attached to a project. Get mentally prepared to work on a project for 2 years then have it cancelled. It happens. Get over it. It's not your baby.
- creer 3y agoBugs?!!! Some good ones sure but I don't understand "Bugs will be your arch-enemy for life". Bugs can't be your enemy. Bugs are what you do. It's your life. We are talking software engineering. If you hate bugs. If bugs make your skin crawl. If you throw up or throw monitors out the window... Then please don't get into software engineering! Or at least first look at yourself and recognize that this is why you get the big bucks. Sorting out bugs is normal. The time it takes is normal (well, do get better as you go about it...) You get paid for that. People rely on YOU sorting that out. Bugs are not the enemy. Bugs are the job. Get yourself to a point where bugs are not the enemy. You can't spend your life getting frustrated by bugs.
- creer 3y agoIf you are new, and you are asked to estimate something, get your boss (or other mentor) to help you sort out the local customs. Don't throw some random number on the table.
- techomsystemau 3y ago[flagged]
- jakupovic 3y ago>>If I need to deliver some feature, and I think it will take 2 days, I add roughly 40% more time to it My first real job and Dan told me to estimate by first doubling your initial estimate and then multiply by 4. This gives a pretty good estimate, in most cases ...
- arendtio 3y ago> 4) You will sometimes work with incompetent people So tell me, when are the times when I will work with competent people? SCNR
- thewileyone 3y agoMy degree was in computer engineering, not software, so when I started out, I got into QA/Testing. Looking back, that was a good way to start in the field because you're thrown into a shallow end of the pool and it allows you to feel your way into the deep end.
- sanroot99 3y agoSeems like a AI generated article, it lacks the personal touch and is too generalized.