thumbuddy

I love how the punchline of the article is, "if you are in management you can stop these people!". But 98% of people in management are these people. The remaining 2% are on the short list by their toxic managers for dismissal. Almost all hierarchys in companies exist so dark personalities can exploit others. Plain and simple.

This is why stratagems like quiet quitting exist.

We'd probably be good on a team together. Nice to see like like-minded people in here.

Respect? In 2023? Think that died for profit in 2010.

I'll take obvious jank over hidden jank any day personally.

The value of human life in most places is exceedingly low. In the US if a company kills ya due to an OSHA violation the company pays something like 35,000 to OSHA. I imagine that's more than a Congolese cobalt miner, but when you compare it to the cost of say a car, a house, an education, etc. It's pretty sad out there.

Look I'm only for it if someone is making some money here.

Lol "dear free laborers your code must be flawless or you will be sued"... Hmmm sooo... About changing my hobbies...

You don't have to clone... Really you don't. If you want fast rust code, learning how to avoid that is probably step 1.

Just practice. Screw all the "how to learn x" grind culture stuff. Just download it. Build a project with it. Read other people's code. Rinse and repeat.

It's a jack of all trades but a master of none. Nothing wrong with that until there is. Then you end up with two languages. This works fine for a while. Until you need 3... Next thing you know half your code was rewritten in other languages and cleaned up. Start realizing ya could have started your projects using different tools.

Not pooping on python it's... Fine. But I am not of the opinion that it's a great choice for all projects because technically "it can" do "anything".

I know where you're at because I used to feel the same way. But what if rust was designed to make manual memory management as painless as possible? IE, it's the antithesis of a language like C because when you learn it's syntax all practical memory management is done by basically writing OCAML.

In rust there are two forms of memory management, 1. You write rust. 2. You write unsafe rust.

You never really have to refactor to suite a different style. Infact changing allocators is as simple as running "cargo install".

Rust isn't as bad as people make it out to be but you do have to invest some time to learning it.

But as far as throw one away goes... You can write it in rust, and then slightly adjust when you do things like clone so nothing gets thrown away unless you really botched it the first time you wrote it.

Is it obscuring the logic to explicitly handle the cases where an item may not exist, or to tell an engineer when they are copying memory? In my opinion it's the opposite.

Orders of magnitude slower with few options for improvement except writing in another language in a lot of cases.

That's wild. First time I saw a match case, if let, and matches! Invocation I was freaking relieved. No by hand type checking in a dynamic language, having to consider corner cases, etc. LSP even autocompletes the cases with a single hotkey. Escape from boilerplate hell.