skysight-inc/HackerNews huggingface dataset:
> Burnout that occurs outside of work isn't talked about enough, maybe because it's mainly restricted to a certain kind of individual in specific kinds of fields like programming.

Wish that was true. There is an outside-work burnout that's arguably quite common in society these days, and mostly not talked about either: having kids. People who are not parents themselves, and not close with some parents of small children, they won't understand. Parents just exchange knowing glances. At least those who aren't conditioned by their society/environment to pretend everything is great and child-rearing is the Greatest Privilege and the Most Rewarding Experience in the Universe.

Going through that right now, I pretty much gave up on coding after work. I tried, telling myself that side projects are keeping me sane. True or not, the tension created by not actually being able to do them, was worse. All the things you write in the second paragraph are true - and they only get worse once you're running on negative me-time budget :).

(EDIT: At least the topic of postpartum depression has been gaining some attention these days. A case of one can easily have negative effect on multiple people across a generation, and there's still very little advance warning or support given for new mothers.)
So anyone who has already unlocked their Pixel 2 is good to go right? Getting the latest Pixel unlocked requires an internet connection, but once done it's done.

So the complaint is that in the far future the vendor might not support that on a six year old phone (by that time)? But, it is supported now, so what's the beef?

My old Pixel 2 only works now plugged into power and on WIFI because the battery is dead. I can get super-pissed off at Google for not supporting battery replacement on the Pixel 2, but it's a 6 year old phone. How long should I expect them to support it knowing at the time about the sealed battery. I can't get that pissed seeing as I bought it knowing the facts at the time :)
Yellen: Not raising debt ceiling may trigger constitutional crisis
Why did you recommend she start a daycare business?

> Why IT? I can't help but wonder what she is trying to accomplish

Uhh, make decent money at a decent job. Not everybody feels the Call of Being a Programmer. It’s just work and you can be OK at it and make good money without it being your entire personality.
It doesn't show the year; but assuming this was about 1980, home computers were only just starting to appear - many kids wouldn't have seen them; and you've just told taught them computers do what you tell them to do, and not by themselves and also told them what the flashing thing is.
For Sesame street that's more than enough for a little sketch.
(And that the computer guy fixes everything....)
I looked through the sci-fi and fantasy sections and there were some odd choices. For example, Jeff Vandermeer's Annihilation was recommended as a "climate change novel" book. It's hard for me to see how this makes any sense.

Other weird suggestions:

* Ender's Game under Best Apocalyptic Fiction
* Parable of the Talents under Best Sci Fi Books on Space Settlement - this is real stretch since the book takes place entirely on Earth, though it does feature a religion that focuses on spreading humanity to other planets.
I graduated in the early 2010s and mostly studying philosophy and gender studies. In my experience of that time period, these too were difficult courses requiring research and informed writing. Certainly, doing well at school required knowing the material and having something to say.
And yet somehow you are sure such things exist?
Yeah, the state of affairs with Google is better than any other mainstream vendor.

It seems lame that you have to phone home to unlock a new device, but it's nothing compared to what they could be doing.
Amazon bears the responsibility here. They chose which insurance company they use to fulfil that responsibility.

While you're correct that the same would also be true between two laypeople, Amazon is a far more powerful and sophisticated actor than a layperson can be expected to be.
>basically nobody transfers data on their phone using a cable.

Maybe because it takes an eternity to do so?
One issue for this process that I have seen when talking about the Pixel is:

- ***You can't actually back up your Pixel***

It's enormously frustrating, because this is the typical advice before moving to a different OS. But apparently, actually mounting the device or seeing it via `lsblk` is from what I can tell impossible.
I tried for a while to simply make a direct image with `dd` to try out other OSes etc but I couldn't even figure out a way to mount it, or in the cases it could be mounted it was using some insanely stupid fuse fs that was specifically made to be difficult to use.
They want you to use some ridiculously complex and idiotic idea that revolves around using the cloud for backups, which I couldn't figure out precisely what was done because it isn't open source, so I refuse to use it. It's insane that you can't just `dd if=/dev/sdX of=phone.img` or something simple.
On the Pi? I had an OS. I think it was the standard raspberry pi OS. I wanted to do Arch Linux Arm for the supposedly lighter xfce, but I couldn't find it. I'm way to dumb to do it bare metal all by myself.
Good point. I just don't want them to look like my AirPods or people near me might think that I am ignoring them. I would rather they look like hearing aids.
How? That's unusual unless you play games or do heavy computations - but then a regular laptop would last you 1-2h max.
Presumably the WGPs are working on rays which start close to each other in space, which causes the potential occupancy problems mentioned. I wonder if you could shuffle the rays around a bit to help occupancy at the possible expense of cache hit rate.
I loved having my car totaled. I was able to sit on it for a few weeks because I was borrowing another family member's unused vehicle. There was some dickering involved because they wanted to pay low-end blue book, but I found a comparable vehicle on craigslist and got another $1000 out of them. About 2-3 days after I agreed on the value, I got a check in the mail.

