Do you ever struggle with your code? Like, you know the answer is there somewhere, but whatever is popping out onto the IDE from the keyboard is definitely not it?
After a few times of this, you finally have the mental model that aligns perfectly with the problem and the solution just flows out.
It feels good, right?
Do you ever try to get to that magical feeling without producing, for lack of a better term, the slop first? Whether it’s code, a blog post, an email, or just a systems architecture diagram?
It doesn’t work, does it. You end up spinning your wheels and producing the slop anyway.
Turns out, this is normal and expected and we should embrace the slop:
Here’s to bad code?
This post originally appeared in my daily email newsletter. If this post interested you, sign up below to get more like it, daily*.
*ish.
One thought on “First comes the slop, then the good stuff”