Mindblown: a blog about philosophy.
-
2025/06/20 [Learn Postgres]
I started the chapter about triggers and rules. Both seem to be very powerful tools. I can see how they enable for example denormalization. I am still curious about maintainability. Let’s say table A is replicated to table B. If table A changes it’s schema it should be recognised by a linter and force programmer…
-
25/06/20 [GADM-api]
Yesterday evening I added level 1 /geojson endpoint. I am still not happy with all code duplication – even after abstracting header setters and query parameter parses. Also I need to create an automation for dev server re-lunch on file save.
-
2025/06/19 [GADM-api]
I refined how pagination parameters are parsed and standardized how headers are being set for /geojson and /feature-collection endpoints. I started working on endpoints for level 1 but before I can complete it I need to refine the way json properties are being generated in sql queries.
-
2025/06/19 [Learn Postgres]
I finished the chapter about postgres functions. I feel the syntax is quite cumbersome and I can’t find a good use-case for them now. I imagine they will come handy when combined with triggers or cron jobs. I am looking forward to next chapter about triggers.
-
2025/06/18 [Learn Postgres]
Moving on with “Learn PostgresSQL”. Today I went through a major part of “Server-side programming” chapter, including data-types (hstore, json, jsonb, dates and time) and writing functions with SQL and PL/pgSQL. Functions in database seem interesting, I can foresee certain use cases. However they also seem like a serious maintenance effort. Perhaps they require integration…
-
2025/06/18 [GADM-api]
I am working on abstracting my queries with squirrel package. I need to find a reusable and scalable approach before I will move on with next endpoints. At the moment I have two endpoints – one that returns FeatureCollection and one that streams new-line delimited GeoJSON. The second one will require extra abstraction for streaming…
-
About Programming Paradigms – Part 1
A programming paradigm is a fundamental approach to solving computational problems. But what exactly is a computational problem? In essence, a computational problem involves working with information—how it is stored, processed, and manipulated to achieve a desired outcome. Examples of computational problems include: As computational problems grow larger and more complex, so do the solutions…
-
Understanding Git
Some time ago, I stumbled upon the Initial Commit blog. While exploring its articles about Git, I decided to summarize my findings in this post. Git is a version control tool that enables you to save snapshots of your project. These snapshots allow you to navigate back and forth between different project versions. A single…
-
Pragmatic Testing
Notest about testing from the book “The Pragmatic Programmer” by David Thomas and Andrew Hunt
-
Snake Game – Log 2
I am working on the game system overview. Without going into details and technologies I sketched out how I imagine the game should work. Client My Snake will be a browser based game. I am not planning to use fancy frameworks works, for now I can start with a simple canvas. From the client perspective…
Got any book recommendations?