Re: Clojure Truck Factor

2015-08-18 Thread Jorge Branco
It surely seems so, I don't deny everyone of us *feels* that way. But you can be sure that that's always easier than having to work on code you do not know with business logic you also do not know of and with all its bugs and quirks of its own. On Mon, Aug 17, 2015 at 6:29 PM, Gary Verhaegen wrot

Re: Clojure Truck Factor

2015-08-17 Thread Andrew Chambers
>From my outside observation you would need to hit Rich Hickey, Timothy Baldridge, David Nolen, Stuart Halloway + other cognitect staff all at once. This wouldn't exactly "kill" clojure. But may put it into maintenance only mode for a while. On Saturday, August 8, 2015 at 4:21:40 AM UTC+12, Gu

Re: Clojure Truck Factor

2015-08-17 Thread Colin Yates
Ha - amen to that! Gregg Reynolds writes: > On Aug 17, 2015 12:29 PM, "Gary Verhaegen" wrote: >> >> On 17 August 2015 at 07:25, Jorge Branco > wrote: >> >> If a file has not been touched in two years, does it really >> >> matter who wrote it? > ... >> >> It may be just me and my bad memory, but

Re: Clojure Truck Factor

2015-08-17 Thread Gregg Reynolds
On Aug 17, 2015 12:29 PM, "Gary Verhaegen" wrote: > > On 17 August 2015 at 07:25, Jorge Branco wrote: > >> If a file has not been touched in two years, does it really > >> matter who wrote it? ... > > It may be just me and my bad memory, but I'm not sure I would have an > easier time than anyone

Re: Clojure Truck Factor

2015-08-17 Thread Gary Verhaegen
On 17 August 2015 at 07:25, Jorge Branco wrote: >> If a file has not been touched in two years, does it really >> matter who wrote it? > > I think that depending on the project and the kind of file, it does make a > difference. One of the primary problems our team faced when working on a > large b

Re: Clojure Truck Factor

2015-08-16 Thread Jorge Branco
> If a file has not been touched in two years, does it really matter who wrote it? I think that depending on the project and the kind of file, it does make a difference. One of the primary problems our team faced when working on a large brownfield enterprise project spanning several (distributed)

Re: Clojure Truck Factor

2015-08-16 Thread Mars0i
Gary, Nice point about Rich's role in maintaining the direction and sensibility of Clojure. I sometimes complain about some choices that have been made for the language, but overall, it's the clear, sensible design that makes Clojure a pleasure to use. -- You received this message because yo

Re: Clojure Truck Factor

2015-08-14 Thread Gary Verhaegen
Hi Guilherme, I am not a Clojure developer (I only use it), so maybe I'm speaking out of line. I would first like to thank you for the initiative; as an industry, I believe we direly need more quantitative, scientific studies of our practices, so I'm really happy to see this. There is of course a

Re: Clojure Truck Factor

2015-08-12 Thread Guilherme Avelino
Hi Alex and Leif, Thank you for the comments. We really appreciate the feedback.Our research is under development and the answers we are receiving for this survey will help to better interpret the results and improve our approach. Regards, Em sexta-feira, 7 de agosto de 2015 13:21:40 UTC-3, Gu

Re: Clojure Truck Factor

2015-08-08 Thread Leif
Hello, Guilherme. First, let me briefly answer your questions: a) yes b) no c) As Alex said, there is a large clojure community. Also, there are a significant number of companies using clojure for production software. I think that would ensure that clojure stayed alive (but maybe not thriving)

Re: Clojure Truck Factor

2015-08-07 Thread Alex Miller
Hi Guilherme, As the language creator and owner, Rich is obviously a critical part of the team that directs and maintains Clojure and if he was no longer involved there would be a significant impact. That said, Clojure is backed by a company (Cognitect) and a community of 10k's of developers an

Clojure Truck Factor

2015-08-07 Thread Guilherme Avelino
As part of my PhD research on code authorship, we calculated the Truck Factor (TF) of some popular GitHub repositories. As you probably know, the Truck (or Bus) Factor designates the minimal number of developers that have to be hit by a truck (or quit) before a project is incapacitated. In our