“How” ages faster than “why”

Re:“How” ages faster than “why” by bungie4 on Friday January 27, 2017 @03:44PM (#13502494)

Sweeping statement from somebody whose been doing this for 35+ years. Learn core technologies. Not things built from those core technologies. Ya, you'll still have to learn the secondary stuff, but at least you have a really good idea what will NOT be around in 10 years.

[ Parent | on HN ]

Re:“How” ages faster than “why” by codemonkey2017 on Friday January 27, 2017 @06:00PM (#13503523)

But a sane person doing this would arrive at single logical solution: focus on server-side and ask company to hire a 27-year old JavaScript "ninja" to handle the front-end garbage framework of the month, while you are hacking OCaml/Scala/Haskell whatnot.

It always makes me chuckle when I see a job posting that clearly states it's JS front-end only: some old dogs know the trick ;-).

Pro-tip: re-write one of less significant systems in Node.js as a decoy!

[ Parent | on HN ]

Re:“How” ages faster than “why” by squirrelgod on Friday January 27, 2017 @04:11PM (#13502697)

What are some examples of core technologies?

[ Parent | on HN ]

Re:“How” ages faster than “why” by reboog711 on Friday January 27, 2017 @04:46PM (#13502983)

ColdFusion! It's been dead longer than I've been developing with it; but is still going strong. :ha, ha:

Seriously, though, I would not say there are any core technologies; but rather core programming concepts.

Variable memory management is one example. Knowing the difference between passing parameters by value, or by reference, when writing Lotus Notes applications actually helped me understand the difference between a variable assignment and creating a deep copy in JavaScript.

Less specific; If I had to guess--in 20 years; I'll still be working in technology that supports things like MVC(S), Dependency Injection, Singletons, Factories, etc....

Learning basic encapsulation techniques, and design patterns, is knowledge that will apply to lots of programming languages.

[ Parent | on HN ]

Re:“How” ages faster than “why” by xiaoma on Friday January 27, 2017 @10:20PM (#13504694)

Unix, git, networking, C, HTTP/HTML/CSS/JS, databases, blockchains, data structures, compilters, most things in a CS curriculum, etc...

[ Parent | on HN ]

Re:“How” ages faster than “why” by mooreds on Friday January 27, 2017 @04:33PM (#13502871)

I saw an amazing presentation at a ruby meetup about database indexes for developers (for example). Will see if I can dig it up.

[ Parent | on HN ]

Re:“How” ages faster than “why” by mooreds on Friday January 27, 2017 @11:24PM (#13504902)

Here you are. The slides aren't as good as the tall (as you'd expect) but still may be helpful.

Other core technologies (in my opinion): cookies, http, TCP/IP, caching.

[ Parent | on HN ]

Re:“How” ages faster than “why” by mooreds on Saturday January 28, 2017 @11:26AM (#13507146)

Ack, forgot the link: https://speakerdeck.com/heimir/databases-for-developers

[ Parent | on HN ]