If you can read this, either the style sheet didn't load or you have an older browser that doesn't support style sheets. Try clearing your browser cache and refreshing the page.

(IT World)   When's the best time of day to write code, aside from during long, boring meetings?   (itworld.com) divider line 51
    More: Interesting, work outs, meetings, exile  
•       •       •

1751 clicks; posted to Geek » on 26 Feb 2013 at 9:47 AM (1 year ago)   |  Favorite    |   share:  Share on Twitter share via Email Share on Facebook   more»



51 Comments   (+0 »)
   
View Voting Results: Smartest and Funniest

Archived thread

First | « | 1 | 2 | » | Last | Show all
 
2013-02-26 09:48:48 AM
Right before it's due.
 
2013-02-26 10:03:22 AM
Not sure if subby means to write IN code, like nonsense he can understand, or if he means write code, like to do some programming or scripting on a website/program/app.

If it's coding like the stuff programmers and developers do to make money, the best time is late at night with a lot of Monuntain Dew in your system.
 
2013-02-26 10:04:34 AM
oh wait... this isn't tfd, there's an article.

meh, my reply still stands.
 
2013-02-26 10:06:58 AM
I agree with ironjelly.. for me its late at night. that seems to be the time that i can get in the zone and crank out code.
// with ice coffee in my bloodstream.
 
2013-02-26 10:07:45 AM

Marine1: Right before it's due.


This.

/our JIRA board is looking awfully empty... Did we really stabilize this thing in time... Or is it the calm before the storm, and we're getting buried tomorrow? (User testing time... Yay!)
 
2013-02-26 10:15:14 AM
My friend goes to a strip club to write his code.  Spends 10 hrs at work faking it, writes code at a strip club for 3-4 hrs, goes to work and uploads it in 2 mins, rise and repeat.
 
2013-02-26 10:16:43 AM
 Most programmers specialize in not doing anything 75% of the time.
 
2013-02-26 10:29:19 AM

Marine1: Right before it's due*.


The night before it's due.

/vampire
 
2013-02-26 10:34:21 AM
imgs.xkcd.com
 
2013-02-26 10:42:32 AM
The Balmer Peak graph is completely wrong.  Programming skill gradually rises with alcohol up until about .08, then takes a sharp rise and then a sharp drop.

Alternately, you can just free-base skittles.

I do my best work after dinner, because that's when I'm most likely to have had a couple of beers.
 
2013-02-26 10:51:23 AM
Whenever everyone will LEAVE ME THE fark ALONE for a little while.

/caffeine helps, but not so much caffeine that I'm shaking
 
2013-02-26 10:54:12 AM
After three bong hits.
 
2013-02-26 11:06:32 AM
I can tell you this much  it's NOT during the time that I'm reading Fark;

I'm getting practically nothing accomplished;
 
2013-02-26 11:11:34 AM

studebaker hoch: Most programmers specialize in not doing anything 75% of the time.


I always thought it was just me.  I keep thinking I could be some super-human code monkey if I could just *focus* that other 3/4 of the time.

Or maybe I could have 4 full time jobs for 1 year, then take 2 1/2 years off, leaving 6 months to brush up the skills, then repeat.
 
2013-02-26 11:45:47 AM

studebaker hoch: Most programmers specialize in not doing anything 75% of the time.


It's called compiling. Of course, that excuse worked better on 8mhz computers when compiling a large program would take all afternoon.
 
2013-02-26 11:51:04 AM

Marine1: Right before it's due.


Forget Just In Time Compilation,
We perform just in time code creation.

Just as the farther away from execution you compile code, the less you know about the environment it will run it,
The farther away from delivery you write code, the less you know about the requirements it has to meet.

So, by spending a couple afternoons this week up at the bar not doing my job, I'm actually saving the company money.
 
2013-02-26 11:58:40 AM
For me, it's whenever inspiration hits.  I've woken up from a dead sleep at 3AM, realized "if I just twerkstinate the friblemaxation of the perflubbity index, then BOOM! the whole thing will fall together!"  And then I rush downstairs and hit the keyboard.  Showering seems to bring out the inner genius as well.  I've stood there transfixed with a brilliant idea, hair still full of shampoo, completely unaware that the hot water had run out ten minutes ago.  A couple of times, I didn't even bother rinsing off- just dashed down to the computer stark naked to get my pruney fingers coding.

