I go into the DAG-centric nature of Google's in my video, and that was one of the reasons for making it and the sim repo.
I did at the outset think that the Google way lead to faster builds. It could could be with parallel step execution and a build cache is setup, but I don't think it is significantly different in a vanilla serial mode.
Perhaps there's another benefit - slimming a monorepo to feed to a coding AI, in order to bring down tokens needed for a task.
I've WIP for a C# module, but I'm stuck on some fine-grained setup for 'vstest'. I also asked Google's Jules agent to migrate one of the depended-on modules to Kotlin, and it has been 24 hours now, with it assuring me that it hasn't stalled.
Yeah I'm not running anything llms spit at me in a security-sensitive context.
That example is not so bad - you've already pointed out the main obvious supply-chain attack vector in referencing a random ephemeral fork, but otherwise it's certonly (presumably neil's default) so it's the simplest case. Many clients have more... intrusive defaults that prioritise first-run cert onboarding which is opening more surface area for write error.
I just used Mermaid for multiple sequence diagrams from build-steps sequences in a video talk I did on comparing build systems - https://www.youtube.com/watch?v=L67ri_xe2oQ (slides - https://paulhammant.com/google-style-dag-build-systems/). The new boost for me was GPT4o. It was able to quickly make what I wanted from the build logs alone, though it took some hand tweaking too. A new (or very old) problem after that was not taking sufficient save points (URL bookmarks) and sometimes making the same edit twice cos I'd lost a URL. That there was a second save of the PNG form for each (https://kroki.io/mermaid/svg/...) added to the keep-track-of-changes problem for me, especially when I'm very tired me :(
Great tech - thanks for your pioneering work. I made https://vsm-book.com/app as a tool to support a meeting and leave a lasting artifact. WebSequenceDiagrams (and https://bramp.github.io/js-sequence-diagrams/ which also credits yours) was very much in my mind, though my grammer is much less elegant.
Someone else made the same - https://github.com/Paul-Browne/HTMLInclude - but it's not been updated in 7 years, leaving questions. I'll try yours and theirs in due course. Err, and the fragment @HumanOstrich said elsewhere in comments.
I think you're right, it is harder to discuss politics as widely as we once did.
That said, what do you think of money changing what is left/right and group/individual? The outcome of Citizens United to allow obscured spending to create seeming grass roots efforts on any topic that the monied want very effectively moving opinions.
Linked in is a mess, for sure. What I liked from it was verified identities. SoftwareDev-land could maybe make something that was Git backed, extensive and allow for secondary evaluation of the claims made - https://gist.github.com/paul-hammant/3375fec8e204f0c7567d4da.... Perhaps tossing out privacy as it does so :(
I go into the DAG-centric nature of Google's in my video, and that was one of the reasons for making it and the sim repo.
I did at the outset think that the Google way lead to faster builds. It could could be with parallel step execution and a build cache is setup, but I don't think it is significantly different in a vanilla serial mode.
Perhaps there's another benefit - slimming a monorepo to feed to a coding AI, in order to bring down tokens needed for a task.
I've WIP for a C# module, but I'm stuck on some fine-grained setup for 'vstest'. I also asked Google's Jules agent to migrate one of the depended-on modules to Kotlin, and it has been 24 hours now, with it assuring me that it hasn't stalled.
reply