Daft

Kékecé le Cloud ?

Unknown — Wed, 23 Feb 2022 00:00:00 +0000

Ci-suit un petit texte d'introduction rédigé pour apporter le sujet du cloud à une amie qui ne travaille pas (encore) dans le domaine de la tech.

Une histoire de serveurs et de clients

Lucas est content, il est l'heureux propriétaire d'un bar : « Little Big Binouze ».

Le bar fonctionne bien, trop bien d'ailleurs. Lucas a du mal à recruter assez de serveurs pour répondre à une affluence variable de clients. Impossible de prédire quand les clients vont débarquer en masse. Lucas à pourtant recruté 10 serveurs en CDI, qui travaillent non stop pour répondre aux demandes des clients. Mais à 18h, quand les matchs de pétanques commencent, ce n'est plus suffisant. Il faudrait 20 serveurs pour pouvoir servir tous les clients.

Le matin, c'est l'inverse, il n'y a pas un chat et les serveurs se roulent les pouces, et coûtent de l'argent à Lucas ! Si seulement, Lucas pouvait faire appel à une société tierce qui lui "louerait" les services des serveurs seulement quand il en a besoin. Le coût des serveurs s'équilibrerait alors, avec l'affluence proportionnelle des clients. Et pourquoi ne pas étendre cela aux inventaires de tables, chaises, verre, Moscow Mule, voir les cuisiniers… Que d'économie en perspective…

Les services de l'oncle Sam

Miracle ! Une telle société tierce existe, il y en a plusieurs même:

Amazing Waiter Service: AWS
Garçon Coutellerie and Plates: GCP

Ils proposent tous deux une multitude de services, Lucas ne paye seulement ce qu'il utilise. Il y a certes un travail d'orchestration pour bien définir ses besoins, mais une fois que c'est en place, quel changement !

6h30, début du service, Lucas fait appel à 3 personnels pour préparer les tables, seulement 8 pour ce début de matinée.

7h30, le personnel responsable de la disposition des tables, n'est plus nécessaire, ils peuvent rentrer chez eux. Ils sont remplacés par les 7 serveurs et 4 cuisiniers qui seront en poste durant la matinée.

11h15, le déjeuner approche et avec lui l'arrivée des clients. Mais Lucas a prévu le coup, les cuisiniers et serveurs sont doublés. Et en cas d'affluence extra-normal, d'autres pourront venir leur prêter main forte en quelques instants.

Il y a un soucis, cependant.

Tous ces services sont des services Américains. Et la Commission Nationale de la Restauration et des Plongeurs n'est pas très contente qu'une société Américaine est la main mise sur le commerce Français. Surtout que les dîtes entreprises Américaines requièrent que leurs clients partagent leurs recettes avec les cuisiniers Américains. C'est un sujet de sécurité culturelle ! Sans compter que ces entreprises Américaines refusent de verser des pourboires à l'Union Européenne.

Est-ce la fin du rêve de Lucas ? Non, une entreprise peuplée d'irréductibles Garçons résiste encore et toujours à l'envahisseur…

bot-a-nique

Unknown — Sun, 19 Sep 2021 00:00:00 +0000

🏗 We be Wipping 🏗

Random Ramble · TDDE Test Driven Development, Eventually

Unknown — Sat, 18 Sep 2021 00:00:00 +0000

Testing, is doubting.

-- Me, ~~an intellectual~~ a smart-ass

How systemd saved me from tendinitis or how to use systemd timer in Nix (also Rust)

Unknown — Fri, 10 Sep 2021 00:00:00 +0000

🏗 We be Wipping 🏗

« Sir, you have tendinitis, also CTS. »

-- Your Doc

« But Doc, I don't understand, I am an healthy 24 years old. I only work 18h a day! Then I relax, playing video games for the rest of the evening. »

-- Benjamin Franklin

While this might not have been an accurate quote, this illustrate a problem that is quite known in my "keyboard wielder" world of tech. This is not to say other fields are exempt from this, though. Case in point, one of my friend who doesn't work in the tech industry suffered wrist pain, "tendinitis" was the diagnosis the doctor presented.

Since this is somewhat of a common sight in my domain, I went over the things I did to spare my wrists.

⚠ Hold it right there! ⚠

This post is just a pretext to ramble about tech stuff. I can maybe name, like five muscles and three bones.

also, I'm very dumb, don't take my word for it.

Don't tempt me Mouse! I dare not take it. 🏗

« Simple, learn not to use the mouse »

-- Gandalf the Grey

My first reaction was, well use your keyboard, silly. Reaching for your mouse every six seconds ain't good, trust me¹.

Do what I did, learn Vim bindings, integrate those bindings wherever you can (Firefox + tridactyl) then ditch Vim and replace it with Emacs + Evil.

Why tho?

Cowboy Bépop 🏗

