skysight-inc/HackerNews huggingface dataset:
> Tech has become all Jobs and no Woz.

Because it's a lot more true than most tech people want to admit.

I am continuously amazed at how many brilliant people there are, that do fantastic things, that do not bring in anywhere near what their value is. Look no further than open source, there's people that write important software begging for scraps while flashy startups get showered with money if they yammer the right buzzwords.

There are certain people that don't want to hear this, but being a leader and visionary is, in practice, a more valuable asset than the cumulative technical skills.
Analogies are rarely perfect, that's why they are analogies. The OSI model isn't intended to be perfect and yeah there are a lot of details that leak between layers, but is also expected, any non-trivial abstraction is always going to be leaky. That doesn't mean it useless or absent of value in discussion at appropriate levels.
'In a more competitive market' sounds like an article of faith, akin to the No True Scotsman, where there's no definition of what is competitive enough until it meets the proponents' sniff test.

What would a sufficiently competitive market entail? Has it ever existed?

Would it look like modern US K-12 systems where commercial schools prioritize the most profitable students and leave the others to the public schools? Where good marketing beats good education?

How would it not be "heavily distorted" by impositions like Title 9 and other civil rights requirements? By government requirements on the school in order to receive state and federal money? By accreditation requirements?
Then colleges are concerned when they see enrollment at many majors keep shrinking, while the demand for computer science grows, even when the college doesn't even have a proper CompSci department, but they depend on the Math school.

Then the students wonder why it's a 4 year degree with a full year wroth of non-major classes that seem unrelated, but tack on tens of thousands to the cost of the degree, plus whatever on-campus housing and meal plan, mandatory for freshmen, might cost.
- One on Ones to discuss roadblocks and thoughts every week.

- Issue tracking as a common place to describe what needs to be done and thoughts / details on how it is solved. Something lightweight like Trello is ideal

- A Kanban board so people have an organised way to pick up new issues when low on work

- A weekly showoff meeting where there are few 5 minute presentations and a 30 minute "I did something really cool or learned something really cool"

- 6 month task split into 1 month ish deliverables, with a flexible deadline for each. Presentation of finished work each deliverable.
Comparing reactivity / signals libs in TypeScript
With the TC39 Signals Proposal reaching Stage 1, I wanted to do a deep-dive on the most popular reactive TS libs, benchmark them, and explore some of their design tradeoffs.
> People on the Internet won't like you calling it 'exactly once delivery' because it's not exactly once

That depends entirely on what you mean by "it".

Messages can get lost. So if you want guaranteed delivery, you sometimes have to re-transmit the same message, and so you might end up with the same message being delivered more than once. But it is trivial to put an abstraction layer on top of that to discard the duplicates and make it appear to the application as if every message is received exactly once.

The whole thing is a tempest in a teapot.
Any integer that is a sum of 2 cubes produces a solution. Since if x^3 + y^3 = z then we have (xz)^3 + (yz)^3 = z^4. So this doesn't seem super interesting?
Evolution of a manager and scrum team achieving high-performance together:

Team: "We are having trouble with Bob."
Manager: "Ok I'll talk to him."

Team:"We are having trouble with Bob."
Manager: "Don't come to me, you guys need to deal with that in your retro."

Team: "We voted Bob off the island."
Manager: 'Ok, I'll forward to HR."

Autonomous teams get more done because they have eliminated management as a wait state and will proactively scale with other autonomous teams to maximize the amount of work not done. 21st century managers need to re-focus on flow efficiencies (as business engineers), and not people. 20th century managers won't have a job in 5 years.
Distinguishing between malice and ineptitude at the systemic level is nearly impossible.

If the OP's type of comment makes you uncomfortable, you might be leaning too far into putting blame on ineptitude by default, instead of a healthy at least 50/50 mix of blaming greedy malice. OP just listed the 20/20 hindsight of this all. If that makes it sound like it was all a scheme, well - who knows - but it's just as unhelpful to always suppose such circumstances could have just been incompetence with no clear evidence.
> Agile, Scrum, Kanban, Method 1, or whatever are all meant to measure success.

In the agile teams I've been on it's been to produce success. Getting good and useful software fast.

Of course, just like there are hundreds of wildly different Christian sub-religions, there are now any number of "agile" interpretations. In the end belief systems can be pushed to do most anything you want.
They would be wondering why it took so long.
Are airbags required for driving in Germany?

If a German owns a 1961 BMW Isetta, is it required that it have airbags before it is driven on the roadway?
The post is fundamentally about all the performance of making stories, assigning points, allocating work and doing standups all the time. None of that is required to actually create software.

If people are judgemental around what stories are left uncompleted or points / week then the situation can become stressful for no benefit to anyone.
You will not own your digital life and be happy.
And:

ABC - Anti Bribery & Corruption

AML - Anti Money Laundering

CTF - Counter Terrorism Financing

FATF - Financial Action Task Force
Which was ultimately lobbied at such a low a number by the AMA, the primary organization representing doctors interests in congress. https://qz.com/1676207/the-us-is-on-the-verge-of-a-devastati...
I use WishKit for my iOS app to collect user feedback
> generally are not carrying a lot of weight

1000lbs is a lot of weight. Mail routes include package deliveries as well as mail and package pickups. Some business deliveries have large transactions every day.

> fairy local and lots of stop and starts.

Mail routes are not identical and there are plenty of rural USPS offices which deliver to the property.

> to at least get some hybrids in the mix.

Part of the point is to not have a mix to avoid all the attendant problems that creates.
Fair, cost and value are only loosely related. Trying to price based on cost always turns into a mess.
Sure thing, feel free to email me at this dev email:

h e l l o <at> p a p i l l o n s o f t w a r e <dot> d e v
Every post about "Scrum sucks" has comments about how you are doing agile wrong. I don't see any yet so as the devil's advocate:

You're supposed to have autonomous teams who put up their own tasks they want to complete in the sprint, and the sprint length can be more than 2 weeks if the team wants. And if it's tight to get the scrum's tasks done, that's supposed to be feedback to you and the team. You have autonomy in setting sprint goals, you can put less stuff on a sprint so you have the slack you're supposed to between sprints. Or spend more effort refining so you don't get surprises so often. (Or otherwise change things up in how you work)

If you don't have the autonomy and the continuous improvement in your work culture, it's not agile. Scrum is for agile and it doesn't work otherwise. If you do have autonomy you can switch to something else from scrum if you want.

Same goes for the "scrumfall" part of course but that's admitted in the text already.

(I do think scrum is overengineered for agile ideals, has failure modes like in the post, and in 95% of cases you should do something lighter than scrum)
> Those are the vehicles killing the planet!

That would be boats. Cars or trucks or even semis don't even rank.
Homemade a low-latency home security camera [video]
I've been using a Raspberry Pi as a live camera to monitor plants on my balcony for a while. A few months ago, a friend visited and noticed this little stuff. He mentioned how he’d love to try something similar since he doesn’t like uploading videos to cloud services, paying subscription fees, or relying on third-party providers. The subscription fee would be very high, especially if he wants to install multiple cameras around his house. So I do my best to begin integrating all the features into an easy-to-use app and design easy-to-follow steps for people (like him) without a tech background to try it out.

- Key Features
* Low-Latency Live Monitoring: Achieve extremely low-latency video streaming through WebRTC.
* Playback of Historical Footage: Easily view and download recorded videos.
* Simple Setup: Configure your Raspberry Pi camera through a user-friendly interface or QR code scanning.
* Privacy Protection: Ensure your data remains private with direct P2P connections and local storage without going through third-party servers.

Open-Source Support: The camera source code is fully open-source, allowing you to customize and extend functionality.

I originally ran the camera program on my Pi 4, but I knew we needed a more affordable option! So I tried it on a Pi Zero 2W which can also achieve less than a 1-second latency while recording video simultaneously at 1280x960, however, the temperature reached up to 80°C... The Pi 4 can easily handle more than 3 users watching p2p live broadcasts at the same time. The Pi Zero 2W has no problem with two viewers, but I started to worry that overheating might ruin it. I'm considering designing a metal case to help cool it down.

Since this project is based on WebRTC we can also watch via 5G mobile data. The total hardware for the Pi Zero set cost me about $30 buck! How long videos can be stored depends on the size of the USB disk you plug in. Currently, the playback can only be played after the download is completed. If I have time, I’ll implement mp4 on-demand through WebRTC.

Github: https://github.com/TzuHuanTai/RaspberryPi_WebRTC
We really should, if for no other reason than to silence those who think that every Linux/BSD box connected to a network is being rooted every 5 mins because they are written in C.

That's if they ever get around to bringing such a Rust-based OS up to enterprise level rather than spouting off about this belief on HN all day every day.
QLD Gov. promises to make 50¢ public transport permanent if re-elected
Great post, love the amount of thought that went into this! I look forward to keeping up with your posts.
Not to mention the flex fuel scheme that GM, Ford and Chrysler pulls. CAFE fuel mileage calculations permits ethanol compatible vehicles to assume that it will be driven 50% of the time using E85 ethanol. For the worst gas guzzlers, they add the additional ethanol hardware to get the “lower” fuel mileage. Hence you only see the flex fuel badge on big trucks and SUVs. And ironically, the flex fuel label is really a label that it’s a gas guzzler.
Apple confirms the iPhone 16 has 8GB of RAM
Because not enough people own really old cars for it to be worth worrying about. And as you note, and increased endangerment is generally to the owner.
The AUR makes either perfect sense or no sense depending on what you think it is. If you think it's an extra repo with more software, then it's a bit odd: Why no binaries? Why the antagonistic view of AUR helpers? Heck, why doesn't pacman just have an option to automatically use the AUR? Just add it as another repo next to extra. On the other hand, there's another viewpoint, where the AUR is what happens if you provide a free-form place for random users to post build scripts. Not packages, really, just "here's the commands I used to build this software on Arch". In that view, you're not expecting a streamlined experience, and binaries are a ridiculous idea; you grab someone's notes, read them over, and if they seem reasonable enough then you execute them (because the notes came in executable format). Or if they don't quite look right, you edit them into shape and then run them, and that's expected because this is just a way for a bunch of hackers to pass around suggested build steps.

And to be clear, I think the AUR certainly started as the second thing, but it's often viewed as the first, and maybe it even should be the first thing. But if you assume it came from the second option then all its design choices make sense.
mTLS support has been added for apps. Docs are at https://clace.io/docs/configuration/authentication/#client-c....

Release v0.7.5 has the change
I keep asking people in my department about using lean but zero interest so far.
There's truth to the ScrumFall design process which is inevitable for most development processes. It's not just that a tool needs to be marketed, but that it needs to be integrated with work from multiple teams and other processes. What ScrumFall does is provide some level of feedback prior to delivery. In the age of Waterfall, devs would develop until they said they were done, we'd get to delivery and UAT only to find that key features work differently than expected and continually extend the release date by months or years until it finally goes out the door more from frustration than actual completion. That stress level would be pegged at 10 for months until it was completed.
It looks... bizarre, like someone gave a box truck the lowrider treatment. And is that a hint of Chevy I see at the top of the grill, although it's based on a Ford?
In my experience, if the PM isn't part of it, the standup doesn't happen, because no one else cares that much. If someone gets stuck on something or needs help we just send a slack message, no need to wait for a fixed meeting.
Perhaps these groups could be regulated and insured by an even larger entity, perhaps even one with the authority to punish individuals and organizations for wrongdoing?
And how many VCs heavily invested in Crypto startups?
Progress is important. That's why you plan for large milestones. There is no need for micro-ticket-story level updates, tracking, and overhead.
What I dislike about SCRUM specifically is that if you're having a rough week at home, recovering from illness or you just have things to do outside of work, you can't really just have an easy week and make up for it later on. It's a kind of constant grind and we always have a way of "filling up" our sprint. If we don't meet our target, it always feels like a fail. I know it shouldn't feel like that but it's human nature.

Maybe having "easy" sprints would work?

There are benefits too, just that constant grind aspect is why I believe it's mostly a temporary endeavor. After 6-12 months most teams seem to just do something else then come back to it once a new manager joins.
Retros all too often focus on the last thing that happened and risk turning into a complaint session.

I've told my team anyone is welcome to ask for a retro whenever for any reason, but we don't make them recurring meetings because there is too much of a temptation to find something wrong to fill the time.
This is a rant that just agrees with my position

At no point does it actually contain any kind of coherency as a philosophy

This is some kind of vague paternalistic naturalism with no real foundational epistemology
jph00 helpfully quoted the paper's definition of hypermedia for us: https://news.ycombinator.com/item?id=41538587

> We find the "functional definition" at Definition 4.1: "A hypermedia control is an element that responds to an event trigger by issuing a type of request to a URL and placing the response at some position within the user agents viewport."

You said:

> Note that this definition doesn’t mention networks or protocols

Neither does the given definition of hypermedia controls in the paper. So it seems that your respective definitions are perfectly compatible.
The law of comparative advantage applies even to the states. It applies everywhere.
Graphite[1] has interesting plugin ecosystem like Grafana[2] & has been around since 2009. Architecture of Open Source Applications book[3] has done a nice overview of the architecture. I really like how it reuses linux filesystem as data store, making archiving very simple.

[1]: https://graphiteapp.org/
[2]: https://grafana.com/
[3]: https://aosabook.org/en/v1/graphite.html
That’s literally what I’m saying doesn’t exist, so we’re in agreement?
Out of the 8 companies I've worked at as a product engineer, the most successful framework to deliver tangible results has been Basecamp's Shape Up approach. Engineering managers always ask "how many days" of effort when the real question they should be asking is "how much appetite"/"how long do we want to spend" on the particular product/feature we want to build? The Shape Up framework was the only time I didn't feel constantly stressed and it actually provided time to cooldown between the six week cycles. And the fact is it actually led to very successful product deliveries consistently. For those interested here's a link to it https://basecamp.com/shapeup/0.3-chapter-01.
He tried gas powered, then due to backlash got the government to give $3B for electric.

“Environmentalists were outraged when DeJoy announced that 90% of the next-gen vehicles in the first order would be gas-powered. Lawsuits were filed demanding that the Postal Service further electrify its fleet of more than 200,000 vehicles to reduce tailpipe emissions.”

“He found a way to further boost the number of electric vehicles when he met with President Joe Biden’s top environmental adviser, John Podesta. That led to a deal in which the government provided $3 billion to the Postal Service, with part of it earmarked for electric charging stations.”
Why is biodiversity preferable to monoculture?
Aligators eat their own babies.

