"gimme gimme gimme" from man after midnight, you say?
Readit Newsferalchimp commented on Why does man print "gimme gimme gimme" at 00:30? (2017) unix.stackexchange.com/qu... · Posted by u/jamesy0ung
Really nice job with this project, and especially the clear/concise write-up of the pipeline steps.
feralchimp commented on Is Apple experiencing a problematic decline in software quality? tuaw.com/2014/10/15/is-ap... · Posted by u/MilkoFTW
If this is real, I don't think it's about release timing at all, but the technical complexity of implementing and integrating the specific new features they've chosen.
I don't have a list of specific examples to back up that claim, but I encourage other apple devs here to think about recent releases from that perspective.
feralchimp commented on Tptacek's Review of "Practical Cryptography With Go" gist.githubusercontent.co... · Posted by u/babawere
This is a great review for two reasons:
a) it provides readers with a laundry list of things to go study independently
b) the book author can, given time and inclination, do the same study and improve the book
feralchimp commented on Failed Startup's Final Income Statements Reveal Grave Error businessinsider.com/jody-... · Posted by u/xadxad
"Grave error" implies something that a non-fool might blunder into. Fools don't blunder, per se, they simply exist.
One of the first jokes I ever heard at a startup was "We'll give the product away and make it up on volume!" Changing the joke to "We'll pay people to take the product and make it up on volume!" doesn't make it less obviously ridiculous.
I'm amazed they were able to hire employees, let alone find investors. Doesn't make the guy's death any less tragic though.
feralchimp commented on The Principled Documentation Manifesto hackingdistributed.com/20... · Posted by u/aydinhan
If you're wondering how to write thorough doc for an engineering audience, I highly recommend looking at IBM's doc for z/OS. The first thing you'll notice is: there's a lot of it.
It is rather arrogant I think.
And yet, an order of magnitude less arrogant than the recruiting attitude that led to its authorship.
feralchimp commented on Ubuntu Phone will include a Terminal application wiki.ubuntu.com/UbuntuPho... · Posted by u/dave1010uk
The market for people who want a native terminal on their phone should be roughly equivalent to people who ever want to terminal INTO their phone.
The market already well served by iOS, Android, etc., is people who want to terminal OUT OF their phone and onto a real computer someplace.
What are the real-world tasks you expect to do with the former that you couldn't do, or couldn't do as well, with the latter?
feralchimp commented on If malloc fails, it's not for the obvious reason scvalex.net/posts/6/... · Posted by u/scvalex1
Does Linux behave similarly by default if one uses calloc instead?
feralchimp commented on Apple has lost their legal claim to the iPhone name in Mexico phonearena.com/news/Apple... · Posted by u/mun2mun
No offense, but I think you are greatly confused about the economics of lawyering. Without getting into a full blown 30 page explanation, you do not always take home big bucks. This is a common misconception.
There is in fact, a large risk of "no payout", or worse, a loss, if apple decides to argue about your billing (which they will). As a firm, you may end up having to pay your associates more than apple pays you, depending on how things go, generating a net loss for the firm. Your associates get paid well (particularly in the IP field), but usually this just about makes up for the large amount of law school debt they have (which can easily be $3000+ a month). Again not that they are poor starving people, but the salary differences you see often are eaten by debt payments and the fact that they work ridiculous hours.
On the direct "payout side", you are right that trademark work is not usually contingency work, but a lot of other work is, in which case the risk is immense. Firms are often fronting many millions of dollars in large cases, and all you have is the hope you will get paid on time. Your recourse if you don't is to sue the client, and then spend even more money, and either settle for 50% to not drag it out (the average time to resolve these cases is 7 years), or hope a judge doesn't think your billing is atrocious.
This risk is certainly less in the corporate world (in my wife's area, family law, individual clients can have something like a 35% non-payment rate, particularly in hard economies), but still there.
Again, i'm not saying lawyers don't make money, and aren't well off in a lot of cases, but to pretend that lawyers are somehow guaranteed "big bucks" in cases like this is just a fantasy. It's a business. Sometimes you do well, sometimes you don't. There are no guarantees, and there is always risk. Given the state of the legal job market and the legal world , if you want to make big bucks, running a law firm and taking cases like this is not the way to do it anymore.
This is awesome, Danny. Now get on that 30-page version. :)