Until a certain point in your career you’re likely to be told the strategy for your company. If you need guidance, you’re able to look up to the people above you.
Being an engineer, we all have at least one common thread: We like to build things. That is why writing code and architecting platforms that scale for millions of customers is appealing.
Technology is fast moving, and devops tools pop up like wildfire. Teams are desperate to solve their problems & often make implementation decisions based on word of mouth, “kick the tires” syndrome or superficial evaluations.
When they work well, OKRs have the potential to be a powerful tool that can clarify vision at all levels of the business, all while providing autonomy for smaller functions to set their own goals and objectives.
Hiring engineers is hard. And with over half of C-suite executives saying that the future of their company relies on being able to source engineering talent, making the correct decisions about who to hire has the potential to transform the fortune of your company.
SRE and infrastructure engineering are about allocating adequate time to do project work that improves the long-term sustainability of our services. But what do we reward SREs for doing? Does your company have a culture of "not invented here" or the converse of "ask the consultants to design it for us"?
If you think back to the work you were doing last year, it probably feels miles away - and that’s great! As engineers, we’re continually building and creating great new stuff - it’s what we do.