In my opinion, you need to understand the difference between hard work and smart work. Software development is like an art.
A person may spend 18 hours a day to create something that just works while another may spend just 8 creative hours to create a masterpiece.
There are many disadvantages of being a hard worker / workaholic:
* The expectation of your manager will get elevated and if one fails to be consistent in working for long hours, it's a negative.
* One does not have much room to accommodate something else at times of need. Think of an outage, you have already worked for 18 hours and fail to deliver at that crucial time.
* It's very difficult to innovate in an insomniac state.
Remember, doing hard work is easier that smart work. It requires much more learning and thinking. But, if you are able to do it, you will be able to contribute much more.
Appraisal based on relative performance: This sounds logical. If a person contributes better to the company's goal, he/she should be appreciated for that. Think yourself being that person it should make sense.
Note: I am not taking the political aspects of your office into consideration. If your manager loves late night availability, long emails at weird hours, it is his weakness. Probably, you can be smart and automate sending 'corporate bullshit' emails at night ;)
The concept is different. VC buy shares/equity of a company.
The company may be owned by a group of individuals (they may or may not have invested money, but they are typically founders of the company)... When a VC invest in Equity of a company, they get some percentage of ownership in the company...
I write a lot of shell scripts as part of my daily Sys Admin work. In my opinion, the author gave us choice to write less codes & readable code by using short flags for most of the command functionalities.
Consider something like this:
$ rsync -qaogtHr example.com:/opt/data/ /home/backup/
1. Elaborating all the short flags into long ones will increase readability by explaining this statement but at the cost of more lines of code.
2. All UNIX commands have options to combine short flags.
For eg:
ls -l -t -r ./
can be written as:
ls -ltr ./
This also helps in reducing code. Writing less code helps in managing it more easily.
Long options may help beginners, but once they get comfortable, Short flags may seem more readable!!