When you successfully do something modestly complex, you should write down what you did and share it. This way the future you will have some inkling of what you were thinking at the time so that they have some hope of fixing it when it breaks.
This is doubly true for home and hobby projects where you might really never notice downtime until much later than the actual failure.
measuring complex systems Show more
1.you can't measure a complex system without changing it in the process
2. any metric that you can come up with, once people are aware of it, can and will be gamed
3. something deeply philosophical about "the quality with a number"
Too complex to reason about Show more
I am giving a talk about complex systems. The more I look at them to prepare the less I am confident that I understand them.
Some of these items have names that only start to make sense if you already have a ton of context.
The bigger systems are tangles that have accumulated dependencies willy nilly over time, to the point of near collapse.
The best of them depend on components that have been largely abandoned by their creators.
build systems as low value work Show more
[D]evelopers want to focus on the high value tasks they are engaged in... not becoming build system experts.
on the problems of doing monorepo-style development with open source dependencies, and on motivating developers to care how their systems are built.
rusty at writing Show more
I wrote a lot of words this afternoon, and now I read them, and they don't make any sense.
It's as if I had forgotten for a moment that my primary audience for any of the writing that I've ever done successfully is for the future me (who will have forgotten what I have learned), and not for any other real or imagined audience.
I'm just rusty at blogging, I suppose the only thing that will fix that is practice. It is a bit discouraging to have spent that much time on it.
Someone needs to do a model of the software development process that looks like Chutes and Ladders.
You've added a new library that solves the task at hand with a lot less code, but in exchange you've inherited a new build system that doesn't quite work on your machine (go back 8 squares and down to another level to fix that).
A lot of things become easier for me to understand - but alas, harder to draw - when expressed in terms of graphs and transformations of graphs.
I realize at times that this makes me come to conclusions that look like leaps of logic, especially when it means moving from one problem domain to another. "Wait, how did you get there?"
The usual alternative to tmux is screen, which is similarly hand-crampy and a bit older. I don't know how complex your setup is.
In the same breath as both of them I usually mention `mosh` which is really good at keeping a connection to a remote system up in circumstance where `ssh` would fail.
85网 88 〽️🤑👹 89 🐂㊑ 91 ☎️网📡📰 95 ㆙💳网 98 🌉🌉网⓿👦①🌳网➎👦⑥〽️📚网 ⑨ 🌰📰(🐸🤠) ⑫🌞🏭🍓💻⑰ 🗽📦网 ⑰ 🤖💪📰 73!
Hi there! A2mi.social is a Mastodon community intended for people living/working/studying in and around Ann Arbor (including Ypsi and elsewhere!) and their friends. Please read more about this community here, including this site's rules and other important information.