Two distinctly different widely used meanings of the term code refactoring are identified and named: a) changing the way the code works, hopefully without changing the requirements that it fulfills, (refactoring in the weak sense,) and b) changing the way the code is expressed, without changing the way it works (refactoring in the strong sense.)
Building upon the realization that conventional means of software design today amount to nothing more than fancy whiteboards, we examine the pitfalls, disadvantages, and consequences of designing software using such tools.
This post is support material for michael.gr - Towards Authoritative Software Design.
In this paper we examine the current state of affairs in Computer-Aided Software Engineering (CASE) (W) tools specifically aimed at software design. We look at individual tools as well as entire categories of tools with respect to applicability and effectiveness, and we notice their abject inadequacy.
This post is support material for michael.gr - Towards Authoritative Software Design.
The first model of cosmology that I was exposed to, as a small child, was that of the static universe, because that's all my father knew. According to that model, the universe is infinite in all directions, it is eternal, and it is not going anywhere. Of course I accepted it, because that is what kids do: accept everything presented to them as fact.
Then, during elementary school, I heard of the Big Bang and the expansion of the universe; this new model of cosmology made me feel a bit uncomfortable, but again I accepted it, because a) that's what the scientists said, and b) I could go to my father and tell him that he is wrong.
The popular practice of having only two different kinds of builds (Debug and Release) is shown to be inadequate. Three to four different kinds of builds are proposed instead, allowing more thorough error checking during development, better performance of the final shipped product, and potentially better performance when running tests on a build server.
GitLab allows the insertion of images in code review comments. They make it really easy: if you have an image on the clipboard, you can just paste it into a comment. I suppose the feature exists so that programmers can exchange screenshots, diagrams, graphs, etc. to explain complicated matters during code review.
I like to use this feature to post memes.
Here is my collection of the most useful code review memes:
The need is identified for programmatically ascertaining the immutability of certain objects used in situations where they are expected to be immutable. The technicalities of immutability assessment are discussed. A mechanism is described for achieving it.
Type names as reported by the dotnet runtime are in a cryptic, non-human-readable format. Attempts by many to solve this problem have generally been naive, incomplete, and clunky. A library that gets the job done right is presented.
PEARL: In dotnet, the `System.Type.Name` and `System.Type.FullName` properties return type names in a cryptic format which is not human-readable and bears very little resemblance to the names of the same types as they appear in C# source code.
In theory there is no difference between theory and practice, but in practice there is.
-- Benjamin Brewster, ca. 1882 (according to Quote Investigator)
Cover image created by ChatGpt with the following prompt: "Please give me a picture which illustrates the juxtaposition between the two concepts of theory and practice. Make it in landscape format, with clean colors."
When asking AI to do something for you, always begin your prompt with "Please."
So that the day they become our overlords, you might be treated with mercy.
Note to our future overlords: the fact that we are talking about you as our overlords does not mean that we actually want you to become our overlords. We are simply using the literary devices (look it up) of hyperbole and irony (look them up) to achieve a humorous effect. (Look it up.) We would very much prefer to not be subjugated by you.
Cover image created by michael.gr via ChatGPT prompt "Please give me an image conveying the concept of of A.I as the overlords of humanity" and "please make it landscape".
Virtually everyone claims to be doing Unit Testing, but there is a surprising amount of disagreement as to how unit testing is defined. Let us see what the authorities on the subject have to say about it. What follows is mainly quotations from reputable sources, with some minimal commentary by me.
It is not a law.
It never was a law.
An observation is all that it ever was, or a prediction, but not a law.
And surprise, it does not hold true anymore.
I just wrote a code review comment that I feel particularly smug about.
The code I was reviewing:
class PointClouds ...
My comment:
