skysight-inc/HackerNews huggingface dataset:
From the article:

> "Supplementation of riboflavin and/or biotin is likely to be beneficial in a subset of Parkinson's disease patients, in which gut dysbiosis plays pivotal roles,"

From https://en.wikipedia.org/wiki/Riboflavin

> Best sources of riboflavin: Beef liver, Chicken liver, Whey protein powder, Almonds

> People at risk of having low riboflavin levels include alcoholics, vegetarian athletes, and practitioners of veganism.

From https://en.wikipedia.org/wiki/Biotin

> Best sources of biotin: Chicken liver, Beef liver, Eggs, Peanuts, Sunflower seeds, Pork chop

Offered without comment.
Yes https://www.appvia.io/blog/chick-fil-a-kubernetes-success-st...
Given your username one might hope "implement a world class public transport system" or better yet "convert an urban highway into a beautiful linear park and waterway" (like Seoul) would come to mind.
Not to be snarky, but which popular programming languages have come out of Silicon Valley? I can think of Swift and perhaps Java (Sun)?
Benchmark: https://gist.github.com/orisano/b4d30946a6a760f1458e86e2844e...
Update: now working
Together with nine stakeholders organisations, the FSFE has submitted a joint position paper to the EC. This paper, supported by legal and data-backed arguments, addresses Apple’s non-compliance with the law, particularly concerning software freedom, alternative Free Software app stores and interoperability obligations.
Also only works with non encrypted conns (ftp, http), that one should not be using.
And like you say on open or PSK networks you can do worst stuff (if isolation is not enable arp spoofing the default G will be way worst then this)
Matrix is intended for chat of any kind. The 'messenger' featureset (i.e. WhatsApp/iMessage) is basically a subset of the 'Team Collaboration' (i.e. Slack/Discord/Teams) featureset. Historically Element has tried to handle both use cases, but it spread us too thin and we didn't pull it off.

So with Element X, we've very deliberately focused on the Messenger use case at first (also driven by the fact that we have more paying customers asking "i want to run my own decentralised WhatsApp/Signal alternative" than "i want to run my own encrypted Teams alternative") - and it is unrecognisably more polished and focused and usable than normal Element. To quote someone in one of the community Element X rooms a few days ago:

> just downloaded element x from f-droid and wowza it just.. loads instantly? can't believe i now live in the age of element being faster than discord

Once the 'messenger' use case is fully launched (aiming for "end of summer"), we'll then carefully add the team-collaboration features (spaces, threads, etc) back in - and hopefully end up with something which can be used for both.
This seems odd, as someone who has no medical knowledge. If it's just adding B vitamins, then a lot of people take vitamins. Especially when diagnosed with something as terrible as Parkinson's. I would expect to hear some anecdotal evidence on that for a diseases that is so common.

Edit: Very informative replies. Thanks!
It took a bit of mental training to stop switching to browser/chat apps while reading, but I have most notifications disabled so it was more a "me deciding that now I'm going to just read" than a device/software thing.

I do still switch or get distracted occasionally but generally now when I've decided I'm going to just read my book, that's what I'll do.
Dupe: https://news.ycombinator.com/item?id=40816994
This link might help... https://dl.acm.org/doi/10.1145/2854146

The linked pdf has lots of details.
Here's the paper if you'd like to skip the horribly ad-laden science alert site.

https://www.nature.com/articles/s41531-024-00724-z
Wouldn't people like your example end up with more billable hours due to reduced congestion, likely coming out ahead?
That's more or less the reliability of modern laptops for you.

I had to replace the fans in my ASUS after less than two years, but the official manufacturer's parts store was out of stock so I had to rely on Ali Express. After that I had to go through the process of replacing them, which was anything but simple.

You can't buy quality any more, but at least you can have repairability.
> Once you're really familiar with the codebase, you know where dragons be, and you can make changes more easily.

