I can’t stress enough how even a modest amount of pre-thinking, sketching or even just making a checklist beats jumping into a code editor or design tool, regardless of whether you’re doing a small ticket at work, building a personal site or even starting a whole client project. Sitting down and thinking away from the tools really helps you to consider what is actually important, what is a nice to have, how you measure improvement and importantly, what the process of iterations/cycles look like.

following

Le web étaient constitués d'humains créant du contenu pour des humains. Maintenant, l'IA crée du contenu (en publiant sur le web) que d'autres AI (en piochant sur le web) vont résumer pour les humains.

Le web est donc invisibilisé, et la qualité du contenu médian ou moyen décroît.

L'accès aux pipelines n'est plus ouvert sur le web, mais requiert maintenant une authentification.

Retour d'expérience d'un développeur

The website of the project is made with it https://aitorllamas.com/astro-loader-obsidian/

The reset:

legend {
  padding: 0;
  display: table;
}
fieldset {
  border: 0;
  padding: 0.01em 0 0 0;
  margin: 0;
  min-width: 0;
}
body:not(:-moz-handler-blocked) fieldset {
  display: table-cell;
}

Another ode to the web

The Web of homemade websites. It’s not the Web of perfect websites. But it's — the Beautiful Web.

If one employee is using AI

your employer captures 100% of the value from you adopting AI. You get nothing, or at any rate, it ain’t gonna be 9x your salary. And everyone hates you now.

And you’re exhausted. You’re tired, Boss. You got nothing for it.

Compared to the 80', time moved slowly in the sense that news and events were spaced way out and society had time to reflect on them. Now it changes so fast we can’t even keep up, let alone reflect.

Crazy addicted early adopters like me are controlling the narrative and make it unrealistic
You can’t stop reading about it in the news; there’s nowhere to hide from it.
Panicking CEOs are leaning in hard to AI, often whiplashing it into their orgs.
Companies are capitalistic extraction machines and literally don’t know how to ease up.

and we’re all setting unrealistic standards for everyone else.

$/hour. "I told the grumbler group, you can’t control the numerator of this ratio. But you have significant control over the denominator. I pointed at the /hr for dramatic effect."

A local-first alternative to Notion

The map uses webrings as subway line and each station is a website. Some websites cross many subway lines.

A review of multiple fonts

The AI is a capable to build product from scratch, up to a limit.

Now with Firefox support

Great utils

Dem Bundesamt für Verfassungsschutz (BfV) und dem Bundesamt für Sicherheit in der Informationstechnik (BSI) liegen aktuelle Erkenntnisse vor, denen zufolge ein wahrscheinlich staatlich gesteuerter Cyberakteur Phishing-Angriffe über Messengerdienste wie „Signal“ durchführt.

1. A simple queue.json
2. Batching with group commit
3. Use a brokered group commit to eliminate contention over the queue object
4. HA brokered group commit to handle unfinished job or broker machine die

Similarly to the job system we built at work, it guarantees at-least-once delivery.

I don't know if the pattern becomes too complex to be viable.

The ambiguity level and the number of unknowns are definitely a crucial factor when it comes defining our modules, and especially when it comes to the implementation strategy choice

The more ambiguity we have, the more fluid and dynamic our domain is and the less certainty about its final shape we have, the more we should focus on adopting a strategy where it is the least costly to completely redesign and rearrange our modules.

Simple modular monolith: folders. Microservices needs one application per module. That's a high cost.

requirements, and some of them might have needs somewhere in between. Thanks to the fact that every module is now basically a separate application, we can assign different resources to each module and have it in a different, often dynamic, number of replicas, based on its own unique needs.

We can eliminate many problems of microservices by adhering to one, simple rule:

When serving any external network request, synchronous or asynchronous, a service can not make any network calls to other services, synchronous or asynchronous.

About SPAs: avoid global things that apply everyhwere

As the last resort, we can have a separate SPA per a few selected routes, having as many html pages as we have SPAs (multiple SPAs approach), or use the Micro Frontends

To reiterate, we went through the following strategies, ordered from simplest to the most complex one:

• Simple Modular Monolith
• Modular Monolith with Isolated and Independently Deployable Modules
• Modular Monolith with Helper Services
• Constrained Microservices - Microliths
• Microservices

I would say things are always easy when the modules are clear, defined and documented :)