I'm at my worst when I have to slog through a bunch of "mandatory brute force programming" tasks.  I.e. there are a couple hundred things that need to be coded for, and they're aren't ever going to be used again or they're just different enough that they can't be put into a common framework or some other labor-saving device.  And then you just start at the top and work your way through it, groaning the whole time.

I tend to make way more mistakes on the latter even though that type of work tends to be simpler than the stuff that comes to me in a flash of inspiration.
 
2013-02-26 12:01:11 PM

studebaker hoch: Most programmers specialize in not doing anything 75% of the time.


You can have me do nothing for 75% of the time and keep me at your company for around 6-10 years or you can have me work 100% of the time, including the extra over time you demand and have me at your company from anywhere between 6 months and 2 years.

Any place that watched how much "work" I did and was always pushing for more was never a place I could stand to stay at for very long. Often I would walk off the job with a big "fark you!" right in the middle of something they thought was extremely important. On the other hand places that did not give a shiat how much I "worked" as long as my assignments were completed I stay at for a long time.

Forcing programmers to "work" 100% of the time means you are going to  chew them up and spit them out quickly requiring constant retraining, because no programmer is effective until they have had six months to learn your business.
 
2013-02-26 12:01:56 PM
If I am having a problem coming up with the right algorithm, the best, or at least a new, idea occurs to me while lying awake in bed in the middle of the night. I write my best code in the morning while absolutely wired on coffee. Later in the day is for tidying up, and finding the next issue to worry about in the middle of the night.

studebaker hoch: Most programmers specialize in not doing anything 75% of the time.


imgs.xkcd.com
 
2013-02-26 12:07:47 PM

NewWorldDan: Programming skill gradually rises with alcohol up until about .08, then takes a sharp rise and then a sharp drop.


I used to think this as well, until I realized that for every hour I spent coding while drinking, I spent 2 hours fixing while sober.  I quickly learned that anything over 1 beer in a day destroys my ability to code.

/ not a lightweight either
// drink waaay too much
/// then again, the liver  isevil and must be destroyed
 
2013-02-26 12:31:22 PM

Slaves2Darkness: studebaker hoch: Most programmers specialize in not doing anything 75% of the time.

You can have me do nothing for 75% of the time and keep me at your company for around 6-10 years or you can have me work 100% of the time, including the extra over time you demand and have me at your company from anywhere between 6 months and 2 years.

Any place that watched how much "work" I did and was always pushing for more was never a place I could stand to stay at for very long. Often I would walk off the job with a big "fark you!" right in the middle of something they thought was extremely important. On the other hand places that did not give a shiat how much I "worked" as long as my assignments were completed I stay at for a long time.

Forcing programmers to "work" 100% of the time means you are going to  chew them up and spit them out quickly requiring constant retraining, because no programmer is effective until they have had six months to learn your business.


Honestly, it's not doing nothing, it's internal brainstorming.  Start with a random class or function, get halfway through it, roadblock, fark off for 20 minutes and "Ah Ha!" and all of the sudden I can finish writing Kubla Khan
 
2013-02-26 01:09:45 PM

Slaves2Darkness: studebaker hoch: Most programmers specialize in not doing anything 75% of the time.

You can have me do nothing for 75% of the time and keep me at your company for around 6-10 years or you can have me work 100% of the time, including the extra over time you demand and have me at your company from anywhere between 6 months and 2 years.

Any place that watched how much "work" I did and was always pushing for more was never a place I could stand to stay at for very long. Often I would walk off the job with a big "fark you!" right in the middle of something they thought was extremely important. On the other hand places that did not give a shiat how much I "worked" as long as my assignments were completed I stay at for a long time.

Forcing programmers to "work" 100% of the time means you are going to  chew them up and spit them out quickly requiring constant retraining, because no programmer is effective until they have had six months to learn your business.


but we need Efficiency!!   and that translates to happy stock holders!   isn't that special!
 
2013-02-26 01:16:51 PM

diaphoresis: My friend goes to a strip club to write his code.  Spends 10 hrs at work faking it, writes code at a strip club for 3-4 hrs, goes to work and uploads it in 2 mins, rise and repeat.


He is a god to me

