News for hackers. Stuff that matters.
Re:How does one get close to mastering software engineering? by peakaboo on Tuesday August 24, 2021 @04:14PM (#28294358)
You are much more likely to burn out then to master it. Look at the age groups in software development. Most people get out of it before 40 because it's such a draining profession.

Can you really even master something like software development where things change dramatically almost every year?

Re:How does one get close to mastering software engineering? by cactus2093 on Tuesday August 24, 2021 @04:34PM (#28294639)
> it's such a draining profession

I truly can't understand thinking this. I've worked in software engineering for over 10 years now, at a wide range of companies from tiny startups to large tech cos. We easily make 2 - 5x more than the median wage, work indoors in a comfortable environment sitting (or standing, for anybody who prefers) all day with high end ergonomic equipment, often get unlimited vacation time, can often choose not to work more than 8 hours a day if we don't want to, and all while doing something that many of us got into simply because it was a fun and engaging thing to do. And just in the past year millions of software engineers have gotten the option of doing this fully remotely, freeing them up to live anywhere they want and never have to commute. What a time to be alive!

Re:How does one get close to mastering software engineering? by decebalus1 on Tuesday August 24, 2021 @04:50PM (#28294840)
Read some of the comments in this past thread https://news.ycombinator.com/item?id=27821392 to understand this better. I've also been working at this for well over 10 years and I do agree that overall this profession is draining. I often need 'hard resets' between jobs, it's hard to compartmentalize work and regular life when you brain is constantly thinking about 'the system'. I have experienced burnout a bunch of times. It's not pretty. Add the new trends of making devs do oncall because frankly everything is online, tech interviews becoming the coding Olympics, the incentive structure in an organization making people cut corners or backstab coworkers to get ahead, it's not hard to understand how someone would consider the profession draining. This is from the perspective of someone who worked both in small and big corps on the west coast.

Comfort doesn't have a lot to do with burnout or job satisfaction unless you're coming from a blue collar mostly manual job.

> many of us got into simply because it was a fun and engaging thing to do

That's one of the problems. For a lot of folks, it was exactly that 'was a fun and engaging thing to do' and then you get do it in the context of office politics, tight deadlines, need to sacrifice professional ethics and ship something half-assed because that's what the business needs, etc.. These things, repeatedly chip away at your happiness. Would you be more unhappy without the ergonomic equipment and all of that? Most likely yes. But ping-pong tables and the unlimited vacation (which is at the discretion of your manager anyway) doesn't always compensate for shit work or the nervous breakdown from having to sit on an incident bridge for 4 hours...

I need to admit, I love my job and I love this profession. But I do understand when people say it's draining.

Re:How does one get close to mastering software engineering? by cactus2093 on Tuesday August 24, 2021 @05:07PM (#28295025)
Most of this is true of any office job though.

Oncall is somewhat unique, and that can be tough, but if it's particularly rough and there is nothing you can do to improve it that's a good sign to find another company (or perhaps another specialization within programming) because it doesn't need to be that way. Incident response is mostly a self-imposed stress, and I've found it to be something that you can learn to manage better and not let it affect you so much, by being prepared with good playbooks, as well as accepting that it's not the end of the world and that all you can do is try your best.

I'm not denying that life itself can be draining. Working any type of office job can be draining. I just don't see how programming is particularly more draining than all the other jobs people do.

Re:How does one get close to mastering software engineering? by brailsafe on Tuesday August 24, 2021 @04:57PM (#28294907)
Well, not to be reductive, but what have you done in that time, and for who? You said a lot about conditions of work, and that's great stuff, but often times a McDonald's employee has more visibility into where their work goes than a developer making stupid widgets to increase their numbers for the week. A construction worker can point to a house and say "I built that foundation, it'll be there for 20 years, during which someone will live in it"
Re:How does one get close to mastering software engineering? by cactus2093 on Tuesday August 24, 2021 @05:22PM (#28295150)
I've done lots of things over the years, sometimes grown sales by millions of dollars, sometimes taken a brand new thing from 0 to 1 and get it out to the first users, and I've experienced the satisfaction of solving a problem for happy customers. Not always, mind you, I've also seen companies have to downsize or shut down when their lofty goals didn't quite pan out. But that's the beauty of being in this field these days, there are so many different kinds of companies out there to choose from.
Re:How does one get close to mastering software engineering? by brailsafe on Tuesday August 24, 2021 @09:17PM (#28297048)
It sounds like you've been very lucky in a few respects, and that certainly wouldn't lead you question whether or not it's a good career choice. Supposing those things that you've done are true, would you feel the same way if you were part of the downsizing, or you never found yourself in the position to affect sales in such a way, or you weren't compensated for it, or you never got to know who the work actually impacted directly?
Re:How does one get close to mastering software engineering? by Koshkin on Tuesday August 24, 2021 @08:53PM (#28296881)
But today there would be no McDonald’s or little new construction going on had we not written the software their insurance companies are using.
Re:How does one get close to mastering software engineering? by brailsafe on Tuesday August 24, 2021 @09:02PM (#28296947)
True, though I suppose we could also do without it :)
Re:How does one get close to mastering software engineering? by doomroot on Tuesday August 24, 2021 @05:13PM (#28295071)
Sounds like you need to quit your job. I hear they’re paying new hires a lot.
Re:How does one get close to mastering software engineering? by brailsafe on Tuesday August 24, 2021 @09:05PM (#28296959)
Thankfully I burnt out, in part because I didn't quit soon enough, and haven't found another yet in a very long time. Heres hoping that if I do find one before I quit looking entirely, it will pay well :)
Re:How does one get close to mastering software engineering? by jmfldn on Tuesday August 24, 2021 @04:41PM (#28294734)
The fact that most engineers are young is much more to do with the numbers in the profession doubling every five years in the last twenty years imho. If you were an engineer twenty years ago, there are now sixteen times more engineers. Your peergroup is going to look pretty small therefore. All of these younger engineers are going to get older too of course, and the demand won't keep on growing at this rate, so inevitably the ratio of young vs old devs will even out.

Sure, some devs become managers but there are only so many managerial jobs. Some also drop out but not in vast numbers. From my own experience, I see quite a few of devs my age (40) and older. For the most part we're senior engineers, some are managers. I don't know anyone who's left the profession. Just my anecdotal evidence but I do feel this phenomenon is overstated.

Re:How does one get close to mastering software engineering? by rubicon33 on Tuesday August 24, 2021 @04:57PM (#28294906)
And what about your 50s, or 60s? When do you plan to retire? The "average" retirement age is what, 65? Do you plan to code until then? If so, are you fairly stable in what language/domain you're coding for, or are you learning constantly?
Re:How does one get close to mastering software engineering? by jmfldn on Tuesday August 24, 2021 @05:35PM (#28295301)
Good questions. I'm not 100% sure, but currently I plan to be an engineer until I retire which I guess will be around 65. My goal will be to wind down later in my career though, work less than a 5 day week and go for contract / consulting kinds gigs from 50s onwards ideally. Right now I'm happy just being on the payroll doing a 9-5 gig. The stability suits me well at this point in life.

I'm a Scala developer working on fairly typical, distributed systems / web apps. I have no plans to stop Scala since I love it but any JVM language would suit me. I'm also into system design / architecture in the distributed system, "reactive" architecture domain. Those are the systems I tend to work on, massive web apps consisting of many microservices.

I'm always learning and trying to be on the edge of my comfort zone which is key I think. If I'm not messing with Scala then I'll be learning more about Kafka, Docker, SQL / Mongo, Terraform, AWS and a bit of Linux.

I'm far from a master in any of these things and I don't think I'll master many which is fine. I know enough to do my job and I keep on learning but the breadth of what I have to know is too broad to master it all. My true passion is programming, particularly functional, and I would love to master that for myself as much as anything. I guess you have to chose where to go deep and where to go for breadth. You can't master it all!

Re:How does one get close to mastering software engineering? by rubicon33 on Tuesday August 24, 2021 @06:39PM (#28295868)
Thanks for your reply, I'm always interested in hearing about how other developers are choosing to tackle this tough career question about depth v.s. breadth.

Scala is an absolutely awesome language, one that I love. I've had some of the best times building distributed systems with Scala + Akka and frankly would have loved to lean into that ecosystem and become a master of it.

Unfortunately, the market for that specialty is relatively small when compared to the broader software engineering market. I worried about specializing in a language that was niche. Compare it to, for example, the need for React, React Native, or even simply Java.

I have chosen to be very flexible in my career and learn many languages, across many domains. This, I think, is the source of some of my feelings of burnout in my 30s. It's just a never ending grind. When I do find a domain that I really love, like firmware, or Scala... I'm forced with the difficult decision of depth v.s. breadth and breadth always seems like the "safe" route, especially if you're willing to jump between frontend or backend and whatever is the flavor of the week as far as frameworks go.

I've heard horror stories of engineers who dug into their tech stack and never really kept pace with the industry, only to find themselves disposable, and inflexible, in their 40s and 50s. Whether or not those anecdotes are worth worrying about is certainly up for debate. I tend to be a worrier so, it's no surprise I've chosen the safe route.

Re:How does one get close to mastering software engineering? by jmfldn on Wednesday August 25, 2021 @01:56AM (#28298444)
I think over-specialisation is potentially dangerous so it's worth bearing in mind. Ideally I think a balance is necessary, have one or two areas you focus on and keep your other, perhaps less developed, skills sharp. This is why I'm keeping a closer eye on things like Terraform and aws these days and generally sharpening my infra skills. Perhaps the best way of summing up my approach is to aspire to know everything about something and something about everything. The former gives you the satisfaction of deep knowledge, and the latter means you can pick up new tech more easily. Generally our industry is about knowing just enough in many areas, and knowing which questions to ask / what to search for.

As for specific languages, as long as you're aware of a couple of paradigms, eg OO and FP, I figure it's not that hard to switch. Once you've mastered one or two languages you can generally be productive in another relatively quickly. We don't necessarily hire Scala devs for example, just engineers we think we can train up.

I'm lucky in that the Scala job market is hot in London but I'm fully prepared for that to change one day. I'd probably target Kotlin or Java jobs if that happened but also open to anything interesting job-wise that will have me. I have my tech preferences but if I need to switch, and someone will allow me to learn on the job, then fine!

Re:How does one get close to mastering software engineering? by rubicon33 on Tuesday August 24, 2021 @04:50PM (#28294841)
I have been seriously wondering about this. I'm mid 30s developer who has (because of jobs) switched domains multiple times over the last 10 years.

I've learned 7 programming languages, COUNTLESS frameworks (both backend, and frontend), across many different domains... frontend web, native mobile, hybrid mobile, backend, even dabbled in firmware for a few years. All of these in a professional context, where I was shipping real live code.

If there's been one constant in my career it's been change. Change is constant. I can absolutely expect that in a given ~3 year timespan, I will need to learn a new language, domain, framework, etc.

The result is absolutely that I feel like a jack of all trades, but a master of none. I can pick up new languages and frameworks quickly, but I don't ever feel intimately familiar with any given language or framework or domain. I don't feel like a "master" of anything other than, perhaps, mastering the ability to learn new . It sucks.

Perhaps not coincidentally, I've struggled with feelings of burnout. Looking back on my career over the last 10 years, it feels like a constant sprint. Of course I'm a better developer today than I was 10 years ago, but I know that the future only brings one thing: New technologies, new frameworks, new languages. I will need to learn those, and only a fraction of my current knowledge will apply.

It's hard not to feel like you're treading water in this industry. I can learn anything, but for long? For how many years, or decades, am I willing to do this? It feels like I need to either accept that this is the reality of this industry, that the biggest skill I can have is willingness and ability to learn, or, accept defeat.

Re:How does one get close to mastering software engineering? by rightbyte on Wednesday August 25, 2021 @06:12AM (#28299746)
Reach for automotive embedded programming. Anything newer than C89 is going way too wild. Better put those variable declarations where they belong!

Jokes aside, the grind and churn is real. Just try to find a job without the fad chasing.

Re:How does one get close to mastering software engineering? by yodsanklai on Tuesday August 24, 2021 @06:01PM (#28295529)
> Most people get out of it before 40 because it's such a draining profession.

Most of my team are 40+, we're doing fine.

> Can you really even master something like software development where things change dramatically almost every year?

This is a good point but things don't change that fast.

Re:How does one get close to mastering software engineering? by jmkni on Tuesday August 24, 2021 @04:22PM (#28294475)
I think that at least partly has to do with life circumstances changing, people get married, have kids, etc and have less time to spend practicing, reading.

I'm 32 now, have been doing this since 20, and (I think/hope) mostly kept up to date, but I'm also single/childless lol.

Also, as you move up, you inevitably end up managing/mentoring younger devs (unless you have terrible people skills or something), meaning you spend less time actually coding, this also makes it more difficult to keep up to date (in detail, you still know what's going on, but have less experience implementing).

To be fair, terrible people skills could also apply to still being single/childless at 32, I hope not...

Re:How does one get close to mastering software engineering? by yourapostasy on Tuesday August 24, 2021 @05:23PM (#28295163)
> ...as you move up, you inevitably end up managing/mentoring younger devs (unless you have terrible people skills or something), meaning you spend less time actually coding...

You can somewhat mitigate this if you want to still keep your hands in the code by finding the intersections of two or more tech stacks that take two or more others to even approach. The inevitable impedance mismatch between say two stacks means that one person familiar with both is usually far more effective than two people who have to feel their way through the mismatch.

As a senior in this position, you often get to do the "fun" parts of throwing together a proof of concept, validate your mental model of the impedance mismatch, outline the details to iron out (usually known-complexity work like documenting, hooking up to various plumbing for unit testing, tracing, logging, monitoring, internationalization, etc.), and go on to the next fire to help put out.

Re:How does one get close to mastering software engineering? by cultofmetatron on Tuesday August 24, 2021 @11:34PM (#28297788)
single and childless at 36. just frees me up to constantly travel fro place to place without a care in the world.
Re:How does one get close to mastering software engineering? by WolfOliver on Tuesday August 24, 2021 @04:28PM (#28294555)
you are in professional software engineering since you are 12? Learning to program is not the draining part it is the fun part. Dealing with people is the hard part.
Re:How does one get close to mastering software engineering? by rjbwork on Tuesday August 24, 2021 @04:30PM (#28294592)
They said since 20. Meaning 12 years.
Re:How does one get close to mastering software engineering? by jmkni on Wednesday August 25, 2021 @06:00AM (#28299660)
Sorry, meant since aged 20
Re:How does one get close to mastering software engineering? by jbarberu on Tuesday August 24, 2021 @04:30PM (#28294583)
Doing this since [age] 20
Re:How does one get close to mastering software engineering? by AQuantized on Tuesday August 24, 2021 @04:21PM (#28294465)
Part of this is probably that it's such a young profession. Most people I work with are quite a lot older than me anecdotally, however.

Even though the frameworks and languages in vogue change rapidly, the patterns and logic seems to be very similar. When I have to learn a new language now it's more a matter of researching the syntax and idioms rather than learning from scratch.

Re:How does one get close to mastering software engineering? by knuthsat on Tuesday August 24, 2021 @05:25PM (#28295186)
learning the underlying principles of things makes the changes look less dramatic.

after some point there's not much one needs to learn to be productive.

I feel no pressure not knowing vue, django, fp-ts, rxjs, Rust, Zig, C++20. Rarely there's something you can do with new stuff that you can't do with old.

Re:How does one get close to mastering software engineering? by commandlinefan on Tuesday August 24, 2021 @05:34PM (#28295283)
> more likely to burn out then to master it

I think you probably meant "than"... although that may be profound the way you spelled it.

Re:How does one get close to mastering software engineering? by peakaboo on Wednesday August 25, 2021 @10:07AM (#28301875)
Nice catch! No just spelling mistake, nothing profound there..
Re:How does one get close to mastering software engineering? by MattGaiser on Tuesday August 24, 2021 @04:30PM (#28294594)
I graduated two years ago and I feel behind not knowing Vue and Elixer, never mind things like Rust.
Re:How does one get close to mastering software engineering? by ravi-delia on Tuesday August 24, 2021 @04:35PM (#28294646)
Don't get me wrong, Elixir is one of my favorite languages, but I don't think you'd be behind for not knowing it. Even functional programming as a whole isn't widely enough adopted that people who aren't familiar with it are behind.