I recently watched this talk on generative art by [**@wblut**](https://www.instagram.com/wblut/)**,** a fellow Belgian _generative artist_ whose work I really appreciate and enjoy. A very interesting and inspiring talk on generative art in general with some insights and examples of how he approaches his work. A talk I can definitely recommend, so here it is:

\<iframe width="560" height="315" src="https://www.youtube.com/embed/L-k9NneqsHQ?si=UXKmftc3ZHvreGEI" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen>\</iframe>

The one thing that strongly resonated with me was how in generative art you don't exactly start with an idea of what the final piece is going to look like. In stead it start with a curiosity about a certain topic and then exploring the concepts or systems that its made up of. Or to summarize, I guess you could say **generative art is a curious exploration**. A way of thinking about generative art as a medium that I hadn't really before, but I definitely felt like there was something there.

So then, a few days later, I'm scouring OpenProcessing to find some interesting sketches that I could use for a live A/V performance I'm working on (soon more about that! [drop your email](https://forms.d17e.dev/subscribe) if you want to stay posted ;). I soon came across this sketch mimicking the ripples on a water surface (click & drag the screen to see the ripples):

\<iframe src="https://openprocessing.org/sketch/1678058/embed/?plusEmbedHash=0b26191d&userID=362930&plusEmbedTitle=true&show=sketch">\</iframe>

A very simple algorithm that beautifully mimics ripples on a water surface. Basically in every step, every pixel that is white will propagate to the pixels around it. In the original code this looks like:

```js
for (int i = 1; i < cols-1; i++) {
    for (int j = 1; j < rows-1; j++) {
      current[i][j] = (
        previous[i-1][j] + 
        previous[i+1][j] +
        previous[i][j-1] + 
        previous[i][j+1]) / 2 -
        current[i][j];
      current[i][j] = current[i][j] * dampening;
      int index = i + j * cols;
      pixels[index] = color(current[i][j]);
    }
  }
```

I quickly got interested to find out what would happen if, instead of _activating_ just one pixel at the time, I could _light up_ a whole range of pixels. Or a specific shape. And what better shape than a circle? Click/tap a few times on my forked version here and see what happens:

\<iframe src="https://openprocessing.org/sketch/2229886/embed/?plusEmbedHash=8c78297c&userID=362930&plusEmbedTitle=true&show=sketch">\</iframe>

Isn't that amazing? Out of nothing these crazy patterns emerge. I had never planned this. But yet here I find myself. Staring at funky patterns and wondering what else I can make this algorithm do... That exploration is still ongoing, but for now I'll leave you with one last still from the version of this sketch in my [creative coding playground](https://github.com/dxviie/creative-coding-playground):

![](https://strapi.d17e.dev/uploads/frame_998_3592e17490.png)

Until next time! x

gen_exploration_ripples.png

I heard somebody say that generative art is exploration. I kind of agreed. Next thing I knew, I was knee-deep in a soup of pixels I'd never intended to see. Now I deeply understood and agreed.

Generative art is exploration

Sometime during late 2023 it came to my attention that [Piter Pasma](https://twitter.com/piterpasma) had been organizing a month of collective generative art explorations on the internet ever since 2021, and was doing so again for 2024. This seemed like the perfect opportunity to take on the challenge and motivate me to try and make cool stuff and share it with the world.

If you're interested to see what came out of my effort, you can find my entries on [the little website](https://genuary.d17e.dev/) I set up for this. Or you can read on and find out about a few of the things I learned along the way.

### 1\. The new CSS color spaces LCH & OKLCH are amazing.

For the second day, the Genuary prompt was "no palettes". As in, no color palettes. The sketch for the day was supposed to focus on generating colors. As I'd been actively avoiding the use of color in order to focus on lines and shapes, this seemed like a great time to check out some of the CSS Level 4 color spaces that were added to a browser near you during 2023.

One of those color spaces is [LCH](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value/lch), where the L stands lightness, C for chroma or color intensity and H for hue or color rotation. If you want to learn more about the story behind this space, there's a [great article by Eric Portis](https://ericportis.com/posts/2024/okay-color-spaces/) that I can recommend. In short, the reason this new color space was invented was to have a space that has a predictable outcome when changing one of it's values (l, c or h).

This makes this color space (as well as OKLCH) quite straightforward to start generating palettes. Which is what I did. And to my pleasant surprise I was quite pleased with [the outcome](https://genuary.d17e.dev/?prompt=2). From that day on, using color in my sketches has felt a lot less daunting.

### 2\. PaperJS is great. Until it's not.

One of the constraints I had decided for myself doing Genuary was that I wanted to us the [PaperJS](http://paperjs.org/) library. The reason for this being that I have a plotter sitting on my desk that I'm still getting to know. Now, this plotter takes svg's as input, which is not necessarily a problem. With a bit of tinkering I was able to get one of my processing sketches to output svg instead of an image. However, the svg output was messy and also made it necessary to do some _post-processing_ before I could send it to the plotter.

This made me think that there had to be better ways of generating my svg's. Which lead me to PaperJS as they call themselves the '_The Swiss Army Knife of Vector Graphics Scripting_'. Great. Just what I needed. When I browsed to the API I could tell that the abstractions closely followed the concepts and structure of an actual svg, so I was sold. I just need to find some time to play around with it. And then Genuary rolled around. Perfect.

What I've learned is that PaperJS is really great as long as you're not generating a bunch of new shapes every frame. You really want to do as much of the object creations at the start and then animate those objects over time in the onFrame method. Another thing it doens't like so much is rendering a bunch of transparent layers on top of each other. Which is kind of to be expected, but I still had to find out the hard way. An example of this is my [ASCII sketch](https://genuary.d17e.dev/?prompt=9). In general I mainly ran into performance issues that I tried to dance around.

Which doesn't mean I'm writing off this library. On the contrary. I'm keeping two use cases in the back of my head where PaperJS might be the perfect fit. 1) When you want to generate static svg's. This is a great option in my opinion since you're working really close to the actual svg model. 2) Interactive canvas based apps. One of the cool things of PaperJS is that every object you create, be it a rectangle or a weirdly shaped path, comes readily packed with event-handling wired up. E.g. setting up the user interaction for the [chaotic system sketch](https://genuary.d17e.dev/?prompt=8) was super straightforward to do.

### 3\. There's only 24 hours in a day. And that's okay.

When I decided to join in with Genuary I thought about what my approach was going to be. As the official website already mentions to _not get burned out doing all the dailies_ I came with plan that I'd spend all the time I could during the month of January. Once January was over, I'd move on to other things. As I did.

So you can probably tell by the prompts that I actually made that I can be quite unrealistically optimistic about things I can do in a certain time. It took 3/4 of the month January for me to surrender to the fact that I wasn't going to be able to do all the prompts within the time window I had given myself. Which is of course okay. But going through this surrendering in a positive way gave me some more practice in being ok with what we get done in the time we have. Something that [I've since learned](https://www.richroll.com/podcast/cal-newport-817/) is an actual thing that's being called _slow productivity_. So I guess this is my way of saying, take your time and be kind to yourself. Just keep showing up and put in the work.

I didn't do all of the prompts. And that's ok. I did some and learned a bunch. But most of all, I had a lot of fun. Next year, I'm doing them all though!!

### 4\. I :heart: Svelte.

Another thing I decided on for doing Genuary, was that I was going to build a [mini website](https://genuary.d17e.dev/) for it too. And I was going to do this using [Svelte](https://svelte.dev/). I'd been intrigued by Svelte and its creator [Rich Harris](https://twitter.com/Rich_Harris) ever since I saw his talk on reactivity, dissing react while the core team was in the front row. His talk was funny and engaging and the man was making immense sense on top of that. I'm not sure how long ago that exactly was, but since that day I've been following the Svelte story with increasing eagerness to get my hands dirty.

So, on the 1st of January I typed into my terminal `npm create svelte@latest genuary-2024` and well... my findings? In short, I wish I had tried it earlier. I haven't come across anything that's been bothering me and everything I try to do just seems to work, so yeah. I'd start listing all the things it does well, but instead I'll just recommend you to take it for a spin. You won't regret it.

### 5\. Hello JS, my old friend.

I've been writing code for a living for almost two decades now. Throughout my career I've been spending a lot of time with C++ and Java mainly. Given that background it may not be surprising that for around the first 10 years I wasn't thinking all too fondly of JavaScript. And that's putting it very lightly.

It was only when I dipped into the world of functional programming through an online Haskell course that I started to see and hear about all the good things about JavaScript. So around that time (2015), I started dabbling around with JavaScript a bit in my free time. With varying degrees of activity.

As much understanding I built up during that time, it was always somewhere on the background. My day to day job was still filled with other languages and responsibilities. So doing these sketches in JavaScript, I realized I had lost some of the feeling I had with the language. Probably a good idea to brush up on those skills I thought. And then Marijn Haverbeke goes and publishes the [4th edition of Eloquent JavaScript](https://eloquentjavascript.net/). Perfect.

### 6\. Wait, what? I thought you said 5.

I did say 5 indeed, but the thing is I learned so many little things along the way. Like how I learned about the pixel layouts on old CRT and modern LED displays or how I found [somebody's math homework](https://github.com/mws262/MAE5730_examples/tree/master/3BodySolutions) in MatLab and figured out how to give me solutions to the 3 body problem. All great learning adventures.

But maybe another big one is that I also learned that it's actually not that scary to make stuff and put it out there. So I think that's just what I'll do.

Show up. Do the work. Have fun.

genuary_2024.png

Since 2021, the month of January is transformed into Genuary, an artificially generated month of time where generative art community builds code that makes beautiful things. And this year I decided to join in. Here's a couple of things I learned...

5 things I learned doing Genuary 2024

**"Comprendre c'est transformer"** is the name of the [exhibition](https://www.oniris.art/exhibitions/51-vera-molnar-comprendre-c-est-transformer/) where Vera Molnar's work that I [re-coded](https://openprocessing.org/sketch/1857733) was featured. You can read all about that in a [previous article](blog/what-generative-art-means-to-me), but for now I want to linger on the exhibition's title for a bit. In case French isn't your strong point, it means "Understanding is transforming". Next to the work I selected itself, I was quite intrigued by this title as well. Just like her work, it is simple yet powerful. Food for thought... 

Thinking about how an understanding of something can indeed be transforming in many ways. New understandings about the world around us, give us new ways of moving through it. The way it's written up in French  also mildly implies causality. Understanding is needed in order to transform. But is that so? Maybe you can transform or change your world in such a way that you set yourself up for understanding it better later on? Or maybe they're two ends of the same stick and will inevitably create each other? What did it all really mean?

I had thought enough and had an idea. For a title, at least. **"Tranformer c'est comprendre"**. _"Brilliant"_, I said to myself, _"Now just the art and we're done"_. Great progress.

Jokes aside, naming the thing also gave me inspiration of what I wanted it to look like. To say a bit more about that, let me first pull up a screenshot of my re-coded version of the original real quick:

![comprendre c'est transformer re-coded](https://strapi.d17e.dev/uploads/2023_11_15_09_27_52_Comprendre_Cest_Transformer_0849_7b999c4039.png)

As you can see, there's three layers to the work. From let's say _busy_ at the bottom to _less busy_, almost serene at the top. Next to that, I also found the _grid_ like structure an important feature that I wanted to preserve somehow.

With those elements and a title turned up its head, I envisioned a set of lines neatly next to each other as if on a grid. Each of these lines would grow from the bottom to the top, transforming from _chaos_ into _harmony_. I tinkered around for a while and can here present you a still frame of the first iteration that gets us close to what I had in mind:

![2023-11-17_17-57-06_TransformerCestComprendre_0497.png](https://strapi.d17e.dev/uploads/2023_11_17_17_57_06_Transformer_Cest_Comprendre_0497_27c1cd7fd4.png)

For the code and the _wiggly_ version you can [visit the sketch on OpenProcessing](https://openprocessing.org/sketch/1986467). I also added some stills of this sketch to the [posts](/posts) section in case you don't want to stray too far.

As much as it comes close to what I envision, it's not exactly there. I feel the chaotic part at the bottom is not quite chaotic enough. I also think that the middle section could have more of its own character, now it's just there in between the two elements without much of its own story. Plenty of room for improvements I'd say. But for that I realized that I'll probably need a different approach of implementing this. But that's for another time.

If you want to find out what that will look like as soon as possible, then you should definitely pop your email in the little box below, and you'll be one of the first to find out. I promise! Until then, I thank you and wish you a wonderful day.

vera_molnar_answer_sideways.png

Re-coding Vera Molnar's work, together with the title of the exhibition where it was featured inspired me to re-think the work. This is the story of where that led me thus far.

A playful answer to Vera Molnar.

These days, when you hear 'generative art', it's easy to confuse the term with 'generative AI'. Especially as the latter seems to be all over the internet these days. Even though I find the applications being built on top of [generative AI](https://en.wikipedia.org/wiki/Generative_artificial_intelligence), like [ChatGPT](https://chat.openai.com/) and [StableDiffusion](https://stability.ai/stable-diffusion/) quite impressive at the very least, that's not what I'm on about. A very interesting topic, but one for another time.

So then, what am I talking about? Well the _definition_ for generative art that I have in mind is a bit older and can be found on the [generative art wiki](https://en.wikipedia.org/wiki/Generative_art):

> _Generative art refers to art that in whole or in part has been created with the use of an autonomous system._

A rather broad definition still, I agree. In fact, by this definition anything that comes out of [Dall-E](https://openai.com/dall-e-3) or [MidJourney](https://www.midjourney.com/) could also be considered generative art. Well, let's refine that definition a bit. See, for me the autonomous systems I'm interested in are rather specific. Not specific in what they could be or do, but specific in how they're built. I want to build automated systems that make art using code. And [robots](https://www.axidraw.com/), too.

Ever since I started my career as a developer, I've had my eye on that corner of the art world that was feeling the same excitement about technology as I did. Projects like [processing](https://processing.org/) made me giddy and people like [Casey Reas](https://reas.com/) or [John Maeda](https://maedastudio.com/) were my idols. Fast forward two decades and the world around _creative coding_ has only grown stronger. What better time than now to get off my cozy sideline bench and out there, I thought. So here I am. And thank you for being here with me.

So where does one start? As a writer's block translates very easily to a blank screen, for a while the answer was "you don't". Until I stumbled onto [OpenProcessing](https://openprocessing.org/). A community website built around [the web version of processing](https://p5js.org/), that allows you to save and display your sketches on their website and interact with other members. I got especially inspired when I discovered the [Recode/Rethink curation](https://openprocessing.org/curation/72108/). The concept behind that curation is that you recode another already existing work and maybe reinterpret it. I had my mission.

It didn't take long before I decide to re-code a work by [Vera Molnar](https://en.wikipedia.org/wiki/Vera_Moln%C3%A1r). She was one of the pioneers in the field so it seemed fitting that I'd also start there. One thing I also love about her work is the simplicity of a lot of the pieces. Simple yet powerful. The piece I ended up selecting was exhibited at the solo exhibition ["Comprendre c'est transformer](https://www.oniris.art/en/exhibitions/51-vera-molnar-comprendre-c-est-transformer/)". The specific work can be viewed on the right of [this picture](https://www.oniris.art/exhibitions/51/installation_shots/image1028/).

Another thing I like is the fact that the only colors are black and white. I feel like adding color to a work is a huge step and I don't feel confident in going there yet. There's still so much to explore yet before we start playing with that, I think. But we'll see. Never say never.

Anyways, without further ado, here's a still frame of the recoded version:

![2023-11-15_09-27-49_ComprendreCestTransformer_0771.png](https://strapi.d17e.dev/uploads/2023_11_15_09_27_49_Comprendre_Cest_Transformer_0771_dd232addd0.png)

As I mentioned earlier. Simple yet powerful. Not that complicated to implement but very interesting and teaching to do so. And a great way to meet my old friend [Perlin noise](https://en.wikipedia.org/wiki/Perlin_noise) again. That's a kind of _random number generator_ that generates _natural_ patterns and is the algorithm that provided the angles at which each set of lines is angled. If you want you can view [this and the source code](https://openprocessing.org/sketch/1857733) on OpenProcessing. Of course, here I'm not working on paper so... I had to make it wiggle, didn't I. That was the logical next step. And also something that perlin noise lends itself to beautifully.

Below is the embedded version of the sketch, but in case you can't see it here you can follow [this link](https://openprocessing.org/sketch/1857733).

\<iframe src="https://openprocessing.org/sketch/1857733/embed/?plusEmbedHash=074c1d27&userID=362930#sketch">\</iframe>

If you see the sketch above here, you can click/tap it to reseed the noise field.

vera_molnar_sideways.png

What is this generative art thing I'm talking about? In this article I try to describe what the term means to me and bring you along on how I re-coded a work from Vera Molnar's exhibition "Comprendre, c’est transformer".

What generative art means to me.

Just as for the title of the previous article, I again let myself be inspired by something I'd seen before. Only this time, I didn't really remember the title of the movie. So I did what anyone would these days. I went on the internet and searched. To my ignorant surprise I came to realize that "What is this place?" is quite a common phrase in movies. So if you thought of a movie reading the title, you are correct! That's exactly the reference I was trying to make. And maybe it's even featured in the little cut-up of people saying "What is this place?" in movies that I added here for your leisure. Just in case.

\<iframe height="360" src="https://www.youtube.com/embed/vd48RvDBiP4?si=_CnidhU9mYiqlFuI" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen>\</iframe>

And that brings us to the question. What actually is this place? First of all, I think it's better if we rephrase that question. It's served its purpose after all. The actual question I can say something about is "Why did I build this place?"

Well, there's actually several reasons. So, instead of trying to list them up let me take you through my thought process of how this place came to be.

Not so long ago I started freelancing. Or, as one could also say, I started a business. This business needed a name and I decided to go with '**d17e.dev**'. Where the _d17e_ part comes from you can read about [in another article I wrote](/blog/d17e-what-s-in-a-name), but for those who haven't, it's basically a short representation of my full name. I had owned the .com domain for a while already, so when I started this new venture there were all these new [funky top level domains](https://en.wikipedia.org/wiki/List_of_Internet_top-level_domains#ICANN-era_generic_top-level_domains), among which the '.dev' and that just seemed perfect. I wasn't sure if the local bureaucracy would accept a name with the dot in it, but they did. And so, d17e.dev was born.

These days, a business needs some kind of online presence, maybe one or more social accounts, or maybe even an own site. But if you choose the company name to be something that looks like a web [URL](https://ittavern.com/url-explained-the-fundamentals/), or something that looks like something you'd type in a browser address bar, people are going to type that in a browser address bar. I mean, I would. So long story short, **I needed a website**. 

Luckily I'm in the software business. This 'software business' is pretty broad though and building websites like these hasn't exactly been a real part of my day to day job description. As in ever. However, I like what I do and 'web development' is one of the areas I've been keeping an eye on over the last decade or so. I had also already built a small portfolio site when I was changing jobs last, so I was confident enough that I'd pull it off. In fact, this was and is the perfect opportunity to **expand and explore** my skills.

Which brings us nicely to one of the big reasons I built this. To **learn hands-on** how it is to run an actual website. I approached this whole endeavor as if I was my own client. That really just means I wasn't allowing myself to cut corners. Aside from ending up with a website, I also saw this as an opportunity to explore infrastructure, hosting, CMS,... options that are out there today and at the end of the road having something set up in a way that I could easily reproduce this and possibly offer it as a service. And I wasn't the easiest client one could get, believe me. But I've learned a ton. And at that, it was even fun too.

Fun. That's a big driver for the choices I've been making in my life. I believe one should strive to have as much fun as possible, as long as that's not at someone else's expense of course. But I digress. I built this website, because it **was fun**. In fact, it still **is fun**. In the future you can expect this place to keep changing now and then. If you want to stay in the loop when I do, make sure to [leave your email](https://forms.d17e.dev/subscribe)! 

One of the elements that make this fun is the fact that I'm the only one working on this, so I've pretty much got **free reign**. I choose what technologies I use or features I implement. In a real-life work situation, this is generally not the case. In fact many times there's things you'd rather be working on. Just as with this project, there were things that weren't exactly fun. But that's part of the gig. The difference this time though, was that I was doing the less fun stuff because I chose to do it. And if I wanted to change my mind on something, I could do so. 

A bit earlier in this write-up I mentioned socials. With this new adventure I'm on, I feel like I can't escape the social platforms. Not that I'd try to escape them, I just want to be mindful of the time I spend across them. And I also wouldn't want any of those platforms be the _root_ of my _online identity_. Instead, this place now also plays the role of this root. Its **home base**. I can manage and organize my content here, on my own server and have [little robots](https://n8n.io/) do my social media bidding.

Lastly I want to point out that even though I'm talking about 'building my own website', I didn't exactly build all of this from scratch. I don't think there's a lot of software that's really written from scratch these days. We are all **standing on the shoulders of giants**. Some of the giants that are the core of this place are projects like [ChakraUI](https://github.com/chakra-ui/chakra-ui) and [NextJS](https://github.com/vercel/next.js/), which both actually build on top of ©Meta's [React](https://react.dev/). It's been an incredible time to see the development world evolve over my career that now almost spans two decades. Open source software was only an obscure idea that floated somewhere between academia and ideologists back when I started out. These days, if you don't share your code on [GitHub](https://github.com/), you're not cool. Kind of. I may have taken some liberties with that statement, but my point is that a lot has changed. And right now, it's a pretty amazing time to be in the 'software business'.

Of course, I _want_ to be cool. So you can find the [source code for this website](https://github.com/dxviie/d17e.dev) on GitHub. Not because I think this how I think each website should be built, no. Not at all. Just because **sharing is caring**. And maybe someday it will be useful to somebody. For example, when a large language model reproduces the obscure hack I implemented for the [blurhash](https://blurha.sh/) algorithm. Or not. Which is also ok. I did my best.

d17edev_site_screen_l.png

Find out why I decided to build this little corner on the internet and what you can expect to find here in the future.

What is this place?

_If you're running short on time, you can_ [_skip straight to the answer_](#tldr)_._

What's in a name? Or to lend the words that Shakespeare had Juliet utter quite eloquently: 

> What’s in a name? That which we call a rose  
> By any other name would smell as sweet;

For me, my name is David. Full out that's David Vandenbogaerde. A birthday gift from my parents. Ever since I've dragged that long ass name around with me. 7 syllables all together, quite a mouth full if you ask me. 

Over the years I have seen many non-Dutch native speakers in a struggle trying to pronounce it. Sometimes people would really struggle so I'd say "David's just fine" and see the relief settle back onto their faces. Never before they struggled at least a bit though. For my enjoyment, but also out of respect. Cause God loves a trier.

When the time came for me to choose an email address I naturally went for my full first **and** last name, without giving it much thought. It seemed like the right thing to do. Fast forward to phone calls to customer service departments where I'd have to spell out my email address... Great practice in patience, but that's about it. It still took me at least half a decade before I would get a shorter alias for my email. An idea that stared me right in the face when my younger brother gave me his email address. It didn't even have his full first name. And the last name he'd reduced to 3 letters. Something had to be done. And I did. That day my main email address got shorter by over 60%, or 12 letters to be precise. Thank you, brother!

Then, it must have been somewhere during the second half of the second decade of the 21st century that I was tasked in work to setup the [**internationalization**](https://en.wikipedia.org/wiki/Internationalization_and_localization) for a software project we were building. For those unfamiliar with the term, internationalization in short means that you offer your website or app in different languages. Internationalization, quite the word huh? 8 syllables even! Well, during my research I found out that this term or idea also gets shortened, because in IT we like to be _efficient_... Shortened how, you ask? Well, to **i18n**. Or, an 'i', then 18 letters and then an 'n' to complete the word. Hmm... I think we're on to something. When I also learned that [**accessibility**](https://en.wikipedia.org/wiki/Accessibility) was getting shortened to **a11y**, I was convinced. If they can do that for 11 letters, I can sure do it for 17.

And that's how my name David Vandenbogaerde got smushed together to d17e. The ~laziest~ most efficient way to write my name. To date.

With regards to [**Kubernetes**](https://en.wikipedia.org/wiki/Kubernetes), also known as **k8s**, it makes me wonder. What's the minimum number of letters needed to justify the use of this lossy compression algorithm?

\<p id="tldr">TL;DR\</p>

_My name is David Vandenbogaerde. It starts with a **d**, ends with an **e** and has **17** letters in between, so d17e for short. Similar to how internationalization, accessibility and kubernetes get shortened to i18n, a11y and k8s, respectively._

logo_header_palettized_artifacts.png

If you're wondering where 'd17e' comes from, you might want to read this. You will also find out what this has in common with internationalization, accessibility and kubernetes,

d17e. What's in a name?

Here you can find my thoughts on anything that makes me **think**, **wonder** or **laugh**... Or all of those, all at once.