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.
Expectations of professional software engineers
11–20 of 116 posts
Re: Expectations of professional software engineers
#12There 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
#13How 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?
Re: Expectations of professional software engineers
#14This 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.
Re: Expectations of professional software engineers
#15Re: Expectations of professional software engineers
#16Re: Expectations of professional software engineers
#17How 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?
Re: Expectations of professional software engineers
#18This 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
#19Re: Expectations of professional software engineers
#20How 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…