skysight-inc/HackerNews huggingface dataset:
I assume because it’s faster, easier, and requires less expertise to get started with a Visual Programming Language (VPL). This is why people use Scratch to introduce kids to programming, so maybe it makes for humanities students? But people have certainly been using VPLs for a long time for web site generators, for business automation, CRUD apps, point-of-sale systems, etc. There are lots of different goals people talk about with VPLs, including simplifying maintenance, limiting technical debt and over-engineering, having the ability to hire and employ people who have non-CS expertise, or just don’t have a CS degree, reducing training time, etc.

What do you mean by “insistence”, are you referring to this article or the broader ongoing existence of visual programming languages?
In a word, they are part of the HN "family".
I think that's a plausible start at a definition, but I think the ship has sailed on the term having a real definition at all.

Once marketers get hold of a term, it doesn't really matter what people who like definitions or precision think. As an example, I was active in the Agile movement before that term was coined. When I've talked recently with the early-days people I keep in touch with, we're all kinda horrified by what the term has come to mean. And it's not like we didn't fight along the way for clarity. But most people just don't care about the precise use of a term when there's a profitable (mis)use of the term.
Tesla's Dojo super: a $billion bet to make AI better at driving than humans
You might end up coincidentally liking some parts of these software design methodologies like Kanban, but they generally aren't intentionally implemented to maximize developer happiness. For me, even the name "sprint" just instantly pressures me to feel rushed in my work and I hate everything about this religion.

These methodologies are designed to be a "good enough" default way for non-technical managers to organize and manage projects in a domain they don't really understand.

Imagine how confusing going to the mechanic is when you don't really understand cars. You're constantly left wondering if he's bull-shitting you about the cost and effort involved in a repair and if any progress is being made and work is actually being performed. So I get why this needs to exist, but I understand that it's not about benefiting the developer.
I'm afraid I didn't find the writing "elegant"; I found it overly flowery. But then she let on that she's a poet. I don't enjoy poetry much, but some people do, so I decided to let it pass. Until I saw your comment...
It turned out that my contrast was the answer. Sorry about that.
Why would banks adopt FedNow when it will ultimately eat into their revenue from card interchange?
Most comics don't actually use Comic Sans.
That makes it even more subjective!! What's your definition of engineering?
Ooh, hadn't seen @disable before, super useful to know! That'll be handy for doing toggleable build options for tracing / debugging.

I've been using Odin for about a year now, many of the pain-points I've had have just been knowledge gaps. Odin's docs and debug info have slowly gotten better over time, and little discord-community tips here and there have made a huge difference for my quality of life.
Just lipstick on a pig.

Same ol', same ol'.
>certain uplifting current' is just activation of a neural pleasure center

What is the difference between these two things from a purely physical point of view?
Most of the dedicated Pong-style game consoles used a chip (or chipset) designed for a specific set of related games.[1]

The Wikipedia photo of the TV Master[2] is a great example of switches that correspond to most of the pins on the AY-3-8500.

[1] http://pong-story.com/gi.htm
[2] https://en.wikipedia.org/wiki/File:Binatone_TV_Master_Mk_IV....
> stop reusing bottled water bottles

Can you elaborate? Like is it somehow worse to buy a bottle of water and refill it periodically over the course of a year, than to let the original contents sit in my house for a year and then drink it? If so, I'm guessing the extra handling (squishing, crunching) is the main culprit? Or does leeching occur more readily when the contents are refreshed, as opposed to static contents that already reached equilibrium? Or is the pH (or other characteristics) of the original contents less likely to cause leeching than arbitrary contents?
The probability of a single whistleblower emerging increases (at least) linearly with the number of people involved. This problem doesn’t exist at all when working toward a real objective.
Capital 'A' Agile has become a total anti-pattern, and the most revealing signs of this are the two-week sprint, excessive meetings, and lack of technical leadership.

