Been working hard on a big new feature for Ghost: automations! Publishers can send a sequence of emails when someone subscribes. More actions and triggers on the way. https://ghost.org/changelog/email-sequences-for-new-members/
Been working hard on a big new feature for Ghost: automations! Publishers can send a sequence of emails when someone subscribes. More actions and triggers on the way. https://ghost.org/changelog/email-sequences-for-new-members/
The orchestrator touches across all layers. With its open-source approach, with:
→the integrated #datacatalog that lists/surfaces all
→#explicitly define assets
→resources for integrating #compute as well as #storage
→integrating best practices
→general #automations
→#governed data platform
#Shortcuts give users access to an advanced layer of controls, actions, and #automations. Custom fade curves give you endless customization to your faders.
Widgets on your Lock Screen, Home Screen, & Control Center. However you want control, you can command it.
This is going to gain me some unfollows, or at the very least some side-eye/eye-roll looks.
The more I use #LLM tools in my day to day, the more I like them. Not to #VibeCode, but to use them as an actual #assistant.
I already wrote a couple of #automations for my team to improve our workflows and improve #consistency and #quality. One we are all actively using to interact with Jira, by following our team standards when writing epics, stories, spikes etc., as I said, it helps keep the content consistent and aligned.
I am also working on an automation for me that could eventually become another team-wide one that gives me a high-level status of all my pull requests, pending #CodeReviews, issue status, etc. and gives me a brief paragraph with how my day is going and recommends what should be my focus (based on the given priorities).
Do I need LLMs for this? No, but as a good engineer, the less I have to worry about some things, the more bandwidth I have to worry about other important things.
Could I do something like this with standard scripting? Most of it yes, but there is a very nice result of using LLMs that would be extremely hard or time consuming with standard tools; they are especially good at adapting to small edge cases and unforeseen or unimplemented features.
I also have to say I am not a stranger to vibe coding. I've done it, and I really like it for those little personal scripts and one-offs that used to take so long with so little gains.
Anyway, if you want to unfollow, block or just eye-roll me, I won't hold it against you.
One of the annoying feature of Google #pixel is that it turns the brightness to full when the charger is plugged in. It won't go back to normal when you unplug it.
I am using pixel 9
So used #tasker, when I connect to power it will turn on auto brightness.
#automations rocks 😉
Dear @homeassistant - why on earth was Continue on error for Automations, being introduced in 2026.3, not the default behaviour already!!!
Just finished watching @smarthomejunkie's video reviewing the 2026.3 beta (https://youtu.be/Xw92u4ZULXo), and I would have missed this important and valuable change if I didn't go back in the video when I heard something that stood out whilst multi-tasking.
Hey fellow #HomeAssistant Fediverse people - can you think of any better approach for this #Automations outcome?
tl,dr: When I arrive home - intent is to turn on the right things, in the right order, and running as many instruction groups in parallel for speed.
Scenes just don't give this level of efficiency, sequence or control (plus I hate the way scene editing works).
However, this automation is now so heavily nested I'm not sure if I've missed a trick to achieve this in a better way.