Not sure what the practical difference is (24/7 vs ~10/5) except for the convenience when planning data migrations if you have regularly planned downtime.
For most code changes being turned off at night isn't much of an advantage, as the new code will need to go live at some point and that point is where the risk is. For systems on 24/7 you simply need a copy of your production environment to test on, a.k.a. staging.
The main thing about 24/7 is needing follow-sun SRE and/or out of hours oncall.
You say this as if the LLM isn’t committing things it doesn’t even recognize as bugs if you don’t babysit it. I’d rather have a codebase with a few very well marked evil zones, rather than a codebase no one has read. All code contains demons and it’s good to have an understanding of their locations and relative power
I do some light juggling adjacent activity, and I think it's absolutely improved coordination in other ways. When things randomly fall unexpectedly now I feel like my hands snap out and catch them so much more deftly than before. And with a crawling baby in my life now, I'm often catching them as well.
Greatest pride was catching a tumbling beer at a party, and getting called spider-man.
Getting good at juggling makes things fall down noticeably slower. But despite getting really good at juggling, I haven't observed any other super powers.
I know mine sure did! As a kid I was totally uncoordinated, always the last one to be picked for any sports teams. But I definitely noticed the difference when I picked up juggling as a young adult.
It isn't worth the time. I am not going to read the 200k LOC to prove it was a bad idea to generate that much code in a short time and ship it to production. It is on the vibe coder to prove it is. And if it is just tweets being exchanged, and I want to judge someone who is boasting about LOC and aiming to make more LOC/second. Yep I'll judge 'em. It is stupid.
"Property" here comes from mathematics (and I guess similar definition to science). What are the properties of this function? E.g. x * y has the property that x * y = y * x.
So we do import stuff from Mathematics alot.
I think we need better tutorials. It is a hard problem. How to teach something, who is your audience. For an AI tutorial, do I need to explain what inference is? Maybe. If I don't and they don't know it is another weird word.
In terms of brain problem - I have the same thing. It is worse inside the corporate barrier as there is no internet documentation on what the terms mean. I think all we can do is slow down and write cheat sheets until we remember.
There are lots of stipends etc. If you don't plan to have kids, and you don't care about luxuries, you will have healthy food and a roof and not be thinking about money. Probably the decision is to forgo luxuries and child raising, and hope you don't need to help a sick relative etc. if you want do to this forever. But it is not impossible in STEM.
I'd go the other way. Have less stuff. Just a text box, markdown, insane support for mermaid and everything. Dump the "blocks" of wordpress etc. Too confusing and fiddly. Maybe have AI assist to help with styling the rendered page a bit.
Here what Matt said:
"The closest thing I’ve seen to a spiritual successor isn’t another CMS, it’s been OpenClaw.”
He's saying "the spiritual successor to WordPress won't be a CMS at all, it'll be something in a different category entirely. Or he lets his emotion get better of him.
For most code changes being turned off at night isn't much of an advantage, as the new code will need to go live at some point and that point is where the risk is. For systems on 24/7 you simply need a copy of your production environment to test on, a.k.a. staging.
The main thing about 24/7 is needing follow-sun SRE and/or out of hours oncall.