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.

Infact... Early stages of a project should make heavy use of owned and cloned types while you figure out the bottlenecks and work out how to architect the solution.

Isn't it just "go mod install" or something? Oh you probably tried it when golang changes where it cached packages. I feel you that was a super crappy time to learn Go.

You probably shouldn't deal with lifetimes outside of first order use cases in 9/10 cases when a project is in its early stages. A clone or wrapper type isn't all that expensive in many applications. Just because something can be optimized doesn't mean it should be, especially early on in a project.

Hard agree here. Once people understand rust, not read some bullet points on a blog they start to understand how useful even the tooling is.

Only thing I'll add is. 8 times out of 10 if you are reaching for advanced rust, you are over engineering. Most software projects don't require it and when they do, you should always question whether there's a simpler more maintainable way or make a other design decision. There is no award for least lines of code, or most utilized compiler. Software is social.

That's Go's biggest strength over Rust and Scala. Good luck getting job security in that language. It takes a few years to really know what I'm saying but in my opinion it's the difference between a senior engineer and a non senior.

If you spent more time with rust your opinion of it would change. It's strength has nothing to do with rewriting software. It's easy to maintain, and pretty fast to write.

I prefer go for cloud integrations because they tend to have the best implementations and most solid APIs. That's about it though.

Python is a good bash replacement, but I don't like writing large projects in it. It's hard to maintain and the errors that come from production are never straightforward. Good for some medium scale mathy compute projects though.

C++ is where I write most math code after prototyping it elsewhere(R or Python)

Rust for me is the answer to most things except, it's ecosystem is a bit weak, and it's a bit of a clout chaser language(not as bad as others though)

Yea like the ones where we throw an entire AWS server room to try multiple random seeds, using gradient descent until it works, but honestly a RNG might work just as well, in a few contrived cases and we write our paper/make our product from it

Aren't these two things directly related in a lot of cases? Or is the only reason they often aren't because "AI" is completely unregulated in the US?

That's hilarious and absolutely true. I think he omitted a few shadier things too.

In ML people don't read the literature, establish precedent or even formulate sound hypothesis'. Why this got posted here, I'll never know... Oh wait I know, next week someone will publish a paper claiming success with this using ChatGPT. A year later it'll be found to be bogus, but that won't stop the cash from flowing in.

Let me ask you this though, is it more profitable?

If only people could think from outside themselves for two seconds to assess technological impacts like you just have.

Wow. Now that's a very special event indeed. Cheers on not having to run a docker or work exclusively from a VM because of office politics.

You mean, open collaboration from people who care about what they are doing often leads to better projects faster? Careful now, someone might call ya a commie or worse an anarchist.

Postgres allowing Json support destroyed so many marketing campaigns from non-technicaleadership "sick of all the money spent on SQL, we gotta try this nosql thing"

Au contraire. Publish nothing, delete the key results, and put intentional bugs in every home project. Otherwise you will be stolen from, or exploited. Sit back and wait and watch the rare few people approach your ideas. Reach out to them with interest and make best friends for life.

I know the op isn't about this but love putting nuggets like this out there