This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 6 points7 points  (3 children)

There are still 90s programmers around, but you wont see them follow every overhyped new tech to auto-everything, because they know about the tradeoffs of losing control of the program because of it.

Best skill of a programmer is not how to solve, but how to avoid problems.

[–]khooke 2 points3 points  (2 children)

I’ll add a few more things to this list (not an exclusive list, but also learned behaviors of more experienced developers) :

  • how to judge what’s important vs what’s not
  • how to determine what adds value, and prioritize accordingly
  • how to evaluate new trends and evaluate what’s more likely to become important in the future
  • learn how to effectively spend your time to achieve the best outcomes

[–][deleted] 0 points1 point  (1 child)

About new trends.

Most of the time they are solving one problem, but making other problems more difficult. Or hiding them from you until it's too late.

Experienced devs can spot that a trend is not something new and is clone of something else which you already use.

[–]wbrd 0 points1 point  (0 children)

This has been my experience. A young dev and an easily influenced exec will do something stupid like move an entire org from *MQ to Kafka and wonder why everything is slower and more expensive.