There are principles you follow to ensure you get the right results, at least most of the time. Likewise,
when you work at the command line, there are best practices you can follow to ensure you get
good results, at least most of the time. This appendix tells you about the best practices I??™ve created
while working at the command over the last 20 years. These are time-tested techniques you can
use to obtain good results. They won??™t always provide perfect results; only practice on your part will
produce the perfect results you seek, but they??™ll help considerably. I??™d love to hear your best
practices as well??”feel free to contact me at
JMueller@mwt.net
.
Always Verify the Data
It always pays to verify the data you??™re going to use with a command or utility. Unlike the GUI
environment, the command line environment doesn??™t ever provide you with a list of acceptable
choices. Consequently, you may find that something very small can product very bad results. For
example, you may have two employees and one is named Newman, while the other is named
Neumann. The difference of two characters can make a huge difference. When working with a GUI,
you??™d probably see both names and choose the right one or ask someone if you weren??™t sure.
Pages:
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372