Re: IDE

[Jean-Christophe Helary]

> On Oct 11, 2015, at 23:05, Przemysław Wojnowski <address@hidden> wrote:
> 
> W dniu 11.10.2015 o 15:41, Jean-Christophe Helary pisze:
> [...]
>> It was not intended as a joke :) But if we start by defining what we mean by 
>> "productivity" in the context of code writing, then it's easier to see what 
>> can be on the feature list and what does not need to be.
> Note one thing: I have written "to help programmers do their work 
> productively".
> It doesn't have to be "writing code". It can be analyzing code, learning it, 
> refactoring, deleting code, running app/tests/debugging, etc.

That's what I'd put under "correctness".

> Actually in many legacy systems writing code is minor activity.

In which case your focus is on "correctness".

> In different projects productivity may be defined differently, but, where 
> money counts, usually it's defined as "deliver software on time". Nobody care 
> how many lines is that - the less, the better. If its oneliner and does the 
> job then do it. :-)

Volume itself is a function of the expressiveness of the language. But even in 
a very expressive language, writing the most and most correct code in the 
smallest amount of time can be used as a definition for productivity and to 
identify basic features that you'd want to achieve that.

But the definition of productivity itself does not matter as long as you have 
one that allows you to specify what features are required and what features are 
not.

Jean-Christophe