skysight-inc/HackerNews huggingface dataset:
The Az PowerShell module just uses HTTP APIs, so anything they do can be done with other tooling if you really want to.

(There’s also the Az CLI tool, which I don’t like as much as the Az PowerShell module but might be easier to manage in an environment like that.)
First read, I don’t take notes unless I’m familiar with the material. At most, I’ll mark interesting passages. But I usually pause after each or every two chapters, reflecting on the concepts.

I don’t take notes with fiction books, but I pause whenever I can’t give it my full attention (interruptions, some other tasks, tired).
Tell me you are a bigot without telling me you're a bigot.
https://archive.is/aubJh
The Ukrainian War would finish in a week, if everybody would stop buying anything produced by the Western Companies still doing business in Russia.

"Stop Doing Business with Russia" - https://leave-russia.org/
PowerShell is more verbose than Bash, and has its idiosyncrasies (like sometimes automatically unwrapping 0/1-element arrays into scalars when you least expect it), but it is more productive and more readable. Object-orientation can be nice to produce pipelines.

For example: find potential file duplicates in a folder, recursively, by grouping by file size:

Get-ChildItem -File -Recurse | Group-Object -Property Length | Where-Object { $_.Count -gt 1 } | Sort-Object -Property Count

No need to remember arcane `file` incantations, no need to parse textual output. You get real objects with properties, and tab completion can see their structure.

Need to parse JSON? No need to involve `jq`, just `Get-Content -Raw whatever.json | ConvertFrom-Json` and do it directly from PowerShell. Need to convert XML into CSV? ConvertFrom-Xml (or Select-Xml) -> do stuff -> ConvertTo-Csv.

Is `Get-ChildItem` too much typing? Use `gci`, or `dir`, or `ls` (by default only on Windows). Is `Where-Object` too much? Try `where` or `?`. And things are case-insensitive.
Oracle Rolls Out UEK-Next Kernel Based on Linux 6.9
I've been on 5 or 6 different teams that used what they called scrum. I've never seem it work well, either it quickly devolves into an exercise in going through the motions or it's used as a micromanagement exercise on a team with little trust.

I have seen it occasionally help promote better communication within the team, like earlier calling out dependencies or having team members ask for help earlier. Communication is a different challenge though, scrum is too oppressive when the problem to solve really is just better, and more frequent, communication on a team.
The saying makes the assumption that people don't want to repeat history, which may have been true a few decades ago. A great many people today actively want to repeat history, mistakes and all. They think then was better than now.
The case for Perl is just that it has no limits. You will never run out of tool if you go with Perl. That is what, I believe, makes the investment worthwhile.

Why Perl gets such a bad rap, then? I'll tell you.

I've used Perl for almost 30 years now, and I've never found any limits in the tool. This means every limit I found was _mine_. Many programmers feel bad when they find their own limits, but it doesn't have to be the case.

You should be OK with finding your own limits, and be willing to overcome them, and strive to become a Perl power user, just like the founder, Larry Wall.

If you choose this, to grow and improve and be better, and better, and better, then Perl is the best option.

It's up to you.
It slightly sets my teeth on edge to see the work items in Kanban referred to as “tasks”. The goal isn’t only to minimise wasteful multi-tasking locally, but to see deliverables flow through to the point of customer impact as smoothly as possible.

For me, the Zen of Kanban in product development is to work the board from right to left, working backwards from a "done" that means "someone's need was met" [1], stickies staying on the board until the learning is accounted for. You just don't get those senses of impact and learning if you think in tasks, and when tasks are managed at an unnecessarily fine granularity, I would consider it dysfunctional.

For what it's worth, I'm the author of Kanban from the Inside (celebrating its tenth anniversary in September) and Right to Left: The digital leader's guide to Lean and Agile (2019).

Edit: In case I am suspected of being anti Scrum, the reverse is true. Scrum done well can be truly great. Moreover, Scrum and Kanban are highly complementary to each other – they not only work in different ways, they do different things. As the article eventually acknowledges, there is no either/or here.

