(McKenna tangent). I like this version of that talk. https://www.youtube.com/watch?v=hL0yfxDe6jE. It's about 12 minutes and animated with some hand-drawn whiteboard drawings. Good stuff.
> In my last performance review, my manager was actually surprised when I told him that I am now more a manager of my own work than actually doing the work.
I think this is very telling. Unless you have a good manager who is paying attention, a lot of them are clueless and just see the hype of 10x ing your developers and don't care about the nuance of (as they say) all the surrounding bits to writing code. And unfortunately, they just repeat this to the people above them, who also read the hype and just see $$ of reducing headcount. (sorry, venting a little)
Great link. I've always been drawn to sqlite3 just from a simplicity and operational point of view. And with tools like "make it easy to replcate" Litestream and "make it easy to use" sqlite-utils, it just becomes easier.
And one of the first patterns I wanted to use was this. Just a read-only event log that's replicated, that is very easy to understand and operate. Kafka is a beast to manage and run. We picked it at my last company -- and it was a mistake, when a simple DB would have sufficed.
I've been through a Vista Equity acquisition. It was not pretty -- they slashed, consolidated and basically ran their one-size-fits-all playbook. The brought in their crew -- which is totally expected -- and then bought other companies in the same vertical. Of course, they all had different tech stacks.
(like ya said, operators is the right word. it felt icky)
At least for the first year, the acquired teams were able to run more or less the same but with new hyped-up-overly-aggressive Vista hotshot managers and then the sh*t-from-above just started raining down.
Also, they hired the worst sw architect / person I've ever had to work with. He wasted so much time and money.
Thanks for the reply. Summary: Here's this really cool thing we're doing! Oh, are you wrote something exotic for it? Nope, just regular Erlang goodness that's been around 20 years.
If you look at Elixir keynote for Phoenix.new -- a cool agentic coding tool -- you'll see some hints about a browser control using a API tool call. It's called "web" in the video.
Interesting project. I'm glad Vue is getting the same attention as the Svelte one. And props for digging in to optimize the payloads, and making it diff-able.
Can you just drop existing Vue components in there? Or are their LiveVue specific things you need to add?
You may want to consider Elixir instead. It has an easier syntax and is (don't quote me on this) equivalent in function and purpose with Erlang. Plus you get lots of other goodies like LiveView (notebooks) and a good web stack (Phoenix).
For people wanting to dig into this idea some more, I'd recommend the book by Austin Kleon called "Steal Like An Artist." Also, there is some nuance in the book about copying and stealing, without being a thief.
Totally agree. A general-purpose solution that ties together different messy interfaces will win in the long run -- i.e the IP protocol, copy-paste, browsers. In these cases, they provide a single-way for different aspects of computing to collaborate. As mentioned before, semantic web initiatives did not succeed and I think there's an important lesson there.
My experience with Notion keyboard use is different. It's not 100% VIM hands-on-keyboard mouse-free but it's getting there. If there was only a "insert after this block" shortcut.
My favorite is to type something then /turnh3 where /turn let's you turn the block into something else.
(newbie checking) tsnet is a really interested idea -- that an application can act like a device with networking baked in. that applicatin access can be controlled at the network level via the tailescale ACLs.
couldn't this just be framed / spun as just using search data as training? i don't seem being bundled enough to run afoul with anti-trust.