Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
rgoulter
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
91.
▲
by
rgoulter
10mo ago
Right. Nix is a wonderful technology. But I would not argue it is practical if you can afford "just fix it when it breaks". A nix setup more/less requires you to pay all the cost up front. I appreciate putting in the effort n
92.
▲
by
rgoulter
10mo ago
Many comments discussing LLMs involve emotions, sure. :) Including, obviously, comments in favour of LLMs. But most discussion I see is vague and without specificity and without nuance. Recognising the shortcomings of LLMs makes comments pr
93.
▲
by
rgoulter
10mo ago
The writing certainly has the cadence & other writing techniques of an LLM reply. :)
94.
▲
by
rgoulter
10mo ago
Cute. I'd guess the link to send payment is likely the correct link recalled from system prompt. (Or it's as likely to be the actual link as in an intended conversation). But I think for "which model are you? which os_env var
95.
▲
by
rgoulter
10mo ago
I put emphasis on splitting spacebar into thumb keys just because the large spacebar is so ubiquitous. -- There's practically no downside to splitting the large spacebar into 6x keys. I think it's good if layout enthusiasts want t
96.
▲
by
rgoulter
10mo ago
By "expensive signal" I mean more like "hard to fake the enthusiasm" rather than "spent a lot of money". In terms of monetary cost, the DIY ones can be quite cheap. -- But it's still going to be more expen
97.
▲
by
rgoulter
10mo ago
> like Agile and OOP Ha. I think there's room to argue "Agile" is a popular bastardisation of what's meant by "agile software development", and with "OOP" we got the lame Java interpretation rather
98.
▲
by
rgoulter
10mo ago
> there is a massive difference between writing mocks and using a mocking library like Mockito How to reconcile the differences in this discussion? The comment at the root of the thread said "my experience with mocks is they were ov
99.
▲
by
rgoulter
10mo ago
Eh. I think the cultural context has changed. In "python paradox", 'knows python' is an indication that the developer is interested in something technically interesting but otherwise impractical. Hence, it's a '
100.
▲
by
rgoulter
10mo ago
> the engineers who care enough to invest in keyboards like this (1) spend a lot of time investing in their tooling and (2) are extremely productive I think (1) is true. Whereas, (2) may be less so. Or at least, "smart but unproduct
101.
▲
by
rgoulter
10mo ago
> I'll be honest, this is the big reason I don't get all the hype around coding agents. I do find them useful but typing isn't the bottleneck. Not even close. It's always possible to go slower for practically no cost.
102.
▲
by
rgoulter
10mo ago
> The problem is when you have to come off the happy path in nixos and now you're debugging some interestingly written c++ code that evaluates a language that has a derivation expressing what you wanted done. I agree that Nix or Nix
103.
▲
by
rgoulter
10mo ago
> The difference is, you can create proper abstraction modules that put everything together, from dependencies, to config files, firewall rules etc and have nice options for your abstraction. Yes, this is an understated benefit. The decl
104.
▲
by
rgoulter
10mo ago
> If everyone else is racing ahead, will the slowpokes be rewarded for their comprehension or punished for their poor metrics? It's always possible to go slower (with diminishing benefits). Or I think putting it in terms of benefits
105.
▲
by
rgoulter
11mo ago
> LLM-generated writing undermines the authenticity of not just one’s writing but of the thinking behind it as well. I think this points out a key point.. but I'm not sure the right way to articulate it. A human-written comment may
106.
▲
by
rgoulter
11mo ago
What do you find confusing about the document encouraging use of LLMs? The document includes statements like "LLMs are superlative at reading comprehension", "LLMs can be excellent editors", "LLMs are amazingly good
107.
▲
by
rgoulter
1y ago
In the article, the author does say "I am not advocating to write things from scratch", while also describing third party dependencies as liabilities (e.g. security vulnerabilities), that people are too trusting of third party dep
108.
▲
by
rgoulter
1y ago
The title is provocative and attention grabbing. -- It's completely fair game to react to the provocation rather than the substance of the article itself. (Or, rather, it's silly to use attention grabbing rhetoric, then complain t
109.
▲
by
rgoulter
1y ago
> I don't know what "fellow engineers" the author is accustomed to collaborating with, junior or otherwise, but the attributes enumerated above are those of a sycophant and not any engineer I have worked with. I read "
110.
▲
by
rgoulter
1y ago
> Is it simple? So what happens when you hit the cap, does AWS delete the resources that are incurring the cost and destroy your app? Sounds like you're saying "there aren't caps because it's hard". > If you w
111.
▲
by
rgoulter
1y ago
A pair of articles, then: "Is Betteridge's Law Useful?" and "Is Betteridge's Law Useless?"
112.
▲
by
rgoulter
1y ago
> It’s too slow and instead of focusing on formulating my thoughts or capturing what’s being said AFAIU, if you're trying to take notes capturing what was said in a conversation between people.. to some extent you're going to n
113.
▲
by
rgoulter
1y ago
> I usually don't have to read the notes again. Yeah. For several kinds of notes, the value from writing is in doing the writing to assist thinking. Once I write it down, it doesn't need to hang around in my head.
114.
▲
by
rgoulter
1y ago
> With an LLM, it will never get annoyed, aggravated, think less of the person, or similar. Between people, it's extremely commonly considered impolite to request excess help from other people. -- So, having an info retrieval 
115.
▲
by
rgoulter
1y ago
I get the impression from the article that the author is writing in support of "LLMs are dangerous; e.g. they instruct people to make bombs". (I suspect that the author is in favour of regulating/restricting access to LLMs).
116.
▲
by
rgoulter
1y ago
Hmm. "poor software design" suggests a high risk that something might go wrong; "poor development practice" suggests that mistakes won't get caught/remedied. By focusing on particular errors, there's the p
117.
▲
by
rgoulter
1y ago
This reminds me of Steve Yegge's discussion of "n00b programmers". Yegge has more broadly reckoned there are two types of programming styles: fast/prototyping (wherein you just fix problems as they come up when you run t
118.
▲
by
rgoulter
1y ago
The DeepWiki tool itself seems pretty neat. It has a pretty good go at collecting documentation from across the codebase and organising it in one place. It has a pretty good guess at coming up with documentation which isn't there. It s
119.
▲
by
rgoulter
1y ago
It's a 'tap-hold' key, so the "tap" functionality is activated separately from its "hold" functionality. Though, in order to get the same effect as "hold down backspace", e.g. QMK lets you have &
120.
▲
by
rgoulter
1y ago
Regarding "not supposed to do that": the docs mention you can install packages with commands like "nix-env -iA <package name>", using nix approximately the same way as apt or pacman. -- Trouble is, this is kindof a
More ›