bwh2

5 ms·

1.
by bwh2 2y ago
Two good ones: 1) Where Wizards Stay Up Late and 2) How the Internet Happened: From Netscape to the iPhone
2.
by bwh2 2y ago
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 changes, etc. have been costlier and more out of your contr
3.
by bwh2 3y ago
I highly recommend the book System Design Interview by Alex Xu.
4.
by bwh2 3y ago
Although you wouldn't expect it, the book Monolith to Microservices presents solid arguments against microservices. The author cautions against using microservices throughout the book due to the additional complexity introduced.
5.
by bwh2 3y ago
Difficult Conversations. So much stress and anxiety comes from anticipating, avoiding, or not knowing how to have difficult conversations.
6.
by bwh2 3y ago
It sounds like retention is your problem, less so acquisition. Have you talked with customers to understand why they are leaving your product?
7.
by bwh2 3y ago
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. helps your marketability.
8.
by bwh2 3y ago
It would help both in demonstration of interest in learning that language further and in being able to pass technical interviews.
9.
by bwh2 3y ago
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 heavily saturated and I regularly read posts on Lin
10.
by bwh2 3y ago
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 book Team Topologies is a good reference for this and fairly q
11.
by bwh2 3y ago
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 technology and product inside and out, but don&#x2
12.
by bwh2 3y ago
A few books that influenced my product thinking: The Cold Start Problem, Working Backwards, and Strategy Rules.
13.
by bwh2 3y ago
Most people have not developed the habits and discipline necessary to benefit from a plan.
14.
by bwh2 3y ago
These are both well written and happen to be about writing: On Writing Well by William Zinsser and On Writing by Stephen King.
15.
by bwh2 3y ago
The Five Dysfunctions of a Team is similar in style and a good read.
16.
by bwh2 3y ago
Difficult Conversations
17.
by bwh2 4y ago
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 * Accelerate My website has more book reviews on
18.
by bwh2 4y ago
The Cold Start Problem and Matchmakers are two good books about marketplace dynamics.
19.
by bwh2 4y ago
Focus on naming accuracy. Clear thinking is often apparent in how variables and methods are named.
20.
by bwh2 4y ago
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 Created an Empire and Transformed Pop Culture
21.
by bwh2 4y ago
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 examples * Monolith to Microservices - how to execute
22.
by bwh2 4y ago
Drift Into Failure is a good read about how systems fail, albeit a little light on solutions.
23.
by bwh2 4y ago
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 TrainingPeaks to be their best. https://tr
24.
by bwh2 4y ago
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 engineering teams * Extreme Pro
25.
by bwh2 5y ago
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. I'm sure some companies refuse Colorado employees, but
26.
by bwh2 5y ago
Physical book, highlighter, and pen for taking notes in the margin.
27.
by bwh2 5y ago
Two books: * The INTP: Personality, Careers, Relationships, & the Quest for Truth and Meaning. This book helped me understand my own journey in life. * How to Win Friends and Influence People. A little cliche, but reading this book drov
28.
by bwh2 5y ago
Read Peopleware. Right now you're focused on mechanics like standups and retros, but for those to be effective you'll need to really grasp underlying principles. As for career path, read The Manager's Path.
29.
by bwh2 5y ago
The book System Design Interview is quite good and pragmatic. Personally, I found Designing Data-Intensive Applications less useful because it works on a much lower level. Like if you want to know how database internals work, then read DDIA
30.
by bwh2 5y ago
Read The E-Myth Revisited to really understand the difference between working on the business and working in the business.

More ›