Recently the world encountered the terrible security bug called Heartbleed and some have called it the “worst” vulnerability ever discovered.
Obviously I care about security as our transport layer delivers data to multiple systems and APIs for our users. I spent some time fixing any possible vulnerabilities, especially the API that I’ve created to do the delivery.
Just wanted to let you guys know that we’re all good and you can safely and securely continue to publish your visual stories to your own properties and networks!
Eww. So big…!
I had a quick conversation with my father the other night right after I had learned that my youngest had fallen off of our zipline in the backyard and really busted up her ankle and leg.
I had just landed in Houston to spend 4 days with the local team here to help launch our new campuses as we take over the great state of Texas (and eat some great Texas-sized food) and my family needed me back home asap.
Ah, what to do, what to do!
Building a successful product and company takes a lot of effort, a lot of sacrifice, a lot of incredible execution and, if we’re honest with ourselves, a whole truckload of luck. We can have the best laid and strategic plans as well as the most tactically-defined roadmap but in the end the future is just as unknown as what you are going to have for lunch today (or tomorrow).
You see, the simple truth is this: Planning for your startup is as good as guessing. I’ve had more than a handful of ventures at this point and I’ve seen this truth work itself into every single scenario.
It’s not that planning is a bad thing; quite the opposite as it’s a very important part of building your product, service, and bringing it to market but where it can trip up founders (especially new startup founders) is when they put all their “eggs” in this planning process and thus reduce their ability to pivot, to change, to be flexible with their venture in ways that will be necessary.
Above is the famous “Startup Curve” that is a pretty realistic depiction of what it’s like to start and live through the experience of a new venture. The chart, courtesy of Paul Graham, is scary in its accuracy as I can tell you from first-hand experience that this is exactly what it’s like.
I’m trying to determine exactly where Pressgram is on the “process” and “curve” – are we in the “Trough of Sorrow” where disillusionment, anxiety, and doubt are the themes of the day (week / month / year)? Or are we seeing some “Wiggles of False Hope” as we entertain things like a possible Featured Spot in the App Store?
The honest truth is that it’s hard to know.
I’ll be helping to coach and mentor teams at Startup Weekend in Athens, GA in less than 2 weeks! Will you be there? Come and hang and we’ll have some fun.
Heck, you might even be able to startup that new project or even company that you’ve always wanted… why not? See you there?
Because stuff like this really, really matters.
Amazing! It would be so cool to see some Tron-like action and a killer story to boot.
I’ve been asked more than a handful of times where and how I teach myself a new coding language most recently being Obj-C and related pairing technologies and IDE of XCODE.
Time and time again I have disappointed my audience by telling them that I started with the very basics and that I did not do much more than just spend time diving deep into the existing material provided by Apple. Specifically I start with the Developer Documentation and went from there.
Why, then, is the answer that I give such a gross disappointment? Why do people look at me sideways and continue to ask as if my answer is not good and decent enough? They ask me for websites or online tutorials or paid curricula and I return their blank stare with my own. It’s as if they expected that being a seasoned software engineer excused me from having to learn the basics!
I encountered this question once more today and it was just another moment to reflect on this strange exchange and I have discovered the tragic truth that underscores their disappointment.