MurphyA/hacker-news huggingface dataset:
by chrisfosterelli | 2026-01-24 22:38:21+00:00
Software engineering isn't some magical, special branch of engineering in which no one piece of software resembles another, no well-studied steps can be replicated, and the design of which is equivalent to rocket science.

If you're truly creating such unique and valuable software that it is to be compared to the world's engineering megaprojects in its challenge then perhaps it is beyond being beholden to a budget. Who am I to say?

But 99.9% of this industry isn't doing that and should probably be able to estimate their work.
by andy_xor_andrew | 2026-01-24 22:41:22+00:00
if I'm not mistaken (and I very well may be!) my primary confusion with closures comes from the fact that: the trait they implement (FnOnce / Fn / FnMut) depends entirely upon what happens inside the closure.

It will automatically implement the most general, relaxed version (FnMut I think?) and only restrict itself further to FnOnce and Fn based on what you do inside the closure.

So, it can be tricky to know what's going on, and making a code change can change the contract of the closure and therefore where and how it can be used.

(I invite rust experts to correct me if any of the above is mistaken - I always forget the order of precedence for FnOnce/Fn/FnMut and which implies which)
by fancyfredbot | 2026-01-24 22:41:58+00:00
Spotting fish who you can overcharge is not really a sustainable business model. You can do it once but your colleagues will find out, move to a competitor, and next time they'll rip them off a bit less than you did and you'll have to rip them off less than that.

There is, eventually, a shortage of dumb money. The sustainable way of making money involves competition, and this involves knowing the "right" price within a tight tolerance.
by crazygringo | 2026-01-24 22:42:18+00:00
I'm sure everyone has their own idiosyncratic interpretations, but I believe I've got enough experience to tell you that what I'm explaining is pretty standard.

Here are literally the top two Google results for "story points" and they both seem to align entirely with what I said:

https://www.atlassian.com/agile/project-management/estimatio...

https://www.mountaingoatsoftware.com/blog/what-are-story-poi...

I don't doubt that what you're describing as story points is something somebody told you. I'm just telling you that their definition was highly idiosyncratic and extremely non-standard. When discussing these things, using the standard definitions is helpful.
by trinix912 | 2026-01-24 22:42:53+00:00
The problem I have with names like BirdyChat is they're not easy to remember and even less easy to explain to someone whose first language isn't English. Like yeah, we know it's "Chat" and "Bird" combined and all but to a lot of people it's just "Bdytsch something". Compare that to Twitter which is relatively easy to pronounce and remember.

Forgejo is even worse in that regard. I live in Europe, speak 5 languages, and still have to think to remember the proper pronunciation every time.

It's much harder to get people on board with yet another messenger app when they forget the name 5 minutes later.
by tomaskafka | 2026-01-24 22:42:57+00:00
Awesome, let's look at this in privacy conscious browser:

> The link to this photo or video may be broken, or the post may have been
removed.
> [Visit Instagram]

Transcribed: "We probably deleted or misplaced documentation of that thing someone spent 21 years creating. We don't care - this way to feed of AI generated cat videos."
by evolve2k | 2026-01-24 22:43:13+00:00
Register and reserve the domain first.

You can hold it as yourself for as long as you need. No harm to having domains except a few dollars of annual cost.

It’s easy for another person to register it at any time, so grab it first.

The scenario of registering a company only to find that someone else bought the domain and you now need to pay them a chunk of money to get started is not where you want to be.
by snowchaser | 2026-01-24 22:44:38+00:00
As a PSA, the Google Workspace version of gmail doesn’t train on your data, if you like other gmail/workspace features.

