Digests » 433

this week's favorite

Best practices for writing code comments

While there are many resources to help programmers write better code—such as books and static analyzers—there are few for writing better comments. While it's easy to measure the quantity of comments in a program, it's hard to measure the quality, and the two are not necessarily correlated. A bad comment is worse than no comment at all. Here are some rules to help you achieve a happy medium.

Zero based versioning

With software releases at an all-time high, the consensus has never been clearer: Major versions are over. So what does the past, present, and future of software versioning look like? Welcome to ZeroVer 0.0.1.

There is no benefit for developers to create quality code

Quality is the responsibility of the culture of the team and the senior members of the development team. The customer and non-technical people won’t understand or value the quality steps in development, but you have to insist on it.

HTTP/3 From A To Z: Core Concepts

After almost five years in development, the new HTTP/3 protocol is nearing its final form. Earlier iterations were already available as an experimental feature, but you can expect the availability and use of HTTP/3 proper to ramp up over in 2021. So what exactly is HTTP/3? Why was it needed so soon after HTTP/2? How can or should you use it? And especially, how does it improve web performance? Let’s find out.

20 questions a software engineer should ask when joining a new team

Different software development teams do things quite differently. Even within a single company, many of the variables can vary from team to team. As a software engineer, it is usually very exciting to start working with new people and on new software. On a personal note, I recently have started with a new team and on new (to me) software. Because this isn’t a regular or frequent occurrence, I took the opportunity to really think about things that I needed to learn in the short term.