c0achmcguirk
This is more than just a "poster in the cafe" because of the reach and invasiveness of the approach.
Disclaimer: I work for Google, speaking for myself only.
They will not wipe your personal phone or your personal profile on your phone. This is completely avoidable and shouldn't come as a surprise.
I moved from Omaha to the Denver/Boulder area two years ago and besides the Henry Doorly Zoo, I miss Nebraska Furniture Mart the most.
NFM is a great place to buy pretty much anything you want to put in your house. Mrs. B really knew how to make a business work. The only weird thing is how antiquated their computer systems are, it's amazing they are so profitable with 70's era technology running the business.
Disclosure: I work for Google.
[1] https://www.infoq.com/news/2007/06/TestDriven-Express-Emails
If the entity offering the microtasks (gig) don't see enough interest in their tasks, they can raise the bid.
I think that's extremely fair. Let the market dictate the price per task. How do you know what the right price should be?
I haven't needed that in over 15 years, but if you need this, install this add-on for free [1].
> footnotes
Insert > Footnote
> References
Tools > Research, Cite as Footnote
> Multi-column layouts
Format > Columns
> A mixture of portrait and landscape pages?
This is hard to do in Word too. If you really need this, make two Google docs (landscape, portrait, and then a Word Doc that integrates the two that you keep in Read-Only mode).
But really, why is this needed for serious uses and considered "seriously lacking?"
> Captions on tables
This could be done by just inserting text and formatting the way you want. I don't think you can generate a table of tables though. Do you have a list of commonly used "hobbled" features? None of these are something I've had a need to do for decades.
[1] - https://chrome.google.com/webstore/detail/mail-merge/lclhkda...
S-expressions are very compact and are easy to parse. There was actually some support for using S-expressions over XML and JSON as a serialization language.[1]
Ron Rivest even proposed S-expressions as a standard.[2]
I still prefer JSON over them though. As the old joke goes, LISP stands for "Lots of Irritating Silly Parentheses."
1 - http://eli.thegreenplace.net/2012/03/04/some-thoughts-on-jso...
A few more I live and die by:
gf git fetch --all; git fetch --tags
gh git log --oneline --abbrev-commit --all --graph --decorateThis is the telegraph operator lamenting all the time spent learning Morse Code when the telephone was invented.
I think scientists can be motivated by looking for new ways to solve real problems. Don't weep over the time spent understanding the classic models. Rejoice that we have a much better tool to further mankind.
But I still push the arrow keys from time to time, you know, to make sure they still work.
After being productive in Vim, I can't go back to using the arrow keys and the mouse. It feels like I lost a hand.
It's fascinating to read how he discovered it and how quickly Google responded.
[1] - http://blog.jeremiahgrossman.com/2006/01/advanced-web-attack...
"Incidentally, when you write a paper, you can expect most reviewers (and readers) to make only one pass over it."
I understand reviewers are busy, but we depend on peer review to filter out bad or poorly-researched material. I don't think one pass is enough.
Obviously, so does the author.
This is very true, but I like to think of how predominant MySpace and Hotmail were at one time. Someone will come along and do it better. Stripe, PaymentSpring, heck even Bitcoin are all potential disruptors here.
I think the days of PayPal's dominance are numbered.
Any advice for those of us who'd like to introduce this to a team rather than play with it on our own?
I'll admit--the Microsoft stack is a walled garden. It offers some nice features like Visual Studio integrating with Visual Studio Team Services with its own issue tracker and build server and so on. If Microsoft supports your workflow or integrates with the tooling you like, awesome. If not, well, just wait and hope that it will someday support what you're looking for.
That is the frustrating part of the Microsoft stack. It can be overcome with some architecture decisions at the outset of the project. You don't have to stay in the walled garden.
But the Enterprise is where innovation dies. The Enterprise is where motivated developers' souls are sucked out as they are told "no" constantly.
.NET isn't the problem.