đ Pierre.co
Introducing a new developer platform for modern teams.
This is the new stack (and if youâre at a startup, youâre on it)âitâs Figma for Design, Linear for issue tracking, Notion for docs⊠and it all feels EXTREMELY GREAT. Itâs real time, collaborative, performant. Thoughtfully designed and executed. What else could you want?
Well⊠what about engineering? Whereâs our shiny new thing đ„ș? Our de facto tools and concepts were largely created over a decade ago and havenât changed much since their inception; codeâhosting, file browsing, pull requests, CI. Innovated on early, for sure, but then copied and cloned ad nauseam for the last 10 years.
Maybe itâs finally time we try something different. Radically different đââïž.
About 6 months ago we started working on just such a thing. Having worked together since 2008, leading early teams at Twitter, Github, Medium, CoinbaseâŠetc, founding companies, creating open source projects, scaling orgs, landing migrations. We saw some shit. And ultimately this is why weâre building Pierre.
We believe itâs time for a new platform for pushing, discussing, and shipping code. A next-generation hub, not just for engineers, but for the whole team, purpose built to get out of your way, and just let you ship. And weâre starting by rethinking the primitives from the ground up:
No more pull requests - instead? Branches. Immediately shareable, with fully integrated previews, rich descriptions, and realtime, highlight-driven comments. No extra steps between you and getting the whole team involved in reviews, not just of code, but of functionality.
No more CIÂ - instead? Bots. Fully programmable, long running, event driven bots that can respond to not just code pushes, but new comments, changes to descriptions, new branches, new commits, etc. And then return not just endlessly, unreadable logs and 1s and 0s, but dynamic widgets, comments, live gauges, and more.
No more bullshit - instead? Only the features you use. Because when you use a platform everyday, the best experience, is the lightest experience. The one where you see only what you need, so you can get the most done, in the least amount of time.
And this is just the start of a whole enormous thing. And weâd love your help.
Weâre looking for teams to join our private alpha and help us shape the future of collaborative engineering. Interested? Drop us a line at jacob@pierre.co or join our discord.
âThe Pierre Team (Jacob, Ian, Mark, Jon, Rachel)
Head over to pierre.co to see more.
What is the problem you guys are solving? Curious what pain points you see with the current tooling and how you envision bots solving them.
Iâm not a developer (I havenât been for a decade), but I work extensively with developers. I joined the "party" to check it out. I hope that is ok.
In my experience large enterprises (e.g. banks) would be in culture shock if your three recommendations were adopted.