skysight-inc/HackerNews huggingface dataset:
Anecdotally, I got some scam crypto ad called "Bitcoin Era" in my GMail app just last weekend. The whole thing is laughably scammy. I Googled the name out of curiosity, and surprise! Almost every single result in the first three pages is a fake review encouraging people to "invest" in this BS. Only 1 or 2 results are actual reviewers who fight such scams and point out how stupid the whole scheme is, with comments from actual people who unfortunately got scammed. The whole experience seems to corroborate the points made in the article quite well.
>Every single time you go to sleep is a roll of the dice.

Isn't that the case even if you have someone sleeping beside you? I suppose it mitigate some risk on the off chance that your partner wakes up and notices you're sweating or whatever, but what if they're sound asleep? Does someone who's high/low on blood sugar exhibit symptoms that are easily picked up by a sleeping person?
Nowhere in the US has a marginal tax rate of 40% let alone actual rate at 100K.

I'm also very suspicious that it would cost 40K per year to rent a reasonable place for 1 or 2 people anywhere in the US except maybe SF
> I measure blood sugar A LOT, though.

That is the most important part, you can really live a good life if you have that. I hope we get more powerfull and cheap way to do that continously. At the momemnt it's at least 300 USD a month for a CGM device that can measure every five minutes. It's abit like monitoring traffic load and adding more servers as you go, except too many servers kill you.

That with knowing how you react to changes in life works wonders, e.g. exercise, eating fat foods, sitting all day.
My first connection when I see a photo of hitler is the holocaust, not budget committee deadlocks or whatever. It may be a stretch but I think my immediate association is going to be pretty close to average for most audiences.

The fact that you had to go so far out of your way to explain why it shouldn't be interpreted that way communicates a bit by itself too.
The running series of Death in Paradise (it is rather mundane but a welcome caribbean distraction for us northerners in those dark winter months) featured such a murder in episode four and I shall not spoil it, only say that I didn't expect that ending.
IMHO the biggest problem is the recruiters do not understand tech enough. If they did then they would not be recruiters, they would be techies.

How to fix? One of the big problems, and others have mentioned it. Employers with unrealistic expectations. I had a boss once create a laundry list of skills for a position, 3 years of each, that no one would have: Java, C, C++, C#, Ada, Java Script, and 2 different assembly languages, as well as a host of other techs. I complained it was a stupid list, as half of the languages listed we never used. Response: "Oh but wouldn't it be nice to have someone who could!" WTF, all they were doing was encouraging liars to apply.

So I believe they should be allowed to list 3 maybe 4 primary skills / experience. Then 3 or 4 'Would set you apart skills' (i.e. tie breakers). If you list more then you do not understand what your team does.

If you are thinking of making something, I would start by looking at Joel Spolsky https://www.joelonsoftware.com/ he has written a ton on the topic (click recruiter to see his articles). He also had a site for recruiting where he vetted the recruiters for a bunch of topics. I cannot find the site or I would put it here.
Nice troll in th
Yep, I wrote most of the support in for Chatty myself as well. Chatty works pretty well with MMS, and I have been using a Pinephone/Librem 5 full time for almost 2 months now.
VR and AR solves every problem advertisers have with browsers. Browsers are: sandboxed away from the OS, are easy for users to manipulate with addons, lacking in new data streams to monetize.

Meanwhile in VR land: Root/super user/driver level access to the system (worst of drm and anticheat software), tons of new data streams (full camera, and microphone access to the room. Some day to have eye tracking, mouth tracking , and anything you fit on health tracking watches), and of course the user can only use the device through the advertisers own software (no skipping of engagement features, no more noscript, and a nice little walled garden App Store).
I did search couple months ago(or even sooner) and obviously nothing was found.To be fair i don't expect pipewire to implement even in the upcoming year such a feature, because it's not something easily done: that's why i switched back.However i was kind of disappointed by the fact that the compatibility module between pulseaudio & pipewire wasn't working in this case, because at least theoretically pulseaudio & paprefs does all the work of piping through the network(Because in my case i would have used the pipewire device, with the PA module, --Fedora-- just to transfer some audio to the actual device with PA --Ubuntu-- that has the BT connected), it's just that the module did not work.

