Programming thread

[Geranium]

The language looks cool and usable enough, but the community of people that use Rust have put me off taking the dive.

Apologies for replying to a post from a few pages back (I did not expect someone to unleash an autistic APL-loving ChatGPT bot into the thread), but Maurice Bos / Mara Bos is one of my favourites.

 

[Napoleon Bonerfart]

I deliberately have not. The language looks cool and usable enough, but the community of people that use Rust have put me off taking the dive. Half of them are actual trannies, and the other half are cultists that rewrite software in Rust just because they can, and preach the Good Word of their computer coding language with a religious zeal that makes the Lispers and Haskellites blush. Becoming a 'Rust programmer' means that these people are now your peers.
View attachment 4029429View attachment 4029393

The only thing Rust has over C is prevention of null pointers and garbage collection. A null pointer check is trivial, and C and C++ compilers and libraries already include warnings about doing that, along with smart pointers.

 

[Kosher Dill]

A null pointer check is trivial

- "Famous Epitaphs, chapter 5: Programmers"

 

[Napoleon Bonerfart]

- "Famous Epitaphs, chapter 5: Programmers"

I wasn’t aware that checking to see if the value of something was zero before continuing execution was such a difficult programming task. Perhaps we should only reserve this skill set for the senior programmers.

 

[Arianne Chan]

I know it's not very relevant to the topic, but, what's up with a shit-ton of programmers being trannies?

 

[Agent Sandoval]

The only thing Rust has over C is prevention of null pointers and garbage collection. A null pointer check is trivial, and C and C++ compilers and libraries already include warnings about doing that, along with smart pointers.

Memory safety does not and is not meant to eliminate null checks. Option<T> is literally just nullable data, you check those constantly in Rust.
The worst move the Rust team has made was to advertise memory safety as a primary feature.

 

[Bruce Springsteen]

I know it's not very relevant to the topic, but, what's up with a shit-ton of programmers being trannies?

Spoiler: This is not programming talk

Autism causes transsexualism. It is not a comorbidity, you just straight up have to be insanely autistic to fixate on becoming the girl/man. This is why you see a huge overlap between trans people, programmers, and speedrunners. I'm a doctor, trust me.

 

[wtfNeedSignUp]

> Make huge ass rebase between branches with multiple fixes needed.
> Tell myself not to be a lazy and wait until it's a huge undertaking.
> Be lazy and continue working on multiple branches at the same time for couple of weeks.

 

[Agent Sandoval]

Spoiler: This is not programming talk

Autism causes transsexualism. It is not a comorbidity, you just straight up have to be insanely autistic to fixate on becoming the girl/man. This is why you see a huge overlap between trans people, programmers, and speedrunners. I'm a doctor, trust me.

Spoiler: This is also not programming talk

To add to this, autists have trouble with empathy and imagining experience outside of their own. In extreme cases they can't imagine attractiveness in terms other than what they personally find attractive. So, in trying to be attractive autistic males pursue feminine traits; that's what they find attractive so that must be what attractiveness is.
I am also very trustworthy.

 

[Fcret]

Happy New Year fellow programmers

May your 2023 be full of boundless TC, comprehensible code, and zero compilation errors

 

[Samuel Hyde]

Anyone tried Rust? Looks interesting, you can see the good stuff they took from other languages. Steep learning curve for sure.

The language is a nightmare and a joke. There's even a thread about the community being full of trannies.

If you want system language then you're still stuck with some flavor of C or C++. If those are too much of a commitment then try a more abstract language that handles memory for you like C#.

The whole idea behind rust was to basically create a "memory safe" environment (they made that up. Nobody was talking about memory safety the way people in the rust community do) by forcing the programmer to do all the various functions of memory life cycle by hand instead of using garbage collection or just expecting programmers to be adults with memory (The C way)

 

[Kršćanin Čendlervic]

If Rust was a real programming language, people would’ve done something other than autistically rewrite things in it for the last 12 years.

 

[The Cunting Death]

Thank heavenly fuck I backed up my code.

Earlier last night I fucked up something with my code and I forgot what set it off. Luckily I kept a backup from a conversation I was having with someone regarding coding (from the night prior) otherwise I would have lost at least two months worth of work.

 

[byuu]

 

