All of the feedback here was really helpful.
As a followup, I wanted to let you know that my company is The Minerva
Project, and we've been given $25 million to build a university. After a
lot of back and forth about which technology we wanted to use on the
product side, we ended up settling o
On 1/7/13 4:02 PM, David Jacobs wrote:
What other tips do you have for convincing an employer that Clojure
makes good business sense? (Of course I've already told them about
domain-tailored abstractions, containing complexity, the ease of data
manipulation with a functional language, etc.)
Our company was recently formed in stages. The first stage did a lot of
research and decided we needed strong NLP tools and felt that the right
direction to go with the NLP was Python. I had spent 7 years doing NLP and
advised them on that aspect and had spent a lot of time doing NLP in
Python.
With the* team, that is. (Couldn't let that stay uncorrected heh. I hear
ya, Colin, re: sleep.)
On Tuesday, January 8, 2013 10:35:07 AM UTC-8, David Jacobs wrote:
>
> Thanks for all of the feedback and suggestions, everyone. To clear one
> thing up, I'm working at an early-stage SF startup, so t
Thanks for all of the feedback and suggestions, everyone. To clear one
thing up, I'm working at an early-stage SF startup, so the alternatives are
along the lines of Ruby/Python/Node, not Java. That said, I think these
arguments are great -- I'll definitely share them with team.
Cheers,
David
Many businesses are short term driven. The paradigm change so called "cost"
is a good way to spread fud. However, it may be hard to analyze this
solely on specific language features versus what benefits you may get.
Here, we had a mixed Java/JRuby/Clojure code base since we went in production
in
(please ignore the atrocious speling mistax in my previous post - not
enough sleep)
On Tuesday, 8 January 2013 12:05:11 UTC, Colin Yates wrote:
>
> I would ask "what problem would Clojure solve that the current technology
> X doesn't"? There are no invalid answers to this, but it is important t
I would ask "what problem would Clojure solve that the current technology X
doesn't"? There are no invalid answers to this, but it is important to
understand *why* you want to move to Clojure.
Perfectly valid answers might be:
- our domain is best solved with functional programming and we wan
> 2. What are good examples of complex domains that have been tackled with
> Clojure web apps and API layers?
>
At my company we have built an entire B2B platform that drives the exchange
of business documents for my country's largest company. Our first
production version was on Clojure 0.9 a
You say "an employer" without saying "our employer." Without a doubt, a *team*
must be convinced of Clojure first.
Assuming your team is convinced, then my argument is this: You will attract
better, smarter people by shifting your company toward Clojure. Avoiding it is
comfortable, but ignorin
On 8/01/2013, at 12:02 PM, David Jacobs wrote:
> 1. Would it be harder to hire if we built our apps with Clojure? More
> specifically: Hiring for people who know about or already love Clojure/FP
> is certainly a nice filter for talent, but is it too stringent of a filter?
Finding really good pe
On Mon, Jan 7, 2013 at 3:02 PM, David Jacobs wrote:
> 1. Would it be harder to hire if we built our apps with Clojure? More
> specifically: Hiring for people who know about or already love Clojure/FP is
> certainly a nice filter for talent, but is it too stringent of a filter?
> What percentage of
12 matches
Mail list logo
