4 ms·
Came here to say this. This kind of work irks me. No offense to the author, this is a widespread trend, not a single example. You write a whole blog-post on a
by fizixer 9y ago
Came here to say this.
This kind of work irks me. No offense to the author, this is a widespread trend, not a single example.
You write a whole blog-post on a topic and not mention Hanlon's razor. It is inexcusable that you didn't know about it. It was your job to do "literature survey" or some google search, or an intellectual discussion with a handful of people, (ideally all three of them, and more) before you blurt out a whole essay on a topic. And then in the essay you create an image of yourself originally coming up with such a brilliant idea.
This is just a piece of writing (and maybe I am a bit harsh but I'm just trying to point to a trend). We're on HN. This is way worse when it comes to coding/github projects:
You create some kind of code, put it on github, create a blog-post in some shiny flat/material design, grey font, maybe medium or nautil.us posting. And put that posting on tech forums, HN, linkedin, reddit, whatever.
And you fail to mention other projects preceding you on this same exact topic, much less discuss the pros and cons of your approach vs previous approach(es). Who knows you might've ended up finding out your own code was a complete reinventing of the wheel and completely redundant (maybe you're too afraid to find that out). (As an example, look at my recent comment about 'building your own linux' vs LFS [1]).
Creating something new and original is hard work. Part of that hard work is searching for existing efforts, related work, doing a literature survey, and whether or not they were successful, and how they compare/contrast with what you did or are going to do, and so on. Short of that, you're just contributing to the noise, the bloat, and the information overload of your content consumers.
What's worse. Not putting in the full effort works for these people too. More often than not, such people are looking for a quick karma-whoring to meet their immediate objective. A github coder is looking to put something quick on their resume, to land a job interview. It's the job of the interviewer or potential employer to hold such people accountable, but I doubt they do.
I don't know. This irks me to no extent. I'm big on minimalism. I spend a lot of my efforts making sure I don't say something that's already said ('say' = a piece or writing, or a piece of code). I don't like to contribute to information bloat. Maybe it's a self-defeating habit (i.e., if you don't say anything most of time, people think you have no talent, you're a nobody).
edit: It also reminds of NIH (not-invented-here) syndrome, something Google is known for. To be clear, it's worse than when it's done by noobs (e.g., for quick karma-whoring to land a job interview, at least they're desperate). When you're in a position of "status", you definitely can do better. It also reminds of the website LessWrong [2]. Those self-entitled wannabes have created a whole universe of philosophical/logical terminology for themselves without consulting the outside world and trying to find out whether "their ideas" originated elsewhere or not.
edit 2: In case anyone wondering, yes I am advocating the opposite of 'publish or perish'. And 'publish or perish' is part of the reason we have so much information bloat (on the internet, in the libraries, everywhere). And that's part of the reason why I say my approach is self-defeating.
[1] https://news.ycombinator.com/item?id=15030582 https://news.ycombinator.com/item?id=15030582
[2] http://lesswrong.com/ http://lesswrong.com/
- vvanders 9y agoOnce you've earned a bit of trust with the approach in the article the above post shows you how effectively to destroy any relationship you've now built.
- PeanutCurry 9y agoThat's a very low bar for an essay... at least in terms of length. I'd be surprised if this took long to write which isn't a criticism so much an expression of confusion as to why you called it an essay. It's also a little weird to call it inexcusable they didn't acknowledge Hanlon's Razor because it's hardly a common reference. Even the wikipedia page only gives two instances of Hanlon's razor being used and one of them is an acknowledgement that the general idea is very likely much older than the Jargon File glossary entry.
- fizixer 9y agoAs I said, I admit I might be a bit harsh. I took a slightly bad example of what I had in mind and went ahead and said what I wanted to say. The bulk of my comment is about the general trend, as well as the coding community.
- moccachino 9y agoI feel you, I do this so often :/
- komali2 9y agoDude, this is so negative, what gives?
- gasof 9y agoWhat's wrong with recreating and repackaging ideas? You'll gain a better understanding of the ideas, show others how to do the same (if you publish your efforts) and perhaps create new ideas through accidental new combinations or the concerted effort to integrate multiple existing ideas in an unusual way.
- 9y ago