Algorithmic approach to coding and debugging.


1. Summarize our goal in one sentence.

2. Outline the high-level process of coding/debugging our particular issue.

3. Gather all necessary background information.

4. Do a more in-depth outline, step-by-step.

5. Outline the exact details of the algorithm.

6. Use TDD to fix the issue.

Comments

Post a Comment

Popular posts from this blog

Dream jobs list

Image
In addition to Research Engineering, this: Is exactly what I want to do, if I don't decide to bridge next into cybersecurity or embedded. I would just work here and never leave until my writing took off. Or even just not leave even when it does.  Fully remote and at the intersection of tech, math, code, physics, and art. Also, I use Adobe's software on a daily basis.  If by a miracle I got an interview, well -- I'd be studying out the wazoo for it. 
Read more

Hobble Creek Half: The slow passage of time marches us towards our inevitable death

Image
or, how I almost died alone in a Honey Bucket porta potty (to be fair, if you are not alone in there that is kind of weird) and lost 3/4 of a summer Saturday and 1/4 of Sunday to dying in various toilets but at least got my Elite 100 medal hell yeah See, I couldn't PR because I had to finish in 6:21 pace. For the memes! * So, in June I ran the Timp Half. No issues. 1:23:55. Course PR. I slowed down after the initial smooth downhill out of the canyon, as designed. I felt a calf cramp coming on, so I slowed down just a tad, was fine, and didn't have to plod my way to the finish line. Runtastic Events always does a great job.  Then on Saturday I ran the Hobble Creek Half in 1:23:09 (so 7 seconds off my PR) and almost died. In fact, I am currently still dealing with the after effects of whatever just happened to my body.  Let us see exactly how the wheels came off:  It was BREAKFAST. Yeah, I screwed that up.  What I had: * 180 mg Crystal Light Energy * 1/4 Bucked Up...
Read more

St. George Marathon: 3:08, but at what cost? 💩 (TMI alert)

Image
I don't know who's carrying the boats, but I'm carrying the logs. 💩💩 This was my second full marathon, having run St. George last year in 3:34. I only tapered for a week and I never stopped lifting except for the day before. I knew I was capable of going much faster than 3:34 overall and that's what I set out to do this round.  This training cycle peaked at 62mpw and had a lot of lifting, but not as much as I'd like. Usually I did 1 speed workout per week and maybe threw in 1-2 fast miles for my long runs with the rest at fairly comfortable conversation pace. My longest training run was 22 miles.  We drove down Friday (I took the day off work and slept 9 hours, hallelujah.) Saturday, probably slept 6.5-6.75 hours, but woke up a LOT. I did core in the morning for about 5-10 minutes just to get the system up and running and also vanity. I wore my favorite Big Cottonwood 2025 tee with my Revel bib clips.  The start line was freezing. I did manage to work on all of my...
Read more