1073
cross-posted from: https://lemmit.online/post/1006130
This is an automated archive made by the Lemmit Bot.
The original was posted on /r/aboringdystopia by /u/Last_Salad_5080 on 2023-10-03 14:21:04.
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Oct 2023
1073 points (97.8% liked)
A Boring Dystopia
9773 readers
178 users here now
Pictures, Videos, Articles showing just how boring it is to live in a dystopic society, or with signs of a dystopic society.
Rules (Subject to Change)
--Be a Decent Human Being
--Posting news articles: include the source name and exact title from article in your post title
--Posts must have something to do with the topic
--Zero tolerance for Racism/Sexism/Ableism/etc.
--No NSFW content
--Abide by the rules of lemmy.world
founded 1 year ago
MODERATORS
Yeah, this was torture in grade school. I figured it would get better in middle school.
Then it was torture in middle school and I thought it would get better in high school.
Then it was STILL torture in high school and I thought it would surely, surely get better in college.
Then I got to college and there were still mofos reading. like. this.
I am an engineer who oversees a team. Most of them can't write more than a coherent sentence. Code and analyze data, sure, but put together a coherent paragraph? Not really.
There's a weird ongoing thing in the programming world where about half of coders think code should be well-commented and the other half not only think that code shouldn't contain comments but also think that comments are an indicator of professional incompetence (aka a "code smell"). I've long noticed that the anti-commenting crowd are also the ones that can't write very well.
Almost like they don't want anyone to figure out how dogshit their code is.
People who dislike code documentation are often overoptimizers, from my experience.
In my experience it is job security.
Optimizing like it’s the early 80s and every byte is precious? Or do you mean something else?
Exactly. Using 10 obscure instructions to save 1 clock cycle.
Assuming it even does save it. The complier is going to do what it wants to do. Unless you really know your stuff any high level language is going to be a black box. One guy I worked with loved to do that but he would be able to prove that it did matter.
One way my code improves is by thinking what I need to comment. Then I refactor some and the comments become somewhat redundant.
I don't think I would agree to work with someone who doesn't comment their code.
I was basically driven out of my last job by someone who wouldn't agree to work with someone (me) who did comment their code. Like I said, it's a really weird dividing line in programming.
I have had to tell software engineers time and time again that is is totally okay to make error strings beyond one sentence or one word. It almost seems to me that they never realized that strings can hold multiple sentences and and don't have relevant memory constraints.