Surma did Nix

YouTube

Nix explained from the ground up

What is Nix? And how does it build software in a completely deterministic way? Chapters: 0:00 - Intro 0:45 - How Nix came to be 3:37 - Install Nix 4:13 - Nix Language speedrun 7:23 - builtins 8:09 - Paths and the Nix store 9:52 - Derivations 17:25 - Nixpkgs…

My two modes of existence.

I was gonna send this message yesterday but decided not to.

```
It has been 4 days
Trying to get NixOS to work on our server VM
This world is made for the normies
Stick to Ubuntu

?
```

After i finally solved the issues, I wanted to send this

```
After 5 days of battling with the monsters of GRUB configurations and their weapons of BIOS partitioning sharpened by the deception of static IP configuration.

I have finally slayed the beast Ubuntu and it imperative folies.

I have officially conducted a kexec take over of our Ubuntu server and switched it NixOS.
```

Is it a good idea to setup a homepage for a server, do people do this?

I have only seen home lab-ers do this.

Interesting article but it's too short. I wish they explored they idea more.

[state and time]
[hacker news page]

gets hired for a rust job
convinces company to use nixos
spends all day writing nix

RFDs

YouTube

Oxide and Friends 8/24/2024 -- RFDs: The Backbone of Oxide

RFDs--Requests for Discussion--are how we at Oxide discuss... just about everything! Technical design, hardware component selection, changes in process, culture, interview systems, (even) chat--we have RFDs for all of these, over 500 in a bit under 5 years.…

SSDs want to be fast, as fast as RAMs.
RAMs want to be big, as big as SSDs.

So what I gather is that microservices are a way of combating against technical debt.

Any system of sufficient size and sufficient age will inevitably accumulate technical debt, this makes it harder to change that system to add new functionality or modify existing behavior. Technical debt is like a cancer, an un-escapeable by product of age and growth.

Microservices embrace this problem and try to limit these technical debts into their own corner of complexity. So it doesn’t matter that any single microservice is full of technical debt, because when you want to add new functionality or modify existing behavior you will always be adding new microservices to accomplish that goal.

This property allows you to build complex systems without falling down the well of refactors. The only requirement for the existing microservices is that they are functional.

The author of this book calls this idea additivity, but it's just the functional programming idea of composition applied at the service level.