Jesse

978 posts

Jesse banner
Jesse

Jesse

@sudojbird

dir of eng @lazer_hq | prev wovn @brtmoments @dapperlabs @SpaceX

SoCal انضم Temmuz 2021
1.6K يتبع1.1K المتابعون
Jesse أُعيد تغريده
atown
atown@AtownBrown·
I experimenting with a new idea, it involves social, current events, prediction markets, perps, options etc. I am looking for some people to do 15 min calls with to demo what I am building and get first reactions and feedback on what would get you to use this If you are open to chatting with me please hit my dms
English
3
2
6
477
Jesse
Jesse@sudojbird·
We need more innovators building and testing ideas onchain. That's why I pushed our Crypto team at Lazer to explore how we could easily equip agents with the needed context and skills to build and publish apps on @base, @farcaster_xyz, and soon @worldnetwork That evolved into the Lazer Mini App CLI. Simply install, run /lazer, and describe what you want. The agent handles auth, wallets, contracts, onchain data, and any platform adapters needed to publish your app.
Lazer@Lazer_HQ

We shipped an Agent CLI for building onchain mini apps. Skip the template. Build only what you need. Try it, link in thread 👇 Contributors: @sudojbird, @0x_reed, @james_mccomish, @freyja__3991, @iykAzorji

English
1
1
5
379
Jesse أُعيد تغريده
Simons
Simons@Simon_Ingari·
In the corporate world, if you have: - a decent salary, - a manager who trusts you without micromanaging, - the flexibility of a hybrid work setup, - the freedom to take time off when needed, - opportunities for growth and skill development, - a supportive and inclusive company culture, You’re already among the top 1% of professionals enjoying a truly balanced and fulfilling work life.
English
96
979
12.8K
780.1K
Jesse
Jesse@sudojbird·
82 ☀️
QST
0
0
0
44
atown
atown@AtownBrown·
Starting my 38th birthday off with Yoga in the clouds
atown tweet mediaatown tweet media
English
13
0
37
1.2K
Beanie
Beanie@beaniemaxi·
You either die a crypto founder or you live long enough to see yourself become an AI consultant.
Beanie tweet media
English
84
19
381
34.2K
Jesse
Jesse@sudojbird·
@jimchang @base @mpp @tempo @crossmint agents are just humans in sheep's clothing. They still function the same wrt needing funds and motive to spend like a consumer.
English
1
0
2
76
Jim
Jim@jimchang·
last week i spent 45 minutes funding my agents. x402 needs a @base wallet @mpp needs a @tempo wallet lobster cash (@crossmint) needs a solana wallet but none of these frameworks help you get money there. they assume you'll just figure it out. so i built Kibble. a skill that teaches your agent how to ask for funds. it sends you a payment link, you pick whatever token you have, and @lifiprotocol routes it to the agent's wallet. feed your agent with any token, on any chain. kibble.sh
English
97
44
488
74.3K
Jesse أُعيد تغريده
Noah Zweben
Noah Zweben@noahzweben·
Remote Control - Session Spawning: Run claude remote-control and then spawn a NEW local session in the mobile app. * Out to Max, Team, and Enterprise (>=2.1.74) *Have GH set up on mobile (relaxing soon) * Working on speeding up session start-time
English
123
117
1.6K
738.1K
Jesse أُعيد تغريده
Robleh
Robleh@robjama·
tl;dr hire ex-founders
signüll@signulll

the most underrated hire right now is a great product person. when i say product person i'm def not talking about a product manager. perhaps i think there has to be somewhat of a new role. i don't have a good name for it yet but maybe something like "product thinker".. someone with an intuitive grasp of the product as it exists, where it's soft, where it sings, & how to iterate it toward something even sharper. in some sense, this person has to cohesively hold in their head where this product should be 2 years from now & work backwards from that. i say this cuz when building was hard, engineering was the bottleneck & the status hierarchy often reflected that. building is no longer hard. which means the variance in outcomes has shifted almost entirely to judgment on what to build, how to sequence it, & how to talk about it. & the story matters as much as the thing. internally, it organizes the team around a shared model of why. externally, it shapes the interpretive frame users bring to their first experience. you can't retrofit narrative onto a product & expect it to land, it has to be load bearing from the start. the rarest version of this person sits at the intersection of culture & deep technology. someone genuinely bilingual. they know what's technically possible & they know which cultural currents are real vs. ephemeral. that combo is what separates products that feel inevitable from products that feel assembled. before ppl clap back with this person has always been valuable, i know.. i am just saying now they might be the most *important* person in the room. their value compounds like never before.

English
12
12
263
40.3K
Jesse أُعيد تغريده
Chintan Turakhia
Chintan Turakhia@chintanturakhia·
Run this prompt frequently. You're welcome.
Chintan Turakhia tweet media
English
121
316
6.9K
908.5K
Jesse
Jesse@sudojbird·
The new moat isn't a clever model, it's a team of 10x operators. At @Lazer_HQ, we've been quietly building one of the best-equipped engineering teams to help companies fundamentally evolve how they build software, implement agentic systems, and reshape their workflows for what's coming next.
JC@shiftj

New pattern I'm seeing in YC companies: a lot of them are operating more like agencies than software companies. Custom workflows, custom automations for each client. The intent is to productize eventually - but day to day, they look like an agency.