By far the most productive teams I've worked with have been on six week iterations, with an at least approximate idea of what they're supposed to achieve in the next 90 days. One week out of that six is basically given over to demo, retro, and working out what the next one should achieve, but there is enough slack in there to accommodate the inevitable ups and downs, which two week Agile/Scrum pretends is not a thing. The lead developer is almost entirely focused on integrating the work of the others, and building strategy for the next iteration with product/marketing and the other team leads.

The other incredible tendency of highly productive teams is a lack of communication . . . because they don't need it. It may be more accurate to class this as a lack of noise, and clarity over what needs delivering. (i.e. product and the leads have done their job). I used to have to visit different teams in many locations, and you could tell how productive they were just by how quiet it was, interrupted only with the occasional "Dave, you broke the build!"
The big banks were pretty stable in this last go around, and systemically it never really felt like there was much risk? So maybe some things are working?
Ooh, it turns out SBF gave them to the NYT. NYT forgot to mention that.

https://www.wsj.com/articles/sam-bankman-fried-accused-of-tr...

https://storage.courtlistener.com/recap/gov.uscourts.nysd.59...

The Government writes regarding the defendant’s recent extrajudicial statements and attempt to interfere with a fair trial by an impartial jury. Specifically, the defendant has sought to publicly discredit a government witness by sharing her personal writings with a reporter so that these private documents would be featured in a New York Times article published today. As such efforts have the potential to taint the jury pool, and could have a chilling effect on witnesses, the Government respectfully requests an order that limits extrajudicial statements by parties and witnesses likely to interfere with a fair trial by an impartial jury.
Yeah, a sprint is an artificial deadline, which is just wrong, IMHO.

That said a 1 or 2 week deadline is much better than the 6 or 12 month deadlines you easily get otherwise. If management needs to have deadlines, shorter ones are less damaging.
Is there any reason to believe that fasting could prevent dementia?
Manage Go Tools with Go
Blog Writing for Developers
Behind the Hype: A Deep Dive into the AI Value Chain
Non so cosa vuol dire struggling e cosa sia questa cosa. Vorrei sapere perche non inventi un telefonino diverso anti stress solo con sms e telefonate senza app.e un po diverso dagli altri e che ogni modello sia unico per via del design particolare, non costoso e creativo, per qu3lle poche persone come me che vogliono avere piu pace ecc.
Only shorterm. No longterm
Maybe I'll get restricted someday!
Now this may be a bias that comes from running on a track team, but I've always been annoyed when my team ends one "sprint" on a Wednesday at noon and starts the next "sprint" at 12:01. We're "sprinting" non-stop. They really should call them "marathons" or something that more accurately captures what the bosses want.

I believe the original idea was that there would be plenty of downtime where the team would study the problem and think about the best way to attack it. Then when there was a solid plan, the team would sprint to execute it before returning to thinking carefully about the next issue.
How do you get an AS?
NPM audit is largely useless[0]. Most people don’t care that the CSS minifier can cause an out-of-memory when fed a bad class name, because that step happens during the build process and not with untrusted code. There isn’t a way to isolate only issues that can be exploited in the production code.

[0]: https://overreacted.io/npm-audit-broken-by-design/
Yes, agreed. It has just been given a special name (sprint planning) to justify the cost of Agile consultants.
I'm sure the 200 billionaire wives cosplaying Natural Living will appreciate it.
They asked if I was going to let the cat outside. At the time we had another cat we adopted from a vet and we let it outside so it made sense that we'd let this one out too. That was a hard no (although they didn't tell you that). It was basically a trick question and if you didn't answer to their liking, they rejected you. That was 20 years ago. Nowadays the cat I do have is kept indoors at all times.
I like the idea of sprints as a simple “here’s my goal this week” sort of thing. Much more structure than that and it feels oppressive, less than that and it feels amorphous beyond the goals of a day.
> Yeah; I get suspicious about these outrage flareups that are conveniently vague about what actually happened

