Build momentum with these small projects that you can finish in an afternoon. Start, implement, and finish. Working through projects quickly will dramatically improve your self-esteem and skills. 00:00 Why quick wins are so important00:35 Not for beginners01:14 Connect Four02:07 Build an API for public information02:50 Deploy a dice roll Lambda04:03 Create a simple mobile app04:57 Real-time transit data feed05:45 Build a live chat with websockets06:40 Pull your financial data using Plaid07:42...

This week on the podcast, I share my experience and insights on starting a consulting business. Covered in this episode: How to find your niche Horizontal vs vertical specializations Product, service, or productized service How to acquire your first clients Scoping projects Pricing services based on value Starting a consulting business is really hard! It won’t solve all your problems to work for yourself — in fact you’ll probably have more problems. But it can also be really cool, if you can...

I discuss the dilemma of whether or not to refactor code that may not have the best design.  There are always trade-offs involved in leaving messy code versus investing time in making it better designed. It’s not straightforward whether you should undertake a refactor. Understanding the scope of the refactor is also critical. Your changes can have a big impact on future developers and the overall system. In the video, I provide a set of questions to ask oneself before undertaking a refactor...

Over-commented code is often more difficult to understand than code without comments. If you can avoid writing a comment then don’t. Let your code stand on its own!  Article: https://levelup.gitconnected.com/youre-commenting-your-code-too-much-and-other-controversial-thoughts-on-documentation-1ee617ed46af Daily email: https://bennettgarner.ck.page

When you assume the junior title, you undercut your career & growth. You probably have what it takes - right now - to work as a full software engineer.  Site: www.developerpupose.com Daily email to 2k developers: https://bennettgarner.ck.page

Consistently working on something every single day produces more results than massive effort that you allow to fizzle.

Breaking production is almost a right of passage. Take full responsibility for fixing it & don't feel guilty.

Companies are insulting developers with their interview process.

Imagine having near 100% recall of past projects. That’d be pretty helpful as a software developer, right?

Some day you won’t do this anymore. Are you prepared to one day leave coding behind?