skysight-inc/HackerNews huggingface dataset:
I agree with all of the above.

And I just realized: I should probably clarify what I meant when I suggested "the abandonment of software that is so poorly designed that it is difficult to package and/or run under Nix" as the means for a "cleaner base".

While that would make things cleaner in some sense, it's not what I'm suggesting Nix should do. I was mostly trying to clarify that the majority of what needs cleaning is extrinsic, rather than some intrinsic failing of Nix itself (though things could certainly be improved there, too).

The greatest source of difficulty for packaging/running things under Nix (having contributed at least a couple dozen packages, and the entirety of the Ruby/Bundler support) is software violating well established principles. To pick one silly example: say you need to get the home directory for the current user. Yes, you could do the equivalent of "/home/${USER}", and while that might coincidentally work on 99.999% systems, that's still wrong -- there's nothing keeping someone from having their home dir be something arbitrary like "/home_is_where_the_heart_is", and now your software will break. The funny thing is that the right way to handle this is also the easy way: use "${HOME}" if it exists, and failing that, fall back to `getpwuid` (or whatever your language calls it). It's easier/simpler because you no longer need to make any assumptions about how the file system is laid out -- either the user tells you through $HOME or you consult the password entry. Easy. But what happens when you send a pull request to fix the objectively wrong logic of the first example? You get push back saying "well, it works on my machine, and this is the first complaint we've heard, so no, I don't think I'll merge your request".

So, I guess I'm being kind of roundabout, but the takeaway I'd like for everyone to have is this: if working with your programming language is difficult on Nix, please go look for (and upvote) open issues in your language's issue tracker (they're probably there) from other Nix maintainers begging for fixes that would not only make it easier for Nix users, but would also remove latent correctness problems that have gone unnoticed solely due to the coincidental uniformity of all other commonly used distros. Just because something works everywhere other than Nix doesn't mean that the code in question isn't needlessly complicated/fragile and/or dependent on non-standardized assumptions that just so happen to be common on other systems.
People who don’t use scrum or sprints or any of it, two questions: 1. Do you actually have very few meeting and all of them are meaningful and useful? 2. Is your work predictable and both devs and PMs have a reasonable idea of how much work is coming up and the nature of the work?

I’ve worked on “no sprint” teams and I end up having several “weekly checkin” meetings for different projects, plus intermittent “stand ups” that lack a clear focus, plus my manager discussing tactical matters in 1:1s and the work plan is still a clusterfuck where it’s hard to know what’s priority, what work is coming up, ensuring we have requirements clarified before starting work etc..

The biggest mistake I see people making with sprints is not understanding that you cluster your planning over 1-2 days then you have 2-3 weeks with basically zero meetings besides standup or working meetings like system design. The benefit of scrum is lots of heads down time, the cost is you’re not allowed to just book meetings Willy nilly whenever you want. Most places I’ve worked have wanted the benefit of sprints but not understood or been willing to pay the cost (no-meeting weeks). So it’s agile rituals plus whatever other meetings you already had, and of course that sucks.

I feel like agile processes are this boogeyman and people think “just get rid of them and we’ll be good!” but you need some process or else work is chaotic. So what’s the better process that works for you?
When I tell people aids can be caused by more than HIV they literally think I’m a kook. Then I have to show them things like this.
> “When people say I changed the culture of Boeing, that was the intent, so that it’s run like a business rather than a great engineering firm.”

Both Boeing and Intel did this.

They reduced the number of people in C-suite who had STEM background until they didn't know how to make big technical decisions, or allocate money for R&D and production.

Scientists and engineers learn how to do business all the time, but you rarely see a lawyer or sales person getting STEM degree.
FLOSS = Free / Libre Open Source Software. It's meant to be a more specific version of FOSS, making the point that it's using a properly "libre" license, and not just free of charge and source-available.
Smalltalk Computers, Past and Future (2019)
I think of the WW1 Christmas Truce and wonder how many competitors are able to stop competing for mutual benefit. It's good when competition in war ceases, but it's not good when several "competing" companies decide to cease competition for mutual benefit. If people can do it in the highly charged situation of trench warfare, why can't companies do it to? Could a market with 10 competing companies cease competing for mutual benefit? What about 20?

Competition is not enough. It must be easy for new competitors to enter the market to ensure a nefarious trust doesn't form between companies.
I see what you mean, yes correct.
Your python.cards looks great. I suggest you add a few examples.

Any chance you are open sourcing the web app? I can see it being a popular way for niches to show flashcards eg. for students to learn X
Not exactly the root cause but also not not the root cause: Infinite Scroll.

That's my line in the sand for just about any app on my phone: If it has infinite scroll, it has no place on my phone.

"In 2006, Aza Raskin developed the infinite scrolling technique, whereby pagination of web pages is eliminated, in favor of continuously loading content as the user scrolls down the page.[3] Raskin later expressed regret at the invention, describing it as "one of the first products designed to not simply help a user, but to deliberately keep them online for as long as possible".[4]

https://en.wikipedia.org/wiki/Scrolling#Infinite_scrolling
These types of debates always seem to go this way - one person saying one option works way better for them so the other option must be crazy, followed by another person saying the opposite. I'm not an infra guy, but my guess is the reality is both are choosing the right option for themselves, because is no one objectively "best" option. Just tradeoffs.

I also think if a company is unhappy with their current set up and thinks that switching from cloud to on-prem (or vis versa) is the answer, they're probably delusional because "the fault, dear Brutus, is not in our stars, but in ourselves."
Yep. Big cloud bandwidth is a 200X markup from list price. Its ludicrous.

It serves two purposes for them. One is obviously a nice profit center. The other is that free ingress but expensive egress causes data to flow in but not out, creating a center of gravity and a form of lock in.
Been using ShapeUp for nearly a year now in an org of ~50 engineers.

Let me start by saying, if you intend to adopt ShapeUp, spend a great deal of time reading and buying into their structure of teams. Aside from SIP/QA & KTLO work, they flatten the “Core Product team” and build ad-hoc teams for a pitch that has won at the betting table - for that cycle. Trying to maintain standing teams with domains of ownership is a very challenging way to adopt this process.

In my experience, unless the entire org is drinking the kool-aid - hard - you end up with 6w cycles of waterfall. Pitches morph quickly from “present your idea that we bet against” to “write up a detailed design doc, along with an Epic, backlog and all projected work” - then the org will just do the work they want (betting or no). Now your team is committed to delivering on your pitch - any other work just gets dumped on the wayside - unless you’re on-call of course.

As with any other incantation of an agile process, you can bastardize it to confusion, thinking you’re smarter, or “we’re adapting this to fit our org”.

Folks, this stuff is a discipline. You have to buy in, you have to learn the principles, you have to practice them - as described - until you attain some degree of mastery that you can adapt. This is not an individuals game, this is at the org level. The individuals must commit with the org to gaining mastery before customizing to your liking.

In spirit - there’s nothing fundamentally broken with Scrum or Kanban or ShapeUp or whatever. It’s really how you hold it - and yes you can shoot yourself and others in the face by holding it wrong.
>There are many basic social needs that aren't being met for a majority of the population because so much time and energy has to go towards merely surviving.

Always has been since humanity's ~200k year history. The unpriviledged masses having free time for leisure and entertainment between work and sleep that isn't a Sunday, is a relatively new development of about ~100 years or less, for which much blood has been spilled. My grandparents were doing subsistance farming working about ~14h/day, 6-7 days/week just to survive, while today I can have my needs met by clocking in 8h of work in an office 5 days/week.

Ideally we should strive for better, but we forget our ancestors had it way worse not too long ago.
You're arguing semantics, you are on massive copium if you think that automation is useful to anyone. Go ahead and set up cryptographic attestation (or just try and interface with a TPM ffs) for your apps on Hetzner to decrypt customer data and see how impossible it is.
> - capture total velocity every 2 weeks and eventually use the avg for future planning

I have never got to this stage. Someone is added to the team. Someone leaves the team. New team members get more knowledge. Old team members get sick or take a lot of leave. The focus of what you're working on moves from one part of the code base to another.

Every time you have to throw your velocity out the window because you're not the same team any more, and those metrics are for a different team that no longer exists.

You could argue points are useful as a discussion point to make sure there isn't some massive piece of complexity hiding in something (everyone says 3 points, the quiet person who knows the most about it says 13), but even tshirt sizing covers that imo, and regardless after that you should just throw them away.
The same way you know that they aren't sending special agents to harvest your DNA from your Starbucks cup and analyze it without you giving them any permission in the first place, or that your bank actually has your money, or that the government actually exists: you don't, but you have to engage with the world at a baseline level of assumption of good faith when not proven otherwise, or you'll lose your mind, and it's generally worth noting which corporations acknowledge potential abuse cases, specifically and affirmatively commit to not doing them, and have a plausible monetization and profit scheme without any hidden abuse.
So I install Msys2 instead of Visual Studio. What's the big deal?

> let alone everything else expected from Windows applications across the board.

For example?
> > There's a simple test - can you put it on your porch or in a hallway?

If the building has ramps for handicapped and elevators you can put your motorcycle everywhere, even on floor 10 or 100 or even 1000.
Part of what makes a healthy online community is allowing topics to be brought up again. It lets people talk about new things, let's people ask about different details, and engages people who may not have seen the previous questions.

Stackoverflow has decided they're a knowledgebase and not a forum, which I think is proving to be a bad decision for them.
> Boeing has a lot to answer, especially since FAA gave them (after a ton of lobbying) the right to self-control themselves.

Then the FAA has a lot to answer for as well.
It was mainly as a joke, but I wanted to remove the attribution clauses, they just seemed dumb for a single-file javascript library that was probably going to be minimized anyway, where are you supposed to stick the license?
I heard that living outside of prison was also very dangerous. You are not protected well by the strong walls and professional guards.
Show HN: I built a Go client for Cloudcraft's developer API
Maybe he believes that a great business makes more money for the shareholders than a great engineering firm
Egypt going to be rather upset, insuring any ship that's going through the suez and red sea is going to basically be impossible at this point.

Meaning container ship traffic is basically going to end up at 0 through there.

Egypt who had been trying to stay neutral is going to struggle now. Egyptian pound is going to fly downwards at this point. Egypt sure not a fan of the Houthis or Palestinians now.
I unfortunately can’t imagine having time to test this, but I imagine there may be a way to accomplish this with embeddings.

The game itself is sort of an embeddings clustering problem, with the added difficulty that each group needs to only be alike in 1 way (versus a full vector distance which measures how alike they are in every way).

Maybe there is some way to search for a vector of weights, which, when multiplied by all members of a group of 4, produces weighted vectors with the least distance from their center? And then it’s an optimization problem to find the 4 groups that find minimize the total distance from each groups center?

It may be possible to find a weight vector that selects for a particular slice of a words meaning
This is interesting, but the telling is fairly vague. It cites a congressional report, which would be interesting to read, but there's no reference that helps me track down such a report.
It's 2024 and FiiO is making a portable cassette player with all-analog features
But that's just, like, your opinion man. It's not actually one of the founding principles of the country. Even when they were talking about limiting the powers of the federal government explicitly, as in Federalist 45, they were talking about devolving it out to the states. The Bill of Rights didn't even apply to the states for almost 100 years after Madison.
They're both fine but the larger React community makes it more interesting to me. More online support, more libraries, more jobs, etc.
Transcranial magnetic stimulation makes chronic pain patients more hypnotizable
The actual title of the video is "Your vision isn't what you think it is -- see for yourself"
You heard from somebody who doesn't know what they're talking about. In the same vein, I heard that vaccines cause autism.
Dark social media
LLM links: The Zvi on problems with LLMs
Well our on-prem team doesn't need AWS pricing calculation and optymization expert, so there's that :-)
It would be fairly easy to change the pricing policy. GCP did something similar for cross-region https://cloud.google.com/storage/pricing-announce#network. This is pretty severe because it seems to affect all reads. However I can imagine an alternate implementation where the source AZ is tracked when data is written and egress fees are charged when the data is read (as if the data was always stored in the source AZ). This could even be done more complexly such as only charging the first time data is read in another AZ. Once you read once it is free as-if it is now cached in that new AZ forever. Another option would just be raising the minimum storage duration so that it basically costs all or most of what the data transfer would.

It would definitely piss a lot of people off as it is adding to their bill, but it could likely be done in a way that makes exploiting this for just data transfer not worth it without adding huge costs to most "real" use cases.
Good point, but a whole new side of iPhone apps will also open up now
If only there was a way to let poster know about past threads before posting...
I am not sure if this is criticism for too many reposts or if once a year is considered a healthy dose of dupes.
Good recruiters vet people, and jobs, and match them up. And good recruiters have relationships and inside tracks with employers. Not all recruiters, of course. Experienced developers, on the other hand, have little incentive to vet their peers, and may do a worse job than a good recruiter because they will focus on different things. Developers and employers have different definitions of quality, in other words.

Of course "managers only care about quality candidates coming through the door," or at least they care a lot about that. But you have to define what you mean by "quality candidates" and how you have an efficient way to identify those candidates and put them in front of potential employers. You can just say that people in your directory have experience and got vetted somehow, but I think you will have to do more than that to stand out and get credibility.

Many people have attacked this problem, including recruiters and agencies, and all kinds of job boards and lists of professionals seeking employment, from LinkedIn to more specialized or elite lists. If you have some new ideas, great.

You started this thread with a proposed directory for developers that would let the "opportunities can find them." Who pays in that model? How does an employer trust the directory? How is the directory maintained and vetted? How is it not LinkedIn, in other words?
So it seems to me that the main reason why "true Scrum has never been tried" is that most companies never intended to actually try it. They just wanted the buzzword.

Scrum is actually a cultural change. The methodology is just the surface stuff, like the buzzword.

It also doesn't actually happen at the company level, unless the company is quite small. It happens at the group level. I just thought of this: The Scrum that can be named, is not the true Scrum.

"Practicing" Scrum by following dictums in a book is sort of like practicing marriage by following dictums in a book. Those are just guidelines, and the reality is at a deeper level.

EDIT: Come to think of it, that can also be interpreted as: Therefore Scrum is broken as a methodology. It cannot be "followed" at scale. (Much as communism is broken as an economic system.)
Direct link: https://rsadowski.de/posts/2024-01-14-openbsd-video-audio-sc...
Why would anyone ever voluntarily eat a whole grain rice onigiri?
Hopefully, the Go client will be helpful for Cloudcraft customers :)

This is my first time writing public code for such a big company, so I'm a bit anxious, but still proud of myself for what I accomplished.

For those not aware of Cloudcraft, it's a cloud architecture design tool that allows you to visually design and model cloud infrastructure, particularly for AWS and Azure. It provides a drag-and-drop interface for creating detailed cloud service diagrams and a nice API you can use for automation purposes.
Do I understand correctly that you're doing nine week sprints? That sounds extremely long to me. I have to think you're spending lots of time planning work that won't be done. When you plan a sprint, how often does the work at the end of the sprint actually get completed by end of sprint?

Say you plan to start the "add Foo button to Bar page" in week 7, do you actually do that? That would require some really strong estimation skills and a remarkably stable product and business environment. What's the point in the sprint where you're doing more unplanned work than planned? Or how much carry over work do you have?

Because if I was trying to plan nine weeks of work, I'd get it drastically wrong, and waste tons of time planning stuff we weren't gonna do.

I would make the next few sprints 4 week ones and plan to get down to 2 week sprints after the shorter pace starts to show it's strengths.

Or maybe you have 9 people doing 1 week sprints and that's how you got 45 days. In which case, whoops! I have no suggestions!
Really makes you wonder if they're even prepared to deal with modern adversaries such as drugs or terror.

(Edit: Let's put an '/s' here just to be safe...)
Edit: By “net negative” I’m speaking in context of the post and therefore to the perspective of the advertiser.
Eben Upton on Sinclair, Acorn, and the Raspberry Pi
you must be management, cuz

1. you think it's the sysadmin's fault

2. there are no competent sysadmins out there
SQLite 3.45 Released
You'd have to dual license your code afaik, the way Qt did/does it
Technically incorrect in nitpick ways but substantially the best intuition: the job of politicians and regulators rounds to: “match the growth of the money supply to people using skills to generate yet another round of speculative but self-fulfilling growth projections with the least amount of dumb rich kids having important jobs”.

To me at least, this sounds like a hard job in Athens with the Bundesbank pardon the ECB breathing down your neck, and a trivially easy job in Washington DC where you can physically destroy anyone who disagrees with your assertions about the value of anything.

Unfortunately the actual job has become: “maximize class solidarity at any cost up to and including arbitrary bloodshed”.
Sure, and I wouldn't want it any other way, or I'd just use Windows in the first place. That said, on Linux I still get error messages, not a big number – an actual message that tells me what didn't work so if googling that error message doesn't yield a solution, I can go ahead and try do fix the issue myself.

I still remember from the Windows days when you were unlucky enough to hit a more unusual error code, where googling it didn't immediately result in a dozen forum threads with people posting the same issue and then some dude replying with a fix where you don't even know how they possibly figured that out. If you didn't find a solution googling the error code it basically meant you can try random shit until you accidentally fix it, or reinstall. On Linux I could just ultimately look at the source code of whatever component is broken and track back from where the error is printed.
Absolutely. You can get squeezed by a potential buyer. You're exposing your books, and if the buyer is particularly shrewd, it can manifest a very unfavorable position, especially for small companies. They squeeze, back out, and come back in 6 months if you're still around. If you're looking to sell your company, you need to know this and set up milestones to mitigate this.
I'll share a take that comes from spending many years as a classroom teacher. Every classroom is a community. Regardless of your views on education, you have to do something to manage that community. If you do nothing, then the loudest voices will take over. The people with the loudest voices tend to drown out others, and their views and actions start to influence everyone else in a very unbalanced way. I've seen this play out in multiple classrooms, in every school I've been in, both as a teacher and as a student.

Every social media platform is a community, and often a collection of smaller communities as well. Moderation is hard, and doing it well costs money. Doing it well means losing many of the loudest users to other platforms that let them shout as loudly as they want.

Most platforms have given in to these loudest users, to the detriment of the communities they were starting to build. Some platforms have done this intentionally; some have fallen into these patterns because they're unwilling to do the hard work of moderation, or unable to figure out how to do it well at the scale they ultimately reach.

Anyone who enjoys the HN community more than some other social platforms should be aware of how much this community is actively moderated, by a small but very skilled moderation team. (I believe it's two people at the moment.)
The verb indigenize sounds very strange in the context.