Senior Engineer Mindset

Description

Why senior engineers get nothing done When you're new life is great When you're seasoned though How this happens to you Ownership takes time Force multiplying takes time What you can do to protect your coding time Timeboxing Optimization Ask good questions and help others ask good questions What makes you a senior software engineer anyway? So how do you become a senior engineer? Certainty makes the difference Computer science is not software engineering Why study computer science then? How to get the most out of a comp sci degree? What if you never studied comp sci? Your career needs a vision What's going on here Working IN your career vs. ON your career Why you should work ON your career, not just IN your career How to work ON your career Whatever it is, do something What a hockey legend can teach you about career development Skate where the puck is going From a sea of options, how do you choose How to grow as a senior engineer or why I got a new job Growing senior talent 1) Management 2) Entrepreneur 3) bigger company with bigger problems 4) become junior in new thing Why engineers are worth so much How engineers build assets Use this concept to up your salary Your work is worth different to different people Why you should talk about engineering salaries But mention money and everyone loses their shit Consider your value Why sharing salaries helps everyone In conclusion Should you work at a startup The modern Silicon Valley hustler is an employee with the mindset of a freelancer Startup vs. BigTech vs. Start Your Own BigTech Startup Start your own So what do you do? Should you take a pay cut for equity What is equity How equity becomes cash money RSUs and stocks Options Vesting and exercise windows Preferred shares To take cash or to take equity What I learned while 6x-ing my income in 4 years Freelancing / consulting The Job job The side hustle The flip-side What's next What if engineers were paid like athletes Old incentives in tech New incentives in tech Who do companies hire when engineers need to bring home the bacon? What if you were paid like an athlete? What about the athlete thing? How to make what you're worth even if you're from the wrong country How your environment holds you back 1 Change your environment 2 Upgrade your attitude 2.5 Think about value 3 Income arbitrage 4 Increase your value You got dis 4 years of coding in San Francisco, lessons learned Your code won't matter if you're dead You die a prototype or become that code everyone hates to work with Don't fix it until it breaks Relax constraints If your code doesn't matter, what does? San Francisco is expensive but worth it The environment pushes you SF is not an entrepreneurial mecca ️ Building software is a distraction Software is a tool, not a goal People buy your solution, not your software DO more work less The Jar of Life Oh and buy time if you can Focus What's more productive, a team or a talented soloist? A soloist can move fast Surgical teams do best How to succeed as a lead engineer – tactics and mindsets from practice How to succeed as a lead engineer It's a shift in mindset So what do you do Create a Slack channel Keep a checklist Daily standup Post a standup recap Delegate Communicate like a boss How to own projects like a senior engineer Overcoming obstacles Excuses and reasons ``it wasn't in the story'' Own the outcome, not the work Surgical teams How Grit superchargers your career Why grit What's grit How grit wins How you can be gritty How to grow gritty people How to teach yourself What about passion? Why programmers work at night The maker's schedule The sleepy brain Bright computer screens Fin My favorite lessons from Pragmatic Programmer The Cat Ate My Source Code Good-Enough Software DRY—The Evils of Duplication Tracer Bullets Prototypes and Post-it Notes Engineering Daybooks Don't Outrun Your Headlights Transforming Programming Inheritance Tax Shared State Is Incorrect State Programming by Coincidence Coconuts Don't Cut It Delight Your Users Why great engineers hack The Process A process is born Nothing gets done anymore You get to work Code is just a checklist Time to deploy HOW great engineers hack The Process Hacking The Process So how What I learned from Software Engineering at Google Software Engineering vs. Programming Beyonce rule and Hyrum's law Shift left Automate common tasks Stubs and mocks make bad tests Small frequent releases Upgrade dependencies early, fast, and often Expert makes everyone's update