Fun fact, you can actually use the current send_email binding to send emails to verified emails in your account (but this announcement will make it possible to send emails to everyone)
You can also reply to incoming emails from what I know, you just cannot initiate any email directly to prevent the obvious abuse. I wonder how they plan to mitigate that apart from keeping the pricing sane.
> Engineers are burning out. Orgs expect their senior engineering staff to be able to review and contribute to “vibe-coded” features that don’t work.
It’s not just engineering folks that are being asked to do more vibe-coding with AI. Designers, product folks, project managers, marketers, content writers are all being asked to vibe code prototypes, marketing websites, internal tools, repros, etc. I’m seeing it first hand at the company I work at and many others. Normal expectations of job responsibilities have been thrown out of the window.
Teams are stretched thin as a result, because every company is thinking that if you’re not sprinting towards AI you’ll be left behind. And the truth is that these folks actually deliver impact through their AI usage.
My wife's seen this at multiple non-tech companies, and it's a disaster every single time. Most (like... 95+% of) folks can't use these things very well, being forced to use them kills morale because they're frustrating as fuck (and managers largely have no idea what they're actually capable of doing productively, so expectations are all over the place and often fantastical) and dealing with the output of co-workers who can't use them well is even more frustrating than the LLMs themselves are. It's sometimes coupled with attempts to realize the increased "efficiency" before it's even proven it exists, by firing significant chunks of staff at the same time as adopting "AI processes", further stressing out remaining employees and ruining ability to actually get things done.
It's trashing whole departments. The come-down from this high (which high is being experienced pretty much only by the C-suite and investors) is gonna be rough.
I've been trying to build a tool that solves that niche problemset of facilitating the edit flow of a dev blog.
I liked Forestry, but wanted something that was embedded directly into my website, so I built Penmark CMS https://penmark.appsinprogress.com/. Inspired by utteranc.es, it uses the GitHub API to make edits directly to your repo. It's definitely a simple CMS but I'm liking it to write for my own blog!
It uses GitHub's own APIs for syncing the storage with your repository, so there is no proxying, only direct access to GitHub.
When you sign in, a token is obtained on your behalf by the Penmark GitHub app, the redirect goes through and passes your own token to your browser, and then this allows the browser code of Penmark to use it to store & sync to GitHub directly
I've always found editing my blog via desktop editors to be inconvenient, especially when it came to keeping the repository in sync and trying to edit on the go, and relying on an external CMS or tools like the now-discontinued Forestry.io was complex to setup for simple cases and spread my website & workflow over multiple different apps. Around the same time, I discovered utterances [1] on here, a comments widget backed by GitHub for your website. Inspired by that project, I decided to build Penmark.
Penmark is an embeddable CMS for your Markdown-based, GitHub-backed sites. Penmark can be embedded directly into your website, allowing you to access a rich text CMS editing experience without external tools, and while keeping all your site's content in your repository.
It's simple to setup, embed the 3 components (Login, Drafts, Edit Post) that create the CMS experience within your site and add the GitHub app to your repository.
Once you've set it up on your site/repo, you can edit directly from your site, on the go and from any device, and let Penmark take care of all the operations needed to keep your site and repository in sync.
I am in the same boat, and I recognize that my desire for office life requires others to also come into the office. Reading this thread, it seems that the vast majority of people in this industry prefer WFH, and people who prefer WFO may have to choose specific companies or reconsider this industry.
Please don't complain about tangential annoyances—things like article or website formats, name collisions, or back-button breakage. They're too common to be interesting.
