You're a developer, so why do you work for someone else?

Re:You're a developer, so why do you work for someone else? by AshFurrow on Sunday November 06, 2011 @11:25AM (#3203033)

For sure - there's a trick in finding the right company.

[ Parent | on HN ]

Re:You're a developer, so why do you work for someone else? by pavel_lishin on Sunday November 06, 2011 @12:08PM (#3203148)

In my experience, the amount of bullshit is directly correlated with company size.

[ Parent | on HN ]

Re:You're a developer, so why do you work for someone else? by scottshea on Monday November 07, 2011 @11:08AM (#3206764)

There is that... and of course all Public Companies in the US have the SOX BS baked into the process.

[ Parent | on HN ]

Re:You're a developer, so why do you work for someone else? by pavel_lishin on Monday November 07, 2011 @12:25PM (#3207195)

Having never worked for one, I have no idea what SOX BS is. Can you elaborate?

[ Parent | on HN ]

Re:You're a developer, so why do you work for someone else? by scottshea on Tuesday November 08, 2011 @12:04AM (#3209569)

Sarbanes-Oxley Act. It was enacted following Enron and Worldcom to prevent corporate malfeasance. Sadly it gave a lot of auditors a lot of power which translated to 'controls' placed on the work environment. Some make sense (e.g. no read/write access to production for development). Others make no sense (e.g. no access to log files from production for developers troubleshooting issues). It really depends on the company and the audit process.

[ Parent | on HN ]