One important difference between animations/videos generated by Opus 5.5 and the stereotypical AI slop videos is that Opus 5.5 is not a video generation model: it generates and iterates the code and renders it, and there are various ways for it to do so.
This one's been stuck in my head since yesterday. I just keep thinking about how long this woulda taken in After Effects. So I was experimenting with having Opus 5.5 make these kinda animations in javascript and realized I can get it to export a JSX script for AE. So I can have it take the first swing, then bring it into the tool I actually use.
At this point I'm wary of seeing something from the "bearblog" domain on an HN submission because it always end up being the same thing despite hosting different authors.
By construction, a personal blog is very likely to break unexpectedly compared to other types of vibecoded projects because a) the scope is very narrow and b) there is only one user.
I recently redesigned my own blog (https://minimaxir.com) during some experiments into how well modern LLMs can be conditioned into not outputting the stereotypical telltale designs of web vibecoded slop; it worked well enough (although more difficult than expected) and "how to design a website using agents that doesn't look like an agent made it" might be a fun topic for a blog post as there were a few gotchas.
The main reason I did the redesign is because my blog is running Hugo + PaperMod theme, which is becoming too popular and it makes blogs no longer stand out. There were also a few features/shortcodes I wanted added (better video support, better sidenote support, etc) that give me more tools for blogging.
How is your site not an example of your stereotypical web design? No unique design choices, no unique color palettes, just one single column for content with massive amounts of white space; it looks like any other generic dev blog.
Stereotypical modifies "vibecoded slop", not web design in general. As someone who has worked with blog coding for over a decade and attempted to actually do unique design choices, it is a generally bad idea to do so unless you have both a) a good design sense and b) analytics to test such that your unique designs don't actually make things worse. Blogs have converged to a one-column layout for a reason.
Nope. There's some truth in the contents of this article that anyone can read for themselves that any verifiable task that can be measured, Claude can optimize. Unironically, rewrites become more approachable and cheaper with a rewarding speed up if you know what you're doing; but not done all at once.
So there's no need to get upset about that simple joke like the last time, and also complaining about comments being "Reddit-esque" which that breaks the HN guidelines [0].
Lastly, you forgot to tell off another user who made the same joke today. [1]
I am not "complaining that a comment is Reddit-esque", just giving an explanation to the user why your comment may have been downvoted (nor is that what the guideline you are referencing says). If you said "at this point it would make more sense to rewrite Claude Code in Rust that fix all the tech debt", or even better your first paragraph in your comment, that would be perfectly reasonable and likely upvoted significantly.
I didn't bring up the previous incident because it wasn't relevant, but since you did, this joke is a really really weird low-effort hill to quintiple down on when you were downvoted on it last time and are clearly capable of providing good insight.
That user in your link in a completely different thread added a more relevant followup to their comment, it wasn't solely the joke (it's not a comment I'd upvote, but it actively contributes to the discussion).
This writeup legit coincidentally matches the asking-agents-to-make-code-faster-but-with-constraints-to-stop-agents-from-breaking-things writeup I posted on Monday: https://news.ycombinator.com/item?id=49803085
Front-end UI optimization is slightly trickier than optimizing strict algorithms, but I found that prompts to the agents to build tooling to track visual regressions are more than sufficient. The main issue (at least with GPT models) is that you have to be very explicit about the use of padding/margins/negative space.
That said, for my front end projects from scratch, I'm staying away from front-end JS frameworks and seeing how far and fast I can get with just HTML/CSS/vanilla JS shenanigans now that agents can wield them effectively.
I was building web apps like this until 2017 when I entered the React + Typescript world. For B2B you can get pretty far, rendering HTML on the server is fast! I was using Rails on the backend, so templates, partials, shared chunks, made it easy to manage and have a consistent UI without repeating too much.
The hard part is when you then need to build an infinite scrollable table, that has bulk select, and in-placs updating of columns. Ok maybe that's a bit too extreme the other way, but when you get to the point where it's easier to build full-on frontend components, you basically have to use a JavaScript framework for your entire UI. And they are basically all or nothing.
Last time I checked (a good few years ago; I gave up and accepted un-optimized frontends as the rule) there wasn't really a good way to do progressive ehancement like the above: the page rendered on the server as HTML, and some components then become fully frontend managed. And no, frameworks like Stimulus and HTMX don't really solve it for me, I want something declarative.
I'm a bit pissed off with DHH, that he went so far in the anti-Javascript direction, as IMO that was one of the big factors in Rails loosing it's limelight status. For backend I still haven't found anything as easy and fun to work with.
That's extremely untrue, look at thread about AI/models with showdead and you'll see tons of flagged low-effort comments (in both pro and anti-AI directions)
Flags having a stronger influence than upvoting is a necessary algorithmic check against genuinely bad behavior/brigading, not disagreement. In general it works as intended, which is the best you can do without something potentially worse.
Are there any stats available on the weighting ratios such as flags to upvotes, likes and comments per post after flagging, average time to frontpage to flag?
(G summarises the following[0], but a definitive source would clear up what the necessary algorithmic checks are).
I wish I could find the email, but awhile ago one YC startup pitched me on a six-figure job role solely dedicated to posting/commenting on Hacker News about it. Apparently I did not respond "no, that's stupid."
The code for the infamous "I'm upping my p(doom)" video (https://www.youtube.com/watch?v=8j-hR4fJywU) is open-source and uses Processing: https://github.com/JohnHeibel/PDoomVideo
reply