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.
What I’m really doing is changing the engineeringculture at OpenSesame. Culture doesn’t change easily. I’m hoping this will help direct people to new behaviors, which will in turn start to change the engineeringculture. Associate SoftwareEngineers Associate SoftwareEngineer 1s are at the start of their career.
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.
Softwareengineering productivity cant be measured. Its a big spreadsheet which describes each title in our engineering organization, along with the skills required to reach each title. For example, Associate SoftwareEngineers are hired fresh out of university. This is a big cultural shift!
Domain-driven design (DDD) has emerged in softwareengineering as a methodology for tackling complex domain problems by connecting the implementation to an evolving model. Resistance to change, entrenched organizational cultures, and the theories’ complexity can pose significant barriers.
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. What is a personal retrospective?
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.
These include running regular training and enablement sessions like Lunch & Learns, publishing a newsletter, advising on or collaborating on custom instrumentation libraries, and supporting the general observability toolset. That light touch frees them to sprinkle in more targeted interventions.
The SRE team is now four engineers and a manager. We are embedded in teams and we handle training, vendor management, capacity planning, cluster updates, tooling, and so on. We are involved in all sorts of things across the organization, across all sorts of spheres.
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.
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.
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. Similarly, Tim Hope said that open source is critical in building an engineeringculture and developing systems. That’s an important statement.
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