1,510 karma · joined May 23, 2012
There are solid reasons why Brexit is the darling of the resurgent neofascist movement, and it should all be seen as part of the same picture.
On the other hand, most of the people who I know who voted 'Leave' had poorly disguised (and sometimes completely insane) xenophobic rationale for doing so.
Also - and significantly - racially motivated aggression and hostility toward my (mixed race) family suddenly increased to intolerable levels in the weeks and months following the Brexit vote.
The whole affair has been an undeniable victory for the nastiest sort of hatred, and has demolished the pride I felt in my country as a bastion of reasonableness and tolerance.
Nonetheless -- the world keeps on turning.
Evil may win a battle here and there, but it cannot be allowed to win the war. What these vandals destroy can always be built up anew.
Sadly, I have found myself exceedingly disappointed at the tooling available to support MBSE, having mainly used Simulink, and also experimented with a few others like Rhapsody, Capella and EA.
Constant mouse usage with Simulink gave me really bad RSI, and merging models was a pain, due to the way that layout and structural information were mixed together in the xml-based .mdl file format.
So (naturally) I made a text-based alternative. It's a bit like TensorFlow in that you create a compute graph (computational model), and then run it.
The model itself can be generated dynamically in a script, using JQuery-like syntax to add or change nodes, or alternatively it can be stored and version controlled in one or more text files, using YAML, XML, JSON or TOML (or some mixture of those) to serialise the structure in an easy-to-diff-and-merge form.
My world view is not even remotely 'left wing', and yet I have no difficulty whatsoever in detecting neofascist propaganda. It's really not that hard, and yet it's prevalence seems to be driving us to the brink of chaos.
Personally though, I'd introduce another intermediate set of names - like 'color-brand-primary', 'color-brand-secondary' etc... so you can make branding changes more easily. The majority of Tailwind can be used as-is though.
Munging these tools together has let me create my own 'distributed back end framework', so I can define back-end logic and front-end logic in the same place, but have the back-end logic run on whichever machine I choose, so e.g. an edge device can send a fragment of UI to a monitoring dashboard.
It's all rather nice and I'm very pleased with myself. :-)
I use it in combination with Python dominate and tailwind.css to write UI components that I can just plug together in a dataflow model at the back-end, and so far it's working amazingly well ... it's well on it's way to becoming a no-code application and UI framework..
Free speech isn't free. It's a responsibility, and we should take care to fulfil that responsibility with caution and diligence.
This, to me, feels very very similar to a model-based approach, where the outermost level is a modeling framework that does nothing more than route data between different functional components and IO components.
I have a strong hunch that this outermost layer does not need to consist of anything more than a suitable framework plus some configuration data specifying (a) the mapping from functional components to hardware resources and (b) the data flow between functional components.
If this is indeed the case, then, extracting individual components or subsets of the system for testing should simply be a matter of providing a suitable transformation of the configuration data, and re-executing the framework.
I have also in the past found myself being led by a deeply unethical individual, resulting (along with everyone else in the organization) in the difficult situation where we have had to collectively somehow drag the organization back out from under the lies (and perhaps fraud) committed by that single unethical leader.
This is a serious issue, and not something that we should take lightly. Not only have I experienced serious health repercussions from this episode in my life, but I have also seen other victims within the organization suffer emotional and psychological problems over the following years.
Creating a functioning, productive and healthy organization is such a critical activity - for all of us. It is something which by now we should know how to approach systematically and reliably, and yet I don't yet see (or perhaps am simply not aware) of a state-of-the art approach to this, or even a useful set of metrics by which we can judge success.
Our digital infrastructure is ludicrously insecure and open to abuse. The stable door is wide open, and has been for over a decade.