I understand what the blog post is trying to convey and I agree that programming is a wonderful craft, allowing anyone who knows how to code an amazing world of possibilities.
However, the way the blog post tried to convey this, it falls down for two reasons:
1 ) If you were someone who had studied media rather than programming you could film your own 'news' channel and upload it to youtube if you thought you could disrupt the news industry. This being the equivalent of sitting in your bedroom at home making a site or an app the way you want to. Thus this freedom to express your ideas does not just apply to programmers.
2 ) Just assuming that the news industry team don't know what they're doing and as a new hire media intern you would know how to fix it for them if only they let you, is almost like being a new intern at a software house and expecting to go in and tell everyone they need to change their methods or practices because you know best.
I expect you'd get similar resistance to making them change, as in both examples you as an intern have little experience compared to the people in either industry. What from an outside observer (or new hire) may seem dumb, perhaps is the most effective methods after years of A / B testing by the people within that organisation.
This article makes me wish HN had a downvote button for submissions - its some upbeat crap with an example that is debatable. It caries neither novelty nor intellectual investment.
However, the way the blog post tried to convey this, it falls down for two reasons:
1 ) If you were someone who had studied media rather than programming you could film your own 'news' channel and upload it to youtube if you thought you could disrupt the news industry. This being the equivalent of sitting in your bedroom at home making a site or an app the way you want to. Thus this freedom to express your ideas does not just apply to programmers.
2 ) Just assuming that the news industry team don't know what they're doing and as a new hire media intern you would know how to fix it for them if only they let you, is almost like being a new intern at a software house and expecting to go in and tell everyone they need to change their methods or practices because you know best.
I expect you'd get similar resistance to making them change, as in both examples you as an intern have little experience compared to the people in either industry. What from an outside observer (or new hire) may seem dumb, perhaps is the most effective methods after years of A / B testing by the people within that organisation.