Show HN: A Senior Engineer's CheckList

#1

Post by littleblah » Mon, Sep 09, 2019, 12:20 AM UTC

Sharing something that I wrote for my use but I think can be useful to others (I am an engineer with the title of Senior Software Engineer)

Visit [1] for a full list (table view gives a lot of options. See "Controls"). Visit [2] for a summary. The source of the list is at [3]

1. https://littleblah.com/post/2019-09-01-senior-engineer-checklist/

2. https://medium.com/@littleblah/my-top-25-items-in-a-senior-engineers-checklist-c8e9f9f6e3c2

3. https://github.com/littleblah/senior-engineer-checklist

Feedbacks/Pull requests solicited :)

Re: Show HN: A Senior Engineer's CheckList

#2

Post by probablypat » Mon, Sep 09, 2019, 1:14 AM UTC

This is great! Thank you for sharing your experience.

I have a couple questions with your notes about politics.

Could you expand on what you mean when you say "fall back to first principals"?

"If politics thrives due to team of company culture, switch" Could you expand on this if possible?

Re: Show HN: A Senior Engineer's CheckList

#3

Post by visviva » Mon, Sep 09, 2019, 2:11 AM UTC

Normally, this is where I'd chide the OP for using "Engineer" in the title when they really mean "Software Engineer", but (refreshingly) most of the items on this list seem broadly applicable to different types of engineers, so it's not really warranted.

Re: Show HN: A Senior Engineer's CheckList

#4

Post by tmh88j » Mon, Sep 09, 2019, 2:29 AM UTC

Thanks for the list. There are a lot of great suggestions here, but I think the scope is much wider than just senior engineers for a majority of the items. Here are a few that I think are especially important for junior level engineers.

• Question everything and ask “why” repetitively until you get to the root of problems and situations.

• Do not be adamant about your views. Listen to others and accept that there is more than one way to look at a problem statement, and multiple valid solutions to a problem.

• Have strong mentors to help you navigate and grow in the company.

• Read a few technical books every year.

• Actively seek feedback from your manager

The bullets above brings me to halfway through the list, and I feel that I was pretty selective in the ones that I chose. At this point for the remainder of the list nearly every item is one that I'd suggest for any experience level.

Re: Show HN: A Senior Engineer's CheckList

#5

Post by j05huaNathaniel » Mon, Sep 09, 2019, 2:32 AM UTC

visviva wrote: post #3

Normally, this is where I'd chide the OP for using "Engineer" in the title when they really mean "Software Engineer", but (refreshingly) most of the items on this list seem broadly applicable to different types of engineers, so it's not really warranted.

Your comment seems pretty elitist. It's clearly implying that Software Engineers aren't real engineers. I'll admit, not every software developer designs and builds engines (see definition of engine) but many Software Engineers, in fact, do. The principles of engineering are simply applied sciences. Many software engineers have degrees in Computer Science and they are applying the science. I also know plenty of Software Engineers that have Engineering degrees as well. So I guess I'm just wondering why exactly you feel the need to "normally" correct OP? Real question, not trolling. I just want to to understand.

Re: Show HN: A Senior Engineer's CheckList

#6

Post by [deleted] » Mon, Sep 09, 2019, 2:33 AM UTC

[deleted]

Re: Show HN: A Senior Engineer's CheckList

#7

Post by digitalsushi » Mon, Sep 09, 2019, 2:36 AM UTC

probablypat wrote: post #2

This is great! Thank you for sharing your experience. I have a couple questions with your notes about politics. Could you expand on what you mean when you say "fall back to first principals"? "If politics thrives due to team of company culture, switch" Could you expand on this if possible?

If you cannot disrupt a perverted culture by introducing a new culture, the politics of the perverted culture will work against you until you break, align, or leave. It is not unwise to leave before you break and it is easier to leave before you align.

Re: Show HN: A Senior Engineer's CheckList

#8

Post by timdorr » Mon, Sep 09, 2019, 2:37 AM UTC

What is this a checklist of exactly? A list of things to do to become a senior engineer, or things to do once you are a senior engineer?

There is little description or context to this, so I'm not sure what I'm looking at here.

Apologies for being dense!

Re: Show HN: A Senior Engineer's CheckList

#9

Post by ben_jones » Mon, Sep 09, 2019, 2:38 AM UTC

j05huaNathaniel wrote: post #5

visviva wrote: post #3

Normally, this is where I'd chide the OP for using "Engineer" in the title when they really mean "Software Engineer", but (refreshingly) most of the items on this list seem broadly applicable to different types of engineers, so it's not really warranted.

Your comment seems pretty elitist. It's clearly implying that Software Engineers aren't real engineers. I'll admit, not every software developer designs and builds engines (see definition of engine) but many Software Engineers, in fact, do. The principles of engineering are simply applied sciences. Many software engineers have degrees in Computer Science and they are applying the science. I also know plenty of Softwa…

But you can't deny there is a pervasive overuse of the label 'engineer' to cover everything from junior web developers with < 1 year experience all the way to senior roles at major companies. The label has an important meaning to non-technical readers and should be used more sparingly.

Re: Show HN: A Senior Engineer's CheckList

#10

Post by sk0g » Mon, Sep 09, 2019, 2:38 AM UTC

j05huaNathaniel wrote: post #5

visviva wrote: post #3

Normally, this is where I'd chide the OP for using "Engineer" in the title when they really mean "Software Engineer", but (refreshingly) most of the items on this list seem broadly applicable to different types of engineers, so it's not really warranted.

Your comment seems pretty elitist. It's clearly implying that Software Engineers aren't real engineers. I'll admit, not every software developer designs and builds engines (see definition of engine) but many Software Engineers, in fact, do. The principles of engineering are simply applied sciences. Many software engineers have degrees in Computer Science and they are applying the science. I also know plenty of Softwa…

I didn't understand it that way, they expected the list to be software engineering specific (touching topics like Git, CI/CD, etc), but the title gave off the impression that it would be helpful for engineers across all disciplines.

And it was, thus they were pleasantly surprised.