Have you ever hopelessly searched for new programmers? We do it all the time and it looks like we are constantly running out of good programmers. But how good does a programmer have to be to produce good software? Maybe it is enough if one can [[HtmlForFood|code HTML]].

Have you ever hopelessly searched for new programmers? We do it all the time and it looks like we are constantly running out of good programmers. But how good does a programmer have to be to produce good software? Maybe it is enough if one can [[HtmlForFood|code HTML]].

==== Current or Certain? ====

==== Current or Certain? ====

==== Current or Certain? ====

==== Current or Certain? ====

''p. 13, para 2 - should "at its certain revision" be "at its current revision"?''

: ''p. 13, para 2 - should "at its certain revision" be "at its current revision"?''

--[[User:David Biesack|David Biesack]] 20:25, 5 February 2009 (TC)

: --[[User:David Biesack|David Biesack]] 20:25, 5 February 2009 (TC)

I am always surprised when I meet with users of the [[NetBeans]] platform and I find out that they are not using the latest development version. Why? We keep [[BackwardCompatibility]]. Migrating to new version is easy. Still, if this is not a priority, then it is OK to stick with some older version, released few years ago before migrating. Very likely this is the so infamous [[Fear of Upgrades]]. Why change something that is known to work?

I am always surprised when I meet with users of the [[NetBeans]] platform and I find out that they are not using the latest development version. Why? We keep [[BackwardCompatibility]]. Migrating to new version is easy. Still, if this is not a priority, then it is OK to stick with some older version, released few years ago before migrating. Very likely this is the so infamous [[Fear of Upgrades]]. Why change something that is known to work?

Btw. Of course, I am not native speaker and as such my understanding of differences between ''certain'' and ''current'' may not be fully accurate.

Of course, I am not native English speaker and as such my expressing abilities are little bit limited. As such I am glad to accept improvements like the following one:

 

--[[User:JaroslavTulach|JaroslavTulach]] 21:00, 6 February 2009 (UTC)

: ''Here's another possible phrasing that I think removes the confusion over this particular word choice: "we'll explore various ways to help people... use a specific version of your library immediately, in a way that will continue to work in subsequent releases".''

: ''Here's another possible phrasing that I think removes the confusion over this particular word choice: "we'll explore various ways to help people... use a specific version of your library immediately, in a way that will continue to work in subsequent releases".''

--[[User:JaroslavTulach|JaroslavTulach]] 21:00, 6 February 2009 (UTC)

--[[User:JaroslavTulach|JaroslavTulach]] 21:00, 6 February 2009 (UTC)

Thanks for your comment David. Current is not bad choice and I was considering it too, but its meaning is not clear. What it means ''to use current version of a library''? For the library author, ''current'' means the development version. For the library user, it is the version that the user is using. Obviously not every user is working on the same schedule. There are always more important things to do than to upgrade to the latest version of a library and as such there is many subjective ''current'' versions.

Thanks for your comment David. Current is not bad choice and I was considering it too, but its meaning is not clear. What it means ''to use current version of a library''? For the library author, ''current'' means the development version. For the library user, it is the version that the user is using. Obviously not every user is working on the same schedule. There are always more important things to do than to upgrade to the latest version of a library and as such there is many subjective ''current'' versions.

That is why I used ''certain'' - it expresses a bit of uncertainty - and points out that the library in use is just at ''some'' version, one of many. That there is is nothing special or privileged in it.

That is why I used ''certain'' - it expresses a bit of uncertainty - and points out that the library in use is just at ''some'' version, one of many. That there is is nothing special or privileged on it.

Of course, I am not native speaker and as such my understanding of differences between ''certain'' and ''current'' may not be fully accurate.

 

Btw. Of course, I am not native speaker and as such my understanding of differences between ''certain'' and ''current'' may not be fully accurate.

--[[User:JaroslavTulach|JaroslavTulach]] 21:00, 6 February 2009 (UTC)

--[[User:JaroslavTulach|JaroslavTulach]] 21:00, 6 February 2009 (UTC)

Thanks for your comment David. Current is not bad choice and I was considering it too, but its meaning is not clear. What it means ''current''? For the library author, ''current'' means the development version. For library user, it is the version that the user is using. Obviously not every user is working on the same schedule. There are always more important things to do than to upgrade to the latest version of a library and as such there is many subjective ''current'' version.

