Screenshot from "What's New in IntelliJ IDEA 2022.3" |
Screenshot from "What's New in IntelliJ IDEA 2022.3" |
To always show all system tray icons in Windows 11:
Open the Run prompt (Win+R) and execute the following nonsense:
explorer shell:::{05d7b0f4-2121-4eff-bf6b-ed3f69b894d9}
In the dialog that appears, there will be a checkbox to always show all icons and notifications on the taskbar.
Original source of information: TheWindowsClub
<rant-mode>
I am one of those people who choose to publish their ideas on a blog.
The practical reason behind doing this is so that in a conversation I can refer my interlocutor to a text which elucidates my points better than I could conversationally. Admittedly, the opportunity to do this does not arise as often as I wish it did, and even when it does happen, about half the time the interlocutor appears to be reluctant to go and actually read the post, so let's just say that I publish my ideas mainly because I like doing it.
A new method for Automated Software Testing is presented as an alternative to Unit Testing. The new method retains the benefit of Unit Testing, which is Defect Localization, but eliminates the need for mocking, thus greatly lessening the effort of writing and maintaining tests.
What are fakes, what are their benefits, and why they are uncontestably preferable over mocks. Also, how to create fakes if needed.
Games industry veteran Mike Acton gave talk/rant at GDC (Game Developers' Conference) 2019 where he listed 50 things he expects of developers: https://www.youtube.com/watch?v=cV5HArLYajE This list was transcribed by Adam Johnson and posted here: https://adamj.eu/tech/2022/06/17/mike-actons-expectations-of-professional-software-engineers/ and I am copying it here for posterity.
I found this list useful as reference material; some of the items on this list do not apply to my job because I rarely do anything especially performance-oriented nowadays, and some of the items on the list are good to always have in mind but subject to the programmer's own judgement, on a case by case basis, whether they should be practiced or not.
Here it is:
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.