Levels has no passion for his projects. They're all quick grifts.

He does though, especially for the early ones like Nomadlist and RemoteOk. If you read his old blog you will see a significant portion of it is about digital nomadism.

The cognitive overload is more so people not understanding the slop they are generating. Slop piles on top of slop until a situation arrives where you actually need to understand everything, and you don’t because you didn’t do the work yourself.

probably not many Firebase users here but I love Firebase's Firestore

It's very bad to search stuff, or have structured database, also it costs a lot

its dirt cheap and you can do basic search

It's not cheap at all once you scale

I first used Firebase/Firestore recently at work, and I was kind of surprised on how it's easy to use. Not my first time with NoSQL databases, but was impressed still

I personally have no use for this type of workflow. I like parallel claude code instances in worktrees but nothing beyond that

Am not a fan of dealing with worktrees Maybe for larger longer lived tasks but the time spent on merges from different agents is definitely a big headwind for parallel work.

This seems handled by this new agent which is cool.

I gave up on worktrees and hacked together a solution with fine-grained lockfiles for editing, running builds, etc that worked surprisingly good for what it was

They have Claude Code web in research preview

It still doesn't support plan mode... I'm really confused why that's so hard to do

Ramp valued at $32B is a joke. Hopefully this sets a realistic benchmark for valuation. All Ramp did was spend more on ads and marketing. And CEO is now claiming their "AI Agents" are going to do something meaningful.

If Ramp is getting all the business, is there any reason to think they wouldn't command a much higher valuation?

Brex killed a ton of their customer relationships to "refocus" on larger biz. That created a lot of negative sentiment for the brand.

> All Ramp did was spend more on ads and marketing

That's distribution. It matters.

Ramp has a much more synonymous name, better recognition, and less bad reputation.

Distribution is king. Kudos to Ramp for that. My weird thesis is that for whatever reason Ruby on Rails shops just seem to survive more. I wonder if someone did a stack specific survival rate analysis.

Pretty sure Ramp uses Elixir.

Ramp is mostly their Python monolith. They have a blog post about their use of Elixir for one service but it's really not their core stack.

Brex was a lot more all-in on Elixir, including being one of the languages "stars," but moved to a more conventional stack (IIRC Java/Drop wizard microservices with Kafka to talk between them).

Ramp is (mostly) a Flask monolith with some sprinkles of Elixir at the very edges where sub-second performance matters.

the Ruby on Rails of Erlang, I guess. Maybe we just generalize the thesis to - the stack must be the ruby on rails of X language.

I'll give that and agree the underlying is a quibble.

feature request: tag startups with YCombinator and be able to visualize failure in terms of capital invested over time. my hunch is it's going up but would be cool to see the data

all fun and games until you need to debug the rats nest that you've been continually building. I am actually shocked people who have coded before have been one-shotted into believing this

If a bug rears its head it can be dealt with. Again, this is essentially already practiced by humans through breeding programs. Bugs have come up, such as deleterious traits, and we have either engineered solutions to get around them or worked to purge the alleles behind the traits from populations under study. Nothing is ever bug free. The question is if the bugs are show stoppers or not. And random walk iteration can produce more solutions that might get around those bugs.

Agree! Don't let it get too bad. See my other comment on debugging and refactoring being a core part of your workflow.