Effective Staff Plus

 This is the first part of a five part series on influence as a Staff+ Software Engineer ( part 1 ,  part 2 ,  part 3 ,  part 4 ,  part 5 ).  I've ported this here from where I  originally published it on Medium . 

 Once upon a time there was a whole series of interesting books about leaning programming languages that followed the same loose format: a series of related practical tips for using them well and avoiding pitfalls. This blog is all about Staff+ software engineering and it'll try to follow the same basic format.  Each post will have a concrete tip.  A few things to note: I'll be typing the words here but many of the ideas are from other people.  I'll be linking out to their docs or websites and putting credits wherever I can.  If I miss one then please let me know and I'll fix it. This isn't written by AI, it's just me and a keyboard. This will always be free here. I'm leaving comments off for now as I'm comfortable with this being write-only and don't want to try moderating them. No ads. For fun, here are a few links to some of the books: Effective C++ Effective Java