If you have no explicit transactions, every insert/update is its own transaction (aka auto-commit). Depending on what you do, you might not need more. It’s still important to know that these execute as a transaction.
Yep, there have been times I get through a whole project without any explicit transactions. In fact it can be a sign of not fully normalized schema design if you rely on those a lot (which can ofc be fine if you deliberately wanted that).
These are still transactions! It's not uncommon for a large % of transactions in an OLTP workload to be only one query without explicit BEGIN / COMMIT; This is called an autocommit transactions or implicit transaction.
How nice for you. But since you totally neglected to say anything about your use-case or schema or query patterns, it’s impossible to know what this even means. Some use cases can trivially be done without any explicit transactions and you’re not giving anything up. For others (usually, something where you need to enforce invariants under high concurrency writes or writes+reads on the same data across multiple tables), transactions are pretty critical. So, it depends.
Did you use SELECT FOR UPDATE at all, or just never had to update dependent data? If the complex operations are implemented using stored functions / procedures then the a transaction is implicit.
If the data is fairly straightforward like just one-to-many CRUD with no circular references, you would be able to do it without transactions, just table relationships would be enough to ensure consistency.
This is nice! This was a problem I faced a few years ago at my job. What I did was create a custom Bash function to switch Git accounts and add it to my .bashrc file. I love this. I’ll give it a try.
The more interesting question is whether AI use causes the shallowness, or whether shallow people simply reach for AI more readily because deep engagement was never their thing to begin with.
AI enables the stereotypical "idea guy" to suddenly be a "builder". Of course, they are learning in realtime that having the idea was always the easy part...
I had found this rebuttal: Ideas are cheap only if you have cheap ideas.
I would argue good ideas are not so easy to find. It is harder than it seems to fit the market, and that is why most of apps fail. At the end of the day, everyone is blinded by hubris and ignorance... I do include myself in that.
They may not be the easiest thing to find, but I'd submit that good ideas are way more common than the skill and resources needed to capitalise on them
Well the claim was that AI makes you boring. The counter is that interesting people remain interesting, it's just that a flood of previously already boring people are pouring into tech. We could make some predictions that depend on how you model this. For instance, the absolute number of interesting projects posted to HN could increase or decrease, and likewise for the relative number vs total projects. You might expect different outcomes
Writtte is an open source document editor. It’s built on top of TipTap, with all extensions written from scratch to fit our use cases. The frontend uses no framework, just vanilla JavaScript with a custom router. It runs on Bun.js, with custom server files and built-in caching. The whole codebase is included and easy to read. We’re getting a good number of users already, and Sentry hasn’t reported any critical issues (yet). If you’re interested, feel free to check out the repo. Thanks!
The backend is written in Go and uses minimal external libraries. We built our own logging library and run everything on Go’s standard HTTP package.
For the database, we use PostgreSQL. All db-related logic is written in SQL files, which allows us to run unit tests (the test files are not included in the repository yet). The backend communicates only through PostgreSQL functions, there is no raw SQL embedded in the application code.
That’s the overall setup. I’m also still working on the build documentation.
I run two production RDS instances by myself. I never thought I really needed something like this. What I usually did was just check the details on the AWS dashboard. Thanks for building this. I love it.
I used a similar tool called AsciiFlow (asciiflow.com). This Monosketch seems easier to use. The best part is that we can add diagrams directly inside the source code.
reply