Coding: "Past you" vs "Present you"

Aniello Musella - Mar 30 '21 - - Dev Community

Have you ever thought about your progress that you made during your career as a coder?

Have you ever measured the distance from your past you and your present you in terms of quality or results?

Whoever you are, a senior with many years of experience or a junior that is at start of his career or why not, a newbie that is starting something new, there are always questions buzzing in your head like: Am I improved? Am I on the right path? Have I made some progress?

When these are the questions that are buzzing in your mind probably it's the moment to call Emmett Lathrop "Doc" Brown to bring you in the past to meet your past you (that probably you forgot) and check if you have made some progress.

In other words choose a time window depending on your seniority and shot yourself in the past. Once landed in the past choose a specific past project or activity and be critical!

In the best scenario "you should meet" a different coder less expert than you, a coder with a different coding style that made mistakes in terms of design, readability, usability and scalability, mistakes that now you wouldn't probably make.

In the worst scenario you don't spot any problems and you think how much you were good at coding!

What you'll see in this time travel will probably define your future you or the next past you (time travels are complex) but what matters is you'll probably find some of the answers that you are looking for.

See you!

AM

...I forgot... don't talk with your "past you" you risk to alter the time line :)

. . . . . . . . . . . . . . .
Terabox Video Player