Young Hands Club

January 27, 2020

WH Review of Week 15 (Jan 20th - Jan 26th)

Filed under: Will Haack — Will Haack @ 4:04 a.m.

This week I focused on planning. I wrote three relevant articles: my computer build plan, a review of the fleetbot the run, and an article on fleetbot's pseudocode.

Putting together the computer while having my written plan at my side was a delight.1 I feel quite silly for only having read 1-2 short guides before first attempting to build the computer. I doubt the men who built the Panama Canal just winged it.

With regards to TheFleet, investigating the problems I ran into and reading through my source (including cl-irc) has given me a much clearer idea of what I need to get done. Certain issues I was going to address by writing more lines of code I discovered can be fixed instantly by removing one line.

Benefiting from scoping out problems before tackling them is not surprising. I will continue to develop my planning/organizational skills in the upcoming weeks. Building anything interesting requires careful planning, so I better get good at it.

On a different topic, I've been more distracted than usual the past few days. There was non-negligible time wasted spinning/derping. On a quantitative level I had decent output,2 but my articles this week had glaring problems. I am due for a penance article that goes over what occupies my headspace and how I am currently wasting time.

  1. BTW, I took photos (with a phone camera :`( ) of the process and logged how long each task took me. I underestimated the time of most steps by a few minutes. The task whose time I grossly underestimated was plugging in all the cables: that took 1.5hours instead of my predicted 20mins. []
  2. My productivity dwarfs the output I used to have when I first joined #o (not that that's a great standard to hold myself to) []

1 Comment »

  1. On the bright side, merely assembling a computer is not quite on the same scale of an endeavor as building Panama Channel! So hopefully the planning is appropriate in size and scope as well.

    Re footnote 1: estimates are still estimates, you shouldn't aim for precision at the minutes level really; but if it's constantly underestimate, you need to keep that in mind so you add a rounding-up correction overall. Do note also that estimates are useful for relatively large tasks/projects rather than for each 10-15minutes task and so there is - and there should be - some baked-in space for adjustment/compensating the underestimates with the overestimates overall. You know, like all approximations after all, it's not that a line will fit the points everywhere, it's enough if it doesn't stray too far and otherwise balances errors on one side with those on the other side.

    As I was saying in chan: this part is gold.

    Comment by Diana Coman — January 27, 2020 @ 11:31 a.m.

RSS feed for comments on this post. TrackBack URL

Leave a comment

Work on what matters, so you matter too.