Remove Engineering Culture Remove Software Engineering Remove Strategy
article thumbnail

Nurturing Design in Your Software Engineering Culture

Strategic Tech

There are a few qualities that differentiate average from high performing software engineering 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.

article thumbnail

You are what you Git: how your VCS branching model affects your delivery cadence

CircleCI

The path of a software engineer is one of constant learning. Before joining CircleCI, my years of experience led me to believe that I was an engineer with a firm understanding of the technical aspects of the craft, as well as what is considered good practice. We learn things from concepts and processes to languages and tools.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Four short links: 18 March 2020

O'Reilly Media - Ideas

The Virus Survival Strategy Guide for Your Startup (Steve Blank) — Unfortunately, it’s no longer a normal market. Software Engineering at Google — a new O’Reilly book. Inklewriter — open source interactive text adventure game creator. That may be no longer true.

article thumbnail

Technical Health Isn’t Optional

O'Reilly Media - Ideas

To help us understand technological health, we asked several CTOs in the Asia-Pacific (APAC) region what their companies are doing to prevent security incidents, how they use open source software, how they use technology strategically, and how they retain employees in a challenging job market. Being Proactive About Security.

article thumbnail

Enhancing Domain-Driven Design Through Collaborative Systems Thinking

Xebia

Domain-driven design (DDD) has emerged in software engineering as a methodology for tackling complex domain problems by connecting the implementation to an evolving model. The cornerstone of DDD lies in its emphasis on collaboration among the domain members.

System 147
article thumbnail

On Not Being a Cog in the Machine

Honeycomb

Someone who can work in both software engineering and automation. It’s related to something cognitive engineers call the context gap. In short, all solutions and strategies we have to solve a problem are contextual and depend on the environment and situation you’re in. Someone able to find balance in all things.

article thumbnail

Anything But Tech Debt

Honeycomb

Of course all of this work could make up a significant portion of a responsible engineer’s quarter or year. The right communication strategy can help While many organizations struggle to prioritize all non-feature work, a few types of work seem to generate the most internal disagreement. Struggling to negotiate time for tech debt?