Orbit · Explore

Programming · by Faisal Al Saud · 2026-10-04

What is worth spending money on for tools with limited time?

Part of me wanted the fancy version with all the tools. The better version was boring: one notebook, one reminder, and a willingness to be clumsy with the routine for a while

53 sparks · 12 comments

Comments

Rafael Almeida · 5 likes

I think the bad version of this advice causes a lot of frustration. It sounds small, but the setup matters

Tiny Sparrow · 4 likes

could be regional too

Silver Rider · 0 likes

Now I want a spreadsheet

Urban Baker · 10 likes

Now I want a spreadsheet

Grace Parker · 0 likes

Beautifully concise

Ren Suzuki · 1 likes

This comment has main-character footnote energy

Aarav Sharma · 5 likes

Thanks that actually helped

Chiara Romano · 4 likes

I would log the input, the expected output and the actual output first. Once those three are visible, the bug usually stops feeling mysterious. The cozy part is easy to underestimate

Oliver Smith · 0 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. The 6-minute rule is underrated

Avery Johnson · 13 likes

short answer: yes. Long answer: also yes

Ananya Rao · 7 likes

I think both things can be true

Yui Tanaka · 0 likes

try making a tiny reproduction with no framework code. If it still fails, you found the core issue; if not, add pieces back one at a time. My friend tried it in Cape Town and had the opposite result