Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

Why is programming...

Name: Anonymous 2013-02-15 16:19

so fun when working in your own projects, but it gets so fucking boring when you're doing it for work?

Name: Anonymous 2013-02-15 16:20

i know, right!?

Name: Anonymous 2013-02-15 16:21

It depends. It you join a 'work' project from the start it can be very fun too.

Unless you work for a bank. That always suck.

Name: Anonymous 2013-02-15 16:22

>>3
s/ It/ If/;

Name: Anonymous 2013-02-15 16:25

Ownership. The stakeholder for your own project is going to be yourself so you should know exactly what your project does. Working for others means that you probably won't get a stake in see your completed effort established and working.

Name: Anonymous 2013-02-15 16:26

>>3
Management software. No. Please no. No NO NO NO

Name: Anonymous 2013-02-15 16:27

Because it's work.

Name: Anonymous 2013-02-15 16:41

using api is the most unfun thing imaginable

Name: Anonymous 2013-02-15 16:58

>>1
so fun when working in your own projects, but it gets so fucking boring when you're doing it for work?
Because you've never tried to make your projects useful for other people. I have, like, three, marinating on the backburner for a year on average, because I respect myself too much to release them without a proper test coverage and comments and shit, and that stuff is boring.

Name: Anonymous 2013-02-15 17:04

programming isn't fun.

Name: Anonymous 2013-02-15 17:06

What >>5 said. I call it conflict of interest.

Name: Anonymous 2013-02-15 17:51

Probably because your projects are about shit you like, while doing work requires doing stuff you aren't necessarily interested in.

Don't change these.
Name: Email:
Entire Thread Thread List