|
Ha I tend to do the designing as I go along. No separate time for it. Or the design comes to me when doing something else entirely unrelated.
Though I suppose I shouldn't really have responded at all, I'm not a professional programmer...yet.
|
|
|
|
|
I consider it "analyzing+planning+designing+coding+testing" and I would I could spend 90% of my work time for coding but can %60-%70.
modified on Wednesday, June 8, 2011 4:35 PM
|
|
|
|
|
Those were the hamster type of developer. Either they code too much at slow phase, or they think too less.
|
|
|
|
|
I do a good share of hardware implementation (circuit design, device UI, microcontroller support components) I also research, develop and test signal processing algorithms for the devices.
After creating the hardware protos, I’ll develop the code and tweak the hardware implantation simultaneously. But once the hardware is pretty much set, I can spend lots and lots of time just coding.
I call it playing, except for the meetings, V&Vs and manditory training sessions (paid nap time... ...Just kidding boss! )
It was broke, so I fixed it.
|
|
|
|
|
I'm salaried, which means I'm contractually obligated to give my employer 40 hours per week of my efforts. I typically work 50 hours or more, which means I'm at work >125%.
I spend probably 90% to 100% of my time working on code.
Around 10% of my time is spent on e-mail and DSJB(*) activities.
15% is spent on non-productive activities like lunch, lollygagging in the Lounge, and so on.
(*) DSJB = Departmental Sh!t-Job Boy: Department server and source control admin, documentation writing, ...
Software Zen: delete this;
|
|
|
|
|
How much they pay you for your job?
|
|
|
|
|
'Salaried' means I'm paid a fixed rate, whether I work 35 hours during the week or 55.
FWIW, I am paid at the top of the scale for my experience level and location.
Software Zen: delete this;
|
|
|
|
|
Gary Wheeler wrote: I'm paid a fixed rate, whether I work 35 hours during the week or 55.
Then why work 50 hours? You are giving away 10 hours a weeks. I personally don't give employers my time. There are the occasional requirements for finishing a project but otherwise those 10 hours are extremely valuable to me; more so than to the employer.
I know the language. I've read a book. - _Madmatt
|
|
|
|
|
While 50 hours per week is the average right now, it's largely due to a new product rollout. Fortunately my boss is flexible if I need to leave early, and I can telecommute on occasion.
Considering the local job market (fairly awful), the economy (so-so), and most significantly my age (50), it would be very difficult for me to find another position that duplicated my current combination of salary (high) and working conditions (excellent).
These factors are a strong motivator for me to give a little extra effort.
Software Zen: delete this;
|
|
|
|
|
|
I think the original question should have been inverted:
How much of your time at work do you spend goofing off?
Or even better:
How many hours a week does your employer 'pay you' for goofing off?
In my case, zero.
Software Zen: delete this;
|
|
|
|
|
|
We work flexitime, so if I do 200 hours of extra work when it's tough, I can even that out later. Best invention since sliced bread.
My boss is very supportive, since he was a coder once as well. If the project leader makes a fuss, he says, My People Don't Work Saturdays. Though we can if we feel we have to.
I am salaried now, but I used to be a contractor once, I remember getting paid by the hour, uff. I wasn't more productive then, probably less, actually.
------------------<;,><-------------------
|
|
|
|
|
We have to report our hours on various projects "for planning purposes". I support two major applications. One week I worked 50 hours. The next I worked 38. The boss's assistant bitched at me for not putting down 40 hours that week. I have no motivation to tell the truth on my "time card" any more.
|
|
|
|
|
Follow the pareto principle.. that is 80% of work is done in 20% of days time
|
|
|
|
|
Get the split right!
Panic, Chaos, Destruction.
My work here is done.
or "Drink. Get drunk. Fall over." - P O'H
OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre
Have a bit more patience with newbies. Of course some of them act dumb -- they're often *students*, for heaven's sake. -- (Terry Pratchett, alt.fan.pratchett)
|
|
|
|
|
--
** You don't hire a handyman to build a house, you hire a carpenter.
** Jack of all trades and master of none.
|
|
|
|
|
and not Code Project. I thought only teenie-boppers used Facebook.
When I waste my time, I only use the best, Code Project...don't leave home without it.
--
** You don't hire a handyman to build a house, you hire a carpenter.
** Jack of all trades and master of none.
|
|
|
|
|
Slacker007 wrote: and not Code Project. I thought only teenie-boppers used Facebook.
Exactly! Could not have been said better.
|
|
|
|
|
Slacker007 wrote: When I waste my time, I only use the best, Code Project...don't leave home
without it.
Excellent material for a signature
"Whether you think you can, or you think you can't--either way, you are right."
— Henry Ford
|
|
|
|
|
It's all yours.
--
** You don't hire a handyman to build a house, you hire a carpenter.
** Jack of all trades and master of none.
|
|
|
|
|
|
Slacker007 wrote: and not Code Project.
Huh, what do you mean? What else did you think "arguing" means?
|
|
|
|
|
I don't believe anybody can devote more than half of work-hours in coding. Too difficult!!! First of all there are too many distractions (as mentioned) and further you can't code (or think abt it) for so long.
Anybody who does, is a machine to me!!!
|
|
|
|
|
You could just be a code monkey, typing out very slowly
My good coding days are usually when all my prep work was done the day before, so I just come in, sit down and hack away.
Don't think... feeeeelllll.....
|
|
|
|