There is a phase in the Software Development career where your tasks have less descriptions, less relevance to the business objective, less visibility, less of everything that used to make it fun and exciting.
At the beginning of my career there was more hype around a task, "hey we're building this app, the client is paying us 300K (big amount) to build it and you're going to be the frontend guy for it!" I was like 'let's go! I'm going to build the best app ever!". I was able to work until 2AM and get back into the office at 9AM. Was my code the best code I have ever written? Probably not, but oh did it come from the purest of my anxieties, pleasing the people who gave me the job. That combined with the fear of being poor (due to possibly losing my job) in addition to the salt added the task gave me the energy I needed to finish a whole app in very little time.
However, I am starting to notice a bit of a pattern in the industry. The hype usually happens at the beginning of the employee-employer relationship, just like a romantic relationship, the honeymoon phase, once that is over you have to be your own hype person, "this needs to happen, make it happen" forget about your laziness, "this is the expected result, make it happen". Ironically enough, this is exactly what I wanted.
On the flip side, once the honeymoon phase is over, you get to the marriage phase. I'll leave it at that cause y'know what it is to be married...
Top comments (0)