Published by Robert Scoble
I give you a front-row seat on the future. Focusing most of my efforts now on next-generation augmented reality and artificial intelligence, AKA "mixed reality."
SUBSCRIBE TO MY NEWSLETTER: http://clevermoe.com/scobleizer-news/
BUY OUR NEW BOOK: https://www.amazon.com/Fourth-Transformation-Robert-Scoble/dp/1539894444 "The Fourth Transformation: How augmented reality and artificial intelligence will change everything."
WATCH MY LATEST SPEECHES:
State of VR with Philip Rosedale (done in VR itself, very cool): https://www.youtube.com/watch?v=2zAA1EVGUZU
At GEOINT, June 2017: http://trajectorymagazine.com/glimpse-new-world/
Augmented World Expo, June 2017: https://www.youtube.com/watch?v=l4xHILvLD8E
At Leade.rs, April 2017: https://youtu.be/52_0JshgjXI
+++++++++++
BIO:
Scoble gives you a front-row seat on the future.
Literally. He had the first ride in the first Tesla. Siri was launched in his house. He's been the first to share all sorts of technologies and companies with you, from Flipboard to Pandora to Instagram.
Today he's focusing on mixed reality, AKA "next-generation augmented reality" which will include a new user interface for EVERYTHING in your life (IoT, Smart Cities, driverless cars, robots, drones, etc).
That's based on his view thanks to his past experience as futurist at Rackspace.
Best place to find Scoble? On his Facebook profile at https://www.facebook.com/RobertScoble
He has been a technology blogger since 2000, was one of five people who built Microsoft's Channel 9 video blog/community, worked at Fast Company Magazine running its TV efforts, and has been part of technology media businesses since 1993.
++++++++
SPEAKER PITCH:
Apple and Facebook now have revealed their Augmented Reality strategies, which means your business needs one too. Rely on Robert Scoble, the world's top authority on AR, to bring to your conference what businesses should do next.
SPEECH ABSTRACT #1:
TITLE: The Fourth Transformation: What's next in mixed reality (AR and AI) and the future of technology?
Here's an example of this talk at Leade.rs in Paris in April, 2017: https://youtu.be/52_0JshgjXI
Why "the Fourth Transformation?"
Soon we will have phones and glasses that do full on augmented reality. Everything you look at will potentially be augmented. This world is coming in late 2017 with a new iPhone from Apple, amongst other products. Microsoft is betting everything on its HoloLens glasses that do mixed reality and the industry is spending many billions of dollars in R&D and funding new companies like Magic Leap.
This future will be the user interface for IoT, Smart Cities, autonomous cars, robots, drones, and your TV.
This is a big deal and Robert will take you through what mixed reality is and how it will change every business.
Learn more about Robert's speaking style and contact his agent at http://odemanagement.com/robert-scoble/Robert-Scoble.html
++++++++
SPEECH ABSTRACT #2:
"The Next Two Clicks of Moore's Law."
Over the next four years, or two clicks of Moore's Law, a ton about our technology world will change. Scoble will bring you the best from his travels visiting R&D labs, startups, and innovators around the world.
He views the world through his rose-colored-mixed-reality glasses, which will be the new user interface for self driving cars, Smart Cities, IoT, and many other things in our world.
He'll send you off with some lessons for companies both large and small.
++++++++
SPEECH ABSTRACT #3:
"Personalized Meaning: What is Augmented Reality For?"
As we enter a far more technological world where even cars drive themselves, I predict we'll see a blowback toward the analog, more authentic world.
What role does augmented reality play in both worlds?
Get Scoble's insight into where augmented reality is going, see tons of real-world demos, and understand what he means by 'personalized meaning.'
CONTACT:
If you are looking to contact me, email is best: scobleizer@gmail.com.
++++++++
ENDORSEMENTS:
IZEA Top 25 Tech Influencers: https://izea.com/2017/07/07/25-top-tech-influencers/
Time: One of the top 140 Twitterers!
FT: One of the five most influential Twitterers!
Inc. Top 5 on list of Tech Power Players You Need to Know: http://www.inc.com/john-rampton/30-power-players-in-tech-you-need-to-know.html
Next Reality: #4 on top 50 AR influencer list: https://next.reality.news/news/nr50-next-realitys-50-people-watch-augmented-mixed-reality-0177454/
View all posts by Robert Scoble
lack of good obfuscation tools suck – even after obfuscation thr .NET code is too easy to decode – so intellectual property is not preserved so goodcas in Java or in native (non-managed) code.
LikeLike
lack of good obfuscation tools suck – even after obfuscation thr .NET code is too easy to decode – so intellectual property is not preserved so goodcas in Java or in native (non-managed) code.
LikeLike
1) TabPages can’t be disabled and the appearance of the tabs themselves can’t be changed (to make it look like it’s been disabled for example). This is basic stuff. Incidentally, the docs in 2005 mistakenly say that you can set the Enabled property in several places.
2) DataBinding – It’s better, but still lacks some basics. If a textbox is bound to a varchar(20) in an ADO.NET DataTable, why does it let you type in more than 20 characters? If you bind it to an integer, why can you type in letters? I understand that you can used masked textboxes, but come on…
3) I won’t go too much into data access/manipulation because it looks like LINQ will go a very, very long way. However… If I have access to my data source during development and during deployment, wouldn’t it be great if the information for making DataTables strongly typed coud be pulled dynamically from the data store cached instead of being in a static XML file that breaks things when the data structure changes? Once the design was firmed up, I could have the option of creating and using static XML. The only thing that really “should” break when the data schema changes are the select statements that explicitly name colmns that no longer exist.
4) Wouldn’t WITH {} blocks be nice in C#?
WITH this.tabControl1.Pages[“tabPage1”]
{
.BackColor = Color.Red
.ForeColor = Color.White
etc…
}
Maybe a personal preference, but easier to type, read and understand for me than
TabPage tabP1 =this.tabControl1.Pages[“tabPage1”]
tabP1.BackColor = Color.Red
tabP1.ForeColor = Color.White
etc…
5) Better control over the appearance of disabled controls such as giving us .DisabledBackColor and .DisabledForeColor properties.
LikeLike
1) TabPages can’t be disabled and the appearance of the tabs themselves can’t be changed (to make it look like it’s been disabled for example). This is basic stuff. Incidentally, the docs in 2005 mistakenly say that you can set the Enabled property in several places.
2) DataBinding – It’s better, but still lacks some basics. If a textbox is bound to a varchar(20) in an ADO.NET DataTable, why does it let you type in more than 20 characters? If you bind it to an integer, why can you type in letters? I understand that you can used masked textboxes, but come on…
3) I won’t go too much into data access/manipulation because it looks like LINQ will go a very, very long way. However… If I have access to my data source during development and during deployment, wouldn’t it be great if the information for making DataTables strongly typed coud be pulled dynamically from the data store cached instead of being in a static XML file that breaks things when the data structure changes? Once the design was firmed up, I could have the option of creating and using static XML. The only thing that really “should” break when the data schema changes are the select statements that explicitly name colmns that no longer exist.
4) Wouldn’t WITH {} blocks be nice in C#?
WITH this.tabControl1.Pages[“tabPage1”]
{
.BackColor = Color.Red
.ForeColor = Color.White
etc…
}
Maybe a personal preference, but easier to type, read and understand for me than
TabPage tabP1 =this.tabControl1.Pages[“tabPage1”]
tabP1.BackColor = Color.Red
tabP1.ForeColor = Color.White
etc…
5) Better control over the appearance of disabled controls such as giving us .DisabledBackColor and .DisabledForeColor properties.
LikeLike