3 ms·
I became a programmer because Travelocity couldn't hire competent front-end developers. I was hired on October 2007 as a designer. They had plenty of designer
by austincheney 6y ago
I became a programmer because Travelocity couldn't hire competent front-end developers. I was hired on October 2007 as a designer. They had plenty of designers. After 3 months of doing very little work I was reassigned to a developer position and told to figure it out. I figured it out because I wanted to remain employed so that I could continue to pay my rent and feed my children.
In hindsight this experience has proven problematic. Many people who perform front-end development never seem to figure it out. They are dependent upon a collection of tools to do large portions of their job for them. This is incredibly frustrating because it exposes a very extreme and immediate sense of dependency that quickly leads to insecurity, which is a polite way of saying hand-holding possibly infantile. That is a wildly different perspective that often results in friction and sometimes hostility.
- mynegation 6y ago> Many people who perform front-end development never seem to figure it out. They are dependent upon a collection of tools to do large portions of their job for them. Do not feel bad about it. This practice applies as much to the back end development, the whole of programming, and human experience in general. There is only as deep as you can go. I would never be able to build a computer from electronic parts and bootstrap even a simple operating system from scratch. If I understand you correctly is what you probably mean is that many developers approach their job mechanistically, without getting into understanding of the parts of the knowledge that would allow them be much better at what they do. To that I say - it is because of immense and fast growing demand and the fact that FE development sits on the very top of one of the most complicated infrastructure stacks in human history.