Regular Programming

It seems a mingle is a thing, and not just in Swedish! But what do we want to get out of them, how do we go into them, and how do we create good ones?

Do you want resonance or hole-poking when you tell people about your plan to arm toddlers with nuclear weapons? Do you want to successfully mingle nerds, or just hit the snacks hard?

The foood, the cake, the coffee, and the old classmates. Too hot, too loud, too crowded.

Links

• Mingle (noun)
• Ben Orenstein
• Tuple
• Thougtbot podcasts - The bike shed and Giant robots. Ben was on episode 183 of The bike shed and episode 136 of Giant robots.
• Øredev
• The art of gathering
• The Whova app

Quotes

• Interesting and fun
• Arm toddlers with nuclear weapons
• We don't trust solutions
• Excitement and resonance
• Intensively and excitedly and indefinitely
• The active rubberduck strategy
• Talking to fish in a barrell
• Successfully mingle nerds
• Hit the snacks pretty hard

Performance: we wish the incentives were there to focus on it more often.

Lars would like more opportunities and incentives to focus on making things fast, rather than just making them not slow. Unfortunately, things tend to line up so that fast enough and more features are in focus. Plus, performance and optimization can be very context sensitive and age out without anyone really noticing.

Also pondered: IRC, Gentoo, and the eldritch horrors buried within the x86 architecture.

Links

• Grep
• os.walk() in Python
• Why GNU grep is fast
• Ripgrep
• Ag - the silver searcher
• Travelling salesman problem
• Bin packing
• Mnesia
• ORM
• Project Euler
• Fibonacci numbers
• D. Richard Hipp - the guy behind SQLite
• Changelog episodes with Richard
• XKCD and IRC
• IRC
• IRCCloud
• Matrix and Element
• Elm
• SVG
• Canvas
• Neovim
• Lisp
• Arch
• Nix
• Gentoo
• Funtoo
• Dart
• Flutter
• Skia - the graphics library under Flutter
• Linked list
• Pointers
• CISC - Complex instruction set computer
• RISC - Reduced instruction set computer
• io_uring

Quotes

• Given up on old man Elixir
• Gotta go fast
• I never really needed it
• Grep, naively
• All the problems at the same time
• Travelling knapsack problem
• My ORM-infected brain
• Measuring things and muttering under my breath
• I have a hobby, I do job interviews
• Tools by toolmakers for toolmakers
• I'm the IRC guy
• Machine-whispering optimization

CTOs want the ability to get prototypes built and out into production fast. Others preach the gospel of building things properly. How fast can you be? How much can you perpare before you hit the ice? And one you built and shipped that prototype, how can you get any kind of speed trying to maintain and evolve something where many corners were cut for speed?

How do we want things to work then? Having an algebra for things might be nice. A sprinkling of interface, things that break noisily, and nice toolboxes to work with structs are all discussed.

Links

• The Scott - Amundsen race to the South pole
• Accelerate, by Nicole Forsgren
• Parse, don't validate
• Mnesia
• Deep modules
• Pure functions
• Plug
• Elm
• Bruce Tate
• CRC - Create reduce convert
• Ecto
• Roc
• Happy Path Programming. Episode 47 features Richard Feldman and Roc
• Richard Feldman, creator of Roc

Quotes

• The gospel of building things properly
• The key to speed on the ice
• Before you hit the ice
• Bare maps
• Every step made sense
• The original intent very easily gets lost
• The curse of all software
• Strive for maintainability
• It must not sprawl
• A little sprinkling of interface
• At dawn, we roadmap
• Things that break noisily
• A quantity unitless
• The simple case of HTTP

Did they do design, or did they just do a system?

Distributed systems are hard in many ways. Andreas describes a system communicating between backends and mobile phones in exciting ways with many exciting possibilities for errors. Like data format changes, loss of messages, having 1.5 source of truths, and of course ordering.

In certain cases, nobody likes an optimist.

The discussion then moves to discuss the working well-windows for various networking solutions, before diving into WebRTC and finishing up with the various dangers of auto.

Links

• Recursion
• Eventual consistency
• Pubsub
• RethinkDB
• Event sourcing
• React native
• Android studio
• Mnesia - a "distributed, soft real-time database management system" written in Erlang
• Dirty reads and writes
• Websockets
• QUIC
• UDP
• TCP
• WebRTC
• NAT
• HTTP live streaming
• Lars' ElixirConf talk
• Zoom H4
• Zoom H4n pro

Quotes

• Working with systems and feeling the pain 
• Coping with system design
• Eventually consistent, on a good day
• Eventually sourced
• A disappointment to work with
• Your internal representation of the user
• This is the shape of the data, deal with it
• 1.5 source of thruths
• Oh, it's an optimist
• I don't like optimists at all
• Optimist databases
• Within its working well-window
• Outside of the working well-window
• A crash of servers
• Bad connections over long distances
• I don't do math

Lars went to ElixirConf EU. Going to a conference can be a credibly incredible experience. Elixir has more clarity than Erlang.

Lars also gave a talk, a fact he was comfortably uncomfortable with. Giving a talk also comes with benefits such as being able to talk to fish in a barrel. But why did he choose to make the whole talk a demo? What is the goal of it all?

Gotta build things! Dive in, make stuff.

Links

• ElixirConf EU
• Lars' conference report blog post
• Code BEAM
• Sverok
• Pieter Hintjens about giving talks by talking to the audience
• Windows 98 (not 95) demo fail
• Lars' presentation code
• Voice Driven Development: Who needs a keyboard anyway? - presentation by Emily Shea
• Hugging Face

Quotes

• Born during ElixirConf
• Less clarity to it
• Genservers and stuff
• Mainstream Elixir
• Comfortable with that discomfort
• Talking to fish in a barrel
• A buddy from the internet
• The first one I bothered to count
• Your loose coupling to anything
• What do you hypothetically know?

Text editors - which ones do we enjoy, which ones have we used, and what do we actually want and need in them?

Andreas has read about vim, sed and awk. Lars is quite comfortable in vim, but finds Visual studio code more than acceptable enough. 

Andreas is excited to show Lars how to use Vim properly. Lars considers advanced setups something of a hellscape.

Lars has held a lecture about functional programming and wishes to provide a path for new .Net developers (dotnet dots?) to become free software zealots.

They both share their history of editors.

There are dreams of ergonomic editing - of code as well as text in general - on mobile devices.

Any other editors we should be trying? No, but you could hack together collaborative vim editing. 

Links

• Humble bundle
• Learning the Vi and Vim Editors - book
• Vim
• The Anarchist Cookbook
• Thunderdome
• Monad
• ex - line editor which inspired vi
• ed
• sed & awk - book
• AWK
• sed
• Sublime text
• Zed
• Neovim
• Tmux
• I3
• GNOME
• Pop!_OS
• KDE
• Treesitter
• ElixirLS
• FZF - fuzzy finder for the command line
• Ripgrep
• Functional programming
• Monads
• Fakeroot
• Notepad.exe
• Borland Delphi
• Notepad++
• Eclipse
• Intellij
• Android studio
• Xcode
• Write/Wordpad
• Nano
• Pico
• Gedit
• Kate
• Netbeans
• Atom
• Scratch
• GNU Screen
• Live Share for Visual Studio Code

Quotes

• Learning violent vim
• Like Thunderdome, but nobody leaves, ever
• I could do that with monads instead
• C's strange cousin
• There's a new sed on the block
• The power of just good enough
• Two terminals beside each other
• It's all a mess in here
• My sword and lots of configuration files
• The dotnet dots
• Quitters don't use Vim
• Real code is done on the server
• Notepad the way I want it to work
• A load-bearing note
• Exciting and fun, and incredibly unsafe

How do we feel about working remotely? Pretty good, on the whole.

Chairs and other basics are of course important, as is making your way of remote work a nice way of doing remote work for you. It is also nice to need to wear your work face less.

The challenges are more around the social sides - communicating differently, but generally replacing and rebuilding ways of being social with people both inside and outside of your work interests. That takes work.

Also, some talk about audio and video gear for remote meetings. It's nice to come off as full-fidelity people!

Links

• Conan the barbarian
• Eventual consistency
• Gamers Nexus on gamin chairs
• Ullman Nite-Flite
• RFC process
• Røde procaster
• XLR
• Ghost power (phantom power)
• Shotgun microphone
• The Kodsnack Slack

Quotes

