228 private links
This article set the priority on humans, which is also a point of the agile manifesto
Le NoSQL est également plus adaptée pour le développement agile car les données ne sont pas structurées pendant les itérations.
Le SQL a réussi à traverser les âges car: il est simple, il est rapide et il est stable.
Les avantages de SQLite:
- facilité d'administration: tout le contenu peut être visualisé par lecture d'un fichier.
- facilité de déploiement: il est possible de pousser les BDD en production et de les migrer
- simplicité: sqlite est intégré avec tous les langages de programmation
- capacité: une BDD peut contenir plus d'un million de TB
Ses désavantages:
- requêtes concurrentes:
- les types de données limitées: NULL, INTEGER, REA L, TEXT, BLOB. Il n'y a pas de BOOL ni de dates.
- les données sont faiblement validées: "abcd" dans INTEGER o 20 charactères dans VARCHAR(5) passent.
- la sauvegarde des données est à faire soit même
- l'hébergement n'est pas possible avec tous les hébergeurs
As author Sam Harris said, “In a world of true abundance, you shouldn’t have to work to justify your life.”
UBI stands for Universal Basic Income.
Proponents of UBI — and I count myself among them — argue that it offers a safety net that enables individuals to pursue education, start businesses, or engage in creative endeavours without the fear of financial ruin, creating a more innovative, entrepreneurial, and dynamic society.
UBI is grounded in the principle of shared prosperity and the intrinsic value of each individual, irrespective of their economic contribution.
Experiments in Finland and Canada have shown that providing a basic income does not significantly diminish people’s desire to work. Instead, it affords them the flexibility to pursue work that is meaningful and suited to their skills rather than being trapped in the cycle of low-paying or unsatisfying jobs.
With a correct basic income, you can safely strive for the progress of humanity.
Make it visible :) It can be in the UI for human and the <head> for tools
It’s a reminder that reliability, consistency, and user satisfaction can coexist in the realm of software development.
- Automating stuff gives you superhero strengths
- Coding is fun (and we can forget the rest)
- Sharing is fun too
- Elegant, creative solutions
- Talk to a machine
- Standing on the shoulders of giants
We take all of this for granted because the devices rarely fail, but it's really amazing when you think about it. It's only been a few decades since much of this was tedious, time-consuming, manual labor.
About automation:
That means we have more time to focus on the fun stuff, like playing with the cat.
The dedication, the urgency to reach your aims must come from within you.
The author shares its point of view on Shuttle that needs little to nearly 0 configuration to get started.
Zerocal was the first project I deployed on Shuttle. The principle was very simple yet innovative: encode calendar data directly into a URL. [https://endler.dev/2022/zerocal/]
#project #idea improve the UI or make a custom one that calls the API
#project #idea use such API to generate other files. Contacts?
Both Figma and Photoshop are for people who believe the web looks like an image.
Semantic HTML is a must. Because there is UX with HTML :D
Another thing our design tools really don’t give a shit about is accessibility. And to be honest, I think most of our industry doesn’t really care about accessibility as well.
Looks also valid to me.
The specialists who helped the architect in making sure it was certified did nothing else than ticking boxes. And this is exactly what most of us do when we think we make our sites accessible. We tick the WCAG boxes.
Those two nonfree programs have something else in common: they are both malware. That is, both have functionalities designed to mistreat the user.
If you use a program to carry out activities in your life, your freedom depends on your having control over the program.
Nonfree software was the first way for companies to take control of people's computing. Nowadays, there is another way, called Service as a Software Substitute, or SaaSS. That means letting someone else's server do your own computing tasks.
In some cases, nonfree software causes indirect harm (secondary injustice): it puts pressure directly on others to use this software (Teams, Skype, Zoom, ...), it encourages to develop the non-free software further. All the forms of indirect harm are magnified when the user is a public entity or a school.
Public agencies exist for the people, not for themselves. When they do computing, they do it for the people. They have a duty to maintain full control over that computing so that they can assure it is done properly for the people.
Will it be worth it for you? If you need to iterate rapidly, probably not. If you have a known scope, or can absorb more upfront cost? Definitely consider it. You’ll end up with bulletproof software. With the WebAssembly angle becoming stronger every month, the prospect of writing perfect software once and reusing it everywhere is becoming a reality sooner rather than later.
About job announces
Le jour où je n’aurai plus aucun incident ni anomalie, je considérerai qu’on a mal fait notre travail en surinvestissant dans la qualité par rapport à nos besoins réels.
Et si j’assume d’avoir un risque casser des choses, ce n’est pas déconnant de choisir quand je veux gérer ce risque. La règle de la mise en production du vendredi, pour les équipes qui en ont une, n’est parfois que cela.