Reconciling assholes for nearly a decade.

Phew!

Finally my boss has ordered that our team start from scratch and build software with minimal functionality initially and then build on it.
This is after 3 months of haggling, groping with daylight saving time related bugs, and many attempts to repair and enhance a system whose parts were being held together by chewing gum.

Sad part is - he wants me to write the spec and not show it to the customer (what a bright spark). Did I forget to say that the spec was never written and neither was any vision document, biz plan or for that matter even an issue list.

I must start writing articles on coconut herd management; nothing else could bring some light into this beleaguered team.
I didnt post this anywhere because I want to have some excruciating details from you guys who've been through this earlier.
Permalink Vineet Reynolds 
January 21st, 2006
>> groping with daylight saving time related bugs <<

Easy fix: Always store date/time in UTC. Only change it to local time just before showing it to a human. And back again immediately after they've editted it.

Best of luck, btw. I've seen analysis paralysis before, and it's all too easy to blow through money while not producing a salable product. It sounds like your management has realized that's what's going on, so that's the first step!
Permalink example 
January 21st, 2006
>>Only change it to local time just before showing it to a human

Half of the problem is that the webservice runs on a server with Indian time, and it caters to US customers (in possibly 8 different time zones).
Permalink Vineet Reynolds 
January 21st, 2006
Local time according to the users' profiles, not according to the server.
Permalink KC 
January 21st, 2006

This topic was orginally posted to the off-topic forum of the
Joel on Software discussion board.

Other topics: January, 2006 Other topics: January, 2006 Recent topics Recent topics