Skibidi.

Skill issue.

Have… you met C?

No, jokes are fun.

<table />

I generally agree, but there are some things that are oversimplified. Sure a point(x, y) can have public attributes, but usually business objects are a bit more complex: insurancePolicy, deliveryRoute, user, etc. Having some control over those is definitely something you want to implement, at the cost of some boilerplate.

Hence 80%.

Most apps out there are a CRUD with a thin layer of logic.

If you are in the 20% that needs real performance, an ORM is not gonna cut it, no matter what DB you have.

It’s literally what an orm does, and it’s good enough for 80% of apps out there. Using it for the wrong purpose is what’s silly.

In my 15 year career? Dozens. Maybe low hundreds. Depends what you work on. Oracle is not making any friends lately and a ton of companies a whole-sale migrating to Postgres, MongoDB, DynamoDB or some of the NewSQL contenders. It’s like 50% of the projects I’m involved in. Results are generally positive, with some spectacular wins (x3000 acceleration or x1000 lower costs) and a few losses.

I hope the tricks are only supported on kafka’s ksql.

Woosh?

Raid gang

I broke DNS plenty of times in my homelab independent from NAT. In the last few months:

• didn’t turn off DNS server in a wifi router set up as bridged access point
• dnsmasq failing to start because I removed an interface
• dnsmasq failing to start because the kernel/udev didn’t rename an interface on time
• dnsmasq failing to start because hostapd error didn’t set proper interface settings
• forgot to remove static DNS entries in /etc/hosts used for testing
• forgot to remove DNS entries from /etc/resolve.conf after visiting a friend and working on his setup

Yes, most of them is my dumb ass making mistakes, but in the end it’s something that constantly breaks and it helps knowing the IP addresses of my servers and routers.

Aditionally, obscurity is a security helper. The problem is relying only on obscurity. But if I have proper firewall rules in place and strong usernames and passwords I still prefer if you don’t even know the IP addresses of my servers on top of that (in case I break some of the other security layers).

Con: you are now even more dependent on DNS, increasing the blast radius even more if when it breaks.

You also have NoSQL databases, where you can have arrays, embedding and you can often save yourself the CPU hit of joins.

Well, it is.

Mastodon has at least 1000 accounts. No way of validating whether there are people behind them.

No, it tells us that this one post was more popular.

Yes, we need another PGP vs S/MIME flame war, it’s been so long!

Elaborate?