3 ms·

Coincidentally, I'm age 34 right now. So at that point where you were at a crossroads you turned things around. Did you work at large companies to correct that?

Coincidentally, I'm age 34 right now. So at that point where you were at a crossroads you turned things around. Did you work at large companies to correct that? Do you think development team size make an impact on your career growth?

scarface74 9y ago
Being at a large company isn't what made the difference. Even though I didn't realize it at the time, I think it is more important to work at a company that sells software and sees software development as a profit center and not a cost center. There are some requirements I would look for: 1. Do they have automated tests? 2. Do they enforce code reviews? 3. Do they use some type of continuos integration system? 4. Do they use source control - preferable Git? 5. For the server side, do they use a statically type language - Java, C#, or even NodeJS/TypeScript 6. Do they have organized training sessions like lunch and learns? I'm at a point in my career now where I'm pretty confident in what I know and I'm the only architect at my company. I ask for advice a lot from some of my former more experienced coworkers on a private Slack channel that we still use.
- toexitthedonut 9y ago
  To all those questions I can answer 'no' to all of them, besides no. 4 because I do use Git. Damn. Now if only I can get offers from companies that have the other qualities.
  - madebysquares 9y ago
    We are the same age and have about the same length of experience. I totally get where you are coming from because I began to feel I wasn't learning anything new and just repeating the same processes. So I left after 3 1/2 years. Since then every job I've had I try to work for people I can learn from and grow. Having people who can mentor or just being around smart people and seeing how they work and implement processes can be really helpful.

3 ms·

Coincidentally, I'm age 34 right now. So at that point where you were at a crossroads you turned things around. Did you work at large companies to correct that?

by toexitthedonut 9y ago

scarface74 9y ago
Being at a large company isn't what made the difference. Even though I didn't realize it at the time, I think it is more important to work at a company that sells software and sees software development as a profit center and not a cost center. There are some requirements I would look for: 1. Do they have automated tests? 2. Do they enforce code reviews? 3. Do they use some type of continuos integration system? 4. Do they use source control - preferable Git? 5. For the server side, do they use a statically type language - Java, C#, or even NodeJS/TypeScript 6. Do they have organized training sessions like lunch and learns? I'm at a point in my career now where I'm pretty confident in what I know and I'm the only architect at my company. I ask for advice a lot from some of my former more experienced coworkers on a private Slack channel that we still use.
- toexitthedonut 9y ago
  To all those questions I can answer 'no' to all of them, besides no. 4 because I do use Git. Damn. Now if only I can get offers from companies that have the other qualities.
  - madebysquares 9y ago
    We are the same age and have about the same length of experience. I totally get where you are coming from because I began to feel I wasn't learning anything new and just repeating the same processes. So I left after 3 1/2 years. Since then every job I've had I try to work for people I can learn from and grow. Having people who can mentor or just being around smart people and seeing how they work and implement processes can be really helpful.