greatist annoyance...being a coder :)

[icyrus]

People who don't know the limits of their knowledge.

 

[FarligOpptreden]

People who don't know the limits of their knowledge.

Like me? I haven't reached mine yet...

 

[Raithlin]

clients changing database schemas to allow nullable fields

Ooh, I'll see your nullable fields, and raise you "outsourced development company supplying dev database for integration - with no primary/foreign keys AND all nullable!"

Did I mention sketchy docs?

 

[RaptorSA]

Another annoyance - managers think who think that adding more people at the later stages of a project helps make deadlines

LOL...yeah, that AND when managers decide to do the project time allocation THEMSELVES for a technology they've never worked on before.

 

[RaptorSA]

Ooh, I'll see your nullable fields, and raise you "outsourced development company supplying dev database for integration - with no primary/foreign keys AND all nullable!"

Did I mention sketchy docs?

I see your nullable fields and zero key database, and raise you "sketchy unusable docs and integrating new database (that changes almost daily) with an old database (no keys, nullable field, horrible field names, terrible design), then the decision to redo the old database 2 YEARS (yes, you read it: 2 YEARS) into the project and integrate with existing "new" code. ALSO, changing database structure based on THE REQUIREMENTS as they "pop" in out of thin air (no -acceptable- initial design, 2.5 tier with business objects etc. on top of it all)...and doing data migration at THE END of the project.

oh, and err... did I mention there's been almost no considerable user testing and the new code is already 2 years old?

 

[FarligOpptreden]

They should write a book called "The Mythical UAT-Month"...

 

[Veroland]

Way up on ny list is not being able to test / debug locally

 

[koeks]

Working with messed up data that needs to be migrated is also another one...

 

[PsyWulf]

I see your nullable fields and zero key database, and raise you "sketchy unusable docs and integrating new database (that changes almost daily) with an old database (no keys, nullable field, horrible field names, terrible design), then the decision to redo the old database 2 YEARS (yes, you read it: 2 YEARS) into the project and integrate with existing "new" code. ALSO, changing database structure based on THE REQUIREMENTS as they "pop" in out of thin air (no -acceptable- initial design, 2.5 tier with business objects etc. on top of it all)...and doing data migration at THE END of the project.

oh, and err... did I mention there's been almost no considerable user testing and the new code is already 2 years old?

I'll see you that chaos with the following:
Maintaining 5 seperate versions of a specific database,varying fields based upon different needs at the times,with a central multi-user system that accesses these and is built to be compatible with these differing databases,including processing invoices using different numbering styles and date formats into a coherent mess and updating each database with new transactions or edits

 

[Raithlin]

I see your nullable fields and zero key database, and raise you "sketchy unusable docs and integrating new database (that changes almost daily) with an old database (no keys, nullable field, horrible field names, terrible design), then the decision to redo the old database 2 YEARS (yes, you read it: 2 YEARS) into the project and integrate with existing "new" code. ALSO, changing database structure based on THE REQUIREMENTS as they "pop" in out of thin air (no -acceptable- initial design, 2.5 tier with business objects etc. on top of it all)...and doing data migration at THE END of the project.

oh, and err... did I mention there's been almost no considerable user testing and the new code is already 2 years old?

You win. I fold.

 

[Raithlin]

Not sure if I mentioned this one before, and too lazy to go check.

Picture, if you will: Business comes up with a basic plan (1 page pie-in-the-sky URS). Steering Committee (All business, mind you) thumb-sucks timing and budget for approval purposes. Timing and budget are approved. Now the fun begins. BA is pulled in to spec project, etc. All continues as per normal, except (don't laugh, I've seen this happen more than once) the budget and time-to-completion remains as per the one page high-level pie-in-the-sky thumb-suck!

I'm going to go to the corner and cry now.

 

[Necuno]

no coffee

 

[FarligOpptreden]

no coffee

You win. Thread now closed!

 

[RaptorSA]

no coffee

Before the end of this day, dead...you will be

 

[friedpiggy]

Oh heck no. I would leave if there was no coffee. I can deal with all the rest, but no coffee? Isnt that against the Geneva convention or something?

 

[nfbs]

Well I am more of a implementor/coder.
1. What I hate is having to ask for access to the program source code, design docs but it gets treated as some sort of state secret. IP puke.
2. Project plans that don't reflect the work and flow of the work that need to be done
3. Get given projects on such short notice like a 2 month project in 2 week so I have to arrange travel, visa etc in a rush.
4. Me supporting all the systems, helping out others who get stuck but not being credited for it.
5. 2 month notice period.
6. And the worst is: American jerk management forcing "garbage in garbage out" time consuming illogical global processes thinking they are adding value.

 

[Necuno]

Before the end of this day, dead...you will be

heh.... my work pc 'died' before the end of the day due to the cooling of the gpu failing so i had it send it in for fixind and then took rest of day off

 

[FarligOpptreden]

Very nice... You have fancy-schmancy GPUs in your work PC?!

 

[Necuno]

Very nice... You have fancy-schmancy GPUs in your work PC?!

heh... how else can i blow the **** out of the rest of the programming team without a gpu

good for stress releiving, fun and teambuildish- we game luch times

 

[FarligOpptreden]

Heh - we used to have our Counter-Strike lunch-times, but sadly as the work load picked up, the lunch times disappeared. That was almost 2,5 years ago!