Projects, Podcasts and Articles
Lifelong Learning
Sharing Knowledge
Creating Value
Giving Back
Mentoring
Projects
The Truth about Vibe Coding with Windsurf…Better than Cursor? – Video series documenting my journey and challenges with Windsurf and Claude Sonnet 3.5.
Options to Cashflow – I have thrown myself into the world of Stock Options to supplement my income. In this course, I will discuss strategies and the psychology of successful stock option trading. Turn your assets into cashflow!
Remote Scorecard – Think Glassdoor for remote companies. The best remote companies do more than allow employees to “work from home”. Their culture is built around supporting and nurturing remote work and they follow a similar formula. The best “Remote First” companies eventually evolve into “People First” companies.
Chief Remote Officer – Training and consulting to help make your company more “Remote First”.
“Making Remote Work, Work For You” Kindle Book – Written before the pandemic and just as relevant as ever. A timeless classic.
Podcast Appearances
Product Driven – “We Still Need Software Engineers, Even With AI”
Be Remote – “Making Remote Work, Work For You”
Distant Job – “Why Some Companies Fail at Building a Healthy Remote Culture”
Articles
Review of AI Code Tools – A multi-part series on my experiences using AI coding tools to create Enterprise level software. Just how close is AI to replacing software developers?
The Case for Bitcoin in 2025 – Cryptocurrencies are confusing, volatile and seem to lack any practical purpose. Yet there are still some very smart people saying 2025 will be the year that Bitcoin goes to ONE MILLION DOLLARS per coin. But why?
The Importance of Whole Company Support – Teams do their best, and most valuable, work when they have a deep understanding of their products, domain and customers.
Quality is Everyone’s Job: How to Get Your Dev Team to Embrace Automation – In an attempt to maximize efficiency, many organizations are asking Developers to contribute more to the testing effort, blurring the lines of responsibility between “Development” and “QA”. After all, nobody knows the code better than the Developer who wrote it… but are they really the best candidates to test it?