kmacleod

6 ms·

31.
by kmacleod 2y ago
Every team has process. It doesn't matter if it's documented or not, or whether improvements (or impediments) are intentional or not. Every team has their process. Source: Identifying teams' principles and practices is one
32.
by kmacleod 2y ago
As for general principles, if one’s packer, containerfile, cloud-init, bash, ansible, or puppet is much more than “install packages, set keys and a small amount of per-environment config, and start services,” it is likely that local package
33.
by kmacleod 2y ago
I've long envisioned a glue architecture around a scalable SmallTalk core. The ST bytecode can be run on various size compute cores from 8-bits to 64-bits. All the ST does is handle code flow. All compute is handed off to co-process
34.
by kmacleod 2y ago
I don't know why you're getting downvoted. I used to work for a PRT (podcar) company and for anything up to a large commuter train or major New York subway, compared seat-mile for seat-mile the networks of small vehicles are just
35.
by kmacleod 2y ago
> A lot of commercial software seems to mostly be about copying existing popular work in some legal way. It only exists because it copies its competition. Fixed that for you. But not really. Open source software exists because a commun
36.
by kmacleod 2y ago
Too late for anyone to see this, but GE/Durham, who build jet engines, do (did?) small teams (<20) with 170 employees and one manager. Fast Company: Engines of Democracy (1999) https://www.fastcompany.com/37815/
37.
by kmacleod 2y ago
Exactly. Black and white TVs worked very much like oscilloscopes and had almost no definition of horizontal resolution. Very few color broadcast TVs were made with three separate beams and three separate color filters (like rear-view proj
38.
by kmacleod 2y ago
Would this be the equivalent of Mock (Fedora) or sbuild (Debian) pristine chroot builders? Containers are just fancy chroots.
39.
by kmacleod 2y ago
This. I've seen kids with wheelies these days. They can go from climbing to zipping around the place with the simplest of natural transition.
40.
by kmacleod 2y ago
I worked for a video titling company in the 80s during their transition from Analog titling to Digital titling. One key thing I learned there is that CRTs have about three times the horizontal resolution folks give them credit for. Most f
41.
by kmacleod 3y ago
Your (3) is ssddanbrown's case. The whole must be distributable under the GPL. Nothing changes with ssddanbrown's repo, license, or anything. At a future time should they "code it out" and substitute another non-GPL li
42.
by kmacleod 3y ago
And that's not what I mean. I understand the linking issue. What I'm saying is that the GPL does not force or require someone to relicense their code. Their code is theirs. They only have to license the distribution as a who
43.
by kmacleod 3y ago
Confirming what panzi is saying here, ssddanbrown you do not need to relicense your work. GPL and MIT are compatible. GPL only requires that you distribute the _combined_ work as GPL. So, your github project remains MIT and others can us
44.
by kmacleod 3y ago
Note that there are two ways to look at derivative works. You're describing a Venn diagram of two independent circles, LibraryA and AppB, and saying AppB does not use any code internally from LibA, share code, modify code from LibA, et
45.
by kmacleod 3y ago
I'm not sure you realize all that Agile gave you that you described: kanban, a direction and goal, self-organized, iterative builds, I assume version control, daily builds possible, in front of stakeholders, adjust, repeat, necessary d
46.
by kmacleod 3y ago
My concept is SmallTalk-ish. Control flow, object frames, and GC in one unit and all higher level math, array, function, FPGA, GPU cell are in one or more adjoined units. The control unit keeps the higher level units fed in a hyper-thread
47.
by kmacleod 3y ago
git log <base-branch>..<branch> I often need the count of commits, usually for build IDs, git rev-list --count <branch> ^<base-branch> I usually use gitk for visualizing branch commits. CLI equivalent
48.
by kmacleod 13y ago
LGPL allows for static linking. The distributor need only be able provide the binary library elements necessary to re-link the LGPL library against. OpenIndiana already provides those. In other contexts, it wouldn't even matter if t
49.
by kmacleod 13y ago
The OpenIndiana package repository[1] appears to contain several dozen (counting all Gnome packages as just one) GPL'd packages as part of the OpenIndiana-distributed greater work. Can you be more specific as to why this one package w
50.
by kmacleod 13y ago
That's not correct. At its level systemd is just a component, it's not linked against anything that would cause it to be incompatible and all communication with systemd and its parts are through process-level interfaces (like D-B