947 karma · joined November 3, 2015
Say hi : luke (at) lukebechtel.com
Current: - Founder @ Reasonote (https://reasonote.com) - AI/ML Consulting @ Positive Sum Products (https://positivesum products.com)
Former: - Principal AI/ML Eng. @ Regscale (https://regscale.com) - Dir. of Eng. @ Revaly (now Cadchat) (Acq. in 2023) - Cofounder @ Collider Inc. (Acq. in 2022)
I wrote more about Spec Driven AI development here: https://lukebechtel.com/blog/vibe-speccing
I agree these things don't think like we do, and that they have weird gaps, but to claim they can't reason at all doesn't feel grounded.
Yeah it isn't a panacea but it has afforded me less frustration than the alternative of jumping straight in.
> Since what I've been working on is just a mash-up of other people's ideas
Totally, I find most work I do, if I'm honest, is in this bucket. LLMs are pretty good at "filling in the gaps" between two ideas like this
this is the idea behind my recent post actually[1] where I recommend people use AI to write specs before they code. If all you have to do is a human is edit the spec, not write it from scratch, you're more likely to actually make one.
it's only useful if it'll be used!
The md files are actually pretty great for shareability, versioning, and picking up where you left off.
I talked about a similar, but slightly simpler workflow in my post on "Vibe Specs".
https://lukebechtel.com/blog/vibe-speccing
I use these rules in all my codebases now. They essentially cause the AI to do two things differently:
(1) ask me questions first (2) Create a `spec.md` doc, before writing any code.
Seems not too dissimilar from yours, but I limit it to a single LLM
Which embedding types did you try? I'm surprised that embeddings weren't able to take you further with this.
"The Emotion Machine", by Marvin Minksy (the AI view)
&
"The Art of Empathy", by Karla McLaren (the Internal / Emotional View)
o3 still drives really well for me.
etc