Man if you actually use proper http status codes instead of returning 200 to every single request no matter the outcome, you’re already better than a lot of “senior” developers. If you’ve written any amount of half-useful readmes or docs or even comments, you’re well above the average. If you’re aware that git has more than 3 commands, you’re well on your way to godhood.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
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.
Man if you actually use proper http status codes instead of returning 200 to every single request no matter the outcome, you’re already better than a lot of “senior” developers. If you’ve written any amount of half-useful readmes or docs or even comments, you’re well above the average. If you’re aware that git has more than 3 commands, you’re well on your way to godhood.
I dazzle the youngins every time I
git rebase
Whereas I…uh… Give the youngins a memorable story to tell later, when I
git rebase
.Fantasticly written. I’m going to quote you in my team onboarding documents.
Did you inherit the same project I did?
Did they also not use feature branches, API documentation, or any frontend framework, opting to create one based on jQuery instead?
You mean every error shouldn’t be a 500?