Tuesday 18th April's issue is presented by QA Wolf
Is feature development outpacing your ability to maintain quality? QA Wolf will build, run, and maintain your automated end-to-end test suite so you can ship confidently, without bugs reaching production.
tl;dr: “I’ll pitch the takeaway up front, and it’s this: hold yourself accountable for making decisions and progressing discussions as quickly as possible, by whatever means necessary. Be restless while a decision hasn’t been made. Dead time is your enemy. Be creative about ways of shaving minutes, hours and days from a decision point.” James gives several examples of how to approach this.
tl;dr: “A common approach with timeboxed iterations is to allocate as many user stories as possible to each iteration in order to maximize the utilization of the staff involved. Slack is the policy of deliberately leaving time that isn't allocated for stories, using that time for unplanned work. Although this seems inefficient, it usually yields a significant improvement for the productivity of a team.”
tl;dr: We talk to a lot of engineering leaders about QA and end-to-end testing. Something we hear all the time is how difficult it’s been to scale their automated test coverage beyond a few key workflows. Here are the three obstacles that are faced by companies of all sizes.
tl;dr: “The study analyzed the calendars of 27 CEOs, coding 60,000 hours. The study found that having explicit priorities and structure for your calendar and evaluating how you spend your time are some of the most important things you can do to end up spending the majority of your time on your strategic priorities.” Molly gives templates and examples.
tl;dr: From the engineering team at Slack, “we’ll describe the architecture that we use to send real-time messages at scale. We’ll take a closer look at the services that send the chat messages and various events to these online users in real time.”
tl;dr: “I realized that iMessage just stores its database locally as a sqlite file, so I went about building an alternate UI for searching, and adding in a few features that I thought would be interesting. These include: (1) Semantic Search (2) Wrapped: stats about my life on iMessage (2) AI conversations with friends. And more.
tl;dr: “In this post we're going to focus on the ways that a single load balancer might distribute HTTP requests to a set of servers. We'll start from the bottom and work our way up to modern load balancing algorithms.”
tl;dr: “I really like using programming playgrounds, and I got thinking the other day about how I didn’t have a great list of playgrounds to refer to.” Julia provides us with a laundry list of playgrounds across multiple categories.
