3 ms·

Yep, surprisingly good. My only criticism is of the implied simplicity of the "backend". In reality the choices are vast with a huge long tail. That's because

by m_fayer 10y ago

Yep, surprisingly good. My only criticism is of the implied simplicity of the "backend". In reality the choices are vast with a huge long tail. That's because backend, as opposed to frontend or mobile, is really just good old fashioned general purpose computing with a sprinkling of networking and http middleware, and distributed systems glue.

oever 10y ago
Exactly. It troubles me that all four suggestions for the backend have very few inherent checks and leave a lot of room for security problems and other bugs. Personally, I prefer Yesod for the backend. It gives a very fast, static binary. It requires learning Haskell. The Haskell package Esqueleto ensures type safety all the way from the HTTP requests to the database tables. A URI parameter that is encoded to be a key on a table can only be used when querying that particular column or columns that are foreign keys to it.
- alexashka 10y ago
  This roadmap is for people who actually want to have a job at the end of their roadmap :)
  - flukus 10y ago
    A job at a trendy startup. If you want a job learn something used in regular business.
- jhall1468 10y ago
  > It requires learning Haskell. Which virtually nobody is using in production.
flukus 10y ago
And java and c# only get one little box each even though they're more widely used in the industry than node, ruby and python combined.
- 1ba9115454 10y ago
  In the context of a "Roadmap to becomng a web developer" that seems appropriate to me.
  - flukus 10y ago
    For what definition of web developer? For front end web stuff most of that is unnecessary. For web apps then Java and c# are still more widely used.
    - seangrogg 10y ago
      Just wondering if you have any sources to support the claim. I've been under the impression that dynamic languages have had the lion's share of back-end web development for a considerable span of time - from PHP to Rails to Django/Flask to Node. .NET is a blip by comparison, JSP/Spring isn't even that. Perhaps just a case of different perspectives?

by m_fayer 10y ago

oever 10y ago

Exactly. It troubles me that all four suggestions for the backend have very few inherent checks and leave a lot of room for security problems and other bugs. Personally, I prefer Yesod for the backend. It gives a very fast, static binary. It requires learning Haskell. The Haskell package Esqueleto ensures type safety all the way from the HTTP requests to the database tables. A URI parameter that is encoded to be a key on a table can only be used when querying that particular column or columns that are foreign keys to it.

alexashka 10y ago
This roadmap is for people who actually want to have a job at the end of their roadmap :)
- flukus 10y ago
  A job at a trendy startup. If you want a job learn something used in regular business.
jhall1468 10y ago
> It requires learning Haskell. Which virtually nobody is using in production.

flukus 10y ago

And java and c# only get one little box each even though they're more widely used in the industry than node, ruby and python combined.

1ba9115454 10y ago
In the context of a "Roadmap to becomng a web developer" that seems appropriate to me.
- flukus 10y ago
  For what definition of web developer? For front end web stuff most of that is unnecessary. For web apps then Java and c# are still more widely used.
  - seangrogg 10y ago
    Just wondering if you have any sources to support the claim. I've been under the impression that dynamic languages have had the lion's share of back-end web development for a considerable span of time - from PHP to Rails to Django/Flask to Node. .NET is a blip by comparison, JSP/Spring isn't even that. Perhaps just a case of different perspectives?