204 karma · joined January 27, 2015
The whole thing is designed to prevent some mid level beauracrat from kicking his brother in law some project for 10% more then "market rate" ... instead we pay 300% more because every project has to get rolled up into some monolithic thing that's big enough for the big contracting companies to get involved.
The problem is that if I had stayed there for thirty years, I would have been pretty much guaranteed to make good money. By changing jobs a couple times, I made that same money in 2. So... people who are capable of getting better jobs and willing to risk change simply left, while people looking for stability or who had trouble getting jobs simply stayed. This didn't lead to the type of environment that I enjoyed working in. Your mileage may vary.
1. Tax treatment (A RSU counts as income when you receive it, an option counts as income when you exercise it and get stock. Remember, many people recommend early exercising options anyway for preferable tax treatment, though this can lead to taking a loss on taxes if the shares wind up worthless. If you are forced to exercise a large block of options when they are still illiquid, you will have a very large one time tax bill, which may be much harder to deal with than smaller ones each year) 2. Risk (For options, you have to dish out cash from your pocket to actually receive stock, which is more risky than if you don't. Until exercise, the two choices are similar)
In general, I would prefer options with a long exercise period, but I may prefer RSU to options with a short one...
Half of the article is various complaints about AUFS, and then Overlay. There are at least 6 storage drivers off the top of my head, and I feel like there are one or two more I am forgetting about. What made you choose AUFS? What were your thoughts on Overlay? Instead of going with the default and complaining, maybe research your options? Even worse though, the filesystem driver is completely beside the point. If you want to store things on the filesystem from a Docker container, you don't use the copy-on-write storage system! You create a volume, which completely bypasses the storage driver. There are even a bunch of different volume drivers for different use cases- say mounting EBS volumes automatically for your container to persist data to? His whole rant about data magically disappearing has nothing to do with the tool, but that he didn't take the time to learn how to use it correctly.
Further, while I am sure he is telling the truth and has machines randomly suffering kernel panics and crashing multiple times per day, it seems hard to believe that it is docker causing this. He is running 31 containers spread across 31 aws hosts... I am running thousands, across hundreds of aws hosts, and have been for a long time, and cannot recall a single kernel panic caused by docker.