I’ve used vim for a long time without using most of the features (code folding, split pane, status line, etc.). This cheatsheet of commands and keyboard shortcuts will help me explore my options more.
He develops a type of friendship with the dead body and discovers that he can manipulate the cadaver like a Swiss Army knife.
Just watched Swiss Army Man on Netflix. One of the most original movies I have seen in a very long time. The subject matter is … awkward, as is describing the film in almost any way that does it justice.
there are foundational principles and patterns of organization that are relevant to any professional who must convey technical information in writing, and you can adapt these concepts to bring order out of chaos
For later study.
I like the mystery person reflected in the door. Our photographer?
The idea is that you can read chapters of this book, discuss them, try the exercises in the book, ask and answer questions, and maybe team up to create software that implements some of the ideas.
I downloaded a free book about applied category theory (293 pgs) and emailed the PDF to my Kindle for later study. I honestly don’t know what I’m getting into, but this could be a nice change of pace back to non-fiction reading (I read a lot). There is an online forum there at the link and some open lectures by one of my nerd-heroes, John Baez. If you like physics & maths, you may like this too!
“Is base17 a g00d1dea?”
Some 4500 words after I decided to add a few comments and insights ... it’s a good idea to consider what happens when follow a handful rather simple and obvious rules of how to write code.
Erik Torsner articulates his authoring of a production-ready-but-not-really WordPress plugin which reproduces the output of Matt Mullenweg’s commonplace Hello Dolly, while demonstrating and justifying his practical choices in software construction and testing; a wonderful example for others to consider and leverage.
Eight hundred years have passed and Earth is nothing like they thought it would be.
… concerned not just with the packaging of data (syntax), but the simultaneous transmission of the meaning with the data (semantics).
When elements from independent systems of semantic interoperability appear within the same document, the semantic compatibility of the independent systems is the measure of their non-interference.
HTML and CSS have very good semantic compatibility, often appearing together in the same document.
This is on my mind lately as I consider the compatibility of web application sources with microformats, while building a utility to help identify any aspects of the web application sources which interfere with the desired interoperability embodied by microformats.
I currently describe my pre-release project as: “A utility which checks webapp sources for compatibility with microformats semantics”. Based on the foregoing, I’m considering changing the description a little. At the end of the day, the work is the program that helps find the issues in the code. I’m hopeful that someone with greater comfort discussing the topic will help me to gain some confidence in how I present the program. So long as it is providing some useful and desired outcome, I’ll be working on it for awhile longer. Hopefully work to benefit more than myself!