How to Sell Excellence
docs.google.com
How to Sell Excellence
1–10 of 124 posts
Re: How to Sell Excellence
#2I still find it odd that Google Docs cannot handle a large number of people looking at a file.
"Wow, this file is really popular! Some tools might be unavailable until the crowd clears."
Even with the tools turned off there should be a way to simply view.
Re: How to Sell Excellence
#3I still find it odd that Google Docs cannot handle a large number of people looking at a file. "Wow, this file is really popular! Some tools might be unavailable until the crowd clears." Even with the tools turned off there should be a way to simply view.
That's what it is saying? You can't use the tools, only view right now.
Re: How to Sell Excellence
#4At the risk of sounding inflammatory... I would be willing to believe that purely functional languages are the "one true way" if there were even the slightest bit of empirical evidence to support it. But where are all the successful large scale projects built with Haskell (or Clojure or whatever)?
The biggest FP project I was aware of was Twitter using Scala and they ended up completely backing away from it. Yikes.
The only other popular site that springs to mind is Hacker News, and frankly, it sucks. It's practically the Hello World of discussion forums.
The truth is, at the end of the day almost everything is being built with Java, Python, Ruby, or JavaScript. Can you really blame the product owners for being wary of writing their whole product in a functional language?
Re: How to Sell Excellence
#5Good stuff, but doesn't Hack language also solve this need? I'd guess a more likely route is PHP shops switching to Hack than to Haskell.
Re: How to Sell Excellence
#6I disagree with the presentation a lot.
* There's no widely used successful system written in Haskell. Yes, there's GHC, Agda, Idris and other research tools but they are marginal.
* It's untrue that mutable state is the main reason of problems with code. You can manage state in Java and C# in any other language.
* Haskell programmers are usually smarter than Java programmers, but they often don't want to work on tasks which they aren't very interested in, which are almost non existent, or have little business meaning.
* Haskell, actually has a lot of design flaws. The worst of them is the scope of record fields.
Re: How to Sell Excellence
#7At the risk of sounding inflammatory... I would be willing to believe that purely functional languages are the "one true way" if there were even the slightest bit of empirical evidence to support it. But where are all the successful large scale projects built with Haskell (or Clojure or whatever)? The biggest FP project I was aware of was Twitter using Scala and they ended up completely backing away from it. Yikes. T…
Clojure Success Stories
Re: How to Sell Excellence
#8I disagree with the presentation a lot. * There's no widely used successful system written in Haskell. Yes, there's GHC, Agda, Idris and other research tools but they are marginal. * It's untrue that mutable state is the main reason of problems with code. You can manage state in Java and C# in any other language. * Haskell programmers are usually smarter than Java programmers, but they often don't want to work on tas…
> You can manage state in Java and C# in any other language.
Yes but I think that the "value prop" with Haskell is that it forces everyone to abide to a certain discipline with respect to type safety and immutability.
> they are marginal.
Relative to what/whom? All the projects you have quoted are really successful and directly or indirectly pushed mainstream software engineering forward (i.e safer style).
Re: How to Sell Excellence
#9I still find it odd that Google Docs cannot handle a large number of people looking at a file. "Wow, this file is really popular! Some tools might be unavailable until the crowd clears." Even with the tools turned off there should be a way to simply view.
That's what it is saying? You can't use the tools, only view right now.
There was no information loading at all when the link first appeared .. only the warning.
Re: How to Sell Excellence
#10Personally I find selling excellence easiest without sweeping negative generalizations like they claim in their summary slides[1]. Presentation feels more like a blame game about how people have done things wrong in the past than highlighting success and features of Haskell.
[1] From slide 152:
- Old East Coast tech culture valued quality and
correctness, weak on practicality and communication.
- The new California-centric one emphasizes commercial practicality and communication
but doesn’t give a damn about software quality or excellence.