• My real comfy legendary office chair
• My chair was kinda good
• Fluffy parts
• It's me and Conan
• I go for the floof
• Eventually ergonomic
• Eventually comfortable
• Whenever I don't have one, I create one
• Your spine has a very particular taste in chairs
• A prosumer phase of life
• Definitely dialled in
• Make sure you have a social life
• I fetch a lot fewer coffees than most people
• Ghost power!
• Full-fidelity people
• It's very much my office
• I don't have to wear my work face all day
• My work face

Lars is thinking about distributed systems, and Andreas kind of fears them. The best thing to do for most cases might be to avoid distributing things at all. But if you do end up needing to distribute, you may run into one of the places in the world where worse is better is not necessarily better? Adding distribution on top of something not really built for it is one of the hard problems.

There are deep dives into reconciliation, vector clocks, normalization, and places where fun goes to die. And there, still, are no magical solutions.

Links

• Phoenix pubsub
• Worse is better
• ElectricSQL
• CRDT:s - conflict-free replicated data type
• The CAP theorem
• Soft real time
• Highlander
• N-tier architecture
• Postgres replication
• Vector clock
• Elixir outlaws
• Phoenix presence
• Operational transformations
• Split-brain
• Riak
• CouchDB
• Raft
• Paxos
• Normal forms for databases
• Googles' Mapreduce
• Google Spanner
• CockroachDB
• Cassandra
• Contentful
• The Cambria paper - schema evolution in distributed systems with edit lenses

Quotes

• Distributed systems are interesting
• I'm doing an insert!
• A special little server
• The devil is always in the failure details
• The naive threshold
• The absolute wrong number of machines
• Where all the fun goes to die
• A good, sortable name
• They lie and they drift
• A simple incrementing number is incredibly useful
• Git merge for vector clocks
• Three is the best number

About Hackers Thinking about the term "hacker". Time to take it back to mean something rather down to earth, rather than a pedistal requiring years of C and a black hoodie?

What do airlines have against Erlang anyway?

There's also the mindset angle: the hacking mindset can be when exploring, versus when needing to solve a specific problem.

The discussion goes into labels one feels comfortable with, switching between different modes, and the ever present, ever hard to find dark matter developers.

Over time, labels can easily go bad in one way or another. But regardless of labels, we can all agree on duct tape and enthusiasm, right?

Links

• Let it crash
• Burning man
• Activitypub
• Static site generator
• CMS
• The Unix philosophy
• COM
• FFmpeg
• vi
• Perl
• Ecto
• Dark matter developers

Quotes

• So security, very programming
• Joy and playfulness
• My mind goes off
• Creative systems thinking
• Think through as many eyes as possible
• Many things are intended as complete packages
• Handing you the fun bits
• Things that provide you the entire world
• Not very together-bashable
• The media version of Vi
• Creating SQL that you didn't intend
• Mostly mindset
• What happens in the outliers
• Neutron programmers
• The unsung programmers
• Duct tape and enthusiasm

About Being Wrong

Wherein polite gentlemen at gaming conventions explain how people didn't have their variables separate enough with regard to the Dunning-Kruger effect. Lars thinks Andreas has drawn the wrong learnings from this.

It's a good idea to be humble … but strong opinions loosely held may not be the perfect thing, either?

Also discussed is the curse of the expert - teaching across a large gap in experience, and how to actually go about changing systems and having better discussions. Have you considered being god's advocate instead of the devil's when in a discussion?

Links

• Gothcon
• The Dunning-Kruger effect
• Autocorrelation
• The Dunning-Kruger effect is autocorrelation
• Golden ratio
• The curse of the expert
• The halting problem
• Linus Torvalds
• Strong opinions loosely held
• Steelmanning an argument
• Yes, and …
• Two's complement podcast

Quotes

• I attempted to make friends
• Hard to know what you don't know
• If you don't have your variables separate
• They fumbled on the input data
• I think you have the wrong takeaway
• The curse of the expert
• Have you looked at presidents recently?
• Exhaust the universe
• The halting problem of the universe
• Sons of pedagogy
• I feel comfortable, but I don't feel certain
• A really badass judo throw
• I can ignore many things
• A multitude of parts
• Bit by bit, you shift the system
• Taking small stands
• Very happy to be wrong
• God's advocate
• Random ideas, loosely shared
• A good crowd for this question

About Estimates

