This guide builds one application with all of those doors on it, from punk new to a passing test suite, using four pieces of the Punk ecosystem: Punk::Auth for the identity and the single-use tokens, Punk::Plugin::Mailer to send the tokens through Resend, Punk::Plugin::TOTP for the second factor, and Punk::Plugin::OAuth2 for GitHub and Google. - Source: dev.to / 13 days ago

What started as a small Nuxt integration eventually became a full Node.js and TypeScript SDK for MailChannels. Along the way, I learned a lot from the Vue, Nuxt, and UnJS ecosystems, took inspiration from other developer-focused tools such as Resend, and eventually had the opportunity to join MailChannels and get the project adopted and officially maintained. - Source: dev.to / 22 days ago

Two practical pieces. First, you need a transactional sender that can do broadcasts. I use Resend because the API is good, the React Email integration is good, and the dashboard is sane. Postmark and AWS SES work fine too. Second, on every publish, send a broadcast to your audience. This is the closest thing you have to a guaranteed reader. - Source: dev.to / 3 months ago

Resend has quickly become the default way to send email from modern applications. The API is clean, the deliverability is good, and the developer experience is impressive. But Resend only handles sending emails. It provides a html field and you produce the HTML that you've ensured is compatible with Gmail, Outlook, and the many other email clients. - Source: dev.to / 3 months ago

Netlify/functions/comment-handler.js is triggered by a Netlify outgoing webhook Whenever a new submission hits the blog-comments queue. It sends an HTML email Via Resend (the same delivery layer used for new post notifications) containing the comment text and two HMAC-SHA256-signed action links:. - Source: dev.to / 3 months ago

Have you ever read any of the introductory material that the git project itself maintains for teaching how to use the tool? - https://git-scm.com/docs/gittutorial - https://git-scm.com/docs/giteveryday - https://git-scm.com/docs/gitworkflows - https://git-scm.com/docs/gitfaq - https://git-scm.com/cheat-sheet Or if you want to sit down and really learn the nuts and bolts - https://git-scm.com/book/en/v2. - Source: Hacker News / about 1 month ago

I was uncomfortable with git until I read (the first 3 chapters of) the pro git book ( free here : https://git-scm.com/book/en/v2 ). It provides a great mental model of how git works under the hood. The UI of git - for better or worse - directly reflects its internals. And when I understood them, everything clicked into place. - Source: Hacker News / about 2 months ago

This reminds me of a passage from the book "Pro Git". "Here’s an example to give you an idea of what it would take to get a SHA-1 collision. If all 6.5 billion humans on Earth were programming, and every second, each one was producing code that was the equivalent of the entire Linux kernel history (6.5 million Git objects) and pushing it into one enormous Git repository, it would... - Source: Hacker News / 4 months ago

If you want to go deeper into how Git actually works, the Pro Git book is the best resource out there. It is free to read online at https://git-scm.com/book/en/v2 and covers everything from basics to advanced internals. I highly recommend it if you really want to master Git. - Source: dev.to / 4 months ago

The relevant XKCD comic https://xkcd.com/1597/ FWIW I too was once a "memorised a few commands and that was it" type of dev, then I read 3 chapters of the Git book https://git-scm.com/book/en/v2 (well really two, the first chapter was a "these are things you already know") and wow did my life with git change. - Source: Hacker News / 5 months ago