Earlier quoted context omitted.
Promoted to what though? A job with more responsibility but not really a good enough increase in pay to go along with it? No thanks.
Exactly, why are you chasing promotions? Isn't it ok to be happy with where you are and have satisfaction? My title is Sr Software Engineer. My boss keeps bringing up in our 1 on 1s about what we should do to carve out a path for a promotion to "Principal Engineer" but I don't care. The small amount of pay bump is just not worth the added responsibility (not to mention the hoops they make you jump for the promotion).
Books that changed my career as a software engineer
41–50 of 295 posts
Re: Books that changed my career as a software engineer
#42Just the section on correlation vs causation is invaluable.
Re: Books that changed my career as a software engineer
#43I'm not sure how any of these books have anything to do with actual career advancement. Career trajectory improvements are generally catalyzed by high-risk business decisions (e.g. doing a startup, joining as an early employee, job hopping, etc.), or political posturing (e.g. getting promoted, gaming the stack ranking, aggressive negotiations, etc.). Being a good engineer doesn't really have anything to do with eithe…
Re: Books that changed my career as a software engineer
#44Is there a good book on object oriented programming for beginners? By beginners I mean people who code regularly but aren't software engineers.
Re: Books that changed my career as a software engineer
#45Earlier quoted context omitted.
Anything you recommend instead? Personally, I got a lot of value from Designing Data-Intensive Applications by Martin Kleppmann.
* Mythical Man Month (Experience) * Rapid Development (Profession) * Epistulae Morales ad Lucilium (You're not alone, we all share this.) * The War of Art (At 9am, you are alone.) * Competitive Advantage (Porter, a personal choice, it's not about the bytes.)
* For those who don't already know, it's a very quick read. And the type of book you'll gladly reread every one to three years.
Re: Books that changed my career as a software engineer
#46I'm not sure how any of these books have anything to do with actual career advancement. Career trajectory improvements are generally catalyzed by high-risk business decisions (e.g. doing a startup, joining as an early employee, job hopping, etc.), or political posturing (e.g. getting promoted, gaming the stack ranking, aggressive negotiations, etc.). Being a good engineer doesn't really have anything to do with eithe…
You do in fact seem to negative, and have a take on life that is a bit more cynical than reality. Completely dismissing any value in actually being a good engineer for career advancement for instance is a bit over the top. Suggesting companies always don’t care about employee opinions as well. Real life is pretty bad sometimes but not universally dystopian.
Ah yes, the same companies that laid off mass numbers of engineers in 2000 and did it all over again in 2008. The same companies that vehemently fight any kind of unionization efforts and the same companies that insist to haze potential hires with live-coding & whiteboarding tests even though folks have 10+ years of experience. The same companies that were wage-fixing employees' salaries and had to pay out almost half a billion dollars in restitution[1]. Those companies? If you think you have any kind of influence on corporate culture as random engineer #3419, I've got a bridge to sell you.
[1] https://www.npr.org/sections/alltechconsidered/2015/01/16/37...
Re: Books that changed my career as a software engineer
#47I'm not sure how any of these books have anything to do with actual career advancement. Career trajectory improvements are generally catalyzed by high-risk business decisions (e.g. doing a startup, joining as an early employee, job hopping, etc.), or political posturing (e.g. getting promoted, gaming the stack ranking, aggressive negotiations, etc.). Being a good engineer doesn't really have anything to do with eithe…
Re: Books that changed my career as a software engineer
#48Earlier quoted context omitted.
Promoted to what though? A job with more responsibility but not really a good enough increase in pay to go along with it? No thanks.
Exactly, why are you chasing promotions? Isn't it ok to be happy with where you are and have satisfaction? My title is Sr Software Engineer. My boss keeps bringing up in our 1 on 1s about what we should do to carve out a path for a promotion to "Principal Engineer" but I don't care. The small amount of pay bump is just not worth the added responsibility (not to mention the hoops they make you jump for the promotion).
Re: Books that changed my career as a software engineer
#49I think the generic bit of this advice is to excel as an engineer is to focus on the business, not the tech.
Re: Books that changed my career as a software engineer
#50I'm not sure how any of these books have anything to do with actual career advancement. Career trajectory improvements are generally catalyzed by high-risk business decisions (e.g. doing a startup, joining as an early employee, job hopping, etc.), or political posturing (e.g. getting promoted, gaming the stack ranking, aggressive negotiations, etc.). Being a good engineer doesn't really have anything to do with eithe…
I find Outliers' chapter on Chinese people and rice field preposterous. It was like reading astrology: The entire Chinese people have grit, and their grit came from growing rice because it was such a laborious job. Really? Really? Really? Did the author even know that for thousands of years, it was the Northern China that dominated the history, and Northern Chinese largely grew wheat? And the book said Chinese were g…