I don't think that's a fair assessment.

He talked to a bunch of experienced devs and summarised their opinions. And then he shared his own opinion on the matter.

Nothing wrong with that.

Nothing wrong, but also nothing worth discussing. It doesn’t qualify as a good research or an opinion of a subject matter expert - just few banalities in a popular genre of provokative tech blog post.

Care to attack the arguments next?

He didn't publish fact. He published opinion.

The context of that opinion is highly relevant and not qualified in the article or a bio.

His insta page listed in the bio however gives an insight into his experience.

So yes, I feel perfectly content to raise his lack of experience.

I'm fed up of noise posing as insight.

Its always like this. Last month the article was about how OOP was useless and a waste of billions of dollars, yet the author had like 2 years of experience as a Php developer (in 2019?). It didn't stop 2 of my sub par coworkers from sharing the article and acting like the author had any creds or experience at all to be saying such things. Generally I never read blog posts from no name people claiming industry standards should be destroyed. Its just a pointless exercise.

The experiences of beginners are as valid as anybody else's.

It creates an unfriendly culture if people are told they can't talk about their frustrations and challenges without having x years of experience first.

>The experiences of beginners are as valid as anybody else's.

In certain situations they may be even more valid. But when it comes to software processes you really need to have lived and breathed them in order to mount a credible argument.

>It creates an unfriendly culture if people are told they can't talk about their frustrations and challenges without having x years of experience first.

Nobody is denying this person the right to talk about their frustrations.

>Nobody is denying this person the right to talk about their frustrations.

bjornsing's comment is implicitly highly critical of them doing so.

The headline title is beyond a "frustration", it reads like a universal assertion.

Something like "I dont like TDD" or "I struggle with TDD; here are my thoughts" would at least ground us in our expectations.

The experience of a beginner with a certain tool is quite important. E.g, if Linux is not user friendly to newbies something could be done about that.

But some tools require expertise and a beginner might not get the entire picture yet. E.g, if someone with 1 year of physics experience claims Quantum Mechanics to be dumb, is that a valid opinion?

It might be. Your point is that it's not worth your time to consider that someone's opinion.

I'm not going to take any opinion seriously with a headline like that.

This isn't some conceptually difficult thing like quantum mechanics, it's something designed to make software easier to build.

If it doesn't in fact do that for this person it's totally valid to mention that.

It's valid to have an opinion on something, another thing is having a well-founded opinion. I love vim and my opinion is that it's better than Emacs.

But I used VIM for a decade and Emacs for 6 months.

Is anyone going to take my opinion on Emacs seriously, knowing that these tools take time to master?

> Is anyone going to take my opinion on Emacs seriously, knowing that these tools take time to master?

Maybe not, but you're welcome to publish an essay on what you think.

True, and everyone is welcome to voice their opinion. I'd encourage that, but it still doesn't make it 'valid' for a larger audience. :)

I think the idea is to avoid calling something "dumb" when you have not enough understanding and experience in it to pass such arrogant judgement.

>experiences of beginners are as valid

What does this even mean? Their experiences are valid?

I find it amusing to read posts like the authors. I bet he also does not even use Agile Methodology lol ;-)