| Website | https://www.calleluks.com |
| https://twitter.com/calleluks | |
| GitHub | https://github.com/calleluks |
| Website | https://www.calleluks.com |
| https://twitter.com/calleluks | |
| GitHub | https://github.com/calleluks |
I'm really excited to finally introduce Pliro: the all-in-one tool for publishers to run a low-maintenance and profitable subscription business 🥳
https://pliro.co/blog/introducerar-pliro (in Swedish)
Regardless of whether you are running a website, publishing a paper magazine, an email newsletter, or a podcast, Pliro lets you focus more of your effort on what really matters to your subscribers: your content.
@pliro I think my preference would be to use prefixed k-sortable random IDs, similar to Stripe's (e.g., cus_abc123) but I'm worried this might give us grief down the line due to not following Rails "conventions".
Have you ever regretted using custom string primary keys in Rails with Postgres?
We're just about to have our first customer start integrating with our API @pliro (🥳) and I'm currently fretting about what kind of IDs to expose 😬
Have you ever regretted exposing auto-incrementing primary keys in an API or web app?
My post this morning feels even more timely with all the AI news today about GPT-4 & ChatGPT set to the backdrop of announcements of yet more layoffs.
Everyone's talking about AI, but we're not hearing nearly as much about how it's going to affect the labor market. So I developed a few criteria to help you determine whether your job might be disrupted by generative AI and (more importantly!) what you can start doing *today* to AI-proof your role.
https://blog.testdouble.com/posts/2023-03-14-how-to-tell-if-ai-threatens-your-job/