Live data from Hacker News

Expectations of professional software engineers

adamj.eu

11–20 of 116 posts

Re: Expectations of professional software engineers

#11
On one hand, well yes, everything mostly makes sense.

On the other, I can easily imagine the reaction from most project managers if they'd asked me put together an estimate for fully achieving all of these on any given project. Some of them would involve sitting in on business strategy meetings, which is a pretty far cry from the level of involvement I generally get! It's sometimes hard to even get hold of representative hardware to test on.

Re: Expectations of professional software engineers

#12
Personally - I don't see a lot of value in this list (I read all 50 items and watched the video and I regret wasting the time).

There are certainly some valuable concepts - but the presentation is fairly incoherent (including the video of the talk he gives) and not particularly helpful.

Many of these items are utterly unrelated: Some are fairly specific to gaming (profiling/memory layout/timing) some are basic professional expectations (I can schedule my time well). In neither case is there real advice for people who actually struggle with some of these areas.

My item number 51 would be... "I can articulate my point in a more compelling manner than an incoherent collection of 50 things I don't like"

Re: Expectations of professional software engineers

#13
post #7

How much would they pay for someone who satisfies all 50 points? Where is the company that gives engineers enough freedom to satisfy all 50 points?

At the end of the day, the people signing paychecks care more about their priorities than they do about these 50 points. But they can be useful to keep in the back of your mind when making decisions that aren't governed by anyone else.

Re: Expectations of professional software engineers

#14

This is a great resource, thank you! Gives me a lot of actionable concrete issues to work on. Maybe I'm just very early in my career or it has to with the subfield I am in (bioinformatics, machine learning) but I should have been fired 20 times over by these standards.

The reality is that in a healthy workplace, you could whiff on 25-30 of these and not get fired, because a healthy workplace gives employees guidance and room to grow. Eventually with enough time in that place you'd be at 40+. Of course, some of them (like professionalism) are basically non-negotiable. But nobody starts at 100%.

Re: Expectations of professional software engineers

#17
post #7

How much would they pay for someone who satisfies all 50 points? Where is the company that gives engineers enough freedom to satisfy all 50 points?

Which, if any of the list of 50 do you think is unreasonable? I don't always explicitly do all of these things all the time on every project, but I'm certainly _capable_ of doing so. For example, working in backend web dev, I generally don't go into it thinking explicitly about, say, memory usage, as long as my monitoring tools are not telling me there's a problem. Of course, there are exceptions, which is why I said "generally" (for instance, if I know I'm making a query to the DB that's going to yield 100k results, I'll definitely be thinking about memory usage), but I also don't just YOLO it and see if things crash.

Re: Expectations of professional software engineers

#18

This is a great resource, thank you! Gives me a lot of actionable concrete issues to work on. Maybe I'm just very early in my career or it has to with the subfield I am in (bioinformatics, machine learning) but I should have been fired 20 times over by these standards.

The reality is that in a healthy workplace, you could whiff on 25-30 of these and not get fired, because a healthy workplace gives employees guidance and room to grow. Eventually with enough time in that place you'd be at 40+. Of course, some of them (like professionalism) are basically non-negotiable. But nobody starts at 100%.

Let's be honest here, a green junior or intern could easily whiff on 45+ of these things and not get fired, as long as they're in a healthy workplace and they have a growth mindset. I literally tell interns at my company that I basically expect them to know fuck all, and that their opportunities at the company are mostly limited by their work ethic, their willingness to ask questions, and their desire to accept and incorporate feedback.

Re: Expectations of professional software engineers

#19
I view these less as actionable items, and more as character hallmarks. No you don't need to actively be making sure you're doing All The Things by iterating through this every day. Yes these are things that should be captured by your company's best practices, and your own professional integrity.

Re: Expectations of professional software engineers

#20
post #7

How much would they pay for someone who satisfies all 50 points? Where is the company that gives engineers enough freedom to satisfy all 50 points?

Which, if any of the list of 50 do you think is unreasonable? I don't always explicitly do all of these things all the time on every project, but I'm certainly _capable_ of doing so. For example, working in backend web dev, I generally don't go into it thinking explicitly about, say, memory usage, as long as my monitoring tools are not telling me there's a problem. Of course, there are exceptions, which is why I said…

None of them. But all of them combined. And they never are all part of the same job description; except perhaps in an organization small enough to not have job descriptions.
Post reply on HN