This is just the latest event in a longer controversy.

IIRC, this is the "is the juice worth the squeeze" lady. When one law student group invited a judge to speak that other law students disagreed with, those other students prevented him from speaking through persistent heckling. In the middle of it, this dean got up a person of authority to "calm" the situation, but validated the hecklers instead.

The whole event cause a lot of discussion about the "heckler's veto" universities and students becoming ideologically closed-minded and unable to even tolerate views and people outside a narrow orthodoxy, etc.

One particularly interesting observation was: we're talking about law students here, whose future job will require them to be able to make arguments compelling to judges they may disagree with, and that requires them to be able to engage constructively with ideas and people the disagree with. If the law school tolerates this kind of heckling behavior, it's doing a disservice to its students and their future clients.
This objection reminds me of those to AOP. With great power comes great responsibility. The increased efficiency means you can make the greater investment when it's appropriate and avoid far greater expenditures. Also, tools like Eclipse's XRef view become required.
Btw, "conventional beauty" is effectively an underhanded slur rooted in the envy of the "are-nots" toward the "ares". "Unrealistic" functions similarly, as there are plenty of women with the body proportions depicted in the handful of images I managed to see quickly perusing this page, and so while they may be uncommon (made, shall we say, more conspicuous in an age where obesity has skyrocketed and slovenly dress is ubiquitous), they cannot be unrealistic as such women do exist and do, in fact, dwell among us as fellow human beings. (N.b., some of the women depicted are entirely average or vulgar, and the manner in which some women are 'depicted' is also deficient in taste.)

And as this is effectively an artistic depiction, it would not be unreasonable to expect some idealization (no wrinkles, no blemishes, etc), which is kind of the whole point, as art, at least fine art, as it is produced to contemplate and enjoy beauty (which is, pace the relativists, objective; subjective tastes may conform to greater or lesser degrees to the objective fact). Even when you get your photograph taken, don't you want your "good side" photographed, or the zit on your forehead concealed?
What is the difference between .so and .so.1 files?
It's the job of an expert to communicate their understanding of the world in a way that motivates non experts to make the correct the decision. If an expert isn't successful in this, they need to improve their methods of communication. Everything else is an excuse.
You can only learn a lesson by feeling the pain of not having learned it before in your own skin
> “there’s no way it has to be like this.”

It really doesn't, but alas: worship at the altar of unnecessary cloud complexity or be cast out to the on-prem Elysian field.
At one company, we did do sprints, including retro and burn rates and all that, and none of the devs liked it. Bloody story point poker was a biweekly low-point. Where I am now, we work with a mid-to-long term goal, split up in limited tasks and sub-tasks to reach that goal, testing task by task, and deploying whenever it's ready. That works much better for me. But it's a small team, so that may help.

> Interruptions and unforeseen tasks will occur.

That's certainly the case in my current job. Since the product is used for commercial projects, bugs and smaller problems crop up and need to be addressed, usually with priority. And my colleagues regularly need support because they messed something up. It takes a lot of time to make a product fool-proof, and it's nearly impossible to plan.

So I'm in favor of incremental tasks in a larger design. Setting artificial goals and deadlines, which often won't be met, is only a source of frustration, not progress. But getting a larger design done in this way really requires that one person has the oversight.
Bizarrely I didn't... even consider the possibility of that, haha.

I'd even gone as far as considering getting a decent digital camera, considering that my current camera is my phone.
> The creation of artificial deadlines leading to overtime, burnout, and, eventually, high staff turnover.

> Inability to handle reality. Interruptions and unforeseen tasks will occur. The database may malfunction, revealing an architectural issue requiring immediate attention.

These both ring very true in my ear based on 3 years of agile dev at FAANG, less so from the 1 year at a startup. Neither were issues at the other FAANG company I’ve worked for, where devs were given more independence and trusted to deliver when they could.

