Cameroon is getting hammered by bond investors after a credit downgrade. Having a nonagenarian leader with no public succession plan doesn’t help. Read more: https://t.co/nvSiWySgWr
🎁: Alberto Pizzoli/AFP/Getty Images
AI is supposed to make life easier.
I wanted to book a dental scaling appointment.
Instead, I had to book a call with an AI agent to explain that I wanted an appointment and explain my issues.....
Then it emailed me a form to fill in my details.
I just wanted to clean my teeth.
We used to just pick a time slot.
Active Search is Basecamp's new gem: one search API for Rails across backends. Define an index, add has_search, then chain search, filter and highlight.
Start on SQLite, Postgres or MySQL, move to Elasticsearch, Meilisearch or Typesense without rewriting queries. Still alpha.
Highly recommend installing 𝗴𝗼𝗼𝗱-𝗰𝘀𝘀 in Claude Code or Codex, then having Opus 5.5 use it to 𝗰𝗵𝗲𝗰𝗸 𝘁𝗵𝗲 𝘀𝗶𝘁𝗲 𝘆𝗼𝘂 𝘃𝗶𝗯𝗲-𝗰𝗼𝗱𝗲𝗱. It holds 47 modern CSS techniques, and with it installed, your agent tries them first whenever it writes styles.
A few on the list you can check right away:
→ Tap a button on your phone and 𝘁𝗵𝗲 𝗵𝗼𝘃𝗲𝗿 𝗲𝗳𝗳𝗲𝗰𝘁 𝗴𝗲𝘁𝘀 𝘀𝘁𝘂𝗰𝗸. Put hover styles inside (hover: hover) and (pointer: fine) so only devices with a mouse get them
→ Open a form and every required field is already red. Switch to :user-invalid so a field turns red only after someone edits it or hits submit
→ Click an in-page link and the heading lands under your sticky nav. Give html a scroll-padding as tall as the nav, and the jump lands just below it
→ A price or timer ticks and the text next to it shifts. Add tabular-nums so every digit is the same width
→ An icon button is too small to tap. Use a pseudo-element to grow the tap area to 44px without changing how it looks
Send this prompt to Opus 5.5 👇
"Install good-css following the README at https://t.co/dXWbMbn7eF, then read its SKILL.md and the reference files you need.
Then use it to check this project's existing styles (CSS files and Tailwind classes in components both count) for three kinds of problems:
1. Things that break on phones: hover states that stick after a tap, and tap areas smaller than 44px.
2. Things CSS can do that were built with scripts or a pile of breakpoints: dropdown menus, popovers, accordions, and layouts stitched together from several breakpoints.
3. Details: in-page links that land under the sticky nav, forms that open already full of red borders, ticking numbers that shift the text next to them, and focus rings that were removed.
Report only these three kinds and skip any the project doesn't have. Components that come from a component library don't count. For each issue, quote the original code, explain what goes wrong on which device, and suggest the smallest change, ranked by impact. Also note which browsers don't support a technique you use yet.
Show me the list of issues first. Don't change any code."
there's no such thing as a rogue agent man its software someone made and deployed they are responsible for what it does
cannot let this blame shifting occur
I MADE IT!
I beat Adobe and shipped a better relight feature than them. (theirs is not even released yet).
A multibillion-dollar company with thousands of engineers just got beat by one person.
Crazy thing is that https://t.co/s8rpanKqsP runs in your browser locally for Free 🤯
Let's kill Adobe one feature at a time.
Stay tuned, I'm working on a desktop version of ImageFlow and a new LightRoom alternative that i'm so excited about!
If billionaires came out and said they were going to hunt us for sport, some of you would defend it by saying:
"You’re just mad because you can’t fucking run fast."