The story of how minor leaguer Brock Bond got into professional baseball is humorous.
It was a mistake. A clerical error.
The Giants meant to take Casey Bond, a gliding, 6-foot-3 center fielder out of Lipscomb University in Tennessee. They mistakenly took a high-achieving, 5-foot-11 infielder from the University of Missouri.
But what he did once he got that opportunity is an inspiration. It’s the story of a guy who realizes he shouldn’t be there, but is determined to make everyone forget that.
Brock Bond had to prove himself at every level but just kept finding ways to get on base, and kept holding on to playing time. A switch hitter, he has drawn 256 walks to 266 strikeouts over six seasons, and last year at Triple-A Fresno, he hit .332 with a .422 OBP in 106 games.
Often, part of success is being in the right place at the right time. What will you do with the opportunity when it happens?
I think the email model is a possible way to evolve voice telephony and make it more useful and enduring, especially in mobile. You could have multiple "lines" from multiple service providers, on a single device. At one level they would interoperate perfectly, but they might have separate special features or business models, in the same way that Gmail is different to Hosted Exchange or assorted others.
The author, Dean Bubley, knows a thing or two about phone networks and carriers. So this isn’t the wild dreaming of someone who doesn’t understand what’s technically feasible.
Today I might get a call on my mobile to my phone number, one of several Tropo numbers that redirect to my phone number, Skype, a SIP softphone, and probably something I’ve forgotten about. One device, multiple entry points. Messages are the same way. SMS, iMessage, Whatsapp, Skype... they all arrive on my phone.
We’re already doing this today, just the carriers haven’t caught on. If I want two AT&T numbers and a Verizon number, I need three phones. But I think this is coming, and fast.
Considering MySQL? Use something else. Already on MySQL? Migrate. For every successful project built on MySQL, you could uncover a history of time wasted mitigating MySQL’s inadequacies.
Thesis: databases fill roles ranging from pure storage to complex and interesting data processing; MySQL is differently bad at both tasks. Real apps all fall somewhere between these poles, and suffer variably from both sets of MySQL flaws.
What follows is a 5300 word treatise on the inadequacies, weird design choices, and tradeoffs that MySQL has. You’re really got to have a lot of hate to spend time writing that detailed of an analysis of something.
For those that actually use MySQL, the post serves as a great summary of things you need to be aware of. Not every tool is appropriate for every job, and every database server has some sort of deficiency, so knowing what you’re in for before you start is helpful.
This can’t be good: http://t.co/vJCJ3D2g
Am I the only one wondering what would happen if I unplugged that Ethernet cable?
Now I know why my hotel wifi signal is so good: http://t.co/ADAKVtPK
The Oakland A’s are selling root beer floats to raise money to fight diabetes. Next month, how about beer proceeds donated to AA?
Dear gmail, please sort autocomplete contacts by frequency of use. I email my wife Christina way more than I do @ChrisPirillo. Put her 1st.
My son’s school is selling or giving my contact info to local businesses. Lovely.
Two iPhones in the house took a swim this week. Opened them up, cleaned them out, they’re both working again.
If your pitch deck is more about the animations than the company, you’ve already lost.
The ER is always filled with interesting people.
Proof reading is gud.
©1999-2014 Adam Kalsey.
Content management by Movable Type.