This post originated from an RSS feed registered with Java Buzz
by Michael Cote.
Original Post: Working Around Problems
Feed Title: Cote's Weblog: Coding, Austin, etc.
Feed URL: https://cote.io/feed/
Feed Description: Using Java to get to the ideal state.
At work, we're doing a lot of integration on the current version: with a new, large frameworks, with a large product, and many other small things. Even "beter," we're integrating with these things before they're complete. I think that's about par for course in the industry -- unless you're on some decade long defense contract, there's not much time for getting your ducks in a row before you start crisply executing.
Anyhow, one skill that's become very important is working around problems. By that I mean that when you encounter a problem/bug/issue that's out of your control -- a change in third party frameworks, for example -- you have to be able to come up with a way to live with it without fixing it.
For example, you might be working on some screen that depends on a domain object existing to modify or create. But, that domain object isn't there. Or, worse, it was there, but it's been changed. Instead of just throwing up your arms and waiting for someone else to fix it, you need to figure out how to work around it.