TL;DR: At a house party, on my Phone, via shitty German mobile network using the GitLab website's plain text editor. Thanks to CI/CD my changes to the code were easily tested and deployed to the server.

It was for a college project and someone had a bug in his 600+ lines function that was nested like hell. At least 7 levels deep. Told him before I went to that party it's probably a redefined counter variable but he wouldn't have it as he was sure it was an error with the business logic. Told him to simplify the code then but he wouldn't do that either because "the code/logic is too complex to be simplified"... Yeah... what a dipshit...
Nonetheless I went to the party and He kept debugging. At some point he called me and asked me to help him the following day. Knowing that the code had to be fixed anyways I agreed.
I also knew I wouldn't be much of a help the next day due to side effects of the party, so I tried looking at this shitshow of a function on my phone. Oh did I mention it was PHP, yet? Yeah... About 30 minutes and a beer later I found the bug and of course it was a redefined counter variable... My respect for him as a dev was already crumbling but it died completely during that evening

PHP ist one of the languages I use regularly, but not the main language.
Anyhow, passing an array to a function will create a Copy of the array unless you specifically choose to Pass the reference.
That's seriously fucked up. What other language does that?! Coming from C, Java, Python to PHP I was not prepared to expect shit like that.

Is it just me or do the ducks look pretty quacking thiicccccc?

Go home Jager, you're drunk.

What I Like about Home Office?
My squeaky clean toilet. No colleagues who Block the toilet, no colleagues who seem to forget their bathroom cleanliness at home

The copious amounts of alcohol I can consume after spending 3.5 hours finding where the missing } should be. Not to mention the mini-fridge stocked up with cans/bottles of lager and a fresh, nice cold bottle of Jäger 👍😛

Any U.S. Americans here who can confirm the stories about "U.S. Americans beginning to stock Up on guns and ammo"?
I mean it sounds plausible but it's surely mostly overblown by the media, right? RIGHT?!

Are there any official definitions for the terms Software Developer and Software Engineer? Today a friend told me He got a raise and he's now a software engineer and no longer "just" a software developer (still at the same company).

To him and me that sounds like bullshit bingo at its best. His tasks and responsibilities will still be the same after the change of his job title.
So I'm wondering whether anyone here knows of some objectively defined distinctions between the two job titles. To me and my friend those are just the same. I never even thought anyone would make a distinction between the two

Is there a way to freeze or cap the amount of ++ that's displayed for my account? I'd Like to stop at 666 without having to stop posting
⊙﹏⊙

Any Go devs in Windows out there? I'm interested to hear about your dev environments.
IDE, Powershell vs MinTTY, native windows vs WSL, other tools?

There's no favourite coding challenge for me. Of course I do them when I'm asked to but I don't think anyone can derive how Well someone works from these short toy challenges.

I once had a proper prototyping Challenge that was really fun. I had to Work on it in advance to the interview. I had to define the scope and how much time I will spend in it in advance and then explain and defend the scoping and all technological/architecture decisions and handle proper criticism in the interview. No bullshit coding challenges Had to be solved :)
I think these prototyping challenges will Tell you way more about an applicant and his worth as a dev than those little challenges ever could.

Only when the latest feature is implemented, the last bugfix and the last workaround are found, the last unit test is written, the latest CI/CD pipeline done, the customer guy does manual testing and acceptance tests on the staging server and let's them pass and a few days later it's pushed to production...
You will be reminded (again) that shitty customers do exist! A customer is the least capable person to tell you what the customer actually wants and is also the least trustworthy person to test the features he requested...
Holy fuck come on! Just test that shit on the staging Server! One Look could have already shown you that that's Not what you expected!

I checked the logs after that and yup you guessed correctly... The said endpoints weren't even used on staging, only on production...

On the back-room interview couch. There is no job *wink wink*

How do you protect your team's git remotes?
We tend to protect the master and stage branch from force pushing and only allow merging pull requests after successfull recent tests and successfull review by someone with proper permissions. Depending on the project the Dev branch is only protected from force pushing though. All other branches are free to handle however wanted.

We recently had someone do a "git push -f --mirror" without understanding the command. Quick reminder what that does: it mirrors all your local branches to the remote so that the remote will be a mirror of your local repo. Branches that exist on remote but not on your machine will be removed from the remote.
A then needed to work from B's feature branch but of course that was gone... So while the idiot didn't fuck up our protected branches he still fucked over other people's workflow with that.

Is there an alternative to outright blocking force pushes which could have prevented that (except force pushing intelligence into his brain)?

Do you guys feel like your current salary fits your current job and your actual tasks and responsibilities?

I for example feel like my previous job was overpayed for what my actual responsibilities were and that my current job (being the first dev in a fresh start-up) is overwhelmingly underpaid for what amounts to way more and bigger tasks and responsibilities than I had at my previous job. But I'm nonetheless more happy with my current job than I ever were with my previous one.