[1] agendashift.com/done
Yes true, the one difference might be that you don't expect other consumers with a different approach to IO to use your internal libraries, although it does help you if you want to change that in the future and the testability is still useful
Show HN: Text- and photo-based calorie tracker with universal language support
I built the most frictionless calorie tracker that works in every country in every language for all food & exercise.
- Works with all local and international foods
- Works in 108 languages for both input and output
- Accurately estimates portion sizes from images
- Zero hassle entries
Sure, I don’t think anybody disputes that the Bible is a not single book written at once.

But the claim that any part of Genesis dates to the Exile is a weak historiographical claim, based primarily on a few pillars of very weak circumstantial evidence: a) we don’t have many physical examples dated to a prior time - but that’s not at all surprising; the vast supermajority of texts don’t survive, and many of the most ancient copies we do have are relatively recent discoveries; b) it makes sense to some people to argue this based on (reasonable) speculation about the development of the Jewish religion and the pressures at different periods of its development and c) as a corollary to b, one mainstream opinion is that Genesis can mostly be attributed to two different sources by a stylistic analysis and one of them is simply believed to date around the Exile.

This corresponds to the general current fads in historiography and history but it is by no means definite, and we shouldn’t be surprised if it is all overturned in a night by a single discovery, as these things very often are. This type of historiography is not really rigorous in a meaningful sense and is based essentially on current academic trends and a few authorities.

So we can safely consider the arguments underlying the dating ourselves without getting in too much trouble, but we don’t even have to do that to address your particular claim that the portions of Genesis must have been devised by an Exilic writer due to Babylonian influence. This essentially requires engaging in a deliberate pious fraud, which then was taken up by the other Israelites without question and who accepted the new stories with no recorded debate, and which also received no pushback when the Israelites who did not go into Exile. We would expect the possibility of diverging traditions on this point, but for example, the Samaritans have precisely the same story on this point, although the dating of that is also a point of contention. Either way, we should keep in mind that only some Israelites went into Exile, and plenty remained in Israel and Judah and maintained their traditions through the 70 year Exile.

It’s possible that this did happen. But it’s also the case that Babylonian contact was not new in the Exile period. The Israelites didn’t exist in a vacuum, they were part of the tapestry of the wider Semitic world for their entire existence and would have had familiarity with all these stories and beliefs the entire time. Indeed, it’s most commonly believed that the Israelite religion was not unique, but a simple development into monotheism from a normal localized Canaanite religion. And indeed, at some point, they all shared a common origin. Rather than adapting a Sumerian-via-Babylon story in a very late period, it’s a much more parsimonious explanation that some version of the story always existed amongst the Israelites in their oral tradition regardless of when it was committed to writing.
"The alter orbis which Great Britain has aspired to be is not simply a world apart from continental Europe but a world embracing non- European continents and islands overseas." - Arnold Toynbee

Brexit was always an eventuality, but much like the empire was always going to fail.
I forgot but one thing I also liked that made me go "Why would bash not have that?" is having a dedicated verbose,info,warn,error,debug output and a glob star *> to redirect everything. It's nice not having verbose text polluting stderr.
If it's required then how can it be an 'addon'?
> Just give me a list of prioritised tasks.

The role of a modern Software developer is changing and Scrum is accommodating that fact. If you just want a task list, start coding and be left alone, that's fine, then you should look out for teams who don't do modern/agile software development. I've had my fair share of such developer types in my career and i would have just wished that they didn't have signed the work contract as they pretty much knew beforehand that they dislike agile but kept that for themselves until after the fact.
No, you want your model to be well calibrated. If the model accurately assessed a 0.55 probability of going blue, then that is what you want.

People who try to correct for “unbalanced classes” and contort their model to give polarizing predictions are frankly being pretty dumb.

