Skip to main content

Practicing zone of proximal development

I was at a LIVE tech conference last week! The keynote was about learning through tinkering. The talk had a chapter that resonated with me quite profoundly: the zone of proximal development. Essentially, it means a student can only learn something "around" a given subject if the topic is familiar to them.

As I've written here a few times, one of the pieces of technology close to my heart is Postgres (and RDMSs in general). I know the basics + some more and can tune some common knobs. Having said that, database internals present a fascinating mystery. I don't understand how they work under the hood - not even close. 

I believe that delving into the details and getting hands-on experience can take my understanding to a whole new level. This is the essence of the zone of proximal development - learning by doing and pushing the boundaries of what we already know.

I stumbled upon the Carnegie Mellon university database lecture series in some of the investigatory rabbit holes. It starts from the fundamental algorithms of how most databases work. Again, very cool, but can I get even the gist of them by watching YouTube videos? The answer is a harsh no. Glancing over some videos barely scratches the surface.

That's why I started to supply the graveyard of side projects with a fresh corpse. This time it is a key-value store. Can you think of a more wonderful project? Honestly, there are some pretty interesting problems to solve there, at least if you are really nerdy! 🤓

Why a key-value store if I am interested in Postgres? 

The answer is ingrained in the practice of zone of proximal development. Learning about RDS internals is only possible if I know the basics. If you squint your eyes a bit, a relational database is a key-value store. Sure, there is the whole query language thingy, but I need help grasping it. I must know the foundation on which those algorithms are built.

In short, I've implemented a linear hashing KVS with a simplistic implementation of how data is persisted to disk. That means 4K pages, page directory, page buffer, LRU cache, free pages, etc. I also intend to be mindful of excess allocations, handle mostly raw byte arrays, and occasionally benchmark the thingy. All of these are present in Postgres on some level but, of course, in a more sophisticated form.

It is in it's early days but here is the repository

https://github.com/jjylik/aapari


Comments

Post a Comment

Popular posts from this blog

I'm not a passionate developer

A family friend of mine is an airlane pilot. A dream job for most, right? As a child, I certainly thought so. Now that I can have grown-up talks with him, I have discovered a more accurate description of his profession. He says that the truth about the job is that it is boring. To me, that is not that surprising. Airplanes are cool and all, but when you are in the middle of the Atlantic sitting next to the colleague you have been talking to past five years, how stimulating can that be? When he says the job is boring, it is not a bad kind of boring. It is a very specific boring. The "boring" you would want as a passenger. Uneventful.  Yet, he loves his job. According to him, an experienced pilot is most pleased when each and every tiny thing in the flight plan - goes according to plan. Passengers in the cabin of an expert pilot sit in the comfort of not even noticing who is flying. As someone employed in a field where being boring is not exactly in high demand, this sounds pro...
Post a Comment
Read more

Bird is causing high CPU on my macOS

There is no lack of people complaining about MacOS Tahoe, mostly about rounded corners and inconsistent design decisions. I have not paid that much attentention to that, but there is one mac bug i have paid attention to. It hasn't been a visual or ux but rather few system processes pegging the CPU. trustd , alongside with ecosystemd and ecosystemanalyticsd all reported high CPU usage. I can't exactly recall when this started, it might have predated my Tahoe upgrade but anyway, the trio of processes all had high CPU usage. Sure, it may have been the virtual efficiency cores and whether it affeced battery life or slowed down other processes i don't know to be hon...
Post a Comment
Read more

Ousterhout's law

Back in the day, everyone was using Winamp. It is a music player with the user interface of a mixing console. The bloody thing had an equalizer on the front page! As an amateur music producer, I know that EQ is a powerful tool but making changes that sound good is difficult, to say the least. Mixing engineers spend considerable effort with the artist to balance the frequency ranges to arrive at the desired musical outcome. I bet the 15-year-old me butchered a lot of songs with the thing. Now we are using Spotify, a player with basically a search bar and a play button. I ran into something called Ousterhout's Law on the  Operating Systems: Three Easy Pieces book . Here is a quote from the book TIP: AVOID VOO-DOO CONSTANTS (OUSTERHOUT’S LAW) Avoiding voo-doo constants is a good idea whenever possible. Unfortunately, as in the example above, it is often difficult. One could try to make the system learn a good value, but that too is not straightforward. The frequent result: a configura...
Post a Comment
Read more