Diligesker IT/AI Digest

Tag: Web Design

  • Dickover UX names the popups that make the web worse

    Dickover UX names the popups that make the web worse

    Dickover UX is the newly popular label for a very old irritation: a website or app covers the thing you came to read and asks you to do something else first. John Gruber coined the term in a May 29 Daring Fireball post, and the reason it landed is simple. Everyone has lost patience with cookie walls, newsletter nags, app install prompts, and fake must-click dialogs that treat attention like a hostage.

    The short version

    • A dickover is a modal, popover, or curtain that blocks content for an interaction the reader did not ask for.
    • The test is necessity: sign-in for paid content is different from a newsletter prompt that appears before the article.
    • The Hacker News thread mostly agreed with the annoyance, but argued over the business pressure and privacy-law incentives behind it.
    • Product teams should review overlays in private browsing sessions, because returning staff often never see the first-run mess new users face.
    • For more coverage of product and web design patterns, see the IT & AI archive.

    What happened

    Gruber defines a dickover as a modal panel, popover, or curtain that deliberately obscures a site’s own content to force an unwanted interaction. His examples include cookie consent panels, newsletter signups, mobile app install prompts, and terms prompts that appear before the page gives the user what they came for.

    The post is not arguing that every modal is bad. A paywall login panel can be part of the content transaction. The sharper complaint is aimed at overlays that serve the site’s secondary goals while interrupting the user’s primary task. That is why dickover UX is less a technical category than a product judgment.

    Gruber also separates dickovers from “dickbars,” his term for partial-width or edge-anchored bars that do not fully block the page. Those can still cover text, break keyboard paging, or distract the reader, but the full-screen curtain is the bigger sin because it demands dismissal before the page can be used.

    Why this is worth watching

    The useful thing about dickover UX is that it gives teams a rude but memorable name for a pattern they often normalize. Most teams do not set out to make hostile pages. They add one prompt for legal coverage, one for growth, one for email capture, one for app installs, and one for retention. The user experiences the stack, not the org chart.

    The term also catches a gap in design reviews. Teams often evaluate whether the modal works, converts, and complies. They spend less time asking whether it deserved to appear at that moment. A high-converting overlay can still teach readers that the site will interrupt them whenever it wants something.

    There is an app lesson here too. Mobile teams use notification prompts, rating prompts, permission dialogs, and install nudges in the same spirit. If the prompt appears before the user has received value, it feels like rent collection at the front door.

    What Hacker News readers are arguing about

    The Hacker News discussion was mostly sympathetic to the term. Many commenters treated it as a relief to have a word for the reflexive popups they already dismiss with Escape, browser filters, or uBlock Origin rules. Several people praised the value of naming bad patterns because a memorable label makes them easier to ridicule inside teams.

    The strongest disagreement was about incentives. One camp argued that readers are not entitled to a clean page if the site depends on ads, email capture, or other conversion mechanics. The counterargument was blunt: the browser is the user’s agent, and once a site sends a page to it, the user can filter and reshape that page locally. That split matters because it frames dickovers either as a price of access or as abuse of the reader’s machine and attention.

    Cookie consent drew the longest side debate. Some blamed European privacy regulation, while others pointed out that GDPR does not require full-screen annoyances. The more practical complaint was about malicious compliance: companies can satisfy lawyers while making rejection harder than acceptance. Commenters also noted Global Privacy Control as a better browser-level direction, though many sites still ignore it.

    The most useful operator point was simple: teams may not see their own damage. Staff, executives, and developers often accepted the cookie prompt years ago or browse from known networks, so they miss the chain of captcha, cookie wall, newsletter modal, app prompt, and checkout interruption that hits new users.

    dickover UX checklist

    A practical dickover UX review should happen before the growth experiment ships, not after complaints arrive. Run the page as a first-time visitor and watch for any prompt that blocks reading, hides the dismiss option, or asks for a commitment before the product has earned one.

    The practical read

    Treat every overlay as a small tax on trust. Before shipping one, ask five questions.

    • Is this required for the user to complete the task they started?
    • Can the user keep reading or using the page without answering now?
    • Is the dismiss action as visible as the accept action?
    • Does the prompt appear after the user has already received value?
    • Have you tested the page in a private window, on mobile, and from outside the company network?

    If the answer gets uncomfortable, the overlay probably belongs later, smaller, or nowhere. Dickover UX is a useful term because it makes a buried product tradeoff sound as ugly as it feels.

    Sources

  • LLM smells are getting easy to spot

    LLM smells are getting easy to spot

    LLM smells are the tiny tells that make AI-assisted writing or AI-built websites feel oddly familiar. A short post by Shiv After Dark put a useful name on the pattern: punchline-heavy prose, repeated sentence shapes, monospace-heavy pages, badges, cards, and step sections that keep appearing across unrelated work.

    The short version

    • LLM smells are not proof that a piece of work is bad. They are signs that the draft may still be too close to the model’s default style.
    • The clearest writing tells are punchline sentences, repeated short sentences, “X is the Y of Z” metaphors, and tidy contrast formulas.
    • The web design tells are just as visible: JetBrains Mono, step layouts, badge dots, familiar cards, and generic call-to-action buttons.
    • The useful editorial move is to treat AI output as a draft, then add concrete details, uneven human rhythm, and product-specific design choices.
    • Hacker News readers mostly pushed the argument toward code quality: AI output looks strongest when you do not yet know enough to judge it.

    What happened

    Shiv After Dark published “Various LLM smells” on May 28, 2026, after noticing that prose once polished by an LLM had started to resemble a lot of other writing on the web. The post is short, but the examples are sharp: aphoristic one-liners, strings of clipped sentences, metaphor templates, and the familiar “not merely X” style of contrast.

    The second half moves from prose to AI-generated websites. The author points to the same stack of visual habits showing up again and again: monospace typography, step sections, cards, buttons, blinking badge dots, and footnote-style flourishes. None of those choices are wrong by themselves. They become LLM smells when they arrive as a bundle, without much relationship to the product or audience.

    If you follow AI writing and web tooling, this fits a larger pattern. Models are good at producing plausible defaults. Plausible defaults are useful for a first pass. They are also easy to recognize once enough people publish them unchanged. For more English briefs on AI tooling and product craft, see the IT & AI archive.

    Why this is worth watching

    LLM smells are worth watching because they are an editing problem, not a purity test. The author is not arguing that people should stop using AI for creative work. The better reading is more practical: if a model gives you a draft in seconds, you still need to remove the model’s house style before the work feels like yours.

    For writing, that means checking whether a sentence adds information or only adds mood. Punchy lines can work, but a whole page of them starts to feel assembled. The same goes for neat metaphors. “X is the visible signature of Y” may sound elegant the first time. By the tenth version, it reads like a preset.

    For web teams, LLM smells are a useful QA category. A landing page can be clean and still generic. If the typography, cards, steps, icons, and microcopy could belong to any AI startup, the page probably needs one more design pass. App builders should pay special attention here, because store listings, onboarding screens, and extension directories reward clarity, but punish sameness.

    What Hacker News readers are arguing about

    The Hacker News discussion quickly widened from writing to competence. One of the strongest recurring points was that LLM output looks best in domains where the user is least able to judge it. That explains the split many people see in coding threads: beginners may experience the model as a dramatic productivity boost, while experienced engineers see the rework, missing context, and bad abstractions.

    Several commenters gave concrete coding examples. One described an assistant proposing a security-dangerous approach that would have bypassed a WebAssembly sandbox and executed submitted Python in the application container. Others complained about agent-generated codebases growing too large because each feature gets built in isolation: every modal is different, every button drifts, and business logic ends up scattered.

    There was a more positive camp too. Some readers said LLMs are genuinely useful for format conversions, API mappings, learning unfamiliar concepts, or getting past small obstacles. The practical distinction was not “use AI” versus “do not use AI.” It was whether the user has enough taste, tests, and domain knowledge to catch the smells before they harden into the final product.

    LLM smells checklist

    Before the final edit, look for the repeated shapes: punchline stacking, metaphor templates, tidy contrast lines, generic cards, and typography that says more about the model than the product.

    The practical read

    Use LLM smells as a checklist before publishing. In prose, look for punchline stacking, repeated short sentences, decorative metaphors, tidy contrast formulas, and abstract claims that do not name a real example. Replace them with specifics. Add the thing you actually saw, measured, built, shipped, or changed.

    In interface work, scan for the default AI landing page kit: monospace labels, gradient cards, step grids, badge dots, identical buttons, and generic hero copy. Keep the pieces that fit. Cut the ones that only make the page look “AI polished.” The goal is not to hide the tool. The goal is to make the result specific enough that the tool is no longer the most visible author.

    The same rule applies to code. AI can get you moving, especially on routine or verifiable tasks. But if you cannot review the output, you are outsourcing judgment. That is where LLM smells stop being cosmetic and start turning into maintenance work.

    Sources

  • Modern pixel fonts are useful again beyond nostalgia

    Modern pixel fonts are useful again beyond nostalgia

    Modern pixel fonts are getting interesting again because the better ones are not simple retro props. They keep the texture of old screens while fixing the parts that made those screens hard to read: weak metrics, awkward baselines, brittle scaling, and decorative-only glyph sets.

    The short version

    • Marcin Wichary’s note points to Analog Mono, Coral Pixels, Two Slice, and Vercel’s Geist Pixel as examples of pixel-inspired type made for current systems.
    • The useful pattern is constraint with cleanup: keep the low-resolution character, but make baseline, spacing, glyph coverage, and rendering work in real interfaces.
    • Modern pixel fonts are safest in short, high-personality surfaces such as badges, landing page headers, game-like UI, status labels, and product moments.
    • The Hacker News thread was enthusiastic about the fonts, but skeptical of the marketing language around them.

    What happened with modern pixel fonts

    Marcin Wichary collected a few recent pixel-style fonts that show how the category has changed. Analog Mono by Andrew Gleeson revisits the VCR OSD Mono look from 1990s consumer electronics, but fixes the low baseline issue that pulled descenders into awkward positions. Coral Pixels by Kumiko Yoshida turns old subpixel color fringing into a deliberate font effect. Two Slice by Joseph Fatula pushes the constraint further: it is only two pixels tall and still somewhat readable.

    The last example, Vercel’s Geist Pixel, makes the product-design point most clearly. Its pitch argues that pixel fonts often fail in production because they do not scale cleanly, their vertical metrics fight the rest of the type system, or they only work as decoration. Strip away the launch-copy gloss and the problem is real. A font can look charming in a specimen and still be annoying in a UI if the spacing, metadata, fallback behavior, and glyph coverage are weak.

    For readers who follow product design and developer tools, this sits neatly beside the broader IT & AI archive: small interface details keep becoming product identity. Typography is one of the cheapest details to change, and one of the easiest to misuse.

    Why this is worth watching

    The interesting part is not nostalgia by itself. Designers have been borrowing from old terminals, arcade cabinets, handhelds, and VCR overlays for years. The shift is that some modern pixel fonts are built like usable type, not screenshots of a mood board.

    That matters for web and app teams. A pixel font used as a logo, chip, scoreboard, command label, or onboarding accent can make a product feel less generic. Used across body copy, it usually becomes a punishment. The better question is where the constraint helps the interface say something quickly.

    Coral Pixels is a good example of the tradeoff. Subpixel fringing was originally a rendering artifact. Some people remember it as ugly eye strain; others read it as a strong memory of early LCDs and Windows-era text. As a color font, that artifact becomes a controlled style rather than an accidental blur. That does not make it broadly readable. It does make it useful in short bursts.

    What Hacker News readers are arguing about

    The Hacker News discussion is mostly a mix of font recommendations, nostalgia, and irritation at product marketing. Several readers liked Geist Pixel, Analog Mono, or Two Slice, while others used the thread to trade older favorites such as Topaz, Unscii, Departure Mono, 04b-03, Sans Nouveaux, and other low-resolution typefaces.

    The sharpest disagreement was around Coral Pixels. One camp found the color fringing hard to justify because subpixel rendering was meant to make text sharper, not more colorful. Another camp pushed back that many people did experience smeary, colored edges on older or poorly configured displays, which is exactly why the look can now trigger nostalgia.

    The most useful criticism was about Vercel’s copy for Geist Pixel. Commenters mocked phrases like “system extension” because they sound inflated. That skepticism is fair, but it also points to the real production issue: a pixel font only earns its place if it behaves well inside a type system. Letterforms are the visible part. Metrics, kerning, glyph coverage, and vertical alignment decide whether it survives contact with a real product.

    The practical read

    Treat modern pixel fonts like hot sauce. A little can make a product memorable. Too much makes everything harder to read.

    For a practical test, set the font in the exact surface where it will ship: a button, badge, hero word, scoreboard number, modal title, app-store screenshot, or game-like status line. Check it at mobile size, desktop size, light mode, dark mode, and one fallback font. If the personality disappears without the specimen page, the font was probably doing decorative work that your product cannot support.

    For app builders, the ASO angle is straightforward: distinctive type can help a screenshot or feature card stand out, but store assets punish low readability. Use the pixel voice for a short label or scene-setting word, then let a normal text face carry the explanation.

    Sources