A need is identified and a solution is proposed for a novel set of software tools to facilitate the visual composition of technical software design documents as schematic diagrams consisting of predefined software components, and the automatic deployment of runnable software systems from such design documents.
|
| The logo from Visio version 1.0 |
This post is intended as support material for another post of mine; see michael.gr - The Deployable Design Document.
One day back in the early nineties, when people were using Windows 3.0 and programming with the Microsoft C/C++ Compiler, a colleague showed me a software design that for the first time he had done not on whiteboard, nor on paper, but on a computer screen, using a new drawing tool called Visio.
He showed me interconnected components laid out on a canvas, and as he moved one of the components, the drawing tool re-routed the lines to maintain the connections to other components. This meant that Visio was not just a pixel drawing utility like Microsoft Paint; it had some understanding of the structure of the information that was being displayed.
 |
| Logos of various visual programming languages |
This post is intended as support material for another post of mine; see michael.gr - The Deployable Design Document.
The idea of creating software using visual tools has existed ever since the first aspiring programmer was bitterly disillusioned by discovering that programming almost exclusively entails writing lots of little text files containing nothing but boring and cryptic text.
 |
| The UML logo, by Object Management Group®, Inc. from uml.org; Public Domain. |
This post is intended as support material for another post of mine; see michael.gr - The Deployable Design Document.
It has miserably failed.
|
| "Dutch Tongue" by michael.gr, based on the logo of The Rolling Stones. |
"I will learn you how to skate." ("Learn" instead of "Teach".)
"When you want, we also have it in white." ("When" instead of "If".)
"Let's meet at sex." ("Sex" instead of "Six".)
"Dear colleagues, hereby the schedule." ("Hereby" instead of "Here is" or "Hereby I give you".)
"We have lot's of bicycle's" (Genitive instead of plural suffix.)
"Meet you at the busstop" (Concatenating words that are not concatenated in English.)
"Let's have a telco" ("Telco", which means "telecommunications company", instead of "Teleconference".)
Object-adjective instead of adjective-object. ("Emergency exit train driver" instead of "Train driver emergency exit".)
 |
| A sign that you can find inside virtually every single train in the entire Kingdom of The Netherlands. The English translation is urging us to not block the driver of the emergency exit train. |
"I am a cineville" ("cineville" instead of "cinephille") -- there is even a .nl domain misspelled this way.
Also: Dutch pronunciation rules cause some really weird phenomena, for example when you call Vodafone, the recorded greeting informs you that you have reached "Fodavone".
|
| "Coding Software Running On A Computer Monitor" by Scopio from NounProject.com |
My thoughts and notes on how I would like a new programming language to look like.
The goals of the language are:
I knew I was definitely going to watch this one, from just the title. It turns out that he comes across a bit annoying due to attitude; nonetheless, the talk is definitely worth watching.
|
|
The Bathyscaphe logo, a line drawing of
bathyscaphe Trieste
by Mike Nakis, based on art found at
bertrandpiccard.com
|
This article introduces Bathyscaphe, an open-source java library that you can use to assert that your objects are immutable and/or thread-safe.
Programmers all over the world are embracing immutability more and more; however, mutation is still a thing, and in all likelihood will continue being a thing for as long as there will be programmers. In a world where both mutable and immutable objects exist side by side, there is often a need to ascertain that an object is of the immutable variety before proceeding to use it for certain purposes. For example, when an object is used as a key in a hash map, it better be immutable, or else the hash code of the key may change, causing the map to severely malfunction.
Quite often, when I rename a maven module, IntellijIdea gets confused and keeps showing the old module name in the project view.
I discovered that this is happening because:
The solution I have found to this problem is:
