I feel like every cloud build meeting should have a moment where everyone has to defend the question "Wait! could this be a regular database with a regular app on a server with a regular cache?"
It would be great if they had a version of this where you had to progress through sampling soil, union negotiations, working with city planners, and then the actual digging with all the delays of machinery, strikes, planning issues, NIMBY's and such.
People of course often do read (and even modify) the model-generated code, but doing so is specifically not “vibe coding” according to the original definition, which was not meant to encompass “any programming with an LLM” but something much more specific: https://simonwillison.net/2025/Mar/19/vibe-coding/
The whole point of the term is to convey that you are only looking at the output and not looking under the hood. If vibe coding a UI, you only look at the UI, not the CSS.
> The developer does not review or edit the code, but solely uses tools and execution results to evaluate it and asks the LLM for improvements. Unlike traditional AI-assisted coding or pair programming, the human developer avoids examination of the code, accepts AI-suggested completions without human review, and focuses more on iterative experimentation than code correctness or structure.
So the real risk with that data center is the fact that Tasmania is a culdesac on the internet. We have three fiber cables coming to the island, all from Victoria (directly to the north). The whole state has lost internet before due to someone in Victoria digging a trench through the cable (yes a silly mistake but we're all humans).
It's not a bad idea to put data centers here, but we really need a few more links out to the world from here.
Taking an idea, and converting it into code is a lot of work. Taking that same idea and then taking the code and turning the both into words that can communicate the original idea is just another complex task.
I'd wager that the dopamine hit of getting stuff working has worn off and most people are writing doco when they're exhausted from their recent work.
No, s3 objects should always be private and then have a cloudfront proxy in front of them at the least. You should always have people hitting a cache for things like images.
This should exist and the class should study openssl.
reply