Log inSign up
Quinn Slack
Amp
14.5K posts
Quinn Slack profile banner
@sqs

Quinn Slack

Amp
@sqs
CEO & Member of Technical Staff @ampcode, founded @sourcegraph
San Francisco
slack.org
Joined February 2007
3,996
Following
18K
Followers
RepliesRepliesRepostsRepostsMediaMedia

Log in or sign up for X

See what’s happening and join the conversation

Continue with phone
or
Log in with username or email
Terms·Privacy·Cookies·Accessibility·Ads Info·© 2026 X Corp.
  • @sqs
    Quinn Slack
    Amp
    @sqs
    1h
    my friend's company is planning to send PS5s with GTA 6 to all their competitors' top employees not to hire them, but to distract them
    11
  • @sqs
    Quinn Slack
    Amp
    @sqs
    3h
    my orb factor is 3.64 - at any given second there are on avg 3.64 orbs awake & running my agents to do stuff for me what is your orb factor?
    8
  • @sqs
    Quinn Slack
    Amp
    @sqs
    3h
    Disappointing for those who like slowness and waiting
    @thorstenball
    Thorsten Ball
    Amp
    @thorstenball
    3h
    Enabled faster orb creation for everyone this morning. Five orbs in ten seconds, bottlenecked by my typing.
    00:00
  • @sqs
    Quinn Slack
    Amp
    @sqs
    7h
    If you like Amp's design, you like Brett. See how Brett works with Amp and makes custom video/graphics tools on-the-fly to get stuff just right.
    @0xBrettj
    Brett
    @0xBrettj
    7h
    Building small apps is so addictive, when you can fire off ideas without agents consuming your machine. In 30 mins I had a deployed utility to trim, crop, and add a background to videos—something I used to have to resort to Adobe After Effects for.
    00:00
    2
  • @sqs
    Quinn Slack
    Amp
    @sqs
    15h
    I hate that we had this (or any) bug in the first place, but it feels pretty magical how we can fix bugs in Amp. Key things we have in place now ("The Amp Way" we call it) that are IMO critical for anyone building a software product now: 1. Our users know we care (and actually
    @sqs
    Quinn Slack
    Amp
    @sqs
    Aug 15, 2025
    When I first saw @artman’s post about Fixing Bugs First at Linear, I nodded a bit, and then a lot. I'm so glad @thorstenball and I radically adhered to this from day 1 on @AmpCode. Here's what I've learned: • Fix Bugs Now (not First): The overhead to file an issue, prioritize
    3