I think sprints are a useful tool when you’re trying to hit tight deadlines with a group of devs working in parallel. However, I’m not a fan in general.
This is only a guideline, don’t treat it like a hard rule. There could easily be good reasons why a 2 point story took three weeks.

Also gotta stop the negative bias. People will want to complain easily if your 2 point story takes you three weeks, but no one will be singing praises if your 5 or 8 point story is done in a day.
I've spent most of my career in Infrastructure and I've found that sprints are a great way to keep a software team focused. A big temptation in infra is to take on a lot of things at once but move at a snail's pace on all of them. Even (and sometimes especially) very talented senior developers fall into this trap b/c in infra at a medium-large company customers are always screaming and everything is always "urgent." Sprints force defining tasks clearly enough to scope them and limit work in progress. Kanban can be effective at this also but any time I've been on a team that uses pure Kanban people always end up with 5+ tasks in progress for weeks.

The most important part of making it work is to have the team manage the process instead of some external scrum master, and to have frequent retros and adjust the process as needed.
Dorstone Hill: A Neolithic Timescape
My assumption was that if you're not performing sprints, you're not assigning points to stories either.

I don't know why I made that assumption.
The other commenter was correct - I meant a droplet. Should have been more explicit, apologies. But yeah if you're looking to learn how to work with backends, going through a droplet set up is by far the best way to get started IMO.
I've worked agile for quite some years now. Please repeat after me:

1. The sprint goal is not a contract. The mental and physical well being of the developers always takes precedence over the sprint goal. The sprint goal is merely a guidance.

2. Not completing all stories at the end of the sprint should not make you feel bad. A sprint is always filled using estimates which never will be correct, and are often way to ambitious and not considering severe issues.

3. Retrospective meetings should primarily allow developers to say how they could work better. It's not an occasion for the the product owner or the Scrum Master to belittle developers for mistakes and missed goals.
I haven’t! I love that there are 3rd party solutions for these things, but the base experience should be better.
Oh yes, way too familiar situation... dry cryostats were really a game changer. Apart of the incredible advantage of not having to refill them frequently and on Sunday, they are much more reliable and without any cold seal
> Notion doesn't know that a person is a person and a company is a company. That makes it impossible for them to build robust integrations CRM have. You can build rules to replicate some behavior, but once you have more business logic, it becomes too limited.

I literally have a 'person' database and a 'company' database.

But yeah fo sho, it will get limiting if i make this much more complex lol
Moderators' expectations were already rock bottom as Reddit had failed to deliver the tools it promised a decade ago.

Moderators who haven't left already will more than likely stick around for the long haul, so there's no real rush on Reddit's side anymore (again). We're back to the status quo, except now without third-party apps.

I don't approve of it, but it is what it is.
> Why would a company shadow ban you for asking an innocuous question?

If you are literally overwhelmed with crises, it becomes appealing to make problems go away in this manner. Not saying they are, but this thread is suggesting that.
It seems to me like there's room for improving your customers' awareness around what is required for HA and how to tell when they are affected by a hardware issue. On the other hand, it may just be that the confusion is mostly amongst the casual onlookers, in which case you have my sympathies!
(Fly.io employee here)

To clarify, we communicated this incident to the personalized status page [1] of all affected customers within 30 minutes of this single host going down, and resolved the incident on the status page once it was resolved ~47h later. Here's the timeline (UTC):

- 2023-07-17 16:19 - host goes down

- 2023-07-17 16:49 - issue posted to personalized status page

- 2023-07-19 15:00 - host is fixed

- 2023-07-19 15:17 - issue marked resolved on status page

[1] https://community.fly.io/t/new-status-page/11398
How might this interact with the APOE4 genotype?
you're behind schedule on your food hipsterism. american cheese has passed through the unironically bad phase, the ironically bad phase, and ironically good phase, and is now back to unironically good.
Calling them "sprints" comes close to directly contradicting the Agile principle about a sustainable pace and not burning out the team. I'm sure I not a true Scrum Scotsman about that. But Scrum jargon gets consumed by management above the project team and misinterpreted.

