RSSAmplifier

Blog

<web>EuAndreh</web>

EuAndreh’s blog

euandre.orgRSS feed ↗17 posts

Latest posts

A Relational Model of Data for Large Shared Data Banks - article-review

This is a review of the article “A Relational Model of Data for Large Shared Data Banks”, by E. F. Codd.

ANN: fallible - Fault injection library for stress-testing failure scenarios

Yesterday I pushed v0.1.0 of fallible, a miniscule library for fault-injection and stress-testing C programs.

ANN: remembering - Add memory to dmenu, fzf and similar tools

Today I pushed v0.1.0 of remembering, a tool to enhance the interactive usability of menu-like tools, such as dmenu and fzf.

Local-First Software: You Own Your Data, in spite of the Cloud - article review

This article is derived from a presentation given at a Papers We Love meetup on the same subject.

Durable persistent trees and parser combinators - building a database

I’ve received with certain frequency messages from people wanting to know if I’ve made any progress on the database project I’ve written about.

The Next Paradigm Shift in Programming - video review

This is a review with comments of “The Next Paradigm Shift in Programming”, by Richard Feldman.

DIY an offline bug tracker with text files, Git and email

When push comes to shove, the operational aspects of governance of a software project matter a lot. And everybody likes to chime in with their alternative of how to avoid single points of failure in project governance, just like I’m doing right now.

How not to interview engineers

This is a response to Slava’s “How to interview engineers” article. I initially thought it was a satire, as have others, but he has doubled down on it:

Feature flags: differences between backend, frontend and mobile

This article is derived from a presentation on the same subject.

cargo2nix: Dramatically simpler Rust in Nix

In the same vein of my earlier post on swift2nix, I was able to quickly prototype a Rust and Cargo variation of it: cargo2nix.

swift2nix: Run Swift inside Nix builds

While working on a Swift project, I didn’t find any tool that would allow Swift to run inside Nix builds. Even thought you can run Swift, the real problem arises when using the package manager. It has many of the same problems that other package managers have when trying to integrate with Nix, more on this below.

The database I wish I had

I watched the talk “Platform as a Reflection of Values: Joyent, Node.js and beyond” by Bryan Cantrill, and I think he was able to put into words something I already felt for some time: if there’s no piece of software out there that reflects your values, it’s time for you to build that software1. At the very end, at time 29:49. When talking about the draft of

Guix inside sourcehut builds.sr.ht CI

After the release of the NixOS images in builds.sr.ht and much usage of it, I also started looking at Guix and wondered if I could get it on the awesome builds.sr.ht service.

Using NixOS as an stateless workstation

Last week1 I changed back to an old2 Samsung laptop, and installed NixOS on it. “Last week” as of the start of this writing, so around the end of I was using a 32GB RAM, i7 and 250GB SSD Samsung laptop. The

Using “youtube-dl” to manage YouTube subscriptions

I’ve recently read the announcement of a very nice self-hosted YouTube subscription manager. I haven’t used YouTube’s built-in subscriptions for a while now, and haven’t missed it at all. When I saw the announcement, I considered writing about the solution I’ve built on top of youtube-dl.

Verifying “npm ci” reproducibility

When npm@5 came bringing package-locks with it, I was confused about the benefits it provided, since running npm install more than once could resolve all the dependencies again and yield yet another fresh package-lock.json file. The message saying “you should add this file to version control” left me hesitant on what to do1. The

Running Guix on NixOS

I wanted to run Guix on a NixOS machine. Even though the Guix manual explains how to do it step by step, I needed a few extra ones to make it work properly.