juliettech

8.8K posts

juliettech banner
juliettech

juliettech

@_juliettech

growth eng 👩🏻‍💻 | co-founder @surge_women https://t.co/W8HYyzpw5u, prev head of devrel @helicone_ai @cyfrinaudits @aragonproject

localhost:8000 Katılım Şubat 2011
5.8K Takip Edilen7K Takipçiler
Sabitlenmiş Tweet
juliettech
juliettech@_juliettech·
After working in crypto DevRel for half a decade, I have a confession I hate to admit. I think DevRels are one of the main reasons why crypto hasn't reached mainstream adoption. Here's what's going on:
English
219
125
1.2K
205.3K
juliettech retweetledi
Connor Loi
Connor Loi@connortbot·
Over the last week, we've automated everything except humans clicking the merge PR button. Introducing Replicas Automations: - daily security reviews / automated pentests - auto-fix customer Slack requests silently - auto-fix sentry / datadog errors - PR description and Linear sync - much more Since we began using it internally, we've been able to automate out an absurd amount of the SDLC. 1. On-call engineering Replicas automatically responds to errors in our Datadog. Additionally, every Slack customer message is silently picked up by Replicas, where it will evaluate, write a PR, and ping me in a different channel. 2. Code Review Since Replicas resolves CI failures automatically, we tracked the 8 most common things we typically rejected coding agent PRs on (useEffects, WET code, doc updates). We made 6 automations to cover them, all of which instructing Replicas to make CI checks. By combining this with reviewers like @greptile, Replicas writes the PR, then iterates over and over until all the OTHER Replicas agents agree that it passes. By the time any engineer reads the PR, its nearly perfect. 3. Testing Every day, Replicas runs E2E tests on our public API. For any unexpected failures, we get a Slack message. 4. Planning and Development (duh) Replicas already had integrations with Slack and Linear, so developing with it was naturally collaborative. Many of our beta testing organizations have found incredible use cases, like full E2E fullstack tests, pentesting, and much more. And we have many exciting triggers and automations to come. Book a demo with us for replicas[dot]dev and I promise we can make engineering 2x faster ;)
English
4
5
31
2.3K
juliettech
juliettech@_juliettech·
im sorry but if you're leaving em dashes (among other hints) in your copy, AI is hurting you, not helping you
English
2
0
3
103
juliettech
juliettech@_juliettech·
watch every saas company become api-first in 3….2….
English
0
0
0
98
juliettech
juliettech@_juliettech·
every engineer in 2026
juliettech tweet media
English
0
0
3
111
juliettech retweetledi
Guillermo Flor
Guillermo Flor@guilleflorvs·
Sequoia's thesis that the next $1T company will sell work, not software, is the most important reframe in AI right now. The argument: if you sell a copilot, you're competing with every new model release. But if you sell the outcome — books closed, contracts reviewed, claims handled — every AI improvement makes your margins better, not your product obsolete. The key insight most people miss: for every $1 spent on software, ~$6 is spent on services. The entire SaaS playbook was about capturing the software dollar. The AI playbook is about capturing the services dollar — at software margins. Not "AI for accountants." The AI accounting firm. Not "AI for lawyers." The AI law firm. The companies that figure this out won't look like SaaS companies. They'll look like services firms rebuilt on software infrastructure. That's a fundamentally different company to build, fund, and scale. And most founders are still building copilots.
Guillermo Flor tweet media
English
227
542
5.6K
2.1M
juliettech
juliettech@_juliettech·
serious things happen when we don't take ourselves too seriously
English
0
0
1
86
juliettech
juliettech@_juliettech·
will never understand how google docs still doesn't have code formatting
English
1
0
1
184
juliettech
juliettech@_juliettech·
I've realized fear most often comes from inexperience, not from lack of ability
English
0
0
2
98
juliettech
juliettech@_juliettech·
call me crazy but I think SaaS will slowly disappear Im seeing more and more non-technical folks ship SaaS-like products for their teams in a few hours. why use someone else's product when you can build one for your own needs and maintain it with a long-running agent?
English
0
0
2
218
juliettech
juliettech@_juliettech·
we're at the point of the cycle where "just bc we can, doesn't mean we should" just bc AI can do it, doesn't mean it should just bc we can tokenize it, doesn't mean we should just bc it can be a mobile app, doesn't mean it should I call it the boomerang moment
English
0
0
1
61
juliettech
juliettech@_juliettech·
guys call me crazy, but Ive been enjoying codex more than claude code lately? claude code generates better code on the first go, but codex is just better at debugging - which, lezzzzbehonest, is half the job
English
1
0
6
434
juliettech retweetledi
MSA
MSA@MainStreetAIHQ·
@claudeai Life if anthropic just fixed the usage
English
14
27
1.1K
67.2K
juliettech
juliettech@_juliettech·
everyone: “AI is great it does everything for me” engineers: “right but how do I get it to do the same thing every time?”
English
7
0
15
257
juliettech
juliettech@_juliettech·
I surprisingly agree. I’ve been testing out Codex at times when my Claude Code gets stuck and damn, Im impressed with how much it has improved!
Dan Shipper 📧@danshipper

