Stop generating, start thinking
Instead of wanting to learn and improve as humans, and build better software, we’ve outsourced our mistakes to an unthinking algorithm.
Instead of wanting to learn and improve as humans, and build better software, we’ve outsourced our mistakes to an unthinking algorithm.
Tackling some common questions, including: what does an engineering career in a larger organisation look like? What actually is a staff engineer? How long should you stay at the same company? Do I even need to progress?
Three years ago I wrote a post listing everything I googled in a week. I'm a senior engineer and web eng lead now, and guess what: I still google a lot. Here's everything I googled in a week, 2022 edition.
In an attempt to dispel the idea that if you have to google stuff you're not a proper engineer, this is a list of nearly everything I googled in a week at work, where I'm a software engineer with several years' experience.
When you're talking about what you're working on, do you ever stop to think about what you're saying and whether the person you're talking to can actually understand it?