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?
162 karma · joined December 30, 2018
https://domwillia.ms
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?
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 :)
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!
It really is a beautiful country. And today is the first day of snow :)
Glad it’s going well for you. I have recently taken the plunge and moved to Estonia :)
It's worked well for a couple of years, and helps me keep the long term goals in mind.
[^1] https://github.com/DomWilliams0/name-needed/blob/develop/.pl...
I write about Rust side projects occasionally.
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 written a blog post covering the technical details: https://domwillia.ms/minecraft-fs
[^1]: https://blog.rust-lang.org/inside-rust/2022/02/03/async-in-2...
‘aspell -c text.md’
Cheers for the link to the meeting notes in the other comment chain, sounds like a great rabbit hole
Good luck with the mammoth project! I think the fun will really start when it comes to running mini programs to test against a reference implementation and finding out we implemented core parts like method/field/(super)interface resolution totally wrong.
Oh, and optimisation too. It’d be cool to implement a JIT but that’s a long way away