chrometaphore

Designer, Creative Technologist.

[chrometaphore @chrometaphore]

The transferable skill you should be worried about acquiring is critical thinking

[chrometaphore @chrometaphore]

@UnslothAI @thinkymachines will it run on my chromebook?

[chrometaphore @chrometaphore]

If you are into the weirdness of agentic workflows, @EntireHQ looks super promising.

[chrometaphore @chrometaphore]

A2A is the business model most companies are not ready for, yet.
https://t.co/Eg2GyZ8BVL

[chrometaphore @chrometaphore]

From the archives (2024)
Generative AI sketchbook
ComfyUI + Controlnet

[chrometaphore @chrometaphore]

Designing for AI is more about harnessing the narrative flow and less about adding the same old UI controls to novel features.

[chrometaphore @chrometaphore]

Just released a @claudeai skill for building consistently with with any design system 🧑‍💻

https://t.co/WXPayeSorv

[chrometaphore @chrometaphore]

Crazy how my M1 from 2021 can run 9B Models locally while multitasking in Figma.

Best laptop I ever had, hands down.

[chrometaphore @chrometaphore]

Excited for this!
@claudeai

[chrometaphore @chrometaphore]

Weekend experiments.

A new take on language learning flashcards 🇯🇵
Give it a spin, it's fun!
https://t.co/oXxLZQgavJ

[chrometaphore @chrometaphore]

Started messing around with Hermes --> @designintern_ai

[chrometaphore @chrometaphore]

@leerob It's so tempting to let automations take over for hours until things stop matching your expectations. It's not a fun ride from there.

Small measured iterations always win.

[Lee Robinson @leerob]

You might believe you should spend less time thinking about code because of AI.

I strongly disagree! We’re watching this play out live where tons of AI generated code becomes a liability.

At the end of the day, an engineer needs to be responsible / on call for code that gets shipped to production. If you don’t understand the system you’re trying to debug, you’re probably going to have a bad time.

Yes, AI can help with all of this, if you set up the proper systems. You can have agents triage prod logs, look at errors, etc. You can speed up parts of the investigation, but an engineer needs to make the call. There might be serious customer or financial implications from that change.

I expect the trend continue for trimming dependencies, vendoring code so you can modify it directly, preferring simpler systems with fewer abstractions, and spending waaaay more time thinking about system design and code maintenance.

I’ve said this before, but it’s a great time to get familiar with CS fundamentals and some of the history behind what great software looks like. Many parts will be different in the coming years as AI progresses, but also a lot more than people realize will stay the same.

[chrometaphore @chrometaphore]

Weekend fun experiment: What if AI agents could see icon libraries the way humans do?

Iconic 👾 is an MCP service that helps agents like @claudeai find icons by intent.

[Three.js @threejs]

🎨 https://t.co/cMVxNkExx7

[chrometaphore @chrometaphore]

Conversational interfaces have been around since forever!

[chrometaphore @chrometaphore]

All my builder friends are now suffering of AI-fueled creative ADHD. It's fascinating

[chrometaphore @chrometaphore]

I thought I'd share my personal recipe for keeping alignment between you, your AI agents, and the project information that matters.
https://t.co/PkMhSZmUBs

[chrometaphore @chrometaphore]

PSA
Don’t share your API keys or .env files with your coding AI assistant

[chrometaphore @chrometaphore]

If you think the vibe coding era makes knowledge of code principles useless, I urge you to think again.

Fundamentals matter now, more than ever.