
I'm sure Hameed can empathize with me on this, and most likely others as well...
Today was one of those days at work where I felt like I was going backwards. I was working at trying to implement something in the program I'm writing that changes the underlying structure of how some data is accessed. I had just about got everything working finally, when today I ran into the issue of trying to get the data saved. Unfortunately, at this point a nasty design issue raised it's head, and I realized that in order to solve it I'd have to rip out some of the features that I thought would have been nice, but which I didn't think we'd technically need.
Ok, so I ripped out the features, and got saving implemented, and was moving on to the next piece of the problem when I suddenly realized why we needed those features in the first place. Unfortunately, I need the features, but they can't be successfully implemented because of a basic assumption of the overall system design.
So, now I'm left with trying to figure out an alternate way to implement the feature without breaking anything else in the process.
I worked really hard all day today, and don't hardly feel like I made any forward progress. That's just the way it goes some days. 
Comments
Re: Backwards progress
How similiar is this to every day at work? I mean, this must be fairly typical, isn't it? Perhaps it is called the Two Step -- two steps forward and two steps back!
Re: Backwards progress
I can certainly relate to that. Been there more than I care to think about. It's bad enough when it's someone elses code and I don't really understand why they did what they did. I don't even want to imagine what it will be like when it's my code and my design flaw.
Re: Backwards progress
It's not really typical, otherwise programs would never get written.
Re: Backwards progress
Yes, that'd be true!
Re: Backwards progress
Oooh! That sounds really frustrating!