Skip to content

Sponsor: Do you build complex software systems? See how NServiceBus makes it easier to design, build, and manage software systems that use message queues to achieve loose coupling. Get started for free.

Learn more about Software Architecture & Design.
Join thousands of developers getting weekly updates to increase your understanding of software architecture and design concepts.


Follow @CodeOpinion

Practices

Continuous Integration vs Continuous Delivery vs Continuous Deployment

Continuous Integration is a term/buzzword that seems to have a clear understanding.  Continuous Delivery and Continuous Deployment on the other hand, seem to get incorrectly interchanged. Continuous Integration Continuously integrate changes into source control in order to test changes through automated builds and unit tests.  This provides developers with early warnings of broken code/merges and allows them to fix problems continuously. Continuous Delivery Some have the opinion that continuous delivery is when you deliver to a user base, such as UAT or QA.  I personally disagree.  Continuous delivery is about making sure your software is always production ready. via Jez… Read More »Continuous Integration vs Continuous Delivery vs Continuous Deployment

Reality of fixed price & fixed scope

Fixed price, fixed scope development contracts are still a very relevant and are not likely going away.  Clients want a to know how much they are going to spend and exactly what they are going to get.  The reality is, iterative development was created because they don’t know (entirely) what they want up front. Waterfall is still primarily used, however the reality is, it’s more of a business decision than a development decision. Same old story… We spend a great deal of time up front gathering business requirements and attempt to create a specification of our interpretations of those requirements. … Read More »Reality of fixed price & fixed scope

Specialization vs Generalization

Depending on your location and the amount of opportunity may ultimately decide which side of the fence your on. For me, understanding why a tool/framework exists and the problem is solves is much more important than understanding how to use a specific tool/framework. Anytime the hiring discussion comes up, I am always reminded of this.  While do people classify themselves this way in a resume?  Django Developer?  I guess if you only want to develop in Python using an MVC framework, then sure.  But doesn’t this tend to lead to “When all you have is a hammer, everything looks like… Read More »Specialization vs Generalization