
@opacityhq, startup builder, coach to founders, BJJ black belt, and father. Ex @slackhq
Carlsbad
Joined March 2026
- Tweets75
- Following113
- Followers65
- Likes112
Dillon Ferdinandi retweeted
i get asked for tokyo recs a lot.
so, i made a little page with some of my favorite places.
it uses local memory so you can create a little saved list for the day—and continuing to ship updates!
check it out here: benitez.jp/japan/tokyo
Dillon Ferdinandi retweeted
We spoke with sound designer Josh Dunsterville (@neversitdull) about the role of sound in software.
🔊 Sound on for this one.
Join the Zoah waitlist at zoah.com.
Early innings still, but I love how easy it is to use the Zoah MCP server to generate initial ideas for typography, color palettes, and branding. Then have my agent translate to a design system with components, and use those comps to build and deploy a website, all in Zoah!
This advice extends well beyond design. I'm also reminded that there needs to be an openness on the receiving end. I've made all the mistakes in the book - too vague or asking to "catch up" and yet people made time for me. The industry only moves forward when people open doors, take chances, and say "yes".
How to Ask for Help
If you're a junior designer, I want to share a few things that will help you ask for help more effectively, be it wanting a portfolio review, introductions, advice, or anything really.
1. Be direct.
Most of the people you want help from are busy people. It is *greatly* preferred when you are upfront and direct about what you want. There are only so many hours in the day, and I'd rather know exactly what you want and how I can help.
2. Be specific
There are very few people in the world who ever want to 'catch up' or 'get their brain picked' when you don't know someone and it's ambiguous what they want.
If you want feedback on your portfolio, ask for that. If you want ideas on how to reposition yourself, ask for that.
If you aren't specific, you'll either get no response, or get generic response. My general feedback on every portfolio will always be: show your work upfront; remove half the words then remove more again, and spend 10x the time refining the work shown vs the design of the portfolio itself.
3. Be concise
Everyone is busy, so be respectful of their time and be as concise as possible with your ask.
4. Follow up
If you don't hear back from someone, the most likely answer is they either missed your message or forgot. Platforms like X have, somehow still, terrible DM's that always seem to be buggy, so just follow up respectfully. I don't find it annoying; rather I appreciate the persistence and reminder.
5. Follow through
If someone takes the time to help you, and gives you advice or suggestions, you should follow through on them. I love hearing about how things went or the updates someone made, but I'd guess less than 3% of the time I hear back from someone. Want to know an easy way to start to build a relationship? Follow through. Those who follow up I am more likely to want to continue helping and building into.
So what does this look like in practice?
Instead of "Here's my portfolio, let me know if you have thoughts!" say "I'm updating my portfolio as I look for a full time role at a startup. Would you mind letting me know 1) if this would pass your first 5 second screen, and 2) do you think the work examples I have selected seem credible to an early stage founder?"
Instead of "I'd love to meet if you're ever down", say "I have a few first round interviews coming up in a few weeks. Would you be open to doing a 30m practice portfolio presentation with me? I'll show up at any time that works for you this week or next."
I have generally found our industry is full of people who want to help others, so I hope this is helps you better ask for help!
Dillon Ferdinandi retweeted
We've been staring at curves for a long time. Figured we'd show you some.
Want access? Join the Zoah waitlist: zoah.com.
Building and testing @OpacityHQ in a bespoke browser that building and testing in parallel is a bit surreal.
Dillon Ferdinandi retweeted
Visual Diffs! For design AND code.
Real-time look at me building @OpacityHQ!
We have our OWN version control that has nothing to do with Git. Y'all, it's time to move off Github and Figma (genuinely love them both, but there's a new kid on the block) and onto Zoah!
Dillon Ferdinandi retweeted
Today we're officially launching @typedotcom, the shared space for your team's best AI work.
Teams need a central place to build apps, skills and automations together. Not swarms of agents.
Our ambition with Type is to be the last piece of software your team will ever need.
To build this, we've raised $4m from @LererHippeau, @haystackvc, @MatchstickVC, and angels from Slack, Github, and Ramp.
So what does Type do?
→ share work from Claude chats into a collaborative space
→ switch harness or model any time
→ manage integrations with granular permissions
→ a central place to deploy apps and automations together
→ build a self-learning company brain
→ use your existing Claude or ChatGPT subscription
Companies like @rayconglobal, @Intelligems and @trueclassictees are already running tens of thousands of successful agent jobs that forecast revenue, manage inventory, answer support tickets, and a lot more.
We're blown away every day at the custom tools and automations our customers are building.
What's something you haven't yet been able to solve or automate in your business? Tell us in the comments and we'll respond by building it for you in Type!
So pumped for everyone who jumped in to @OpacityHQ founding member program. There's a lot of rough edges and some product areas aren't close to done yet but we forced ourselves to get it into your hands. Can't wait to build alongside you all.
So proud of the team. A lot of hard work to get here!
FIRST REAL PAID CUSTOMER! 🚀
Just a minute after our exclusive access email went out to our waitlisters :D
Thanks for everyone who believed early and got on our waitlist!
And congrats to team @OpacityHQ!
Dillon Ferdinandi retweeted
new name, new assets.
zoah.com
Dillon Ferdinandi retweeted
I heard ya'll like cute little animated vector characters?!
opacity.com -> zoah.com
To help build @OpacityHQ, we've built a significant amount of internal tooling to help manage worktrees, run multiple local app instances without colliding, and have deeply integrated server-side and browser-side tooling to measure performance, telemetry, visualize data, etc.
Dillon Ferdinandi retweeted
Who's gonna tell vibe coders about...
> Rate Limiting
> Caching
> Load Balancing
> Reverse Proxies
> API Gateways
> CI/CD
> Docker
> Kubernetes
> Service Discovery
> Circuit Breakers
> Timeouts
> Retries
> Exponential Backoff
> Idempotency
> Message Queues
> Pub/Sub
> Event-Driven Architecture
> Distributed Transactions
> Saga Pattern
> Dead Letter Queues
> Cron Jobs
> WebSockets
> Long Polling
> Server-Sent Events
> Database Indexing
> Query Optimization
> N+1 Queries
> Connection Pooling
> Read Replicas
> Sharding
> Partitioning
> Replication
> Leader Election
> CAP Theorem
> Eventual Consistency
> Optimistic Locking
> Pessimistic Locking
> Distributed Locks
> Race Conditions
> Deadlocks
> Memory Leaks
> Garbage Collection
> Thread Safety
> Backpressure
> Autoscaling
> Horizontal Scaling
> Vertical Scaling
> CDN
> Edge Caching
> Cache Invalidation
> Feature Flags
> Blue-Green Deployments
> Canary Releases
> Rolling Deployments
> Rollbacks
> Health Checks
> Liveness & Readiness Probes
> Monitoring
> Logging
> Distributed Tracing
> Metrics
> Alerting
> SLOs
> SLIs
> Error Budgets
> Observability
> Secrets Management
> IAM
> OAuth
> JWT Rotation
> TLS
> Encryption at Rest
> Encryption in Transit
> WAF
> DDoS Protection
> CORS
> CSRF
> SQL Injection
> XSS
> SSRF
> Database Migrations
> Schema Versioning
> Disaster Recovery
> Backups
> Failover
> Multi-Region Deployments
> Chaos Engineering
> Cost Optimization
> Cold Starts
> Serverless Limits
> Latency
> Throughput
> P99 Latency
> Tail Latency
> Network Partitions
> Clock Skew
> DNS
> TCP vs UDP
> HTTP/2 & HTTP/3
> gRPC
> Webhooks
> API Versioning
> Semantic Versioning
> Infrastructure as Code
> Terraform
> Helm Charts
> Build Caching
> Dependency Hell
> Production Incidents
> On-call
> Postmortems
...until the app gets its first million users.
Dillon Ferdinandi retweeted
The pen tool hasn't changed since 1987. We're rebuilding it at Opacity.
Early access: opacity.com























