Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ubercore
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
4 ms
·
31.
▲
by
ubercore
3mo ago
The big hammers buy you more confidence and need less supervision. In pure task execution you _might_ smash the ant with a small surgical hammer, but if you absolutely need it smashed, that's when people still reach for the big hammer.
32.
▲
by
ubercore
3mo ago
I think tokio does userspace threads running on a thread per core. At least by default.
33.
▲
by
ubercore
3mo ago
All the cargo deps would be "upstream", and pulled on build.
34.
▲
by
ubercore
3mo ago
Reputation for reliability can be directly impacted by thousands of upstream dependencies, though.
35.
▲
by
ubercore
3mo ago
It's partly a problem because the narrative is still "rewrote Bun in Rust in 11 days". And they didn't do that, if you consider quality of code. And now people look and see "look what you can do with an LLM in 11 da
36.
▲
by
ubercore
3mo ago
Well annotated code is fine in Python too.
37.
▲
by
ubercore
3mo ago
I just skimmed that linked paper. Only mention I found of cooling is: > Cooling would be achieved through a thermal sys- tem of heat pipes and radiators while operating at nominal temperatures. Isn't that drastically underselling po
38.
▲
by
ubercore
3mo ago
Been there done that. My point is that even with Fable being a big improvement, it still needs constant feedback. The loops themselves are a lot better, but it still needs judgement calls, and Fable will often take an odd direction, and if
39.
▲
by
ubercore
3mo ago
Anecdote, yes, but I am _right now in the middle of helping Fable clean up a mess_. Complex code is hard and Fable still makes mistakes.
40.
▲
by
ubercore
3mo ago
The problem is the _way_ AI will solve an AI bug. I've seen the loop countless times. There's a creeping complexity and brittleness that creeps in over time as more and more complexity is left purely to the LLM agent. It will beco
41.
▲
by
ubercore
3mo ago
How am I misreading this part of the readme? > What is explicitly not done yet — this is the active roadmap, in order: > CPython test suite (cpython-full): the standing grind; failures are clustered and burned down per wave.
42.
▲
by
ubercore
3mo ago
I was trying to say "not confident at all" but hedged a bit too much. I see this as a case of the "quick to get to a POC that falls apart after sustained development for the same reasons it didn't work pre-Fable" pr
43.
▲
by
ubercore
3mo ago
I hate to be that guy, but... one week old project, clear signs of vibing. I will be shocked if the remaining work listed (cpython test suite) proceeds in any reasonable timeline. This is a pretty hard problem to just solve in a week. EDIT:
44.
▲
by
ubercore
3mo ago
It's also postgres, but timescaledb's licensing (and therefore its lack of good support in azure managed postgres) is a bummer.
45.
▲
by
ubercore
3mo ago
I love postgres, but the complexity of using it for everything starts to get pretty high, compared to more tailor-suited tools. We should probably use it for _more_, in general, but the cost of "everything in postgres" is generall
46.
▲
by
ubercore
4mo ago
I'm not wading into the schizophrenia part, but inner monologue doesn't necessarily imply constructing a fully formed sentence you then repeat to yourself.
47.
▲
by
ubercore
4mo ago
Willing to bet the fact that you went looking to improve is the thing that made the difference, not anything you learned from those seminars.
48.
▲
by
ubercore
4mo ago
Cursor, from my companies perspective at least, seems to be handling charming leadership to get enterprise AI contracts in place, compared to the alternatives. That's feeling like the moat from my first-hand experience. Easy single con
49.
▲
by
ubercore
4mo ago
I had a similar experience, I was working on a jupyter notebook, and Claude knew that it could write code that would use a DSN with read-only database access so I could run it. Opus just plugged along. First Fable session with it, it tried
50.
▲
by
ubercore
4mo ago
It's really not that big for a postgres db in a lot of places, honestly.
51.
▲
by
ubercore
4mo ago
75% of the value on PR review is team visibility
52.
▲
by
ubercore
4mo ago
The jobs AI crisis is me being stressed and overworked as management demands more AI, showy (but shallow) "look I made a skill" presentations grab attention, and my PR review queue grows every day as people generate more code than
53.
▲
by
ubercore
4mo ago
Agreed, and it's the same in software. Probably the biggest time-sink right now as a tech lead is people going from idea to fully-fleshed-out PR, and then having to go back to have a discussion of "was this the right thing to do&q
54.
▲
by
ubercore
4mo ago
I make a version of this happen with Aerospace on macOS.
55.
▲
by
ubercore
4mo ago
I've never even seen someone suggest a rebase master onto feature workflow! TIL.
56.
▲
by
ubercore
4mo ago
Didn't read the article, sorry, but this reminds me we _really_ need more cool acronyms back in our industry.
57.
▲
by
ubercore
4mo ago
You haven't used messenger much then, if you're comparing the complexity of the two.
58.
▲
by
ubercore
4mo ago
I love this angle as people learn how to interact with LLMs. Doesn't matter what the LLM is, we are still people and I think there are consequences to shoveling rudeness at a thing that talks to you like another person!
59.
▲
by
ubercore
4mo ago
Yes, this is one of the most ineffective parts of public trading. It's impossible to say what the leadership here would have done without such _wild_ changes in the surrounding environment. While I understand the argument that in the e
60.
▲
by
ubercore
5mo ago
They could, easily, but then it wouldn't taste like Hershey's chocolate and people don't like that.
More ›