Estimates are a nasty subject, Andreas doesn't know how to handle it.

Fortunately, Lars has one weird trick, which doctors hate.

When you have plenty of control, estimates can be useful.

Not useful: unexplained deadlines.

Finally: when things get stuck. (Lars is usually available to blame.)

(In an alternate timeline, Andreas' tells us everything his relatives taught him about quark cake.)

Links

• Deadlines whooshing past
• The XKCD about determining if you're in a national park, and check if your photo is of a bird
• Basecamp
• Shape up
• Elm
• Zenos' paradoxes - you can't run past a tortoise
• The travelling salesman problem
• NP-complete problems
• CRUD
• Lean manufacturing

Quotes

• Their due dates, their deadlines
• I have this one weird trick, that doctors hate
• A constraint for the work
• The magnitude of the task
• Some real dumb things, and some very decent ideas
• Skate curve
• The smallest unit is always a day
• Not agile enough
• Slightly confused and maybe a little bit sad
• If you think that's a map (, I think you're using it wrong)
• Assorted concerns
• You can't run past a tortoise
• You can always split a cake in two
• Quark cake
• Accelerate a cake
• A fixed estimate on the travelling salesman problem
• Usually available to blame

Passing pandemics make it possible to meet developers in real life again. Elixir-Lars makes a splash, and tells about recent and coming real-life events he's enjoyed. Things learned from real-life events and the need - or not - of constant learning are mentioned.

(It's not bit rot, it's data composting!)

Finally, a deep dive into the art of arranging good events, including preparatory pre-event events.

Who wouldn't like a movie night with a bunch of developers and pizza?

Linkable matter

• Elixirconf EU 2023, in Lisbon
• Varberg
• Code BEAM - there are so many of them
• TDD - test-driven development
• Lettuce
• Cucumber
• NAND
• Nerves' Ramoopslogger
• Textalk
• Software craftsmanship Göteborg
• Event sourcing
• Redux
• Hackers
• Gleam
• Membrane
• Code BEAM Stockholm 2023
• Code BEAM Europe 2023 in Berlin

Title-like quotes

• Developers in my local area
• A splash as Elixir-Lars
• I guess I'm visible
• I met one developer
• I enjoy meeting developers
• Leads and future prosperity
• Composting becomes very natural
• Harness the entropy
• It's not bit rot, it's data composting
• The series of events that brought us here
• A speedrun of "Well, you have options"

The continued cratering of Twitter, and the joy of discovering open alternatives. Lars and many others find themselves on the open and federated Mastodon instead of Twitter, having a great time, and feeling more excited about open systems than in a long time.

On the level of individuals, owning and controlling your own data feels back in fashion, but there is even more to dig into on the level of large organizations.

Perhaps when GDPR says no and the good spirit of the internet is strong, there is a chance for municipalities and other public sector organizations to get and help build open alternatives to the closed, proprietary, and often hair-raisingly expensive and poorly received software they have today?

Lars sees exciting business opportunities, better software for all, as well as the interesting challenges of navigating tender processes and plain old corruption.

Links

• Mastodon
• genserver.social
• fosstodon.org
• Ruby on rails
• PostgreSQL
• Object storage
• Redis
• Pleroma
• Akkoma
• glitch-soc - "Mastodon Glitch Edition" - where Mastodon UI discovers new features
• Glesys' object storage
• PeerTube
• Pixelfed
• Activitypub
• SpaceX rockets exploding compilation video
• WebTorrent
• Element and Matrix
• eSam
• Mattermost
• SPF - Sender policy framework - email authentication method
• Skolplattformen
• Offentlighetsprincipen

Quotes

• Elon happened
• A very straight path to somewhere else
• As open as email
• Satiate my doomscrolling needs
• A Twitter on IRC
• I don't trust the ecosystem under my feet
• Lectured about a culture I'm not in
• Teams was dubbed illegal
• videos.varberg.se
• The good spirit of the internet
• GDPR says no!
• People software
• You have people living in you
• I want "Svenska IT-myndigheten"
• Pointless, annoying, and wasteful

How to teach functional programming? What are the proper steps, beyond the first ones? Especially when you can't or don't want to point to a framework and say "we do it this way!"

Lars outlines his ideas for teaching Elixir to someone without requiring any prior programming experience.

