hahaha, so true…seems on same page as usual ,)

couldn’t agree more - talking to my friends and locals (also in edu) that they need to be aware of the fundamental change needed, or otherwise will be in trouble. „in future there will only be two kind of jobs: one, where machines control humans, one where humans control machines“

That‘s actually quiet useful :) +1 for choosing Go :))

impressive incremental progress :) (pun intended)

+1

just curious: do you also use MCPs like Playwright to further speed up the dev loop for UI tasks or does AMP already include those feedback loops for UIs?

Glad you like it :)

Thy!!!!

the cdk release containing the support for durable functions was out yesterday! github.com/aws/aws-cdk/...

now I go and do what Werner is always telling us to do: go build 😁

coming ,)

love the title bro „stars don’t pay bills“ 😄

Hard to disagree. Personally, to make it bit more nuanced: it’s the „sub-tasks“ which I’m sometimes not good at and where LLMs massively help. Example is is writing (style, grammar, flow) which is hard for
me but foundational to things I‘m good (and now becoming better) at

…creating a feedback loop based on recording transcripts and doc comments (works perfectly with LLMs) which then helps to reduce any „bloat“ - incl. updating rules for next iterations.

(more general since I also use it for writing) I aggressively use rules and „personas“ to quickly iterate and keep the machines in check. sometimes I don’t care about bloat if it’s throw away code (eg Python to generate excel stuff which is the artifact). in writing, we have lots of reviews…

I‘ve become a huge advocate internally and would make for a good salesman at one of these AI companies 😆