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.
I support people to use any possible tool in their creation process.
This is not very different than using newer electric tools in cooking vs using the older/habitual techniques. Some may prefer the former, some later. The taste could be different pallet to pallet, or the subtle chemical reactions could cause different outcomes for different foods.
If the food is tasty, fulfilling and suitable for my pallet what would differ if chopped with a knife or with a blender?
You can prefer one to the other and who have any right to say no? Just don't forget same applies both ways.
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.
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.
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.
I support people to use any possible tool in their creation process.
This is not very different than using newer electric tools in cooking vs using the older/habitual techniques. Some may prefer the former, some later. The taste could be different pallet to pallet, or the subtle chemical reactions could cause different outcomes for different foods.
If the food is tasty, fulfilling and suitable for my pallet what would differ if chopped with a knife or with a blender?
You can prefer one to the other and who have any right to say no? Just don't forget same applies both ways.
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 🤣
Donna is probably one of the best if not the best companian.
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.
Don't blame remote work, blame all the underlying problems related to housing pricing and politician who really does nothing to solve it.
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.
I suppose it's "confusing perspective" worthy.
It's time ROI to disengage from UK/NI and integrate more with Europe. Starting with freedom of movement.
That's ridiculous. That's their property. And it does not look half bad at all.
Then I hope it won't get any traction.
I hope this is a joke and not intended to be real.
What? The? Fuck?
I changed the nozzle while the heat block was 200C.