Viewing profile — bwh2

Two good ones: 1) Where Wizards Stay Up Late and 2) How the Internet Happened: From Netscape to the iPhone

The primary cost differences I have experienced come with maintenance and fees, not the initial build. Maintenance = iOS version updates, dependency upgrades, App Store requirement…

I highly recommend the book System Design Interview by Alex Xu.

Although you wouldn't expect it, the book Monolith to Microservices presents solid arguments against microservices. The author cautions against using microservices throughout the b…

Difficult Conversations. So much stress and anxiety comes from anticipating, avoiding, or not knowing how to have difficult conversations.

It sounds like retention is your problem, less so acquisition. Have you talked with customers to understand why they are leaving your product?

Agreed. That was the point of my comment - there is an abundance of developers who just work in JS/TS/React and have not picked up new technologies. Adding C#, Java, SQL, etc. help…

It would help both in demonstration of interest in learning that language further and in being able to pass technical interviews.

As a hiring manager who looks at a lot of resumes, I think your hunch is correct. I see a lot of junior to mid-level developers that primarily work in JS/TS/React. That market is h…

Similar size company and over the past 2y we transitioned from technology based teams to stream-aligned teams that include engineering, product, and design within each team. The bo…

Consider focusing on managing the team through this: "there are a lot of skeletons in the code & infra to worry about." Sometimes what happens is you have seniors who know the tech…

A few books that influenced my product thinking: The Cold Start Problem, Working Backwards, and Strategy Rules.

Most people have not developed the habits and discipline necessary to benefit from a plan.

These are both well written and happen to be about writing: On Writing Well by William Zinsser and On Writing by Stephen King.

The Five Dysfunctions of a Team is similar in style and a good read.

Difficult Conversations

Some of my favorite books around managing software projects and technical leadership: * The Manager's Path - read the chapter on being a Tech Lead * Making Work Visible * Accelerat…

The Cold Start Problem and Matchmakers are two good books about marketplace dynamics.

Focus on naming accuracy. Clear thinking is often apparent in how variables and methods are named.

A few books that I enjoyed: * How the Internet Happened: From Netscape to the iPhone * Where Wizards Stay Up Late: The Origins of the Internet * Masters of Doom: How Two Guys Creat…

A few books that are relevant to your situation: * High Growth Handbook - covering the operations and biz side * The DevOps Handbook - developer effectiveness in larger orgs with e…

Drift Into Failure is a good read about how systems fail, albeit a little light on solutions.

TrainingPeaks | Colorado or Remote in USA | Full-time * Software Engineer (0-2y experience) * Senior Software Engineer (+4y experience) Athletes and coaches around the world use Tr…

I have a big list on my website at https://www.briansnotes.io/books/ but here are a few: * The DevOps Handbook - Lots of tactics for improving the productivity and effectiveness of…

I live and hire people in Colorado, and a bunch of recruiters contact me about remote roles. Most companies that fear transparency just advertise very broad ranges, e.g. $100-200k.…