This is an interesting, and often overlooked, point. A month or two ago someone asked us, the Fossil SCM maintainers, if we'd be open to them refactoring the tree to something which better matches modern sensibilities (i'm paraphrasing here). Despite its many proverbial dragons, the long-time maintainers are comfortable with it and know where those dragons are and how to defeat them (or, in some cases, sneak around them), so, despite our collective geek tendencies to prefer "perfect code," we're happier with the dragons we know than those we don't. (That's not to say that fossil's code is awful, but its structure varies significantly from what one might write today if one was to start such a project from the ground up.)
It's not just what's printed on them, really. I touch type, but a US keyboard have different shapes. For instance a longer left shift, and then go straight to Z, while we have an extra button inbetween. After jkl we have three buttons and then a thin and tall enter, but you have two and a short enter.
> If even a single one of the over 12,000 connections was a little flaky, it could slow down the entire training run

It's an unusual enough sentence to be remarkable and I was like "I read this exact same sentence before". Indeed, this and most of the writeup appeared on Twitter, LinkedIn, Reddit it seems word-by-word. Is this just spam ?

https://x.com/imbue_ai/status/1805629547473518695

https://reddit.com/r/learnmachinelearning/comments/1dobgbs/t...

https://www.linkedin.com/posts/mattboulos_training-a-70b-mod...
Last year I worked for a client that gave me a lot of time, money and autonomy to lead dev on a critical software rewrite.

We got a small team of competent people, with domain experts to peer code with the devs.

It was wonderful. We could test, document and clean up. Having people who knew the trade and users at hand removed second guessing.

The result was so good we found bugs even in competitors' implementations.

We also got x5 in perfs compared to the system it was replacing and more features.
Did you look at the example changelogs git-cliff creates?

> I try to put the important things first in the changelog and keep it brief. The changelog is a heads-up for users that things have changed or been fixed and users don't want to spend hours reading it.

Provided the commits use conventional commit format such as "feat(thing): fixed crash when copying file to xyz backend" or "fix(database): generate migrations correctly" not only do you get the type of commit but also the category or area.

git-cliff and others then use that to automatically add sections for each category of commit. This wouls surely needing to spend hours on writing changelogs, which seems an insane amount of time to me.

> I also spend maybe an hour each release editing the auto generated changelog, removing the noise (refactored X, fixed docs for Y, made tests for Z work), condensing multiple entries, reorganizing, moving things to the correct section, linking stuff etc.
Im curious about the people who use R in big tech companies that you've worked at. Were the R users the people who had just come out of school and still working using their academic dev environment before weening off?

I always found that was the group who used R - kind of a use what you are used to until it gets out of step with the remaining workflow.

I also would say that the amount of R I see is far less than python.
Yeah for sure. Even with my phone's brightness on max, in bright sunlight ereaders are much better. That's probably always going to be the case I guess.
I also echo the code ownership part.

I have a part-time gig where I maintain accounting software for a former client of mine. It takes up a few months' weekends a year.

I wrote about 60-70% of it when I was working for the owner of the software. It's something where as long as the client's happy, and they get new integrations and updates on time, they could keep using it for a decade longer.

I had almost complete ownership of the architecting of the software. It's broken down into a few microservices (think database, core business logic, reporting, auth, logging etc).
The best thing I did at the time was pushing to use gRPC even though management felt it was too new tech.

The UI is in Angular, pain-free periodic upgrades. I've even rewritten some perf-sensitive code in Rust, and everyone's happy with snappier calculations.

The code hygiene is relatively good.

The only downside's that if someone else were to take over the code, they'd struggle (it's one of those things where I'm wearing many hats). I've been fortunate to be a professional accountant who moved into software engineering, so everything makes sense to me.
> I've heard that one way to use it effectively is writing a detailed comment about what you want to do, then let it suggest the code. I personally don't like those style of comments

I do the same as you: write such comments, let Copilot draft the code, then I delete the comment.

Since the comment is detailed, I think of such use of Copilot as a “pseudocode to code compiler”.
That's true, but also not really an explanation. There is a Polish keyboard layout that's derived from a typewriter, but got abandoned very early on in PCs, even though Polish has 9 additional characters.
My past three employers code bases: mono-repos, Bazel, lots ot C++ and Python, thousands of libraries and tools, code generation and modeling tools that are fully integrated into the build, easy cross compilation, large integration tests just one bazel test invocation away, hermetic and uniform dependencies...
As far as I know, those aren't wasting the space for a battery. Framework opted for their current battery sizes. Larger capacities are available for the same size of battery they do have.

For example, my other favorite laptop, the Redmi Pro Books basically have the same physical size batteries but at 80wh/99wh ratings.

I just think Framework can't find a contract manufacturer for higher density batteries at their volume.
Baking bread is more correct, but in my experience "to cook" is generic enough to include baking. If someone has something in the oven and I ask "what are you cooking?", it's not weird.

On the other hand, "cooking bread" is like 2/10 weird.
The Netherlands and China has built transit at the same time as (or before) new areas are developed.
Honestly, if you need to compare it to a Mac, you're in the wrong crowd and in the wrong market. This very emphatically isn't a device for you.
Laravel, once you get the hang of it everything just works, and using a debug bar to optimize database calls is very satisfying.
Even if they let you go through with the ceremony, it doesn't actually stop them coming after you.
subjective replies to 9 year follow up study

I couldnt work out how they came to the 56% figure.

researchers found people considered lonely at the start of the study had a 25% higher risk of stroke than those not considered lonely.

Researchers found that adults aged 50 and above who experienced chronic loneliness had a 56% higher risk of stroke than those who consistently reported not being lonely.

How many actually had a stroke?

How many died of stroke because they lived alone and had nobody around to contact emmergency services?
If this is true, then why has almost the entire US worked to make it illegal to build high density housing? Presumably they wouldn't have bothered if nobody was trying to build it?
I'm not involved with this, but I did create the winget-pkgs issue to get git-cliff available for use on Windows.

Because of this Windows users can simply run "winget install git-cliff".

Small things like this help with adoption.
When I was in high school (many decades ago now) we had a vacuum tube tester with a switch that allowed you to select the heater voltage. We quickly discovered, devils that we were, that if you stuck a simple diode with a 1.5 V heater in the tester and cranked the voltage to max it would launch like a little rocket. Eye protection recommended.
If a team of devs is incapable of writing good commits with simple prefixes then that's a strong case for adding git hooks that reject commits without the prefix.

Before someone starts getting their pants in a twist at this idea, you can configure a solution such that commits to branches don't need a conventional commit format, but that the commit that merges a PR into master must have conventional commit format.
One of them stands out, due to being super-productive, over years, and then decades.

A large system that was originally written by only two super-productive engineers (I mean real engineers, both with PhDs in an area of Engineering). And a comparably capable and essential IT person.

The reasons for the super-productivity include one of the developers choosing great technology and using it really well, to build a foundation with "force multiplier" effects, and the other developer able to build out bulk with that, while understanding the application domain.

Another reason was understanding and being pretty fully in control of the code base, so that, as needs grew and changed, over years, someone could figure out how to do whatever was needed.

One of the costs was that most things had to be built from scratch. Over time that also proved to be an advantage, because whenever they needed (put loosely) a "framework" to something it couldn't do, they effectively owned the framework, and could make dramatic changes.

When I said "costs", I mean things like, many times they needed to make a component from scratch that would be an off-the-shelf component in some other ecosystem. So if someone looked closely at how time was sometimes spent, without really understanding it or knowing how that panned out, it would look like a cost that they could optimize away. But if they looked at the bigger picture, they'd see a few people consistently, again and again, accomplishing what you'd think would take a lot more people to do.

