Sidewalk to Summit — build log
A note before this starts moving: Been quiet here for a few weeks — heads down building instead of writing about it, which is exactly the trap this devlog exists to prevent. So: catch-up first, then this becomes the actual habit. One running post, edited in place every time I do real work, newest bit on top. No pile of unpublished drafts allowed after tonight. Aug 11–16 — Not a build week:…
In the span of a few weeks, the project transitioned from quiet development to focused execution. On August 11-16, the team fine-tuned the plan with Melanie, testing the app's direction before further development. No work was shipped or demonstrated during this period. On August 10, a property test revealed an undercount in the plan engine, leading to the wrapping up of property testing.
The function estimating plan duration was found to be inaccurate, undercounting plan duration due to assumptions about training ramp growth and ignoring week one. This bug could cause plans to appear fine when they were actually falling short of expected fitness. CI also now includes typecheck, lint, and tests for every pull request, discovering four pre-existing security holes in dependencies.
A friend suggested adding more personality to the app's background, resulting in a hand-drawn illustration delivered in person. The next day, eight tasks were completed in roughly four hours, pushing the development faster than expected. This rapid pace led to five judgment calls waiting for the developer's final decision. On August 2, a baseline rule was discovered to punish beginners for being honest, causing underestimation of plan difficulty for sedentary users.
This issue was only caught by manually running the rule on a specific test case. On July 29, Peter joined the team for a focused session, resulting in six tasks being completed in ninety minutes. The biggest feature, generating a route based on user location, was moved to a future version to focus on other aspects first.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
