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
There are a few qualities that differentiate average from high performing softwareengineering organisations. In my experience, the culture is better and the results are better in orgs where engineers and architects obsess over the design of code and architecture. They prefer to work in isolation and just deliver.
While helpful in pinpointing known-unknowns, it impeded the team’s ability to explore the workings of the software, particularly in uncovering unknown-unknowns. It also fell short in supporting an engineeringculture of ownership and curiosity within the organization, exacerbated by the pricing model.
Expensify founder and CEO David] Barrett, a self-proclaimed alpha geek and lifelong softwareengineer, was actually Red Swoosh’s last engineering manager, hired after the failure of his first project, iGlance.com , a P2P push-to-talk program that couldn’t compete against Skype.
The future of observability has never been more exciting, and this latest round ensures we can continue to invest—with conviction—in improving the lives of softwareengineering teams. We hope this is a moment of welcome change from the soul-crushing headlines plaguing the tech industry these past few months.
Our engineeringculture embodies the essence of open source, and it’s a small contribution to the community ? And being one of the industry leaders in hackathons, we had a reputation to uphold! by Anagaha, SoftwareEngineer from Suki). a token of respect, a small payback. Entertainment break — Stand up comedy.
The official definition of DevOps is “a softwareengineeringculture and practice, that aims at unifying software development and software operation.” The concept of Site Reliability Engineer (SRE) has been around since 2003, making it even older than DevOps.
However, we haven’t seen any discussions of “technical health,” which suggests that industry at large doesn’t know what differentiates a company that’s been through a successful digital transformation from one that’s struggling. Similarly, Tim Hope said that open source is critical in building an engineeringculture and developing systems.
Someone who can work in both softwareengineering and automation. The more time I spend in this industry, the more interested I get about that social aspect of our systems. Initially, as a software developer, it’s tempting to frame the software as an independent system that you work on.
He describes “some surprising theories about softwareengineering”: I discuss these theories in terms of two fundamentally different development styles, the "cathedral" model of most of the commercial world versus the "bazaar" model of the Linux world. If you give softwareengineers manual work, their first instinct is to automate it.
It seems every week there is an article or blog post decrying the lack of women and people of color in softwareengineering, or on the other side defending the gap. At LaunchDarkly I have experienced similar intellectual honesty, one of the many facets of our outstanding engineeringculture.
Common patterns: what are the responsibilities of a Principal Engineer. He or she is one of the key faces of engineering and the company and enables awareness of the company while attracting talent and participating in tech conferences. Principal Engineer is in charge of driving engineeringculture.
VPs of Engineering often have a lot of influence over both company culture and policy, and the decisions our companies make ripple outside of the companies themselves. The whole tech industry would benefit from more perspectives in this role. However, we have fairly different backgrounds and skill sets.
And for me, the big part of the success of growth was actually a step above the pure engineering architecture. It’s firstly rooted in the engineeringculture because the first Netflix employees are great people. So I think I was becoming more of a generalist over time. I agree with you on the Python bit. Thanks for that.
I wouldn’t go as far as to say “tech industry therapy,” but Honeycomb leadership’s investment in good management is something I haven’t seen before. doesn’t turn any heads; everyone I’ve talked to has experience with what it takes to build a great organization (and product), from all different perspectives of the industry.
That’s fascinating because it touches on so much of what you know and I’ve been in softwareengineering for a couple of decades now, a couple of days, decades, but sounds like couple of days. I do like that the industry seems to be getting better at management. As well we’re kind of learning from the industry.
Softwareengineering productivity cant be measured. The question of measuring productivity is a famous one, and the best minds in the industry have concluded it cant be done. Its a big spreadsheet which describes each title in our engineering organization, along with the skills required to reach each title.
But as the engineering manager there, I grew a team from zero. A team of me to a team of about somewhere between 20 and 25 softwareengineers. All focused on trying to level up Indeed’s front end engineering capabilities. The technical project manager role was actually pretty new. Ben Vinegar: Yeah.
Perhaps surprisingly, those two trends don’t usually translate to making a startup VP of Engineering job one of the most lucrative in the Bay Area. Honeycomb has long taken a principled approach to compensation and sticks to relatively narrow comp bands shaped by industry data from similar stage companies. Is there friction?
On the self-regulation point, I can’t emphasize enough how much the tech industry has managed to externalize the burden of learning and keeping up with things onto its workers. Sabbaticals like this are a smart way to highlight these issues without needing to lose employees to burnout to discover them.
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