The correct answer is to take your well calibrated probabilities and use you brain on what to do with them.
> there’s an obvious attack on this, but I’ll go ahead and note my position on it: the whole premise that we can do any of this without just using actual matter the ordinary way is so far into magical territory that we might as well ask “what if lephuchans simulated it?” or “what if god imagined the simulation?”—well ok, sure, I guess if magic is involved that could work, but what’s the point of even considering it?

That's one of the main points of using a thought experiment: by declaring axioms explicitly, by fiat ("true" by definition), it prevents the mind from taking advantage of thought terminating get out of jail free cards like this, it forces people to argue their point.
If you don't mean to say that trans people exist as a fad, you might edit this comment for clarity.
> 1/256th vCPU & 4mb RAM. Don't use it all up now!

The compute costs on some databases are absurd. I was considering timescaledb recently

0.5 vcpu and 2 gb of ram is $32 a month.

Also the prices do not increase linearly, 1vcpu and 4gb of RAM is $149 a month.

What the actual fuck!

That being said, I will give a shoutout to Neon. You actually get a very good db just on their free plan. Let's see how long that lasts before they start the squeeze.
No expert in either but I've had to use both a fair amount. Powershell fell into a few traps that rendered it awful to use IMO:

* Trying to be a .NET language. I don't know why the one-runtime-many-languages promise of .NET withered on the vine while it flowered in Java-land without the promise even having been made, but it did. If you're writing .NET code, use C#. (And I say that having worked in one of the very few teams doing large scale development in F#.)

* Failing to get the basics of being a shell right. I can't remember the details as I've left it firmly in the past now, but its handling of redirection was just broken, to the extent that things that were trivial in bash were nigh on impossible in powershell. I got the impression its developers ignored the things bash etc. did well in their enthusiasm over building something new and powerful.

* Being fetishistic about stuff like requiring Verb-Object naming for everything. It's certainly subjective and has its defenders, but IMO it renders scripts ugly, is awkward to type and doesn't materially improve discoverability or memorability at all.
I think part of the purpose of the Agda project is to see how far they can push programs as proofs, which in turn means they care a lot about termination. A language that was aimed more at industrial development would not have this restriction.
Compliance with what exactly? When you bring servers down to Brazil it gets weird, outside just not supporting that region, not much you can't do about it. We never did anything in Brazil because it was such a huge pain in the ass, it's hard to get stuff in and expensive to rack once you're there. imo Good for fly for doing the work, even if they did have to slip someone a 5 on the way in.
> I have this web page saved up in case I ever need to convince anyone of this... http://mywiki.wooledge.org/BashPitfalls

This is a great list of pitfalls, absolutely, but they are more an argument for integrating shellcheck into your IDE than avoiding bash, IMHO!

I know, I know, possible religious war, but I find that bash+shellcheck is far more often the right toolset than switching languages to avoid the pitfalls.

The immense power and expressiveness and immediacy of bash makes so many programs and so much prototype->PoC->MVP progression so easy and effortless that it is worthwhile having tooling to catch the worst of the warts.
The five secrets to Ferrari's success as a luxury brand
Ask HN: High Quality JavaScript Code Bases?
Are there any JS projects which you consider to be top notch and worthy of emulation.

Library code is OK, but extra +1 if you can point me towards any extremely well done application level JS.

Thanks.
Yes, the trees in the shadow in the top left part of the image appear more green, since they aren't tinted by the sunset.
>In paintings, it is known that the viewer can get out more than the painter put in.

There’s something very much “Dabblers and Blowhards” about this statement that I can’t quite put my finger on it. [0]

Try painting, I mean really painting, before spouting nonsense. It wreaks havoc on the rest of your comment.

[0] https://idlewords.com/2005/04/dabblers_and_blowhards.htm
That's a great website, I didn't know it, thanks!
Railink background: writing a game in Go
I researched this like a decade ago and my conclusion at the time was that Kanban and Scrum kind of work the opposite way. Kanban is a "pull" approach where you have some kind of big goal you need (e.g. a car at toyota) and then all the dependencies (car parts and orders etc.) are pulled along with it into the pipeline (or todo list).

