|
We're a small shop undergoing huge transformation and modernization, so I spent most of the last four or five years working with JBoss server administration, environment setup, and creating and responding to use cases and test cases. I wrote code last month for the first time since I can remember (not including updates to legacy code to keep it up and running).
Can't wait to get back to writing code. Wait, cannot do that next week, I am in training for some of the proprietary stuff our vendor plugged into our system. So coding has to wait another week. Well, the week after that it's Admin training for the same plug-in. Then the advanced designer class. I hope to write code again in June...
|
|
|
|
|
10%-25%
My nose is in code much more than that, but often it's fixing screw-ups by users. Sometimes, however, serial screw-ups lead to a new interface so they can do it themselves.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
|
Slacker007 wrote: a proactive effort,
In theory we should all follow that route.
My users, however, might well be a confluence of HR and IT's server administrators - each giving the employee a different uid for login (or, it's happenend where they have two uid). This ![Elephant | [mastadon]](https://www.codeproject.com/script/Forums/Images/elephant.gif) 's up the works big time. Direct manipulation of the database is often required AFTER they reconcile just what the real uid is to be.
Causes data attribution problems and data access problems. In a few cases, I even created the admin page for fixes and updated (for the IT server mob) and they still can't get around to fixing a problem until you make them do it.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Mainly coding.
Fortunately, I am not required to attend many meetings.
10% - on design, etc.
Edit: currently, I am working on an existing web app, and thus design/etc. percentage is not very high.
modified 2-Apr-18 6:20am.
|
|
|
|
|
If you do a lot of re-factoring you should think about better architectural concepts.
PS: I cant believe that 
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
not a lot of refactoring. It's an existing site that grows/scales based on client requests. We add to it more than change it.
KarstenK wrote: PS: I cant believe that
Why is that so hard to believe? What kind of shop do you work in, where as a software developer, you are not paid and expected to be heads down coding, rather than bullshitting with your friends and surfing the internet?
|
|
|
|
|
Because nobodies job is "just coding" - we all have to read a specification, interpret it, work out what we have to do as a result, design, code , test, redesign, recode, retest, repeat, release.
Getting the code down is the easy bit! It's all the other stuff that takes the time, but strictly that is part of the "development experience" which includes the mechanics of converting your design (be it for a single method or a whole app) into something the compiler will accept.
I'd count "coding" as sitting in from of VS typing...
So I've gone for 50 ~ 75 %, but I don't think it's really accurate. Thinking about it, it's probably more like 10 ~ 20 %
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
My interpretation is "any activity directly related to code", starting at the first problem analysis brainstorming, ending with committing the revision log, completing the release checklist.
The other fairly well defined alternative is to count the time when the source code editor is the active application, and you are actively typing program statements.
If you, in the second alternative, include the time spent leaned back, considering whether you should write the loop as a for loop or a while loop, then you are doing code design, not coding. There is no clear and well defined line over to more significant choices, such as deciding upon a data structure, code modularization, thread/process design, ... Typing code statements is at one end of the scale, including everything from problem analysis to revision log is at the other end, and the scale between them is continuous. The only well defined points are at the ends; any other is an arbitrary choice.
Even if you count in everything code related, jore time is spent at non-coding than most people believe. You chat with colleagues about how they spent their Easter holiday. You discuss what kind of qualities you should ask for when announcing a new position in the company. You fill in your travel expenses report after that customer visit. You answer to CP Surveys 
So I simply do not trust those who claim they spend 90+ % of their time coding. Even 80% is on the high side; that is when you include the time when you appear to be doing other things (such as group meetings, going to the bathroom etc.), but you mind is still at the code, planning how you will be writing the code statements as soon as you get back to the keyboard.
When I was a student, I was expecting wroking life to be 100% coding. I guess I learnt different the first week of my first job. And I have never been close ever since.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
