Re:What do YC Founders think about working at Big Companies?
by brc on Tuesday November 09, 2010 @10:35PM
(#1889036)
An example of rules and unwanted outcomes. I once wrote an application at a big company, which had a strict application packaging process, for remotely installing apps on machines. A last minute change was requested, which resulted in a small error being made in the 'tab order' of the screen. It would have taken one compile and 20 seconds to fix, but because the rules said the executable couldn't be updated once packaged, it remained so. 7 years down the track, the same application was still being used, and the users of said app had to skip using the tab key to get around fields and instead mouse backwards. 7 years of aggravation and frustration on the part of users which could have been avoided with 20 seconds worth of rule breaking. I'm aware of what those rules are for, but having a structure so fixed that it causes this type of inefficiency is frustrating to all involved. It's not like anyone benefited from following the rules, save for the guy who could honestly say to his boss 'I made them follow every last rule'.
[ Parent
| on HN ]
Re:What do YC Founders think about working at Big Companies?
by cageface on Wednesday November 10, 2010 @02:13AM
(#1889493)
That's exactly the kind of thing that drives me nuts about bigger companies.
I spent three years trying to get a single dropdown menu changed in a web application at my last job.
Re:What do YC Founders think about working at Big Companies?
by lhnz on Wednesday November 10, 2010 @05:24AM
(#1889829)
Ahaha, this is like what happens in my company. They allow you to create packages right up until version 1.0, and then after that you have to create awkward 'patches'. The problem is that they force you to call something version 1.0 due to politics alone.