douglasg14b

Hospital near me has password requirements for their electronic medical records system as:

• 6 characters, no more, no less
• 2 characters must be a number
• 4 characters must be a letter
• case insensitive
• never changed

And for new hires and what not, they tell them to use {hospital abbreviation}{2 digit year}. Like casu24

No freaking wonder

Why would it be on each dev to setup?

Your repo can, and should, include workspace settings for major editors that provide a uniform experience for anyone onboarded to the platform.

I agree that precommit hooks are good for uniformity. But slow pre commit hooks are frustrating, they are also often turned off. Your CI will always be the last gatekeeper for linting/formatting rules regardless.

Making precommit hooks slower means more devs disable them, which is the opposite of what you want. Save them for simple, read, checks and validations that can run in < 1s for even huge changesets.

Is that even legal?

I mean if you own a real estate, it doesn't cost more just because the plot of land becomes popular. You can sell it for more, sure.

I don't get how your registrar can suddenly boot you out from under a domain just because someone else is interested in it that has money.

Shouldn't that person or company have to offer you money to buy that domain?

Or on save even. Slow pre commit hooks suckkkk

That's not a linting problem that's a formatting problem.

That project should have automatic formatting on save setup.

Linters are not necessarily formatters they're solving two different problems and are becoming increasingly separated in their toolset.

Am I saying you are scientifically illiterate?

Based on the previous statements, yes. However, as a matter of fact, not necessarily insult.

The good news is you're following up with questions and want to learn more, instead of doubling down. With curiosity you will become more literate.

Maybe you were born with all the knowledge of the human race, but the rest of us have to learn it.

The education system in the country you are from has failed you. Assuming you are in your mid-late teens, or older, scientific topics should have already been taught in what North America would call "middle school" (11-14 years old). That teaches you things like conservation of momentum.

There is a reason why it's called illiteracy, because there is an expectation that the baseline level of education everyone in developed countries receives teaches them the fundamentals of how the world around them works. Without this fundamental understanding it's not possible to understand more complex topics that build upon it, stunting growth.

They're not on to anything here. As further stated by your comment.

Equal and opposite reaction.

There's a law for this. The matter is "pushing" against the ship, it doesn't have to push against anything else.

In fact having an atmosphere to push against actually reduces the effectiveness of thrust due to atmospheric pressure, which must be overcome. Which is why different engines are designed to run in atmosphere versus out of atmosphere.

If you throw a baseball in space you have transferred momentum to that baseball, pushing you back. You will move in the opposite direction (likely spin because you just imparted angular momentum onto yourself since you didn't throw from center of mass)

Given how many people think that railguns have no recoil because "there is no explosion" they might actually seriously believe what they just wrote.

Scientific illiteracy is through the roof.

Or maybe it's the same as it it's always been it's just that people that are scientifically illiterate are given platforms to speak their illiteracy as truth.

Practice practice practice, always challenge and improve on your foundational skills. Everything else gets easier. Write code and solve problems, struggle through it in whatever way works for you. There's not really a shortcut to getting more experience than to put in the work.

It's especially important to try and do things the "right way" as a learning/growth tool. It will take longer, and you'll rewrite your code multiple times, but the next time you encounter a similar problem you suddenly know exactly what to do and the constraints around the problem.

Do this often enough and you'll find yourself having a general idea of how to solve just about any problem you come across, and how to do it elegantly.