If my house was totaled it would not be so fun.
I went to one with school as a kid, and this projector in the middle was the most science fiction looking thing I'd ever seen in real life

It probably was one like this: https://upload.wikimedia.org/wikipedia/commons/b/bb/ZeissPla...
I disagree very much. I don't think any blanket statement like that makes sense.

I recently started building a service and need to keep costs down. Serverless is perfect for it. My service has low to moderate traffic, costs pennies to run on AWS Lambda and MongoDB Atlas. If I had gone the boring route of JVM + PG + k8s, putting aside the time it would take to defamiliarize myself with anything on the JVM, the cost to run this service would have been in the hundreds of dollars a month vs the pennies. Interestingly the most expensive part of my current setup is the NAT Router on my VPC. With JVM + PG + k8s it would have been PG or K8S depending on where I ran PG.

I do agree that there is a misconception with containers taking longer than server less. I don't think either takes longer considering the current tooling available.

Seems like you got burned on Serverless at some point, I'm sorry that happened, but for many people and teams it is a productivity multiplier and can be a big cost cutting solution.
I'm glad to know this was actively studied.
Not strictly impossible, but probably difficult to the point where the FLIR sensor becomes a cheaper solution.

The visible detectors are kind of a lucky accident, that the visible spectrum is within the range that can be detected by a silicon sensor. Therefore, visible sensors are cheap and easy to make thanks to silicon IC technology. Sensors that detect IR beyond about 1 micron wavelength (the bandgap of silicon, where it becomes transparent) have to be made out of more "exotic" materials that are also more expensive. The problem might be surmountable, but fewer people want to set up and optimize "fabs" for those materials.

The problem with detecting heat with silicon is that the intensity is extremely low, and the amount of background radiation high. Getting a temperature measurement that isn't corrupted by other effects is going to be difficult.
Stereotypical response to penalize the entire user base in order to combat spam. As if detecting spam bots by username will fix spam.
That's impossible. There are multiple accounts and tests that show you should be getting >10h with just video meetings.
The less edgy, pithy, probably correct explanation is that the over-worked developer wasn't aware of the standard.
> Then why does the passkey scheme even bother with public key cryptography? Why not just generate random passwords for each site and store those? This seems to be logically equivalent to a password manager.

The big reason is phishing. If I can convince you that my site is the login page for something else, I can login as you – and if I’m clever, get you logged in as well or present some temporary error page before redirecting you to the real login page so you don’t even realize I’ve done that. Weaker forms of MFA like TOTP, SMS, app push notifications, etc. are vulnerable to that since you’re expecting a prompt. Because WebAuthn uses the hostname in the setup process, there’s no way to phish someone and keeping the private key locked down also prevents someone from even trying from another device.
Sad to not see DLSS thrown into the upscaling test section, as I’ve seen the best quality to performance ratio running that over FSR or others.
I had an alert about 9 months ago that someone might have accessed my hotmail, I went to check the previous logins and did see some from places in SE Asia but from months ago.

Mixed in were many logins from an IP address owned by the Microsoft campus at times when I would have been asleep. The account is a backup, and I don't have that mailbox attached to any apps. I emailed their security team asking what was going on but never got a response. After changing the password all the access was stopped. Though I should go back and re-check.
Security in banking apps in the U.S. is an absolute joke. I'm glad to hear Canada takes it more seriously.

I've used everything from giant multinational banks to local credit unions in the U.S., and none of them will even let me sign in with U2F. Many of them still have password character limits.
This is why I don't keep the primary source of anything that I can't afford to lose anywhere but my own house.
how delightful!
Thanks for pointing that out. I hadn't thought of it that way.
It's possible that the definition has changed; (human) language is malleable. But the original definition of "green thread", which goes back at least to the 1990s, was in contrast to "native thread" where the latter was implemented by the operating system and the former by the language implementation. The whole point of "green threads" was that they let you do something that looked like parallel processing (but was really just time-slicing under the hood) with no support from the O/S.

If there's a new accepted definition someone should update the Wikipedia page.
That's fine, you can build a reasonable general purpose JSON API very quickly, particularly if you aren't having it dragged around by your web applications nitty-gritty needs.

In the linked essay I am riffing on someone already recommending splitting your JSON APIs into a general purpose API for clients, and a specialized one for your web application, in order to separate these two concerns and remove the pressure that that latter puts on the former.

I recommend going further with that and adopting hypermedia for your application API, since no one else should be depending on it. I recommend this because I like the hypermedia paradigm, but it only makes sense as part of a complete hypermedia system. Trying to reuse a hypermedia API for other clients isn't a good idea and that's not what I'm recommending.

