Startups live and die by the velocity and the resulting momentum that they build as they continue to iterate and scale.
And the lack of velocity and momentum is what can certainly kill any organization of any size! Whether it’s engineering, product marketing, sales, or human capital, if an organization doesn’t have and increase momentum then the end is an inevitability.
“Never stop learning” is a trustworthy adage that everyone can agree with. But what I’ve discovered is that there are two types of learners out there, the first are those that are proactive in their efforts to continue learning and then there are those that are less so.
It’s not that the latter group doesn’t continue to learn – they do and they can learn a ton! Most folks fall into this group as they continue to build relationships, grow their career, and encounter new challenges through the work that they already do.
One of the things that’s currently “in vogue” right now is machine learning and anything dealing with artificial intelligence and statistical algorithms in software.
In fact, if you don’t have at least one of those things in your startup pitch deck you may be deemed “out of touch” or irrelevant (this is, of course, a joke…).
As we continue to grind on making the Software Development Life Cycle a bit more useful to most folks we’ve been encountering a lot of positive validation from within and without our own networks.
The reality is that most (all?) technology companies just aren’t getting the throughput that they really need to maximize their tools, their systems, and perhaps most importantly, their people.
When a business and organization launches a software product they are executing against the SDLC, a Software Development Life Cycle (or sometimes just generically called “Systems”).
Regardless of how codified the organization’s system might actually be, they still execute against it in gist, the general process of planning, developing, testing, and then deploying software into the wild.
I’m excited to share that I’m opening up a small “internship program” today!
The reason for the quotes is that there’s a part of me that doesn’t want to call it an internship but that’s what it essentially is, so, I’ll dispense with the creativity and call it what it is!
If you’re interested then continue to read! If not, well, there’s always yesterday’s issue of #EngOps which has some really good content to read, curated by yours truly!
A short but quick update today folks!
Just wanted to share with you the “soft launch” of a small Slack Community that we’re putting together to congregate folks within our community.
I’ve already spoken a bit about our efforts to grow a platform and a community around our early-stage company and because we know that it works we’ve been at it since Day #1 (and we obviously encourage you to do the same!).
Our motivation was simple and we decided, among many other reasons, to take and heed the advice of David Bailey (whom I’ve already quoted before):
In software engineering, the details really do matter.
Our world was quickly reminded of that with the recent AWS outage that was caused by human error, a small yet powerful command that was, unfortunately, committed incorrectly:
Unfortunately, one of the inputs to the command was entered incorrectly and a larger set of servers was removed than intended. The servers that were inadvertently removed supported two other S3 subsystems.
And the world came to a screeching halt and organizations lost hundreds of millions of dollars in revenue.
As most things go, context can change everything, from the way that you and I see the world and how we interact with it and, most importantly, how we ultimately make decisions.
Encountering someone we’ve never met at 2:00 in the morning is entirely different than encountering someone we’ve never met at Whole Foods during lunch hour.