07-18-2016
Well, like you guys, I write a lot of code, and have a lot of sites, passwords, scripts, etc across many sites.. a lot of IT.
Even the best written code can be hard to understand after we have not touched it for a month or two, let alone a year or more.
So, I learned the hard way many years ago not to write "fancy one liners" and write well documented code and scripts.
Maybe I am being too simple here; but when I was a young lad my mother used to say 'Neo (well, not really Neo... haha), always put things back where you keep them in the same place, that way when you need them again, you don't waste time looking for it"..... and that is what I do not, even thought I never did it when I was young, of course!
The same is true with code... but the twist is different... always make sure your code is easy to read and self documenting as possible (clear variable names, simple clear logic etc, not fancy one-liners) because when we need to go back and work on that code again, we don't want to waste time trying to understand what we did before......
... and my mom would be proud of me, I always put my tools back in the toolbox now, always put my scissors back in the same place, always put my car and motorcycle keys in the same place after I use them.... and so my life is so easy as I never waste time trying to find that stuff anymore. LOL
Just keep it simple and life will be easy and less stress, and we then have more time for other things that are more fun.... that is my view.
4 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
First of all, apologies to the admins for not reading the rules totally and missing the bit about ranting off about other OSs.
But that raises a question. Where do you go to have a good rant, to vent your disgust at various corporations and thier hideous behaviour?
:confused: (2 Replies)
Discussion started by: u6ik
2 Replies
2. Shell Programming and Scripting
Guys,
I have a requirement like this.
A file has >5K records always. Separated by "|", it has 30 fields for each line. In some lines, I am getting an odd field. say, the 15th field is supposed to be 2 characters but comes in as >2. In this case, for resolving this I need to copy the value of... (6 Replies)
Discussion started by: PikK45
6 Replies
3. What is on Your Mind?
I wanted to say LOL and punch my face when I saw post#11 (where Don_Cragun even reduced the string manipulation with a simple regex) in the thread https://www.unix.com/shell-programming-scripting/220553-add-0-start-filename-2.html
I mean, when things can be done with just a one liner, sometimes I... (6 Replies)
Discussion started by: ahamed101
6 Replies
4. What is on Your Mind?
Hi guys...
(Apologies for any typos etc...)
This is basically a rant.
I have been doing kids level projects and writing code to suit since around 1982, for the uProfessor, for the Sinclair Spectrum and later for the QL, IBM-XT in MS-DOS and after that for a 386DX40 up to Windows 95, until I... (3 Replies)
Discussion started by: wisecracker
3 Replies
RANT(1) General Commands Manual RANT(1)
NAME
rant - A flexible and portable build tool.
SYNOPSIS
rant [OPTION] ... [TARGET] ...
DESCRIPTION
Striking features
* Defining custom tasks.
* Automated packaging, testing and RDoc generation for Ruby
applications and libraries.
* Creation of a monolithic script tailored to the needs of a specific
project which can be used instead of an Rant installation - users
don't need to install Rant. [See man rant-import]
* Creating gzipped tar and zip archives -- without installing
additional software.
* Optional recognition of file changes based on MD5 checksums instead
of file modification times.
* Dependency checking for C/C++ source files (integrated makedepend
replacement).
* Primitive support for compiling C# sources with csc, cscc and mcs.
Startup
On startup, rant will look for a file called Rantfile , rantfile or root.rant which contains the build specification (which in fact is
valid Ruby code). After reading the Rantfile(s), rant will execute the following tasks:
If at least one target was given on the commandline:
rant will execute all tasks necessary to build all targets given on the commandline.
else:
rant tries to build the target called "default". If no task with this name exists, rant invokes the first defined task.
If you want to know which task(s) will be invoked when no target is given on the commandline, run rant with the -T option. Example:
$ rant -T
rant # => test
rant package # Create packages for distribution.
rant doc # Generate documentation.
rant publish-docs # Publish html docs on make.rubyfore.org.
# Note: scp will prompt for rubyforge password.
rant test # Run basic tests.
The first line always shows the target that will be built if no target argument is given. In this case, it would be the test target.
OPTIONS
--help -h
Print a help message and exit.
--version -V
Print version of Rant and exit.
--verbose -v
Print more messages to stderr.
--quiet -q
Don't print commands.
--err-commands
Print failed commands and their exit status.
--directory DIRECTORY -C DIRECTORY
Run rant in DIRECTORY.
--cd-parent -c
With this option, Rant starts to search for an Rantfile in the
current working directory as usual, but if it doesn't find one,
it changes to the parent directory and looks there for an
Rantfile. This is repeated until an Rantfile is found or the
working directory is the root directory of the filesystem.
--look-up -u
Look in parent directories for root Rantfile.
--rantfile RANTFILE -f RANTFILE
Process RANTFILE instead of standard rantfiles.
Multiple files may be specified by repeating this option.
--force-run TARGET -a TARGET
Force rebuild of TARGET and all dependencies.
--dry-run -n
Print the names of the tasks that would be executed instead
of actually executing task actions.
--tasks -T
Show a list of all described tasks and exit.
HOMEPAGE
<http://rant.rubyforge.org/>
AUTHOR
rant developed by Stefan Lang <langstefan@gmx.at>
COPYRIGHT
Copyright (C) 2005 Stefan Lang <langstefan@gmx.at>
SEE ALSO
rant-import(1)
September 17, 2006 RANT(1)