13 private links
D2 is a domain-specific language (DSL) that stands for Declarative Diagramming.
D2's long-term goal is to significantly reduce the amount of time and effort it takes to create and maintain high-quality diagrams for every software team.
"a modern alternative to graphViz"
Rust for Perl programmers
Having to know everything at once makes it hard to teach Rust as well. It seems like no matter where we start, we are always touching on concepts that we haven't covered yet. This is quite the opposite of Perl, where it's fairly easy to learn as we go. But perhaps making this one assumption--- that we all know Perl--- will help us navigate the complexities of Rust. I don't know if this is going to work, but I thought I'd try it.
There are a lot of topics in software engineering that are the result of accumulated intuition over decades. But we've had a pretty good definition of abstraction since 1977, originally in the context of program analysis, and — I claim — it actually translates quite well into a precise definition of “abstraction” in engineering.
...just not all the other things that programmers tend to throw the word "abstraction" at
GitHub - azet/community_bash_style_guide: Community Bash Style Guide: writing useful and modern bash scripts, seriously.
Community Bash Style Guide: writing useful and modern bash scripts, seriously. - GitHub - azet
One day, while studying old code, I found out that it's possible to encode Windows Portable Executable files as a UNIX Sixth Edition shell script, due to the fact that the Thompson Shell didn't use a shebang line. Once I realized it's possible to create a synthesis of the binary formats being used by Unix, Windows, and MacOS, I couldn't resist the temptation of making it a reality
binary releases of VS Code without MS branding
People do, of course, design object-oriented programs, and they do so successfully. But they do so by mapping them onto procedures. A use case document recognisable by Ivar Jacobson lists the steps taken by the user to achieve a goal, and documents the flow of data through the system. This being too wordy and not Agile™ enough, it is replaced by the user story, but what is a story other than a sequential description of events with a beginning, a middle, and an end