One email per week, 5 links.
Would you like to learn how to build better teams, improve your leadership skills, and company culture?
Keeping up to date with all the blogs, podcasts, and articles is time consuming so why not let someone else curate the content for you?
With our weekly newsletter you will get five top stories hand-picked into your inbox every Monday.
This newsletter is perfect for every CTO, engineering manager, team leader, technical lead, or senior engineer who wants to learn more about the human side of software development.
Escape the distractions of social media and own your focus. Check out the latest issue and subscribe!
Tech Lead Digest#95
PostHog's product analytics suite has everything product-led teams need in one place. Heatmaps, Session Recording, Funnels, Feature Flags, Experimentation and more — all seamlessly integrated. And you can self-host, so user data never leaves your infrastructure.
this week's favorite
RFCs - requests for comment - or Design Docs are a common tool that engineering teams use to build software faster, by clarifying assumptions and circulating plans earlier. There are some similarities between writing automated tests for your code, and writing RFCs before you start working on a non-trivial project.
His good news was that his new company provides essential services and regardless of how much they stumbled they were going to be in business for a long time. But the bad news was that the company wasn’t keeping up with new technologies and new competitors who were moving faster. And the fact that they were an essential service made the internal cultural obstacles for change and innovation that much harder.
Software architecture needs to be wrested from committees of people disconnected from developing, and to put it in the hands of the people who can actually make it real and executable, the developers. Only then will we achieve the resilience and sustainability that we need from today’s applications
Many software teams describe desired product capabilities as a product backlog: a list of user stories. These stories capture who needs the work, what the work is, and why it's needed. Too often teams expect a product owner to be the sole source of the backlog, but anyone could (and should) write user stories
There are two projects, both deemed important by the business, and both need a UI developer. Unfortunately, only one UI developer is available. The manager has an idea though: why not just let the UI developer split his time across both projects. Sure, this will slow the pace a bit for each project, but at least they'll be moving in the right direction.
Deploy High-Performance Database Clusters in Modern Applications. Develop a high-level understanding of industry-standard databases, the design of database architectures, and different deployment methods in the cloud. Download instantly — no registration required. Download Now.
or subscribe with
Join 5,400+ readers for one email each week.