[canalCrab]

 

[glow]

The only thing worse than other people's code is other people's test code. Developers who write decent-ish code using good practices, encapsulation and good comments suddenly become absolute barbarians when writing test cases. I'm going to cut a bitch next time I see a test case named ServiceShouldReturnResultAsExpected which is 200 lines long and contains dozens of assertions, for loops and supplementary fake classes and gives you no clue about what the developer was even thinking about.

Below it is a test case called ServiceShouldReturnResultAsExpected2 which is exactly the same but some minor amendments, and below it is another one which is marked as "skipped" and the comment refers to a ticket from 4 years ago which was moved across sprints multiple times and eventually just got quietly dropped by some PM and the body of the ticket is "placeholder ticket to fix threading issue, call pratesh with any questions", only both people called Pratesh haven't worked here for years and I don't even know which one they're referring to.

Below that is another unit test that also replaces some, but not all repository classes with real classes that reference a local database server and take 2 minutes to run for no apparent reason. There is no custom fucking SQL there or anything and I can't even see any meaningful assertions. The names are also vague as fuck.

Eventually I figured out the scam: all the test cases were variations to send the frame pointer through specific code paths to meet some long abandoned management KPI from years ago to increase code coverage. They don't assert anything meaningful, the point isn't actually to test anything, it's just to improve numbers.

I took the time to clear up the technical debt and wrote about 20 test cases that represented real world expectations from the system, fixed the bug and was questioned by the PM about whether my time would have been better spent implementing some bullshit feature.

A programmer's life is pain.

 

[Rusty Metal Skull Gun]

The only thing worse than other people's code is other people's test code. Developers who write decent-ish code using good practices, encapsulation and good comments suddenly become absolute barbarians when writing test cases. I'm going to cut a bitch next time I see a test case named ServiceShouldReturnResultAsExpected which is 200 lines long and contains dozens of assertions, for loops and supplementary fake classes and gives you no clue about what the developer was even thinking about.

Below it is a test case called ServiceShouldReturnResultAsExpected2 which is exactly the same but some minor amendments, and below it is another one which is marked as "skipped" and the comment refers to a ticket from 4 years ago which was moved across sprints multiple times and eventually just got quietly dropped by some PM and the body of the ticket is "placeholder ticket to fix threading issue, call pratesh with any questions", only both people called Pratesh haven't worked here for years and I don't even know which one they're referring to.

Below that is another unit test that also replaces some, but not all repository classes with real classes that reference a local database server and take 2 minutes to run for no apparent reason. There is no custom fucking SQL there or anything and I can't even see any meaningful assertions. The names are also vague as fuck.

Eventually I figured out the scam: all the test cases were variations to send the frame pointer through specific code paths to meet some long abandoned management KPI from years ago to increase code coverage. They don't assert anything meaningful, the point isn't actually to test anything, it's just to improve numbers.

I took the time to clear up the technical debt and wrote about 20 test cases that represented real world expectations from the system, fixed the bug and was questioned by the PM about whether my time would have been better spent implementing some bullshit feature.

A programmer's life is pain.

Changing your mind about Java yet?

 

[glow]

Changing your mind about Java yet?

I stand by my previous comment - shitty programmers write shitty code, the language/runtime doesn't matter. I've worked on great codebases in many languages, even PHP if you can believe it. My current codebase is .NET and in general it's decent but there are areas which were either done under time pressure or more likely developers who just didn't give a shit.

 

[Fcret]

I took the time to clear up the technical debt and wrote about 20 test cases that represented real world expectations from the system, fixed the bug and was questioned by the PM about whether my time would have been better spent implementing some bullshit feature.

A programmer's life is pain.

Whenever I take time to put tech debt in our backlog and am asked about it, I'm just frank about it: "This is going to save our asses a year from now when we get a fuckton of business asks all at once."

And actually that ended up being correct recently so I'm now vindicated and can get away with anything.

 

[glow]

Whenever I take time to put tech debt in our backlog and am asked about it, I'm just frank about it: "This is going to save our asses a year from now when we get a fuckton of business asks all at once."

Precisely correct, and this is normally what is done but sometimes management or product people can behave like heroin addicts, like skipping paying rent to get their next fix and worrying about the consequences later.