Scrum is "push" where small items are pushed into the pipeline (backlog) hoping the outcome is what is needed.

For an individual "worker" it's not that much of a difference, they have to work on the tasks anyways. The project might have different outcome / duration though.
Ask them to write the tests that will trigger the failure condition - i.e. make them prove that it's a possible thing that can easily occur.

If it is, then at least you have a simple test case to work with so they've done a chunk of the work for you. If it's not, then they'll spend ages trying to craft a test case for a scenario that's extremely unlikely.

People very often leave you alone when challenged to put in the work to prove their point.
It can still be used for free as from my experience and the docs, monthly bills under $5 are free.
Mine was great. It had a normal amount of homework, a smaller class size (which was a happy but unintentional accident), and accelerated four years into three. We shared electives with the rest of the school and socialised widely. I was bullied pretty badly through my pre-teen childhood and the program provided a way out of that, which in turn taught me how to interact with a group of people who didn't physically and emotionally abuse me for social gain - something a lot of people take for granted.

Which is to say that anecdotes are of course going to be mixed.
Unsure, but why would they do that? Why risk paying more by making a higher offer elsewhere before making a lower offer?
What if say only 5% of people within each discipline do so, what is the epistemic value then of the claim "Archeology & history claim to be scientific"?
ChatGPT Mac App Stored User Chats in Plain Text Prior to Latest Update
I used to think like you but the rise of the extreme right wing (and extreme left wing) in Europe and the US has convinced me I was wrong.

You're right a kid with a hundred dollars of hardware and an internet connection might be able to out-meme the CIA but the problem is that the messages that get amplified seem to always be the most extreme. Moderate messages don't generate as much interest and this leads to an increase polarization of political discourse, an increase of extremism and voters who are all too willing to vote for demagogical opportunists who take advantage of that.

The younger generations of my friend groups are like yours but they don't necessarily represent society. I don't have any friends who would vote for someone like Trump if they were in the US. I do have family who vote for the French extreme right wing and those people in my family who do represent the majority of the population are not smart enough to get reliable information.
There are several ways in which it's bad. Forcing all the work to fit into sprints, for instance.

What if the natural way to divide the work results in some chunks that probably don't fit? Normally you'd just do them and it's be fine, but "we're doing Scrum" so now they have to be divided further and the parts have to be developed separately, even if that makes no sense.

Also Scrum assumes things -- that the product owner is very competent, that dev teams are self managing, that the business is interested in updates in the same frequency as the sprint -- that aren't necessarily true.

And everything that goes wrong is blamed on Scrum not being done exactly to the letter. So nothing else is fixed and everybody is more and more focused on doing Scrum ceremonies precisely right even if that was never their intention.
I see two sibling comments with reports of patchy reliability, so I'll note that it's been rock-solid for me (multiple daily deploys every weekday) since I last commented on it (about a year ago?)
Loved react till v15, I'm lucky enough that I moved into a strictly backend role right about when react 16 was introduced. I don't comprehend how hooks stuff is more readable. I occasionally browse the front end code in our company when trying to debug an issue, and the code just looks so un-intuitive. It's littered with `useHooks`, `useEffect`, `useMemo` and stuff.

It's night and day comparing that to our backend/backoffice written in Elixir.
To be fair, Brazil does have weird and expensive customs/import duties on technology products, which makes a lot of hardware expensive. Maybe fly.io just didn't know about it and that's why they say "suspicious"; But yeah, it definetely sounds like admitting to bribery, which as an American-registered company is illegal even in other countries.
Kind of funny but wouldn’t you want to just maximize(distance_left, distance_right) if you wanted the center?