*Bows down*
 
2013-02-26 01:26:17 PM

CujoQuarrel: diaphoresis: My friend goes to a strip club to write his code.  Spends 10 hrs at work faking it, writes code at a strip club for 3-4 hrs, goes to work and uploads it in 2 mins, rise and repeat.

He is a god to me

*Bows down*


He's actually worked for Sikorsky, AT&T, numerous AFBs, and somewhere in D.C.  It's a crime he gets to do that and regularly gets paid 6-figures... I hate his guts... and he's a friend.
 
2013-02-26 01:30:30 PM

diaphoresis: CujoQuarrel: diaphoresis: My friend goes to a strip club to write his code.  Spends 10 hrs at work faking it, writes code at a strip club for 3-4 hrs, goes to work and uploads it in 2 mins, rise and repeat.

He is a god to me

*Bows down*

He's actually worked for Sikorsky, AT&T, numerous AFBs, and somewhere in D.C.  It's a crime he gets to do that and regularly gets paid 6-figures... I hate his guts... and he's a friend.


But doesn't the dancer on his lap interfere with him getting to the keyboard?
 
2013-02-26 01:31:54 PM

CujoQuarrel: diaphoresis: CujoQuarrel: diaphoresis: My friend goes to a strip club to write his code.  Spends 10 hrs at work faking it, writes code at a strip club for 3-4 hrs, goes to work and uploads it in 2 mins, rise and repeat.

He is a god to me

*Bows down*

He's actually worked for Sikorsky, AT&T, numerous AFBs, and somewhere in D.C.  It's a crime he gets to do that and regularly gets paid 6-figures... I hate his guts... and he's a friend.

But doesn't the dancer on his lap interfere with him getting to the keyboard?


Lol
 
2013-02-26 02:03:03 PM

studebaker hoch: Most programmers specialize in not doing anything 75% of the time.


Now if we could just perfect the program to write programs.
 
2013-02-26 02:20:59 PM
Stop with the ITWorld articles.  They are worthless.

Article headline: "When is the best time of day to write code?"

After stupid musician talk...."The answer, of course, is that it depends. "


WORTHLESS
 
2013-02-26 02:21:17 PM
3 AM with a bag of chips to one side and caffeine pills to the other.

/Got WAY too many school projects done that way.
 
2013-02-26 02:45:51 PM
When Marissa Mayer is right behind your back screaming about how you're not trustworthy enough to work at home as you develop apps to help other people work from home.
 
2013-02-26 02:51:09 PM
Used to be late in the evening/night, but then I got married and had kids.

Now it's early in the morning before people show up and start making distractions.
 
2013-02-26 02:59:34 PM
"It's called compiling. Of course, that excuse worked better on 8mhz computers when compiling a large program would take all afternoon."

That must be what Windows Azure uses....
 
2013-02-26 03:06:00 PM

DSanchez: "It's called compiling. Of course, that excuse worked better on 8mhz computers when compiling a large program would take all afternoon."

That must be what Windows Azure anything uses....


FTFY.

Nothing quite like going into work, typing the make command into the screen, pulling out a book, waiting 8 hours for the build to complete, and going home.
 
2013-02-26 03:50:39 PM
Old time programmer here ... I used to code in my sleep and key it when I hit the office the next day.  Finally diagnosed with severe sleep apnea after all those years. I don't program any more and miss it a lot.
 
2013-02-26 04:42:22 PM

Marine1: Right before it's due.


I thought that's when you're supposed to test it...
 
2013-02-26 04:57:41 PM
I can code pretty much any time of the day, but I do hate it when people say that Im farking off half the time. If i get stuck, I will start surfing to get my mind off of it for a while and thats when a solution usually "hits me."

I also need music, of my choosing. If you make me listen to shiat, you will get shiat. Music gets my creative juices flowing and my magical fingers ah stroking on the keyboard.
 
Bf+
2013-02-26 05:08:11 PM
*sigh*
Saturday mornings.
/wish I were kidding
 
2013-02-26 06:00:24 PM
Day? that nixes it right there. 1 to 3am is my sweet spot for writing code
 
2013-02-26 06:32:55 PM

you have pee hands: Whenever everyone will LEAVE ME THE fark ALONE for a little while.

