Loading video...

Video Failed to Load

Go Home

We're hiring! We've got roles open for: /Software Engineer, Growth /Software Engineer, Product /Design Engineer /Senior Software Engineer, Payments /Senior Software Engineer, Identity & Access /Senior Software Engineer, Product /Senior Software Engineer, Developer Platform /Sales Development Representative /Account Executive /Tax Operations Specialist /Customer Experience Specialist /Account Manager /Customer Activations...

warpdotco's profile picture

Warp

6,404 subscribers

11,231 views • 1 month ago •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Come ship with us as we deploy robots faster than ever before possible. Ultra is hiring across engineering, manufacturing, and operations: — Senior Machine Learning Engineer — Application Engineer — Senior Mechatronics Engineer – R&D — Senior Mechatronics Engineer – Robot Platform — Supply Chain/Manufacturing Engineer — Robot Assembly Technician — Robot Lab Manager (2nd Shift) — Robotics Field Support Engineer — Robotics Software Engineer Careers page linked in comments. ↓
0:23

Come ship with us as we deploy robots faster than ever before possible. Ultra is hiring across engineering, manufacturing, and operations: — Senior Machine Learning Engineer — Application Engineer — Senior Mechatronics Engineer – R&D — Senior Mechatronics Engineer – Robot Platform — Supply Chain/Manufacturing Engineer — Robot Assembly Technician — Robot Lab Manager (2nd Shift) — Robotics Field Support Engineer — Robotics Software Engineer Careers page linked in comments. ↓

Ultra

50,094 views • 4 months ago

Joakim Recht (Uber Distinguished Eng) on tech leads: "Software engineers need to write code. If you're not writing code, you're not a software engineer." Joakim grew from a Senior Engineer to a Distinguished Engineer at Uber and I asked him what it took to get there. We covered: • The project that grew his career • What makes a great software engineer • Learnings from promo committees • When promos are unfair • Biggest technical mistake at Uber in hindsight • Advice for his younger self 𝗣𝗼𝗱𝗰𝗮𝘀𝘁 𝗹𝗶𝗻𝗸𝘀: • YouTube: • Transcript: • Spotify: • Apple:
0:57

Joakim Recht (Uber Distinguished Eng) on tech leads: "Software engineers need to write code. If you're not writing code, you're not a software engineer." Joakim grew from a Senior Engineer to a Distinguished Engineer at Uber and I asked him what it took to get there. We covered: • The project that grew his career • What makes a great software engineer • Learnings from promo committees • When promos are unfair • Biggest technical mistake at Uber in hindsight • Advice for his younger self 𝗣𝗼𝗱𝗰𝗮𝘀𝘁 𝗹𝗶𝗻𝗸𝘀: • YouTube: • Transcript: • Spotify: • Apple:

Ryan Peterman

72,291 views • 9 months ago

Rahul Gandhi getting 🩴🩴 shots from software engineers, startup entrepreneurs, and CEOs, at Technopark in Kerala. Rahul Gandhi: What do people like me need to do for you to compete with DJI successfully ? Answer me that question. Software Engineer: Sir, I'm proud to say that within the next three years we will be competing with DJI because 80% of the components right now we're developing in house in Kochi. Maybe our rest of the R&D is finishing in three years. Rahul Gandhi: You make your own motors ? Software Engineer : Yes, own motors. 🩴🩴🩴💥 Rahul Gandhi: What type of motors do you make ? Software Engineer : BLDC motors.🩴💥 Rahul Gandhi: What size drones do you make ? Software Engineer : Size largely carrying 50 to 100 kg payload. Rahul Gandhi: Can I come and see ? Speaker A: Yes. Rahul Gandhi: Where is it? Software Engineer : Kochi, sir. I also brought some of our product to showcase to you. Rahul Gandhi: Here itself ?? Software Engineer: Yes. In my bag. 🩴🩴🩴🩴💥💥
1:20

Rahul Gandhi getting 🩴🩴 shots from software engineers, startup entrepreneurs, and CEOs, at Technopark in Kerala. Rahul Gandhi: What do people like me need to do for you to compete with DJI successfully ? Answer me that question. Software Engineer: Sir, I'm proud to say that within the next three years we will be competing with DJI because 80% of the components right now we're developing in house in Kochi. Maybe our rest of the R&D is finishing in three years. Rahul Gandhi: You make your own motors ? Software Engineer : Yes, own motors. 🩴🩴🩴💥 Rahul Gandhi: What type of motors do you make ? Software Engineer : BLDC motors.🩴💥 Rahul Gandhi: What size drones do you make ? Software Engineer : Size largely carrying 50 to 100 kg payload. Rahul Gandhi: Can I come and see ? Speaker A: Yes. Rahul Gandhi: Where is it? Software Engineer : Kochi, sir. I also brought some of our product to showcase to you. Rahul Gandhi: Here itself ?? Software Engineer: Yes. In my bag. 🩴🩴🩴🩴💥💥

