vishvananda

5 ms·

1.
by vishvananda 2mo ago
I've been doing a lot of experimenting with this with a c++ compiler project[0]. I definitely experienced a lot of challenges, but I do believe it is possible to end-up in a consistent space by putting in some very careful guardrails.
2.
by vishvananda 2mo ago
From harness? Because people expect a squishy set of things from a harness that is different from what I end up building. I end up with a rigid internal structure that the harness uses in-turn (tests with clear error messages, tools, etc.)
3.
by vishvananda 2mo ago
I’m definitely on the deterministic code train as well. All of my success for long running tasks has been around wrapping the agentic harness (cc, codex-cli, etc.) in a deterministic workflow with deterministic gates. We need a name for thi
4.
by vishvananda 3mo ago
For me it was earlier this year when I started dusting off some old stalled projects and had an agent work on them. In a few days I: * Built a clone of the Alpha Zero implementation[1] my team built at oracle * Ported my hobby NES emulator
5.
by vishvananda 4mo ago
I've been experimenting quite a bit with long-horizion agentic coding[1] and I have also noticed that agents seem to perform worse when forced into certain architectural patterns. I have found that is a bit better when including the co
6.
by vishvananda 4mo ago
I think there is a flow in most organizations from: llm -> prompt -> result llm -> prompt + prompt encoded as skill -> result llm -> prompt + deterministic code encoded as skill -> result I do think prompting to generate c
7.
by vishvananda 6mo ago
This is actually a very interesting moment to potentially overcome network effects, because more and more code is going to be written by agents. If a crdt approach is measurably better for merging by agent swarms then there is incentive to
8.
by vishvananda 1y ago
I share the concern based on the current productivity expectations but I did stumble across something recently which makes me feel a lot better. There was a change in the tax code that coincides with the beginning of the post-pandemic layof
9.
by vishvananda 1y ago
I am by no means an AI skeptic. It is possible to encode all sorts of things into instructions, but I don’t think the future of programming is every individual constructing and managing artisan prompts. There are surely some new paradigms t
10.
by vishvananda 1y ago
I'm really baffled why the coding interfaces have not implemented a locking feature for some code. It seems like an obvious feature to be able to select a section of your code and tell the agent not to modify it. This could remove a wh
11.
by vishvananda 2y ago
Heroku is turning the 12 factor manifesto into a community project and modernizing it. I posted my thoughts in a blog[1], and I'd love to hear what other people think! [1] https://medium.com/@vishvananda/the-rebirt
12.
Updating Twelve-Factor: A Call for Participation(blog.heroku.com)
11 points by vishvananda 2y ago|2 comments
13.
by vishvananda 2y ago
This is something I’ve been arguing for for a while[1]. I called it a “Framework Knowledge Base”. I think it needs to go a bit further and include specific code examples, especially for newer bits that are not in the training set. Ultimatel
14.
by vishvananda 2y ago
Doesn’t this already exist as https://www.npmjs.com/package/dotenv-cli ?
15.
by vishvananda 3y ago
I've followed Caleb on YouTube for a while, due to his MtG content. He is PhD in Optical Sciences that makes some very interesting AI art. He has created a new card game with hand curated AI art and some interesting rules aimed at solv
16.
by vishvananda 4y ago
Just reran the benchmarks from 10 years ago, python is only 37X slower than C on the benchmark now, and the go version is running faster than the C version. Python still has big productivity wins of course...
17.
by vishvananda 4y ago
Python is extremely slow for some tasks. I was surprised to discover how slow when I ran some benchmarks, despite having used python for many years at the time. It has been improving lately, but here is a blog post I made on the topic quite
18.
by vishvananda 4y ago
This is definitely an intriguing line of thinking. I too am constantly appalled by the complexity we introduce into the things we build, but I suspect a lot of it has to do with human issues that can't be solved by better technology. T
19.
Progrium Technology Thesis(progrium.com)
2 points by vishvananda 4y ago|1 comments
20.
by vishvananda 5y ago
I'm surprised that neither the documentary nor the review gets into the legacy of OpenStack. I may be biased, but it seems to me that a huge amount of the success of kubernetes is directly attributable to OpenStack. First, OpenStack pa
21.
by vishvananda 5y ago
In this particular case, some of the runs from iFit instructors are actually quite good, and it cool that it adjusts the speed and incline to match the instruction. Probably not worth the extra $$$$ but it is pretty cool. But now I also wan
22.
by vishvananda 5y ago
Thank you for this. I was hoping someone had figured it out but I hadn't found this yet.
23.
by vishvananda 5y ago
I hadn't been following the "Right to Repair" movement too closely until I discovered that NordicTrack recently locked their users out of Privileged Mode[0], which makes it virtually impossible to install 3rd party software l
24.
Locked out of 'God Mode', runners are hacking their treadmills(wired.com)
593 points by vishvananda 5y ago|460 comments
25.
by vishvananda 5y ago
You could always use a pointer for this, but admittedly it is pretty ugly when compared to a true optional type: func f(s *string) string { ret := "" if s == nil { ret = "default"
26.
New Tech Cuts into Rock Without Grinding It(wired.com)
2 points by vishvananda 5y ago|0 comments
27.
by vishvananda 6y ago
While the particular issue of network namespaces and locking the os thread was fixed, there is still c code that must run before the go runtime starts to work around the issue that you cannot do some of the necessary nsenter calls once you
28.
by vishvananda 6y ago
Go is actually a really poor choice for the container runtime because much of the container setup cannot be done from multithreaded code[0], so it has to be done in C before the go runtime initializes. I do think rust is a better choice for
29.
by vishvananda 6y ago
I was the main developer with a little support from the rest of my team. I moved on a couple of years ago and my team was RIFed a few months later, so likely they don't have anyone left to work on it.
30.
by vishvananda 6y ago
Nice work on this! If you cut out a bunch of the features supported by other containerization systems, the code gets quite short. My first one was in C and only a couple hundred lines. I worked on a full-featured rust container runtime whil

More ›