• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

My boss the dunder head

HumblePie

HumblePie

Lifer
So, I'm designed a brand new archival process for one of our software products along with a simple database to keep track of the archives. I need to generate a Software Design Document, all the previous documentation had been done up to now.

For the database, in it I specify table names, field names, field types, records, querys with explicit conditions, forms, any explicit macro, any explicit VB code, any explicit joins, command buttons, algorithms, reports, and general layouts. Reading over it, ANYONE who has ever tried programming a database would instantly be able to figure out how to make one from the volume of information I gave. Something like 75 pages with screen shots.

Now my boss comes back and says it too vague and it should be written as a design document so that anyone reading it can write the database from scratch. WTF?!?!?! Is he smoking crack? He told me it needs to be so that the govt. folks (ones who can barely figure out how to turn their computers on) will be able to read, understand, and make a database from that document.

Uhhh.. design documents aren't for NON CODERS. They are for coders. Grrr.... I want to slap him so hard. What does he want me to write? an Intro to computing, intro to programming, and intro to databases ALONG with my design document so any one could write my coding project? Holy crap!


Cliffs..
Geek hates boss.
 
Usually, in the dev process there is a fundamental or basic design. It is signed off on, then there is the detailed design.

I work with momos, that say, go and get me a rock. Come back, No not that rock, get another one, try again.

Functional requirements, business logic, all that crap...most do not know what they heck they want in the first place.

bunchomomos
 
Originally posted by: HumblePie
So, I'm designed a brand new archival process for one of our software products along with a simple database to keep track of the archives. I need to generate a Software Design Document, all the previous documentation had been done up to now.

For the database, in it I specify table names, field names, field types, records, querys with explicit conditions, forms, any explicit macro, any explicit VB code, any explicit joins, command buttons, algorithms, reports, and general layouts. Reading over it, ANYONE who has ever tried programming a database would instantly be able to figure out how to make one from the volume of information I gave. Something like 75 pages with screen shots.

Now my boss comes back and says it too vague and it should be written as a design document so that anyone reading it can write the database from scratch. WTF?!?!?! Is he smoking crack? He told me it needs to be so that the govt. folks (ones who can barely figure out how to turn their computers on) will be able to read, understand, and make a database from that document.

Uhhh.. design documents aren't for NON CODERS. They are for coders. Grrr.... I want to slap him so hard. What does he want me to write? an Intro to computing, intro to programming, and intro to databases ALONG with my design document so any one could write my coding project? Holy crap!


Cliffs..
Geek hates boss.
Click to expand...

being a "gov't folk", I certainly do know how to turn a computer on! 😉
 
Originally posted by: dquan97
being a "gov't folk", I certainly do know how to turn a computer on! 😉
Click to expand...

that's great... now how about the other 100 people working around you?

I was talking about MY govt/ folk I deal with, not you.

I'm writing code for THEM, not the other way around. I don't need to make a design document which explicitly states how I am going to write that code understanable by them at all. I just need to make sure I can understand it or another coder who knows anything about coding and databases could repeat my work based off the design document so that they would be able to fulfill the requirements by following what design I layed out.
 
why don't you eat some humble pie and DO IT! j/k

I hate writing manuals, such a PITA. 75 pages and I would have killed myself.
 
Originally posted by: HumblePie
Originally posted by: RaDragon
Your Cliffnotes needs a detail or two. 😉
Click to expand...

I'm not Barnes and Nobles, you are lucky to get even that for cliff notes.
Click to expand...

The cliffnotes doesn't accurately describe the frustration you feel.

I'm sorry man. Have fun writing computers for dummies.
 
Originally posted by: 777php
why don't you eat some humble pie and DO IT! j/k

I hate writing manuals, such a PITA. 75 pages and I would have killed myself.
Click to expand...



HAHA, I just did 30 pages of requirements, a 10 page "pre-requirements" document, and 180 page software test plan BOOK. Don't get me started on how much paperwork I did for my last project.

I spend more time writing the documentation and then "dumbing it down" so that anyone could understand it, or so my boss likes to think, then I do actually doing my real job. GAH!
 
Originally posted by: RaDragon
Your Cliffnotes needs a detail or two. 😉
Click to expand...

Actually, I think it covers it pretty well.

7/10 on the rant scale for lack of anger
10/10 on my sympathy scale... I relate BROTHA!!!
 
Here's a direct cut&paste quote from my boss's email to me about my design document. Bear in mind, this is a design document for creating a database

When you get time, go back through and add some more information that would allow someone who may not have any knowledge of databases, ####, etc. to implement your design (we're not proposing that someone else do your work, but we need the document to be understood by the govt. folks).
Click to expand...

I had to put #### to remove the name of something that can not be posted in public forums. Sorry.

Still, a design document is BLUE PRINT. Think of blue prints for houses, if I give a blue print to a housing developer, any housing developer, I'm pretty sure they can figure it out well enough to make me a house from it. If I give a housing blueprint to my barber, I'm pretty sure he would not be able to make me a house from it. My boss is asking me to create a blueprint such that my barber could make something from it with no prior knowledge.

I so want to hurt him.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top