Bear Bibeault wrote:Because every developer's day will be exactly the same...
Jimmy Clark wrote:Sounds like he/she is looking for things to say in his/her next job interview, i.e. wants to say something that sounds "natural."
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Paul Clapham wrote:I don't get it. You are a programmer with no experience, and you are going to a job interview where you imagine the interviewer will ask you about the typical day of a programmer? I haven't had a job interview for a very long time but that sounds quite unlikely to me.
9:51 Split back of new pants while wiping up coffee
9:55 Use packing tape in bathroom to repair pants enough to attend meeting without revealing the color of my underwear
Slawomir Wieczorek wrote:Thank you Joanne.
Bear Bibeault wrote:9:50 Spill coffee on floor when coffee machine spits hot coffee at me
9:51 Split back of new pants while wiping up coffee
12:30 Return to work, coffee machine shows error 14490, "reboot" coffee machine
2:30 Get more coffee, coffee machine is out of beans, refill machine
Joanne
Joanne Neal wrote:Ever thought of drinking tea ?
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Sai Surya, SCJP 5.0, SCWCD 5.0, IBM 833 834
http://sai-surya-talk.blogspot.com, I believe in Murphy's law.
Jeanne Boyarsky wrote:I like how Bear's day prominently features coffee.
Bear Bibeault wrote:
9:50 Spill coffee on floor when coffee machine spits hot coffee at me
9:51 Split back of new pants while wiping up coffee
9:55 Use packing tape in bathroom to repair pants enough to attend meeting without revealing the color of my underwear
Jeanne Boyarsky wrote:.... to show how different two consecutive days can be.
When you do things right, people won't be sure you've done anything at all.
Janeice DelVecchio wrote:6a - leave for work
9a - arrive at work
Luke Kolin wrote:
Janeice DelVecchio wrote:6a - leave for work
9a - arrive at work
Luke
When you do things right, people won't be sure you've done anything at all.
Sai Surya wrote:Here is what I was doing from last 2 months in my new job.
1. 9:30 Come to office.
2. 9:30 - 10:00 Read online news papers.
3. 10:00-10:30 Javaranch.
4. 10:30-12:00 Read technical books (PDFs).
5. 12:00-12:30 Lunch
6. 12:30-1:30 Reading news updates
7. 1:30-2:30 Facebook
8. 2:30-3:00 Linkedin
9. 3:00-5:00 Reading process oriented stuff (RUP, Agile)
10: 5:00-6:00 Javaranch
11. 6:00 Go home
I am really bored of this schedule and I haven't given any serious work until now.
I am about to ask my lead for any contribution I can make.
However, people around me also seems to be having same schedule like me. Trying hard to keep my mind out of rust.
There are only two hard things in computer science: cache invalidation, naming things, and off-by-one errors
fred rosenberger wrote:7:30 - get to work
7:31 - read email, check ranch, a few tech blogs
8:00 - start working on my work
8:01 - get interrupted by someone who needs me to "Look at this RIGHT NOW"
8:06 - get interrupted looking at whatever that was by someone else who needs me to look at THEIR problem RIGHT NOW
8:09 - get interrupted by someone else...
8:17 - resolve one of the issues.
random 5-10 minute intervals throughout the day - do my own work on my projects
repeat similarly all through the day
4:00 go home
Weeks when I carry our PRODUCTION pager are even worse
http://www.lifesbizzare.blogspot.com || OCJP:81%
Don't get me started about those stupid light bulbs. |