Under the hood and working with .Net, TDD, Software Design, and Agile Stuff
Browse by Tags
All Tags »
Legacy Code (
RSS)
-
|
In a conversation last week I was asked for my recommendations on how to retrofit automated testing and build processes into an existing system. I'm not going to dissemble at all, it's hard. Moreover, I think rescuing existing code from the brink...
|
-
|
I'm a card carrying member of the SOA skeptics club, but I'm going to push for a dose of SOA thinking to my current client. I do understand the potential benefits of things like BAM, BPM, and flexible orchestration if the entire enterprise were...
|
-
|
Before you go on, I'm specifically worried at the moment about "Logic Intensive Systems" here. Systems that perform complex calculations, make optimizations, determinations, decisions, etc. Many, if not most, enterprise applications have...
|
-
|
The blogosphere is full of discussions and arguments on the best way to write and design software. It might be worth the effort to stop and go back to first causes -- just what quality or qualities do we want in our code? What are we trying to achieve...
|
-
|
Tip #1 - Go get a copy of Michael Feather's " Working Effectively with Legacy Code " book. If you take away one thing from this post, that's it. The book is full of good ideas for decoupling legacy code and retrofitting tests, but there's more to the...
|
-
|
Uncle Bob Martin has a post up called Wading through Code where he talks about becoming a better developer by reading someone else's code. The value of reading good code, or just plain different code, from someone else is obvious, and you'll pick up plenty...
|
-
|
I added an exciting new feature to our suite of applications this week. Not "seeing Star Wars for the first time" exciting or maybe even Ajax/Web 2.0 cool, but something that will definitely make our collective lives easier. I added environment tests...
|
-
|
At the last Agile Austin lunch we were talking a little bit about the infrastructure improvements we’d all like to be making, if only there was time. We talked about improving our continuous integration builds, retrofitting legacy code with more automated...
|
-
|
...you don't know where they've been, or who's been touching them. I've been burned pretty badly in the past by making assumptions about existing databases. Database documentation isn't always helpful either, because it is out of date or just wrong to...
|
-
|
If you've been reading the Shade Tree Developer this week you'll know that I'm fighting with a legacy component. I was trying to get a piece of code into NUnit to test my new functionality. A class in the stack works by giving it a key value to a record...
|
-
|
I'm a ReSharper junkie, and I get angry when I don't have it. I've spent the majority of my .Net career working with converted Java developers. To a man, they all complained about the crudeness of Visual Studio.Net compared to IntelliJ or even Eclipse...
|
-
|
My colleague and I are making minor extensions to some legacy code (in C#) for the next month or so (and that generally implies that the Shade Tree Developer will feature quite a bit of ranting in the near future). After that my team will be making some...
|
-
|
Yesterday I griped about legacy code. I carped about VSS, whined about the tight coupling, groused about the arcane configuration setup, and spewed invective about the stupid manual post compilation steps it took just to make the code work. Today it's...
|
More Posts