Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
zbentley
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
52 ms
·
841.
▲
by
zbentley
1y ago
Setting aside malicious government employees, the authN part of this seems like something for which technical solutions exist. Governments could operate PKI trusts and link their employees’ development credentials (in the US, this would be
842.
▲
by
zbentley
1y ago
> it was doomed before the first line of code was written The Direct File system was live more than a year ago, I thought: https://www.usds.gov/impact-report/2024/directfile/ …or did you mean “eventually d
843.
▲
by
zbentley
1y ago
Honestly, that mixing of concerns is the biggest benefit, at least for me. While Erlang clearly lost the popularity war, using it (well, Elixir in my case) feels like going to an alternate timeline where it wasn’t a given that a good appl
844.
▲
by
zbentley
1y ago
Interested, not skeptical: do you have sources or analysis you like which discuss the declining enrollment you mentioned?
845.
▲
by
zbentley
1y ago
Unsubstantiated hunch: the hypervisor is doing a shitload of probes against the host system before allocating/configuring virtual hardware devices/behaviors. Since the host's hardware/driver/kernel situation can cha
846.
▲
by
zbentley
1y ago
All very fair points! I think it is perhaps much more situational than I made it out to be, and that functioning in an “hours” environment is only possible as described if some organizational patterns are in place to make it work.
847.
▲
by
zbentley
1y ago
I think that discussions in this area get muddied by people using different definitions of “rapidly”. There are (at least) two kinds of speed WRT tests being run for a large code base. First, there is “rapidly” as pertains to the speed of r
848.
▲
by
zbentley
1y ago
Nothing you said is wrong, but: > makes sense to people in silos Investors, especially PE investors, are in a motherfucker of a silo. The sign on their silo says "short term growth at all costs. ZIRP/dotcom boom days are never
849.
▲
by
zbentley
1y ago
It uses a huge amount of what I’m terming “getattr bullshit”: many/most fields of ORM objects are only determined at runtime (they’re technically determinABLE at early runtime during Django initialization, but in practice are often n
850.
▲
by
zbentley
1y ago
I hope you're right. But how is WASM going to answer questions like "how does the application play sound?" or "how does the application request a password from the system keychain?" WASM solves a lot of problems, bu
851.
▲
by
zbentley
1y ago
I see the real utility these tools are providing to many folks, but ... It just feels so ugly . Square peg meets round hole. We built all these tools for defining security boundaries for user-installed applications, and it turned out tha
852.
▲
by
zbentley
1y ago
What’s blocking IO have to do with this topic? Also, I don’t feel like that’s true: Rust has the exact same non blocking IO primitives in the stdlib as any other systems language: O_NONBLOCK, multiplexers, and so on. Combined with async
853.
▲
by
zbentley
1y ago
As someone who overused bullet points before it was AI-cool and doesn’t write with the assistance of AI (not due to a general anti-AI belief, I just like writing by hand) I have also started getting that feedback a lot lately. Who knows, ma
854.
▲
by
zbentley
1y ago
I'd suggest "high-cast" and "low-cast". They draw attention to the thing that people usually mean when they talk about strong (not static) typing: whether operations in a language bias towards automatically coercing
855.
▲
by
zbentley
1y ago
Not entirely wrong, but … only one of Clojure and Kotlin is close enough to Java that it’s inspiring meaningful improvements in the upstream ecosystem. If the “dissing” hypothesis were true I’d expect Clojure to be the one influencing the m
856.
▲
by
zbentley
1y ago
I mean…the cloud message queues that use HTTP are not good examples of quality software. They all end up being mediocre to poor on every axis: they’re not generalizable enough to be high quality low level components in complex data routin
857.
▲
by
zbentley
1y ago
Another terrific write up on this subject is Jen Pahlka (cited in the article)’s essay on the “cascade of rigidity”.
858.
▲
by
zbentley
1y ago
That article spends an awful lot of words to get to what amounts to: - manual QA processes suck - without determinism there can be no rigor or objective quality evaluation; everything is just vibes and gut-checks - we don’t know what went w
859.
▲
Gen AI: Too Much Spend, Too Little Benefit? [pdf]
(goldmansachs.com)
2 points
by
zbentley
2y ago
|
0 comments
860.
▲
by
zbentley
2y ago
When I was junior IT at a smaller place (150ish people), we set up DMARC for the first time in "quarantine" mode. Plan was to eventually set it to full reject but only if folks didn't report issues for a month or so. While it
861.
▲
by
zbentley
2y ago
I'm not going to spend a long time responding to your comment, since it seems accusatory and rude; if you modify it to be more substantive I'll happily engage more. The one specific response I have is: it's not that I > sa
862.
▲
by
zbentley
2y ago
Thanks for the thoughtful response. I generally don't want to get into the specifics of what Martin advocates for. Whether to prefer or eschew comments, give methods a particular kind of names, accept a performance penalty for a refa
863.
▲
by
zbentley
2y ago
> The only way around that would be with stupid method names Yep. Method names make terrible comments. No spaces, hard to visually parse, and that's before acronyms and ambiguity enter the conversation. As the person who often write
864.
▲
by
zbentley
2y ago
It's striking to me how out of touch Martin seems to be with the realities of software engineering in this transcript. Stylistic refactors that induce performance regressions, extremely long and tortured method names for three-line met
865.
▲
by
zbentley
2y ago
> If you just blindly write the event, then you always know that fact about customer 1234 in any future query. Unless the write times out or the DB is down for maintenance when the event arrives. Sure, you could block acknowledgement o
866.
▲
by
zbentley
2y ago
Debezium is popular in this space, though it does bring more tools into the CDC/CQRS stack: https://debezium.io/
867.
▲
by
zbentley
2y ago
I've worked on (and variously built and ripped out) systems like that, and I end up in the "more trouble than it's worth" camp here. Context-ish things do have considerable benefits, but the costs are also major. If cont
868.
▲
by
zbentley
2y ago
I think this isn't shoddy engineering; I think you disagree with a design tradeoff that was consciously made here. If CLIs are designed around facilitating the easiest means of editing the most commonly-edited word, different programs
869.
▲
by
zbentley
2y ago
Because I switch computers (often, for work), and what's muscle memory on one then becomes "command not found" on others without the alias. Many of those computers I don't control and can't say "well, everyone
870.
▲
by
zbentley
2y ago
Oh, are you zdykstra? If so, thanks for creating an invaluable tool! > you can create a zpool checkpoint before doing something 'dangerous' (disk swap, pool version upgrade, etc) and if it goes badly, roll back to that checkpoi
More ›