Why Podcasts Are My New Wikipedia —the  Perfect Informal Learning Resource

This was an interesting idea about podcasts-discovering content. However, it requires active participation.

I have been toying with the idea to invest time (and some resources) for one, but it doesn’t gel up. I, per se, don’t see any significant ground being covered in it. They represent a “fad” and an opinion.

But how is it possible to listen to podcasts at a programming job? Well, other than writing “if… else…” logics, there are actually a lot of “low thinking” tasks in modern software engineering, e.g., writing unit tests, refactoring code, copying & pasting code from Stack Overflow, tweaking CSS styling, tweaking config files for some server software, playing with 3rd party APIs, messing with HTML, configuring IDE, setting up dev environment, waiting for CI to finish, writing throwaway code to test out new technology, experimenting some low risk DevOps tasks on local dev or staging, testing coworker’s code locally for code review, manually doing QA for certain product features…

What happens if you wish to “bookmark” something? Take a clip of the file? Would you be taking notes?

I am still sitting on the fence and actively exploring this medium. Another issue is pay-day. It would be complicated to get users to pay, and it costs serious money to get started and get discovered.

There’s an overt concentration of the media happening via Facebook, Apple Music and Spotify (and other major corporations). They would then act as another layer of gatekeepers and “algorithmically decide” on your “interests”. As it is, I have been hearing and reading reports of YouTube videos being taken down for “perceived violation of terms of service”.

Always be on the medium that you can control. Period. There’s no point in chasing chimaeras and the masses.

via Why Podcasts Are My New Wikipedia —the  Perfect Informal Learning Resource | Listen Notes