Join 135,938 Programmers for FREE! Get instant access to thousands of experts, tutorials, code snippets, and more! There are 2,689 people online right now. Registration is fast and FREE... Join Now!
Well Im at work for 9 hours, where at least 6.5 of those is spent actually coding, then theres meetings and researching items to code. Then when I get home I usually code until bedtime.
Well Im at work for 9 hours, where at least 6.5 of those is spent actually coding, then theres meetings and researching items to code. Then when I get home I usually code until bedtime.
Then you must have a twin, otherwise I don't know when do you flood dic with posts and tutorials
our focus factor is at a .5 which means 8(.5)hours of working for the client a day. So what happens in the other 4 hours? Darts...candy...food and more food...documentation...sifting through debug mail...R&D...wait no, R&D included in the focus factor...so I guess....2 - 3 hours of actual coding
Hmm... I get flooded by user requests, emails and phone calls. There'd be days where I fire up Visual Studio, but never got to write a single line of code. Because I'll be answering emails and phone calls, doing production support, server maintenance, SSL certificates and a whole host of other stuff.
I swear my users have my phone number on speed dial. I've even gotten calls where the first thing I hear is "Oh, sorry I actually wanted to call another person...". They've gotten used to calling me for answers remotely relating to the applications I support. Flattering, but still...
Anyway, when I do get the chance to code (for work), I'm usually able to crank out stuff. I make the time I have count, so I think and design a lot. I probably only have one chance at coding, so I make sure it's coded right the first time. I'm sure you'll hear many people here talk about the importance of design.
Code it once, code it right. Because you might not have time to debug it.
Some days I'll code 9 hours straight. Other days when there are distractions in the office I'll only get to concentrate for 40 mins at a time before something comes up and I have to focus on something else.
I prefer to have 2 hour chunks where I can concentrate totally before doing something else for bit. Lunch is always a priority for me if possible because I go running. Then I'm fired up for the afternoon.
I probably spend about 6 hours a day coding and sometimes more on the weekends. I don't have much spare time because I work as a software developer and take computer science graduate classes. I get up at 4:00AM just so I'll have time to work out every day. In between semesters I travel, play guitar, garden/landscape my house, and usually take one of the MIT EE/CS opencourseware courses that interests me (at a leisurely pace). Oh - and I also try to learn a little bit more about one of the languages that interest me (Russian, Spanish, Latin, etc.). If I could, I would add another 6 hours to each day to do whatever I wanted.
right now I am working 8 - 12 hour days 6-7 days a week. Sometimes I spend the day coding, but most of the time I am messing around with associated applications (set up and deployment to the app. server, configuring application program that I interact with etc.) -- Generally this is a trial and error process as I am a programmer not a administrator on the platforms I am developing for. I figure that after I have more experience in these environments I will be able to redistribute my time.
I also spend a good bit of time in research. Truth is, I don't spend all that much time actually coding... once I know what I need to do, and how to do it, things go pretty quickly.