Explore >> Select a destination
|
You are here 
|
stackoverflow.blog | ||
| | | | |
continuousarchitecture.com
|
|
| | | | | This article is part of a series that provides practical advice and guidance on how to leverage the Continuous Architecture approach. All these articles are available on this blog. Here we will discuss the "Minimum Viable Architecture" concept that we introduced in our original "Continuous Architecture" book[1]. A full discussion of this concept, including some... | |
| | | | |
www.jrothman.com
|
|
| | | | | In Effective Agility Requires Cultural Changes: Part 1, I said that real agile approaches require cultural change to focus on flow efficiency, where we focus on watching the work, not the people. Too few organizations can do that. But teams can change how they work-in any approach. Here are three suggestions to emulate flow efficiency [...] | |
| | | | |
www.startuppatterns.com
|
|
| | | | | When will the team be ready to ship?" There is probably no question we engineers hate more than that one. For as long as I have been building software, bumping up against 20 years now, I have observed engineers, engineering teams, and engineering managers squirming in their conference room chairs, frantically waving their hands, and saying just about any words they can think of - words like "dependencies" and "technical debt" and "build process" - to avoid directly answering that question. | |
| | | | |
www.softdevtube.com
|
|
| | | Programming history is filled with bugs that turned out to be features and limitations that pushed developers to make even more interesting products. We'll journey through code that was so 'bad' it was actually good. Along the way we'll look at the important role failure plays in learning. Then we'll tame our inner perfectionists and | ||
