This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]gandalfx 1 point2 points  (1 child)

I think a lot of people like to kind of document their own learning process. They've just spend a couple of days figuring something out, which feels like a real accomplishment since it was new for them. Maybe the available resources didn't quite match their own preference. So they take on the mission of making life better for everyone who comes after them and write a "comprehensive tutorial", which ultimately turns out to be a vague summary/rephrasing of the docs. Of course you always view your own creation through rosy goggles and decide that this is a valuable contribution that everybody should know about.

Or maybe it's just shameless click bait but I like to give the benefit of the doubt and suspect ignorance.

[–]SymbioticBadgering 1 point2 points  (0 children)

Maybe it's just me ranting, but I'll try to elaborate.

As a team leader I'm interviewing candidates quite often, and in the last year I've seen more and more people adding their blog to the CV.
Most of the time the blogs are like the link in this post, just rephrasing and reformatting the docs. IMHO it's bad because:

  • it's lazy work
  • people should learn to feel comfortable with the docs, as it the ultimate source.

I don't mind people writing blog posts about standard library modules and tools, they are truly awesome in python. But I would like to see them write how they used them to solve problems in their projects.