julian37
Joined 16 years ago
Karma
3,512
Submissions
501
Member since
Jun 17
Recent submissions
Comment · 1 month ago
Comment · 7 months ago
Use planning+execution rather than one-shotting, it'll let you push back on stuff like this. I recommend brainstorming everything with https://github.com/obra/superpowers, at least to start with.
Then work on making sure the LLM has all the info it needs. In this example it sounds like perhaps your hypothetical data model would need to be better typed and/or documented.
But yeah as of today it won't pick up on smells as you do, at least not without extra skills/prompting. You'll find that comforting or annoying depending on where you stand...
Comment · 1 year ago
Works fine here (134.0 on macOS)
Comment · 2 years ago
kdrag0n's first post about this on HN, afaict: https://news.ycombinator.com/item?id=34100779
Amazing how far they've got since, in just two years. As others have pointed out, it's already "boring" software in that it just works. And that's no small feat because this kind of tool requires all kinds of low-level hackery to make work, and make work fast. Hats off!
(Happy user here if you couldn't tell.)
Comment · 2 years ago
You mean what Docker for Desktop can't do? It does have a few unique features (for example automatic HTTPS for containers) but that's not the point. The point is that it's much faster, the fan runs quieter, the battery drains less, memory gets hogged less, it crashes less, the UI is smoother, the updates actually work, and it keeps improving at a steady pace. The fundamentals just work a lot better.
Comment · 2 years ago
OrbStack is where it's at on macOS these days. It's so much better than Docker Desktop, it's not even funny. It's in a whole different league.
I'd take this article with a grain of salt when it doesn't even mention it, or any of the other alternatives.
Comment · 2 years ago
This. For graphql-ruby: https://graphql-ruby.org/operation_store/overview
Comment · 2 years ago
I don't how hard it is, but part of the problem is the FDA's chronic understaffing issues:
https://www.washingtonpost.com/opinions/2023/01/10/baby-form...
https://abcnews.go.com/Business/story?id=3944507&page=1 (2007)
Related: https://undark.org/2023/02/01/for-a-host-of-vital-lab-tests-...
Comment · 2 years ago
Right, but fetching rows along with a bunch of related rows from other tables isn't niche, it's literally the _raison d'etre_ of GraphQL (simplifying a bit because GraphQL types don't necessarily map onto db tables.)
It's something lots of apps need all the time.
Comment · 3 years ago
Closure Compiler follows the same line of thinking:
https://github.com/google/closure-compiler/wiki/FAQ#closure-...
Comment · 3 years ago
Reminds me of Hand Cheese (Handkäse), a regional specialty popular around the Frankfurt area. It's delicious, quite pungent but with a deep flavor. It gets its name because it was traditionally formed by hand (from Quark, a harmless dairy product similar to cottage cheese). Around these parts one can expect clean hands as well, so there really is nothing untoward about the final product -- except perhaps for its name. Give it a try if you happen to be passing through!
Comment · 3 years ago
Surely the UI code is what responds to clicking "reveal" and therefore, if compromised, could fetch the secret even without a click?
Comment · 3 years ago
I've found that this PL/pgSQL implementation also works well when you don't need maximum performance:
Comment · 4 years ago
That's hardly a convincing example. All of these points can be solved elegantly with a stream abstraction, which can be cheap or free given a sufficiently advanced language and compiler.
As for legal or policy reasons, those still aren't reasons to write boilerplate code. Your reimplementation can be tight and reuse other abstractions or include their own.
Now, if the instructions were more explicit in forbidding (generic) tool use then perhaps we'd have something to talk about. I'm not surprised a handwavy "we're trying to evaluate you" isn't enough to stop it from trying to make up for its own shortcomings.