evanmarshall

8 ms·

1.
by evanmarshall 3mo ago
I want OpenBSD on blu-ray
2.
by evanmarshall 3mo ago
Yes, but the tests and evidence won't include screenshots, it'll be more curl requests and logs.
3.
by evanmarshall 3mo ago
The tooling hasn't caught up yet to code gen speeds. If we generate code at AI speeds, we need verification at AI. Bottlenecks move. If code gen was 50% of the time and now it's 0% (it's not), you only get 2x faster. Lots of
4.
by evanmarshall 3mo ago
It uses code diffs + descriptions + issues as the base test plan (acceptance criteria + regression). You can then interact with it to shape it more towards what you want.
5.
by evanmarshall 3mo ago
Our first POC was slow, expensive, and bad quality. It takes a lot of effort to build the infrastructure, memory layers, QA code gen fixtures and more to get it working reasonably well.
6.
by evanmarshall 3mo ago
Static code analysis is great but it misses a lot. Agents that read code make guesses about how code would execute, Ito makes a guess and then verifies it with runtime evidence.
7.
by evanmarshall 3mo ago
Cloud agents + workflows in the future. Escaping single player mode on a machine. Cursor has background agents. I build Ito.ai to do code reviews that actually run code. There's many more but the future is escaping your local machine.
8.
Show HN: Ito – Code reviews that run code(ito.ai)
10 points by evanmarshall 3mo ago|8 comments
9.
by evanmarshall 8y ago
Steel wool works pretty well.
10.
by evanmarshall 8y ago
I think attacking one problem at a time is the best way to go about (at least for me). I noticed that many people try to make drastic changes all at once and then fail at all of them. I'd recommend trying one thing and just doing that
11.
by evanmarshall 8y ago
thanks, this worked for me
12.
An ethereum-backed digital tombstone for my uncle(mark-kane.com)
2 points by evanmarshall 8y ago|0 comments