I started my career working in the semiconductor industry back in the early 90’s. By that time, Intel had firmly established itself as the leader in the microprocessor space. They were in the process of moving their 486 to mainstream production. In fact, the first personal computer I purchased had a 486 processor that operated at a blazing 20MHz.
Being inside the industry, I was generally in awe of Intel. They were on the cutting edge of semiconductor development. They were the creator and keeper of Moore’s Law, which stated the number of transistors on a computer chip would double every two years. It was a law which drove Intel for over 50 years.
Given my history in the industry, and on the recommendation of a good friend and a trusted recommendation source (Brad Feld’s blog), The Intel Trinity: How Robert Noyce, Gordon Moore, and Andy Grove Built the World’s Most Important Company by Michael S. Malone felt like an interesting book to read. I’ve read quite a few biographical business books, but never one that was directly related to industry I was involved in. That reason alone had me eager to learn more about how the most influential company in the semiconductor industry came to be.
One of the better habits I’ve developed over the last couple of years is setting aside 10-20 minutes in the morning to read. The books I read during this time are geared toward personal development. They are about business, leadership, personal growth, and related topics. As someone told me a few years ago, if you’re able to read 10-15 pages a day, you end up completing a book every month. Over the last two years, I’ve read over 25 books this way.
It shouldn’t be much of a surprise that Start With Why by Simon Sinek ended up as one of my morning reads. It was recommended through Sean Murphy’s blog that I follow, SKMurphy. The book’s also highly rated and has received plenty of positive press since it’s release in 2009. Given the short shelf life of most business books, part of my curiosity was to see if the ideas in the book were still relevant almost 10 years later.
For a recent project, I decided to make the leap and go serverless. For smaller or new projects, the benefits had become too attractive to pass up – low startup and lower overall costs, on demand scaling, no servers to maintain or manage. What’s not to love?
For the APIs, going serverless is a no-brainer. Lots of people have done it, there are plenty of examples, and the cloud providers have extensively documented the process. When it comes to running a serverless database, not so much. I really liked the idea of using Amazon’s Aurora Serverless MySQL for the back-end, but my biggest stumbling block was connecting to it in case I needed to do database administration tasks.
After some online research, piecing together a few articles, and a bit of experimentation, here’s how I setup a serverless MySQL database using Amazon Aurora and then connected to it with HeidiSQL to manage it in a Windows environment.
Running a technology business, I’m always on the lookout for ways to tweak or improve processes, particularly around new product development. As a smaller company, resources are valuable and precious. Chasing a new product that doesn’t pan out can have dire consequences for the business. You want every advantage you can get screening product ideas and determining product-market fit.
We’d implemented agile methodologies in our development workflows, but these concepts have more of an impact on scheduling and getting product releases completed. They have minimal, if any impact on what product or features should be built. If what is getting put into the top of the development funnel isn’t a viable product, it doesn’t matter how fast or how good the product is that comes out the other side. You need to have a good methodology in place for building the right stuff.
For suggestions in this area, I turned to Sprint – How to Solve Big Problems and Test New Ideas in Just Five Days by Jake Knapp. I wanted to get ideas and gather insight into evaluating and fine-tuning new product ideas.
As part of my day job running a web/application development company, I regularly think about the web versus native app debate, especially when it comes to mobile. A recent article on one of the (few) websites I follow these days titled ‘Better Than Native’ on CSS-Tricks got me thinking again about the web vs native debate. It made me consider the current state of affairs and whether the web can and will win, and what it might take for that to happen.
Autobiographical business narratives are generally not my thing. I’ve read enough of them to know the general format. The beginning of the book is a recount of how the narrator built their business, the middle tells how the narrator overcame various trials and tribulations to achieve the pinnacle of success, and the remainder of the book is either a defense of their character, an explanation of why their company is not evil, or a lecture on how to grow and run a business. I find the beginning of the books interesting, and then tend to zone out through the rest.
Therefore, it was with a bit of trepidation that I picked up Shoe Dog by Phil Knight. I wasn’t excited about reading it, but it was very highly recommended by a close friend and had also received a good review on Brad Feld’s blog, where I’ve gotten many, many good book recommendations.
My go-to resource for web analytics is Avinash Kaushik. Guru does not adequately describe his level of expertise on the topic. If you have any interest in analytics, his blog is a great resource that is chock full of information. The articles are deep dives into the concepts, techniques, and tools that allow you to get the most out of your online presence. For bite-sized pieces of insight, I’d recommend subscribing to his newsletter, which you can do from his website.
So what does Avinash Kaushik have to do with the book Be Like Amazon: Even a Lemonade Stand Can Do It? In June of last year, Avinash mentioned the book in one of his newsletters. I have such high regard for his opinions and insights, that I immediately added the book to the top of my reading list.
I wasn’t disappointed.
Every so often, I like to read a business book on industry strategy. It’s even more interesting when the book is about an industry that I have a lot of contacts in and spend a lot of time working around – real estate. It made reading Disruptors, Discounters, and Doubters by Joe Rand an easy choice. For one, it was an excellent opportunity to gain valuable insight into the real estate industry and where it’s headed. Second, I know Joe personally and have on-going projects with him. I figured his book would provide a better, deeper understanding of the goals behind the projects we’re working on together.
What makes the book especially valuable for anyone working in and around real estate is that it is an insider’s view of the industry. More often than not, industry strategy books are written by outsiders who forecast or critique based on observation. Joe is writing his critiques while in the trenches. He has the foresight to see that disruption of the real estate industry is on the horizon. In fact, it’s inevitable. He’s raising the warning flag and suggesting that the disruption happen from within. Otherwise, those with little or no industry knowledge will force it on them from the outside .
When it comes to work, there are a few principles that are important to me. One is to always be learning new things. A second, closely related principle, is to continuously improve. As part of living out these tenets, I like to read books that I can apply to my business. Because time is precious, I look to trusted sources and watch what other CEOs are reading and recommending to add to my reading list. I learned about the book Scrum: The Art of Doing Twice the Work in Half the Time by Jeff Sutherland and J.J. Sutherland through Matt Blumberg’s Return Path blog. He had great things to say about the book. Since I run a software development business, it was a no-brainer to make sure I read the book during 2017.
With most books, it’s pretty clear what you’re going to get when you read them. Others can surprise you. I’d have to put Setting the Table by Danny Meyer in the latter category.
I received the recommendation from a customer I started working with last year, who I would now consider a good friend. When we started working on a project together, he suggested that I read the book. My first thought was, “a book by a guy who runs restaurants, how could it possibly apply to my technology business?”
Turns out, the book is very applicable to my business. In fact, anyone running a business that deals with customers, meaning every business owner, can benefit from the lessons and experiences Danny Meyer’s shares.