Edit: no, derp, just walked into the same problem lol. Maximize the min should work though
In addition to what others have said, the license is GPL3, so a competitor would legally need to open source their app too.
It depends on the proportions.
The most general definition of R^2 can produce a result that is negative, and we are talking about a paradox related to values of R^2 that one should expect. So it is common to use linear models and linear regression. I don't know if the variance of the total population can be computed as the sum of the variances in each state, and state is not a continuous variable.

The population variance is the sum of the Between Group Variance and the Within Group Variance weighted by the number of elements in each group.
NASA's Planetary Radar Tracked Two Large Asteroid Close Approaches
I am fascinated by off-shore sailing, competitive and otherwise.

How racers manage to do the vendee globe (solo, from france around-the-world back to france) in just 80 days with just sails and ropes as engines is beyond me.

FYI the fastest solo sail around the world was set in 2017 at 40 days in a Trimaran
Compliance with ISO 37001 for example. As a big company, you can’t just go around and bribe random border guards to get your stuff through.

I’m also not sure if it is illegal to pay bribes in other countries when you’re an American company. So compliance with laws is another problem when paying bribes.

Edit: https://en.wikipedia.org/wiki/Foreign_Corrupt_Practices_Act

Looks like it is explicitly forbidden to bribe foreign officials as a US entity.
Not very smart to suggest you’re bribing people in other countries in official communications.
For practical systems, to improve synthesis/codegen, do you think working on the compile/eval toolchain is a good direction ?

For example, if we can cache/re-use the compiler run on previous codegen candidates, to speed up compilation of the next candidate sniplet
Sleep-Deprived Memories Restored by Common Medications
> I am genuinely asking what we lose by not knowing.

How would we know what we're losing if we don't know? But even beyond practical uses for anthropological information about our past, we as creatures just seem to inherently value exploration and desire for knowledge. That seems reason enough for people to feel "sad" about not knowing something.
This seems to be a small thing but it's odd to see people talking about how "Kowloon" used to exist. Kowloon still exists.

Kowloon isn't the name of the Walled City, Kowloon is where the Walled City was located.

You can still visit Kowloon even today.
Google's Emissions Shot Up 48% over Five Years Due to AI
Get a group of competent developers, say about five in a team. Trust them. Let them work with the stakeholders to figure out what needs building, and let them build it.
Meanwhile, I have never understood positions like this. What exactly does ideal team work look like to you? Do you collaborate with your teammates or do you all go off and work on completely isolated tasks? Do you only share knowledge after the fact through code reviews or do you manage to spontaneously talk about how to accomplish big things before the tasks are assigned? Do you routinely communicate with your users or representatives thereof or do they spontaneously show up and let you know about the actual problems they have and how things are going? Is the application you are building so simple that you are the only person working on it otherwise why is a ratio of 1:31 an effective ratio of collaboration for you?

From my perspective, well functioning teams communicate with each frequently. What's the daily, short term (spring), long term plan? Why did that last plan go well/wrong and what should we do differently? Routine meetings have a habit of becoming rote, but it is difficult to ensure such conversations are spontaneously happening between more than a couple of people. I don't want my colleagues to be surprised when they review my implementation, so we need to discuss it before I do it and vice versa. Discussing those things ahead of times also allows us to plan and prioritize more effectively. It also helps us align and build a better understanding of what we are doing.

I think people are obsessed with this kind of thing because people quest for a silver bullet, but individual teams working on disparate products and problems will find different strategies more effective and require a different balance of communication. Meanwhile, most organizations will push a chosen silver bullet in the name of consistency instead of enabling teams to truly self organize.
It makes me laugh.

You know what’s true in this article?

That perception that scrum is really distinguished from kanban in that makes it easy to generate estimates.

…and easy to make, totally wrong estimates, are exactly what people pretending to do agile can use to do their (doomed) waterfall design and release plans.

That’s not agile. It’s stupid.

If anyone ever tells you that you need to swap from kanban to scrum so that you can get good estimates, you’re basically doomed to a future of dark scrum.

Run!