The Art of Building Modern Software
From APIDesign
(tidied up the english-- I kept it uncontroversial; there are missing "that"s and "have"s that could be considered minor stylistic points.) |
|||
| Line 4: | Line 4: | ||
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? ==== | ||
| + | |||
| + | 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) | ||
| + | |||
| + | 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. | ||
| + | |||
| + | 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. | ||
| + | |||
| + | 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) | ||
Revision as of 21:00, 6 February 2009
Have You Ever Wondered...?
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.
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 code HTML.
Current or Certain?
p. 13, para 2 - should "at its certain revision" be "at its current revision"? --David Biscay 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.
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.
Of course, I am not native speaker and as such my understanding of differences between certain and current may not be fully accurate.
--JaroslavTulach 21:00, 6 February 2009 (UTC)
Follow
