Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
riwsky
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
31.
▲
by
riwsky
10mo ago
> part of the problem was caused by bad design The entirety of the problem was that the design was bad! Adding a layer of abstraction is a design choice.
32.
▲
by
riwsky
10mo ago
I heard that Google and OpenAI also make coding models, but I’ve never bothered to confirm.
33.
▲
by
riwsky
10mo ago
Would be more maintainable if they injected the loading strategy to be used as a dependency from config instead of hardcoding it :/
34.
▲
by
riwsky
10mo ago
Where did he go/what’s he doing now? He’s clearly still big on AI coding, given https://steve-yegge.medium.com/six-new-tips-for-better-codin...
35.
▲
by
riwsky
10mo ago
JavaScriptScript?
36.
▲
by
riwsky
11mo ago
Because the incidence and cost of mistaken under-consistency are both generally higher than those of mistaken over-consistency—especially at the scale where people would need to rely on managed off-the-shelf services like aurora instead of
37.
▲
by
riwsky
11mo ago
Because intentionally fucking over their customers would be an impossible secret to keep, and when it inevitably leaks would trigger severe backlash, if not investigations for fraud. The game theoretic model you’re positing only really make
38.
▲
by
riwsky
11mo ago
So much of the tech debt work scheduling feels like a coordination or cover problem. We’re overdue for a federal “Tech Debt Week” holiday once a year, and just save people all the hand-wringing of how when or how much. If big tech brands ca
39.
▲
by
riwsky
11mo ago
Screw discipline, it’s a tooling problem. Making canary rollouts with automatic rollback the default would take a lot of investment up front, but then would make discipline at release time a non-factor.
40.
▲
by
riwsky
1y ago
what happens is that they're comparatively boring
41.
▲
by
riwsky
1y ago
So is Costar, the horoscope app, of all things
42.
▲
by
riwsky
1y ago
the underlying LLM service provider APIs require sending the entire history for every request anyway; the state is entirely in your local (or kilocode or whatever), not in some "session" on the API side. (There are some APIs that
43.
▲
by
riwsky
1y ago
Oh, if you’re an ex-hg guy, this makes this easier, then: jj is in many ways a renaissance for hg’s philosophy: https://ahal.ca/blog/2024/jujutsu-mercurial-haven/
44.
▲
by
riwsky
1y ago
Here’s where you're clearly wrong. The correct favorite in that corpus is Golden Gate Claude: https://www.anthropic.com/news/golden-gate-claude
45.
▲
by
riwsky
1y ago
42
46.
▲
by
riwsky
1y ago
No. The GP making a commit off of the first non-conflict isn’t the essence of the feature he’s talking about, just an example of what he can do next. He’d also be free to edit upstream to not commit, or split a change in two so that parts u
47.
▲
by
riwsky
1y ago
The criticism invoked “anyone with serious experience with schizophrenia”, implying the author of the article is not such a one. Citing the author’s experience is a perfectly valid rebuttal to that implication. It’s not an argument from aut
48.
▲
by
riwsky
1y ago
Humanity used fire for like a bazillion years before figuring out thermodynamics
49.
▲
by
riwsky
1y ago
> For those who’ve built coding agents: do you think LLMs are better suited for generating structured config vs. raw code? Raw code. Use case was configuring a mapping of health data JSON from heterogeneous sources to a standard (also JS
50.
▲
by
riwsky
1y ago
That exact workflow? It won't improve much. But it tends to change peoples' workflows. For example: let's say you have a few feature branches in flight at the same time, and you want to make a change to one of them to address
51.
▲
by
riwsky
1y ago
Great, now even computers need to leave the IC track if they want continued career progression.
52.
▲
by
riwsky
1y ago
“This meeting could’ve been an email”
53.
▲
by
riwsky
1y ago
A long time ago, in the four out of the six boxes below that contain a picture of a galaxy far, far away…
54.
▲
by
riwsky
1y ago
Perhaps LLMs are magic?
55.
▲
by
riwsky
1y ago
I’ve never onboarded or successfully convinced a colleague to use jj. But roughly once a month I find myself helping someone escape git hell that would either be easier to solve or avoided entirely with jujutsu. I’m not speaking hypothetica
56.
▲
by
riwsky
1y ago
You indeed can: https://jj-vcs.github.io/jj/latest/config/#set-of-private-co...
57.
▲
by
riwsky
1y ago
jj’s workflow isn’t about being careless with commits—it’s about time-shifting that care to when it’s most convenient. You’d split the commit later for the same reasons you wouldn’t want your text editor to force manually marking each line
58.
▲
by
riwsky
1y ago
It’s both. Their CLI has a lot of overlap with what you’d use jj for (rebasing, amending, etc), but does basically everything worse other than “creating stacked PRs”. Slower; refuses to work from a detached HEAD; gets confused more easily b
59.
▲
by
riwsky
1y ago
“Trauma” is a bit much.
60.
▲
by
riwsky
1y ago
Extremely amenable—my workflow shifted to match your description after I started using jj, because it makes that easier. Conceptually, it’s not “edit commits by adding on only parts of your staging area”, but “edit commits by only moving
More ›