Blockchain, Heavy Metal and Testcontainers

An airhacks.fm conversation with Kevin Wittek (@kiview) about:
typing with 3 on a terminal, 486 for playing DOS games, radio
controlled cars for fathers, RC car races with transponders,
worldcup in beijing, hawaii, las vegas, tamiya, kyosho,
professional competition RC cars by Mugen Seiki, playing
civilization-like game, switching from PCs to console gaming,
starting with Quick Basic programming at highschool, writing text
adventures with Quick Basic and huge if-else blocks, advent
calendar with Quick Basic, switching from Quick Basic to Java 1.4,
a coffee lover without aeropress, aeropress and aerospace
technology, aerobie frizbies, teaching polymorphic dispatches at
highschool, who cares about object orientation, bluej programming
learning environment, the great scratch IDE, manipulating the ASCII
characters might not be the future, sometimes it is better to
manipulate the Abstract Syntax Tree (AST) directly, writing a
ZIP-compressor in Java, studying in Gelsenkirchen-the Java-focussed
university, writing Android software for Museums, Museums don't
have money, writing fraud detection services for GData, banking
trojan detection was really successful, leading the blockchain
research group, having a dream job, lazy loading the PhD topic,
assessing the non-functional aspects of a blockchain system, why
Groovy is a pragmatic language, Groovy started as an ergonomic
version of Java, playing e-guitar at a heavy metal band "Iron
Kobra", Rush, Deep Purple, Led Zeppelin, and a bit Metallica, one
of the best guitar players is Uli Jon Roth from the German
Scorpions band, starting to play guitar with 16, starting with TNT
from AC/DC, software engineering is like playing blues, the
SoCraTes Conference, the JUnit 5 extension for Docker, the
beginnings as TestContainers committer, Richard North was the
initiator of the TestContainers project, TestContainers started in
a blockchain-related project, TestContainers project was written in
Java from the beginning, TestContainers started with JUnit 4
integration, the TestContainers project has actually nothing todo
with testing, ephemeral container concept is built-in into the
testcontainers, the docker container is going to be removed after
the JVM exits, ryuk is a side container which watches the actual
container, when the JVM stops sending the heartbeat - ryuk will
remove the container, GraalVM might replace Go in the
sidecontainer, testcontainers gives strong guarantees about
readiness, testcontainer ships with multiple probes / wait
strategies: log-based wait strategy, port-based wait strategy,
docker health-check strategy, testcontainers ships with container
communication API, in the case of a database testcontainer will
provide a JDBC-URL, testcontainer can is able to start DB on demand
by using the JDBC driver, testcontainer also works with remote
Docker daemons, testcontainer is using the REST interface to
communicate with Docker, the switch from Netty to OkHTTP,
testcontainers relies on Docker Java, hardcoding functionality in a
project is the right choice at the beginning, testcontainers has to
be refactored into two parts, testcontainer's 2.0 goal are distinct
APIs for testing and container orchestration, windows support was a
challenge, testcontainers supports windows, linux and MacOS, the
testcontainers team is using Macs for local development, azure
pipelines is used to test windows,

Kevin Wittek on twitter: @kiview, on github
https://github.com/kiview and Kevin's blog.