2 ms·
In the world of programming, repercussions of what you do take longer than a year to full play out. Let's say you join a company, get up to speed quickly (let'
by jasonlotito 10y ago
In the world of programming, repercussions of what you do take longer than a year to full play out. Let's say you join a company, get up to speed quickly (let's say 3 months), and you get on your first product, start working on it, and after 6 months you release a beta. And 3 months after that, you launch. And then you are done, and you move on to the next company.
You don't see the results of that year that you were there. You don't see the results of of long term maintenance. What worked, what didn't, where you wasted time, what was used, etc.
Even the tools you used, you only used that to get it into production at some level, but you don't fully understand the full long-term impact.
So when someone looks at that, they don't see production level experience. They see that you've done the first years worth of work 10 times, and that you don't have experience with the results. That your experience doesn't mean you can build something that works in the long term. That you can even be counted on to work on something in the long term.
That's just one of the ways it can be looked at.