(I'll let myself out)

Edit: the fix could be to fill it under national security hazard(?)
I don't believe Uniqlo falls under the fast fashion umbrella though. It's practical clothing, yes. But young people rarely shop at Uniqlo to pickup a new skirt before going out on Friday night.

Uniqlo, at least in Japan, isn't the cheaper stuff either.
It shouldn't be too big of a deal to have an ice and an ev share a truck style vehicle, because there's going to be structural support for batteries and probably room for them too; possibly requiring a higher load floor, but depends on design, I guess. Sounds like the target EV range is 70 mi, so the battery pack won't be super large.

Ford makes the F-150 in ice, hybrid, phev, and full ev, I think.
Tabulating machines were developed by IBM’s predecessor for the 1890 census and used in various forms until evolving into punchcard computers.
Many engineering orgs just give lip service to scrum, which is as good as not doing it, which is good and works better. Meaning, in my experience: You work in a priority queue, that priority queue is re-synced with stakeholders (at least) once every two weeks, retros may be there as an opportunity to get other business verticals into the room to see what engineering finished recently, and the concept of "a ticket going over to the next sprint" doesn't raise blood pressure, because the system is designed for this and sprints aren't deadlines. Features might have deadlines, absolutely, but that's independent of the sprint.

I've worked at ~three places that operated similar to this; "minimum viable scrum" is a good name, or even better, "emergent scrum" because it isn't a process that's designed, its the process that emerges when someone toggles the "agile/scrum" button in Jira, but no one really cares one way or the other. Its a good process.

I've worked in one environment that was hard scrum, had scrum masters, extremely strict. To be honest: I felt almost no stress, but the company also delivered very little. There was a lot of "we can't get to swapping the color on that button until Sprint 18 in three months, but we'll schedule it for then". Missing a sprint was life or death, so every estimate got padded like crazy. When you took vacation, it was common knowledge that you needed to leave halfway through a sprint and come back halfway through another, sprint planning would basically forget about you. That (public tech) company doesn't exist anymore, and it radicalized me against agile/scrum: The entropic end-state of perfectly executed agile/scrum is an extremely well-lubricated machine that actually does very little.
cppreference is a Mediawiki site. It absolutely could be a better experience, but it's currently running an ancient version that makes things like responsiveness and theme improvements harder to pull off. https://en.cppreference.com/w/Special:Version
This is how gangs benefit the economy.
Tell that to a large PM organization. They love tracking minutia.
I got them through an in network hospital audiology department, so paid by health insurance. For out of pocket Costco looks good to me. They have special models that are a little less fancy than the top of the line stuff, from name brand manufacturers.

I also checked out earlens.com, a pretty cool concept that’s supposed to be superior in audio quality. But they are pricey, and need to be fitted by a doctor/audiologist with a transducer that sits directly on the eardrums (and stays in your ear canal) and is driven by induction. Ultimately turned off by cost ($12k/pair).

I think the technology in hearing aids has profited from the advances in chip manufacturing [1]. So the latest models may also be on 5nm and thus have more transistors for fancy AI and longer battery life. You may have a better experience nowadays.

[1] https://esg.tsmc.com/en-US/articles/106
My understanding is that the bought a majority-gas fleet with the budget he had, and as congress have him additional money for EV purchases, he adjusted increasingly towards EVs.

Also, 2021 was a long time ago. It was easy in 2021 to say "We're transitioning to EVs by 2030!" but it was not easy to actually buy $6B in working EV vans... they were all hypothetical. That changed, and so the USPS purchases did accordingly.
It's really disheartening. All those names the OP has mentioned, but we can't see them as X.com has X'ed them under password.

We need to look at some other service that is open to share our own identities without the login hell.

Does anyone know if such service is available?
Spring Boot allows you write application configuration in `application.properties` file and pull any variables used from environment. This replicates the same in Go, except it uses a yaml format and you can leave the value empty which you expect to be present in env.
It was a huge hit as a non-VR game first and only later got a VR version. It doesn't feel like a VR conversion, but it's mostly because it just happened to translate into VR really well, both gameplay- and story-wise (but also because VR version is more like a standalone sequel than a port).
Theoretically this would be a great opportunity for someone to take the EPA to court over this and have a chance of it actually having an effect, whereas before that was unimaginable. Of course it will require deep pockets, but a coalition of automakers could perhaps make it happen.
Unless of course you want to use your hard earned crypto to buy tangible things over the Internet.
I recently also wanted to play around with some itunes podcast data. But it seemed Apple removed the scrapable catalogue index of their podcast library. How did you build up your database, if i may ask?
Data says otherwise though.

Only three European countries are above the US in tertiary education rate: Ireland, UK and Luxembourg.

https://www.statista.com/statistics/1227287/share-of-people-...