Dr Poornima 🇮🇳

102,247 views • 5 months ago

Srilatha (Bobbie) Manne, senior fellow and software development engineer, shares how designing for product energy efficiency benefits our customers and the environment. At AMD, we know our design choices have a broad impact, and we are proud of our engineers who bring these solutions to life. See how AMD is advancing with purpose:
0:25

Srilatha (Bobbie) Manne, senior fellow and software development engineer, shares how designing for product energy efficiency benefits our customers and the environment. At AMD, we know our design choices have a broad impact, and we are proud of our engineers who bring these solutions to life. See how AMD is advancing with purpose:

AMD

13,265 views • 4 months ago

.Amjad Masad : Creating software is going to be one of the most exciting areas. The average person will soon be as capable as what a senior software engineer is today, as we shift from doing the work to directing it. Instead of coding line by line, you’ll run multiple agents in parallel, building the frontend, refactoring the database, shipping features, all in the background. On top of that, you’ll have a clean interface to design and interact with AI more creatively. Software creation is moving from execution to orchestration, and soon, it won’t be a specialised skill, it’ll be the baseline.
0:47

.Amjad Masad : Creating software is going to be one of the most exciting areas. The average person will soon be as capable as what a senior software engineer is today, as we shift from doing the work to directing it. Instead of coding line by line, you’ll run multiple agents in parallel, building the frontend, refactoring the database, shipping features, all in the background. On top of that, you’ll have a clean interface to design and interact with AI more creatively. Software creation is moving from execution to orchestration, and soon, it won’t be a specialised skill, it’ll be the baseline.

Extraordinary

19,241 views • 5 months ago

The cost of software is going to zero. So what actually wins in 2030? Michael Watson (Ex-Citadel Head of Equities Engineering, now running Hedgineer): "The value accrual goes to companies that can offer incredible experiences." "The forward deployed engineer is the product." "The software they leave behind is going closer and closer to zero. But the FDE — that is the experience you want." "We take turnaround times from quarters down to hours." SaaS margins compress. The expertise behind the software doesn't. That's the model.
7:52

The cost of software is going to zero. So what actually wins in 2030? Michael Watson (Ex-Citadel Head of Equities Engineering, now running Hedgineer): "The value accrual goes to companies that can offer incredible experiences." "The forward deployed engineer is the product." "The software they leave behind is going closer and closer to zero. But the FDE — that is the experience you want." "We take turnaround times from quarters down to hours." SaaS margins compress. The expertise behind the software doesn't. That's the model.

Ethan Kho

138,027 views • 5 months ago

Some personal hot takes from AI: engineer Miami follows... 1. Software development is a dead-end profession because anyone can be a software developer now. 2. Anyone can use Cursor or any other tool and generate code. Being a coder and being a software engineer are different. 3. Computers used to be gated; now everyone has the power to make computers malleable. Everyone is a software developer now, but that does not mean they are software engineers 4. If you cannot demonstrate how a coding agent works, you are just a consumer and have imposed an artificial glass ceiling on your career as a software engineer. 5. If you are curious, you will have a job. If you have not been curious in the last two years, you are replaceable. 6. SaaS per-seat economics may become unstable as customers need fewer people to achieve results, prompting founders to think about new unit economics 7. Most companies will take two or three years (or more!) to figure out AI transformation. 8. Some companies are already building AI native teams of five to ten people who can build with the grain of AI 9. There will be an explosion in the number of software developers. Software development is now essentially free, and tokens are cheaper than humans 10. Not enough engineers know what it means to be a product engineer 11. JIRA ticket monkeys are cooked 12. If your company has banned AI, you should quit that company 13. AI is more like a musical instrument than just a tool play with it, make discoveries, build intuition learn where AI is good and where it fails
14:55