/caffeine helps, but not so much caffeine that I'm shaking


This.  I get annoyed when I'm asked to do ten things at once and they wonder why I'm not meeting their arbitrary deadlines.  Or sometimes it's MY arbitrary deadline that becomes unreachable when other work gets piled on.  Or I'm waiting on somebody else, and it's somehow my fault because I didn't "push hard enough".
 
2013-02-26 06:52:12 PM

bhcompy: Slaves2Darkness: studebaker hoch: Most programmers specialize in not doing anything 75% of the time.

You can have me do nothing for 75% of the time and keep me at your company for around 6-10 years or you can have me work 100% of the time, including the extra over time you demand and have me at your company from anywhere between 6 months and 2 years.

Any place that watched how much "work" I did and was always pushing for more was never a place I could stand to stay at for very long. Often I would walk off the job with a big "fark you!" right in the middle of something they thought was extremely important. On the other hand places that did not give a shiat how much I "worked" as long as my assignments were completed I stay at for a long time.

Forcing programmers to "work" 100% of the time means you are going to  chew them up and spit them out quickly requiring constant retraining, because no programmer is effective until they have had six months to learn your business.

Honestly, it's not doing nothing, it's internal brainstorming.  Start with a random class or function, get halfway through it, roadblock, fark off for 20 minutes and "Ah Ha!" and all of the sudden I can finish writing Kubla Khan


Gold plated THIS.
 
2013-02-26 06:56:06 PM

Do the needful: studebaker hoch: Most programmers specialize in not doing anything 75% of the time.

Now if we could just perfect the program to write programs.


But you'd need a program to evaluate programs. To wit, a program that could tell if a program will finish.

/too bad the "Solve halting problem $1000" from getacoder.com is gone...
//no, can't be arsed to look in archive.org
 
2013-02-26 07:32:27 PM

studebaker hoch: Most programmers specialize in not doing anything 75% of the time.


That's because 25% of the time we're putting in 150% of the effort of everyone else.
 
2013-02-26 07:44:37 PM
Before 9 or after 5, when everyone will leave me the hell alone.
 
2013-02-27 01:34:19 AM
While masturbating furiously.
 
2013-02-27 05:58:00 AM
From about 9am to 3pm, actually. Right around noon. I don't know why. Now I work nights and the prime coding time is when I try to sleep. :(
 
2013-02-27 01:39:57 PM

zobear: Marine1: Right before it's due.

I thought that's when you're supposed to test it...


... test?

/kidding
//sort of
 
2013-02-27 08:00:47 PM
Been coding 10 years.   I get outrageous amounts of progress done between 12 and 4 AM.

Still have to get up @ 7, to go in to office to pretend to work for 8 hours.  Usually nap at lunch.

Sucky part is, when I code that late, it's like I'm smoking pot.. Gotta have various munchies, and I don't move from the desk for the whole time.
 
2013-02-27 08:33:29 PM

ghoti_nap: Been coding 10 years.   I get outrageous amounts of progress done between 12 and 4 AM.

Still have to get up @ 7, to go in to office to pretend to work for 8 hours.  Usually nap at lunch.

Sucky part is, when I code that late, it's like I'm smoking pot.. Gotta have various munchies, and I don't move from the desk for the whole time.


This.

/Gained 60 pounds sophomore year of college pulling a minimum of 2 all-nighters a week.
 
2013-02-27 10:06:21 PM

ghoti_nap: Been coding 10 years.   I get outrageous amounts of progress done between 12 and 4 AM.

Still have to get up @ 7, to go in to office to pretend to work for 8 hours.  Usually nap at lunch.

Sucky part is, when I code that late, it's like I'm smoking pot.. Gotta have various munchies, and I don't move from the desk for the whole time.


Been coding (less over time) for 23 years.  Bet you aren't married with kids yet.
 
2013-02-28 02:11:42 AM
It depends. HTML, CSS, and JavaScript? Stoned. PHP? Wired. Java? Drunk. Visual Basic? Never.

/need to learn a language designed for sobriety
//or maybe I need to go to a meeting
///perhaps both
 
Displayed 50 of 51 comments

First | « | 1 | 2 | » | Last | Show all

View Voting Results: Smartest and Funniest


This thread is closed to new comments.

Continue Farking
Submit a Link »






Report