manoji

I doubt if we will ever get AGI.

This !! I like the thinking and behind programming . My most fun has been solving programming puzzles on sites like leetcode and codeforces. Most day to day programming is about solving business problems which are mundane need directing teams , designing interfaces , api's etc.Sure it helps to have some experience when designing API's and interfaces but thats something that can truly be learnt in a year . Architecting is definitely fun but to build a real system that can stand the test of time takes years and years of understanding the problem you are trying to solve .Any decision you take will take some time before you see the impact and then you take those lessons with you for future architectures . Something that LLMs can never take away.

Such a good write up . Having explored a little bit of sqlite internals for a codecrafters challenge i was mildly happy i could follow along what was happening .

Hey ! Great work , I wanted to try something like this as well to begin my journey into games and computer graphics . I would love to know what resources you used to learn.

This is spot on ! Most of the work we really do is pure boilerplate and should be automated. While there are instances of interesting work those are far and few in between . The most recent instance of "how the hell did they do that?" for me was duckdb.

Yes , I had so much fun implementing sqlite from the scratch . Incidentially it was right about the time I started trying claude code. I did the last challenge in sqlite to scan with an index using claude code and I was blown away. It actually solved it.

I am working on trentdb . An in process single node database query engine inspired heavily by duckdb . Its primarily for me to understand databases in depth . Its completely written by codex and in java . Why Java? Its the language I am most familiar with . I just finished adding support for running all TPC-H queries.

Excellent article . Few more that come to mind

Think real carefully about breaking transactionality unless absolutely needed . It has been the single source of most problems i have seen over the past few years.

Keeping 2 different systems in sync is really hard do not do it if you dont have a real need to do it.

Monoliths are really good , there is absolutely no need to run microservices or any services for that matter other than a single monolith. The place where i work at is generating billions of dollars with a single monolith.Having said that there will come a time when some logic has to go to a different services , If you get there your company is really really successful :) .

Relational databases can do a lot more than what you think and they can absolutely scale well.