There is also discussion of mapping, reducing, and representing one in terms of the other. Also things which are better in Haskell than Elixir, perfectly named modules, and - inevitably - why you don't just use Rust instead.

Links

• Chalmers
• CakeML
• Elixir in action - Saša's Elixir book
• Monad
• Map
• Reduce
• Filter
• MapReduce
• Elixir's enum module
• Multiple function heads in an anonymous function
• Immutability
• Guards in Elixir and Haskell
• Witchcraft - the module
• Nerves
• Frank Hunleth
• REPL

Quotes

• It felt like I cheated, I don't know if I did
• In my bone marrow!
• Putting the module before the functions
• Try to explain a monad (there is no second step)
• Pretend that the rest of computing doesn't exist
• Ignore the rest of the world
• Save brain cycles
• Solid, sound, and true
• It's going to have to be a reduce
• I never really updated my map

Archives are cool. How do you keep your digital things in order and, hopefully, backed up?

We need more archivists.

Andreas has re-read Snowcrash, and while it isn't the manual for the world to adopt it doesn't seem to stop the megacorps from thinking it is and trying. Where did Google go wrong, and why? And why aren't we jealous of their recruiting?

Linkable matter

• The library of Alexandria - overrated?
• Backblaze B2
• Syncthing
• Tailscale
• Nextcloud
• Hetzner Storage Share (NextCloud)
• ZFS
• Borg - backup handling software
• Andreas' Instagram account
• Dragonbox algebra (5 yo / 12 yo)
• Snowcrash by Neal Stephenson
• Ender's game by Orson Scott Card
• Meta's new professional Quest headset
• The Corecursive podcast episode about Android
• Supabase
• Swedish archive paper

Better titles

• Overrated library though
• Perfectly gitted and dotfiled
• Way too pragmatic
• A virtual private server and magic
• Nested backups
• Suddenly: math
• More stacks of logos; less clarity
• Preparing for the metaverse
• 1984 isn't the manual
• Snowcrash isn't the manual
• Designing dystopia
• The opportunity for amazing glitches
• Need to try harder at working less
• A strong ack

There are good things in programming, many of which are enumerated in this episode.

Among other nice things: the best features in Elixir. Lars won open source? Bots and realtime-y stuff. Not to mention a type system that screams at you.

Also: Lists in lists, in lists (in lists).

Code made by other people is not one of the things, however. Code made by other people is always upsetting. CSS does not make the list either, but Tailwind does, prompting a discussion of fractally difficult things, leaky abstractions, and progressive enhancement.

Linkable matter

• IO-lists - lists in lists in lists with eventually some binary data in them
• Id3vx - The now published ID3 library
• LiveView
• Phoenix
• Either in Haskell
• Clowns to the Left of me, Jokers to the Right (the paper)
• Stealers Wheel - Stuck in The Middle With You
• Functors
• Elm
• Fmap and bind in Haskell
• Lars' Telegram bots
• Genserver
• Moment.js
• Autobots and Decepticons
• Snow Crash by Neal Stephenson
• Tailwind CSS
• Graceful degradation
• Progressive enhancement

Better titles

• Keeps giving nil
• Carefully optimistically happy
• A JSON-thingy
• You won open source
• I have written the code, and it's not my problem
• Murdering your garbage collector
• A type system that screams at me
• The maybes I got over pretty quickly
• They never stopped being results
• An inherited Erlang footgun
• The speaker that was in the monkey
• It's not only that I'm a backend developer

The hardware woes episode. But first: the joy and wonder of ID3v2.3.

Implementing the specification of a binary format as a library.

Lars' next laptop. Then Lars' gear situation. Power bricks and cable capabilities are … a labyrinth.

The trials and tribulations of getting and setting up a Steam deck.

Linkable matter

* The ID3v2.3 spec
* EXIF
* Fold left and fold right
* Lars' blog post about working with ID3
* CRDT
* Apple's WWDC keynote
* The M2 Macbook air
* The Framework laptop
* Linux on M*-chip computers
* Dell's XPS laptops
* RJ45
* Steam deck
* Slackware
* PopOS
* Regolith
* Frank Hunleth (of Nerves fame)
* Sony A7C

If we had titles

* Trying to be clever, and doing it poorly
* It still reverses the whole thing
* Arbitrary comments
* The future of mp3:s
* The world is less and less file-centric
* A USB-C-shape cable

