|
 It's not you that's unloved - it's the task of documentation.
Most developers recognise the importance of documentation but hate having to do it. I would hope, therefore, that they would welcome having a tame documentation specialist to do it for them. (You are tame, aren't you?)
Phil
The opinions expressed in this post are not necessarily those of the author, especially if you find them impolite, inaccurate or inflammatory.
|
|
|
|
|
Well, you have to 'splain your definition of "tame".
Me friends says I'm wild and crazy, but work-wise I'm very diligent.
I'm not meek by any means.
S.Nowlin
-----------------------
The journey is straight, it's the path that is twisted. Oh and did you hear? There is no spoon, only sporks.
|
|
|
|
|
The number of times I could have used someone like you makes me sick. Working alone my answer to upfront documentation or creation during development, was usually something like “do you need the documentation or do you want it finished on time?”
Once time after the project application was complete and ready to go, I said now I can do all that documentation (as I had planned for). The answer was no, we need you to work on this other project now. Very frustrating as I was looking forward to a change of pace; oh well. 
INTP
"Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra
|
|
|
|
|
I freelance!!! 
S.Nowlin
-----------------------
The journey is straight, it's the path that is twisted. Oh and did you hear? There is no spoon, only sporks.
|
|
|
|
|
am I using CListCtrl? If I'm not, the likelihood of completing the job in a reasonable and sane time frame is probably not within the problem domain that you've set for yourself. On the other hand, it might be simpler to go out, have a few beers with your buddies, and just contemplate Chuck Norris counting to infinity.
¡El diablo está en mis pantalones! ¡Mire, mire!
Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)!
SELECT * FROM User WHERE Clue > 0
0 rows returned
Save an Orange - Use the VCF!
VCF Blog
|
|
|
|
|
How often would the boss/client be happy, if the job matched the initial spec ?
Christian Graus - Microsoft MVP - C++
"I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )
|
|
|
|
|
Very rarely I suspect. That is why it is often a moving target. 
INTP
"Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra
|
|
|
|
|
What makes the Boss happy and what makes the Client happy are usually at odds with each other. The Boss usually wants the projects done on time and under budget. The Client usually wants all their features, plus a few more that they just thought up a day before the deadline. As scope starts to creep as it often does there is a fine line to be walked. An extra feature can normally be put in here or there when time is left over, but if hours are tight the client starts to hear "No" when they ask for changes.
The boss will be happy you said no to new features or changes but the clients won't be.
The extent that this becomes an issue is based on the company you work for in my experience. I've seen both extremes. I worked for one company that would gladly burn clients at the stake as long as we got paid. I've also worked for a company that would loose money on a client just to make sure they were happy in the end.
As a employee who likes to receive paychecks I make sure the boss is happy first.
|
|
|
|
|
What a pedantic lot you all are 
regards,
Paul Watson
Ireland & South Africa
Andy Brummer wrote: Watson's law:
As an online discussion of cars grows longer, the probability of a comparison involving the Bugatti Veyron approaches one.
|
|
|
|
|
thrakazog wrote: As a employee who likes to receive paychecks I make sure the boss is happy first.
I'm my own boss - if my client is happy then I'm happy.
In my case, I voted 5 for this one.
|
|
|
|
|
Come on guys, when is the boss ever happy
Why is it when you are busy everyone whats it yesterday, But when your not no-one has any work for you?
|
|
|
|
|
This, my friend, is a corralary of Murphy's Law.*
*Murphy's Law was, not, in fact, named after Murphy, but was actually named after someone else with the same name!
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
|
|
|
|
|
Just curious. I've seen so many promising products release to a big fanfare and rave customer reviews that (not too much) later are rotting on the vine because fixing bugs and adding unforeseen features are nearly impossible.
Dale Thompson
|
|
|
|
|
"The job is fully documented
The design and implementation was first rate"
Those go some way towards maintainability, right?
regards,
Paul Watson
Ireland & South Africa
Andy Brummer wrote: Watson's law:
As an online discussion of cars grows longer, the probability of a comparison involving the Bugatti Veyron approaches one.
|
|
|
|
|
Maintainability is WITHOUT A DOUBT covered in Design and implementation.
Mike Tsouris
Developer
http://tsouris.net
michael@tsouris.net
|
|
|
|
|
Sure - someone is paying me to make something for them.
But, the reason I'm in this business is because I love coding.
It's no different than a painter or composer;
Or a chemist or physicist.
I hope I include most of you when I say this is our art.
A fine piece of work - a clever routine or an imaginative solution: because we are more and better than an a cooks following recipies on a boxes.
That our work wasn't merely done by the book - but beyond it.
Why else do this for money?
"You sell all your hours for a handful of dimes . . ." - Jimi Hendrix
|
|
|
|
|
I agree. What we do is an art and we all take pride in it......
BUT. DO NOT FORGET that....
Oracle costs a crap load of money
SQL Server licenses costs a crap load of money
WINDOWS SERVER costs a crap load of money
20 licenses of VISUAL STUDIO 2005 for your development team costs a crap load of money
Where does that money come from?
The business. We code for money FIRST. Just like musicians and artists who work for commissions, we all have to set aside our own preferences when we are doing this as a professional gig.
I love a beautiful architecture as much as the next senior programmer, BUT, money talks, and there are many times when we have to PURPOSEFULLY make a piss poor sh*t design because that is what fits in budget and time line.
good programmers know how to make it work inside these real world parameters.
THE MOST IMPORTANT PART OF ALL THIS IS DELIVERY.
Bugs can be fixed and are considered acceptable in our culture.
Look at the .NET Framework..... Have you ever profiled "hello world" in a .NET app? It uses like 20mb of memory! But who cares, because the point is rapid delivery of working applications.
Optimization and beautiful architecture is a LUXURY.
Mike Tsouris
Developer
http://tsouris.net
michael@tsouris.net
|
|
|
|
|
I thought the money part was implicit in "Sure - someone is paying me to make something for them."
One of those things that seems clear to the writer and not quite so to the reader. Perhaps I was feeling too much the poet?
The whole thing does revolve around the money. I make them pay me, too.
For that matter, sex really revolves around reproduction. That works, if that's all one cares to make of it. Whore's do it purely for money; and lovers for the unequaled beauty of the shared expression. You can fill in the in-between mitigations as you wish.
I'm not unaware of the cost of things - I just like to pretend to myself they're of no importance, taking pleasure in the plan while it yet unfolds, as though it were alive.
"Life is just a bowl of all-bran.
You wake up in the morning and it's there."
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
|
|
|
|
|
I agree for the most part.
The one thing though, is, the fact that one can put a lot of stress on themselves in the daily grind if they put priority on the finer things of programming.
Take for instance, a scenario where a project's deadline and resources don't really accommodate for the best architecture. If you find yourself caught up in the "preferred" approach, ie. making the most extendable and elegant architecture possible, you can basically doom the project yourself from day one, by not realizing that it's only a job, and you just have to make something that works.
The sales manager will NEVER pat you on the back by adding built-in support for interoporability for older platforms or using reflection for dynamic greatness..... they just want to see it work. You'll get a promotion MUCH faster by making a reputation of always delivering. It's amazing how forgiving people can be of "bugs".
I am not criticizing your comment, it just reminded me of how I Personally used to approach things (the most ideal way) and how, after several months of 70 hour work weeks, i realized to detach my personal investment of pride from the actual project.
I'm not saying do a sh**ty job all the time, just try to find that balance between ART and DELIVERY.
Mike Tsouris
Developer
http://tsouris.net
michael@tsouris.net
|
|
|
|
|
|
I can not agree more!
That is how I have always felt about coding. Good code is an art form and a thing of great beauty. It makes it easier to maintain and understand. Due to time constraints, or other reasons, I have not always been able to create great art, but I do try.
At one point in my career I had nightmares about the code I inherited. I am not sure if I would have taken him under my wing or requested that he be fired. I know the true meaning of spaghetti code and have learned how to straighten out some amazing messes.
My favorite analogy has always been that of an author creating story: research, outline, write, and rewrite; with attention to detail. You do not design your character by placing his head in one place and his arms, legs, and body in a dozen others.
INTP
"Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra
|
|
|
|
|
The programmer, manager, CEO/stock holder and client/customer will all have different priorities.
Hence the conflicts we have in any development effort.
Marc
|
|
|
|
|
Having a good PM to run interference between development and clients takes some of these conflicts away, or at lest pushes them further away.
only two letters away from being an asset
|
|
|
|
|
in software development, it is quite common that the budget is an amount of working hours; the longer the developers spend on a project, the more the project will cost. I would be surprised to see the two values differ too much.
just my two cents
Federico
|
|
|
|
|
Federico Sasso wrote: in software development, it is quite common that the budget is an amount of working hours; the longer the developers spend on a project, the more the project will cost.
Not necessarily. The client may say they need the project completed in three months (by the calenday) but only want to pay for 6 man-months of development effort despite the fact that in order to get it in on time it will take 3 people (i.e. 9 man-months)
So, they are going to have to trade off something.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
