Coding in home VS Coding in office
-
Mahmoud Zidan wrote:
In office you code what you didn't imagine that you can do.
Or you could never be bothered doing until you were forced? I hope I understand what you mean.
I understand if nobody's interested in what I have to say...
-
code what you want at home code what your told to code in the office have to meet deadlines in office can leave it at home
Yes I do but office consume a lot of working hours :sigh:
-
At home I code work and private code, in the office just work, but that's the only real difference I see. I do a lot of R&D code at the office as well, which brings out the real artist in me, and I do a lot of deadline stuff at home. That is, before I fell on my laptop and broke the screen. Now, until I get my office desktop and can take my laptop in, I only code at the office. :(
-
For me, it's exactly the opposite. I produce code (at work) that I know will work. The stuff I do at home is where I experiment to find out what will work. Anything else is just downright reckless and is selling your employer short.
Deja View - the feeling that you've seen this post before.
-
As Pete said, it's completely the opposite. But also, "in office" implies working as an employee. "in home" implies (at least for me) working more as a contractor. The truth is, I take more pride and care when I'm working for a client than I ever did working as an employee. Code ownership, the ability to go "off the clock" and write something general purpose that goes into my code library or becomes a CP article, is invaluable to me. I detested the "we own you" attitude of employers, often backed by employment contracts I had to sign. So I much prefer working at home. :) Marc
-
Yes I do but office consume a lot of working hours :sigh:
yeah, i'd hate to see the work to hours ratio of work and home :sigh:,
-
For me, it's exactly the opposite. I produce code (at work) that I know will work. The stuff I do at home is where I experiment to find out what will work. Anything else is just downright reckless and is selling your employer short.
Deja View - the feeling that you've seen this post before.
At work, I produce code they tell me to produce. At home, I am free to innovate.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
-
At home you can code in your underwear. :-O In the office you have to wear a dress meet the office dress code. X|
Simply Elegant Designs JimmyRopes Designs
Think inside the box! ProActive Secure Systems
I'm on-line therefore I am. JimmyRopes -
I think it is all rather individual, based both on the person's individual nature and the job that he/she does. I have two different kinds of work at home, I take both very seriously. On deadline crunches, I will do my usual office work on a laptop or my home machine at home (this has also been done in the halls of the LA convention center during a conference, and many other locations). The other type of home-work is pure R&D. This is where I can take proposals that have been turned down and do it, or I can take an idea that no one believes will work, and make it work. I can innovate in ways that work would never risk my time, because I am too important to risk on whims of fancy. But some of our best code comes out of whims of fancy. No one paid for both my line-of-sight analysis or my intercept prediction algorithms, because in both instances no one believed they could be improved beyond what exists (which was passable, but not desirable). any work at home I can put down any time I want, per se. Though in some instances I need the extra time, or work desperately needs the extra time.
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
