The user discovery happens because the act he performs provides the exact intent you need to give him the shortcut.

Also for clarity this is only relevant for content based sites and not apps. It is vanishingly rare for users to scroll up when reading content unless they want to reach the top

First time I'm seeing a "no AI" used to differentiate a work for hire.

Can't say this wasn't obviously coming. Boutique hand-coded consultancies/software-houses are probably going to spring up a lot.

It is the first thing I suggest to anyone when I see someone didn't implement it.

I've never heard a complaint about it until now.

This would be the first time taxes are paid in a different currency in Israel history.

Pretty wild that it's such a large acquisition it can affect a nation's monetary policy.

Comments URL: https://news.ycombinator.com/item?id=47240868

Points: 1

# Comments: 0

I've never heard of something like that. Usually the requirement for being director level manager of engineers is to at least have managed people as an EM for several years before.

Product manager titles can have completely disjoint scopes of work between organizations - in one org they might be what was once systems designer role - getting requirements and writing specs, in another they might basically be doing UI or UX (even creating pages in figma), in others they are basically project managers.

It is not very useful in giving you confidence your changes would not cause unexpected side effects, which is usually the main problem working with legacy code.

If you want confidence when working with legacy code, your best bet is to do a strangler fig pattern - find a boundaries for the module you want to work on, rewrite the module (or clone and make your changes), run both at the same time in shadow mode, monitor and verify your new module is working the same as the old one, then switch and eventually delete the old module.

If your particular use of a SaaS is not susceptible to security issues (for example you can use it on your local laptop) then a slither of features that are insecure is exactly the thing for you.

Not everyone is going to replace SaaS with half-baked personal implementations, especially the big companies that most SaaS are aimed at, but it will gnaw out some of the long tail of SaaS subscription revenue for sure.

So I don't think it's fair to characterize it as he "only complains about it when his company is fined".

You also most likely lose out on a lot of logging frameworks your language has that your dependencies might use.

I would say this is a good layer to put on top of your regular logs. Make sure you have a request/session wide id and aggregate all those in your clickhouse or whatever into a single "log".

I've never heard an XSS vulnerability described as a supply-chain attack before though, usually that one is reserved for package managers malicious scripts or companies putting backdoors in hardware.

It has become a standard tool, in the same way that most developers code with an IDE, most developers use agentic AI to start a task (if not to finish it).

"The final implementation criteria for school inclusion were thus:

• At least 66% of the lead Primary classroom teachers are trained by one of the two most prominent Montessori teacher training organizations, the Association Montessori Internationale (AMI) or the American Montessori Society (AMS). One school was excluded on this basis.

• No more than two adults, the trained teacher and a non-teaching assistant, in the classroom on a regular basis. No school was excluded on this basis.

• Classrooms are mixed-age, with at least 18 children ranging from 3 to 6 years old. Five schools did not mix ages so were excluded.

• At least a 2-hour uninterrupted free choice period every day. Five schools were excluded on this basis.

• Each classroom has at least 80% of the complete set of roughly 150 Montessori Primary materials, and fewer than 5% of the materials available to children in the classroom are not Montessori materials. No school was excluded for failing to meet this criterion."

So seems like the criteria for this research is fairly good.

In general though it's hard to tell if a school is Montessori or not. The method is not trademarked and anyone can claim to be a Montessori school ,or Montessori inspired etc...

There are two organizations that certify - AMI, which was created by Maria Montessori's daughter and functions mostly in Europe, and AMS which is an American organization founded by people inspired by the Montessori method.

AMI is stricter while AMS is more modern, but most places that identify as Montessori is neither.

I would say the best way to identify if a school is Montessori is first if they have mixed-age classrooms, the standard is a 3 year class (so 1-3, 4-6, 7-9...).

If all the kids in a class are in the same age, it's not Montessori.

Second, for preschool, you expect the class to be very organized with intermittent shelves and work areas, and very neat (no mountain of toys etc...) - https://www.google.com/search?udm=2&q=montessori+classroom

Maybe the Windows Vista of Tablet OSs though.