HN user

discodachshund

31 karma
Posts1
Comments16
View on HN

This is a point I've been discussing for a while but never to my knowledge gets brought up in the mainstream Trident debates.

Another point is the two test failures in a row recently.

Regardless of the stance on whether we should spend so much on Trident I think most would agree if we are spending we want it to work, and be able to maintain it ourselves.

I get the points about not needing a formalised system for diagrams, even if C4 is quite light touch in my opinion (I never go down to the code level).

However, I do have to credit structurizr, which outputs C4 diagrams, as a great productivity boost. One model producing multiple views at all specificities is fantastic compared to mermaid, plantuml, etc, where every diagram needs to be self contained and define and redefine the same components over and over. Branching off, editing the model, presenting ideas, has been a very successful workflow for me.

I have never tried a TRX and good luck on your journey.

I would like to add for others, you can go from 0 to pull-ups with just a bar, which I imagine is much cheaper too. I certainly did and my fitness level was minimal.

It's a case of progressions. For instance starting with negative pull-ups:

- Use a stool or just jump to the top position of a pull up

- lower yourself down with control, as slow as you can. At first this might be 1 second!

- Repeat for sets and reps

- when you hit 3 sets of 8 reps, slow down your descent another second or two

- Repeat until you've built up to 10 second reps, 3x8

At that point you should have the strength to be able to do a pull-up. You may need to ease into the technique, if so, introduce a resistance band to help train the motion, and gradually reduce your dependency on it.

Sadly the effect system isn't granular to narrow down what effect is happening other than "IO", which could be logging, network, disk access, rm -rf /. And without that visibility it doesn't provide you much advantage.

Haskell similarly suffers, I'd like to see IO broken down into composable units of functionality so I can see if e.g. my logging library has some ridiculous network constraint.

You might enjoy a language with refinement types. I know Scala has a library for this called refined, which I believe is a port from Haskell.

In summary it gives you compile time feedback on types with refinements, e.g. positive ints, negative ints, even ints, etc, and can be based on custom predicates.