skysight-inc/HackerNews huggingface dataset:
I guess I still just don't get it. I'm always shocked at glowing recommendations of TikTok...from HN of all places! Every time it comes up here, I take a few minutes to browse the site, to see if anything changed to justify the praise, and it hasn't. The content may be more lighthearted, but over half of the random feed on the home page I just browsed is fundamentally the same "camera in your own face" narcissism amplifier as Instagram and the influencer portions of YouTube. I'm not even seeing a lot of hobbies there. It's just people who are not remarkably talented, but want to be in a video, making a video of themselves. It's got the same validation-seeker signals as the rest of social media (like count, comment count, share count). I browsed for about 30 minutes this morning so I could at least be informed before I comment, and literally found nothing remarkable or interesting. No unusual musical talents or athletics. Nothing really novel or even relatable. Just 20 year-old zeros making videos about themselves. Why is this a thing?
Except that as the author of the article says, they don't owe investors any explanations. VC money will demand results which you cannot just ignore for a quarter.
Benchmark on Mac(or Windows) is hard.

You really have to know how it works to know what you're actually benchmarking, and if the numbers are even remotely related to what they would be on Linux. Unless the plan is to actually use in on Windows/Mac, ofc.
An active compost pile can consume an animal carcass of any size, bones and all, in the 60-90 days. This is the way nature recycles resources and she has gotten very good at it over the eons.
The “exception” section pretty much describes why you should use comments. The other examples are just bad comments.

A comment like “delay for 5 seconds” is bad and easily goes out of date because you might change the number of seconds in the code without updating the comment. The comment should be something like “wait a few seconds for foo the settle down” to explain why you’re doing (such a horrible hack).
"if we simply could have used a smart contract where money is automatically deposited upon project completion, we would have ensured payment."

What? I didn't know this was currently possible. Maybe you should make this your product.
Isn't that a tautology? They aren't 24/7 sources and we don't have the battery technology to power modern industrial society. In addition to renewables we need nuclear energy; a constant source of safe(1) clean power, compact, little waste.

1) https://ourworldindata.org/safest-sources-of-energy
The only way I can think of that working is if the provider is intercepting DNS requests for popular speed tests to redirect to an internally-hosted version that would be faster. Otherwise, I can't think of any realistic way DNS settings can affect actual throughput.
In a lot of places, _you can_ friend!
any mention of a “right” tends to have an absolute or moral quality to it

and that seems to be exactly how the law is meant to be understood from the way it is written.

the main problem with choice is that it is only the choice of the employer, not of the employee. and therefore having such a choice would be at the disadvantage of the employee.

there is a balance to be made between the convenience for the consumer and that for the employees. as an employee, having the same day off as for everyone else is what makes it possible to join other activities. if people start getting random weekdays off then suddenly most of my friends will not share the same time off as me. that's not workable.

therefore the more important question is, how many people get disadvantaged if we allow supermarkets to open on sundays, compared to how many get a benefit, and is it worth that tradeoff? obviously different countries feel different about that, but pretty much all of them still give everyone else the same weekend off instead of offering full flexibility for companies to choose what days to take off.
Why 87% of applied ML projects never make it to production
Pray that the rocket doesn't blow up spreading nuclear fuel all over the place. Here is a Soviet "success story" involving a nuclear reactor on a sat.

https://en.m.wikipedia.org/wiki/Kosmos_954

Concrete would need cement made with limestone and massive amounts of heat and water which is scrace on Mars.
> A huge benefit of TypeORM is that you get full static type support in all of your queries, including in the returned results.

When did I say I wanted to give up static typing? You can have both[1][2]. I would never give up static typing and would not have used Node if TypeScript/Flow were unavailable.

> TypeORM in particular is well designed and quite awesome.

I've used TypeORM extensively in production on multiple projects for years, including with a fairly large team.

It has silent failures, and its API was unstable/unclear for a long time. It's been a very messy project for most of its lifetime. They couldn't even decide on an API for lazy-loading of relations, and there was some hidden API that was semi-supported and not type-checked.

Partly because it's built on Node, it's very difficult to use a debugger to see the relevant frames when you hit a breakpoint or an exception -- if you can even set a breakpoint where you want it to be before just running into an error at runtime.

There's also the same core issue that all ORMs suffer from, which is that the abstraction becomes leaky as soon as you need to do anything complicated with lots of joins or advanced SQL features.

1. https://github.com/adelsz/pgtyped

2. https://jawj.github.io/zapatos/
What about people with the same birthdays?
> If I need to read your comment in order to understand your code, there is something wrong with your code.

This whole post is based on a bad premise. Whether the reader can understand the code is dependent on the reader and not just the code.
The article’s content is fine IMO.

