Cool. Can you tell us a bit more about the technical process of porting the TS code over to Go? Are you using any kind of automation or translation?

Personally, I've found Copilot to be surprisingly effective at translating Python code over to structurally similar Go code.

    Q:  How many Pentium designers does it take to screw in a light
        bulb?
    A:  1.99904274017, but that's close enough for non-technical
        people.

    Q:  What do you get when you cross a Pentium PC with a  research
        grant?
    A:  A mad scientist.

    Q:  What's another name for the "Intel Inside" sticker they put 
        on Pentiums?
    A:  The warning label.

    Q:  What do you call a series of FDIV instructions on a Pentium?
    A:  Successive approximations.

    Q:  Complete the following word analogy:  Add is to Subtract as 
        Multiply is to:

                    1)  Divide
                    2)  ROUND
                    3)  RANDOM
                    4)  On a Pentium, all of the above
    A:  Number 4.

    Q:  Why didn't Intel call the Pentium the 586?
    A:  Because they added 486 and 100 on the first Pentium and got
        585.999983605.

    Q:  According to Intel, the Pentium conforms to the IEEE 
        standards 754 and 854 for floating point arithmetic. 
        If you fly in aircraft designed using a Pentium, what is the
        correct pronunciation of "IEEE"?
    A:  Aaaaaaaiiiiiiiiieeeeeeeeeeeee!

    TOP TEN NEW INTEL SLOGANS FOR THE PENTIUM
    -------------------------------------------

    9.9999973251   It's a FLAW, Dammit, not a Bug
    8.9999163362   It's Close Enough, We Say So
    7.9999414610   Nearly 300 Correct Opcodes
    6.9999831538   You Don't Need to Know What's Inside
    5.9999835137   Redefining the PC -- and Mathematics As Well
    4.9999999021   We Fixed It, Really
    3.9998245917   Division Considered Harmful - No Life-
                    Maintenance Devices Should Be Used With This
                    Processor
    2.9991523619   Why Do You Think They Call It *Floating* Point?
    1.9999103517   We're Looking for a Few Good Flaws

    And the 0.9999999998th Slogan Is...
                                    The Errata Inside

A manager can start work on this kind of culture shift without even saying the word "agile". They need to give their teams more trust and room to govern themselves. i.e. managers need to get out of the way. When a team is open to the idea of Agile or scrum, then the manager could ask the team if they would like training or coaching. But the ground has to be made fertile first.

The Agile industrial complex can't really sell a message to their customers (i.e. managers) that the development teams should have the power and run themselves how they feel fit. This message amounts to "if this works, we can fire the managers". Not a popular message for managers.

So, instead of building on an agile foundation, companies just add some story points and funny sounding meetings on top of the old structure and nothing really changes. It is Agile cosplay.

The terminal VSCode has been picking up on these kinds of features lately. Now they can even "sticky" the previous command line at the top of the window when scrolling through long output.

It has taken a long time, but these ideas are slowing spreading around.

For Facebook is would be either 2% of the firm’s worldwide annual revenue from the preceding financial year, or 4% of said revenue.

A bit bigger than a rounding error.