--- title: "Nice article on ordering code construction tasks by Jeremy Miller" url: "https://osherove.com/blog/2005/11/26/nice-article-on-ordering-code-construction-tasks-by-jeremy-m.md" canonical: "https://osherove.com/blog/2005/11/26/nice-article-on-ordering-code-construction-tasks-by-jeremy-m.html" published: "2005-11-26T23:32:00" updated: "2005-11-26T23:32:00" tags: ["Agile Related", "Architecture", "Cool Articles", "Project Management"] author: "Roy Osherove" description: "Jeremy Miller has some sound advice and an interesting read on the order of code construction (a nice \"Where should I start building my project, and how do I continue to implement the various pieces of the…" usage: "Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page)." license: "https://creativecommons.org/licenses/by/4.0/" --- # Nice article on ordering code construction tasks by Jeremy Miller By Roy Osherove November 26, 2005 In [Agile Related](https://osherove.com/blog/category/agile-related), [Architecture](https://osherove.com/blog/category/architecture), [Cool Articles](https://osherove.com/blog/category/cool-articles), [Project Management](https://osherove.com/blog/category/project-management) **Historical article** · Originally published November 26, 2005; technical details may be outdated. [Jeremy Miller](http://codebetter.com/blogs/jeremy.miller/) has some sound advice and an interesting read on the [order of code construction](http://codebetter.com/blogs/jeremy.miller/archive/2005/11/26/135098.aspx) (a nice "Where should I start building my project, and how do I continue to implement the various pieces of the infrastructure" piece) _"it’s easier to make a change by going around a framework or drilling exception cases into a framework with “if/then” statements, you’ve created a viscous framework that’s might be causing you more harm than good.  If you start to hear the phrases “can’t we just go around the framework?” or “this would be easier without the framework” or even worse “we need to get \[Some Guy\] to change the framework first” you’ll know that you’re going down a painful path with your framework. "_ _"Time and time again I’ve learned or observed that projects go much smoother when you build vertically instead of horizontally.  What I mean by this is that you build a new system by creating a feature at a time with the entire stack of UI, business logic, and database work to make the feature fully functional.  As you build new features you religiously eliminate duplication to avoid creating a_ [_Stovepipe anti-pattern_](http://c2.com/cgi/wiki?StovepipeAntiPattern) _and harvest reusable code."_ This is a good read mostly because Jeremy talks out of his own experiences and also failures, taking pride in what h and his teams have learned from them. [Subscribed](http://codebetter.com/blogs/jeremy.miller/rss.aspx). ## More in Agile Related [All posts in Agile Related](https://osherove.com/blog/category/agile-related) - Dec 4, 2005 ### [Special Agile Israel Meeting with Johanna Rothman: Moving Towards Agile Project Management](https://osherove.com/blog/2005/12/4/special-agile-israel-meeting-with-johanna-rothman-moving-tow.html) - Nov 28, 2005 ### [Agile Israel meets today! The Planning Game](https://osherove.com/blog/2005/11/28/agile-israel-meets-today-the-planning-game.html) - Nov 24, 2005 ### [Test-First vs. Implementation-First : What Microsoft really meant](https://osherove.com/blog/2005/11/24/test-first-vs-implementation-first-what-microsoft-really-mea.html) - Nov 23, 2005 ### [Webcast: Agile and eXtreme Programming from patterns & practices (Level 200)](https://osherove.com/blog/2005/11/23/webcast-agile-and-extreme-programming-from-patterns-amp-prac.html) --- ## About the author **Roy Osherove**: Senior Solutions Architect at AWS working on AI for production and AI-driven development; author of The Art of Unit Testing and Elastic Leadership, with about 20 years of consulting and training on unit testing, TDD, team leadership and continuous delivery. ### Sites - [RobotPaper](https://robotpaper.ai/): This blog: AI patterns and anti-patterns, AI and coding agents, and engineering leadership. - [osherove.com](https://osherove.com): Roy's personal site. Author of The Art of Unit Testing and Elastic Leadership; consulting and training on unit testing, TDD, team leadership and continuous delivery, plus about 20 years of blog posts. - [The Art of Unit Testing](https://www.artofunittesting.com): The Art of Unit Testing, 3rd Edition (Manning): readable, maintainable, trustworthy unit tests, plus TDD workshops in C#, JavaScript, Java and Kotlin. - [5whys.com](https://www.5whys.com): Roy's writing on software team leadership: self-organizing teams, surviving chaos, learning mode and the Elastic Leadership model. - [Pipeline Driven](https://pipelinedriven.org): Continuous delivery and DevOps practices: build patterns, pipeline-friendly testing, DevOps metrics and enterprise DevOps. - [Elastic Leadership](https://www.elasticleadership.com): Elastic Leadership, Roy's framework for software team leaders (survival, learning and self-organizing modes). ### Social - X: https://x.com/royosherove - LinkedIn: https://www.linkedin.com/in/osherove/ ### Contact - Contact form: https://forms.gle/jQSx5KoXvrVA1JCK7 ### License Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page). License: https://creativecommons.org/licenses/by/4.0/