Content
@
0 reply
0 recast
2 reactions
Grand Busta
@grandbusta
I am revamping a 3.5 years old code. A lot of things are very inconsistent and i blame myself for writing it then😅 Revamping it now and i can see how super improved i am.
1 reply
1 recast
2 reactions
Grand Busta
@grandbusta
One of the things i learned when revamping is that all these popular structures might not be what your project needs. Most times, it could be very better to create a set of rules that your code must adhere to. It’s very project specific!
1 reply
0 recast
0 reaction
Grand Busta
@grandbusta
Every of your code must adhere to these set of rule. How do you handle queries? How do you handle updates? How do you name your files and folders? These things makes your code very easy to navigate. You will move very fast. Interesting to see.
1 reply
0 recast
0 reaction
Grand Busta
@grandbusta
These rules should actually span to how you do your imports(case of JS and TS). Do you want to import as a default and then access? Or you want to destructure? Just pick one and stick to it. Be consistent.
1 reply
0 recast
0 reaction
Grand Busta
@grandbusta
Also unnecessary abstraction can actually wound you on the long run. Repetitions are not bad when done judiciously. DRY(Don’t repeat yourself) is not cast on stone. Be wise with your choices. Sometimes you just have to repeat.
1 reply
0 recast
0 reaction
Grand Busta
@grandbusta
Jumping on the trending technology is another risky thing. It is good to experiment but make sure you give yourself the possibility of switching when things go wrong.
1 reply
0 recast
0 reaction
Grand Busta
@grandbusta
If you want to use an external API, avoid community api wrappers that are not properly maintained if possible. Would so much prefer to call the APIs directly and configure the way you like.
1 reply
0 recast
0 reaction
Grand Busta
@grandbusta
Don’t let the ease you’re looking for be what will make your life hard.
0 reply
0 recast
0 reaction
