What's your recommended way of implementing this in a simple App Server <> Postgres architecture? Is there a good Postgres plugin or do you utilize something on the App side?
I agree with you. I tried really hard to get this escalated. Tier 1 seem to have absolutely no ability to escalate tickets. It's a cost-saving decision for sure, and it feels really bad to fall between the cracks due to it
They're not a bad actor, I wouldn't be surprised if they have no idea they're even logged in.
I actually just threw away my TV in the local drop off point. I thought it was broken beyond a point that was worth to repair but I'm guessing somebody more handy than me picked it up and DIYed it
How do you imagine types would prevent this? No matter how I think about types in this context, I think a runtime check of "is this ID an app ID?" is mandatory in order to truly prevent this (alternatively- different URLs/parameter names to delete an app and a site)
pnpm has been my goto JS monorepo package manager + script runner for a couple of years now. IMO it has almost zero downsides and huge upsides. I'd be surprised if npm doesn't end up adopting the pnpm node_modules directory hierarchy in the next 5 years or so.
I'm a crypto novice. My impression is that the author is correct (though the metaphor with the gas company is terrible) - there is no way to reverse a bad transaction.
I appreciate the stated goals of Pen. However, I don't see how these goals translate to language design. Anybody tried the language and can share how the design facilitates these goals more so than other languages?
- Everyone can learn the language and participate in actual development quickly.
- Developers can focus on application logic rather than ever-changing implementation details.