Stop me if you’ve heard this one
I mean, sure. You can try to convince { the other devs | your client | your boss } that that component needs to be a WCF Service written in C# 4, hitting the database with Massive, and that you ought to look into slapping ELMAH in there to help with those late-night support calls.
But { the servers are only running .NET 2.0 | we don’t use Open Source here | we’re a VB shop }. And there isn’t a thing you can do about it.
So. What can we do to reconcile this gaping void between your fire-breathing potential as a software god and your boss’s to do list? Not long ago, my colleague Dan Fischer posted here extolling the virtues of maintaining an app that has nothing to do with your day job. I’m here to second Dan’s approach—perhaps even to third and fourth it. Because there is nothing like one hundred percent ownership of a codebase to learn you up a thing or two about writing software.
Do You Have A Pet Application? [ Aptera Software ]
