4 ms·

I dont know, I seem to learn a lot more from different programming languages, frameworks and libraries. I could get deep knowledge in Java but wouldn't learn h

I dont know, I seem to learn a lot more from different programming languages, frameworks and libraries. I could get deep knowledge in Java but wouldn't learn how to deal with concurrency from functional programming until maybe Java Lambdas and thus use some kind of object oriented hacking with locks, or a myriad of other useful methods and thinking that would be either much harder or un-doable in Java that has added to how I deal with code. On the other hand, that could be the mark of a beginner so I might be mistaken.

dkasper 8y ago
I don’t think I could say it better than Rich in the last paragraph: > And, you need to be careful to recognize the actual game involved. Programming mastery has little to do with languages, paradigms, platforms, building blocks, open source, conferences etc. These things change all the time and are not fundamental.
- forkLding 8y ago
  I disagree because even the Actor Model was inspired by Lisp and Physics. Why are we so against different ideas in programming? Theres no pure land ivory tower in development, whatever works will work because they are tools to a craftsman, you can't compete with new tools like the cloud deployments if you're still fighting with an old school server under the same load and achieve cost efficiency, programmers need to constantly relearn and reshape to keep up with the trades and the times. I learn new programming languages to keep up with the market because the market isnt fair and loves hyped up new stuff and to also provide for myself and family, if I stayed with the programming language I had from high school, I might be a master in Visual Basic but also likely live not as well. In the end, its people's choice and tradeoff I guess. Unless of course this person can supply a empirical causation, he isnt right.
jkoudys 8y ago
I've frequently found that when I go back to code I've written long ago, the new languages/libraries/patterns I've learned about since could have helped me back then. I used to be terrible at templating (presentation) many years ago. Like a lot of people I took it for granted, and considered it an afterthought compared to more "serious" work like writing backend business logic or data modelling. After hitting some frustrations writing a frontend, I started learning all I could to avoid writing those same giant html-templates rife with microlanguage, inline for loops, hugely nested conditionals, etc. I started reading up on xslt and a lot of the reasoning behind it. While anything XML is torturous to work with for a variety of reasons, a lot of the lessons I learned about writing good xslt (e.g. defining larger templates as composed of smaller ones, preferring `apply-templates` to 'map' datasets over explicitly for-looping over them) transferred to any other language. Eventually this got my interested in facebook's hacklang and its XHP syntax, which led me directly to React (jsx felt like XML that didn't scold me every time I forgot to spend 300 characters writing namespaces at the top) once it came out, and I was one of the first adopters. Nowadays, I feel like I could probably go back to es3 and use plain functions, concatenation, and array methods and write better templates than I could using any fancy lib before, since I actually understand what I'm doing.
- forkLding 8y ago
  I can see what you mean, going to stop arguing on the internet anymore, realize its both addicting and embarrassing, any way to delete comments?

dkasper 8y ago

I don’t think I could say it better than Rich in the last paragraph: > And, you need to be careful to recognize the actual game involved. Programming mastery has little to do with languages, paradigms, platforms, building blocks, open source, conferences etc. These things change all the time and are not fundamental.

forkLding 8y ago
I disagree because even the Actor Model was inspired by Lisp and Physics. Why are we so against different ideas in programming? Theres no pure land ivory tower in development, whatever works will work because they are tools to a craftsman, you can't compete with new tools like the cloud deployments if you're still fighting with an old school server under the same load and achieve cost efficiency, programmers need to constantly relearn and reshape to keep up with the trades and the times. I learn new programming languages to keep up with the market because the market isnt fair and loves hyped up new stuff and to also provide for myself and family, if I stayed with the programming language I had from high school, I might be a master in Visual Basic but also likely live not as well. In the end, its people's choice and tradeoff I guess. Unless of course this person can supply a empirical causation, he isnt right.

jkoudys 8y ago

I've frequently found that when I go back to code I've written long ago, the new languages/libraries/patterns I've learned about since could have helped me back then. I used to be terrible at templating (presentation) many years ago. Like a lot of people I took it for granted, and considered it an afterthought compared to more "serious" work like writing backend business logic or data modelling. After hitting some frustrations writing a frontend, I started learning all I could to avoid writing those same giant html-templates rife with microlanguage, inline for loops, hugely nested conditionals, etc. I started reading up on xslt and a lot of the reasoning behind it. While anything XML is torturous to work with for a variety of reasons, a lot of the lessons I learned about writing good xslt (e.g. defining larger templates as composed of smaller ones, preferring `apply-templates` to 'map' datasets over explicitly for-looping over them) transferred to any other language. Eventually this got my interested in facebook's hacklang and its XHP syntax, which led me directly to React (jsx felt like XML that didn't scold me every time I forgot to spend 300 characters writing namespaces at the top) once it came out, and I was one of the first adopters. Nowadays, I feel like I could probably go back to es3 and use plain functions, concatenation, and array methods and write better templates than I could using any fancy lib before, since I actually understand what I'm doing.

forkLding 8y ago
I can see what you mean, going to stop arguing on the internet anymore, realize its both addicting and embarrassing, any way to delete comments?