4 ms·
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?
by nottorp 4y ago
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?
- kevingadd 4y agoAt 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.
- actually_a_dog 4y agoWhich, 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.
- nottorp 4y agoNone 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.
- actually_a_dog 4y agoI disagree. I think the list of 50 is an entirely reasonable set of expectations for a senior (or at least staff+ level) engineer, with the caveat in my previous comment that not all of these things need to be done explicitly, every time, on every project. Like another commenter said, being able to articulate something isn't the same as explicitly doing it. I also realized, I'd put a small asterisk on "I have recently profiled the performance of my system," as well. I would expect that an engineer would do at least some minimal profiling of their code in order to make sure it's not too slow in itself and doesn't excessively slow down any calling code, but for the most part, with a running production system, it's generally safe to assume that performance is good enough unless you've been shown or told otherwise. And I think that all still fits into the spirt of the expectation as well.
- vsareto 4y agoThis list will impede velocity by quite a lot, especially with coming up with and implementing Plan B's
- MajimasEyepatch 4y agoYou only implement the Plan B if Plan A fails. Plan B doesn’t have to be elaborate. It can be as simple as, “I’m going to look into using this third-party service to solve 99% of this problem, but if it isn’t a good fit or it’s too expensive, I think we can put together a home-grown 80% solution in a couple of sprints.”
- vlunkr 4y agoOne of the points is "I have already implemented my Plan B in case my solution to my current problem doesn’t work." So that's not what they're advocating. Though I think they're 100% wrong on that point, and most managers would probably think so too.
- nottorp 4y agoWell one case where it can make a lot of sense is when Plan B is a quadratic/exponential solution that can be written in one day but there are complex to write/research item solutions that are much faster for Plan A. Same for single threaded vs parallel etc.
- vinay_ys 4y agoExpecting an engineer to do all of this even when they are at odds with rest of the execution machinery is simply not practical. It leads to heroic behaviours and burnout. I hope this guy has a complimentary list of 50 things for other roles.