My setup is fine now (I had some stability issues with the latest kernels w/ Fedora anyways) but i hope there's more adoption for Pipewire (preferably Ubuntu due to the massive user base) to be a serious contender in terms of features (because it is already pretty stable).
Nice troll in the URL.
They're likely already compromised and definitely will be after this story... they should hire a security lead and harden their systems right away.
Measuring the developer experience in a systematic way
Yeah, getting caught out somewhere without snacks and a looming hypo is one of my nightmares. I try to always, always, always have snacks on me (for a diabetic, this is even more important to have when you leave the house than your keys or wallet), but sometimes things happen, and you end up somewhere without anything. It's really scary, but the good news is that if there is anybody around, enough people understand at least enough about diabetes to give you something to eat if you start saying "I'm having a diabetic emergency, does anyone have anything with sugar?"

The scary part is potentially getting caught out somewhere entirely alone and without an emergency snack.
Easier to just put an email in your about, if you want to be contacted?
> In an Emacs file, Gackle collects a list of contradictory statements that people have used to describe Hacker News.

dang, could you please describe your Emacs setup?
Right, I think the title should be something closer to "Don't point out something wrong to make yourself feel valuable/smart/etc". Obviously in lots of contexts you do need point it out immediately (the server is down, your neighbor's house is on fire) but when it's just giving feedback, it's good to be helpful (even then there are times when tough love is required, I don't feel bad about pointing out when a mistake would have terrible consequences if it shipped).
Up until this past year, every single ZWave radio was made by the same company. They are now allegedly certifying third parties but I haven’t yet seen anyone announce that they’ve achieved that certification. It’s possible to build a crappy ZWave device, but the radio and network side should be solid, even on crappy devices.
Jitsi is the best. Open source and free but all the dinosaurs use teams because it belongs to micro$oft. I installed it today because a client is using it and surprise: it works only with Google Chrome and Edge! No Firefox, no Brave.
This is the hardest lesson I had to learn in my consulting work. It is is especially important if you are not familiar with the full context - which is almost never the case.

The main insight for me was that yes, things can be "wrong" due to lack of knowledge or incompetence. Sometimes.

But more often than not there is a good reason. Like:

* we know this is stupid, but we had immense time pressure and this was the only way to get it done for the deadline; we never got the time to fix it

* external system constraints (like legacy applications, legal/certification requirements, ...)

* particular domain constraints that you might not be familiar with, and that only make sense if you know the details

* important senior engineer X designed this and no one had the guts to call it out as flawed

* the company paid a lot of money for product Y, so we just had to use it

* a manager read a blog post on how technique Z is awesome, so he made us do it this way

* political infighting between parts of an organisation (redundant work, refusal to work together, deliberate sabotage)

* ...

But you will usually not hear these reasons right away. And being critical can easily put others in a defensive stance and make it very hard to get that information at all.

So my best tip is: if you spot something "wrong", don't react immediately and don't interrupt. Let the other party finish. Make a note. Gather more information. Ask why it was done this way, who is responsible, if it has been effective or not, and whatever else could be relevant.

You can still be as critical as required later.
It isn't (entirely) genetic. There are some genes that are risk factors, but no one knows what causes T1D. It also doesn't affect you at birth–it's an autoimmune disease that usually manifests between the ages of 3 and 20 but can appear at any time in life (see the other commenter in this thread whose wife developed T1D in her 40s). In keeping with this, the risk factor genes are mostly related to the immune system. Even in populations with the highest risk haplotype, only ~5% develop T1D, and many people without this haplotype also develop T1D.