Thanks for your comment David. Current is not bad choice and I was considering it too, but its meaning is not clear. What it means ''to use current version of a library''? For the library author, ''current'' means the development version. For the library user, it is the version that the user is using. Obviously not every user is working on the same schedule. There are always more important things to do than to upgrade to the latest version of a library and as such there is many subjective ''current'' versions.

That is why I used ''certain'' - it expresses a bit of uncertainty - and points out that it is just ''some'' version, one of many. That it is not special or privileged in any way.

That is why I used ''certain'' - it expresses a bit of uncertainty - and points out that the library in use is just at ''some'' version, one of many. That there is is nothing special or privileged in it.

Of course, I am not native speaker and as such my understanding of differences between ''certain'' and ''current'' may not be fully accurate.

Of course, I am not native speaker and as such my understanding of differences between ''certain'' and ''current'' may not be fully accurate.

--[[User:JaroslavTulach|JaroslavTulach]] 21:00, 6 February 2009 (UTC)

--[[User:JaroslavTulach|JaroslavTulach]] 21:00, 6 February 2009 (UTC)

==== Current or Certain? ====

==== Current or Certain? ====

p. 13, para 2 - should "at its certain revision" be "at its current revision"? --[[User:David Biscay|David Biscay]] 20:25, 5 February 2009 (TC)

''p. 13, para 2 - should "at its certain revision" be "at its current revision"?''

--[[User:David Biesack|David Biesack]] 20:25, 5 February 2009 (TC)

 

Thanks for your comment David. Current is not bad choice and I was considering it too, but its meaning is not clear. What it means ''current''? For the library author, ''current'' means the development version. For library user, it is the version that the user is using. Obviously not every user is working on the same schedule. There are always more important things to do than to upgrade to the latest version of a library and as such there is many subjective ''current'' version.

Thanks for your comment David. Current is not bad choice and I was considering it too, but its meaning is not clear. What it means ''current''? For the library author, ''current'' means the development version. For library user, it is the version that the user is using. Obviously not every user is working on the same schedule. There are always more important things to do than to upgrade to the latest version of a library and as such there is many subjective ''current'' version.

Have you ever hopelessly searched for new programmers? We do it all the time and it looks like we are constantly running out of good programmers. But how good does a programmer have to be to produce good software? Maybe it is enough if one can [[HtmlForFood|code HTML]].

Have you ever hopelessly searched for new programmers? We do it all the time and it looks like we are constantly running out of good programmers. But how good does a programmer have to be to produce good software? Maybe it is enough if one can [[HtmlForFood|code HTML]].

== Have You Ever Wondered...? ==

== Have You Ever Wondered...? ==

Have you ever considered yourself artist when coding? Do you think programming is kind of art? Have you noticed the difference in developing software systems today and twenty years ago? Do you know why people consider ugly solutions wrong? If you ever asked questions like this, this chapter gives you answers that I found after many years of oscillating between feeling like artist and behaving as engineer.

Have you ever considered yourself an artist when coding? Do you think programming is kind of art? Have you noticed the difference in developing software systems today and twenty years ago? Do you know why people consider ugly solutions wrong? If you ever asked questions like this, this chapter gives you answers that I found after many years of oscillating between feeling like an artist and behaving as an engineer.

Did you ever hopelessly searched for new programmers? We do it all the time and it looks like we are constantly running out of good programmers. But how good a programmers has to be to produce good software? Maybe it is enough if one can [[HtmlForFood|code HTML]].

Have you ever hopelessly searched for new programmers? We do it all the time and it looks like we are constantly running out of good programmers. But how good does a programmer have to be to produce good software? Maybe it is enough if one can [[HtmlForFood|code HTML]].

Have you ever considered yourself artist when coding? Do you think programming is kind of art? Have you noticed the difference in developing software systems today and twenty years ago? Do you know why people consider ugly solutions wrong? If you ever asked questions like this, this chapter gives you answers that I found after many years of oscillating between feeling like artist and behaving as engineer.

Have you ever considered yourself artist when coding? Do you think programming is kind of art? Have you noticed the difference in developing software systems today and twenty years ago? Do you know why people consider ugly solutions wrong? If you ever asked questions like this, this chapter gives you answers that I found after many years of oscillating between feeling like artist and behaving as engineer.