I don't disagree with the cost of context switch and I see value in limiting the work in progress, my argument is against focusing on throughput and measuring it by units of work, and particularly using estimates as the base of the measure
my problem is that all the manufacturing techniques I saw being attempted in software development assume each "unit" of production is somewhat equivalent but in my experience thats a very rare occurrence.
No, I know about pull, Toyota, Lean, and all that.
Still manufacturing and production of repeatable widgets...
Will you apply the same approach to make a bunch of mathematicians prove a theorem?
No! No! No! No! WHY??
We spend years saying "software development is not manufacturing", and now it the name of "agile" we allow all this to crept back.
Your team is not falling behind, your estimates were wrong!!
I think is just a matter of editing, the line "It even works with functions:" should probably say something like "It's even the same with functions" as before clearly stated that "let cat: Cat = Animal()" doens't work
If I'm not mistaken, considering the category of subtyping relationship you get exactly that: with the covariant functor you get (in Scala notation) if B <: A then F[B] <: F[A] and with the contravariant functor if B <: A then F[B] >: F[A]
agree, there's a difference between "believer" and "gullible".
And regarding 2), I suspect a sane dose of skepticism will do more to avoid bad decisions than drinking the company cool-aid
And in my experience, for every 10 issues that I realize it might crop up, I know there's also 10 issues that I DON'T realize it might crop up, so I take that into account
This.
Particularly with books, I can decide way faster by picking one, skim the back, index and pages than clicking though lists and "previews". Also, I can scan a whole bookcase in a couple of seconds, not just a list of tittles and tiny thumbnails.
Right now, for me, is a matter of bandwidth and latency
Sure, I understand, for some orgs, betting on Haskell is the best choice.
What I meant is that they're not using Scala in a small obscure project that nobody cares/know (as most early adoptions of languages are in big companies), they have a significant amount of code and their main business runs on it.
(I'm not talking about the ideal case/what I would like, I'm talking about what I've observed in my bubble )
If you consider Scala functional, I think it wins the popularity contest: used by startups and established companies (Linkedin, Twitter, Meetup, Verizon, Morgan Stanley, Autodesk, HuffPo, etc, etc...) and is not "we use it in a dark corner where nobody cares" and more like "betting the whole farm on it".
it might be pop sci, but the explanation I heard long time ago is:
creativity is boosted by beta brain waves, (associated with daydreaming)
Physical activities that don't fully engage your brain (walking, exercising, taking a shower, etc..) increment beta waves.
On the other hand, increased focus and alertness, is associated with alpha waves, coffee produces that effect thus reduces your creativity
I guess my point is if you learned to program 30 years ago using functional programming with dependent types and category theory, it must have been an awesome place to work/study, and I envy you.
Which university it was?