(Workspace TOS is now part of the Cloud TOS https://workspace.google.com/terms/premier_terms/)

Section 12.11 of the Workspace specific terms confirms that Google will not train on customer data(which Gmail emails in workspace are). Incidentally, this is where Generative prompts and responses submitted or created via GA versions of Gemini in workspace are identified as “Customer Data”, which is not used for training. https://workspace.google.com/terms/service-terms/
by ratrace | 2026-01-24 22:44:56+00:00
AI Overview

"ND'd" is jargon for a Negligent Discharge, referring to a firearm that fires unintentionally due to operator error, lack of attention, or failure to follow safety procedures, such as violating the rule of keeping one's finger off the trigger until ready to shoot. It is often distinguished from an "AD" (Accidental Discharge), which refers to a mechanical failure.
by toonalfrink | 2026-01-24 22:45:18+00:00
I don't like it.

We should be divesting from unethical businesses, not from american ones.

Nationalism can be so seductive but if you engage in it you're being pulled down to "their" level.

Instead, consider your true "country" is the set of good people, no matter where they live. Keep spending your money on ethical american businesses, and european ones, and russian and chinese ones, if you can find them. Stop spending your money on unethical businesses, even if they're local.
by crazygringo | 2026-01-24 22:45:41+00:00
> For the first one, you CANNOT use what you just described, since it doesn't represent time, so you cannot give dates in any form.

That's the purpose of story points and planning poker. They don't represent time guarantees or delivery dates. That's not a bug, it's a feature.

They represent estimated effort, with a recognition that uncertainty is generally roughly proportional to size. Which is why point estimates are usually restricted to approximately Fibonnaci sequences values (or sometimes doubling). Often it will be limited to 1, 2, 3, 5, 8, 13, 20, where stories aren't allowed to be larger than 20 -- if they are, you need to break them apart.

So to be clear, when you say that estimates are composed of two parts -- time and risk -- planning poker intentionally conflates them into a single number. If a task is both large and truly high-risk, then it should be broken into a research story and an implementation story, where the size of the research story can be better estimated, and then implementation waits for the next sprint depending on what research tells us. If it's small and high-risk, then you basically just "try", and accept that it might not get delivered, and then revisit in the next sprint whether it's worth trying again and if it needs to be revised.
by Nextgrid | 2026-01-24 22:46:26+00:00
> maybe it's also our fault and we can do better?

Part of it is absolutely our fault; part of it is the industry.

In the electronics world, when you need <common functionality>, you can find an off-the-shelf part that fits your requirements, fit that part in and it'll work. When you need logic in a hardware device, nobody's rolling their own CPU from discrete parts - they just take the cheapest microcontroller fitting the requirements.

In the software world we don't seem to have this concept of building blocks for common functionality even decades into the industry. Most software projects are some flavor of CRUD app with custom logic operating on the CRUDed objects. You'd think all the complexity would be in the custom logic, but actually it's at best 50-50 and at worst most of the complexity is in the whole CRUD bullshit and not what happens to the object once it's CRUD'ed.

How come in 2026 there's still no way to have an off-the-shelf component I can buy to do "I have a table of objects on the server, and I want to expose this as a UI to the client"? Why do I still see people writing this by hand in React/$JS-framework-of-the-day and messing around with things like OpenAPI and/or writing serializers/deserializers by hand? I swear most of the work I see in the web development space is the minutia between client/server communication.

I think there are several reasons:

* overengineering/resume-driven-development: even if there was to be an off-the-shelf component to do the task, people would probably avoid it and prefer to bullshit around reimplementing a (worse) solution. That's already the case where people are using React/SPAs/etc for views that do no need any interactivity and could just be an HTML form.

* political choices influencing tech selection: more often than not some tech or service provider is selected based on political reasons and not technical, and then the engineering challenge becomes as to how to shoehorn this ill-fitting part into our solution.

* aversion to paid software: hardware engineers are expected and allowed to select parts that cost money. I've never been on a software project where we had an explicit budget for licensing software. Reaching for paid software became the least resort option I'd have to fight for and burn political points, while spending 10x the cost building a (shittier) replica in-house was considered fine.

Due to the last point there's also little incentive for software providers to build and sell such components, so the market is quite small and not competitive, with the (very few) competitors having their own dealbreakers. Firebase will give you the instant database and UI, but then you're forever tied to paying them rent. You can't just license the server component and install it in-house like you can buy an FPGA.
by mtalantikite | 2026-01-24 22:46:45+00:00
Agreed, I'm constantly coming back to a Claude tmux pane just to see it's decided to do something completely ridiculous. Just the other day I was having it add some test coverage stats to CI runs and when I came back it was basically trying to reinvent Istanbul in a bash script because the nyc tool wasn't installed in CI. I had to interrupt it and say "uh, just install nyc?". I was "Absolutely right!".
by threethirtytwo | 2026-01-24 22:46:52+00:00
>Jesus Christ, dude. Just because someone works with their hands doesn't mean they're stupid. Good lord. Working in a professional kitchen is an incredibly demanding and difficult job. Don't be elitist to people who work way harder than you.

You're making a personal comment. It's orthoganol to the point. You said cooks learn the chemistry, he says they don't and they are too stupid too.

As bad as that statement is, it's true. Culinary arts as an occupation has statistically lower IQ than many other occupations. Additionally they don't actually learn the chemistry. You sidetracked off on a tirade talking about someones "elitest" character... but if you stick to the point, what you said was completely and utterly wrong.

>Funny story, I'm evaluating SaaS ETL products and I found one that looked great. So I spent a couple hours testing out some tinkertoy examples with the idea to ask for budget if it worked.

You know Ryan Dahl? Inventor of NodeJS, likely smarter, more successful, and a better coder than you says this: https://x.com/rough__sea/status/2013280952370573666

So you have a funny story, and then there are other smarter competent people saying the EXACT opposite of you. Does that ever make you pause and think? We've all seen evidence of AI fucking up. AI being stupid is a story so obvious that even the proponents of AI know AI can fuck up big time. But have you ever wondered what would make Ryan Dahl say something like that? Does what I'm saying even compute or are you just so stubbornly sure that your "funny story" invalidates everything?
by sbierwagen | 2026-01-24 22:47:22+00:00
>The drag coefficient was the headline: 12% better than our design target.

Is the drag much better than a regular cubesat? It doesn't look tremendously aerodynamic. From the description I was kind of expecting a design that minimized frontal area.

>Additional surface treatments will improve drag coefficient further.

Is surface drag that much of a contributor at orbital velocity?
by jbullock35 | 2026-01-24 22:47:42+00:00
I've watched four videos but haven't seen any footage (clear or otherwise) of gun removal. Can you post a link to clear footage of the removal?

One video [1] shows someone walking away from the scene with a gun a fraction of a second before the shooting begins. But I can't see that the gun was removed from the protester.

[1] https://www.reddit.com/r/law/comments/1qlvpbr/footage_of_the...
by wildylion | 2026-01-24 22:48:15+00:00
I'm so afraid that my landlord (a big company) will use ANY excuse to rob me of my deposit when I move out... lol, even though I'm a member of Mieterverein.

The same landlord whose workers outright forgot to install the water heater in the kitchen the day I got the flat, and __painted shut__ the bathroom window. LMAO.

Though I can only second this -- use transparent fiber and be creative in where you route it -- and nobody will be able to tell you did something 'naughty' in your rental.
by ssl-3 | 2026-01-24 22:48:43+00:00
Sure, the plan you outline does sound very simple. And in an ideal world, that'd be perfectly fine.

Except we don't live in an ideal world.

See, for example, the fuckery alluded to above.

Therein: Linking a Microsoft account to a Windows login is something that appears to happen automatically under some circumstances, and then bitlocker keys are also automatically leaked to the mothership...

The machine is quite clearly designed with the intent that it behaves as a trap. Do you trust it?
by idibiks | 2026-01-24 22:48:46+00:00
My dude, they were already beating him for no reason whatsoever. When someone showed me this video the first time, I thought the outrage was that they were beating a guy who wasn’t resisting for no reason whatsoever, which is true, but then they also killed him, again for no reason. They were already violent criminals before they murdered him. If he had been drawing it would have been justifiable self defense and ICE would still have been entirely in the wrong. Though he didn’t.
by threecheese | 2026-01-24 22:49:40+00:00
Did they release this already? With version 2.1.9 the behavior is vastly different, all of a sudden the main loop is orchestrating subagents in a way I’ve not seen before.

“FTSChunkManager agent is still running but making good progress, let’s wait a bit more for it to complete” (it’s implementing hybrid search) plus a bunch of stack traces and json output.
by doubled112 | 2026-01-24 22:49:53+00:00
It works with most real companies. If you signed up for it, you can generally unsubscribe from it. It’s easy to do by mistake, and some default to yes with no option during sign up.

I don’t care about whatever new shows Netflix has. Unsubscribe.

I don’t care about my DNS registrar having a sale. Unsubscribe.
by B1FIDO | 2026-01-24 22:50:17+00:00
I've got a crazy bizarre idea. Why don't you contact Amazon customer service and ask them about it?

You can describe the cards and give them the numbers and then tell them why you believe they've been tampered.

I mean it's totally illogical, right?

When I was accused of possessing counterfeit money, I went right to my bank and showed the bills to them (they were, of course, authentic).
by dekhn | 2026-01-24 22:51:33+00:00
The statement you say was O'Hara was made by McLaughlin (DHS employee). If the article implies otherwise, it's incorrect.

Here's the facts as I see them:
A protestor who had a gun he was legally allowed to carry got involved in an incident with ICE/Border Patrol. The protestor was interacting with the agents and other protestors, at which point BP or ICE pepper sprayed him and took him down to the ground. At least 4 different federal officers were physically holding him. at this point it appears they disarmed him (unclear) and then shortly after, shot him.

At no point did the protestor hold the gun in a threatening way while approaching, when he was taken down he did not have a gun in his hands, and while down, it's very unlikely he could access the gun and use it in a way that any reasonable officer would feel unsafe and be required to shoot the protestor.

Based on the videos I've watched, the protestor made some ill-advised choices getting physically involved, but there was no reason for him to be shot. I read various online conservative communities (to try to understand their reasoning) and nearly all the posts I see seem to think that ICE/BP truly made an error here, possibly due to poor training.

I understand your point about the use of emotional terms, I try to avoid them and instead focus on facts and known unknowns, but in this particular situation, it's pretty clear that ICE/BP made an egregious error in a way that is clearly obvious to everybody (even those who would normally support the federal officers) and in denying this, the federal leadership is undermining itself. This is a situation where they could de-escalate and not immediately blame the protestor, while focusing on increasing the training of the ICE/BP officers, rather than taking an aggresive posture.
by theptip | 2026-01-24 22:52:17+00:00
I think both can be true, no?

Multi-agent coordination is obviously what's next.

And, Gas Town itself might never amount to more than a proof-of-concept.

Personally I'd put my money on whatever Anthropic build to do this job, rather than a layer someone else builds atop CC.

Remember when code LLMs were just APIs, and folks were building their own coding scaffolds like Aider and Cursor? Then Claude Code steamrolled everyone; they win because they can do RL on the whole agentic scaffold.

Any multi-agent system will have the same properties, i.e. whatever traits (e.g. the GUPP) and tool expertise (e.g. using Beads) are required to effectively participate in a swarm will get RL'd into the coding model, and any attempts to build alternate scaffolds will hit impedance mismatches because they do not fit the shape of what was RL'd (just like using non-CC UIs with Anthropic models gives you worse results than using the CC UI).

I say this with love - Yegge is putting forth some excellent ideas here. Beads seems like a great concept to add to CC ASAP; storing the TODO state in a repo would mean we don't need MCPs onto issue trackers. And figuring out what orchestration concepts are required will need a lot more trial and error, but these existence proofs are moving the frontier forward.
by nomel | 2026-01-24 22:52:23+00:00
Please note, a question does not imply an opinion.

Could you provide a reference for them not being federal law enforcement officers (specifically immigration law)?

I've seen this mentioned several times, but can only find evidence that they are. For example Cornel Law [1]:

> The U.S. Immigration and Customs Enforcement (ICE) is a federal law enforcement agency under the Department of Homeland Security (DHS).

> CE’s primary mission is to promote homeland security and public safety through criminal and civil enforcement of federal laws governing border control, customs, trade, and immigration.

And USC 1357 seems to make this indisputable [2], but IANAL.

All the sources I could find that say they aren't law enforcement are questionable, and aren't related to interpreting law.

[1] https://www.law.cornell.edu/wex/immigration_and_customs_enfo...

[2] https://uscode.house.gov/view.xhtml?req=(title:8%20section:1...
by notaurus | 2026-01-24 22:53:21+00:00
How did you manage meaningful attitude control with only torque rods? They would need to big (read: heavy) to be useful — was this just stabilising in inertial frame or active pointing?
Mag dipoles in chassis and components tend to lock tumbling satellites into the Earth’s magnetic field. Did you see this? Or did you see atmospheric drag dominate at this altitude?
by jbullock35 | 2026-01-24 22:53:23+00:00
Thanks. I watched the videos. It's a horrific event. But I can't see that either of the videos shows a gun being removed from a protester. At the end of [2], someone does seem to walk away from the scene holding a gun, just a fraction of a second before the shooting begins. But I can't see any point at which a gun is removed from a protester.
by metalman | 2026-01-24 22:53:39+00:00
it looks like Toppher Haddad has two writing styles, the tech bro blog , and the style he used above to discuss the technical aspects of there optical technolgy, and that is high geek, high uber geek of the type generaly associated with an inability to comprehend others lack of incomprehension, so actualy an unusual integration of skills and aproaches
by zmj | 2026-01-24 22:53:42+00:00
I was prepared to disagree with the thesis that estimation is impossible. I've had a decent record at predicting a project timeline that actually tracked with the actual development. I agree with the idea that most of the work is unknown, but it's bounded uncertainty: you can still assert "this blank space on the map is big enough to hold a wyvern, but not an adult dragon" and plan accordingly.

But the author's assessment of the role that estimates play in an organization also rings true. I've seen teams compare their estimates against their capacity, report that they can't do all this work; priorities and expected timelines don't change. Teams find a way to deliver through some combination of cutting scope or cutting corners.

The results are consistent with the author's estimation process - what's delivered is sized to fit the deadline. A better thesis might have been "estimates are useless"?
by turdprincess | 2026-01-24 22:53:47+00:00
Same - my new team doesn’t do any scrum or story points and it’s an amazing breath of fresh air - don’t miss those days just yelling random numbers at the zoom call for hours.

The truth is on most teams one or two people who are closest to the task have enough context to estimate, and probably only after they spent some time starting or prototyping the task.

Those people can give a reasonable estimate, in time not some strange point system.

Sometimes the estimate is wrong and that’s ok.

It’s fine to have a meeting catching everyone else up on the context but those pther people still likely don’t have enough to give an accurate estimate and shouldn’t be involved in estimation
by Zak | 2026-01-24 22:54:27+00:00
I am not assuming the FBI doesn't investigate random people. I am, however assuming that the FBI does not randomly seize computers and obtain court orders demanding encryption keys for them from Microsoft. Unless Microsoft is lying, that happens about 20 times a year.

One of the privacy protections is simply that it's a lot of work to go through that process. The FBI wouldn't have the resources to do it to everyone it's merely curious about even if it had the authority, which it doesn't because warrants require probable cause.

I believe that it's generally acceptable that when law enforcement has probable cause for a search warrant, third parties grant them what access they reasonably can. I also believe people who actually want to protect their privacy and security should learn fundamentals like whoever has the key can unlock it and if nobody has the key, it's gone forever. If I was building a consumer product, I'd have to care quite a bit about the fact that many people won't do that, but I'm not so I don't.
by fpoling | 2026-01-24 22:54:52+00:00
I lived in a building in Norway that had phone lines from like 1924. As it was declared as historic it was very difficult to dig newer cables. So ISP tried to use the old cables. At best one can get 10 MBit/s with a lot of packet loss. Eventually everyone switched to mobile internet. With 5g and stationary antenna it was possible to get 300 MBit/s with no packet loss and sub 10ms ping to local servers.
by pandaman | 2026-01-24 22:55:06+00:00
>That might be true where you live, but it's hardly a universal constant.

I have not said it's a universal constant, it's true in the US, where we use miles. ~1 hour per 100km is not as easy.

I cannot say I care much if you are doubtful, especially if you live in Germany and not in the US, I doubt many people in the US will care about your doubts too.