centuryfall

Docker is great. I entered into the post-Docker era (mid 2010s) and it is amazing how much sense it makes to imagine Docker as like a single task “mini computer”. I appreciate the insights of this article a ton: I feel after getting used to Docker, we take it for granted, but it’s great to see how someone junior to it would react.

Is there a reason why the menu on that website also has an icon for every item?

This same statement has been said countless times, replacing “AI” with whatever trend is big at the time. It has also been wrong in every case where that thing is said to replace QA.

I don’t doubt that there is technical feat and prowess in being able to do it, and if this satisfies your vision, then you were able to contract an AI agent to do in full, but it is still a layer away from the personal effects of art done by one’s self. I just feel that this still leans more towards some new type of commission.

But largely more is this is a display of how we as people view what AI _seems_ capable of, and how we aren’t being fully aware of what actually has been accomplished. I appreciate the willingness to put this out for the world to see, criticism or not, yet if this is a reflection of how you want your website to be perceived, then having it in a ready, working state tells me how carefully you coordinated the effort. Right now, it just feels reinforces the narrative that work with AI has lost a large sense of quality, even if in this case, it didn’t handle that part. I suppose I expected the article to be something different, but that is on me.

Besides the About page and this one blog post, all other links on the site are broken. There’s no need to feel defeat.

> pointing out differences between the thing I worked on for 24 hours and a room designed painstakingly by hand over weeks.

I went in expecting something handmade, and instead got something that was Claude-made. This doesn’t make me feel good, or feel user-centric. Now we’re throwing Blender into a webpage and serving it client-side rendered to users?

If anything, all of this feels more like bloat rather than something personal. It’s art for Claude’s sake. It’s not telling a story. Even on the actual blog post, the dropdown table of contents displays how long it takes to read each section. It feels so disconnected because it’s possible to throw a feature in, but is it really necessary? Maybe I am getting better at determining AI-made UIs, but all of this feels incredibly artificial.

Lastly, for all of the parallel QA checks and threads, all of the header links besides the “About” page throw a 404 at me. It’s almost ironic.

It’s really not ignorant at all when a large majority of these changes go untested.

Better at what?

I’m not understanding how websockets fixes the issue of pushing JSON to the client side for it to be rendered into HTML. JSON is just a data object can translate into text to place in the HTML document.

Moving this to the backend with a templating engine still requires a formatted object, correct? I like SSR rendering, but I think the diagram with websockets is missing a key step, where the database results still need transformed into a consumable format that gets plugged into the templating engine. That step can’t get eliminated with either model.

Regardless of where the document is built, it needs to consume some format of structured data. Am I missing something?

On a side note, this is possibly the prettiest dev landing page I have ever seen.

By chance is it the one in Asheville, NC?

> Lowering the barrier to entry for writing code and other tasks feels democratizing

It really isn’t doing any of that, though. When AI gets it wrong, that person needs to understand why it is wrong, and without that upfront knowledge or skill of reasoning, it’s much less direct to actually build something in the correct ways.