257 private links
Every couple of years in software development, the meta changes. Libraries and frameworks are rotated in and out of popularity, languages evolve and best practices change. These are some of my personal beliefs1 on what the current meta is, and what parts are worth adopting.
Now is better than never.
Although never is often better than right now.
- Use statically typed languages over dynamically typed languages
- Use automatic formatting
- Parse, don’t validate
- Use union types
- Parse, don't validate
- Avoid abstracting too early
- Be aware of monads and functors
- Accept that generative AI is here to stay
- Prefer integration tests over unit tests
- Be kind during code reviews
- Respect a candidate’s time
- Pair or mob program frequently
- Pick a git commit format and stick to it
- Use Dependabot and friends for dependency maintenance
- Write infrastructure-as-code
- Use platforms that allow developers to focus on the code
- Use queues as data sources
Find relevant indexes to set based on the usage of the postresSQL database.
Avoid a round trip for the slow start TCP algorithm. Depending of the internet connexion it can save 100s of ms.
This cookbook is intended for new Rust programmers, so that they may quickly get an overview of the capabilities of the Rust crate ecosystem. It is also intended for experienced Rust programmers, who should find in the recipes an easy reminder of how to accomplish common tasks.
How to link webmentions.io messages, likeCount, replyCount and reportCount to a personal blog with a few JS lines.
A great media query for example disabling custom fonts!
Project Wallace is a set of CSS analyzers that check your complexity, specificity, performance, Design Tokens and much more. And all of that in a single web app.
Because of modularity
A list of triangle shapes that can be reused
background-repeat: space makes the background kind of responsive.
If you implemented this, and then you deleted all but one of the call sites, would you be tempted to inline the abstraction? If yes, you shouldn’t do it.
More techniques than Resource: The Complete Guide to Centering in CSS | Modern CSS Solutions.
It covers a lot of cases:
- when the element size is known or unknown
- depending of the layout algorithm currently used
As I write this in early 2024, browser vendors are in the process of implementing align-content in Flow layout, so that it controls the “block” direction alignment of content.
🤯 so we will be able to stick to the default layout.
So, for many years, I treated CSS like a collection of patterns. I had a bunch of memorized snippets that would paste from my brain, to solve whatever problem I was currently facing.