How to Make a Better Code in a Nutshell

Didik Tri Susanto
Teknomuslim
Published in
1 min readSep 4, 2016

You have promised that you would make a better code for the next project.

You were spending a day to think what infrastructure & code pattern would you used in this project

You stayed up in late night to refactoring code to make sure your code is follow the pattern, maintenable, and human friendly.

You wrote some regression test and build automated test to make sure your code is not broke after you made of change

You enjoyed to work in this project, and thought like, “I will never wrote a crap code anymore, not for this project”

Suddenly,

You have been ordered to speed up project delivery in “no-make-sense-time”.

Slowly you forgot the pattern because you need to finished fast and didn’t care what pattern were used.

Refactoring is wasting time.

Regression test & automated test is a lie.

Technical debt everywere.

You didn’t care, you have to deliver fast.

You ended like, “yeah i wrote a crap code again. I will get better in next project”.

Repeat for the next project.

--

--

Didik Tri Susanto
Teknomuslim

Proud to be Moslem | Introvert | Backend Engineer | Laravel Developer