What Motivates Junior Developers To Make Fun of Someone Else’s Code | by Jesse Langford | Mar, 2022

And the methods they’re damaging their careers

Regardless of the motivation, making enjoyable of another person’s code achieves nothing.

Large because of Brian Christensen for uplifting this text.

Some time in the past I wrote an article about three habits junior developers should avoid. Bryan commented on the publish about his expertise with junior builders trashing the code of others and the way annoying it’s. That obtained me serious about the instances it has occurred to me, and instances when I’ve accomplished it.

I felt the subject deserved its personal write-up as a result of the act of trashing the code that others write isn’t a foul behavior — it is a damaging one.

Under are a couple of motivations I imagine junior builders act on after they make enjoyable of another person’s code. I’m basing these alone expertise as a junior developer making the error myself, and on my expertise mentoring junior builders. When you really feel there are others, please let me know.

Earlier than I proceed, I need to current this text in a diplomatic style, however in case you’ll forgive one outburst, I really feel it’s vital to get my uncooked emotional emotions throughout on this: In case you are a junior developer, and you’ve got a behavior of constructing enjoyable of different folks’s code, cease, it makes you appear to be an fool.

You aren’t gaining clout with anybody; you’re doing the alternative. I promise you your superiors suppose much less of you each time you do it.

With that out of the way in which, let’s proceed.

I used to be responsible of this one a couple of instances after I was a junior developer. I wished to impress my boss so I made enjoyable of some code that I had come throughout once we had been doing consulting work. It felt like a simple method to get amusing out of him and show my programming data.

Now that I’ve been on the opposite facet of the interplay, and had builders come to me and make enjoyable of another person’s code, I’m assured I achieved the alternative.

I might love to listen to suggestions on this, however I’ve by no means as soon as been impressed when a junior developer confirmed me another person’s code and instructed me how dangerous it’s.

To this present day, I get a sense of disgrace and cringe after I bear in mind it.

There have been a couple of instances when the code being made enjoyable of is definitely poor high quality. In these circumstances, I err on the facet of empathy for the developer who wrote it. I’ve launched code I’m not happy with due to loopy time pressures or app necessities altering mid-development. I might hope if somebody noticed it they’d give me the good thing about the doubt.

In these circumstances, the junior developer making enjoyable of the code has by no means been given a extremely difficult challenge. Their journey up to now has been in managed environments the place the stakes are low. For them, the one rationalization for dangerous code is incompetence. They don’t but respect that sooner or later, everyone seems to be requested to construct one thing they don’t absolutely perceive, with much less time than they want. Not everybody who has written dangerous code is incompetent.

I bear in mind the challenge the place I lastly understood this. A couple of years in the past, I requested our CTO if I could possibly be extra concerned in frontend improvement at work. I used to be seeking to develop my data and capabilities. HTML, CSS, and jQuery had been all that I had expertise with.

I used to be then requested to construct a Monorepo with React and TypeScript. For these unfamiliar with JavaScript and net improvement, that’s like having expertise constructing wagons and being requested to construct a automotive. Ultimately, I used to be in a position to get every little thing working and the challenge is reside to this present day, however components of that codebase aren’t optimum, to say the least.

I’ve had this one come to me in two varieties: The primary is when a junior developer comes throughout code that’s extra advanced and nuanced than what they’re used to seeing. They mistake this code for poor high quality as a result of they’re unable to learn it.

Not all code is written with readability in thoughts. Typically it is written to be as environment friendly as humanly doable. Usually I discover this to be true with costly database operations or advanced asynchronous logic. Wherever that effectivity and price are carefully associated.

The second type is after they see code that isn’t overly advanced; it’s simply written in a method they don’t acknowledge. If you first begin out it, may be straightforward to suppose that the one manner code is written is the way you do it. If the one code you ever learn is your personal, others will at all times look international. With extra publicity to the work of others, this notion ought to go away.

Hopefully, this subject was informative. My intention is to not put down anybody who has this behavior. I extra need to give them an perception into the thoughts of somebody who’s watching.

More Posts