marviel

5 ms·

1.
by marviel 1y ago
Thanks for sharing this blog post is a great speculative deep-dive.
2.
by marviel 1y ago
it mentions native multimodality somewhere in either the Arxiv or post -- seems like it might handle it well?
3.
by marviel 1y ago
nice! Can't agree more on Vibe Speccing. I wrote more about Spec Driven AI development here: https://lukebechtel.com/blog/vibe-speccing
4.
by marviel 1y ago
how do you account for the success of reasoning models? 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.
5.
by marviel 1y ago
have often wanted something like "liquid types", but didn't know what it was called! Thanks for this
6.
by marviel 1y ago
there is now I suppose! ;) 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
7.
by marviel 1y ago
I'm almost to this one in my read through! I'm excited to get to the "information age" arc
8.
by marviel 1y ago
I totally agree! 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 ac
9.
by marviel 1y ago
def cleanup inactive specs over time. it's only useful if it'll be used!
10.
by marviel 1y ago
Yeah just learned about this! The md files are actually pretty great for shareability, versioning, and picking up where you left off.
11.
by marviel 1y ago
I need to try Claude Code's plan mode! Definitely feels useful.
12.
by marviel 1y ago
Totally. Yeah I think your approach is a solid take!
13.
by marviel 1y ago
Thanks for the writeup! 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 essential
14.
Vibe Specs: Vibe Coding That Works(lukebechtel.com)
39 points by marviel 1y ago|8 comments
15.
by marviel 1y ago
I've found that people who " good due to naivety ", are less reliably good than those who " know evil, and choose good anyway ".
16.
by marviel 1y ago
i need this in ableton
17.
by marviel 1y ago
yeah -- I saw it's built on "open source foundations", do you know what project this is?
18.
Semi-Sync Meetings: Stop Wasting Our Time(lukebechtel.com)
31 points by marviel 1y ago|0 comments
19.
by marviel 1y ago
Thanks for sharing! Which embedding types did you try? I'm surprised that embeddings weren't able to take you further with this.
20.
From Heaven to Hell: The Odd Vertical Limits of Land Ownership (2018)(99percentinvisible.org)
2 points by marviel 1y ago|1 comments
21.
There Are N+1 Hard Things in Computer Science(lukebechtel.com)
3 points by marviel 1y ago|1 comments
22.
by marviel 1y ago
There are two good books that explore this concept from different angles: "The Emotion Machine", by Marvin Minksy (the AI view) & "The Art of Empathy", by Karla McLaren (the Internal / Emotional View)
23.
by marviel 1y ago
"Wired For Story" is a great book that discusses an alternative set of "Story Atoms" which can be combined to create unique, compelling stories.
24.
by marviel 1y ago
what do you dislike about it?
25.
by marviel 1y ago
mermaid probably.
26.
Trying out llama.cpp's new vision support(simonwillison.net)
1 points by marviel 1y ago|0 comments
27.
Cursor Readonly Rules(reasonote.com)
1 points by marviel 1y ago|0 comments
28.
Why John Wilson Can't Stop Filming(youtube.com)
2 points by marviel 1y ago|0 comments
29.
by marviel 1y ago
We've found a lot of success with this approach at Reasonote -- would love to hear about how others solve the same issues.
30.
Cursor: Readonly Rules(reasonote.com)
3 points by marviel 1y ago|1 comments

More ›