Atypical Engineer

Habits, commitment, and discipline. Three things you need on the road to a better career as a software professional.

The most important thing for SW Engineers to know as they embark on a career in entrepreneurship.

People continue to try to out do each other and think that stacking programming languages on their resume is going to get them paid more, but that's not true.

Rant time. Trends around the globe aren't going to allow for software engineering work to continue with such high costs. If you think you're going to keep making $100k writing Javascript code, ask the 1970's Auto Workers how that's worked out for them. How do you prepare yourself?

How does "Software Partner to the Executive Team" sounds is a great sentence to hear. Yesterday I previewed an upcoming meeting with an execs form a big company to hear a pitch of some software I've been building. Tune in to see what happened and how to leverage a 30 minute meeting into something awesome.

There are moments of clarity when the truth of your message is painfully obvious. Today I have to pitch a business idea and software to C-level executives. Doing this with the Engineer hat on is a surefire way to fail. Want to know why this show and it's message is important? Here it is.

Remember those stupid physics problems that had the whimsical backstories of somebody calculating the coefficient of friction of their milk carton against a lunch table? That's you being taught not to think about which problems are even worth solving. Now you're left with an inability to find problems which need solving, and whether or not they are profitable to solve. 

Were you intrigued by Engineering because it was the most difficult path, only to discover the truth.. In the real world, engineers are essentially replaceable and the occupation gets only an average amount of respect. Now it's time to do what people in the real world respect....business. But you don't have the skills. Here is a short version of my story and why I'm doing this show.

It's too easy for people who came up as engineers to get started building a solution before they know if a problem exists. That's because there is an underlying assumption that any problem that they needed to engineer a solution existed for a reason. But rarely do they use their engineering skills to solve for the problem of "which problem to solve".

A few minutes about what you will get from listening to this show. Just because the name is vague doesn't mean the purpose is.