I just learned a knot is faster to untie than to pick apart. Wait, no, I mean I learned this about my code. Let me explain. | Career Advice - Talk Freely
I just learned a knot is faster to untie than to pick apart. Wait, no, I mean I learned this about my code. Let me explain.
Last week a senior dev on my team watched me spend 45 minutes untangling a mess of if-statements in our booking system, then she said, 'you know you could just pull the whole thing out and start over, right?' I did, and it took 10 minutes. Does anyone else have a habit of stubbornly fixing bad work instead of just deleting it?
Ever try to salvage a half-rotten board instead of just cutting a new piece? That was me with code for way too long. I'd sit there nursing some broken function back to life because I wrote it, so it felt like quitting to toss it. Then a buddy watched me wrestle with a login flow for an hour and said the same thing your senior dev did. Rewrote it from scratch in 15 minutes and it worked better than the original ever did. Now when something smells off I give it one honest pass and if it's still a mess, it goes in the trash.