fsniper

I had to take a step back before I got the reference :)

Oh unfortunately not. I only created the gear for this one. My father in law worked on the sewing machine.

When you consider "my problem is solved this time" as documentation then a discord discussion can be considered good documentation. But If you want documentation as reference for everyone and don't wan't to repeat process/procedures every time some one needs it. It's the worst platform for it. And For documentation we never want the first.

In this context email lists were the best of the best documentation ever.

Hey, this is not cool! Please think of us who learned English as a second or least. We still can't keep up with the book English and you invent this shit?

I hate video links. The information could have been a few paragraphs of text that I could glance. Instead this much minutes of video that you can't search, glance over, read while listening to something else.. So it's a pass for me.

Totally unrelated, these second black circles on the people in the background 🤣

I wouldn't ever imagine to shed a tear for the processes I have killed in my whole life. I feel like a homicidal maniac.

this is not cancellation. This is Google taking a step back, and regroup to attack back.

Repeat after me: Doctor regenerating to a woman was never the issue.

But bad writing, bad acting, forced relationships, killing the established lore, being boring .. These are the worse sins.

Anon is a server. But can't anon be a server and have a relationship at the same time? Does not compute?

First, persistency. You data lifecycle may not be directly proportional to your applications lifecycle. You may need it even after the app is shut down.

Second, RDBM systems provide a well defined memory/storage structure and API - "structured query language". This enables you to easily query your data and acquire suitable views that are beneficial for your applications purposes.

Third, It's always better to outsource your data layer to a battle tested, and trustworty database then trying to reinvent the wheel.

So this paves a road for you to focus on your business logic than splitting that focus for the data layer and business logic.