this post was submitted on 05 Mar 2025
1660 points (100.0% liked)

Programmer Humor

21779 readers
3068 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 
top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 121 points 2 weeks ago* (last edited 2 weeks ago) (9 children)

Regex

Edit: to everyone who responded, I use regex infrequently enough that the knowledge never really crystalizes. By the time I need it for this one thing again, I haven't touched it in like a year.

[–] [email protected] 39 points 2 weeks ago

You get used to it, I don't even see the code—I just see: group... pattern... read-ahead...

[–] [email protected] 34 points 2 weeks ago (1 children)

Most of regex is pretty basic and easy to learn, it's the look ahead and look behind that are the killers imo

[–] [email protected] 11 points 2 weeks ago

(?=) for positive lookahead and (?!) for negative lookahead. Stick a < in the middle for lookbehind.

[–] [email protected] 14 points 2 weeks ago (1 children)

You always forget regex syntax?

I've always found it simple to understand and remember. Even over many years and decades, I've never had issues reading or writing simple regex syntax (excluding the flags and shorthands) even after long regex breaks.

[–] [email protected] 16 points 2 weeks ago (6 children)

It's not about the syntax itself, it's about which syntax to use. There are different ones and remembering which one is for which language is tough.

load more comments (6 replies)
[–] [email protected] 9 points 2 weeks ago (4 children)

https://regex101.com/

Don't let the gatekeepers keep you out. This site helps.

load more comments (4 replies)
[–] [email protected] 8 points 2 weeks ago (1 children)

No. Learn it properly once and you're good. Also it's super handy in vim.

load more comments (1 replies)
load more comments (4 replies)
[–] [email protected] 61 points 2 weeks ago (5 children)

PSA: Run ShellCheck on your shell scripts. It turns up a shocking number of programming errors. https://www.shellcheck.net/

load more comments (5 replies)
[–] [email protected] 54 points 2 weeks ago (5 children)

Clearly you don't write enough bash scripts.

[–] [email protected] 17 points 2 weeks ago (4 children)

Or scripts for basically any other variant of the Bourne shell. They are, for the most part, very cross compatible.

[–] [email protected] 11 points 2 weeks ago

That's the only reason I've ever done much of anything in shell script. As a network administrator I've worked many network appliances running on some flavor of Unix and the one language I can count on to be always available is bash. It has been well worth knowing for just that reason.

load more comments (3 replies)
load more comments (4 replies)
[–] [email protected] 50 points 2 weeks ago (4 children)

I don't normally say this, but the AI tools I've used to help me write bash were pretty much spot on.

[–] [email protected] 24 points 2 weeks ago (1 children)

Yes, with respect to the grey bearded uncles and aunties; as someone who never "learned" bash, in 2025 I'm letting a LLM do the bashing for me.

[–] [email protected] 39 points 2 weeks ago (4 children)

Until the magic incantations you don't bother to understand don't actually do what you think they're doing.

[–] [email protected] 41 points 2 weeks ago (1 children)

Sounds like a problem for future me. That guy hates me lol

load more comments (1 replies)
[–] [email protected] 14 points 2 weeks ago (1 children)

I wonder if there's a chance of getting rm -rf /* or zip bombs. Those are definitely in the training data at least.

load more comments (1 replies)
[–] [email protected] 11 points 2 weeks ago* (last edited 2 weeks ago)

In fairness, this also happens to me when I write the bash script myself 😂

load more comments (1 replies)
[–] [email protected] 16 points 2 weeks ago* (last edited 2 weeks ago)

Yeah, an LLM can quickly parrot some basic boilerplate that's showed up in its training data a hundred times.

load more comments (2 replies)
[–] [email protected] 30 points 2 weeks ago (3 children)

There's always the old piece of wisdom from the Unix jungle: "If you write a complex shellscript, sooner or later you'll wish you wrote it in a real programming language."

I wrote a huge PowerShell script over the past few years. I was like "Ooh, guess this is a resume item if anyone asks me if I know PowerShell." ...around the beginning of the year I rewrote the bloody thing in Python and I have zero regrets. It's no longer a Big Mush of Stuff That Does a Thing. It's got object orientation now. Design patterns. Things in independent units. Shit like that.

[–] [email protected] 14 points 2 weeks ago (4 children)

I consider python a scripting language too.

load more comments (2 replies)
[–] [email protected] 30 points 2 weeks ago (11 children)

Ever since I switched to Fish Shell, I've had no issues remembering anything. Ported my entire catalogue of custom scripts over to fish and everything became much cleaner. More legible, and less code to accomplish the same things. Easier argument parsing, control structures, everything. Much less error prone IMO.

Highly recommend it. It's obviously not POSIX or anything, but I find that the cost of installing fish on every machine I own is lower than maintaining POSIX-compliant scripts.

Enjoy your scripting!

[–] [email protected] 10 points 2 weeks ago (3 children)

If you're going to write scripts that requires installing software, might as well use something like python though? Most Linux distros ship also ship with python installed

load more comments (3 replies)
load more comments (10 replies)
[–] [email protected] 26 points 2 weeks ago (1 children)

every control structure should end in the backwards spelling of how they started

[–] [email protected] 17 points 2 weeks ago (1 children)

Once you get used to it it is kind of fun.

Shame about do though.

[–] [email protected] 14 points 2 weeks ago

it could have been not since there's no try.

[–] [email protected] 26 points 2 weeks ago (2 children)

Today I tried to write bash (I think)

I grabbed a bunch of commands, slapped a bunch of "&&" to string them together and saved them to a .sh file.

It didn't work as expected and I did not, at all, look at any documentation during the process. (This is obviously on me, I'll try harder next time)

load more comments (2 replies)
[–] [email protected] 20 points 2 weeks ago* (last edited 2 weeks ago) (3 children)

That's why I use nushell. Very convenient for writing scripts that you can understand. Obviously, it cannot beat Python in terms of prototyping, but at least I don't have to relearn it everytime.

[–] [email protected] 23 points 2 weeks ago (14 children)

So the alternative is:

  • either an obtuse script that works everywhere, or
  • a legible script that only works on your machine…
load more comments (14 replies)
[–] [email protected] 12 points 2 weeks ago (7 children)

Nu is great. Using it since many years. Clearly superior shell. Only problem is, that it constantly faces breaking changes and you therefore need to frequently update your modules.

load more comments (7 replies)
load more comments (1 replies)
[–] [email protected] 18 points 2 weeks ago

Wait im not the only one? I think i relearned bash more times than i can remember.

[–] [email protected] 15 points 2 weeks ago

Bash was the first language I learned, got pretty decent at it. Now what happens is I think of a tiny script I need to write, I start writing it in Bash, I have to do string manipulation, I say fuck this shit and rewrite in Python lol

[–] [email protected] 14 points 2 weeks ago (1 children)

Knowing that there is still a bash script i wrote around 5 years ago still running the entirety of my high scool lab makes me sorry for the poor bastard that will need to fix those hieroglyphs as soon as some package breaks the script. I hate that i used bash, but it was the easiest option at the time on that desolate server.

[–] [email protected] 8 points 2 weeks ago

Bash scripts survive because often times they are the easiest option on an abandoned server

[–] [email protected] 12 points 2 weeks ago (2 children)

This. But Pandas and Numpy.

Pandas and Numpy and Bash.

load more comments (2 replies)
[–] [email protected] 12 points 2 weeks ago (2 children)

So true. Every time I have to look up how to write a bash for loop. Where does the semicolon go? Where is the newline? Is it terminated with done? Or with end? The worst part with bash is that when you do it wrong, most of the time there is no error but something completely wrong happens.

[–] [email protected] 13 points 2 weeks ago* (last edited 2 weeks ago) (3 children)

It all makes sense when you think about the way it will be parsed. I prefer to use newlines instead of semicolons to show the blocks more clearly.

for file in *.txt
do
    cat "$file"
done

The do and done serve as the loop block delimiters. Such as { and } in many other languages. The shell parser couldn't know where stuff starts/ends.

Edit: I agree that the then/fi, do/done case/esac are very inconsistent.

Also to fail early and raise errors on uninitialized variables, I recommend to add this to the beginning of your bash scripts:

set -euo pipefail

Or only this for regular sh scripts:

set -eu

-e: Exit on error

-u: Error on access to undefined variable

-o pipefail: Abort pipeline early if any part of it fails.

There is also -x that can be very useful for debugging as it shows a trace of every command and result as it is executed.

load more comments (3 replies)
load more comments (1 replies)
[–] [email protected] 12 points 2 weeks ago (5 children)

And I thought I was the only one… for smaller bash scripts chatGPT/Deepseek does a good enough job at it. Though I still haven’t tried VScode’s copilot on bash scripts. I have only tried it wirh C code and it kiiiinda did an ass job at helping…

load more comments (5 replies)
[–] [email protected] 12 points 2 weeks ago (1 children)

Unironically love powershell

load more comments (1 replies)
[–] [email protected] 10 points 2 weeks ago (3 children)

No, Makefile syntax is more extreme.

load more comments (3 replies)
[–] [email protected] 10 points 2 weeks ago

Any no-SQL syntax for interacting with databases.

[–] [email protected] 10 points 2 weeks ago

Me with powershell. I'll write a pretty complex script, not write powershell for 3 months, come back and have to completely relearn it.

[–] [email protected] 9 points 2 weeks ago (9 children)

Bash substitution is regex-level wizardry.

load more comments (9 replies)
[–] [email protected] 9 points 2 weeks ago (2 children)

to be honest I agree and thought we would be using something more intuitive by now

load more comments (2 replies)
[–] [email protected] 8 points 2 weeks ago

When I was finishing of my degree at Uni I actually spent a couple of months as an auxiliary teacher giving professional training in Unix, which included teaching people shell script.

Nowadays (granted, almost 3 decades later), I remember almost nothing of shell scripting, even though I've stayed on the Technical Career Track doing mostly Programming since.

So that joke is very much me irl.

load more comments
view more: next ›