To be honest, this will not be impressive to a lot of developers out there. But for me it was an acomplishment and a moment of learning as a developer that consistently feels slow to catch up, not to mention often intimidated & needed a way to ease his own imposter syndrome. For now anyway.

Before I explain, let me show you my old work flow

The old but sort of simple way

Did you know that if you create a Github repository with your username you can unlock a secret? Go on, give it a try! You’ll be pleasently surprised with this alert

Backstory

At the time of this writing, it has been 7 months since the COVID19 pandemic had taken over the world. Making it harder for me & my group of friends to meet with each other. And then one day, one of us decided to put us all together in a Discord channel so we can still hang out virtually.

Discord lets you install bots like Pancake to do other stuff like loading songs from YouTube & playing it on voice channel everyone listening.

And then one day I thought “why waste such an opportunity?” I immediately got to work. At…

Tl:Dr — DRY for production code, sometimes ok in test code, but DAMP is preferrable.

(Disclaimer: Since I use Python 3 & Django on a daily basis i’ll be using snippets from them as examples.)

Since last year up until now i’ve been struggling with a concept of DRY coding. In a nutshell, “Do not repeat yourself”. So if you can find stuff that’s pretty repetitive, then chances are you ought to automate this to a single source. This way when specification changes you can reduce having to do multiple changes.

And this is great for production code. And probably okay for test code right?

Nope.

Well, theoretically (i thought) yes. We just don’t want to…