3 ms·
13 years. 0) Money. the big money is in projects that need help. E.g. CEO during your interview: "The last lead programmer flipped me off and our accounting s
by ransom1538 9y ago
13 years.
0) Money. the big money is in projects that need help. E.g. CEO during your interview: "The last lead programmer flipped me off and our accounting system in small talk is broken." That's hard.
But that is where money is.
2) errors happen. Do tdd - so you can go to that concert.
2) Be the go to guy. If someone needs something you better be able to help. Brushing someone off creates office enemies and will remove any hopes of promotion.
3) any idiot can write code. I can with one hand tell you the names of people that can take over a system with 500k of mangled code.
4) think win/win. If you are doing a project - work hard -win for the company, but also put it docker so you learn something too.
5) launch side projects. You should release something large every year.
- jrumbut 9y agoI really like this response because it is helpful and practical but not overwhelmingly cynical or Machiavellian. You can do well by doing right in this field! I think a corollary to 0 is that if an organization is in trouble it will usually find a way to always be in trouble. It's human nature to think a crisis is always almost over, often it's only beginning. For sure, taking over a troubled project is a great and honest way to make money, and I love sorting out tangled messes where the original developers have all left (hit me up if you've got one, email in profile!), but just make sure that the problem wasn't a chaotic or toxic work environment. People and their interactions are more important than events and circumstances in terms of creating an environment. Some teams run on crisis and others run on collegiality. The direct and indirect benefits of a positive work environment are tremendous.