/Management

Code Documentation In The IDE

- Eden Hermelin tl;dr: Documenting your codebase doesn’t have to suck. Forget code comments or “self-documenting code”. IDE integrated documentation is slowly becoming one of the most convenient ways to manage knowledge about your codebase and this article explains why. 

featured in #415


Maintaining Productivity As Engineering Teams Scale

- Vasan Subramanian tl;dr: Key takeaways: (1) Deal with technical debt: recognize it, spend time fixing it but justify it. (2) Avoid distractions. (3) Protect old hands: spend time with your senior engineers. They are more valuable than you think. (4) Recognize different skills: create a managerial path and a technical path for people, identify your senior folks as one or the other. (5) Communicate often.

featured in #414


The Complicated Parts Of Leadership: Betting On People

- AbdulFattah Popoola tl;dr: “This experience left me wondering how many teams could be transformed with the proper investment in training and development. And also how many teams are struggling because they are too busy to invest in training.” The author provides the following tips when betting on people: (1) Have skin in the game. You must push past your discomfort and genuinely believe in the team’s abilities. (2) Stay curious and maintain curiosity, even when confronted with obstacles. (3) Verify and have accountability checkpoints.

featured in #414


So You Want To Build End-To-End Tests

- Rebecca Stone tl;dr: A well-built test suite runs faster, gives more reliable results, and makes long-term maintenance easier and cheaper. After thousands and thousands of end-to-end tests, QA Wolf has picked up a few tricks to build fast, stable, and accurate ones. This guide teaches you how.

featured in #414


Best Career Advice

- Mike Fisher tl;dr: "I try to speak with a former colleague or acquaintance at least once per week... The benefit of this for me is the social aspect of catching up with an old friend and sharing some memories and some laughs. It is also a big benefit to me to hear what is happening in their industry or field. In this way I learn about emerging trends, hot topics, areas of concern, and opportunities." Mike discusses how this has helped his career. 

featured in #413


Monoliths Are Not Dinosaurs

- Werner Vogels tl;dr: "I always urge builders to consider the evolution of their systems over time and make sure the foundation is such that you can change and expand them with the minimum number of dependencies." Werner discusses being less dogmatic about architecture allowing it to evolve with its needs. 

featured in #413


Boost Your Team's Productivity With Postman Workspaces

tl;dr: API collaboration is essential for driving development efforts forward. Postman Workspaces help teams streamline the process, ensuring APIs are consistently available, highly performant, and meet consumer needs. Discover how to collaborate effectively at every stage of the API lifecycle in an API-first world.

featured in #413


Measuring Flow And Focus

- Abi Noda tl;dr: Based on a study with Google engineers, the best predictor of flow is “focus time:” performing a number of similar actions in a given window of time. Researchers also identified 3 practices for facilitating flow: (1) Schedule management. (2) Goal setting so engineers are working on tasks that feel fulfilling. (3) Giving time to “get into flow.”

featured in #412


Interviewing Engineering Executives

- Will Larson tl;dr: The topics that Will explores are: (1) Avoiding the unicorn search. (2) How interviewing executives goes wrong. (3) Structuring your evaluation process. (4) Focusing on four areas to evaluate engineering executives.

featured in #412


Benefits Of API Collaboration In An API-First World

tl;dr: Collaboration is the key to successful API development. Whether it's working with internal teams or external partners, effective collaboration can help teams work faster, smarter, and with fewer errors. In this article, we explore the best practices for API collaboration and offer tips for working more effectively across the entire API lifecycle.

featured in #412