Nice, I’ve been looking for something like this for a while.
I’ve noticed on my huge catkin cmake project that cmake is checking the existence of the same files hundreds of times too. Is there anything that can hook into fork() and provide a cached value after the first invocation?
Code is a liability. When I let a LLM take the wheel, I end up with thousands of lines of crappy abstractions and needless comments and strange patterns that take way more brain power to understand than if I did it myself.
My current workflow has reverted to primitive copy paste into web chat (via Kagi Assistant). The friction is enough to make me put a lot of thought into each prompt and how much code context I give it (gathered via files-to-prompt from simonw).
I have little experience with frontend and web apps, so I am trying out a supervised vibe coding flow. I give most of the code base per prompt, ask for a single feature, then read the code output fully and iterate on it a few times to reduce aforementioned bad patterns. Normally I will then type it out myself, or at most copy a few snippets of tens of lines.
What doesn’t work I found is asking for the full file with changes applied already. Not only does it take a long time and waste tokens, it normally breaks/truncates/rewords unrelated code.
So far I’m happy with how this project is going. I am familiar with all the code as I have audited and typed it out nearly entirely myself. I am actually retaining some knowledge and learning new concepts (reactive state with VanJS) and have confidence I can maintain this project even without an LLM in future, which includes handing it over to colleagues :)
What worked for me in Estonia was to find a C++ job (robotics) then gradually push for Rust as I gained seniority and autonomy. Now maybe 70% of the code I write is Rust, both robot side and backend :)
I’m having this problem now. I want to publish a post about recent months of progress on my project, but while writing it I found the solution isn’t complete and still has some flaws, so I feel I must put some more weeks of work into the code first before I can publish the post…
I’m trying to practice writing “this doesn’t work yet” acknowledging in the post that it isn’t fully done, and publishing the bloody thing. We will see how it works next time I sit down to write!
I wrote game engine after game engine with various languages and designs. Somehow I’m still motivated today to rewrite navigation in my 15th engine for the 3rd time.
Yep, moved to Tallinn from England for work 6 months ago. Being a software engineer classes you as a “top specialist” so getting a visa and residence permit was very straightforward.
It really is a beautiful country. And today is the first day of snow :)
For my long term side project I just dump ideas into a barely organised backlog.md [^1]. After finishing a feature or taking a few months away, I normally dive back in by browsing this and choosing the next milestone.
It's worked well for a couple of years, and helps me keep the long term goals in mind.
It uses a custom static site generator because I needed to procrastinate somehow before starting the first post... Now it's nicely stable and punishing new posts is quick and easy
I’ve noticed on my huge catkin cmake project that cmake is checking the existence of the same files hundreds of times too. Is there anything that can hook into fork() and provide a cached value after the first invocation?