I think it’s a bad practice to simply blame the previous developer or team for something. Give them the benefit of the doubt and assume that they made the best decisions they could under the constraints they had. They didn’t have the knowledge of the fully baked system.
I’ve definitely been guilty of this in the past, but am trying to be more cognizant of this behavior, especially when I see some of the ham-fisted “solutions” I implement to meet a dictated deadline.
Q:So - what technology stack do you currently develop in?
My development time is spent in mostly Microsoft technologies. New development is mostly using ASP.NET MVC (along with several JS libraries) while legacy support is ASP.NET 2.0 web applications. We have a rather large project going on right now where we are re-engineering our applications to work with a new SAP system being put in place.
Aside from that, I’ve spent a lot of time in SQL Server Integration Services and Oracle SOA Suite over the past two years.
I’m finding I’m more and more interested in the development process as a whole. I’ve recently taken on setting up a deployment system for my team’s various applications targeting different environments. I have a prototype of Octopus Deploy that I’m showing off later today.
I’m gonna get my blog going again.
The topics will vary: technology, programming, pictures I take, being a new dad, living where others retire, hobbies, food, games (video and board), and whatever else comes to mind.
Eventually my A.D. Bower related domains will point here, both 80bower.net and eightybower.com.
Follow, subscribe, comment, or ask questions!