13
netikras
22d

I'll give you a few reasons to walk away from a dev's chair:

1. if you want your life to be simple and not challenging, if you just want to go with the flow - choose something else. Dev's life will definitely bring some challenges to your day (and sometimes night, and sometimes - your weekends). Especially if you feel you are a perfectionist, dev life could turn your life into a living hell if not handled with care.

2. If you like to see people smiling, if you love that feeling when you help someone and that someone has a better day thanks to you - choose something else. 1st line SD would probably do, but the further from technology you go - the more smiles (and human faces overall) you'll see.

3. If you prefer person-to-person interaction over to talking to machines - definitely don't be a dev. Go to management, administration or smth else, but development. >90% of the human interaction in this field is arguments and conflicts; ~8% are requests for assistance, and the remaining 2% are shared by saying "hi" to the office administrator and your (semi|)annual reviews with your manager. Not kidding.

4. If you have a personality where you find it difficult to stand your ground and not budge to the pressure/blame game/your managers asking you to stay in late. Like it or not, it happens quite often. Many devs have spoiled the management by budging to their requests/demands to stay for OT/unpaid OT to "fix the mess they have made". That's a blame game right there. And these people stay in and do what the slaves do - work for free because they are yelled at. And then management sees this technique work and (ab|)uses it on other devs. If you can say NO and stick to it, prolly wave with some printed paragraphs of labour law in front that manager's nose - it won't be a problem. But if your consciousness is too troubling - stay away from this field of engineering.

5. If you want to easily "disconnect" from work and go do something else - dev's career might be a problem. Yes, your computer might be shut down/hibernated/suspended after 5pm until 9m the next morning, but your brain will most likely keep trying to solve the problems you were facing. You'll prolly use your own computer to do some research, check some forums, docs, etc. - this is all your free time, this is all your family time donated to your manager (and to your personal knowledge base). Not to mention, all these things you learn will soon enough become obsolete, as new technologies will replace them. So if you'd like to easily "disconnect" after 5pm, doing that as a dev might be too challenging.

Comments
  • 1
    Wowwww!!!

    Now these are some solid reasons.

    Absolutely wonderful. Loved reading this.
  • 3
    6. If you like to share your day with your family/friends, then it's a good bet this won't happen if you're a dev. There are 2 reasons:
    - most likely tgeae people are non-tech and will not understand a thing you're talking about - that will be an experience no better than complaining to a mirror, to a wall or a car in a parking lot. You will have to find someone elae to share your experiences with [like dR], and find some other topics to talk about with your fam. Which is not easy, as your work consumes most of your time...
    - your days are too monotonous to have anything to share. What are you going to say? That you've solved yet another bug? That requirements have changed again? I.E. The same things you tell them every day? You might as well add that the water is wet and fire is hot - frankly, the last two will most likely be more entertaining that the former ones.

    Dev life is paved with problem solving, however, these problems are usually too technical and/or monotonous to be anything even close to a topic for a conversation.

    Ffs, I even find it hard to find a dev topic to talk to the dev/tech part of my fam about!
  • 1
    I felt 2, 5, and 6 the most.
Add Comment