Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
carlmr
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
19 ms
·
361.
▲
by
carlmr
2y ago
>PS: Recruiters generally come from the same cloth as car sales and sports, so they're not usually going to be the sharpest pencils in the drawer. Aren't you committing a similar mistake here, saying that recruiters can only re
362.
▲
by
carlmr
2y ago
>strangely enough after a while all those candidates who replied got rejected. That also seems like a bad interview strategy. Make a mistake and you're out? Did you have so many perfect people to hire that you could just sort out al
363.
▲
by
carlmr
2y ago
>An ice cream store in the desert should make money. Because the Intel ice cream store is in a hot city and only sells the same vanilla ice cream they've been selling for decades. While it's on a busy street with Nvidia, arm an
364.
▲
by
carlmr
2y ago
Maybe let AI finish the article.
365.
▲
by
carlmr
2y ago
And especially in large monorepos anything that understands the code can become quite sluggish. While ripgrep remains fast. A kind of in-between I've found for some search and replace action is comby ( https://comby.dev/
366.
▲
by
carlmr
2y ago
Maybe I should revisit async Rust. I haven't used that part of Rust in a while.
367.
▲
by
carlmr
2y ago
Funny, it's the same in Germany.
368.
▲
by
carlmr
2y ago
>For the record, if you do not know what a dict actually is, and how it works, it is impossible to use it effectively. While I agree it's good to know how your collections work. "Efficient key-value store" may be enough to
369.
▲
by
carlmr
2y ago
>All the doctors I've seen tell me that no, Covid doesn't do that "Strong arguments support the thesis that, through various mechanisms, COVID-19 infection can contribute to the development of hypertension." [1] At le
370.
▲
by
carlmr
2y ago
>In fact I bet that if we dug into it we would find internal memos written by UX engineers pointing out exactly what you wrote, and other engineers in response pointing out that all those functions on the touch screens are “non safety cr
371.
▲
by
carlmr
2y ago
>Aviation is a mature field. People much more clever than you or me spent decades of their lives thinking deeply about how to make it safe. I know this, and I'm not saying there weren't clever people working on it. Maybe that c
372.
▲
by
carlmr
2y ago
>(I don't think this affects your argument directionally, but worth noting.) Aside, but this is high class discussion culture I haven't seen on the Internet in a while.
373.
▲
by
carlmr
2y ago
>not sold for profit. The only way to ensure no profit would be to provide them for free. Which, granted, may be good still for the pharmaceutical companies to lessen the costs for approvals, but Hollywood accounting makes it impossible
374.
▲
by
carlmr
2y ago
I'm a big Rust fan, but async Rust is an abomination.
375.
▲
by
carlmr
2y ago
>You need to create an internal 3D model of the objects in the scene, and their relative positions in space across the length of the video. And no one told the model explicitly how to do that, it learned to do it "on its own".
376.
▲
by
carlmr
2y ago
>nudge the junior toward seeing the errors in their ways. At least plant a seed of doubt early on.
377.
▲
by
carlmr
2y ago
>I think you have a twisted assumption about how much care goes into aviation UX. The people who do these designs did much more than read a single book. I don't work in that sector which is why I went by the posted examples. Showing
378.
▲
by
carlmr
2y ago
You could of course blame the individuals for not knowing where which information comes from, but that wouldn't help in avoiding such problems in the future. I think it's a UX failure in some sense. It's important information
379.
▲
by
carlmr
2y ago
Australia is one of very few exceptions it seems: https://www.reddit.com/r/MapPorn/comments/tujqxf/voter_id_la...
380.
▲
by
carlmr
2y ago
What I'd like to see from the Democrat camp is making mail voter registration easier, making government IDs mandatory, and also improving voter identification. Maybe also moving all voting to Sundays, so most people have time. Better v
381.
▲
by
carlmr
2y ago
I think these are just general pitfalls that happen when you port something. Also thinking everything is safe from a security perspective because you don't use the keyword `unsafe` seems kind of naive to me. For one safety and security
382.
▲
by
carlmr
2y ago
>We don't always have the engineering tools to predict strong "wear and tear" models of such things in software like civil and mechanical engineers have for common bearings/gaskets/lubricants Because it's no
383.
▲
by
carlmr
2y ago
Understandable. I don't think there's a good way around this though. Even if you run valgrind on a C++ repo that hasn't seen much valgrind use, you'll get a lot of output. But that output is because the memory management
384.
▲
by
carlmr
2y ago
https://stackoverflow.com/a/45248015
385.
▲
by
carlmr
2y ago
>Only software development seems to believe that anything, anywhere reaches a magic state of "done" and will never need to be touched again. The problem is the mental model. There is a state of "done" for a lot of sof
386.
▲
by
carlmr
2y ago
It still seems like a valid use-case for AB testing. Ideally, you should maybe redo the design, something you could AB test if it helps. My guess is yes, because consistency in design usually makes people assume better quality.
387.
▲
by
carlmr
2y ago
>when they attacked SpaceX for not recruiting "refugees" to work on export-controlled dual use rocket tech. Sauce?
388.
▲
by
carlmr
2y ago
They don't need compatibility but functionality in the first place. Most AI workloads use an abstraction layer anyway, e.g. pytorch.
389.
▲
by
carlmr
2y ago
It's either strategic incompetence, technical incompetence, or both at this point.
390.
▲
by
carlmr
2y ago
Put in other words. Creating a graph of your assets should be a part of your checklist.
More ›