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. So we need to make it part of everything we do.
It’s been a fascinating opportunity to rebuild an engineering organization from the inside, and I’m loving every minute. We’re introducing a lot of cutting-edge software development practices, such as self-organizing vertically-scaled teams and Extreme Programming. Culture doesn’t change easily. It tends to snap back.
Softwareengineering productivity cant be measured. We use Extreme Programming as our model of how to develop software. You see, Extreme Programming is too. Its a big spreadsheet which describes each title in our engineering organization, along with the skills required to reach each title.
PDF) Culture Changes The purpose of the new career ladder is to help change the engineeringculture at OpenSesame. Just as the ladder sets new expectations of engineers, the management track sets new expectations for managers, with material about managing the system rather than just managing the work.
This post was written by Stig Brautaset, CircleCI Senior SoftwareEngineer, in collaboration with Cian Synnott, CircleCI Senior Staff SoftwareEngineer. Retrospectives are a well-established resource in the software and systems engineering toolbox. cf “Railway Oriented Programming”, [link].
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.
finding good softwareengineers takes so long and requires so much effort… but it doesn’t have to. If you like the ideas in the post, then why not come and join me at Navico and help us to build a highly-innovative engineeringculture and a brilliant place to work. Hiring is so hard?—?finding extremely well.
This can span from: Creating on-call rotations and associated supporting materials, like handover communication methods Running an ops-focused Office Hours Building out a Learning from Incidents program The increasing number of irreducible dimensions within software systems and the changing relations between them requires contributors to adopt an attitude (..)
Any significant shift in an organization’s softwareengineeringculture has the potential to feel tectonic, and observability (o11y for short)—or more specifically, Observability Driven Development —is no different.
While my engineering experience is deepest in frontend technologies, I am very grateful to have built early experience in a number of shops that did pair programming and brought a DevOps mindset to their work. Working across the stack.
What was the first programming language you, you ever recorded in and you still use that? And for the first few months, I was just doing things like discussing different bits and pieces about programming and all I had was a paper to write different things on. Uh, so yeah for me the first programming language is Pascal.
E : Programming in an overly-defensive manner is probably the big one! 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. Q: What are some bad habits you had to unlearn from other companies?
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. “I want to make video games.”
This practice, while small and often overlooked, can have a significant impact on the overall excellence of a softwareengineering project. The true power of these small actions lies not just in the immediate time saved, but in the cumulative effect they have on the organization's engineeringculture.
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.
Nor would many popular programming languages, including Go, Rust, Python, JavaScript, and Ruby. Chander Damodaran of Brillio noted that, “the culture of sharing solutions, frameworks, and industry-leading practices” has been a crucial part of Brillio’s journey. More importantly, open source has unleashed tremendous creativity.
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.
For example, right as I was transitioning into this role, I did inhumane things with my own schedule to quickly build out our SOC 2 and HIPAA compliance programs at the request of our go-to-market leaders.
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