How inappropriate data access patterns massively slow down programs and how the same problems arise with RESTful APIs.

Retrieving whole rows is hugely wasteful when only part of the row is required to resolve a user request. The issue becomes pronounced when: retrieving sub-parts of the data (projection), consulting multiple tables (joins) or digesting the dataset (aggregation).

RESTful API design consequently suffers the same problems as Active Record ORMs. [...] The largest class of API clients is separated from the server by high latency network links: mobile phones. [...] This means that accessing multiple API endpoints to resolve a single user request can take seconds - an appreciable annoyance to any user.

From ORMs: demand first class queries and transactions. Avoid Active Record style access patterns whether in ORMs or elsewhere.

Bank Python implementations are effectively proprietary forks of the entire Python ecosystem which are in use at many (but not all) of the biggest investment banks. Bank Python differs considerably from the common, or garden-variety Python that most people know and love (or hate).

I've said so far that a lot of data is stored in Barbara. Time to drop a bit of a bombshell: the source code is in Barbara too, not on disk. Remain composed. It's kept in a special Barbara ring called sourcecode.

it's possible to sit down, write a script and get it running in prod within the hour, which is a big deal.

Using simple Python functions, in a source controlled system, is a better middle ground than the modern-day equivalent of J2EE.

One thing I regret about software as a field is how little time is spent learning from existing systems and judging what they did well, or badly. There are only a small number of books discussing, in detail, real systems that exist.

The idea for SQLite actually came out of his frustrations with an existing database called Informix that was installed on a literal battleship

they said, “Well, do you have any pricing information?” “Well, look, I tell you what, let’s have a call tomorrow and I’ll get back to you on that.”
Of course, inside, I was like, “What? You can make money with open source software? How does this work? How do I price this? I have no idea how to do this.”

Somehow or another, and I don’t know how this happened, Mitchell Baker, she’s the woman who runs the Mozilla Foundation, she got wind of this and called me up, says, “Richard, you’re doing this all wrong. Let me tell you how to set up a consortium.” She laid down the law, says, “Look, the developers have to be in control. Their decision is final. No voting rights on what gets to go into it. The companies that are using, they get the honor of contributing money, but you make all the decisions.” She was very adamant about this and she laid out everything. She’s a lawyer.

I actually started following some of their processes, and one of the key things that they push is, they want 100% MCDC test coverage.
That’s modified condition decision coverage of the code. Your tests have to cause each branch operation in the resulting binary code to be taken and to fall through at least once.

I looked at Git, I looked at Mercurial, and I looked at my requirements and I thought, “You know what? I’m just going to write my own,” so I wrote my own version control system (fossil), which is now a project unto itself, and that worked out very, very well

Source : https://sebsauvage.net/links/

Le Bottin des Jeux Linux est votre base de données libre en français et en anglais dans laquelle vous trouverez 3835 jeux Linux et 847 outils (moteurs, émulateurs, …), avec des liens utiles, de l’aide (pour installer certains jeux & outils), des tests et des vidéos.
Deux versions sont disponibles (1 en ligne + 1 hors ligne). Cette base de données est la vôtre, elle est libre et open source (licence CC-BY).

The database of old games (abandonware). Tribute to the best underrated PC games of all time.