As a solo web developer, I struggled with time management. Looking at my to-do list, I sometimes felt like a chef trying to cook ten different pasta dishes at once.
In my haste to keep up with incoming orders, I sacrificed the boiling time.
I skipped best practices like unit tests, thorough comments, and documentation early on in development. Sound familiar?
Then, some of my once-small clients started to grow. They invited others to the feast. I realized my undercooked spaghetti code was about to be exposed.
I scrambled to refactor my code, adding unit tests, comments, and drafted basic documentation.
I didn't want to look like a chef who can't cook al dente.
From then on, I always take the boiling time seriously. When creating code, I include a lean version of best practices from the beginning and incorporate it into my issue planning.
It saves me the hassle down the road and I don't have to swallow my pride in front of clients.
About Ambreen Dar
Ambreen designs for thrillseekers. She left the classroom behind to chase adventures in publishing, then dove into digital marketing's deep end. New tricks abound, but Ambreen's four furry fans still think she's top dog. Alongside Rebekah and Sam, Ambreen makes BRIL.LA's magic - and wouldn't have it any other way.