4 ms·

But usually you missed them for a reason. They just aren’t directly relevant to you. ... but I made a technical decision because of an idea on hacker news. Yo

But usually you missed them for a reason. They just aren’t directly relevant to you. ... but I made a technical decision because of an idea on hacker news. You should have researched that decision outside of hacker news. Less aggregate time spent.

deleted 6y ago
[deleted]
heisenbit 6y ago
There is a lot that I know which was relevant but is not anymore. A large percentage of knowledge needs constant replacing and often I do not know with what until I‘m exposed. HN gives me exposure. It is part of my solution to staying on top of developments. It does not provide answers to questions I have but to questions I should have had.
- shaklee3 6y ago
  Excellent way to phrase it. For lock of a better way of saying it, you don't know what you don't know. You can become comfortable with certain things, but the pace at which stuff moves in this industry makes you stale if you don't at least look at the trends every few months or so. you could always be in the camp that says you should look at new trends, but I'm of the complete opposite viewpoint. Some of these new trends which people love to hate ended up working really well in production for me, and being on HN gave me the exposure I needed to them. It also gives you people that have used these technologies in production, and have opinions on them that might be helpful.
shaklee3 6y ago
Of course I researched the decision outside of HN. But just the superficial exposure you have to so many different things that you wouldn't have by just browsing around is invaluable. And just by hearing something like a name can take you on a tangent that can be very fruitful. Case in point: I'm very familiar with Kafka, and the discussions on here usually lead to hinting about new technologies that you may not hear of just by reading a Kafka threat. Things like NATS, Jetstream, liftbridge, pulsar, and the list goes on. Having that kind of exposure just knowing that alternatives are out there, and people having real-world experience with them is really useful.

deleted 6y ago

[deleted]

heisenbit 6y ago

There is a lot that I know which was relevant but is not anymore. A large percentage of knowledge needs constant replacing and often I do not know with what until I‘m exposed. HN gives me exposure. It is part of my solution to staying on top of developments. It does not provide answers to questions I have but to questions I should have had.

shaklee3 6y ago
Excellent way to phrase it. For lock of a better way of saying it, you don't know what you don't know. You can become comfortable with certain things, but the pace at which stuff moves in this industry makes you stale if you don't at least look at the trends every few months or so. you could always be in the camp that says you should look at new trends, but I'm of the complete opposite viewpoint. Some of these new trends which people love to hate ended up working really well in production for me, and being on HN gave me the exposure I needed to them. It also gives you people that have used these technologies in production, and have opinions on them that might be helpful.

shaklee3 6y ago

Of course I researched the decision outside of HN. But just the superficial exposure you have to so many different things that you wouldn't have by just browsing around is invaluable. And just by hearing something like a name can take you on a tangent that can be very fruitful. Case in point: I'm very familiar with Kafka, and the discussions on here usually lead to hinting about new technologies that you may not hear of just by reading a Kafka threat. Things like NATS, Jetstream, liftbridge, pulsar, and the list goes on. Having that kind of exposure just knowing that alternatives are out there, and people having real-world experience with them is really useful.