I saw the title and thought this might have been some sort of hot take on self-documenting code. What I found was the same "why, not what" advice that's been repeated for decades. It's a good guideline, but nothing remotely controversial or original.
What is depression caused by, in your opinion?

I have my own view, just want to see if yours is similar to mine or is interesting in some other way.
And someone will then have to puzzle through what they assume is "well-written code" to work out what broke when things failed...

I tend to comment rather heavily, in the "free form" style frowned on here. However, most of my code is directly related to hardware, in some form or another, and "Assuming the person reading the code has the full hardware reference manual memorized" is simply a jerk move. There are plenty of things like direct accesses to particular memory addresses that, even with plenty of #define wrappers, are still a bit obscure unless you know what, exactly, that bit is doing. And that's before you get into weird corner cases of hardware or doing things outside the norm where even if the code is clear, it's only because you already know what it's trying to do.

It's an interesting goal and may work in a few small corners of the software industry, but having spent plenty of time sorting through what assumptions about the state of things "well written code" (which is usually a lie anyway... what's obvious to one person may not be obvious to a different person with a different background and different expectations about the code), I'll take something with a couple hundred lines of explanation at the top of the file covering the concepts the file intends to implement over bare code, any day.
I wonder when whey will make the debugger work with non-proprietary versions of VS Code.

I am not joking, I wish I was. The official C# debugger is not only proprietary, it’s also not licensed for VS Code versions compiled from source.

The rest looks cool, hopes are high for MAUI. But really man, forcing me to jump through a bunch of hoops just to get a (somewhat) working debugger ... That kind of a move is a remnant of the old Microsoft that absolutely needs to die for the new Microsoft to live on.
How does KYC benefit them? Seems like (if legally allowed) they would want to reduce the friction as much as possible.
I don't code very much Java or C#. I've tried to get into Spring because I wanted to save time but it was too complicated for my patience. I also evaluated ASP.NET and it seemed significantly more convoluted.

There is a ton of documentation for both Spring and ASP.NET but both are so complicated and specific to investing in exact ways of modelling users/auth/whatnot that they are both super hard to get into as a hobbiest outsider.

I like both languages and they both have good microservice libraries and general ecosystem. I just don't think it's worth saying Spring is complex without talking about ASP.NET.
How tolerant was it against typos? For example: "fuk". Or did it contain every variation already?
Show HN: H5records – large dataset format for deep learning
Why, not what.

In the real world, code is based on business logic, so comments are a good place to add a ticket number (though most times a better place is usually a commit message) or a brief explanation of "why in the hell would anyone ever do it this way". Because the answer is usually something like "the client asked us to do it this way".
After reading the whole article, I didn't see anything that "points away" from the lab leak theory, unless it's supposed to be this:

> “The connection between RaTG13, the Wuhan Institute of Virology and Sars-CoV-2 isn’t required any more,” says Robertson.

But it was never required, just possible (and perhaps plausible, according to many people).

I did, however, find lots of transparent attempts to throw mud at the lab leak hypothesis, like this little gem of spontaneous irrelevance:

> The resurgence of the lab leak theory – promulgated early last year by Donald Trump and his supporters, before being dismissed – has been fuelled by the...

The gist of the article seems not to be related to any "new studies", but rather this:

> This leaves the lab leak theory resting principally, for now, on unverified reports of three cases of respiratory illness among the WIV’s nearly 600 staff in November 2019, a winter month in Wuhan, and the fact that the institute took a database of viral genome sequences offline two months earlier – to protect it from hackers, they told WHO investigators.

Fine. But what does the alternative hypothesis rest on? The only claim they make on behalf of the natural origin is that it has happened before. Well guess what: this[1]

[1] https://en.wikipedia.org/wiki/List_of_laboratory_biosecurity...
This is a complete mischaracterization of why these things occurred.

It has nothing to do with renewables - it has everything to do with aging infrastructure:

* In California, we haven't kept up with climate change and made the grid safe for the new normal of high heat, high wind, and dangerous fire conditions.

* In Texas, they didn't keep up with climate change and crazy events like the winter storm they had this year. They also have a screwed up operational model but that is a side point.

This will get worse and worse as the climate changes and also as we attempt to electrify everything to try to address it.

This is why investing in infrastructure right now is so important.
“The Idea Factory” is the story of Bell Labs and the development of the transistor which led to Silicon Valley.
We understand the skepticism, and we're grateful for the great work that the community has put into CCXT.

We've added a lot of features around the GUI, including a portfolio builder tool that helps you create and manage your own index fund, as well as balance management and multi-exchange price comparisons.

