Cincom VisualWorks Smalltalk: doing something useful part 3

I told myself to give up, but after futzing about with Pharo and thinking about VisualWorks, I went back

The Omega Man

That little AWS Browser built in VisualWorks, I just couldn't let it go. I do need something more convenient to tell me things like where the target groups are in my load balancer, what the entries are in the dynamodb tables etc. without having to wade through the AWS website. It's painful (especially digging through the EC2 stuff to find the load balancer target groups). Maybe I dismissed this too early. Trialling the VisualWorks image on my debian box I realised I was constructing the command line arguments wrong, so I fixed that and got this far:

So, it enumerates all the elastic load balancers in that account, enumerates the target groups and then enumerates the target health of the targets within the target group. All by encapsulating the correct commands. Not only does it save me from remembering the commands, it's more convenient than the AWS website. I mean, who in developer land could possibly remember this:

aws elbv2 describe-target-health --target-group-arn "arn:aws:elasticloadbalancing:ap-my-region:555555555555:targetgroup/SmartShepherdDocker-tg/3b3b3b3b3b3b3b"

There is something of logic to the aws cli, but the details of each individual command are frustratingly specific. No matter, it's all encapsulated in the Smalltalk classes.

SHUT UP! Why the hell can't you leave me alone?

What I was really missing was the mode of working, it's just so very different to the write / compile / test cycle you get with something like Java or .NET. I feel like I had forgotten how to Smalltalk but sleeping on it seemed to awaken some old pathways in my creaky brain that gave me a few hints as to what I was doing wrong. So I stopped fighting it. The trick is to think iteratively, don't design too much ahead of time, when patterns emerge, do some refactoring. Tinker, test, throw some things into the Workspace and test the tiny snippets of code. The object structure starts to emerge, so make a super-class and define a pile of "^self subclassResponsibility" methods that give your classes a signature, but also prompt you to make the methods in your subclasses. It rhymes with java or C# programming but the activity of doing it is very different - you're not a slave to the editor and typing a pile of stuff, testing it and then fixing it. You're iterating at a much smaller level.

Is this how it starts? A trip to the laughing academy? No, you silly bastard, it starts with you asking yourself silly questions

In the background I've been trying to find an alternative but suddenly remembering how insanely productive VisualWorks was (when you're in the groove) and that unprecedented cross-platform ability just about floors me. As a tool for building personalised, graphical desktop apps quickly, VisualWorks still has no competition.

Popular posts from this blog

Tailscale ate my network (and I love it)

Image
No matter where you go, there you are If you're like me, you travel occasionally. Access to your office from home, or from an airport lounge, or from a hotel room is paramount to being productive for most of us now. While I had a fairly simple Tailscale setup that got me into my test machines in the office, what I really wanted was to integrate my AWS production VPC into that system. It's surprisingly simple. Tailscale AWS instructions What do you want to do that for? In the "before tailscale" times, if I needed to test against the production AWS resources or connect dBeaver for database maintenance, I would edit the security group to add my IP address, do my testing, edit the security group to remove myself. This is as error prone as it sounds. I quite often forgot to remove my IP address from the allowed addresses, a major potential security risk when you are travelling. Tailscale has an extremely nifty way to get around it: if you run up a small ec2 ins...
Read more

Stupid stunts with WSL2 , Python3 and AWS ECS

Image
Hand rolled CMS system gets a previewer The ongoing process of updating the help system on the SmartShepherd inspired two new features: editing of the html in a temporary location and a small web server to check your work before pushing it to production. The surprise? That GitHub desktop will show you a side-by-side view if you change an image file. Can't believe I didn't notice that before. Can you hold my camel for me? Sometimes I get so far down a dead end I don't realise how many issues could be sorted simply by re-thinking something. The initial deployment of the SmartShepherd web server was to an Elastic Beanstalk setup on AWS, mostly because I had no idea what I was doing. Elastic Beanstalk isn't really one product, it's more of an elaborate script that creates systems for you. In my case, it was spinning up a small Windows EC2 instance, installing the .NET Core website and auto-configuring a load balancer to point to that instance. I mean, it's...
Read more

Time machine: Solaris 2.6 on QEMU

Image
You can never go home A big chunk of my professional career in the 1990s was spent with a Sparcstation on my desk. Before that the 68000 Sun2 and Sun3 floated past my sticky fingers but the Sparc machines quickly superseded those. I don't remember too much about which ones: pretty sure there was at least one IPX, one Sparcstation 5, a Sparcstation 10 and then the last one was most likely an Ultra 1 or maybe even an Ultra 5. It was a long time ago. Every now and again I think about how productive those machines were and do a little Ebay digging on how much one would be worth to have around. Except I don't have the room for more machines and the idea of trying to revive 25 year old hardware from that era is well beyond my electronic capabilities. Never fear, QEMU is here. Following these excellent instructions from Adafruit , you too can install Solaris 2.6 and have your very own emulated machine. Note that there is one instruction in there I am not sure you need. A...
Read more