Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
tcoff91
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
61.
▲
by
tcoff91
5mo ago
I want a set of smaller ones if it's practical.
62.
▲
by
tcoff91
5mo ago
The quiet isn’t even the best part of passive cooling. It’s that the cooling will never stop working due to dust clogging fans.
63.
▲
by
tcoff91
5mo ago
Wow that is so dystopian.
64.
▲
by
tcoff91
5mo ago
Yes that’s exactly how I started coding!
65.
▲
by
tcoff91
6mo ago
Yes I love that my employer says go wild with it. But I feel like the leaderboard is dumb.
66.
▲
by
tcoff91
6mo ago
The perverse incentives created by these AI leaderboards are crazy.
67.
▲
by
tcoff91
6mo ago
It seems really dumb for the models to not due security related things. What if I want it to do a security audit of my own software that I'm building?
68.
▲
by
tcoff91
6mo ago
Mailing patches is the same as squashing commits. The Linux kernel would be much harder to maintain without messy history being carefully distilled down to well crafted patches. But mailing patches is a pain in the ass. VCSes should support
69.
▲
by
tcoff91
6mo ago
These calorie counting picture apps should be sued for false advertising.
70.
▲
by
tcoff91
6mo ago
Are you giving the LLM the weights of the ingredients as you go? Sounds like a great system.
71.
▲
by
tcoff91
6mo ago
The data entry is a pain in the ass with those apps when cooking food from scratch. It’s much much easier with LLMs and natural language and voice mode and pictures of a food scale and things like that.
72.
▲
by
tcoff91
6mo ago
I’ve found that the best way to deal with this is to add an entry to /etc/hosts for my local machine that fits the pattern for QA environment. Then I run a local reverse proxy with a self signed certificate. So I do local dev on
73.
▲
by
tcoff91
6mo ago
There’s a lot of humans I wouldn’t trust to be an assistant with access to my bank account. It’s bold to assume that within 2 years these things are going to be scam resistant. It’s going to be bleak when there’s articles about how “my agen
74.
▲
by
tcoff91
6mo ago
That's Anthropic. Codex is OpenAI.
75.
▲
by
tcoff91
6mo ago
I hope none of your accounts are associated with that email address that can be read by an LLM that has access to untrusted input. OpenClaw lives right in the prompt injection lethal trifecta. The idea of an OpenClaw instance having the abi
76.
▲
by
tcoff91
6mo ago
Yeah if this can truly just autonomously make great software, then where is all the new SaaS that is able to undercut incumbents by charging 10-20% of what they are charging?
77.
▲
by
tcoff91
6mo ago
Anonymous branches are amazing for when you are trying out a bunch of different approaches to a problem. As I search the space of possible solutions for what I'm really looking for, I end up with a tree of various approaches. Then when
78.
▲
by
tcoff91
6mo ago
Yes, the root of the problem is the workflow of the company being centered around GitHub instead of Git itself. This feature helps improve GitHub so it's useful for companies that do this this way. At our company, only admin users can
79.
▲
by
tcoff91
6mo ago
I run jj in colocated mode so I put stuff in .git/info/exclude if I want it ignored but not part of the main .gitignore
80.
▲
by
tcoff91
6mo ago
jjui TUI is incredible also
81.
▲
by
tcoff91
6mo ago
Well, I stand corrected.
82.
▲
by
tcoff91
6mo ago
Rebase the stack onto main.
83.
▲
by
tcoff91
6mo ago
It looks like in the UI if you base a PR on another branch you can just check a box to make it a stack. So I don't think you have to know the full shape of the stack in advance unless you're using the cli. I use jj to stack branch
84.
▲
by
tcoff91
6mo ago
It's crazy that you're getting downvoted for this take. This isn't reddit people. You're not supposed to downvote just because you disagree. Downvotes are for people who are being assholes, spamming, etc... If you disagr
85.
▲
by
tcoff91
6mo ago
Let's compare 2 approaches to delivering commits A, B, C. Single PR with commits A, B, C: You must merge all commits or no commits. If you don't approve of all the commits, then none of the commits are approved. 3 stacked PRs: I a
86.
▲
by
tcoff91
6mo ago
It's basically trying to bring the stacked diff workflow pioneered by Phabricator to GitHub. The idea is that it allows you to better handle working on top of stuff that's not merged yet, and makes it easier for reviewers to revie
87.
▲
by
tcoff91
6mo ago
Most editors have some kind of way to review github PRs in your editor. VSCode has a great one. I use octo.nvim since I use neovim.
88.
▲
by
tcoff91
6mo ago
I definitely am open to other possible developments and accept that I'm likely wrong just as basically everyone is wrong when predicting the future.
89.
▲
by
tcoff91
6mo ago
Hell yeah, those look awesome. I look forward to the autonomous versions that don't require fully manual remote operation. It'd be great if coordinators could have like an RTS-style view and command these like they're starcra
90.
▲
by
tcoff91
6mo ago
That would require global consensus and could ignite wars if there isn't global consensus. Seems very likely that this could have unanticipated consequences that could be worse, but admittedly this is an area I don't really know m
More ›