« Simple, change your keyboard layout »

-- Alexandre Astier

I won't go into details about why the "original" QWERTY / AZERTY (and other variants) aren't really suitable in a modern world, with modern keyboards. It's more a thing of the past that stick. It's a:

~~« if it ain't broken, don't fix it »~~ «If I don't care that it's broken, don't try to fix it for me.»

kinda situation.

What are the alternatives?

A bunch of alternatives, actually. There are lots of keyboard layouts that try to facilitate the typing experience. Usually by "clustering" the most used key together.

You want ERgOnOMiCS 🏗

Simple, just buy a 300$+ split / ergonomic keyboard

-- r/ErgoMechKeyboards

Holup Nerdy McGuy, speak human, please 🏗

But maybe, there's a first step somewhere, everything I talk about up to this point would represent a massive change in one's life. How about just taking it easy?

Don't just stay here! Move arround!

First attempt · A systemd Timer baked solution 🏗

TODO: whatsup with systemd, why not CRON

  systemd.user = {
    timers.get-off-computer = {
      enable = true;
      wantedBy = [ "timers.target" ];
      partOf = [ "get-off-computer.service" ];
      timerConfig = {
        OnBootSec = "30m";
        OnUnitActiveSec = "20m";
      };
    };
    services.get-off-computer = {
      description = "Don't stare at displays too much, take some pause. Get up, do some stretchs… Let me remind you of it gently.";
      serviceConfig.Type = "oneshot";
      path = [ pkgs.bash pkgs.libnotify ];
      script = ''
        notify-send -a "get up, nerd!" -t 20000 "$(echo -e "Stop right there criminal scum!\nYour time is up, hands up, get up, stop looking at screens!")" \
        && sleep 20 \
        && notify-send -a "Time to work!" "$(echo -e "Alright, back to work, slacker!!")"
      '';
      environment = {
        "DISPLAY" = ":0";
        "XAUTHORITY" = "/home/daf/.Xauthority";
      };
    };

Second attempt · Why make it simple, when you can rewrite in Rust? 🏗

The code 🏗

use random_ramble::refactor::RandomRamble;

use notify_rust::Notification;

static SOUND: &str = "message-new-instant";

fn main() {
    let timeout = 20;

    let summary = RandomRamble::new()
        .with_template("{{ intro | rr }}\n{{ desc | rr }}")
        .with_others(
            "intro",
            vec!["Stop right there, criminal scum!", "<snarky remark here>"],
        )
        .with_adjs(vec!["Lazy", "Sad"])
        .with_others(
            "desc",
            vec![
                "Get up! Lazy <noun>",
                "You'll die if you don't move!",
                "You've been pretending to work for like 20 minutes! Take it easy.",
                "Hands off the keyboard.",
                "Hands up!! Now, wave them around, like you just don't care",
                "Something method Pomodoro, something…",
                "You remind me of the humans in Wall-E… GET UP!"
            ],
        )
        .to_string();

    let btn_txt = RandomRamble::new()
        .with_template("{{ btn | rr }}")
        .with_others(
            "btn",
            vec!["Feck off", "Leave me alone!", "Honey, I'm not in the mood.", "SNOOZE", "OMG, I don't care"],
        )
        .to_string();

    #[cfg(all(unix, not(target_os = "macos")))]
    Notification::new()
        .icon("chronometer")
        .sound_name(SOUND)
        .summary(&summary)
        .appname("Get up, NERD!")
        .action("snooze", &btn_txt)
        .timeout(timeout * 1000)
        .show()
        .unwrap()
        .wait_for_action(|action| match action {
            "default" => println!("default"),
            "snooze" => println!("clicked a"),
            // FIXME: here "__closed" is a hardcoded keyword, it will be deprecated!!
            "__closed" => println!("the notification was closed"),
            _ => {
                println!("hello?")
            }
        });

    Notification::new()
        .appname("Back to work, NERD!")
        .icon("display-symbolic")
        .summary("Alright, back to work.")
        .timeout(3 * 1000)
        .show()
        .unwrap();
}

Nix 🏗

What's next? 🏗

Would you like to know more?

No, really, you gotta trust me. I invested too much in my ways to be wrong. Also I cannot be bothered to do some research.

Random Ramble

Unknown — Mon, 30 Aug 2021 00:00:00 +0000

🏗 We be Wipping 🏗

In the life of an agile project, the most exiting aspect of it, by far, is naming the sprint… Well, no, ending the sprint is better, because there's the celebration at the pub afterward.

Still, naming the sprint is important. So much so that my coworkers often find themselves frozen by the responsibility of finding a good, meaningful name. Or maybe it is total disinterest and boredom.

Anyway, I came up with a solution to these problems: introducing RandomRamble.

*Cough*

In reality, I just wanted a pretext to play around with Rust.