Bashing our fellow developers for using <insert tech> is not cool. This especially became overboard with PHP. And yes I've been guilty of this, despite using PHP before for so long as well.
https://justmarkup.com/log/2018/...

@Mousey oh I might came off like I was complaining about people bashing me. They don't and I wouldn't mind much either.
This is as much a message to myself as to others

Well this is the thing my brotha.

Our field is full of elitist fat(or really whimpy) fuckers that would always shit on the tools that others like in order to feel superior.

This is why I heavily dislike developers most of the time.

For real!! Let people like what they like nothing matters

I'll join in on the fun when people bash tech I don't like, but there's a fine line from judging the people who happily and successfully use it.

One of my worst foot in mouth moments was when I was talking with someone about their work and found out they used some years old framework I don't like, and I let slip "ha why not [this new and better thing]?".

It might not seem like much, but it was only while I was given a thorough justification that I realized I had criticized them rather than the tech. Don't do that.

Different pieces of technology belong in different places. If the technology won’t scale (it won’t work), and the project is a huge one, I will let others know, by asking:

what tools have you looked at and what are their pros and cons. Can I add tool x to your list? And take time to help.

If it is a small project, it is easy to rewrite when the time comes (it needs features or fails to scale).

Individuals and interactions > processes and tools
Working software > comprehensive documentation

Both are important. The one on the left is more important.

I also believe working software > processes and tools. But it is cleaver that that is not in the agile manifesto.