Software

It may sound counterintuitive to say that a software product is not about code. Sure, it’s the output of what software engineers do but there’s a much more important series of events that happen before that. One of the more fundamental components is communication.

I've been trying to come up with a definition of what a good software design or architecture is (here I'm kind of using the two words interchangeably). What are the characteristics of a good design versus a bad one?

Almost everyone building software has adopted some form of agile in the past decade. The concept of an agile workflow has even spilled into other departments within companies - devops, data engineering and sales all talk about it. Yet on software teams, people seem to be unhappy about their process.