1. 12

  2. 4

    This blog post is interesting by describing an coherent approach, but lacks answering two important questions: better then what, better for whom?

    It’s obvious that the author only gives a rough handwave towards an unstructured approach to learning a programming language and moves on to calling theirs “better”. It’s also becomes clear from the text that this works better for the author. For example, the ability to learn on the job is not one everyone has.

    That’s completely fine, but this is not the better way to learn a new programming language, but a way that works for this author (and most likely for many others). It shouldn’t be framed as anything else.

    1. 3

      I give a specific set of criteria for how to make learning easier: motivation, specific goals, learning one thing at a time, not starting with blank slate, access to help from others. Meeting those criteria is what makes for a better learning experience.

      In general, I believe this is easier to achieve at work, though of course there are counter-examples. The important thing is matching those criteria.

    2. 3

      That’s how I learned Scala. It’s a great approach when you can do it but isn’t feasible very often.