Social media on programming low quality
Content:
I cannot be the only one seeing this. The average quality of technical content posted to social media is very low today.
Article after article full of errors and misunderstandings so they are totally useless is being published at a high rate.
Not sure what is going on. Beginner copy pasting material without understanding it and therefore getting it wrong? Lazy beginners asking some AI tool to write an article?
Anyway it is not good. We could end up destroying the learning of an entire generation of developers. They get fed so much low quality infomation that they never learn.
And what happen with LLM's based on material availale on the internet when the majority of content is crap?
Some characteristics immediatetly giving away an article of low quality:
- Use of OOPS instead of OOP for object oriented programming - I have no idea where that OOPS comes from, but if OOPS is used then there is 99.95% probablity
that the content is crap
- Wrong case of keywords and names for a case sensitive language - that reveals lack of practical experience and poor review process, which means that there are many other problems
- Recommendation of using non-synchronized methods (Java: ArrayList, HashMap, StringBuilder; .NET: List, Dictionary) for singlethreaded use and
synchronized methods (Java: Vector, Hashtable, StringBuffer ; .NET: ArrayList, Hashtable) for multithreaded use - best practive for almost two decades has been to
always use the non-synchronized methods and add higher level synchronization if needed (synchronized only prevents internal data corruption - it rarely
ensure correct and predictable result)
- Claiming how great the advanced singleton lazy loading solutions are - they practically never provide any value over simple solutions
- Examples of "junior code" with N clean readable lines and "senior code" with N/2 unreadable lines of code using some advanced language feature, where
reality is the opposite - juniors do the advanced solution, seniors do the simple solution that they know the future maintenance programmer can understand in 2 seconds
Comments: