|Change the way you choose.|
Ulrike's blog for app development dummies.
There are certain things that I am starting to understand in terms of software development. Take the basic Linux code commands for example. Ok, let’s not exaggerate. There is really only one code command that I understand and that is the following: “kill”. In my view, that is pretty straight forward. End and shut down whatever it is that the command is referring to.
Once again, just like in real life.
In order to better understand code language, the next question that needed to be clarified in my mind was the following: Is Linux religious?
You wonder why this is important? No, I am not talking about taking responsibility for your own actions, even though that is definitely part of being a developer as has already been discussed in the Develappment blog under “Git Blame”. What I am talking about is the possibility of an afterlife.
Once you have used the command “kill”, is there a chance of resurrection or rebirth?
Which means, the logical command you could use to fix a potential mistake would be “revive”. Unfortunately, Linux does not seem to be religious, as this command apparently does not exist. Well, maybe the developing world can learn something from me for a change and add this command to the Linux vocabulary.
At least this way, there would be one more word that I can understand.
And it's not like I didn't make an effort. I have tried to talk to the developers about code commands and that got them very excited. I did my best to pay attention and follow the conversation, but seriously:
“pipe to grep”?
“cat the log”?
“born again shell”? - I do like this one, mainly because it produces another great acronym: Bash.
This time there are not even any links that I could add to these expressions in order to make "normal" people understand. I guess they will have to remain amongst the mysteries of the geek world.
Conclusion of Sprint 6&7: