347 private links
A love letter to the personal website
A reflection of your personality in HTML and CSS (and a little bit of JS, as a treat). This could be a professional portfolio, listing your accomplishments. It might be a blog where you write about things that matter to you. It could even be something very weird and pointless (even better) – I love a good single-joke website. Ultimately, it's your space and you can do whatever you want with it. It can be a single-joke website.
On the other side, it is now intimidating to be a newcomer now with all these frameworks. They skip right over the basics.
The website we use today for fun are also businesses. They need an account to view the content. They have a barrier to entry.
Your website, your rules. There's no reply guys on your own website if you want to. it doesn't have the downsides of Twitter.
You can be a creator anywhere on the internet these days, but there's only a small handful of places where you actually own your own content. Your own website is one of them.
Now AI is generating slop. During the talk, Maggie asks: is there a future in which we need to have some kind of "reverse Turing test" to prove our humanity on the internet?
The whole point of WWW is to be decentralised and independent. It was released as an open standard so that access could be as democratic as possible.
To bring the WWW spirit back, we can carve out our own individual spaces on the web. HTML is accessible, and there are many web services to build websites nowadays. So why aren't we doing it? we don’t build websites for ourselves like we used to, we build them for the audiences we want.
Try something. For the nerds: try out. The site deploys in less than 30s. Try new CSS things as lomng as you rely on progressive enhancement.
The personal site isn't dead. It's just been forgotten in the commercialised, capitalist web of today. We owe it to ourselves to rediscover this lost art. [...] So, once again my digital call to arms: build your own website. Make it fun. Make it pointless. But most importantly: make it yours.
Greg Morris started Micro Social: https://gregmorris.co.uk/2025/02/12/micro-social-the-launch.html
As I wrote about right at the start, I wanted Micro Social to be very targeted in the way it worked. Providing something that I wanted from a micro.blog app, and not becoming all things to all people. It’s easy to get side tracked, though. The app is already a long way away from what I intended it to be, with features and abilities that I didn’t even dream of when I started.
Saying no to these users is hard, but it has to be because he can not do everything.
Les personnes qui insistent pour nous dégafamiser et nous linuxiser à l'os ONT RAISON.
Non elles ne sont pas "maladroites" ou "trop insistantes", ou "elles desservent leur cause" ou je ne sais quoi encore, on les déteste parce qu'elle nous mettent le nez dans notre propre caca. Et que changer implique de renoncer à notre petit confort.
Et c'est pareil pour les végans."Tu devrais installer Linux" est effectivement la meilleure réponse à "J'ai un problème avec mon Windows" même si ça ne nous fait pas plaisir et que ça ne va pas dépanner notre Windows.
Excellente utilisation de Mastodon : Ca se débat gentiment, ça se commente, ça se conseille, ça se fourgue des recettes, ça geeke dans tous les coins, l'ambiance est bonne, je suis extrêmement satisfaite.
First things first, you’ll need an account on crates.io to acquire an API token. To do so, visit the home page and log in via a GitHub account (required for now).
Free software is too dependent on MicrosoftHub but for Rust libraries, it is worse, a MicrosoftHub account is mandatory: "log in via a GitHub account (required for now)" I believe it is the only big programming language in that case?
(via https://mastodon.gougere.fr/@bortzmeyer/114008682103118141)
What cost AI per token in electricity and water?
TL;DR; concurrencer les GAFAM c'est
- Open source: Mistral, Mappy, Mastodon, ...
- relocaliser sans centralisation, sinon il y a bien le risque de recréer des GAFAMs
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
- open source is a community project
- compensation doesn't follow value
- 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