Apropos of...

You have to love method names in stack traces “invokeExplosively” has to be a new favourite (and a reason why I limit myself to simple 4 letter names in my code).

Tradfi coder by day, hacker by night. Doesn’t know night from day. Freelance scribe. Dad cook. Dog butler.  Happy Grandpa. Draws badly.

Building /bright-moments - minting onchain art IRL | /purple #15 | FID 129 #magikarp

You open things and shut things. Save view read edit junk swap list etc. it’s a vocabulary. All coding is repetitive. I only use real names in business vocabulary. I use three letter words when they make sense. Get put add all len del.

I could go on. Everything is a part; parts have defined interfaces and are always independent. Plugs integrate parts to the outside system and each other. Parts are assembled into functional units. I am open sourcing the framework at some stage. I’ve done it in Java and rust but I’m sticking with Java at the moment as I prefer the reflection system and memory management for this task.

can you give us an example of our last ten four-letter variable names?

do you ever have to contort yourself to make the four-letter constraint work?