Programmer Humor

853 readers

14 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

cat_programmer@lemmy.ml

217

Spent 10 minutes debugging... (lemmy.ml)

submitted 9 months ago by Ephera@lemmy.ml to c/programmerhumor@lemmy.ml

6 comments fedilink hide all child comments

top 6 comments

sorted by: hot top controversial new old

[–] kittehx@lemmy.blahaj.zone 34 points 9 months ago (1 children)

Only 10 minutes? Those are rookie numbers

[–] DahGangalang@infosec.pub 23 points 8 months ago

Or pro numbers, depending on how you look at it.

[–] fraichu@lemmy.ml 12 points 9 months ago* (last edited 9 months ago) (1 children)

I'm curious you'd see it in ls -l Did inode change? I remember making the same mistake. I think everyone sees this sometime during the career

[–] Ephera@lemmy.ml 14 points 9 months ago

The inode does change, yeah:

The regular ls -l doesn't show the inode on my system, though. I only realized it when I had assigned more permissions to the file and those got reset by deleting the file. The last-modified timestamp also gets updated each time, but I only spotted that afterwards...

[–] Still@programming.dev 12 points 8 months ago (1 children)

lsof is a good tool would recommend it whenever something weird is happen, tho you gotta be root for it

[–] AndrasKrigare 1 points 8 months ago

Another is checking modified time of the directory