Curious what problems you expect to matter in the next couple of years.
Thx!
Essentially, it’s like VSCode Peek definition but with a different visual style, and similar to the same functionality of source insight but free and in Linux.
The purpose is to read xv6 source code. I have found some parts of the kernel, e.g. the file system to be convoluted, and I need to follow quite a few jumps to form the system mindset. Having such a small tool is very helpful.
Actually it doesn’t look too hard to implement. Maybe I’ll write it myself in QT.
Imagine a whiteboard that has sticky notes, writing, little tokens and trinkets and the board also becomes a digital version that you can iterate on.
I really like to plan with my hands and in MY memory, but still love the utikity of planning digitally of course.
It feels like a much more flexible approach than an expensive proprietary whiteboard. Would a camera-only setup cover your use case?
A loooong time ago I had one of those notebooks (rocketbook I think) that you would take a picture of and the software would detect it and upload a digital version of it, it was clunky though. But the thing I liked about it was the little icons you would color in that would denote what kind of note to save the page as.
I have a lot of systems, but I could really use a Jarvis at work right now and it seems like the whole damn promise of AI is to deliver that. I’m waiting.
I want to plan, but I don't want to be on the computer yet. But if I plan non-digitally, it's slower, I can't copy/paste, and then I don't really have good access to it unless I have it with me.
But if I plan too much digitally, it's stored in digital memory, not my memory.
I'm really struggling to find something to mitigate this. I wish I had a tactile miro board that also created the miro board online.
Instead of brute-force method of selecting the appropriate test suites by path or similar, have LLM analyze changes and propose the set of test suites that is relevant to the change.
If there are new complex tests added to the change, estimates how many times to run them to ensure they are not flaky to begin with (hundreds? or thousands?).
When I exit the ssh session, it terminates (or "pauses").
I've wanted to make it for a while but never got around to it.
kubectl run -i --tty --rm debug --image=busybox --restart=Never -- sh
Doesn't use ssh though.
I hate DevOps. I have to do multiple commits to implement something.
I would love to be able to have access to the same env as the CI so that I could prototype the script/job on my own machine before committing to git. Most things are using Docker anyway, so it should be possible.
I hate that I need to write commands in Yaml files, commit (or use the browser) and then look at the result.
Solve this and I would pay for it.
This is what I miss whenever I have to do devops...
Perhaps the ability ability to stop at a specific point in the script and being able to modify any commands and execute the step and then continue the script until it fails again.
You know .. debugging interface would be a killer feature that would save so much time developing scripts.
