My dream was to be a web developer who creates simple, elegant, and fast products, but I’m starting to lose hope. First of all, I can’t keep up with the endless stream of new technologies. Secondly, simple and fast products are not in high demand, making it an already niche area.

Avoid, at all costs, arriving at a scenario where the ground-up rewrite starts to look attractive

Aim to be 90% done in 50% of the available time

Think about pathological data

Edge cases are our entire job.

There is usually a simpler way to write it

Write code to be testable

It is insufficient for code to be provably correct; it should be obviously, visibly, trivially correct

Documentation matters

Good documentation is more than just nice to have—it's a powerful way to spread knowledge. For development teams, clear documentation keeps everyone aligned, helps make decisions visible, and ensures no one has to reinvent the wheel when new people join. For users, it saves time. Poor documentation, on the other hand, leads to confusion, support tickets, and more work for everyone involved.

... all common and good tips. They are generics and I don't find anything actionable though.

Try writing a tax code in chat messages. You can’t. [...] That’s why we use documents

You program by writing documents instead of chatting.

Suite à la prise de fonction du président des État-Unis, Sebsauvage effectue un rappel de ce premier mois.

I agree

If one project using open source technology is successful, then the open source projets will benefit from it.

By default, if you are building with Nuxt, I want you to succeed. If you are a third-party provider with a great Nuxt module or integration, I want you to succeed.

Because

1. open source is a community project
2. compensation doesn't follow value
3. success is contagious

Can one have a project with a relational database that is deployed early and often, and not have thousands of SQL migration scripts? Seems like it’s difficult to have both. Maybe there’s some way to “roll up” old migration scripts into one nice SQL schema. I guess running them all on a new database and exporting the schema will do that. 🤔

Prisma provides a "baseline" to reset merge all migration scripts. There are always many migrations though.

I realized that one of the best things about open source software is that you can solve a problem once and then you can slap an open source license on that solution and you will never have to solve that problem ever again, no matter who’s employing you in the future.

I like to say that my interest in open source is actually really selfish. I figured something out. I never want to have to do this work ever again.

I like to say that my interest in open source is actually really selfish. I figured something out. I never want to have to do this work ever again.

Instead of a "take", use

• Opinion
• View
• Perspective
• Thought
• Judgment
• Stance
• Belief
• Attitude
• Position
• Interpretation
• Reaction

But, when a developer experience feature is baked into the browser, I start to get uncomfortable. I know I can be a bit of a curmudgeon about this stuff, but that isn’t my default setting. That comes from lots of experience of lots of different codebases in my years as a CSS consultant. I’m a stickler for learning from mistakes.

AI is an ideological project to shift authority and autonomy away from individuals, towards centralized structures of power. Projects that claim to “democratize” AI routinely conflate “democratization” with “commodification”.

Ce n’est pas libre, puisqu’on ne contrôle pas du tout la façon dont ce logiciel a été entraîné et qu’il est matériellement impossible (sauf à avoir les capacités de stockage et de calcul d’OpenAI) à reproduire soi-même.

Humans tend to make mistakes at the edges of our knowledge, our mistakes tend to clump around the same things, we make more of them when bored or tired, and so on. We have as a result developed controls and systems of checks and balances to help reduce the frequency and limit the harm of our mistakes.

The mistakes of AI models (particularly Large Language Models) happen seemingly randomly and aren’t limited to particular topics or areas of knowledge. Models may unpredictably appear to lack common sense.

Another possible reason for building a custom desktop computer in the future might be to use alternative components in place of those used by PC manufacturers to intentionally hobble their PC's. The fact that computers are becoming more locked down and less general-purpose should not be a secret.

I had 3 personal laptops during my entire lifetime. It is enough:

• one before college
• one during college
• one nearly after college

On the other hand, games are not really possible on them.

Rust is associated to software engineering. The post confirms rust concepts.

In all cases, it takes time for the worst or the best.

On the contrary I have some expectations.

I exist only at the moment.

I exist for a better future.

If I die tomorrow, I wouldn't mind at all.

I could have don more without dying.

If life is fleeting and fragile, why do we exhaust ourselves with ambition?

Good point. I didn't thought about it.

If I succeed at things, I don't feel happiness. If I fail at things, I don't feel sadness. Because I know that there is no difference between them, just like life and death.

I feel satisfaction when I succeed at something.