<div dir="ltr"><div><div><div>That's what they *say*, anyhow. In practice though, most managers have all sorts of other concerns, some of which are blown way out of proportion or sometimes completely irrational. The trick is to address these too.<br>
<br></div>One of the biggest things is the manager's version of premature optimization: worrying about scale way too early. Not just scaling technologically (although that might come up) but also hiring and training lots of developers. All too often, they think that training developers in a new language will be too difficult and that they need a market of developers comparable to Java to be able to hire for their team.<br>
<br></div>The funny thing is that this is almost the opposite of what happens in practice: using a language like Haskell actually makes it *easier* to hire good developers. Haskell motivates programmers to apply more actively and self-select, which is nice. This thread[1] has some testimony that might be useful to show that hiring Haskellers is actually easy. <br>
<br>As far as training goes, it's also not too difficult. The IMVU blog post mentioned earlier covers this:<br><br>> "Today, training an engineer to be productive in our Haskell code is not
much harder than training someone to be productive in our PHP
environment. People who have prior functional programming knowledge
seem to find their stride in just a few days."<br><br></div><div>Their experience is that Haskell is actually pretty easy to teach if you have strong opinions about style, idioms, libraries, extensions and so on. The clear plan for what to cover is important. They covered this idea in their BayHac[2] talk, which might be worth a look.<br>
<br>[1]: <a href="https://groups.google.com/forum/#!topic/haskell-cafe/-HzmH5CVehM">https://groups.google.com/forum/#!topic/haskell-cafe/-HzmH5CVehM</a><br>[2]: <a href="https://www.youtube.com/watch?v=gl3expkos4Q#t=483">https://www.youtube.com/watch?v=gl3expkos4Q#t=483</a><br>
</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 25, 2014 at 8:55 AM, Carter Schonwald <span dir="ltr"><<a href="mailto:carter.schonwald@gmail.com" target="_blank">carter.schonwald@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Well said. If using a tool makes cheaper / faster to deliver a given set of features/level of quality, next week, business won't care how, just that it is. <div class="HOEnZb">
<div class="h5"><span></span><br><br>On Friday, July 25, 2014, Brandon Allbery <<a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Jul 25, 2014 at 7:25 AM, Закиров Марат <span dir="ltr"><<a>marat61@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I need to convince group of managers that Haskell is cool.</blockquote></div><br>This sounds like getting off on the wrong foot from the start; managers don't care about cool, they care about getting stuff done.<br clear="all">
<div><br></div>-- <br><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a>allbery.b@gmail.com</a> <a>ballbery@sinenomine.net</a></div>
<div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div>
</div></div>
</blockquote>
</div></div><br>_______________________________________________<br>
Haskell-Cafe mailing list<br>
<a href="mailto:Haskell-Cafe@haskell.org">Haskell-Cafe@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
<br></blockquote></div><br></div>