Some personal hot takes from AI: engineer Miami follows... 1. Software development is a dead-end profession because anyone can be a software developer now. 2. Anyone can use Cursor or any other tool and generate code. Being a coder and being a software engineer are different. 3. Computers used to be gated; now everyone has the power to make computers malleable. Everyone is a software developer now, but that does not mean they are software engineers 4. If you cannot demonstrate how a coding agent works, you are just a consumer and have imposed an artificial glass ceiling on your career as a software engineer. 5. If you are curious, you will have a job. If you have not been curious in the last two years, you are replaceable. 6. SaaS per-seat economics may become unstable as customers need fewer people to achieve results, prompting founders to think about new unit economics 7. Most companies will take two or three years (or more!) to figure out AI transformation. 8. Some companies are already building AI native teams of five to ten people who can build with the grain of AI 9. There will be an explosion in the number of software developers. Software development is now essentially free, and tokens are cheaper than humans 10. Not enough engineers know what it means to be a product engineer 11. JIRA ticket monkeys are cooked 12. If your company has banned AI, you should quit that company 13. AI is more like a musical instrument than just a tool play with it, make discoveries, build intuition learn where AI is good and where it fails

geoff

65,789 views • 2 months ago

'India can be the FDE factory for the world.' What is a Forward Deployed Engineer (FDE) and why is it becoming AI's hottest new job? Speaking to Shereen Bhan on Young Turks Reloaded, Fundamentum Co-founder Sanjeev Aggarwal says FDEs combine the skills of an engineer, product manager and AI architect to solve real business problems. 'It's almost like a unicorn... a 10x engineer.' He says a company can potentially build a $100 million business with just 100 FDEs, compared to 2,000–2,500 employees in a traditional IT services model. 'The gross margins can be as high as 70-80-90%.' As AI rewrites software development and companies like Microsoft ramp up hiring for FDE roles, Aggarwal believes India's decades of IT expertise could make it the world's biggest talent hub for this new category. Shereen Bhan
2:53

'India can be the FDE factory for the world.' What is a Forward Deployed Engineer (FDE) and why is it becoming AI's hottest new job? Speaking to Shereen Bhan on Young Turks Reloaded, Fundamentum Co-founder Sanjeev Aggarwal says FDEs combine the skills of an engineer, product manager and AI architect to solve real business problems. 'It's almost like a unicorn... a 10x engineer.' He says a company can potentially build a $100 million business with just 100 FDEs, compared to 2,000–2,500 employees in a traditional IT services model. 'The gross margins can be as high as 70-80-90%.' As AI rewrites software development and companies like Microsoft ramp up hiring for FDE roles, Aggarwal believes India's decades of IT expertise could make it the world's biggest talent hub for this new category. Shereen Bhan

CNBC-TV18

101,423 views • 1 month ago

What is it like to be a founding engineer at a startup, and how do you become one? Michelle Lim joined Warp as the founding engineer, and she's now a founder at Flint AI where she is hiring founding engineers. We talk through her journey and tactics helpful for anyone wanting to make an impact at a startup. Watch or listen: • YouTube: • Spotify: • Apple: Brought to you by: •⁠ Statsig ⁠ — ⁠ The unified platform for flags, analytics, experiments, and more. •⁠ Linear ⁠ — ⁠ The system for modern product development. I really liked how Michelle was realistic how, as a founding engineer, you have two jobs at once: #1: Software engineering. Build the stuff you need to do #2: Everything else to help the business succeed, including lots of things that are not to do with software engineering! Do all of these once you did job #1 well. In return, you get to learn a lot on how a business is built - which will help you if and when you become a founder yourself! Thanks for the great convo, Michelle, and keep it up!
0:58

What is it like to be a founding engineer at a startup, and how do you become one? Michelle Lim joined Warp as the founding engineer, and she's now a founder at Flint AI where she is hiring founding engineers. We talk through her journey and tactics helpful for anyone wanting to make an impact at a startup. Watch or listen: • YouTube: • Spotify: • Apple: Brought to you by: •⁠ Statsig ⁠ — ⁠ The unified platform for flags, analytics, experiments, and more. •⁠ Linear ⁠ — ⁠ The system for modern product development. I really liked how Michelle was realistic how, as a founding engineer, you have two jobs at once: #1: Software engineering. Build the stuff you need to do #2: Everything else to help the business succeed, including lots of things that are not to do with software engineering! Do all of these once you did job #1 well. In return, you get to learn a lot on how a business is built - which will help you if and when you become a founder yourself! Thanks for the great convo, Michelle, and keep it up!

Gergely Orosz

17,126 views • 8 months ago

Calling all senior developers! Applications are now open for the Andela AI Engineering Bootcamp. This intensive (and free!) program is designed to equip you with all the competencies you need to become a forward-deployed, enterprise-ready, and AI-fluent engineer. This training will combine a series of expert-led sessions with hands-on activities to make you a complete AI engineer over 10 weeks. Duration: 10 Weeks, kicking off on Monday, February 16. This program is open to technologists who: ✦ Have at least 8 years of experience as a software engineer. ✦ Have solid experience working with Python or Node.js, APIs, Databases, and software architecture. ✦ Good knowledge of TypeScript, modern frameworks like React or Next.js, and exposure to AI-related tools or libraries such as LangChain, OpenAI APIs, or vector databases. ✦ Can commit 40 hours per week for the next 10 weeks. ✦ A PC (not a phone) with an internet connection is required. Either Mac (Linux) or Windows. ✦ Are NOT employed full time, either with an Andela Client or externally. Apply here:
1:15

