 |
| Basically, Kevin Smith's character from Die Hard. From http://diehard.wikia.com/wiki/Warlock |
That's a long way from what I do. First of all, it's really hard to get anything useful done in a dark basement. Secondly, a single person typing madly at for hours on end does not create useful software. Useful software comes from patient, well rested software developers who get plenty of sunlight.
A Day in the Life of a Real Software Engineer
6:00
- Wake up
- Feed the dog
- Put on a tee shirt and jeans
- Grab my backpack and lunch
- Drive/bike to work
7:00
- Make coffee
- Check email, news, stocks, etc
- Work on a task
- I can't share real work tasks here, but I can share tasks I'm doing for my open source music player, which are pretty similar in scope and content to what I do at work.
- Here's an example that took a few weeks to get sorted out.
- This one wasn't quite as tricky.
8:00
- Chat with coworkers about an approach to a problem I'm facing.
- Keep working on the task.
9:30
- Attend team meeting
- These generally are about sharing progress ("Here's what I've accomplished, here's where I'm stuck") and clarifying goals.
- Get a big piece of paper to sketch notes and diagrams related to the task I'm addressing.
11:30
- Get hit by flying rubber band (inter-cubical communication).
- Go for a walk.
- Design an icon for a button related to my current task.
- Each lunch.
12:30
- Discuss the downward spiral of M Night Shyamalan's career.
- Brainstorm approaches to a tricky problem.
1:00
- Switch to a different task.
- Discuss status of ongoing office pranks.
1:30
- Get more coffee.
- Read documentation in an empty conference room (to avoid distractions).
2:00
- Do pull ups.
- Switch to standing desk to avoid getting too sleepy.
2:30
- Take a quick nap.
- Update notes on task progress.
3:30
- Drive/bike home
No comments:
Post a Comment