Suggestions
Quinn Slack
CEO at Sourcegraph
Quinn Slack, Board Member at Hack Club
Quinn Slack is a prominent figure in the tech industry, serving as the CEO and co-founder of Sourcegraph, a leading code intelligence platform. He is also a Board Member of Hack Club, a national nonprofit that brings coding clubs to high schools across the country.
Professional Background
-
CEO and Co-founder, Sourcegraph (2013 - Present): Quinn co-founded Sourcegraph in 2013 and has been leading the company as CEO since its inception. Sourcegraph uses AI and machine learning to help developers better understand, fix, and automate their code.34
-
Board Member, Hack Club (2015 - Present): Quinn has been a Board Member of Hack Club since 2015. Hack Club is a nonprofit that empowers teenagers to learn coding and build real-world projects.12
-
Co-founder, Blend Labs (2012 - 2013): Prior to Sourcegraph, Quinn co-founded Blend Labs, a platform that transformed consumer banking experiences and streamlined workflows for teams.4
-
Forward Deployed Engineer, Palantir Technologies (2011 - 2012): Quinn also worked as a Forward Deployed Engineer at Palantir Technologies.5
Education
Quinn Slack studied Computer Science at Stanford University, where he earned his Bachelor of Science degree.36
Personal Life
Quinn Slack lives in the San Francisco Bay Area.6 His email address is qslack@gmail.com, and he can be found on Twitter, GitHub, and LinkedIn under the username @sqs.6
In summary, Quinn Slack is a highly accomplished tech entrepreneur and leader, serving as the CEO of Sourcegraph and a Board Member of Hack Club. His expertise in computer science and his commitment to making coding more accessible have made him a prominent figure in the industry.
Highlights
Lots of people building @AmpCode original features into other agents, like the oracle, the librarian, and thread sharing.
Etc.
We love to see this and would love to hear feedback from people who do this and who use these transplanted features: what’d you learn in transplanting it to another agent? If you blog about it and share your feedback and criticism, that’d be awesome!
The truth is that the current iteration of coding agents is nasty, brutish, and short.
It’s like back when there was 15 DVCSes, several like Git and Hg were popular but the workflows were messy, and people were working toward the higher-level platform and workflow (the GitHub in this analogy, but this’ll be much bigger than GitHub).
We build Amp so that we and our users are on the front lines and can build/discover that next thing and workflow, the next generation of the stuff congealing in this primordial soup of threads, tasks, tools, skills, commits, subagents, etc.
So, for anyone, and especially those who build stuff inspired by Amp and get to know it really well, please share your ideas and criticism back with us so we can congeal this soup faster.
(We write down what we’re learning at https://t.co/ili8nvb5AM. There are some great agent design critiques from @mitsuhiko at https://t.co/HTexrjZeQg. Also @mitchellh @badlogicgames @simonw @HamelHusain @geoffreylitt.)
2 years ago in Germany an airport security person asked me “is this your first time flying?” when I left my laptop in my bag.
