loading...
Cover image for How to get your code re-written

How to get your code re-written

arandilopez profile image Arandi López ・2 min read

This is one of the great skills that "Senior developers" have today and here I'll list the steps to follow in order to have your code re-written once it's done.

Do not follow any convention.

You are a Senior Developer, any convention from a geeky group of programmers won't tell you how to code. Your code is beautiful by itself. Why do you need to correctly indent your code? It is not your fault that the IDE of others does not correctly format tabs and spaces.

Do not test your code.

You do not need it. It's your code and it's perfect. The tests are only a waste of time and you do not have that time. If you were not taught about tests in school it's because they are not that important. Those software engineers are very suspicious about your standards (or lack thereof), your code does not need to be tested. Also the tests are not safe, there is no one like a user really testing it, right?

Do not use design patterns.

Design patterns just make your code less understandable. We all know how the switch, if, and for statements work, so deep nesting them won't hurt anyone. You don't have to improve that code structure. You're a Senior Developer and you know what you're doing and you're doing it right.

Do not extend libraries, take them and modify them.

You are a great Senior Developer, so great that you could take jQuery and "improve" its methods. You don't have to plug anything. You can take the source and make your changes on it. You are so great.

Do not use automated tools, or minify your files.

We know that doing things manually is better than automating those repetitive tasks. Webpack and Gulp are tools you do not need.

You do not need to think thoroughly about your software solutions.

You are a great Senior Developer, obsessed with that database without relational and use it in ALL, EVERYWHERE. Don't start any research about how much it will cost, Just use it, you know that "one size fits all", anyway that "relational" thing is so outdated. Anything you say MUST be used, and by now you already are a Solution Architect.


These are just some of the steps to follow in order to get someone to throw away all your code. A good Senior Developer should be open minded in order to increase the quality of the product in which he/she works.

Unit testing and acceptance testing are part of the code, one without the other are not complete, so invest your time to know the benefits of implementing tests methodologies in your projects. Do not ignore the Junior developers you have there. They just want to improve the code.

Originally plublished on Medium in spanish

Thanks to Miguel Coronel for his revisions

Posted on by:

Discussion

pic
Editor guide
 

Yep, definitely, don't! ;) == great article
I believe this comes with a certain level of developer's maturity (don't mix with seniority, word 'senior' is overused and abused).
Mature developers care for their code and they know their business domain. They know the hype, but they choose wisely what to use, where, and why ;)

 

Currently re-writing some code. This resonates.

 

It would be funny, if I had not seen EVERY one of these in my own personal experience... great satire!