Being a (web) programmer (As a job/carreer) sucks... If you take (web) programming as:
- A homemade problem without a deadline
- A chill job.
- Not a constant challenge.
- An ideal job to work from home super comfy and that's all.
In my short (current) carreer I have found that the best way to approach programming as a job, is to take it as a challenge, and to befriend with some ideas, like having to constantly learn and re-learn stuff, you WILL dedicate more time than usual, and you WILL re-learn stuff all the time, specially if your job covers a lot of stuff.
Your P.M may be an asshole, or may be your savior, roll a 1d20, that is also (web) programming.
You will code for the machine, but with an assignment; Meaning that you will code for people basically, as the problema rises from a human, not a machine, that is also (web) programming.
You will be held responsible sometimes for things that are out of your scope, yet you will find yourself doing them, that is also (web) programming
The problems you solve, may be a problem itself in the future as your product changes and is defined on the fly, that is also (web) programming.
So yeah, (web) programming actually (sucks) rules, but you have to chew through the bitter part first.
Throw away your optimistic JavaScript course and embrace reality. This was my experience, and I loved it and would do it again
You are welcome to share your experiences and thoughts on this.
Top comments (0)