Does that make sense?
Doesn't M1 and M2 have on-chip memory? Even if it may be the same interface, doesn't the physical distance help make it significantly more performant?
Yes, absolutely, but nobody said the SBC was supposed to be portable.
Has it occurred to you that the feature you're defending allows Google to lock customers into their provisioning/MDM? That this is worse than Verizon controlling provisioning/MDM, because at least Verizon is subject to market competition (ie you can buy the device from other parties), whereas Google doing it means you have no choice whatsoever?

You're also grossly exaggerating things. We're not talking about a change that would prohibit management, just one that would not allow them to do zero-touch enrollment into their management systems.
There are many but most never gained traction. Compiling C to JVM bytecode obviously is possible but the resulting code would not run efficiently due to the semantic mismatch. For example, implementing call-by-value semantics that C has using bytecode would not be efficient. Neither would pointer arithmetic.
JSON and Lisp-Like Queries (2020)
Don't bank apps complain if the phone is rooted or runs anything than a stock OS?
Two months is an awfully long time to go with no working car and no money to buy a new one. This could be a substantial hardship.
Almost as if it’s a coordinated propaganda push. Hmm …
Not convinced. If it's so easy why hasn't anyone done it yet and made it easy to consume for everyone else?

To me this is a red flag. "Just roll it yourself" is not a constructive response in the eyes of a commercial programmer. We come to an ecosystem expecting certain basic building blocks. I am not paid to evolve LISP's ecosystem. Not to mention nobody will give me the time in a world where deadlines and milestones are a fact of life.

If I was doing programming purely as a hobby -- sure! But I don't. And I'd bet most commercial programmers don't as well.
Wait, and this blood gets donated?
I use https://conjure.so as a habit, time and goal tracker. I built it for my own needs and to explore some ideas (habit rules engine, completion types, measurements).

I’ve been using https://akiflow.com/ for tasks for several months now (I switched from Omnifocus) and I love it.

I also use https://one-sec.app/ on my phone to add friction to opening apps I want to limit time on and try reduce distractions.
> How do you suggest a mugger to find out whether such an app is even installed, let alone do anything about it, in this day and age of full-device encryption being the default?

They make you do it, the same way they made you give them the device in the first place.

I don't know why anyone thinks it would turn into a kidnapping, but it's pretty easy for someone who has already forced you to give them your phone to use the same technique to force you to unlock it.
Who signs new nodes in the tree? The server or the content creator? What prevents a server from creating content for anyone?

So you can confirm it was not changed, but cannot confirm that the original addition came from the real person?

I don't see anything in the docs that talk about cryptographic signatures or key management.
The man eats his own toenails. C'mon bro.
After 2 months of waiting, it is a reasonable conclusion that they were hoping that if they just waited long enough, they would never have to pay.

This certainly isn't the behavior that I'd expect out of a customer obsessed company like Amazon aims to be. Certainly someone failed miserably at the first leadership principle, Customer Obsession.

https://www.amazon.jobs/content/en/our-workplace/leadership-...
Here's a question the article doesn't answer: why Common Lisp? I.e. why not Scheme? Scheme is a plenty powerful language these days with all the libraries it has available. Granted, it doesn't have history going back to the 1950s, but it does date back to the 1970s. There are also multiple implementations, each with its own set of strengths. And there are some solid standards written for the language that have good implementations.

It seems to have all the exact same features they're saying make CL a good choice (e.g. it's hard for me to imagine that a language older than most working programmers doesn't have "longevity" or "staying power.") Besides, if you click through to https://stevelosh.com/blog/2018/08/a-road-to-common-lisp/#s8... (linked in the article), it shows a picture of the index of CLtL, where the entry for 'kludges' spans the entire book lol!
It would indeed be insanity to argue that, which is why I didn’t. The argument for splitting into micro services is generally that particular teams would own particular services and therefore make debugging/change easier for them, at the cost of increased overall complexity of the overall system. Anyone arguing it reduces complexity is being very hopeful.

I personally think an org should generally cling to a so called monolith as long as they possibly can. But it’s very hard to be prescriptive without knowing particulars of the problems an org is trying to solve.
I need different cables to charge my ipad/mac and iPhone.

I can charge basically all (dozens) of my gadgets using usb-c cable, but I still need to carry additional outdated lightning with me to charge the damn phone.
Just um, try not to spend too much time reading it or you'll have to run run run to that toilet.
This is what I use with Logseq. A new nie created every day and the added before of tags to gather the various points together.