It helped that the first programmer also became the director for that area of business, and made sure that smart engineering kept happening.

Someone might look for a reason this couldn't work, and think of bus factor. What I think helped there was the fact that the work involved one of those niche languages that attract way more super programmers than there are jobs. "Gosh, if only we had access to a secret hiring pool of super programmers who were capable of figuring out how to take up where the other person left off, and we had a way to get them to talk with us...")

It was easy to imagine a competitor with 100 developers, not able to keep up, and at many points getting stuck with a problem that none of them were able to solve.
> Any codebase that I had complete control over.

This is probably one of the pillars of good codebases, or at least decoupling the bits that you don't control as well as you can (this includes external services). I remember needing to write a wrapper around another JWT library, but because it was quite important, I aimed for >95% test coverage, some of the tests acted as documentation for how to use the code, there was also a nice README, there was CI configuration for pushing the build artifacts to Maven and suddenly even managing dependency updates became easy because of the test suite. Years later, it's been integrated in a bunch of services and "just works".

Come to think of it, things always get less pleasant once you add a bunch of complex dependencies and libraries/frameworks. Need to make a few RESTful Web APIs in Java? Something like Dropwizard will probably give you fewer headaches than Spring (or Spring Boot) and all of its inherent complexity, in the case of the former you might even need to do configuration in XML and that has honestly never been pleasant. If you need to integrate with a bunch of other stuff and want something opinionated, going for Spring Boot will make sense then, but for simple use cases it's overkill. Same for ASP.NET, Ruby on Rails, Laravel and many others, while they might be easier to use, updates (especially across major versions) and breaking changes will give you a headache and just add a bunch of churn to the project.

Similarly, if you need a message queue, externalizing that into RabbitMQ might make a lot of sense, same with storing files in an S3 compatible store, using something like Redis or Valkey for key-value storage, as well as not trying to shove too much logic into your RDBMS. Just pick whatever tool feels best for the given task at hand, instead of shaping things into what they're not (using the database for blob storage, for example), unless you have a whole bunch of constraints to contend with. Otherwise, sometimes you just get the worst of both worlds, like needing to use Oracle for a project, not having easily launchable local environments (because Oracle XE doesn't support some features), having to share DB instances with others during development and also running into weird obscure issues like DATABASE LINK queries taking 100 times longer in some cases, even when executing the same SELECT query on the remote DB works without issues.

To not go into a rant, I'd sum it up like this: be in control, isolate the things that you cannot control, pick the correct technologies, do the simplest thing that you can get away with without overengineering and think about the person who'll have to maintain, debug and grow the system in the following months and years (which might also be yourself, sans knowledge about what the code did, if you don't make it explain itself or don't comment the non-trivial stuff).
I really hope we dig into the gut processing of B group a bit more. Another candidate for improvements there is some types of ADHD. Some better defined links there would by awesome.
Good for you. Magical moments in careers are hard to find in my experience but they are so satisfying when you get there.

Glad whomever was over this didnt just drop the "dont rewrite" joel spolsky article and fight making it happen.
It's not known in Australia where you have to have a prescription to buy a vape but can buy cigarettes freely. Apparently they're relaxing the prescription requirement later in the year but still only pharmacies will be allowed to sell them.
GP was never their customer, though. They started filling out the application to open an account, got past the ID verification step, and then decided not to complete the new account process.

Likely the issue is that they just didn't think of this possible case, and there's no way to delete the ID information, and the CS person didn't want to go through the extra work to find someone who could approve it and/or get it done.
While we're talking about keyboards, why won't they put dedicated page up/down keys ? There are 2 empty spots right above the left/right keys that would be ideal for this and are basically just wasted, being left empty, as one can see on the photos. It's one of the reasons that makes me cling on my old Thinkpad for so long, I use them all the time.
Okay but now this is just imperative lol, it's no longer functional at all, since your function is now just a sequence of instructions, i.e. it's a procedure rather than a pure function. You've just proved my point
When I was a kid my dad took me to “take your kid to work day” at Lockheed. I think they hid the secret stuff somewhere where visitors wouldn’t find them.
> a bank is required to maintain a record of the identifying information provided by the customer.

