About Long-Lived Code

03/04/24 • 42 min

Fredrik wants to think about long-lived code. Lars is offended, Andreas only a little bit so.

Are there other good software development practices out there? Other than the ones focusing on building something quickly? Practices for building software which lives on and is maintained for much longer than we seem to care to admit? Should we remove dependencies over time? The swamp of dependency management and vendoring is probed, gradually shifting into firmware, the horrors of floating point (proper excuses are made), small language models.

Finally, of course, indecent cups of tea.

Links

Fredrik wants to think about long-lived code. Lars is offended, Andreas only a little bit so.

Finally, of course, indecent cups of tea.

Links

Previous Episode

About Fat Tuesday Buns

The Saint Valentine's peak passed without issue. Andreas had time for semlor.

Lars has opinions on semlor, and can imagine many possible improvements. Like having an apple. Or a pizza.

Lars has had a nice influx of work, including hardware work using Nerves. Testing and very hackish hot code reloading are both included.

Finally, some thoughts on Linux audio, and musings about the possibility of creating really nice audio tools for the platform.

Links

Saint Valentine
The strangler fig pattern
The strangler pattern
Phoenix
Cowboy
Semla
Mudcake
The Swedish chef making chocolate moose
Finnish fastlagsbulle with jam
One of Lars' blog posts about Nerves
Frank Hunleth - also hot code reloads the way Lars has done
Lars' Stream deck library for Elixir
Stream deck
Elgato key light
PulseAudio
PipeWire
Rogue amoeba's audio tools for Mac
JACK
Custom APT repository

Quotes

The Nordics go all awkward and weird
In my heart, it was a catastrophy
Had time for semlor
An unimpressive pastry
It's less messy to have an apple
Professional nerves
Building with nerves
A reasonable enough abstraction
The Rogue Amoeba for Linux

Next Episode

About Ranting at Ecto

Stories about Ecto quickly redeeming itself, and of what it takes to introduce foreign keys.

Some of us are super comfortable referencing the ID. Lars dislikes that Ecto needs to be more complicated because of SQL, but the abstractions do hold.

Also: the biggest reason to ever use a ORM! It can be reallynice to come back to one after a tour of plain SQL-land.

Some people have just been bitten so hard by cowboys.

Links