well, shit happened. let me tell you about something that occurred recently that made me realize we might have a problem with this whole vibe coding trend.
let me tell you a story about infrastructure. no, wait. don’t leave. i promise this won’t be boring.
ah, so here we are. the long-awaited part three of my testcontainers saga. the finale? definitely. but not for the reasons you might think. spoiler alert: i’ve been wasting my time. and maybe you have too.
alright. so the last post was a simple introduction to testcontainers: what are they, how to set it up, how to run a couple integration tests against a database… it was quite good for an introduction, but there were of course things missing.
well, it was about time to start writing some code in this - supposedly - blog. time to get our hands dirty.
this is probably the post that makes the least sense of all but i still need to get some practice before i get into business and dive deep into the technicalities so here it is
physicist → chemist → dev
some (hopefully) interesting stuff