--- Day 27 | ⌛1h | Total: 50h --- Building an OSS time-tracker Today I was literally just thinking about stuff. I noticed when I change and save start/stop time that duration doesn't get updated automatically, but only when I refresh the page. Since I derive duration from start/stop times (that are saved in the db), I got confused. I'm using @tan_stack query through @WaspLang, shouldn't it all get auto updated? Now it's obvious that is because duration is also an input field, which has its own state. So there are two ways to modify the same thing ultimately. I have to keep them in sync manually, since no system can know what I actually want to achieve here. That all got me going through a bunch of things - React methods, react-query behaviour, etc. Got nothing (externally) done, but also cleared up a bunch of things to myself. Hopefully tomorrow I actually get around to coding something :D. I bootstrapped TrackIt with https://opensaas.sh/ (a free, open-source boilerplate starter for React/Node), and you can see the full source code here: https://lnkd.in/dTV2S_un
Next.js | React | shadcn | Tailwind | v0.dev | cursor.ai | Anthropic API | AWS EC2, S3, IAM, Lambda, API Gateway, Sagemaker | git
1dWas the insight one many times is required to think at an UX abstraction level when trying to solve what one thinks is a purely code level issue? Thanks for sharing your thought process!