Calling all senior developers! Applications are now open for the Andela AI Engineering Bootcamp. This intensive (and free!) program is designed to equip you with all the competencies you need to become a forward-deployed, enterprise-ready, and AI-fluent engineer. This training will combine a series of expert-led sessions with hands-on activities to make you a complete AI engineer over 10 weeks. Duration: 10 Weeks, kicking off on Monday, February 16. This program is open to technologists who: ✦ Have at least 8 years of experience as a software engineer. ✦ Have solid experience working with Python or Node.js, APIs, Databases, and software architecture. ✦ Good knowledge of TypeScript, modern frameworks like React or Next.js, and exposure to AI-related tools or libraries such as LangChain, OpenAI APIs, or vector databases. ✦ Can commit 40 hours per week for the next 10 weeks. ✦ A PC (not a phone) with an internet connection is required. Either Mac (Linux) or Windows. ✦ Are NOT employed full time, either with an Andela Client or externally. Apply here:

Andela

457,133 views • 6 months ago

𝗝𝗼𝗶𝗻 𝘂𝘀 𝗠𝗼𝗻𝗱𝗮𝘆, 𝗝𝘂𝗹𝘆 𝟮𝟭 𝗮𝘁 𝟭𝟱:𝟬𝟬 𝗨𝗧𝗖 𝗳𝗼𝗿 𝗥𝗼𝘂𝗻𝗱𝘁𝗮𝗯𝗹𝗲 𝗧𝗮𝗹𝗸 #𝟭𝟴: 𝗔 𝗙𝗼𝗹𝗹𝗼𝘄-𝘂𝗽 𝘁𝗼 𝗡𝗲𝘀𝘁𝗲𝗱 𝗧𝗿𝗮𝗻𝘀𝗮𝗰𝘁𝗶𝗼𝗻𝘀 In December 2024, we held a foundational discussion on Nested Transactions, focused on building a baseline understanding of the concept. Since then, the conversation has matured. This Roundtable Talk creates space for a pluralistic dialogue, covering both the technical and governance dimensions. It’s an opportunity for builders, SPOs, protocol contributors, and ada holders to explore the stakes and surface a range of perspectives. 𝗔𝗺𝗼𝗻𝗴 𝘁𝗵𝗲 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀 𝘄𝗲’𝗹𝗹 𝗲𝘅𝗽𝗹𝗼𝗿𝗲: 🔹Where does the readiness stack for Nested Transactions currently stand? 🔹What are the alternatives, and what would be lost, or gained, by taking a different approach? 🔹What are the risks of complexity, and are there censorship-resistance concerns as raised by parts of the community? At the table will be: – Matthieu Pizenberg, Senior Software Engineer | CF (Host) – 🪏 Michele | Harmonic, Founder | Harmonic Labs – Alexey Kuleshevich, Software Engineer | IOG – Samuel Leathers, Head of Product, Core Tech | IOG – , CTO | FluidTokens – waalge, Founder | 🧵👇
0:27

𝗝𝗼𝗶𝗻 𝘂𝘀 𝗠𝗼𝗻𝗱𝗮𝘆, 𝗝𝘂𝗹𝘆 𝟮𝟭 𝗮𝘁 𝟭𝟱:𝟬𝟬 𝗨𝗧𝗖 𝗳𝗼𝗿 𝗥𝗼𝘂𝗻𝗱𝘁𝗮𝗯𝗹𝗲 𝗧𝗮𝗹𝗸 #𝟭𝟴: 𝗔 𝗙𝗼𝗹𝗹𝗼𝘄-𝘂𝗽 𝘁𝗼 𝗡𝗲𝘀𝘁𝗲𝗱 𝗧𝗿𝗮𝗻𝘀𝗮𝗰𝘁𝗶𝗼𝗻𝘀 In December 2024, we held a foundational discussion on Nested Transactions, focused on building a baseline understanding of the concept. Since then, the conversation has matured. This Roundtable Talk creates space for a pluralistic dialogue, covering both the technical and governance dimensions. It’s an opportunity for builders, SPOs, protocol contributors, and ada holders to explore the stakes and surface a range of perspectives. 𝗔𝗺𝗼𝗻𝗴 𝘁𝗵𝗲 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀 𝘄𝗲’𝗹𝗹 𝗲𝘅𝗽𝗹𝗼𝗿𝗲: 🔹Where does the readiness stack for Nested Transactions currently stand? 🔹What are the alternatives, and what would be lost, or gained, by taking a different approach? 🔹What are the risks of complexity, and are there censorship-resistance concerns as raised by parts of the community? At the table will be: – Matthieu Pizenberg, Senior Software Engineer | CF (Host) – 🪏 Michele | Harmonic, Founder | Harmonic Labs – Alexey Kuleshevich, Software Engineer | IOG – Samuel Leathers, Head of Product, Core Tech | IOG – , CTO | FluidTokens – waalge, Founder | 🧵👇

