Sometimes the small things in life can make the biggest difference. This time it is a small adventure in Python.

What a weird tech stack I made recently. I already wrote on this a bit. Now I come back for some more.

I was working on getting some work ported over to Strawberry from Graphene-Django, and I suddenly hit a snag. Once I found out what happened to the Strawberry Fields, I was just glad I could solve it at that point.

I saw this thing being advertised on HackerNews or some such similar thing. After checking it out, it was just a blatant lie and more than that, it is just trying to sell JavaScript and HTML as they are intended on being used as if they thought of this.

So these days it seems there are too many choices, and the wrong simplification is being applied. Since everything in the frontend and backend is being consolidated to a singular language/framework to solve the entire issue.

So this has been the case for many a year now, that everything in JavaScript land or in this day and age, TypeScript land, is targeting the fact that the developer can use one codebase for everything frontend and backend.

You would think this takes place in the early days of computing, but no this takes place in 2023. I needed to share some files to help my brother to launch a new website.

I quite like keeping old things alive, longer than they were meant for maybe, but also repairing things that got broken. For example toys my children play with.

I just wanted to find out if a directory was writable for the user, and it turns out it is quite difficult to get that information in Golang. How difficult could it be?

Sometimes you need to run Docker containers in different circumstances, like on Raspberry Pi's or you have systems that are just wired differently (Alpine) and sometimes even a combination of those (Alpine on a BananaPi) and you do not always have everything laying around to reproduce it. So what do you do?