/Management

How To Access Infrastructure Without Usernames And Passwords

- Ev Kontsevoy tl;dr: Eliminate passwords and other static credentials like SSH keys from your infrastructure, making it more secure, scalable, and easier to use. Stolen credentials are the #1 cause of data breaches — open-source Teleport makes it easy to ditch secrets and embrace identity. Learn more.

featured in #343


Questionable Advice: Is There A Path Back From CTO To Engineer?

- Charity Majors tl;dr: "It is absolutely possible to return after a few years away. And yeah, you could come back as a principal or staff engineer. Someone will definitely hire you. However, I suggest otherwise. I suggest you come back as a senior engineer, writing software every day, for a good 6-9 months. Your grounding in the technical challenges and solution space will be much deeper and richer if you come back hands on than if you came in at a higher level..."

featured in #342


How Engineers Can Tackle Data Privacy And Security

tl;dr: What can engineers do to stay on top of privacy? Most startups are not going to have a dedicated in-house privacy expert at their disposal. Learn how engineers can stay secure while growing a team and a product in Vanta’s recent blog.

featured in #342


How Do I Progress To The Next Level In My Career?

- James Stanier tl;dr: "Progressing, in general, is a two-stage problem: you need to discover where it is that you’d like to go, and then you need to take positive action to work towards it. In my experience, many people over index on the prescriptive “how” before spending enough time on the “what”. The search space of possibilities for your career trajectory is effectively unbounded, and can rarely be predicted over long enough periods of time. This is a feature, not a bug, and should be embraced."

featured in #341


The Secret To Getting To The Staff+ Level? Leverage

- Camille Fournier tl;dr: "You need to develop skills that give you the leverage to show bigger value to the company. These could be interpersonal skills that make you more trusted and valued, execution skills that let you drive complex projects to success, strategic skills that give you bigger ideas and the ability to sell them, or, occasionally, expert skills that make you very hard to replace."

featured in #341


How To Pick A Starter Project That'll Make Someone Quit

- Amir Rachum tl;dr: "Ever had hiring manager’s remorse? It’s where you regret hiring someone immediately after they start. It could be that you don’t like their face, or just want to see the world burn. Worse, they might have mentioned they like jazz. Whatever the reason, this post is here to help you make them quit on their own by picking the worst starter project for them."

featured in #341


Oncall Compensation

- Gergely Orosz tl;dr: Gergely dives into: (1) Oncall philosophies across the industry. (2) Companies which pay and those that don’t. (3) How much do companies pay. (4) Companies which don’t pay. (5) Poor oncall cultures.

featured in #340


“Black Hole Words” And The Power Of Asking Stupid Questions

- Molly Graham tl;dr: Molly warns us of black hole words, which "are commonplace in a given industry but everyone has a slightly different definition of them. You can have a whole meeting and if you don’t define the word, you just wasted an hour of everyone’s time." Molly gives us examples, such as "values", "work-life balance", "impact" and "fast."

featured in #340


How We Work: Moving Fast To Ship Customer Value

- Chris Bell tl;dr: Chris discusses his company's principles for shipping code: (1) Lean into trunk-based development. (2) Ship high quality so each feature "needs to feel cohesive, work near flawlessly, and be the best iteration of itself for it to be valuable." (3) Make it easy for everyone on the team to ship. (4) Keep a weekly changelog to include all of the features shipped over the past week. (5) Optimize for developer autonomy.

featured in #340


Automate Pull Request Labels Based On Changed Files With Actions

- Lloyd Atkinson tl;dr: "That’s a lot of functionality that can be built with labels. As an example, I’ll show how to add labels automatically depending on which area of a codebase has changed. This is what I use in every project I work on as it allows maintainers oversight and awareness of the impacts of changes. It does not depend on the language or types of files - it’s based on the git diff and paths."

featured in #340