Start by calling iterative cycles, or even individual cycles of task completion if you are not all "sprinting" together, "iterations." Get rid of as much jargon as you can. Then everyone, inside and outside your Agile world will understand what you are talking about.

Ron Jeffries calls what you are getting at "Manifesto Agile" which label unfortunately never gathered much momentum, but it's a good idea.
Perhaps an "/epicfail/recent" gallery is also needed. Show the images that are horribly wrong. No porn please.
Hi OP here. Thank you so much for everyone who's taking the time to give feedback. You have all given me lots of things to think about, and to improve on, I can't thank you all enough!

It's getting late here in Australia so I'm going to have to call it a night. I'll respond to the comments I haven't responded to over the weekend.

And I will for sure add some screenshots to the landing page, as many of you have suggested.

EDIT: Updated the landing page with some screenshots. Will try to perfect it more over the weekend...
That is like a gorilla grunting that humans are weak and will die after it hits us with its fist. Which is to say, that is completely true. But if you're up against an opponent who is smarter than you it might never come down to a fistfight.

Every big gorilla on the planet could kill me. None of them can outcompete me for something, because I'm not stupid enough to challenge a big gorilla to a fistfight. There won't be a fight until after I've got my hands on a gun and the gorilla is an easy shot. There probably won't need to be a fight because I'll just trade for what I want using tactics that a gorilla cannot comprehend the effectiveness of.

There is a pretty good chance humans won't even realise they are competing with an AI until they are locked out from having options. I'm not even sure if most gorillas realise to this day that we humans will crush them if they ever try anything that threatens us.
No. Agile is for companies to keep track of the work their developers do. It's just that simple. The problem is non-technical people trying to keep track of what technical people do is bound to fail and cause friction.
I think technically mopeds, but yes. It's a weird and convoluted space now. Just as an example -- people will purposely install bicycle pedals on Surrons to make it look like they are just assisted ebikes or something.

https://currentebikes.com/wp-content/uploads/california_elec...
Michelin is almost unique. If a restaurant is not reviewed, a certain class of people do not go there. This is a rather different situation.

As to ``only positive reviews'': restaurants have been known to shutter when they lose a star.
How could stripe adopt this? Accounts are limited to depository institutions, aka banks. Stripe is a money transmitter, and their customers are businesses.
I'm not OP but yeah I assume it's fine until proven otherwise. Why wouldn't I?

Otherwise where does it end? What other things should I assume are dangerous despite no evidence? Or are you saying I should latch on to whatever baseless hysteria is popular at the moment?

I'm not a betting man. I think plastics have been around for a long time and as far as I know we haven't proven that they have a negative effect. If they did have a significant negative effect I'm pretty sure we would have proven it by now. So maybe they have an insignificant negative effect. I'm okay with that risk. If I weren't I wouldn't have time to do anything other than worry about and avoid shit that might have an insignificant negative effect - not to mention things that we know have a significant negative effect such as alcohol.

Honestly if you drink alcohol and you worry about microplastics you're just hypocritical.
What exactly are “the facts evident in the data”?

For example if one were to train an LLM on HN comments aside from just learning the syntax of language, the model might be much more useful if there was a way to somehow weight utter dross like the contents of your comment vs comments from domain experts.
I desperately wish there was some way I could both make my works publicly available and bar the use of them to train AI models.

But I don't think there is, and there's the real tragedy.
In the long term we’re all dead so too just have to survive 80-90 years
These three lessons are all the same lesson: so far, it costs too much to make food this way.
Video archivist Peter Kuran is the force behind it. Im surprised he’s not mentioned on HN; filming atomic fireballs is quite technical.

His site:
https://news.ycombinator.com/item?id=34294804
EDIT: I misunderstood.