Hacker News new | past | comments | ask | show | jobs | submit login

In Part 3 of the series[0] he hits home pretty hard. Often when I have an idea for something I also take that "opportunity" to learn something new or interesting, something I don't do at my day job

> Use Java/.NET/PHP/Rails/Perl/VB in your day job? Then Java/.NET/PHP/Rails/Perl/VB it is.

> I don’t care if you don’t know ASP.NET MVC and only know WebForms. Just use WebForms. Does that suck? Yes, it does. But do it anyways.

> Learn something else once you’re making money and you can afford to pay yourself the time to learn something else.

> I once spent three months learning production-grade Scala for a project I thought it would be awesome for. That project never got off the ground, and now I make $0.00 a year from having learned Scala.

...

> Take a lesson. Use whatever you know.

> The same thing goes for architectural concerns.

> Microservices? STOP.

> Crazy ass front-end stuff with ReactJS or Angular2 with TypeScript? STOP.

> How about some hot new NoSQL platform? STOP.

> What about going cloud with AWS or Heroku? STOP.

I've learned a lot, made little, and most of my extracurricular activities/skills have basically been funneled back into my day job.

[0]: https://hackernoon.com/make-it-rain-building-an-mvp-for-fun-...




> Use Java/.NET/PHP/Rails/Perl/VB in your day job? Then Java/.NET/PHP/Rails/Perl/VB it is.

Another way to put this (that I've seen on HN a handful of times so bear with me) is that it depends what the product is for?

If you only know C# but want to learn Go:

- Do you want to make money? Write it in C# - Do you want to learn a new language, struggle, (most likely) produce little value, and scrap the whole thing a half dozen times in two months? Write it in Go




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: