Yet again: why are Open Source maintainers so rude with newbies?

My first contact with this was with the rude-wall Graham Campbell from the Laravel projects. I don't have the links anymore, but I recall a specific issue where, after a couple of passive-aggressive messages from both sides, he agreed he started stuff with the wrong foot and he's usually rude in the first place - and then we were able to actually discuss the issue.

Now I am a newbie on Home Assistant and was clueless on why an add-on wasn't working... I found an issue on GitHub with the same problem and no actual solution, and locked... So I opened a new one, wrote a ton of stuff, only to find a crude "provide logs" with no help on how to achieve that. Turns out the developer does acknowledge he's an asshole "at first sight" in how own profile.

So... why?
Is this hatred for newbie questions, without recalling they were also one at some point in their lives?
Are these cocky developers, full of themselves and their important projects (no irony on "important", they are indeed), that can't think of issue reporters as "an actual human being on the other side of the screen"?
Maybe just another symptom of internet interactions?

I totally acknowledge I got rude after his answers, but I still had an honest interest on helping the project from a user POV and he just don't give a damn, probably since he got hatred by my person after showing newbieness?

- original issue with unresponded questions about logging and docs: https://github.com/hassio-addons/...
- my follow-up on the same issue, where I faced the same logging cluelessness: https://github.com/hassio-addons/...
- follow-up with another honest question on the same topic, closed on sight: https://github.com/hassio-addons/...

When I can see actual clients using my software, and can get real feedback from them.

I usually work on backstage projects and my job never really affected "real, normal users". When I have something pushed and can really see user feedback and smiles, that means I've made it.

Of course, if that's on a decent job, with a decent team and decent pay. Which is where I am at now.

Soon, the app will be released - if the external infrastructure guy stop sucking. So, I'm hoping to feel I've made it soon, real soon :)

To all React developers out there:
have you ever used the "so famous" Redux Time Machine Debugger capabilities?

Every now and then I see articles praising that as "one of the greatest things in Redux", but I either didn't understand the feature enough to see usage, or my applications are "way too CRUD"(?) to warrant time-traveling debugging.

Please, someone enlighten me :)

The legacy codebase, episode 94385948:
How to neatly organize your code in the age pre-docblocks.

Bonus: could this function be renamed to colectomy? Or maybe de-punctuation?
(yep, probably a bad joke with a "typo", sorry)

Bonus 2: seriously? A function for that?

THANKS FOR THE EXPLANATION. I WOULD HAVE NO IDEA OTHERWISE. SERIOUSLY.

2020 and Chrome has yet to decide upon a standard style for they inner form controls.
This is a date field with:
- a blue gradient "clear"
- a gray-bg spinner
- and a transparent bg calendar dropdown

2020!!!! I don't want to use huge date pickers anymore, Chrome!

The legacy codebase, episode 4584985948:
- outdated comment
- die parentheses space string no-space parentheses
- die AND exit, just to be on the safe side
- won't comment about the screaming boolean
- at least they used triple equals (and yep, that's a font ligature)

Because, definitely, size shouldn't matter.

Code description for the blind: if the size of this query is loved, then close the database and die.

This is probably VERY OLD, but why don't devRant supports Markdown? Having to upload (not paste or drag) code screenshots and having to UPPERCASE to yell or emphasize text feels... quite non-dev.
I found the bug repo and checked the Markdown issue has... almost three years.

I just came by the @highlight bot. Seriously? There are several layers of "wrong" with that hahah

Bonus: not very good UX to write a message, try to post it, and ONLY THEN get to know there's a time limit. This should show when you open the form, not when you submit it.... But I just sent a bug report on that, at least.

Bonus 2: if the char limit is 5k, why's the textbox so tiny on the web?

Mystery of the day: why some developers can't decide on a code style. Let's count:
- two types of brace placements
- three types of assignment spacing (with, without spaces, and aligned with extra space)
- two types of clause spacing
- mixed case in the first char of a variable for no apparent reason(?)
- bonus: unneeded parentheses

At least in ONE thing the person was consistent: no space between parameters!

WHY GOD.

"So, my company made a Mother's Day video, with photos from mothers around the company, with their children and stuff. A while ago they sent an email asking for replies with photos from those who wanted to participate, blah blah.

Then the video came out, and some people were missing. They complained.
HR then complained to IT Support that 'some emails didn't arrive'.
Support then replied to the ticket with screenshots of the person's own email inbox, with all the so-called missing emails.
HR then called back, apologizing for having screwed up with their own email inbox."

And this is another story of injustice with the poor IT department.
Or another story about people who can't properly manage their inboxes.
Or both. Your choice.

I just received it from a friend (I guess I should bring him into DevRant).

The legacy-PHP-project-to-pay-my-future-trip strikes again.

WHY NOT !empty($var) OMGGGGGGG

And here I am, back to DevRant, to post some crazy code from the new refactoring project I'm on.

And today in Laravel-land, how to take fluent APIs to the utmost consequences.

Better...? Seriously? All your lines got longer and you know have closures to run.

Ok, now seriously. Am I the only one bothered with all those fancy congresses and cool events that first open up the speaker list, rush you on buying the tickets, raise prices, and... AGES later, weeks before the event day maybe, they finally release what the heck they'll be speaking about?

I totally understand those who go to events mostly for networking, but c'mon event organizers, focus on the topics, no the person on the stage. They're just the mean to spread knowledge, NOT its own embodiment.

That moment when you want to stop reviewing bad coder's code. Or else, you'll go nuts.

My old mechanical keyboard broke, so I had to buy a new one. I'm Brazilian, so the local market for mech keyboards is either limited or very fancy (fancy as gaming keyboards).

So I got this amazing Logitech G610, which unfortunately is not sold with blue switches here, only brown ones. Very solidly built, well made, good extra keys and whatnot.

BUT OH MY, who ever thinks those LED effects are good for normal usage after 5 minutes of playing with them??? VERY distracting! <o>

That moment when code reuse makes you reuse reused code and you actually reuse a BUG.

You decide to go for code reusing when your boss asks: "Can you add an edit popup besides that 'add customer' popup button?". You do some little tweaks to the "new customer" code and it allows that to save over an existing entry, cool.

However, after a lot of time spent on reviewing the resulting PR, turns out there was a dormant bug on the code you reused, and it woke up with its new use.

That code was a bad copy-pasta from another, bigger form, which included a whole bunch of optional fields. As it was only used to save new entries, those now missing fields were simply being saved as empty. But as you reused that to save existing entries, you were now cleaning up all those optional fields without noticing.