If it were purely genetic, evolution would have selected against these genes long ago since T1D was a terminal disease with a life expectancy of less than a year until the discovery and development of insulin-based therapies in the 1920s.
My theory is that single-platform clouds actually make more sense than trying to be everything for everyone. While the latter can scale to $billions, the former might actually have higher margins because it delivers more value.

An example might be something like a Kubernetes-only cloud driven entirely by Git-ops. Not TFVC, or CVS, or Docker Swarm, or some hybrid of a proprietary cloud and K8s. Literally just a Git repo that materialises Helm charts onto fully managed K8s clusters. That's it.

If you try to do anything similar in, say, Azure, you'll discover that:

Their DevOps pipelines are managed by a completely separate product group and doesn't natively integrate into the platform.

You now have K8s labels and Azure tags.

You now have K8s logging and Azure logging.

You now have K8s namespaces and Azure resource groups.

You now have K8s IAM and Azure IAM.

You now have K8s storage and Azure disks.

Just that kind of duplication of concepts alone can take this one system's complexity to a level where it's impossible for a pure software development team to use without having a dedicated DevOps person!

Azure App Service or AWS Elastic Beanstalk are similarly overly complex, having to bend over backwards to support scenarios like "private network integration". Yeah, that's what developers want to do, carve up subnets and faff around with routing rules! /s

For example, if you deploy a pre-compiled web app to App Service, it'll... compile it again. For compatibility with a framework you aren't using! You need a poorly documented environment variable flag to work around this. There's like a dozen more like this and clocking up so fast.

Developers just want a platform they can push code to and have it run with high availability and disaster recovery provided as-if turning on a tap.
> Extra extra fun considering Windows doesn't have clipboard history like Linux DEs have for years.

Windows + V allows you to enable it.
Yea, I have a feeling well off communities will be ok as well. I live in one such community in the sf bay where residents already paid for and construction is well under way for a higher sea wall:

https://www.sfchronicle.com/projects/2021/san-francisco-bay-...
Don't know about other managers, but in Keepass you can use key file [0][1] alongside master password.

There is also an option to lock the db behind a Windows account [2]. Not sure if it's a good idea, though.

> One master password decrypts the complete database.

> Alternatively you can use key files. Key files provide better security than master passwords in most cases. You only have to carry the key file with you, for example on a floppy disk, USB stick, or you can burn it onto a CD. Of course, you shouldn't lose this disk then.

> For even more security you can combine the above two methods: the database then requires the key file and the password in order to be unlocked. Even if you lose your key file, the database would remain secure.

[0]: https://keepass.info/features.html#lnkkeys

[1]: https://keepass.info/help/base/keys.html

[2]: https://keepass.info/help/base/keys.html#winuser
There's so much nuance in code review communication. The way I'd interpret this article's advice in the context of reviews would be: don't begin adding comments about minor annoyances and details that you've noticed until after you've read through most/all of the changeset and raised any more important structural concerns first.
> Or maybe there are bigger fish to fry and it’s not worth quibbling over small things.

I've taken this approach with one of our engineers, and now we have a huge pile of "small things" that has created some pretty serious technical debt.

