2is10
Re:Suicide Linux (2009)
on Thursday October 01, 2020 @01:50PM (#24654010)
> the operating system does its best to pretend that nothing is wrong
Call it "Trump Linux"! :)
Re:How Much Should Startup Employees Earn? Wealthfront Tells Us With A...
on Tuesday September 18, 2012 @12:48PM (#4539094)
On the initial view, only the 40th to 60th percentiles are shown. On subsequent views, only the 25th to 75th percentiles are shown. There are many above those ranges, including some outliers with 3% or more of their company (choose Scientist > Fellow for one example).
Also, according to the Source line at the bottom, executives and founders are excluded from the data set. Getting a large share of equity of a private company is rare for everyone else.
Re:Taking corrective action with git pre-commit
on Tuesday March 08, 2011 @01:55PM (#2302081)
If you're working with a legacy repository, quit your job. Work somewhere where you are empowered to do what will make you and your team more efficient. I nuked trailing whitespace in our whole repo at wealthfront when I added the whitespace check to our pre-commit hook.
Re:Bulletproof Rails Asset Caching
on Saturday February 19, 2011 @05:04AM (#2238815)
You've missed the point. 90% of Rails websites behave badly every time they're deployed, and the developers don't even realize it. I included our build scripts in the post to illustrate how simple it is to fix the problem. The important thing is that people reliably version their asset URIs, not what tools they use to do it.
Re:Bulletproof Rails Asset Caching
on Friday February 18, 2011 @12:42PM (#2236395)
Got a link to details? I'd be surprised, since any correct solution requires two-stage deployment and keeping old assets around. These capabilities are beyond the scope of a web server framework. The Rails team could certainly educate Rails developers and choose conventions that make correctness easier.
Re:Bulletproof Rails Asset Caching
on Friday February 18, 2011 @12:36PM (#2236365)
But any dynamic processing of stylesheets sacrifices performance. It means they have to be served by Rails. Preprocessing before deployment frees you to host them anywhere, ideally closer to your users.