My work involves so much context-switching that I ended up building a weird system just to keep continuity. It’s basically an outliner inspired by MaxThink for DOS. At its core, it’s text plus structure: a tree you can revisit non-sequentially, with time anchors when they matter. It helps me survive interruptions and gaps without losing decisions, context, or long-running threads, and it helps me correlate my digital notes with my paper notebooks.

To support the “thinking” part, it also has some goodies for shuffling, sorting, splitting, and joining lists in place to help with ideation. I’m working on the fourth incarnation now.

I recorded a demo a few months ago to share with a friend. It’s not my best recording because I was recovering from hand surgery so typing was weird: https://www.youtube.com/watch?v=N9HX3G69Xdo

I may open-source it once I’ve worked the bugs out.

I've been using a git alias for quite some time

`lead = shortlog -s -n --all --no-merges`

I’m glad things went well for you and that you managed to regain control of your life’s work.

- on tab pressing, there's a percussive sound https://www.soundsnap.com/typewriter_electra_xt_old_electron...

- same happens on shift https://www.soundsnap.com/typewriter_erika_model_shift_press...

- same on other keys, like backspace

- once you reach the end of the page on some models, the carriage does't progress so you hit the same position over and over until you CR.

I've had a 3D printer for a while, and I have to say that Bambu has completely changed my perspective on the whole experience.

Before, I treated it mostly as a time-consuming hobby - setting up my own Octopi for remote printing, tinkering with different settings and parts on my Prusa. It was all trial and error, with most prints turning out below average.

Now it feels more like a continuous integration system. It runs mostly unattended, always ready to execute my next batch of prints.

I recently traveled for a week and only needed my wife to refill the filament and remove finished prints, allowing my workflow to continue uninterrupted.

I don't regret my initial experience since I learned a lot, but I really appreciate having a more streamlined process now.

Don’t forget that In large deployments, you have no idea who is using what, which features are enabled or what’s the flavor of optimization someone pushed to make things work for the customer. You have dozens of engineers and all trying to keep the lights on.

This was the state when I joined Auth0 and it took us a year to migrate every individual customer env to a managed PAAS and another year to migrate our multi tentant environments later.

* I understand that some people have concerns about the brand's security practices and affiliations, but I went further and completely locked it down from public cloud features.

No wonder we all turned cynical.

Unless you're in Germany using a service provided by the Vogons, you might end up getting a letter containing an activation PIN via snail mail or worst having to visit the post office to show your passport.

Turns out I found out you could even invite external collaborators into your fork and totally bypass enforced SSO.

Even if you block forking into your main repo, the existing forks remains active and still can pull from upstream.

It feels like if you need proper security, you have to go with enterprise

You're going in the right direction! for the near future, I suggest you to add a cli, connectors, simple symbolic calculation on notebooks (take some inspiration from calca http://calca.io/examples), offline support and fully encrypted namespaces.

That will put you miles away from everyone else in the field :)

You're probably busy with the launch, but you can contact me if you wanna discuss the list above,

Abraços

Recently I tried to render an animated scene that took me a weekend to render properly in 2003. It's still slow :D

https://fernandomeyer.com/microblog/2023-07-29-1107998078355... https://fernandomeyer.com/microblog/2023-07-29-1107998901402...

They have different heuristics for conflict resolution when more than one rule can be fired. Once you define the strategy, it will be consistent throughout the entire lifecycle.

Once the network is compiled, it ensures that previously matched patterns are not recomputed, which increases performance.

I’d be careful aggregating this.

First time I run a dhcp server by accident and suddenly went sideways but the blast radius was small,

Second time and more interesting one, My campus had a mac address allow list; when I got a new computer and didn't want to handle the process of updating my access access permission, I just run a script to change my mac to the old known address.

Later, I also sold the old computer to another colleague which didn't bother to register as well since everything was working. Long story short, we keep disconnecting each other.

One day I was, "c'mon, I'll fix this". Opened wireshark and started to capture network traffic. I've got a list of mac addresses from the pcap dump and every time I got disconnected, I ran the script spoofing my address to the next one in my list.

That worked fine until the day I spoofed the mac address of a central managed switch that shit itself out of the network.

:)

https://scholar.harvard.edu/files/yetisen/files/morpho_butte...

Comments URL: https://news.ycombinator.com/item?id=38894692

Points: 3

# Comments: 0

If you consider modern hardware and OS is practically impossible to have a simple enough machine that you could teach the young generation. Fantasy consoles like pico-8 are good options for programming, but not for understanding the hardware underneath. That way you still have school who use old architectures for teaching.