Elon Musk wanting to buy Twitter leads naturally into the topic of cyberdecks and jacking in, which in turn naturally leads one to talk about audio on Linux.

But what is a cyberdeck? How do you build one? And when would you use it?

The sad state of video calls compared to Star Trek - why don't they have to install Teams to hail the Microsoft ship?

Lamenting the sad state of the current crop of dystopic overlords. Who runs Google, really? Amazon might be the most attractive target, just don't take down all our clouds by accident, okay?

Cyberpunk wasn't prepared for crypto, but when other things get bad enough that ceases to be a problem. Let's not papercut ourselves all the way to dystopia.

Linkable material

* Elon Musk has or has not yet bought Twitter
* Cyberdecks
* Jack - the sound library
* Shadowrun
* Keytar
* Pi 400
* Pi TFT
* Touchbar Lemmings
* The Framework laptop
* Google glass still exists
* FPGA
* Obsbot PTZ Camera
* Cory Doctorow on the Corecursive podcast
* Lightning - the on-top-of-Bitcoin payment system
* Podcast index
* Mer - the Swedish cordial-type drink

Alternate titles

* Jack in
* Something vulgar about it
* As far as cyberdecks go
* The keytar of keyboards
* Just hack the Gibson
* Rearview mirrors, but cameras
* Out cyberdecking
* The current crop of dystopic overlords
* Web-scale capitalism
* Our current psychopaths
* Papercut our way to dystopia

Notes will improve when beatings continue.

Hopefully some day :)

TBD

TBD

TBD

:)

TBD

Show notes may show up again some day. But right now we wouldn't be on it :)

Thanks to the listener who chimed in and wanted our thoughts on microservices. That wasn't what put it on the topic list but I think we still get credit for responding to input right?

We apologize for any discomfort in the audio. We lost the original Ekeroot recording and had to use the backup cloud recording. The people responsible have been sacked.

This episode was a bit delayed, sorry about that. Poor planning on our part :)

Show notes, hopefully some day :)

Show notes TBD, maybe :)

Running with show notes?

Some show notes might show up later if you are lucky :)

More notes TBD

We're talking gear and trying to answer the always relevant question of what is needed to program.

• C++
• CSS
• HTML
• Javascript
• Gymnasium
• IBM's briefcase-shaped PC
• Monochrome monitor
• Glitch.app or maybe Glitch.io
• Raspberry pi, all versions
• Microsoft ergonomic keyboard
• Trackball
• GHC
• Swift
• Rust
• LLVM
• Property based testing explained by Jessitron
• Elixir
• Erlang
• BEAM
• Dialyzer
• Docker
• Vagrant
• VirtualBox
• Moore's law
• Let's encrypt
• Bayesian inference
• ASIC
• Balrog
• Laggard
• Filco majestouch with Cherry MX blue switches
• Filco majestouch tenkeyless with Cherry MX brown switches
• KVM switch
• i3
• Moonlander
• Logitech TrackMan Marble FX Trackball
• Counter-Strike
• Kerp used a trackball when playing League of Legends
• Sony zv1
• Elgato keylight
• Blue yeti
• Audio Technica atr2100x usb
• Focusrite Scarlett
• ThinkPad T400
• ThinkPad T440s
• NFS
• Tmpfs

Painstakingly putting together a framework on frameworks. Also name dropping as if there was no tomorrow.

• Ariane 5 rocket launch explosion
• TDD
• Haskell
• Python
• Mocking or mock objects
• Quickcheck
• Hypothesis
• Pytest
• Elixir
• Phoenix Framework
• Domain-driven design
• Telegram
• Elixir Outlaws: Episode 97: Successfully Vamped
• Chaos monkey
• Prince of persia
• Testing telecoms software with quviq QuickCheck
• Blue green deployment
• Django
• The About ORMs episode
• New Relic
• Datadog
• Prometheus
• Grafana
• PromEx
• Livestream with Alex Koutmos
• Antiloop's Purpose in life
• Purescript
• PHP
• ripgrep
• Protocol buffers
• The Bike Shed
• factory_boy
• Golden tests
• Python difflib
• PostgreSQL
• nginx
• Elm
• Nixos
• Arch linux

• Jonathan Stark speaks about value based pricing, his podcast Ditching Hourly is highly recommended.
• Fight Club

Show notes are on vacation time. Hopefully we'll have them expanded eventually :)

Notes will arrive if vacation allows.

All about that base, data base no, trouble.

• ORM
• Python
• PHP
• SQLAlchemy
• Django ORM
• Drupal
• Wordpress
• Elasticsearch
• C# dapper
• Ecto
• Elixir
• The pattern book
• Laravel
• Ruby
• Java
• Diesel
• Selda
• Haskell
• SQL
• SQLite
• PostgreSQL
• MySQL
• MS SQL
• N+1 queries
• select_related
• prefetch_related aka The other one
• REST
• Modelforms
• Ecto schemas
• Ecto changesets
• Http forms
• Repo insert
• Repo update
• Data mapper
• Structs in Elixir
• Record types
• DSL
• Post-mortem: 10 years in the vertical - Part 3
• Episode 4
• Cartesian product
• SQLAlchemy core and the other one
• Module
• Erlang
• Reducer, map, filter, etc.
• foldr, foldl
• Bruce Tate
• Construct, reduce, convert
• Elixir pipes
• Plug webserver
• Higher order function
• XKCD standards

Painstakingly putting together a framework on frameworks. Also name dropping frameworks and everything under the sun as if there was no tomorrow.

• Phoenix Framework
• tailwindcss
• alpinejs
• Django
• jQuery
• Wordpress
• Laravel
• Symphony
• Drupal
• Django admin
• Django modelforms
• Ecto schemas in Phoenix
• Ecto changesets in Phoenix
• Ruby on Rails
• Django formsets
• Flask
• FastApi
• HTTP basic auth
• Django REST framework
• Plug
• Cowboy
• Liveview
• Erlang
• Celery
• Sidekiq
• Cron
• Redis
• Oban
• Beam
• PostgreSQL
• Postgrest
• Views
• Schema
• Lemmingpants
• GraphQL
• Haskell
• Yesod Web Framework
• Scotty
• Sqlite-simple
• Lucid: templating DSL for HTML
• EDSL@HaskellWiki
• EDSL@Ward wiki
• Surface ui
• php
• Cycle.js
• Functional reactive programming
• Virtual DOM
• Elm architecture
• Javascript
• PureScript
• PureScript Halogen
• Mithril
• React
• Vue.js
• Vuex
• Redux
• React router
• Angular
• Typescript
• Ionic 1
• Cordova
• Phone gap
• Xamarin
• PETAL
• Livewire
• Hotwire
• Django hotwire
• Vim
• Refactoring UI
• Styled components
• Sass
• Less
• Bootstrap
• Purecss
• Ecto
• Telegram
• DOM API
• om virtual dom
• Clojurescript

On the benefits and woes of written communication. Code reviews are usually written, so we revisit them again.

• rfc2119 Key words for use in RFCs to Indicate Requirement Levels
• Dunning–Kruger effect

On the benefits and woes of code reviews.

• Accelerate by Nicole Forsgren, Jez Humlbe and Gene Kim
• Marie Kondo
• Flying workstation
• CI/CD
• Kubernetes
• "Nobody expects the spanish inquisition!"
• hlint
• Credo
• clippy
• rustfmt
• dialyzer
• The do-not-eat-all-the-resources-ticket
• partial in Python

Sometimes you end up talking about Javascript. 

• Unpoly
• Mithril.js
• Lodash
• Webpack
• Parcel.js
• Elixir
• Phoenix
• Alpine.js
• Stimulus
• Turbolinks
• Cordova
• React native
• npx
• Marie Kondo
• Elevator saga
• Lars mentorship
• Fancy forms without Javascript
• Mozilla Developer Network
• MJPEG
• HTTP Live Streaming
• Membrane framework
• FFMPEG
• WebRTC
• WebUSB
• Web Bluetooth
• Remote Code Execution in Slack desktop apps
• Stagefright, Android MMS remote code execution
• Pine phone
• Arch Linux
• Shark phone
• CAT phones
• KaiOS
• React
• React Router
• Bonus: Opinionated react
• AngularJS
• ISO8601
• flatpickr
• Moment.js
• Vue.js
• React Portals
• Vuex
• Stripe
• cassie.codes
• Factorio
• Slay the spire
• Beam Bloggers Webring