They didn't complete the application, though, and so were never a customer of the bank. So this shouldn't apply.
The dose makes a huge difference. The amount you get in the daily multivitamin pills is minimal really if you have issues with processing those.
> I don't quite understand the use case for this sort of app (generating a nice changelog from a well structured commit history.) In my experience if your team is disciplined enough to use something like Conventional Commit rigorously you don't actually need an app.

> Just copying the commit descriptions into a doc, even in a nicer format, feels like theatre to me. You aren't gaining anything. Non-technical users won't benefit from it and everyone else can learn 'git log'.

> I really hope I'm missing something.

Yes, this seems to be cynical for the sake of cynicism. The point of tools like this is that you do in fact want this document, because no one will be copy pasting messages from git log to put in the changlog files. And if they are, they would appreciate a tool to do it for them.

Additionally, changelogs are part of releases and will show up in GitHub releases, package managers, etc.
GU5, Bramley – Do Not Drink Tap Water Notice
> You'd have to be a "US Person" which means generally at least green card or a citizen of a friendly country.

Under ITAR, “US Person” means US citizen or green card holder. (And a few other obscure categories, such as individuals granted refugee status by the US government.) Export to citizens of friendly countries (who don’t have green cards or dual US citizenship) requires an export license. I heard some talk they might exclude Australian citizens from this rule as part of AUKUS (although even there I don’t know if it would apply to space stuff, since space ain’t got nothing to do with nuclear submarines), but right now no ally is excluded.

> Like if you gave a tour to a Chinese citizen you could well be guilty of exporting protected technology.

From what I understand, theoretically speaking you are okay if they have a green card, or dual US-Chinese citizenship. How well the theory holds up in practice, I don’t know. (Technically China bans dual citizenship-however, if a Chinese citizen naturalises into the citizenship of another country, what happens if they don’t tell the PRC government they did it? And even if they do tell the PRC government, although PRC law says the government has to cancel their Chinese passport, the PRC government is free to ignore its own laws whenever it wants to.)
How can I improve the natural language understanding (NLU) of my AI chatbot?
The gyroscope aiming on mobile is fantastic!

I've never seen a demo with such small latency and responsive to small movements. Even more impressive by being a web page and not a native web.
My reason for learning the US layout back in the days was because of Counter Strike. For some reason it didn't adhere to your OS keyboard settings when chatting, so trying to write ø always became ; etc, so we kinda after a while just learned how it worked (didn't even know it was a US layout thing to look up, just bruteforced and memorized).
To enhance your AI chatbot's NLU, consider the following strategies:

Quality Training Data: Use diverse and well-annotated datasets.
Advanced Models: Implement and fine-tune models like BERT or GPT-4.
Context Handling: Ensure the chatbot maintains context over conversations and recognizes entities accurately.
Continuous Learning: Incorporate user feedback and regularly update the model.
Error Analysis: Regularly analyze and address errors to refine the chatbot's understanding.
These steps will help improve the chatbot's accuracy and user interaction quality.
Yeah I've had laptops with various hardware layouts and don't really care, other than I prefer a Nordic layout on Macs where the Enter key is tall rather than wide. But it's a trivial adjustment.
Nordic keyboards were a mistake. Should be redone. They are bad for both writing and coding. Changed to US International years ago too, and will never go back.
It's not QT. The interface is HTML+css via node.
> Every software bug is an example of a computer doing exactly what it was told to do, instead of what we meant.

That is only as long as the person describing the behaviour as a bug is aligned with the programmer. Most of the time this is the case, but not always. For example a malicious programmer intentionally inserting a bug does in fact mean for the program to have that behavior.