Billy Pilger

Merge Sort is an efficient sorting algorithm that recursively divides an unsorted list, sorts the individual segments, and merges them to produce a fully sorted list

Visualizing recursive merge sort with a recursive sequence diagram: app.ilograph.com/demo.ilograph.…

linkedin.com/company/ilogra… bsky.app/profile/ilogra…

@fetrigon Hi, thanks for this feedback. It is possible to set the detail on a step to low (say, 0.001) and select/highlight the nodes you like. I'll have a think if the opposite, choosing resources to "hide" in a step, would work.

@ilographs It would be nice to be able to obscure some details for each step, without changing the layout, during walkthroughs.

High-detail architecture diagrams:

What kind of system architecture diagrams can AI generate? ilograph.com/blog/posts/dia…

@iavins I created an ilograph tour: @mikestaub/atprotocol%2520overview/Protocol%2520Overview/_walkthrough/1" target="_blank" rel="nofollow noopener">app.ilograph.com/@mikestaub/atp…

Ilograph 1.8.4 (all environments) is a small update that adds scroll bars to resource descriptions when they get long.

Spent this week deep-diving into the atproto.com source code. This is the first decentralized protocol I've ever seen that has a chance of scaling to billions of users. Very exciting stuff! #programming #tech #startups @mikestaub/atprotocol%2520overview/Protocol%2520Overview/_walkthrough/1" target="_blank" rel="nofollow noopener">app.ilograph.com/@mikestaub/atp…

@swedishsouthpaw Sure thing, let me know how it goes. No immediate plans. I did experiment with sub-sequences that could be collapsed/folded, but it conflicted a bit with selecting and focusing on resources. I'll have a think on revisiting it 😀

@ilographs Thanks for the reply! I’ll try your suggestion :) Any plans for something more tailored?

@ilographs Hey! How would you handle conditional flows in a sequence diagram?

@swedishsouthpaw - If not, try using combinations of "restartAt" and "color" to differentiate the two paths. Color one path, say, blue, then use "restartAt", and write the next path in, say, red. - "toAsync" would also be handy for one-time conditional calls

@swedishsouthpaw Howdy, good question! There isn't specific mechanism for this in the language itself. Thinking on it, here is what I'd do: - If the two (or more) paths are important and/or differentiated enough, then putting them in their own perspectives. (🧵)

In system architecture diagrams, arrows are just as important as boxes. Ilograph 1.8.1 (all environments) adds markdown support for arrow descriptions, so you can show all the details about how your systems interact:

Ilograph 1.7.9 (all environments) is a small maintenance release that fixes arrows not rendering fully in some edge cases.

New wordmark... can you spot the difference 😅

Ilograph 1.7.8 (all environments) adds a foil effect to selected resources:

Before and after: new arrow rendering on Ilograph

Happy diagramming! Please let me know if you see any issues with the new arrow layouts.

Previously, these arrows would “jump” over resources that were in their way. The result was not always very pleasing:

Ilograph 1.7.6 (all environments) is an exciting new release that updates how arrows are rendered. When space permits, arrows will now route around other resources: