we're growing our product team at Polymarket
work with @shayne_coplan and I on the future of prediction markets and ship crazy zero to one ideas to millions of users
Email [email protected] with your best work
Polymarket 🤝 @ufc@TKOGrp
The UFC has chosen to partner with Polymarket as its Exclusive and Official Prediction Market.
The UFC will be integrating a Polymarket Scoreboard into the fights that will show the realtime % likelihood of who will win.
When I watch UFC, I love looking at the Polymarket odds to gauge who's winning. Now, hundreds of millions of others will be introduced to the power of Polymarket too.
Humbled to ring the @NYSE bell this morning with @danawhite, @AriEmanuel, Jeff Sprecher, @lynnmartin, Mark Shapiro, and @MatthewModabber.
Dream come true. More to come.
I’ve built a background daemon that connects to @linear for one of my enterprise clients (multi-billion company).
It runs autonomous AI workflows:
– Creates PRDs from tickets
– Waits for human review
– Implements, verifies, and opens PRs automatically
Built with LangGraph for orchestration, Codex + Claude for deep code understanding, direct LLM's API calls (via OpenRouter) for more deterministic tasks.
It’s pretty cool watching the whole flow execute live in the console ⚡️
Polymarket has acquired QCEX, a CFTC-regulated exchange and clearinghouse, for $112 million.
This paves the way for us to welcome American traders again.
I've waited a long time to say this:
Polymarket is coming home 🇺🇸🦅
@_Kavsoft Great work! If you could do another one like this with an animated header but with each tab being it’s own view (i.e. basically a Twitter profile) that would be much appreciated!
@dmokafa@allenholub Not disagreeing. I’m a big fan of TDD for making good design decisions. But once the architecture is in place most new code written should be an almost brainless exercise. If you’re not “designing” and are merely building upon past design decisions you don’t need* to follow TDD
@allenholub@dmokafa I don’t disagree TDD is a design strategy, but you’re missing my point. If you design with TDD at the outset properly there should be no reason to “design” anything else as you build features. New features should follow the same proven design principles, they don’t need TDD
@allenholub@dmokafa Follow TDD when it makes sense, write tests later when it makes sense, and skip tests when it makes sense. The answer in software dev is always “it depends”
@allenholub@dmokafa Following TDD like a religious zealot could be a huge waste of time for an early stage product. When your requirements change so do your tests and keeping things green starts to feel like a chore rather than a great benefit
@azamsharp@stephencelis In this example @stephencelis is asking how you ensure client side logic works properly if createAccount(“Johndoe”) returns a 500 error. And the point is that you can’t (unless your server happens to be down). Without mocking you can’t fully test all the paths through your logic
@alpennec I use a modifier like this for most icons to maintain alignment. A bit "hacky" but works 🤷♂️
func body(content: Content) -> some View {
Image(systemName: "rectangle")
.hidden()
.padding(6)
.overlay(
content
)
}
The combination of these powerful products has created a delightful user experience for beginners while also providing a secure, non-custodial platform to store their funds while earning passive income.
#Streams#Ethereum#Crypto#Plaid#Stripe#Polygon#Gnosis#Wyre
@azamsharp The iOS16 apis are promising, but if we’re talking about large complex apps my gut tells me the reliability of UIKit based navigation still can’t be beat. May change my mind after having more time to experiment though
@azamsharp Done this a few times but used UIKit for navigation by wrapping SwiftUI in hosting controllers. Works great. Couldn’t imagine building a modern app any other way. If you approach it with “pure” SwiftUI you’ll have a rough time though