Slashdot Mirror
Workplace Monotony?
bcorrigan78 asks: "I love programming, however I work in a network operations center with very few co-workers where the air conditioners can just about put you to sleep. Besides music, what do all of you programmers do to avoid workplace monotony?"
I get more reading done during work than any other time of the day.
And you can get them from your local public library.
I recomend this cd player
=================
Unix is very user friendly, it's just picky about who its friends are.
1) Listen to DVDs...I find it's more interesting than music and not more intrusive. I minimize them and just listen to the sound, flipping over for the good parts.
2) Write code. Ever wanted to learn a graphics library? New language? Check out SDL, neat little cross platform graphics library. Write a PacMan clone to learn it.
3) Read news. I read a lot of news during the slow times.
4) Gameboy. The SP is pretty small, would probably go unnoticed or be mistaken for a PDA.
--trb
I currently have the same problem as you. I VNC into my box at home and do stuff. Browse torrent sites, etc... I also run a radio station for everyone in the department (Computing Services for my university) and people making requests and such make things interesting (don't have that one... hmmm, lemme find it and throw it on the playlist) AIM keeps things interesting, as does sites like MySpace, Orkut, and even LiveJournal. Slashdot, fark, and others keep me sane. an occasional game of solitaire, stepping outside for a cigerette (a vanilla clove is excellent for killing stress, I have to say), Other projects you have more interest in: I'm currently in the process of learning PHP so I may make my own dynamic site for my photography... that and working on a short story that gets less and less "short" by the week... Online photoshop contests are fun too :)
Viva La Revolucion! Buy a Mac!
1) I know you mentioned "besides music", but that really is one of the best ways. One thing I've noticed is that, being a programmer, *really* hard industrial really helps me get into "the zone" while coding, and trance just makes the hours fly by. Apoptygma Berserk, VNV Nation, Oakenfold, etc.
2) Get a laptop, watch DVDs or music videos on it while working. I did this for years in my younger years. Helps boredom, but not the greatest for productivity.
3) Someone brought this up before, and it's an awesome time-suck. Learn a new language/technology.. expand your knowledgebase. Employers generally encourage this (in my experience).
4) If all else fails, and the job is just insanely boring, the company won't let you listen to music, watch DVDs, research new fields, read news, whatnot.. find yourself another job. I had this happen once a few years back with a job they sold me as a dev position, and turned out to be configuration management. After 3 months of total boredom, I moved to another job.
Hope that helps!
-- Jinsaku
-- Jinsaku
I work on my juggling for a few minutes here and there. It means I have to stand up and move around which has to be a good thing.
:)
My five ball cascade is improving too
Cheers,
Roger
Do you have any better hostages?
Listen to old time radio shows (OTR). They offer drama and excitement, and you don't have to take your eyes off the screen. You can download MP3 of shows from many places.
I find it is great when coding, but not as good when reading text like emails.
Employment can be a subsidized education. Take advantage of the free time.
Of course, barring that, find a bunch of smaller message boards and alternately check them. You can even be a rabid republican on one and a bleeding heart democrat on another.
I always carry around my pick set and a masterlock. When things get slow at the office, and when I am sitting on the train to and from work I practice the fine art of bypassing locks.
A few years back, the hype surrounding Extreme Programming got me curious, so I tried the style of development known as Test-Driven Development. It makes development less frustrating and more fun, so I'm a lot less likely to wander off to places like Slashdot.
Basically, the way it works is you sit down, figure out what you're going to do next, and write a few line of test code that don't pass yet. You write a little code to make the test pass. Then you expand the test a little, and make that pass. And so on. There are two main rules: don't write production code without a broken test, and try to keep the time between cycles pretty short, say under 10 minutes.
The short cycles and alternating viewpoints make it feel something like playing chess against yourself. Since everything you write is tested, bug rates are very low, and using the debugger becomes very rare. And although I thought my code was pretty good before, I think it's better now. By starting out thinking how it looks on the outside, the APIs are cleaner and easier to use.
Your question here seems to be very poorly structured, and the range of answers people are giving reflect that. Many of the suggestions (read, watch DVDs) assume that the problem is that too much of the time the job is merely to be physically present. If what you need is an answer to how to fill up the idle hours, and you love to program, I'd suggest that no NOC I've ever seen has all the tools that it really needs. Consider what kinds of tools would make your job easier when problems occur (or tools that can analysis the available data and identify potential problems before they occur) and write them.
If your problem is that you're already programming and you've got plenty to do, but there's no "human contact" in the way the job is done, try to add some. It might be as simple as adding informal design reviews -- "Hey, Bob, can we get together for 30 minutes on Tuesday so I can describe how I'm structuring this, and get your opinion about it?" When I had programming tasks, I always found that having such reviews sometimes led to people pointing out better ways to do a task, and always clarified my own thinking about what I was doing.
From a distance, English text in a text editor looks (or can be made to look) very much like source code. Hammer out the words when you've nothing better to do, mail it to yourself at home, clean it up and send it off to a publisher. You too could be paid to write a best-seller!
Of course, if there is an intellectual property rights agreement between you and your employer, you may find that they can fire you for doing this, or (worse) that the book's copyright belongs to them. If the book is successful, they might sue you for a share of the royalties.
I'm writing a book in this manner. I use my own PDA for it, so the book is neither stored on nor passes through any computer that the company controls. I write only during my lunch hour and when I'm travelling to and from work (I commute by train), so I'm never writing when I'm supposed to be working.
Just another wannabe fantasy novelist...