Quote: (12-26-2017 04:12 AM)roid Wrote:
HackerNews and lobste.rs are more like news sites, I think you should not count it as work. However, I am interested to know how much time you devote to learn new language in case the current language you're working on is fading away.
The time to learn a new language decreases exponentially once you are familiar with a few languages from different paradigms. Becoming an expert in a particular language takes a lot of time, of course, but you don't need to be an expert to have it in your toolbelt. Reading a few articles about the language, reading a syntax reference, studying some source code and writing a small test project is enough to get started and can be done over the course of a weekend. If you don't want to do it in the weekend, you can break it down over the week. Once you have done that, you can decide whether to drop it or to invest more by writing a larger project or looking for work in that language. I believe this is the way most seasoned programmers learn new languages. They don't sit down every day and study and practice for a few hours until they're good with the language. They eat around the edges using the accumulated knowledge that they already have.
HackerNews and lobste.rs are not just news websites. They're more like reddit in the sense that anything can be linked and upvoted. They're important tools from a market perspective because they give you an insight on the problems being faced by people in the industry and the approaches they're using to solve them. There are a lot of articles in HN talking about a resolution to a particular problem using a certain language or framework. In addition, HN has lots of introductory articles about new technologies that are coming up. It's easy to pick up the trends when you're reading those every day.
For example, recently there was a lot of traction in an article about the Red programming language. I had never heard about that language before, but the article was interesting. I didn't learn Red from reading it, but I learned something about Red. And it enticed my interest enough to click through the website and see code samples. Now I know what Red looks like and have an idea about how it works. Searching for red language in HN tells me this is not the first time the community has been vocal about Red in the last couple of years. That tells me Red should be on my radar. Maybe it will never be more than a curiosity, but maybe it will amount to something. If I start seeing articles about people using Red to solve real problems, I might decide to explore it further and spend a Saturday writing something in Red. Then I'll really know.
Of course I can not count this as work, but it isn't purely entertainment either. It's learning about things that interest me but that are also useful for my work. That's why I said this isn't a problem as long as you like what you're doing.