4 ms·
This is good advice, but it's a bit hard to act on. How does one know when to leverage their existing skills to build something vs spending time learning someth
by throwaway1890 12y ago
This is good advice, but it's a bit hard to act on. How does one know when to leverage their existing skills to build something vs spending time learning something new and using it to build something (which might not pan out due to lack of experience with that technology, and which will certainly take longer than using what is familiar)? For me, the biggest investment is that of time... and while he provides ideas for small things to do, in the end one really needs to use a technology to grasp it (which he does say).
I'm a beginning programmer working on a small team. We won't be hiring anytime soon so many of the things he suggests aren't options. I'm lucky in that I've been able to learn a lot of things across the stack. However, our main language is Perl, which isn't the most marketable language anymore.
I have an idea for a useful little site -- something that will look good on a resume, but not something that I can imagine becoming a big money maker of any sort. Do I use my main strengths, my familiar technologies (such as Perl and SQL), to write the site? Or do I choose something that might be an up-and-coming technology (like Node.js or Clojure) even if I can't really find any jobs in my area for them?
I do love learning. I spend downtime at work learning new things, but my time outside of work to actually build stuff is limited. I'm getting a bit burnt out on learning new languages and frameworks... I've wandered between Perl, Elixir, Haskell, Clojure, Racket, Javascript/Node, and any number of frameworks for them. I just want to make something solid, but I'm worried that using my Perl skillset will be more of a short term than a long term gain.
I know there's probably no easy answer to this question. But it seems to me that it's better to have made something and launched it (even if it doesn't use the sexiest tech) than to have something half-finished stagnate because I don't have the time to learn the ins and outs of the quirks behind some new tech. Does anyone have any insight into handling this? Thanks.
- sleazebreeze 12y agoI've had the same quandary as you. Mainly work with Java and Javascript at work, so I wanted to add a purely functional language. I flirted with Haskell, Scala, Node, Scheme and Clojure and eventually settled on focusing on gaining a better understanding of functional programming with Clojure because it has a familiar platform (JVM), syntax I can understand (sorry Haskell and Scala) and it seems like it's going places. Last year, I maintained a focus on Java and JS because I'm still intermediate level with those and didn't want to distract myself with other languages and paradigms. That was a good choice. For this year, I've made a commitment that any side projects I do, I do in Clojure. I cheated and started in 2014, but I am liking this way of focusing on a language for a year and doing everything in that. Maybe once I have more familiarity with more languages, I will feel more comfortable using the appropriate language to solve a particular problem. However, isn't that part of learning? Using a hammer on nails, screws and bolts and figuring out what the hammer is good at and what it isn't?