Show newer

Feeling an evil glee from this code. I've gotten this "Corestore" module to replicate cores from two different versions by instantiating the old core version manually and injecting them into the map used by the corestore to track what it's already opened.

Love when API authors don't bother with private variables so I can monkey patch their internals and make their code whatever I want 😈

> participants were able to volitionally modulate the firing rate of the direct neuron in these previously uninvestigated structures

pmc.ncbi.nlm.nih.gov/articles/

@carnage4life This is the root cause of almost all technical conflicts I need to mediate. People wasting their time arguing, instead of understanding.

The eng leads at YouTube had a great way of addressing this. One of the ground rules for any VP-level Eng Review was that each side needed to be able to articulate the other sides perspective, including pros/cons and top concerns. If you failed to demonstrate this during the review (either explicitly or implicitly), then the meeting was stopped and rescheduled for later. Both sides were told to go back, understand each other's points, rework the deck, and come back when they could articulate each other's side.

SVPs shouldn't waste their time mediating catfights. They need to focus on making hard technical decisions that will determine the success or failure of the company. Putting this ground rule in place (and living by it) quickly got the message across -- don't bring us fights, bring us hard problems with difficult tradeoffs.

Worked wonders.

Found a neat feature using geohashes for restricting content intended for specific areas. Might reuse this spec for my decentralized spatial indexing mesh. hashstr.com/

I would have a lot more trouble functioning if I didn't have techno.

Distrobuted Geospatial Table: LoRa or HaLow mesh. Nodes are kv stores tjat need you to be physicaly close. Ask the mesh for mearby spatial data. Nofes only respond if there's more than N items for the scale you're searching on.

baby: you see this playpen? this cage they’ve got me in? you know what it’s short for? play penitentiary. yeah, that’s right. and they decide when i come and go. [takes a long swig from the baby bottle] geahhhh 🫩

For an uncommon gene, it seems I'm surrounded by cilantro soap tasters

Buhhhh my friends are all too busy to go clubbing tonight 🥲🥲🥲🥲

The clown makeup I did for halloween isn't coming off 💀💀💀

I made a fun little thing over the weekend that had been on my mind since the local-first conf. I combined @ethersync and the Language Server Protocol to enable some kind of real-time collaboration in Helix.

I use the "textDocument/didChange" event to track editor's changes and convert them to an edit message in Ethersync.

When a peer makes changes, the other peer receives them from the Ethersync daemon and converts them into a "workspace/applyEdit" message.

Also thinking about using inlay hints for showing other peer's cursor

I'm not sure if that will even be able to work properly, but it's worth trying anyway

Ethersync: github.com/ethersync/ethersync

#localfirst #p2p #lsp

Show older
Mauvestodon

Escape ship from centralized social media run by Mauve.