+ Writing enterprise ready software
@@ -76,7 +78,7 @@ long time ago, and the program is still used in production. -->
full, one do not want to kick out 30000 users to take down the
database and resize the file system.
-
Disktrouble
+
Disk trouble
RAID is only only useful until the last redundancy disk is lost.
@@ -95,7 +97,7 @@ painful and prone to errors.
Trying to get some network server to work when it require to use
some given port range, which is already taken by some other service
-and blocked in the router -- or try to get the coorporate network
+and blocked in the router -- or try to get the corporate network
gatekeeper to open up the firewall
Version trouble
@@ -105,7 +107,7 @@ PHP usable with all of these?
Usability trouble
-
When starting a program from the meny, where does it go if nothing
+
When starting a program from the menu, where does it go if nothing
appear on the screen?
Do users always read their ~/.xsession-error file?
@@ -126,7 +128,7 @@ appear on the screen?
the operations needing root access. (build / configuration as well)
make sure the software can be installed anywhere (location
- independent), avoid hardcoding paths into the binaries.
+ independent), avoid hard coding paths into the binaries.
make the source available to make it possible to fix problems on
site, and to use it on different platforms (os/hw) in the future
@@ -145,7 +147,7 @@ appear on the screen?
extra library in place
use well known libraries instead of making your own implementation.
- reduses the security risk.
+ reduces the security risk.
make sure libraries, and programming languages are backwards
compatible.
@@ -184,11 +186,13 @@ appear on the screen?
reuse configuration when possible. ktouch have its own x layout setting.
better to fetch the current one from X like xkeycaps.
-
providing hooks to the local admins
+
providing hooks to the local administrators
reduce flexibility. trying to support people over the phone when
the gui is different for every person is a pain.
+
do not try to cleverly find the final resting place of the installation.
+
Solving the upgrade problem using multilevel
@@ -198,7 +202,9 @@ appear on the screen?
local configuration should be kept during upgrades
-
easiest to do if the local configration is separate from the
+
do not change configuration file format
+
+
easiest to do if the local configuration is separate from the
package default
several actors what to have a say in the service
@@ -217,8 +223,6 @@ appear on the screen?
-
-