With my newfound enthusiasm of working with LLMs, I end up doing a lot of feature creep and scope changes, which may or may not even be useful (am I product manager now?). What I wanted to limit this creep is to use timers to keep myself accountable.

I want to work on this feature for 30 minutes, that's it. I fired up the timer on my watch and got started, but the timer was on my watch and i forgot about the 30 minutes limitation until the timer rang.
So I need a timer in my face which I can't ignore, but being on linux, I (surprisingly) couldn't find any already made minimal timer gui that did what I wanted, so I did what any engineer would do, build one. My aim was minimalism and the abiliity to pin it to my display. Sadly wayland doesn't allow applications to pin themselves, that job is allocated to the DE (KDE in my case). So after getting the base app to work, I setup KDE rules to pin it and called it day.
Until I opened my Mac at the end of the day to close out stuff from bed. Mac doesn't have a DE option to pin apps (at least not afaik), but luckily eframe/egui native method for pinning worked on mac, yay.

I entirely built this app using LLM, from start to finish in rust using eframe/egui. I do not know enough rust to eny write hello world by myself. Last I built a GUI app was with tkinter in python which made me wanna kill myself. So I was surprised by how well claude (opus 4.5) was able to get the app to work. I think in total it costed around 10$ to build it in terms of API usage. But I think most of that was my fault by using opus instead of sonnet or haiku. I'm sure a lot of tasks apart from the initial planning did not need opus.

And from my experience, haiku is also a capable model. I think a claude code feature to automatically prompt for which model to use for follow up convos would be nice. Or maybe once opus creates the todolist and appropriate context, it can hand it over to haiku/sonnet.