Skip to main content

The Unbuilt Software Trap

· 6 min read
Kam Lasater
Builder of things

Blank polaroid photograph

Everyone fails at software they don't build

There are three types of software systems that any company runs. First, high value software systems that drive customer value. Second, the systems necessary to deliver the product or service, but not sufficient as stand alone products on their own. Third, systems that support the business but are not related to the competitive advantage of the company. The fourth type of software system is one that doesn’t exist. Every company has software they chose not to build. This is "Unbuilt Software". To understand how much value organizations are missing out on, we must first better understand each type of software system and how software investment decisions are made.

Users Are the Best Feature

· 3 min read
Kam Lasater
Builder of things

Crowd at a concert

As an engineer I like to talk about the features of a product. I talk about the product’s implementation and how it was built. I get excited about the internal workings. I have spent days of my life working on features that were never used. I operated under a mental framework that users came from outside and were external to the product. I was concerned with building the product. The users would be there when I was done. So I spent most of my time heads down writing code.

The Right KPIs

· One min read
Kam Lasater
Builder of things

Graph of new visitors to site

Chasing the wrong KPI is like chasing a mirage of water in the desert.

Check out our trailing twelve month site analytics above.

Our marketing and user acquisition was awesome in Feb, right? More of that?

Talking About Failure

· 4 min read
Kam Lasater
Builder of things

Awwww snap!

When I was a younger I went on several rock climbing and mountaineering expeditions. I was exposed to some instructors and practitioners that took staying safe in the mountains very seriously. One of them carried a book from The American Alpine Club on climbing accidents. The accidents were never the cause of a single bad choice. They were caused by a series of decisions, taken over time, that combined to create the conditions for the accident.

How to Get Your First Developer Job

· 5 min read
Kam Lasater
Builder of things

I've hired roughly 30 developers where the job would be their first professional position as a developer. I interviewed nearly 150 candidates. I reviewed resumes for about 300 candidates.

None of this is certainly going to get you hired, the goal is to just improve your odds. Also, each hiring manager is different. Sometimes the person doing the screening and first line interview may not have ever coded. This advice is much geared to increasing your odds with a hiring manager who is technical.

How to Fail at Serverless: Serverless is Stateless

· 5 min read
Kam Lasater
Builder of things

This blog series is an extended version of a talk I gave at Serverless Days NYC 2022. The goal is to share ways that a "friend of mine" has failed at serverless to help level up the community. Just as the transportation industry shares accident report analysis with the whole industry to improve safety, we in the software community need to do the same. This is my attempt to do that.

6 Command line Tools All Experts Know

· 3 min read
Kam Lasater
Builder of things

I work on Mac OSX and Linux command line environments. My tool kit is shaped by the needs I have. This is my tool box of tools that work with almost any command and help me go from just using the command line to being an expert. Wow, your friends and colleagues. These tools make every other command at the command line more powerful.