My perception is that they don't try to understand what I'm pointing out, and come up with rational for how they have it. I think I have a lot to learn.
You might look to move your deployments to Kubernetes, once you get past the learning curve. Its by far the easiest way to remain "cloud agnostic" in todays age.
This is the main lawyer that handled PIA's (Private Internet Access) legal challenges: https://www.linkedin.com/in/jarsenault
Being a VPN, they would get contacted about a lot of stuff like this. He is a decent guy from my personal experience and maybe he would be a good contact if you don't already have a lawyer handling this.
As a KDE user i have to download hundreds of MBs of dependencies just to use one GNOME app, i don't think this is a great argument either way.
I agree C kind of stand out from that list (I don't know lisp).
But I think as C is a small language, some people can write pretty simple to read C.
But I guess the term is used to describe C as well because of how "close to metal" it is, and people can do some insane things to optimize their code, in a way that becomes "write-only".
One example might be Linux kernel code?

Another example from what I heard directly:

A few years ago, from one of the project nominated for the Gordon Bell prize,
one of the Scientist showed us their code. For perspective, this was to be run
on Intel KNL so it is extra hard for the compiler to optimize it well.
Since our machine is from Intel (and the contract stated they will provide support),
Intel engineers were involved in optimizing a kernel.
In the end they generated hundreds of lines of C code and committed to the code
base directly. It was partly because it is time-sensitive so they can't wait
until they modify the Intel compiler to optimize that code, so they sort of optimize
it manually.
Now if you read that source code, there's no way you can modify it,
rightly fit into the description of "write-only" language.

Also, there's a less well known term of read-only language. I can't find a wiki page for that.
But I think AppleScript is on the list, because you know, reading an AppleScript
makes it looks quite straight forward it should be written this way,
but if you're asked to reproduce it or write something similar, you can't.
Hence read-only.

Edit: It was described in earlier history of the same wikipedia page but was removed: https://en.wikipedia.org/w/index.php?title=Write-only_langua...
If you don't want an investor to buy your house, just look at the letters sent in with the offers. Pick the best one and sell to them if they match the high bid. Investors won't even bother writing a letter.
The rationale for using cloud is so often that it saves you from complexity. It really undermines the whole proposition when you find out that the complexity it shields you from is only skin deep, and in fact you still need a "PhD in AWS" anyway.

But as a bonus, now you face huge risks and liabilities from single button pushes and none of those skills you learned are transferrable outside of AWS so you'll have to learn them again for gcloud, again for azure, again for Oracle ....
The good news is that for most diabetics, your body will automatically wake you up for a hypo. It's a survival mechanism. But some people suffer from hypoglycemic unawareness, and their body doesn't wake them up.

Most diabetics have CGMs these days, though, and somebody like that should be setting hypo / hyper alarms so that either them or their partner wakes up.

(The problem there becomes false alarms and the subsequent alarm fatigue that results in you turning them all off.)
The way to do this properly as a reporter would be to record using a standalone voice recorder and transcribe using offline software (Dragon Naturally Speaking or something similar) on an air-gapped machine.

If you're a reporter working on human rights pieces which involve nation states, you need to step up your game here or you're putting sources at risk.
silly question I know. I know they're indepenent, and higher than sea-level, but just wondered, more precipitation, snow melt, etc.

Should've googled it before I asked

> The Great Lakes are land-locked bodies of water that drain via the St. Lawrence River into the Atlantic Ocean. Lake Ontario, the lowest of the Great Lakes, sits 246 feet above sea level. It (and the other four Great Lakes at elevations of 571 feet for Lake Erie, 577 feet for Lakes Michigan/Huron and 600 feet for Lake Superior) will not be affected by rising oceans, whose rise will be only about one foot by the year 2100. Oceans have been rising at an average rate of 0.14 inches per year in recent years, but the rise is expected to increase slightly in coming years. The levels of the Great Lakes fluctuate a few feet in cycles that are independent of ocean levels.

https://wgntv.com/weather/weather-blog/will-rising-ocean-lev...
Every single iOS app using Core Data (which runs SQLite under the hood)
What are you doing to facilitate methane removal?
What other option is there? When you've got over a hundred different random passwords, at some point you've got to manage those, so you use a manager.

Though I would never recommend a service-based one, just use something like KeePass and sync that file.
I just see asterisks?
Yes, that's an example of the obvious pandering that I left room for.
I could see this being useful when reporting bugs as well. Seems like the "Oops, something went wrong" screen is pretty standard for handling unexpected errors. Being able to programmatically trigger a user-detailed bug report whenever this happens would be pretty cool.
Refactoring should not break your tests. You wrote them without knowing anything about the implementation, so how can they break when you change only the implementation and not the user interface, results, or side effects? (If you change any of those you've moved beyond mere refactoring and need to start the TDD process over with new tests.)
I wonder how they compare (but I'm not willing to spend hours comparing for myself).

I do note in passing that S2n-QUIC has a really nice set of examples of how to use right up front in the README. All libraries should ideally have that. Without reading anything else, I already have a good idea of how hard it would be to use S2n-QUIC (looks easy).
Yep shipmate is only used against people too new to know you’re actually insulting them (in boot camp and earlier schools it’s more of a cute jest), and when someone is so fucked up that they’re not worth reading the name on their uniform.
Agreed. The future for the masses is "freedom" to be a wage slave to whatever corporation provides a "job". It's weird how dystopian fiction seemed outlandish to me around 10 years ago, but now seems pretty on target.

I'd love to be proven wrong, but as you say, the rent-seeking is too damn high. I live in the US at the moment, but definitely looking to leave to somewhere with an actual social safety net / infrastructure.

Nowhere is perfect, but damn if the USA isn't moving backwards. I imagine the top plan to just hide in their fortresses / go overseas if it goes to hell (as the dystopian fiction tried to foretell).
Yeah, heroku is absolutely the best in just getting something running. Truth is most projects don't ever have to scale, either because they are hobby projects, or cause they just fail. Heroku is the simplest platform that I know to just quickly test something. If you do find a good market fit and then need to scale, then sure, use some time to get out of it. But for proof of concepts, rapid iteration, etc. Heroku is awesome.
I might be minority here, but I prefer Bitwarden because of it's seamless ability to sync passwords with my wife. There's no way she's going to use something complicated or non-intuitive and she mostly uses iOS. We have nothing to hide from each other so all of our passwords are in the same vault. We also use the secure notes functionality to lookup important family info.
At my company, the developers are all on fairly powerful MacBook Pros, and everyone else in the company has Windows laptops (I think generally Surface devices)

For the developers, Teams works... as good as Teams can. So not great, but it works most of the time (for me, anyway). For everyone else though, I hear nothing but issues. Constantly having to restart to make Teams work. And again, this is on Surface devices, so Microsoft is making the app, the OS, and the hardware!

Even aside from the performance, I just think Teams is laid out horribly and it stifles communication. The redundancy between chats, group chats, and Teams channels (which are like a message board?) is just bizarre and constantly causes confusion. It's so much worse than Slack (which we used to use, and I used at a previous job) where all communication channels are listed along the left side, and you didn't have to dig through menus and trees of categorization to get to certain places to talk to your coworkers. And since Teams channels are sectioned off behind another screen from your chats (where you'll probably be most of the time), the only way to be aware of when someone posts in one of the channels is to turn on notifications for it. Which is very annoying!

edit: oh also a recent update made it so when you paste a code snippet into the plaintext editor thing (whatever it's called, you activate it by typing 3 backticks), it strips all the whitespace from the left, meaning you lose all the code indentation. Just great
I am also a T1D.

This post was a great summary of the constant mental juggling that happens when you have T1D. After almost 25 years with it, the cgm has been the biggest technological leap for management, but the mental aspect is critical too. I highly recommend seeking out groups where you can meet other T1D parents, because that will be a huge help! Seeing people who understand what you are going through, and can help talk you through situations, or heck, just be an informed listener can be huge! :)

I participated in JDRF as a kid, went to Diabetes camp (which I highly recommend!), and now participate in a young adults t1d group where we meet once a month for appetizers and drinks (pre covid, now we meet virtually).

When I am not doing those things, I also like to write and do projects around t1d.
Here I write about converting a day's worth of cgm data into sound: https://dddiaz.com/post/glucose-sound/ or here I write about using my health-kit data from my apple watch and combining it with my Dexcom data to try and create a ML algorithm that can predict which days I exercised. https://dddiaz.com/post/glucose-datascience/
Actually had a few legit warnings where a knew I had contact - but also had ones where I was not able to track down a risk contact.