PGSimCity - How PostgreSQL Works
51–60 of 104 posts
Re: PGSimCity - How PostgreSQL Works
#52Re: PGSimCity - How PostgreSQL Works
#53Besides the sadly obvious vibe-coding, just note that SimCity is still an active trademark from EA, so might be good to rename it.
Re: PGSimCity - How PostgreSQL Works
#54Re: PGSimCity - How PostgreSQL Works
#55Re: PGSimCity - How PostgreSQL Works
#56Earlier quoted context omitted.
Yea on mobile especially
I hear you. WIP! thanks for all the feedback. It's amazing for me too. It all started yesterday with a single prompt and curiosity what Opus 5 can do. ~3.86B tokens used so far (not counting GPT 5.6 Sol that at some point started to do a lot of legwork for coding)
Re: PGSimCity - How PostgreSQL Works
#57I imagined as soon I saw the initial visual that I would somehow be able to enter a query and it would walk me through the flow through the entire system starting from input parsing to all the way to delivering output and perhaps along the way understand some of the autonomous processes that happen in parallel that aren't query specific but run constantly. What others are saying - fantastic attempt, but don't know wh…
try pressing T
Re: PGSimCity - How PostgreSQL Works
#58Earlier quoted context omitted.
how do you know it has been vibe-coded? And why does it matter?
Because it reduces my trust in the truthfulness of the represented information.
Re: PGSimCity - How PostgreSQL Works
#59Considering that it has been vibe-coded with not even 48 hours passed: Is this truthful and accurate at all? Or will it lead to false conclusions and anti-knowledge?