I built dly (https://github.com/wsw70/dly) to make one line notes taking faster.
It's quite common for people from elsewhere in the world to buy electronics in the US, Europe, Japan, etc and then bring them back to their home countries for a fraction of the cost of what the official or unofficial importer(s) want. That's why you end up with all sorts of region-locking nonsense, companies trying to protect their importers who have a monopoly on distribution of a particular device.
The whole messaging on passkeys are extraordinarily confusing. When I start reading, it sounds like a great thing: instead of passwords, I authorize devices to my account by associating a public key with the account. But it's unclear if supporting passkeys actually requires services to support more than one public key associated with an account. The fact that you can sync passkeys to the cloud (rather than just using a key stored in a TPM) suggests that it's not actually a requirement, and it isn't even the default behavior. It seems like passkeys are intended as a fancier version of "log in with" rather than an actual private key/hardware-based replacement for passwords. A properly secure system would have a mode that made sync impossible, you would have to generate a unique and hardware-secure passkey for each device.

It sounds like maybe I can achieve that, but not with any of the standard implementations.
Ask HN: Why did Python break imports in 3.10?
A change was made which requires changing an import path in some cases: From "collections" to "collections.abc"

From the outside in, it's amazing to me that such a decision would actually pass muster and ship:

- The amount of human productivity wasted by people trying to find why major packages broke. There are still thousands of unfixed references on Github a year and a half later

- The effect it will have on adoption of future versions as people are stuck on packages that aren't updated: the most common fix mentioned is to simply downgrade your Python version

- Python doesn't acknowledge that there's such a known cause for this specific import error

- The fact fixes requires changing code, afaik there's no sort of backwards compat flag or something.

It just seems like incredibly short-sighted engineering. There was a deprecation warning, but isn't this an ideological change at most? Was there some greater benefit I'm missing?

I'd love for people more involved in the ecosystem to share their thoughts on this.
GPT 4 is Smarter than You Think [video]
Right, that's because they went way out of their way to drag a bunch of startup people in as advisors, and they worked all their stuff into the plot (it helps that there's something innately comedic about startup culture). Watch the credits sometime and look for names you recognize; you'll see them.
Dept of Computing at Imperial was reportedly:

doc@doc.ic.ac.uk

“Dock at dock dot ick dat ack dot uck”
can we extend this to hostile UIs? Please?
Those first users will be hard, they’ll have to trust you and commit.

Anecdotally, in my own experiences with something somewhat similar what surprised us was that the less polished what we showed during UX research, the more willing users were to tell us what they really thought and gave more suggestions. We actually started showing even rougher mock-ups and prototypes than we had to. Completed versions were treated as “finished”. That’s just something to think about.

I would try to find a niché - a productivity app for X. Then those first users feel more inclined to stick around.

Good luck!
Why would shuffling the rays around help with occupancy? I 'd also guess that worse locality could easily obliterate any other benefits, but you never know unless you test...
I im honest I don't see the big deal with this practice.

a) You can unlock the device

b) You can connect via WiFi, why is the device 'phoning home' such a big deal when its brand new and has no data on it?
Nope, the shorter distance makes no measurable performance difference. It does make the motherboard smaller though.
Because insurers decide if who is at fault and to pay or not. This system is creating bad incentives since the entity at fault and the entity deciding who is at fault are the same on one side.

The problem with American society, as your comment reflects, is that culturally every discussion always goes back to money.

But money, while quite a good proxy for many things, reduces the human experience to a simplistic model.

It's like game theory: beautiful in a lab, but a parody of life interactions IRL.

You have to shape the system so that the emerging behaviors take in consideration justice, happiness, sustainability, etc.
I don't think that's much of an endorsement of in-office collaboration if you need the power to go out to actually focus and get work done.
I use serverless successfully - handing tens of millions of annual revenue.

We do this in a handful of small services, none of which gets much traffic. The alternatives (e.g. app-engine, container in vm, or k8s) all require more infrastructure, would cost more (no scaling to zero), and are overall less suited for the kinds of problems we expect to see.
In most of the world by landmass and population it doesn’t
> I make money from porting people off of poor technical choices

I make money by delivering features my customers care about.

We tried k8s, it was a ton of mental effort and time wasted when we could have been building more features. That particular bit of infrastructure is currently running in elastic beanstalk, where it's cheap and I don't have to think about it.
> Making even the most simple changes or basic features would often break something else in unexpected ways.

As I get older I find myself valuing locality of behavior over most other concerns.

I can deal with some pretty spaghetti-ish code that's bad along many traditional metrics as long as I know what my changes are going to impact.
Look, you're probably right but there's no need to be so annoying about it.
For all we know it's just Google activating the device to ensure it wasn't stolen and reflashed with another OS. Apple requires a device to be activated before it's usable.
I get what you are saying. But, you seem to be making a moral argument here, whereas I'm making a legal statement. I certainly agree that Amazon should have just paid the woman at some point and dealt with the situation with their insurance company themselves. Of course, that's assuming she attempted to contact Amazon at some point (which seems likely but isn't stated in the article).