I don't plan to let it stop me....
(def typical-estimated-cost 50000)
(defn propose-cost-with [choice]
(if (= choice "Clojure")
( * typical-estimated-cost .7)
typical-estimated-cost))
> (propose-cost-with "Clojure")
...
> (propose-cost-with "Other")
...
In my opinion many large companies will chuck this out the door since
your cost does not represent the organizational cost, which depends
upon their ability to maintain your code [1] + no one ever gets fired
for picking Microsoft. For smaller companies not afraid of the dark,
or a start-up the above will work.
[1] "Object-oriented programming is popular in big companies, because
it suits the way they write software. At big companies, software tends
to be written by large (and frequently changing) teams of mediocre
programmers. Object-oriented programming imposes a discipline on these
programmers that prevents any one of them from doing too much damage.
The price is that the resulting code is bloated with protocols and
full of duplication. This is not too high a price for big companies,
because their software is probably going to be bloated and full of
duplication anyway." - Paul Graham http://www.paulgraham.com/noop.html
Tim
On Jul 6, 9:48 am, Thomas Kjeldahl Nilsson
<tho...@kjeldahlnilsson.net> wrote:
> Nick,
>
> I'm not doing proper paid work in Clojure yet, but I convinced my department
> manager that learning Clojure on company time was ok. So that's a start at
> least. :)
>
> I used the concurrency features of Clojure as a main selling point, as well
> as the value of getting started early on in promising young
> languages/platforms. ("high risk, high reward").
>
> --
> Med vennlig hilsen
> Thomas Kjeldahl Nilssonhttp://kjeldahlnilsson.net
>
> On Tue, Jul 6, 2010 at 10:50 AM, Nick Mudge <mud...@gmail.com> wrote:
> > One of the things I like about Clojure is it is a way to get lisp and
> > functional programming into workaday programming work; into the many
> > places and businesses that use Java.
>
> > I'd be very interested to hear stories or experiences of getting
> > Clojure into the workplace and how it was done. That is, convincing
> > customers and business people and other programmers that it is okay
> > that you start doing your work in Clojure in your job. And similar
> > such experiences.
>
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Clojure" group.
> > To post to this group, send email to clojure@googlegroups.com
> > Note that posts from new members are moderated - please be patient with
> > your first post.
> > To unsubscribe from this group, send email to
> > clojure+unsubscr...@googlegroups.com<clojure%2bunsubscr...@googlegroups.com>
> > For more options, visit this group at
> >http://groups.google.com/group/clojure?hl=en
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
