3 ms·
Some good thoughts in here. However I feel like when I learned Haskell (which was actually my first serious foray into programming) the hard parts were not this
by kmicklas 9y ago
Some good thoughts in here. However I feel like when I learned Haskell (which was actually my first serious foray into programming) the hard parts were not this high level functional language philosophy stuff, but rather not knowing how to appropriately use the tooling. It took me years to finally write cabal files, QuickCheck tests, Traversable instances, etc. In that regard, this guide has been immensely useful:
http://dev.stephendiehl.com/hask/ http://dev.stephendiehl.com/hask/
- brudgers 9y agoI've had very similar experiences. I took a Scala course on Coursera back in 2014 and at the end I realized I couldn't really write a Scala program because the course had provided all SBT files for everything...and because they enabled all sorts of functionality related to autograding, they were impenetrably complex in addition to the necessary complexity of a build tool (which requires a willingness to read a technical manual that assumes I high level of experience and sophistication). A lot of the difficulty is that it is relatively easy for a two pizza team to have enough experience and knowledge to collectively figure out how to get all the moving parts moving more or less in the right direction at more or less the right time. For an individual, it's always going to take years to achieve the equivalent knowledge of a team after six months.
- deleted 9y ago[deleted]