If you use #tauri and find the way commands are registered in most docs and examples clunky, this might be helpful:
https://til.io/posts/2026/06/14/tauri-tips-1-invoke-handler/
| Homepage | https://til.io |
Jesse
@jtolj
- 13 Followers
- 120 Following
- 44 Posts
Software developer (#php #laravel #golang #javascript) among other things in Richmond, VA
I'm pretty new to #rust - is this a stupid thing to do in a unit test suite to ensure my fixture touches every variant?
Learned about this today from an MDN search: the #html inert attribute.
"A Boolean attribute indicating that the element and all of its flat tree descendants become inert."
...
"When an element is inert, it along with all of the element's descendants, including normally interactive elements such as links, buttons, and form controls are disabled because they cannot receive focus or be clicked."
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/inert
HTML inert global attribute - HTML | MDN
The inert global attribute is a Boolean attribute indicating that the element and all of its flat tree descendants become inert. The inert attribute can be added to sections of content that should not be interactive. When an element is inert, it along with all of the element's descendants, including normally interactive elements such as links, buttons, and form controls are disabled because they cannot receive focus or be clicked. The inert attribute can also be added to elements that should be offscreen or hidden. An inert element, along with its descendants, gets removed from the tab order and accessibility tree.
Working solo right now and I've really missed the mentoring that I used to do when I had a team. I've been planning to live stream coding sessions to scratch this itch, and have been practicing that to an audience of 0.
It's kind of amazing how productive I've been when I'm vocalizing my thought process to this imaginary audience.
I've dubbed it rubber duck live streaming and it's my new go to when I'm stuck on something.
I'm not completely satisfied with this, but I've been mulling over this post for too long and needed to get it on the page.
My thoughts on #ai in software engineering, but hopefully a slightly different approach that's helpful to someone out there.
https://til.io/posts/2026/03/16/how-im-navigating-an-uncertain-future/
Terry Godier@manton all of my chips are on being a real human, writing code by hand, with experience and strong opinions. The era of personal software I think is here. And that is both personal as in folks will make their own, but also to be a person behind the software. there’s never been a more important time to have beliefs and make opinionated software that a robot wouldn’t.
Larry GarfieldI may regret this at some point, but I felt the need to put down in writing how I feel about this moment in the tech industry.
It is not kind. You may well be insulted by it. If you are... then you really should question yourself.
If you confidently share your predictions about the future every single day despite 100% of your previous predictions being wrong, you might be a (tech|crypto|ai|) bro. Just fyi.
I think the saddest thing I'm seeing from heavy LLM usage is the gleeful deskilling of people who used to be pretty okay at their jobs.
There's a nearly complete delegation of reasoning followed by a quick gut check ("LGTM") before committing the code, sending the email, etc. I think it's doing something very bad to the brain compared to reasoning it through yourself.
I feel very fortunate to be working solo this year and to have a lot of control over how and when I interact with this stuff.
Aram SinnreichImagine having a billion dollars and wasting your time doing anything other than:
1. Reading novels in the bath
2. Making art
3. Traveling
4. Cooking and eating
5. Giving heaps of cash to awesome people and institutions who need it