English
0
0
0
87
Jesse
Jesse@sudojbird·
@dwr You should only hire staff level engineers
English
0
0
0
189
Dan Romero
Dan Romero@dwr·
I'm hiring people for biz dev and biz ops roles at Tempo. Send me a DM if you're interested. Please be succinct and link to your LinkedIn.
English
61
14
676
108.3K
Jesse أُعيد تغريده
Ryo Lu
Ryo Lu@ryolu_·
software is still about thinking software has always been about taking ambiguous human needs and crystallizing them into precise, interlocking systems. the craft is in the breakdown: which abstractions to create, where boundaries should live, how pieces communicate. coding with ai today creates a new trap: the illusion of speed without structure. you can generate code fast, but without clear system architecture – the real boundaries, the actual invariants, the core abstractions – you end up with a pile that works until it doesn't. it's slop because there's no coherent mental model underneath. ai doesn't replace systems thinking – it amplifies the cost of not doing it. if you don't know what you want structurally, ai fills gaps with whatever pattern it's seen most. you get generic solutions to specific problems. coupled code where you needed clean boundaries. three different ways of doing the same thing because you never specified the one way. as Cursor handles longer tasks, the gap between "vaguely right direction" and "precisely understood system" compounds exponentially. when agents execute 100 steps instead of 10, your role becomes more important, not less. the skill shifts from "writing every line" to "holding the system in your head and communicating its essence": - define boundaries – what are the core abstractions? what should this component know? where does state live? - specify invariants – what must always be true? what are the constants and defaults that make the system work? - guide decomposition – how should this break down? what's the natural structure? what's stable vs likely to change? - maintain coherence – as ai generates more code, you ensure it fits the mental model, follows patterns, respects boundaries. this is what great architects and designers do: they don't write every line, but they hold the system design and guide toward coherence. agents are just very fast, very literal team members. the danger is skipping the thinking because ai makes it feel optional. people prompt their way into codebases they don't understand. can't debug because they never designed it. can't extend because there's no structure, just accumulated features. people who think deeply about systems can now move 100x faster. you spend time on the hard problem – understanding what you're building and why – and ai handles mechanical translation. you're not bogged down in syntax, so you stay in the architectural layer longer. the future isn't "ai replaces programmers" or "everyone can code now." it's "people who think clearly about systems build incredibly fast, and people who don't generate slop at scale." the skill becomes: holding complexity, breaking it down cleanly, communicating structure precisely. less syntax, more systems. less implementation, more architecture. less writing code, more designing coherence. humans are great at seeing patterns, understanding tradeoffs, making judgment calls about how things should fit together. ai can't save you from unclear thinking – it just makes unclear thinking run faster.
English
135
426
2.8K
226.3K
Jesse أُعيد تغريده
Peter Kazanjy
Peter Kazanjy@Kazanjy·
Founders: The winning sales deck structure: 1. Market forces (why now) 2. Current challenges (their pain) 3. Future vision (the dream) 4. Your solution (the bridge) 5. Proof points (why believe) 6. Next steps (the path) Tell a story, don't list features.
English
9
36
590
26.8K
aneri
aneri@0xAneri·
I lead AI acceleration for our product discipline at @coinbase If you’re doing it right, the mexican standoff isn’t PM vs. designer vs. engineer. It’s you vs. the version of you still working like it’s 2023 or even 2025. We focus on using AI to work better with design and eng (shared context, collaborating more easily, faster from idea to ship) and constantly trying to disrupt ourselves as PMs.
a16z@a16z

“There’s a Mexican standoff happening between product manager, designer, and coder.” Marc Andreessen on how AI is reshaping core tech roles: “Every coder now believes they can also be a product manager and a designer, because they have AI. Every product manager thinks they can be a coder and a designer. And every designer knows they can be a product manager and a coder.” “People in each of those roles now know or believe that with AI, they don’t need the other two roles anymore.” @pmarca on Lenny's Podcast with @lennysan

English
19
3
135
12K
Jesse أُعيد تغريده
Tech with Mak
Tech with Mak@techNmak·
"Programmers will automate themselves out of existence." That's what they said. And programmers laughed so hard they couldn't respond. Two years into the AI revolution, here's what actually happened: What the doomers predicted: 1./ AI writes all the code 2./ Developers become obsolete 3./ Only managers and marketers survive 4./ Programming becomes a dead career What actually happened: 1./ AI writes code that needs debugging by developers 2./ Developers spend more time reviewing AI output than writing from scratch 3./ The skill gap between good and bad developers got WIDER, not narrower 4./ Demand for senior developers who understand what AI can't do went UP The brutal irony nobody saw coming: AI didn't replace developers. It replaced the developers who thought AI would do their job for them. Here's the real shift: - Junior devs who learn to prompt AI? Productive. - Senior devs who understand system design? Irreplaceable. - Developers who just copy-paste without understanding? Already obsolete (AI just made it obvious). - Managers who thought they could skip hiring developers? Drowning in unmaintainable AI-generated code. We're not laughing because we're safe. We're laughing because the people who predicted our extinction don't understand what we actually do. AI is a tool. And like every tool before it, it makes good developers better and exposes bad developers faster.
Tech with Mak tweet media
English
79
89
863
126.3K