Cardano Community

51,202 views • 1 year ago

The three ways AI, particularly long-horizon agents, are changing the role of PMs: "First, product development is changing because the models and the capabilities are growing so fast that if you try to be very strict and stringent about describing exactly what you're going to build, its not going to work. It's very important for the PMs to be understanding of what these models are capable of and to be hands-on. The only thing PMs do now is articulate what the customer needs are at the highest level. But the actual product is built bottoms up by engineers, researchers, and product managers and designers all working together on the code itself. Second, the product manager and designer role are merging increasingly. When given the choice between an extra designer and extra engineer, they're saying, give us an extra engineer. And the other very important thing that's fundamentally different is non-deterministic software. Today, you could do X, Y happens. But if you do slight variation of X something completely different happens. That means someone has to evaluate whether or not what the software is producing is reasonable or not across various use cases. So the PM's job is to be very clear at a high level of what the user needs are, and then have a very clear sense of whether this product is good to ship or not by evaluating it."
2:58

The three ways AI, particularly long-horizon agents, are changing the role of PMs: "First, product development is changing because the models and the capabilities are growing so fast that if you try to be very strict and stringent about describing exactly what you're going to build, its not going to work. It's very important for the PMs to be understanding of what these models are capable of and to be hands-on. The only thing PMs do now is articulate what the customer needs are at the highest level. But the actual product is built bottoms up by engineers, researchers, and product managers and designers all working together on the code itself. Second, the product manager and designer role are merging increasingly. When given the choice between an extra designer and extra engineer, they're saying, give us an extra engineer. And the other very important thing that's fundamentally different is non-deterministic software. Today, you could do X, Y happens. But if you do slight variation of X something completely different happens. That means someone has to evaluate whether or not what the software is producing is reasonable or not across various use cases. So the PM's job is to be very clear at a high level of what the user needs are, and then have a very clear sense of whether this product is good to ship or not by evaluating it."

Patrick OShaughnessy

41,781 views • 6 months ago

Many people consider Linear the gold standard in B2B software. Their focus on craft, the end-user experience, and building strongly opinionated software is inspiring a new generation of founders. It's also one of the most beloved and fastest-growing B2B products out there today. In my conversation with Nan Yu (Nan Yu), head of product at Linear, we discuss: 🔸 Why it's a red flag if you think speed and quality are at odds 🔸 Linear’s philosophy on deadlines 🔸 The “double triangle” framework for product management 🔸 Nan’s systematic approach to creativity 🔸 Nan’s approach to landing his dream product roles 🔸 Their unique approach to product development 🔸 Much more Listen now 👇 • YouTube: • Spotify: • Apple: Thank you to our wonderful sponsors for supporting the podcast: 🏆 Sinch — Build messaging, email, and calling into your product: 🏆 Paragon — Ship every SaaS integration your customers want: 🏆 Wix Studio — The web creation platform built for agencies: it
1:18

Many people consider Linear the gold standard in B2B software. Their focus on craft, the end-user experience, and building strongly opinionated software is inspiring a new generation of founders. It's also one of the most beloved and fastest-growing B2B products out there today. In my conversation with Nan Yu (Nan Yu), head of product at Linear, we discuss: 🔸 Why it's a red flag if you think speed and quality are at odds 🔸 Linear’s philosophy on deadlines 🔸 The “double triangle” framework for product management 🔸 Nan’s systematic approach to creativity 🔸 Nan’s approach to landing his dream product roles 🔸 Their unique approach to product development 🔸 Much more Listen now 👇 • YouTube: • Spotify: • Apple: Thank you to our wonderful sponsors for supporting the podcast: 🏆 Sinch — Build messaging, email, and calling into your product: 🏆 Paragon — Ship every SaaS integration your customers want: 🏆 Wix Studio — The web creation platform built for agencies: it

Lenny Rachitsky

34,279 views • 1 year ago

