|
I was there ;)
-Now, I have 35- ... in my time the changes was made by Microsoft, and really I'm a sucker for learn new things. "More things change, more stay the same" Despite all the noise that new stuff generate, exist timeless wisdom that permeant all the good things, so focus in answer the question "What good, timeless thing I can get from this?" Even if some tech fade with the time, you keep what do you learn. I start programming with FoxPro 2.5 in DOS, then Visual FoxPro 3. I still give credit to have used first a xbase language in how "good" I'm (in contrast with some people) doing database work, and have get OO instead of the people that chose Java... despite that Fox died long time ago. Everything will teach you something good. For example, Pascal/Delphi show me how is work with structure. Python, what look like to have simplicity & readability. Fox, this is how you do database, and Visual Fox: This is how you do OO. Delphi, this is how look like to have performance and RAD, and not need C/C++. Erlang, this is how multi-core development must/could be, Haskell, this is the crazy world of immutability (and this is functional programming).. etc. The mistake is follow a BIG. This burn me and others devs in my community when we follow whatever MS say. Don't do the things that a BIG tell you: Them are big, and their problems and resources are not yours. Instead, I focus in learn stuff practical for a solo developer or for a very small team (well, if you want to be part of a BIG, then do otherwise: ie: Understand the motivations and intentions of whatever you are listening). Don't attach to anything.. too much or for too long. Learn as broad as you can, yes... but don't commit until you need to. For example: I have read a bit about Erlang and GO. However, I don't do anything (in code) with that, because? I don't have a real, present requirement to use that tools. So, I don't get burned for that tech. I just read the websites, download the binaries, run some samples and get back to my actual, present, work. However I get aware that exist that things called Actor Model & CSP (and I google: CSP vs actor model) so I could use them, even with limitations, in python. Or just know that shared/state/mutation is bad for multi-task and passing non mutables messages is good, and use the libs at hand with that in mind. I have not committed to GO or Erlang, but still, have learning a good, timeless, practical thing that I could carry with me. So, not worry to get deep to soon, to fast. Learn broadly - look like is your thing!- but not worry about until the time to get worry come. |