Live data from Hacker News

Ask HN: Reasons to stay in Software Engineering

news.ycombinator.com

11–20 of 58 posts

Re: Ask HN: Reasons to stay in Software Engineering

#11
Everyone wants to be a software developer until it's time to do software developer things. I spent a couple of hours on Friday handholding a contractor who needed to create a Jenkins pipeline in Groovy and despite there being copious documentation on the subject, he seemed completely unable to accomplish his task. No matter how he asked, I wasn't going to do his work for him, only help him understand the process of figuring out what to do.

So I ask you: What type of person are you? Do you dig in and solve the problem or do you run to others to "fix it for you?" If you are of the 2nd type, software development is definitely not for you.

Another observation: Many people I have worked with have managerial aspirations and seem to want to jump past doing any of the actual work in order to lead and direct others (and get paid high salaries). I find that behavior reprehensible.

Re: Ask HN: Reasons to stay in Software Engineering

#13
post #8

Earlier quoted context omitted.

In Software Engineering, you don't need to work where you live nor live where you were born/studied. One very good reason.

If you're privelleged enough to not need a visa.

I think they were referring to remote work.

Re: Ask HN: Reasons to stay in Software Engineering

#14
post #9
post #7

The effort to reward ratio is as good as it gets. Professions with similar or higher reward usually do so only with a lot of effort. Think litigation lawyers or doctors that pull crazy amount of overtime. There's a lot of jobs in the software field that will pull in 6 figures with great conditions and reasonable effort. That's why everyone is fighting each other to enter the field, for better or worse. And while "eve…

I've been hearing about saturation for about 15 years and honestly there are no signs of it, not even close.

Some time back I wrote this ( https://news.ycombinator.com/item?id=16148087 )

I'd be willing to take either side of a debate for "is there a shortage of people who, when given tight specifications for a piece of software (write a function that takes X as input and provides Y as output) that enumerates all of the corner conditions can produce a program in a language that they are familiar with."

At the same time, the "person who can work with the business user on the software, think about the architecture of it, identify the design necessary, come up with the estimate that actually matches the time frame that it will be done in with a reasonable error... and produce software that takes X as input and provides Y as output while being aware of where the edge conditions may exist and ask for clarification on how it should work"... I believe there is a distinct lack of that portion of labor.

Furthermore, there is also a lack of people who are able to move from the first labor pool to the second, and a lack of mentors who have the time and ability to help that group move to the second.

I don't think its incredibly difficult to hire an entry level person as long as one sets the bar low enough and has people within the origination who are capable of providing the design. On the other hand, it is very difficult to find the people who can give the necessary instruction to the entry level people to allow them to become productive within their ability.

As an aside, I also find that within the entry level group... there are a sizable portion that have the attitude of "I learned language X and that was hard enough, I'm going to stick with it and not learn anything else." That X can be found for all languages and none have the monopoly on it. However, it is disconcerting for me to see those individuals... I started out as a C programmer, and then Perl (full stack web - some JavaScript in there) and then Java (enterprise), and then Java stand alone (swing application)... and while I'm still a Java programmer, I can see other languages looming on the horizon. Java will become the COBOL, and while there are still COBOL programmers out there, its not something that one wants to get stuck in for another two or three decades waiting for that last app server to be turned off before they can retire.

----

At the "anything past entry level", I still find that the number of qualified applicants drops off substantially. For entry level, the applicant pool is very, very large. I am now despairing that many of that pool don't have the necessary skills to move beyond following someone else's design.

Re: Ask HN: Reasons to stay in Software Engineering

#15
Why are you getting a masters degree? Are you doing this while working full time? What is your end goal for a masters degree?

The interview process for software developers is as you write, terribly broken at a lot of companies from the point of view of most developers. I do not see this changing in the foreseeable future and it does not matter what software you have written in the past, you will get the opportunity to prove yourself all over again for the rest of your career.

One possible solution is to work for yourself. This solves some of your issues and introduces a whole different set.

Re: Ask HN: Reasons to stay in Software Engineering

#17

devs with 20 yrs experience have to go through whiteboard interviews. thinking that this is an insult is wrongheaded. hardware jobs pay less. many times, much less.

In my experience, a web job can net up to 4x salary vs a much more difficult hardware engineering role. I know because I went form hardware to web and the average compensation is much higher. Additionally, web jobs tend to be less stressful.

Re: Ask HN: Reasons to stay in Software Engineering

#18
I stay because I love it. Coding is my passion, and I'm grateful every single day to be paid well to do something I enjoy. I'm not entirely convinced that other professions don't suffer from the same negative aspects either (bad management, terrible deadlines, cargo cult-ing, some boring tasks). For me, outside of maybe working in pro audio, I can't imagine doing anything else.

> "For some reason, companies do highly mistrust my skills and degree. Other jobs, equally well paid, do not require this."

I think if other jobs were able to directly test your technical skills in an interview they probably would. I personally hate whiteboard style interviews as well but, having sat on both sides of the interview process over the years, I see a lot of value in seeing people's code. Personally my preference is a take home coding test, but interactive coding is fine too if the problem isn't too tricky. Probably this is because I am self taught and don't have a degree to lean on that colors my opinion so take my words with a grain of salt I guess.

Re: Ask HN: Reasons to stay in Software Engineering

#19
Your second point contradicts your first. You don’t need credentials to do it but you need to know a lot. People with good word of mouth reputations have much better job security (perhaps spanning multiple firms) than most other fields.

The key question is “Do you like the work?”

Re: Ask HN: Reasons to stay in Software Engineering

#20

I was recently speaking with a recruiter who advised me to “prep” for tech interviews. “Read Cracking the Coding Interview”, he said. “Do some programming problems so your skills are fresh”. I’ve never prepped for a tech interview and I’m never going to read a stupid book that’s supposed to coach me. What am I prepping for? I’ve been a programmer 10+ years. I’ve had 10+ years of “prep”. Is that “fresh” enough for you…

After reading Cracking the Coding Interview... I was more than satisfied about getting a job as a "Software Developer" instead of "Software Engineer"... then going home after job, not thinking about job, big O in the shower etc... whats the point of life, if we don't have the time to investigate "this" thing we call living.
Post reply on HN