🤝 Join QANplatform as Senior Developer Relations Engineer (DevRel) We're hiring a Developer Relations Engineer who speaks fluent code, content, and community. Ready to shape the future of Web3? At QANplatform, we're building the quantum-resistant hybrid blockchain designed for the next generation of secure, scalable applications, putting developers first with multi-language smart contract support and built-in developer royalty fees. 👀 We’re looking for someone who can help developers: - Discover and understand our platform - Adopt our tools and SDKs - Build incredible, world-changing projects on QANplatform 🖥️ What you’ll do As a Senior Developer Relations Engineer, you’ll be the bridge between our engineering team and the wider developer ecosystem. You will: - Translate complex technology into actionable insights - Champion developer needs within the organization - Build meaningful relationships with the community - Write sample code, tutorials, and blogs - Run hackathons, deliver workshops, and host live SDK demos - Be the voice of developers internally — and our public voice to the community externally 🦄 Why this role is different This isn’t a traditional DevRel position. You’ll move fluidly between: - Writing and reviewing code - Creating technical and educational content - Engaging developers through events, demos, and collaboration Ready to make an impact? If you’re excited about bridging the gap between developers and next-generation blockchain technology, we’d love to hear from you. Apply now and let’s build something extraordinary together. Fill in this form to apply:
0:33

🤝 Join QANplatform as Senior Developer Relations Engineer (DevRel) We're hiring a Developer Relations Engineer who speaks fluent code, content, and community. Ready to shape the future of Web3? At QANplatform, we're building the quantum-resistant hybrid blockchain designed for the next generation of secure, scalable applications, putting developers first with multi-language smart contract support and built-in developer royalty fees. 👀 We’re looking for someone who can help developers: - Discover and understand our platform - Adopt our tools and SDKs - Build incredible, world-changing projects on QANplatform 🖥️ What you’ll do As a Senior Developer Relations Engineer, you’ll be the bridge between our engineering team and the wider developer ecosystem. You will: - Translate complex technology into actionable insights - Champion developer needs within the organization - Build meaningful relationships with the community - Write sample code, tutorials, and blogs - Run hackathons, deliver workshops, and host live SDK demos - Be the voice of developers internally — and our public voice to the community externally 🦄 Why this role is different This isn’t a traditional DevRel position. You’ll move fluidly between: - Writing and reviewing code - Creating technical and educational content - Engaging developers through events, demos, and collaboration Ready to make an impact? If you’re excited about bridging the gap between developers and next-generation blockchain technology, we’d love to hear from you. Apply now and let’s build something extraordinary together. Fill in this form to apply:

QANplatform

10,755 views • 9 months ago

What are traits of standout software engineers? Here are great observations from Ebi Atawodi - currently Director of Product Management at YouTube Studio, and a former product leader at Netflix and Uber. I worked with Ebi for 4 years at Uber, and in this The Pragmatic Engineer podcast episode we go through how engineers, engineering managers and product managers can work better together. Watch or listen: • YouTube: • Spotify: • Apple: Brought to you by: • WorkOS — The modern identity platform for B2B SaaS • The Software Engineer’s Guidebook: Written by me (Gergely) – now out in audio form as well ---- Some of my takeaways: 𝟭. 𝗣𝗿𝗼𝗱𝘂𝗰𝘁-𝗺𝗶𝗻𝗱𝗲𝗱 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝘀 𝗴𝗲𝘁 𝗺𝗼𝗿𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝗱𝗼𝗻𝗲: 𝘀𝗼 𝗯𝗲𝗰𝗼𝗺𝗲 𝗼𝗻𝗲 — and if you are a PM or EM, help your engineers become one! One of the biggest gifts from Ebi, myself, and our engineering team was helping all of us become product-minded engineers. Ebi exposed us to how Product worked, made decisions, allocated headcount, and pitched new initiatives to be funded by the business. I wrote more on how to become a product-minded engineer. 𝟮. 𝗚𝗲𝘁 𝘁𝗼 𝗸𝗻𝗼𝘄 𝘁𝗵𝗲 𝗽𝗲𝗿𝘀𝗼𝗻 𝗯𝗲𝗵𝗶𝗻𝗱 𝘁𝗵𝗲 𝗘𝗠/𝗣𝗠/𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿/𝗰𝗼𝗹𝗹𝗲𝗮𝗴𝘂𝗲. At work, roles are somewhat artificial. What is not artificial is the person behind the role. It made a massive difference when I got to know the “real Ebi” behind “Ebi, the product manager” — and the other way around, about “Gergely, the engineering manager.” It’s a lot easier to trust a partner when you know more about them than “just” their role at work. 𝟯. 𝗙𝗼𝗰𝘂𝘀 𝗼𝗻 𝗱𝗼𝗶𝗻𝗴 𝗴𝗿𝗲𝗮𝘁 𝘄𝗼𝗿𝗸 𝗮𝘀 𝗮𝗻 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿 — 𝗳𝗶𝗿𝘀𝘁 𝗮𝗻𝗱 𝗳𝗼𝗿𝗲𝗺𝗼𝘀𝘁. As tempting as it is to “game the system” of performance reviews or promotions: both Ebi and I agree that you absolutely can game whatever system your company has in place to fast-track that next promotion, or try to get better performance reviews. But the people who do this, others around them notice — especially engineers! What speeds them up in the short term often slows them down in the long term. This is because more senior positions often need strong referrals: and someone who was visibly focused on their own advancement only can struggle to get these. Do standout work, help others when you can, and be kind to others around you, and years later, other standout colleagues could well tap your shoulder, wanting to recruit you to the companies they are currently at. This is how Ebi often got recruited for increasingly senior roles.
1:00