BREAKING: @OpenAI just released GPT-5.4 and it is AMAZING. We spent a week @every putting it through real engineering tasks from code reviews to planning workflows and using it inside of our @openclaw setups. The verdict: OpenAI is back in the coding race. - Its planning capability consistently beat Codex 5.3 and Opus 4.6 in head-to-head tests. It produces plans that are thorough and technically precise, and have a user focus and “human” feel that has been missing from OpenAI's previous coding mode - It reviews code with more depth than 5.3 Codex, and a much more conversational voice that doesn't make you feel dumb. - It became our go-to model in @OpenClaw: with some model-specific tweaks to the harness it's fast, intelligent, and more human. It's also about half the price of Opus 4.6. As ever, there are tradeoffs: - GPT-5.4 has a tendency to expand the task well beyond what you asked for and to call tasks done before they're finished. - In the @OpenClaw harness it sometimes completed tasks in obviously wrong ways, then lied about it. Overall though, it's my new daily driver for coding and in my Claw. Its thinking-traces produced some genuine wow moments for me. Our complete vibe check is available on @every now -> every.to/vibe-check/gpt…

English
2
0
10
398
juliettech
juliettech@_juliettech·
❤️‍🔥 so excited for this next chapter!!
Justin Torre@justinstorre

Hi friends! Big news today: Helicone is joining Mintlify 🚀 3 years ago, we started Helicone out of YC W23 with a simple bet: every hype-cycle has a massive observability market, and we felt like AI was going to be even more prevalent. We knew someone needed to build the platform to ingest and make sense of it all. So we did. Years of grinding and a handful of pivots later, we built something real that customers use every single day. I spent most of that time worried about tomorrow and never really stopped to look back. But looking back now: - 14T+ tokens processed - 30k+ sign ups - 36M+ users tracked - Trending on Github last year (5.2k stars) - $1M+ ARR - Product of the week on Product Hunt That still blows my mind. So why Mintlify? In a post-AGI world, a knowledge infrastructure layer is the thing that makes the most sense for companies to invest in. Waymo didn't reinvent the roads, but still needed to learn about them. Mintlify is the information layer for agents building the systems of the future. The overlap with what we were building at Helicone was obvious. Same world, different angle. More importantly, I actually like the team and the product. That sounds simple but after talking to a dozen companies, it's rarer than you'd think. @handotdev and @hahnbeelee are both incredible and formidable founders that Cole and I really admire. Things I learned building Helicone that I think are underrated - A 5-person team can do an absurd amount if everyone is locked in. Headcount is not a moat. - If you have data at scale and need analytics, just pick ClickHouse. Don't overthink it. - The grind is real, and it's fun. But REALLY try not to be stressed when you aren't grinding. That part took me way too long to learn. - It's never too late to pivot and try new things. - Charge more for your product. What's next I'm going to be leading an engineering team at Mintlify and I'm genuinely excited about what we're building. Keep an eye on my X, because I can't wait to be tweeting about it more. Thanks to @coleywoleyyy for being an incredible co-founder. Thanks to our team, our investors, our customers, and everyone who bet on us early. And thanks to my fiancee for putting up with the chaos of startup life. That part is deeply underappreciated. And lastly, thank you @mintlify for taking a bet on the Helicone team. We are so excited for the next phase. More to come. DMs are open.

English
4
0
13
705
juliettech retweetledi
Alex Atallah
Alex Atallah@alexatallah·
It's somewhat unfortunate that virtually all software platforms are only using AI to go wide instead of deep, piling on more features to increase the value of their platform lock-in. More companies should use AI to master the long-tail edge cases of their core domain and increase their composability, rather than merely expanding into adjacent areas.
English
27
14
200
14.7K
juliettech
juliettech@_juliettech·
before: websites now: MCPs injecting UI widgets into AI chat iframes
juliettech tweet media
English
2
0
5
291