Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
sshine
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
43 ms
·
661.
▲
by
sshine
2y ago
Not exactly my point. I meant to say: I think the quality varies both per factory and over time. There's a lot of complexity in industrial production. From the outside it looks like there's only the classic and the revamped design
662.
▲
by
sshine
2y ago
I also believe the amount of panel gaps varies a lot per factory.
663.
▲
by
sshine
2y ago
Same experience with my 2022 Model Y: Have yet not had a single problem for two years. Surely the problem lies in a high variance in the production of later models. Like when you visit a stellar restaurant and come back years later to reali
664.
▲
by
sshine
2y ago
There is something beautiful about global, mutable state: Your program must be really small and scoped for this to make sense. Also, kudos for providing so many corner cases to avoid that are non-trivial to formulate. It feels like one of t
665.
▲
by
sshine
2y ago
Most certainly it's about prepping for the zombie apocalypse.
666.
▲
by
sshine
2y ago
I somehow ended up doing the same. Probably as a result of too many failed heroic attempts at modifying read-only code in one big go. Now any heroic modification of code comes in a series of incontroversial, isolated and testably idempotent
667.
▲
by
sshine
2y ago
Yes, but you'd have to invite each interviewer by their GitHub handle. An unlisted repository would be one that is public to those who know the URL.
668.
▲
by
sshine
2y ago
It should be “LLM training data has been backdoored.”
669.
▲
by
sshine
2y ago
The watermarks are both PDF metadata and slight variation in wording. The metaphor of a watermark indeed falls short, and it should perhaps be called fingerprinting.
670.
▲
by
sshine
2y ago
NixOS suffers a little from rapid upstream changes like Arch. You can pin nixpkgs and bump when you feel like it (or when a version of something isn’t recent enough), which is great. However, bumping every three months always renders my con
671.
▲
by
sshine
2y ago
On a roadtrip ten years back we chose to navigate by map and compass, and avoid highways. With sat nav I don't even try to read the exit signs; I just follow the blue line. It takes me 10-20 drives somewhere before I have the muscle me
672.
▲
by
sshine
2y ago
I use LLMs as a translation tool, and make sure to generate JSON flashcards. Sometimes it is more important to get a point across in another language than it is to learn that language. Computers being automatable, you can use it to create a
673.
▲
by
sshine
2y ago
I assume you disagree with there being such a thing as "responsible AI use", because besides that, I completely agree with everything you write, including my own experience of "spot wrong answers, but feel becoming lazy"
674.
▲
by
sshine
2y ago
> sshine reply above is coming from a very conflictual mindset. "Can I still use AI and not be caught? Is it cheating? Does it matter if it's cheating?" First off: Since your opinion is the popular one, "sshine repl
675.
▲
by
sshine
2y ago
> please do not use AI assistants during the application process. We want to understand your personal interest in Anthropic without mediation through an AI system, and we also want to evaluate your non-AI-assisted communication skills.
676.
▲
by
sshine
2y ago
Projects are personal projects, or at least projects in which you did a distinguishable effort. They don't have to be public to the whole world, you can have links that are only in your resume. But if they're on GitHub, they have
677.
▲
by
sshine
2y ago
I can't speak for job interviewing, but having recently completed 3rd-semester trade-school oral exams in Java programming: It is really important to watch people code. Anyone can fake an abstract overview.
678.
▲
by
sshine
2y ago
I use LLMs to shorten my verbose email writing style. It’s AI anti-slop and I presume people like it.
679.
▲
by
sshine
2y ago
100 WPM at 98% accuracy. It used to be 80 WPM. Then I learned Dvorak, which also boosted my QWERTY +20 WPM. Now I switched to a split keyboard, and I'm slowly gaining my typing speed. I went from 20 WPM to 65 WPM in two weeks. It'
680.
▲
by
sshine
2y ago
It’s a human thing: Treat people with intimidation, and they’ll be nice to you out of fear. Treat people nicely, and they’ll walk over you. (Treat people with cautious respect, and they don’t know where to put you in the hierarchy. Or some
681.
▲
by
sshine
2y ago
Ubuntu, ThinkPad
682.
▲
by
sshine
2y ago
My previous 7 positions: Firmware (bare-metal) Firmware (Linux-embedded) Blockchain (mixture of cryptography and network programming) Platform (DevOps / Kubernetes) DeFi R&D (Smart contract compiler / smart contracts) Full-sta
683.
▲
by
sshine
2y ago
> Async Rust (by default) can allocate memory For bare-metal Rust firmware, you would always use no-std, which excludes a default allocator. I understand from what you're saying that the principal difference between embassy-rs and
684.
▲
by
sshine
2y ago
Thank you for the elaborate explanation. I understand the definition of real-time. I just don't understand why you need an operating system, compared to building a real-time firmware application with a runtime that contains a scheduler
685.
▲
by
sshine
2y ago
Having a PhD vs. making that API call might ironically suggest you don’t emanate hands-on product thinking. I know PhDs in data science and language technology who are not startup material because they’re too uncomfortable outside of MatLab
686.
▲
by
sshine
2y ago
> non-cooperative processes existing on the same device That sounds like a real-world problem you could avoid by design. Is that because of 3rd-party vendoring? > Soemtimes it's to get a collection of higher level features, li
687.
▲
by
sshine
2y ago
Some years into Rust firmware with no classic RTOS experience: I get the feeling that embedded async Rust is a little like an RTOS library toolkit. Why do you need an OS abstraction when you can handcraft an embedded async runtime? Componen
688.
▲
by
sshine
2y ago
>> ”well acksually wayland is just the name of the protocol" […] is a symptom of the underlying problem > well acksually It’s not the protocol’s fault, but the system and organisation that brought it.
689.
▲
by
sshine
2y ago
Yeah, but they’re not made with NextJS.
690.
▲
by
sshine
2y ago
> I would recommend Berlin over San Fransciso In most capacities except for salary.
More ›