Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Sounds like you're inflexible and slow down process. Which can be a good thing, but it really depends on the studio.

I've tried to do this in the games industry and I just end up being called "slow". Because games have historically been "break fast, ship buggy". There's not a lot of value in a well-architectures codebase here. It's getting better due to some high profile buggy disasters, but change is slow.

> very rarely believe in anybody professionally, because people has a tendency to nurse their subjective opinions and thought more than commit to long reasonings of why and find evidens for their claims.

Most peope don't want to hear long reasonings unless they are the ones directly solving the problem. There's no point making an articulate proposal if the readers skim and pass on feedback I already addressed.

I imagine it's the same for many ambitious juniors. They get dismissed and they change their language as they adapt to the industry. Things aren't as eglitarian as the marketing shows, and those who see the sausage being made adapt.

I don't know. It sounds like you either had some very quality work history to come to these conclusions, you had the funds/connections to found/co-found work where you shape the culture, or you have an extremely strong sense of duty. I'm proud of my experiences, but I can't say I relate, and I'm already broken. No point correcting corporate, better to suck off their funds and prepare to be my own boss.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: