danenania

5 ms·

1.
by danenania 4d ago
Outside of mathematics, I think it’s very rare for a single human to understand 100% of any complex undertaking, and this was true long before AI.
2.
by danenania 13d ago
Another suggestion to get the most bang for your buck: use the best model you have access to with max reasoning for planning, implement with a smaller model/lower reasoning, then review with the big model. Repeat as needed. Input token
3.
by danenania 2mo ago
Super cool! Can you talk a bit about how you built it?
4.
by danenania 2mo ago
Being one of the people on this list... yes I would personally say it's mainly about agency and determination, and being obsessive/perfectionist about details. I think YC selects for these traits much more than domain expertise or
5.
by danenania 3mo ago
> publicly reported numbers Anyone can google it /shrug
6.
by danenania 3mo ago
I’d also point out that LLM inference revenue already totals more than 100B annually based on publicly reported numbers. Almost none of that is replacing knowledge workers. Almost all is increasing their productivity. So empirically what yo
7.
by danenania 4mo ago
Cool, good to hear. I think it’s often the case even within an individual file or change that it’s 90% routine and 10% critical to review. That’s a big part of the problem in my mind.
8.
by danenania 4mo ago
Interested to try this! Have you thought about separating the parts of a PR that are routine/uninteresting from the parts that are load-bearing and need more careful review?
9.
by danenania 4mo ago
I mean it’s quite literally a command line interface to their tool… what else should it be called that differentiates it from a pure browser flow? What you are describing sounds more like “TUI” than “CLI” imo. A CLI is an interface —it’s a
10.
by danenania 4mo ago
You can’t get every detail right up front, but you can build a robust foundation from the beginning. The argument seems to be that AI is causing managers to demand faster results, and so everything has to be a one-shotted mess of slop that
11.
by danenania 4mo ago
You’re assuming that building something robustly is significantly more time consuming than the “quick and dirty” version. But that’s not really true anymore. You might need to spend another hour or two thinking through the task up front, bu
12.
by danenania 4mo ago
Getting the model to do it is the skill.
13.
by danenania 4mo ago
Line by line is no longer what I need to think about. I think about types/schemas, architectural division, contracts between services and components, how to test thoroughly, scaling properties, security properties, and these kinds of t
14.
by danenania 5mo ago
It takes very little time to polish now.
15.
by danenania 5mo ago
That sounds pretty much the same as it’s always been? It used to be: “Does the happy path work? Then ship it! There’s no time to make it robust or clean up tech debt.” Now there actually is time to make things robust if you learn how to d
16.
by danenania 5mo ago
> thinking, abstracting, deciding how to apply your knowledge and experience, searching for information None of this requires coding by hand. I can do those things better and faster with agents helping me. That incudes unfamiliar areas w
17.
by danenania 5mo ago
That’s also true without AI. Engineers want more time to polish and businesses want to ship the 80/20 solution that’s good enough to sell. There's always going to be a tension there regardless of tools.
18.
by danenania 5mo ago
This is a great point. We’re very much in a transitional phase on this, but I personally do see signs in my own work with agents that we are heading toward the main deliverable being a readme/docs. The code is still important, but I co
19.
by danenania 5mo ago
If it’s broken and the dev can’t debug it, the business won’t have much of a choice.
20.
by danenania 5mo ago
If a junior builds something with agents that turns into a mess they can’t debug, that will teach them something. If they care about getting better, they will learn to understand why that happened and how to avoid it next time. It’s not all
21.
by danenania 6mo ago
It seems like that could change the math quite a bit, since you’d presumably be losing a lot of capacity to failures. I’d assume you would have a much higher failure rate in space, and component failure is already pretty common on earth.
22.
by danenania 6mo ago
What about maintenance? I’d naively assume that’s the killer.
23.
by danenania 6mo ago
> I thought we might finally have a high profile prompt injection attack against a name-brand company we could point people to. These folks have found a bunch: https://www.promptarmor.com/resources But I guess you mean o
24.
by danenania 6mo ago
tmux makes it easy for terminal based agents to talk to each other, while also letting you see output and jump into the conversation on either side. It’s a natural fit.
25.
by danenania 7mo ago
Gemini 1.5 Pro actually has 2M! No other model from a major lab has matched it since afaik. Edit: err, I see in the comment below mine that Grok has 2M as well. Had no idea!
26.
by danenania 7mo ago
I built a tool at work that allows claude code and codex to communicate with each other through tmux, using skills. It works quite well.
27.
by danenania 7mo ago
The correct answer is “Postgres would handle it, but if it needed to scale even higher, I’d…” The point of a system design interview is to have a discussion that examines possibilities and tradeoffs.
28.
by danenania 7mo ago
I have a similar process and have thought about committing all the planning files, but I've found that they tend to end up in an outdated state by the time the implementation is done. Better imo is to produce a README or dev-facing doc
29.
by danenania 7mo ago
Very cool! A noob question about how models handle video: do you do everything via sending frames as images to the model at some framerate? Are there tricks to avoid what it seems like would be massive token use from this approach?
30.
by danenania 7mo ago
I’m very pro AI coding and use it all day long, but I also wouldn’t say “the code it writes is correct”. It will produce all kinds of bugs, vulnerabilities, performance problems, memory leaks, etc unless carefully guided.

More ›