Not everyone feels comfortable in an IDE, so we want to make these tools easier to use for everyone!
MIT, Allen AI and Microsoft Open-Source a Suite of AI Programming Puzzles
"... except in reasonable and justifiable cases where a user has been placed into a so-called "walled garden" for reasons of abuse, security compromise, account non-payment, new service activation, etc."

Their own words
It's probably good if it's done once every four years. But companies do it every year if not multiple times a year. So at that point, without new blood coming in, you end up cutting into the meat of a high performance org.
Nuclear powered submarine has a highly trained crew, many are busy monitoring / servicing the reactor.

And the reactor brings itself home for service if needed.

That seems way different than what you'd want in Antarctica.
While the title is a bit off, the sentiment is still valid.

No comments by default, every comment needs to be justified. As a rule, still more reasonable than "use comments only when needed", which is more on the pro-comments side.
that actually sounds like a fun thing to do in a formally verified language like Dafny. you'd write a "ghost function" for the Mandelbrot equation, then write your code, then prove a theorem that the epsilon between the equation and the code was below a threshold at every pixel in your rectangle.

I guess that'd still be TDD, but with the first T standing for Theorem :p
Yeah, I too dislike it when companies respond positively in response to criticism.

I prefer the orgs I interact with to be perfect and never make mistakes and when they do (but they don't because I only interact with perfect institutions) I prefer them to double-down instead of improve.
This makes so much sense, I prefer that my body can be used to grow plants/trees and whatever vegetals rather than getting putrefied in a coffin, and using land space for no reason
Thanks @nathias. Please let us know if you run into any issues or if you have any feature requests!
Writing is followed for design reviews as well.

The recommendations to solve the challenge you mention are to (a) writing better, (b) splitting into a sequence of meetings, (c) reading the document ahead of the time.

There's no real reason why writing process should not apply to design documents as well.
To end science denial, admit that policymaking is not all science
This one is pretty tame. I feel like we have all been tempted to write ridiculous test data -- "Dear Valued Customer, we regret to inform you that the HBO Max Defraculator has been compromised and your credit card details have been sold to a self-aware purchasing bot. We are sorry and wish you the best." Sending that to your customers is a minor disaster. Sending "This template is to be used by integration tests only." will be ignored by everyone who isn't a software engineer.
So 1000, 1001, 1000, 1002, 1000, 1003, 1000, 1004 requiring 80 bits is good if you could get it to 16 bits plus a Huffman tree which would admittedly eat up the 64 bits difference in this tiny example? Storing the delta is essentially predicting that x[i + 1] = x[i] and storing the difference to that prediction. One could do better by having a better prediction, for example x[i + 1] = x[i] + median_gap_size which would bring the prediction error down to 0, 1, 0, 2, 0, 3, 0, 4 in my example, which could be encoded in 24 fixed length integers plus the median gap size. This could probably be further improved by adaptively predicting the gap size. Making the prediction errors small and independent of the gap size makes the use of short fixed length integers in the common case and switch to longer integers for outliers by reserving one short code as an escape code a much better choice.

In the end the result is probably heavily dependent on the exact structure of the integer lists you want to compress but I do not see how fixed length deltas can be competitive on arbitrary inputs.
As an adult-diagnosed ADHD person and someone who's taken Concerta (time-released ritalin) for about 12 years, I wouldn't be so quick to dismiss a differing experience of stimulants as a myth. I had stopped taking it for about one year while I was undergoing chemotherapy, and recently started taking it again, so I have a pretty clear recollection of what it feels like to get started. No euphoria, but a feeling of mental fog clearing.

I've never experienced euphoria from stimulants, and I've always felt like I've processed caffeine differently than neurotypical individuals. I've spoken with several people with ADHD who have the same experience. Perhaps it's more accurate to say that not everyone feels euphoria from stimulants and there's some correlation between ADHD and stimulant non-euphoria.

I do agree with the titration schedule being a good idea. With any potentially mood-altering substance it seems wise to start slow. It gives time to gradually understand its effects (some good, some less so), and after some experimentation, I decided that a low dose was best for me to provide just enough of the "glasses for the brain" effect without otherwise affecting my mental state.

Anecdotal, perhaps. But enough anecdotes to point to some signal in the noise.
Do we not have enough of these fully featured game engines? Game development has become so bloated these days. You need teams of hundreds or even thousands of people to create a full game. In the PS1 era some of the best games were built by a team of a dozen or so people working for 1-2 years. Instead of focusing on graphical fidelity I think we should be focusing on lower development time, gameplay features/diversity, stability/portability and implementation. I have yet to see a proper open world game (Think GTA but you can enter every room in every building) with good draw distances that don't suffer from horrible pop in.

Also how about a game engine where it's easy to build games? The WC3/SC2 world editors are great examples, you can get started and start building stuff from the start. Even though it's an engine made for making RTS maps it's modifiable enough you can create FPS games in WC3 if your willing to put in the effort. https://www.youtube.com/watch?v=gwtteOIksbo
To remove the prefix which de-emphasized how really important it was that the JDK was free beer.
i think that is not an issue of sunday closure, but simply a sideeffect of most everyone working monday to friday, and hence shopping on the weekend. in places where sundays are open the phenomenon is simply spread over two days. if you really want quiet shopping you need to go on a weekday morning while everyone else is at work.
I think he contradicts himself and confuses the data with the information. I don't think delimited values representing a table in a column can be considered normalized.

>Make no mistake, encoding multiple values in a single string is generally a bad design. But it has nothing to do with first normal form. First normal form mean a column should not allow relations as values. A comma-separated string is still just a single string from the perspective of the database type system.
Visual Studio Community has been free for years and lets you build anything. VS Pro and Enterprise are for bigger teams/projects with some advanced features but nothing you absolutely need.

Also what's the problem with VS Code? It's great for C#, and basically the mainstream choice for many other stacks like Go and Node already.
I'm a C# and ASP.NET developer.

You should definitely use this stack for a startup or any operation with less than three full-time developers.

I've literally done this at three enterprise scale startups with just three devs (including myself). Working on the 3rd startup right now. The productivity of .NET, Visual Studio, and Azure is amazing.
I don't speed read, but here's how I read faster (+50 books/yr):

* Read more. I find myself subvocalizing more when reading about new topics and less with familiar topics. The more you read, the more recurring themes you find.

* Highlighting helps me gamify reading. I'm basically hunting for interesting sentences.

* Appreciate which books are meant to be read quickly (self-help books usually fall into this category) vs. those meant to be read slowly. Give yourself permission to read at the appropriate speed for the given content.
Because "getting to know your data storage technology better" isn't the business goal. On the surface, that's a great goal to have, but taking an approach that requires you to do 100x as much work so you can learn SQL better isn't software engineering. It's over-billing.

I throw together 200 lines of schema in Prisma.io and it creates 20,000 lines of GraphQL handling code plus more ORM-specific code that allows me to create type-safe access to the database.

And "the database" right now is PostgreSQL, but one of the business requirements is that "the database" could also be SQL Server or MySQL.

Having learned the salient details of the ORM in ... hmm ... about three days? ... I feel that the advantages of getting a full GraphQL API that can be wired up to an arbitrary backend database for 99% of the queries vastly outweigh the fact that most of my database queries are entirely inside a "black box."

In six months I've encountered exactly one problem where the black box made my life more difficult. I think I wasted about an hour, maybe 90 minutes, on tracking down why it didn't work as expected. Given that "writing custom SQL" for all of the queries that I've created would have required 10s of thousands of lines of additional code plus system tests to verify that the queries were all working as expected? That's a profoundly huge win.

I'd still be writing SQL queries months from now if I had taken the approach you're suggesting. Maybe it's advice that's good for consulting firms that charge by the hour and love to find ways to make their developers work more hours, but in my book it's not even ethical to recommend.
It won't ever get to 21M...

https://medium.com/amberdata/why-the-bitcoin-supply-will-nev...
> make team success the important goal

That leads to the prisoner's dilemma and tragedy of the commons. When team success is the goal, slackers thrive.
Now I will have to read it :-)
The was also the B-52 crash out side of the Thule air force base in Greenland, which was carrying a nuclear warhead[0]. This, in an area designated as a nuclear-free zone by the Danish government.

The cleanup project was unofficially referred to as "Dr Freezelove" by the Americans involved, which is a bit disturbing when you think about how Dr. Strangelove ends.

[0]: https://en.wikipedia.org/wiki/1968_Thule_Air_Base_B-52_crash
Not official, but I have had good experiences with AvaloniaUI, which sticks very close to WPF and is part of the .NET foundation umbrella. It inherits quite a lot of what made WPF mature and robust
You could probably get away with just using nuclear power and avoid all the industrial waste produced by manufacturing the vastly inferior renewable energy equipment. That seems like the real big brain strategy. A big problem is that it's not politically correct to say renewable methods are just not going to work but if we could get over that hump then we'd find ourselves on a much better path.
For me at least, TDD has driven me to look for more functional solutions to problems. It's hard to come up with a more testable piece of code than a pure function that spits out the same output every time for a given input.

Unfortunately this approach tends to be less effective in languages that do not have good support for functional ideas like Java and C#.
How to Hack Parkinson’s law to get back 20% workweek every week
"a fox knows many things, but a hedgehog knows one big thing"
A Little Every Day: The secret to finishing your projects