“Vítor and I worked at IDwall, where we were software developers in distinct product development teams but worked together in various occasions. Vítor is very enthusiastic about his work and often engages with different projects, always concerned with making the company a good place to work: he is a “team player”, as they say. Vítor also pays close attention to new arriving technologies, testing them and bringing new knowledge to our consolidate processes in order to adapt and improve them. Last but not least, he is very communicative and fun to work with.”
Sobre
Senior Software Engineer with 12+ years of experience building and shipping user-facing…
Atividades
-
Commencing our team retreat in Tulum 🇲🇽 🌴 DM us w feature requests and we'll hack them out 🔨
Commencing our team retreat in Tulum 🇲🇽 🌴 DM us w feature requests and we'll hack them out 🔨
Vítor Capretz gostou
-
We have a new tradition for each time we add a million dollars in ARR. Million-dollar meals. Everyone on the team gets to take their loved ones out…
We have a new tradition for each time we add a million dollars in ARR. Million-dollar meals. Everyone on the team gets to take their loved ones out…
Vítor Capretz gostou
-
I'm hiring a Senior Full-Stack Engineer for my team at Netflix! I lead PANDA (Platform Applications and Domain Acceleration). We build the platforms…
I'm hiring a Senior Full-Stack Engineer for my team at Netflix! I lead PANDA (Platform Applications and Domain Acceleration). We build the platforms…
Vítor Capretz gostou
Experiência e formação acadêmica
-
Resend
Ver experiência completa de Vítor
Veja o cargo, tempo na empresa e muito mais dessa pessoa.
ou
Idiomas
-
Portuguese
Nível nativo ou bilíngue
-
English
Nível avançado
Recomendações recebidas
2 pessoas recomendaram Vítor
Cadastre-se agora para visualizarMais atividade de Vítor
-
June was full (& very busy) of Resend highlights ✨ Kelsey Mills & Ben Anderson joined the Ops team. They are both already building so many great…
June was full (& very busy) of Resend highlights ✨ Kelsey Mills & Ben Anderson joined the Ops team. They are both already building so many great…
Vítor Capretz gostou
-
Design como conhecemos morreu. E tem que morrer mesmo. Qualquer PM hoje monta uma tela funcional em 20 minutos, a era de fábrica de mock-up já…
Design como conhecemos morreu. E tem que morrer mesmo. Qualquer PM hoje monta uma tela funcional em 20 minutos, a era de fábrica de mock-up já…
Vítor Capretz gostou
-
After 14 years at Google, it's time for something new. Before I go, here's everything I wish someone had told the version of me who walked in the…
After 14 years at Google, it's time for something new. Before I go, here's everything I wish someone had told the version of me who walked in the…
Vítor Capretz gostou
-
QA is dead. Or at least, the old way of doing it is. AI now writes all your code. Does it still work? That's the gap: coding agents are scaling…
QA is dead. Or at least, the old way of doing it is. AI now writes all your code. Does it still work? That's the gap: coding agents are scaling…
Vítor Capretz gostou
-
the perfect startup swag doesn't exist...
the perfect startup swag doesn't exist...
Vítor Capretz gostou
-
Presented Say Cheese! to Apple CEOs at Apple Park 🍎 I had the incredible opportunity to present Say Cheese! at Apple Park to Tim Cook, Apple’s CEO,…
Presented Say Cheese! to Apple CEOs at Apple Park 🍎 I had the incredible opportunity to present Say Cheese! at Apple Park to Tim Cook, Apple’s CEO,…
Vítor Capretz gostou
Outros perfis semelhantes
Ver mais publicações
-
William Antônio Siqueira
I think I made the first citizen maintained open data REST API for the Brazilian government. The first ever, rest apis were not so popular at that time. The API is not working anymore (I would have to keep paying), but it was the first public API for Brazilian elections, back in 2010 https://lnkd.in/dVUXVzeb
-
Octavio Pitaluga Neto
𝐓𝐚𝐪𝐓𝐚𝐪 𝐢𝐧𝐭𝐞𝐠𝐫𝐚𝐭𝐞𝐝 𝐰𝐢𝐭𝐡 𝐒𝐲𝐦𝐩𝐥𝐚 Later this week, we’ll announce the integration between TaqTaq and Sympla, leading events organization platform in Brazil. This new feature will be highly beneficial for all event organizers who use Sympla as their main platform. Here’s how it will work: * The event organizer creates an account on TaqTaq. * They connect their TaqTaq account to their events on Sympla. * Everyone who confirms attendance at the event will be invited by TaqTaq to download the app. The free version includes 2 digital cards and up to 50 contacts. * Attendees will arrive at the event with a shared networking tool. 𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 1. A much richer networking experience; 2. Faster and easier contact capture; 3. Increased business opportunities; 4. Environmentally friendly & sustainable; 5. No wasted time transferring data to digital platforms; 6. CRM integration (Pipedrive) coming soon; 7. Organized digital presence; 8. Management of large volumes of events and participants; 9. Easy re-invitation for future events; 10. Notifications about updates and news to contacts. We invite all Sympla event organizers to download TaqTaq now and offer this enhanced experience to participants at their upcoming events. We can also develop this same integration with other event platforms, as well as with organizers’ own event pages and systems. Interested? Schedule a web conference with us. 𝗟𝗲𝘁´𝘀 𝗧𝗮𝗾? That’s the new question. #Sympla #TaqTaq #integration #eventorganizers #events #CRM #Pipedrive
-
🐔 Guilherme Dalla Rosa
Just got my hands on the early access of "Node.js Design Patterns" 4th edition by 🦁 Luciano Mammino and Mario Casciaro, and it's the most straightforward path I've seen to production-grade Node.js. Having worked with Luciano on multiple projects, I can tell you this book captures exactly the kind of pragmatic wisdom he brings to real-world architectural discussions. This new edition brings fantastic updates on TypeScript integration, Web Streams, and a new testing chapter that alone is worth the upgrade. What I love most? The authors don't just throw patterns at you - they show you when NOT to use them, which is honestly just as valuable. The real-world examples hit different when you've been burned by the exact anti-patterns they warn against (looking at you, callback hell survivors 😅). Whether you're scaling your first Node.js app or you're a seasoned dev looking to solidify your architectural game, this book delivers. Can't recommend it enough! #NodeJS #JavaScript #DesignPatterns #SoftwareArchitecture #Backend #Packt
2 comentários -
Pedro Piñera Buendia
Ubiratan Soares recently asked me about swift-build, and it got me thinking about Apple's build tooling ecosystem. While unifying build systems is definitely a step in the right direction—especially as Swift expands across platforms—there's a fundamental challenge: the persistent fragmentation of build graphs between Xcode projects and Swift packages. I'd love to see Apple provide clear direction on the path forward. Without that clarity, teams are stuck maintaining two separate graph representations, ensuring they remain reconciled, and dealing with bugs that emerge from this complexity. Build graph reconciliation is genuinely challenging, and splitting that effort across two systems compounds the difficulty. We're now seeing Swift Package interfaces adopting features that Xcode projects have had for years. Developers naturally want feature parity, which is understandable. However, this has created a liability: the Swift Packages interface has become an awkward mix of APIs for dependency management and interfaces for project-level configuration. These are fundamentally different use cases, and serving both creates friction. This tension forces Xcode to trigger asynchronous reconciliation processes that leave the IDE essentially unusable during execution. What's worse is the lack of meaningful UI—just a spinner with no insight into what's happening. For teams under tight deadlines, this is a genuine productivity blocker. If I were making these decisions, I'd commit to a unified solution and establish a long-term plan that addresses architectural decisions in Xcode that didn't pan out well. Many improvements would involve deprecating workaround features like "mergeable libraries." This shouldn't have been necessary—if the build system properly handled dynamic frameworks without requiring copy phases, we wouldn't need band-aid solutions. Technically, I don't think Swift in its current form is ideal for build configuration. You want something that evaluates instantly and prohibits environment access to ensure hermeticism. But when even Apple's packages perform I/O operations and break hermetic builds, we can't expect the broader ecosystem to maintain stricter standards. From an outside perspective, it appears the Swift and SwiftPM teams are pushing new capabilities forward while the Xcode team works to integrate those changes retroactively. There's significant investment in Swift Build—necessary infrastructure work—but it doesn't address fragmentation at higher architectural layers. That fundamental question about how these systems should converge remains unanswered. #Swift #SwiftPM #Xcode #iOSDevelopment #BuildSystems #DeveloperTools #SoftwareEngineering
2 comentários