What are traits of standout software engineers? Here are great observations from Ebi Atawodi - currently Director of Product Management at YouTube Studio, and a former product leader at Netflix and Uber. I worked with Ebi for 4 years at Uber, and in this The Pragmatic Engineer podcast episode we go through how engineers, engineering managers and product managers can work better together. Watch or listen: • YouTube: • Spotify: • Apple: Brought to you by: • WorkOS — The modern identity platform for B2B SaaS • The Software Engineer’s Guidebook: Written by me (Gergely) – now out in audio form as well ---- Some of my takeaways: 𝟭. 𝗣𝗿𝗼𝗱𝘂𝗰𝘁-𝗺𝗶𝗻𝗱𝗲𝗱 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝘀 𝗴𝗲𝘁 𝗺𝗼𝗿𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝗱𝗼𝗻𝗲: 𝘀𝗼 𝗯𝗲𝗰𝗼𝗺𝗲 𝗼𝗻𝗲 — and if you are a PM or EM, help your engineers become one! One of the biggest gifts from Ebi, myself, and our engineering team was helping all of us become product-minded engineers. Ebi exposed us to how Product worked, made decisions, allocated headcount, and pitched new initiatives to be funded by the business. I wrote more on how to become a product-minded engineer. 𝟮. 𝗚𝗲𝘁 𝘁𝗼 𝗸𝗻𝗼𝘄 𝘁𝗵𝗲 𝗽𝗲𝗿𝘀𝗼𝗻 𝗯𝗲𝗵𝗶𝗻𝗱 𝘁𝗵𝗲 𝗘𝗠/𝗣𝗠/𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿/𝗰𝗼𝗹𝗹𝗲𝗮𝗴𝘂𝗲. At work, roles are somewhat artificial. What is not artificial is the person behind the role. It made a massive difference when I got to know the “real Ebi” behind “Ebi, the product manager” — and the other way around, about “Gergely, the engineering manager.” It’s a lot easier to trust a partner when you know more about them than “just” their role at work. 𝟯. 𝗙𝗼𝗰𝘂𝘀 𝗼𝗻 𝗱𝗼𝗶𝗻𝗴 𝗴𝗿𝗲𝗮𝘁 𝘄𝗼𝗿𝗸 𝗮𝘀 𝗮𝗻 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿 — 𝗳𝗶𝗿𝘀𝘁 𝗮𝗻𝗱 𝗳𝗼𝗿𝗲𝗺𝗼𝘀𝘁. As tempting as it is to “game the system” of performance reviews or promotions: both Ebi and I agree that you absolutely can game whatever system your company has in place to fast-track that next promotion, or try to get better performance reviews. But the people who do this, others around them notice — especially engineers! What speeds them up in the short term often slows them down in the long term. This is because more senior positions often need strong referrals: and someone who was visibly focused on their own advancement only can struggle to get these. Do standout work, help others when you can, and be kind to others around you, and years later, other standout colleagues could well tap your shoulder, wanting to recruit you to the companies they are currently at. This is how Ebi often got recruited for increasingly senior roles.

Gergely Orosz

19,552 views • 1 year ago

