This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
As a software engineer or individual contributor, the next step in your career can be to become a principal engineer. The path to becoming a principal engineer at companies can feel unclear, which can inhibit individual engineering careers. By Ben Linders, Joy Ebertz, Pablo Fredrikson, Charlotte de Jong Schouwenburg
She joins a special livestream of the Dev Interrupted podcast to share her career journey, her strategies for sustainably scaling engineering teams and the three pillars of engineering processes. Her lessons on team management, building company culture, hiring and mentorship are not to be missed!
This is a transcript of my keynote presentation for the Regional Scrum Gathering Tokyo conference on January 8th, 2025. It was September 2023, my CEO was asking me a question, and my position as Vice President of Engineering was less than three months old. This is a big cultural shift! How are you measuring productivity?
Upon reflecting on the conference, and my experience now two months into my first software engineering job at LaunchDarkly, I wanted to share a smattering of thoughts with you as a woman in tech. At LaunchDarkly I have experienced similar intellectual honesty, one of the many facets of our outstanding engineeringculture.
Our existing deploy tooling and engineeringculture made the transition to remote work go much more smoothly. Though our deploy velocity remained the same, the engineering org has been far from stagnant. For DevRel, 2020 was the year of the virtual event. It is not normal, it is not necessary, it is costly as f**k.
Our existing deploy tooling and engineeringculture made the transition to remote work go much more smoothly. Though our deploy velocity remained the same, the engineering org has been far from stagnant. For DevRel, 2020 was the year of the virtual event. It is not normal, it is not necessary, it is costly as f**k.
In 1988, Berkley scientists David A Patterson, Garth Gibson, and Randy H Katz presented the paper A Case for Redundant Arrays of Inexpensive Disks (RAID) [3] at the ACM SIGMOD Conference. He realized that such enthusiasm could not surface in his company, because the culture did not value good engineering. This is lean.
We organize all of the trending information in your field so you don't have to. Join 49,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content