Within software architecture, few people shaped the industry as much as Grady Booch. Safe to say he's a true legend. In today's The Pragmatic Engineer Podcast episode, he shares fascinating stories, insights, observations. Listen or watch the full episode: - YouTube: - Spotify, Apple, or web: Thank you to our wonderful sponsors: 🌟 WorkOS — The modern identity platform for B2B SaaS. Learn more at 🌟Sevalla — Deploy anything from preview environments to Docker images. Check it out at 🌟Chronosphere — The observability platform built for control. Get details at --- 3 of my takeaways from this fascinating conversation: 1. Surprising: The US Department of Defense and the military built some of the most complicated software systems in the 70s and 80s. In the 70s, these organizations probably had the most code to deal with - globally! - and things like distributed computing were pioneered thanks to these use cases. 2. The three axes of software architecture Grady argues that when talking about software architecture, we should look at these three dimensions: ceremony, risk and complexity. 3. The economics of software and software architecture are always connected Machine time was very expensive in the 1960s and 1970s, and software had to be written from scratch. Good architecture meant writing highly performant code to utilize these rather limited machines. However, these days, machine time has gotten very cheap, and there are also plenty of “building blocks” at our disposal: from frameworks to cloud services. Software architecture is frequently still connected with cost: to decide on what services and technologies to use, taking the cost aspect into account! I hope you enjoy this conversation - together with a history overview of the last 50 years in software - as much as I did! Thanks a lot Grady Booch
0:43

Within software architecture, few people shaped the industry as much as Grady Booch. Safe to say he's a true legend. In today's The Pragmatic Engineer Podcast episode, he shares fascinating stories, insights, observations. Listen or watch the full episode: - YouTube: - Spotify, Apple, or web: Thank you to our wonderful sponsors: 🌟 WorkOS — The modern identity platform for B2B SaaS. Learn more at 🌟Sevalla — Deploy anything from preview environments to Docker images. Check it out at 🌟Chronosphere — The observability platform built for control. Get details at --- 3 of my takeaways from this fascinating conversation: 1. Surprising: The US Department of Defense and the military built some of the most complicated software systems in the 70s and 80s. In the 70s, these organizations probably had the most code to deal with - globally! - and things like distributed computing were pioneered thanks to these use cases. 2. The three axes of software architecture Grady argues that when talking about software architecture, we should look at these three dimensions: ceremony, risk and complexity. 3. The economics of software and software architecture are always connected Machine time was very expensive in the 1960s and 1970s, and software had to be written from scratch. Good architecture meant writing highly performant code to utilize these rather limited machines. However, these days, machine time has gotten very cheap, and there are also plenty of “building blocks” at our disposal: from frameworks to cloud services. Software architecture is frequently still connected with cost: to decide on what services and technologies to use, taking the cost aspect into account! I hope you enjoy this conversation - together with a history overview of the last 50 years in software - as much as I did! Thanks a lot Grady Booch

Gergely Orosz

55,813 views • 1 year ago

Bob McGrew (Bob McGrew) helped build some of the most influential technologies of the past two decades. He was an early engineer at PayPal, an early executive at Palantir—where he helped pioneer the Forward Deployed Engineer (FDE) model— and was recently Chief Research Officer at OpenAI - where he led the development of ChatGPT, GPT-4, and o1. On this episode of Lightcone Podcast, he explains how FDEs became central to today's startups, why "doing things that don't scale at scale" works, and where he sees the biggest opportunities for founders working in AI. 00:29 – From PayPal to Palantir to OpenAI 02:19 – The Role of a Forward Deployed Engineer 03:19 – How Palantir Invented It 07:56 – Product Discovery in the Field vs. Sales 09:51 – Echo and Delta Teams Explained 13:34 – Training Ground for Founders 14:35 – Consulting or Real Software? 17:54 – The Birth of Palantir’s Ontology 23:04 – Why AI Companies Adopt It 36:17 – What Success Metrics Look Like 41:14 – Building with Demo-Driven Development 44:56 – Joining the US Army Reserve 47:43 – Opportunities for Founders
50:42

Bob McGrew (Bob McGrew) helped build some of the most influential technologies of the past two decades. He was an early engineer at PayPal, an early executive at Palantir—where he helped pioneer the Forward Deployed Engineer (FDE) model— and was recently Chief Research Officer at OpenAI - where he led the development of ChatGPT, GPT-4, and o1. On this episode of Lightcone Podcast, he explains how FDEs became central to today's startups, why "doing things that don't scale at scale" works, and where he sees the biggest opportunities for founders working in AI. 00:29 – From PayPal to Palantir to OpenAI 02:19 – The Role of a Forward Deployed Engineer 03:19 – How Palantir Invented It 07:56 – Product Discovery in the Field vs. Sales 09:51 – Echo and Delta Teams Explained 13:34 – Training Ground for Founders 14:35 – Consulting or Real Software? 17:54 – The Birth of Palantir’s Ontology 23:04 – Why AI Companies Adopt It 36:17 – What Success Metrics Look Like 41:14 – Building with Demo-Driven Development 44:56 – Joining the US Army Reserve 47:43 – Opportunities for Founders

Y Combinator

409,322 views • 11 months ago