Aktivitäten
2433 Follower:innen
-
Felipe Pelizaro Gentil hat dies geteiltFelipe Pelizaro Gentil hat dies geteiltQuer fazer parte de um time curioso que busca inovação e as melhores tecnologias? Estamos com uma oportunidade para atuar como Software Engineer Sr. em uma das nossas squads. Se interessou? É só compartilha com a gente o seu perfil do LinkedIn no link de “candidatura simplificada” que está nos comentários. #tecnologia #ruby
-
Felipe Pelizaro Gentil hat dies geteilt🚀Felipe Pelizaro Gentil hat dies geteiltPalestrante confirmado para o DevConf 2020!! Felipe Pelizaro Gentil Desenvolvedor desde 2011 e cozinheiro nas horas vagas! Trabalho com Ruby desde 2012 e atualmente trabalhando com Ruby e Python na CargoX, uma startup na área de transportes no Brasil, situada em São Paulo. A Palestra dele será: Uma jornada pelos seus microsserviços com BFF e GraphQL - Um aplicação com o tempo tende a crescer devido a demanda do negócio. - Temos um problema! O que fazer? - Separar o frontend e quebrar o backend em diversos serviços. E agora? - Temos n problemas! Em termos técnicos, o frontend precisa agora entender as diversas APIs e muitas vezes transformar os dados antes de exibir ao usuários final. E se adicionarmos um novo frontend, como um aplicativo mobile? BFF (backend for frontend) é um padrão que tem, por ideia principal, criar um backend único por frontend. E junto com GraphQL, onde toda a flexibilidade dos dados obtidos é dada ao próprio cliente. A ideia da palestra é mostrar o dinamismo que GraphQL nos dá pela sua capacidade de funcionar em diversos protocolos, e utilizar um padrão onde as APIs estão diretamente ligadas ao usuário final. Garanta seu ingresso para o evento em https://devconf.com.br/
-
Felipe Pelizaro Gentil hat dies geteiltFelipe Pelizaro Gentil hat dies geteiltEstamos en busca de mais um tripulante para a jornada de transformar o futuro dos transportes no Brasil! Aqui na CargoX, você pode ajudar a transformar a vida de milhões de pessoas e criar condições melhores para caminhoneiros e suas famílias! #ProductManagersUnite! #LogTech #CargoX #Product
-
Felipe Pelizaro Gentil hat dies geteiltFelipe Pelizaro Gentil hat dies geteiltNo Walmart.com, estamos com vagas abertas em várias áreas: Marketing, Comercial, TI, entre outras áreas. Se tiver interesse, visite o nosso site (https://goo.gl/sP1u6A) ou LinkedIn (https://goo.gl/Dib5A9).
-
Felipe Pelizaro Gentil gefällt dasFelipe Pelizaro Gentil gefällt dasRisk rarely enters a project loudly. Most of the time, it appears as a small hesitation in the middle of an otherwise normal conversation. Someone wonders whether the permissions model is going to be simple. Someone else asks if we really know that customers need this. Design notices that the happy path looks fine, but the first-user experience is still mostly assumed. None of those questions feels dramatic enough to stop the work, so the team keeps moving. The idea becomes a roadmap item, the roadmap item becomes tickets, and the tickets become estimates. From the outside, that can look like progress. But sometimes what is really happening is that uncertainty is being converted into commitment too early. That is when risk becomes expensive. Not because risk exists, but because it stayed private for too long. This is why I like the idea of a Risk Sketch: a small moment before the initiative hardens, where Product, Design, and Engineering make the important uncertainty visible enough to decide what to do next. Not to remove risk. Not to create another process. Just to avoid discovering the wrong thing when changing direction is already painful. In the third post of my series, The Engineering Team Operating Layer, I explore how a Risk Sketch can help teams surface risk before it becomes rework. 👉 Link to the post in the first comment! What is one risk your team usually discovers later than it should? #SoftwareEngineering #EngineeringLeadership #ProductEngineering #TeamCulture
-
Felipe Pelizaro Gentil gefällt dasFelipe Pelizaro Gentil gefällt dasAfter a team meeting this week, I kept thinking about a strange kind of engineering work: the kind that leaves no commit. The meeting was about workflow, delivery rhythm, and how we could use AI deliberately as part of the development process. I had prepared a proposal, but the useful part began when the proposal stopped being mine. People asked questions, added context, challenged parts of it, and treated the conversation as something we could shape together. If you have ever brought an unfinished idea into a team, you know the small pause before the room tells you what kind of culture you are in. Someone unmutes. A cursor moves through the shared notes. The first question lands, and you can feel whether the team is trying to protect the current shape of things or understand what might become better. That moment made something visible quickly: not all engineering value appears in the codebase. In AI-accelerated teams, this becomes even more important. Code is not becoming worthless, but it is becoming less scarce. First drafts arrive faster, prototypes take less time, and implementation can begin before the product question has fully settled. The scarce work moves toward judgment: naming assumptions, making validation visible, deciding what should not be built, and keeping the work pointed at the user. Some of that judgment appears in PRs, but much of it happens before and around them. It appears in planning conversations, review habits, shared notes, retro follow-ups, and the small team practices that turn private experience into shared learning. None of that looks as clean as a merged diff. But it may change the next ten diffs. I wrote about the engineering work that leaves no commit — and why, in AI-accelerated teams, leadership may look less like control and more like stewardship: helping a team think better before it ships faster. 👉 Link to the post in the first comment! What kind of invisible engineering work does your team consistently undervalue? #SoftwareEngineering #EngineeringLeadership #AITools #TechCulture
-
Felipe Pelizaro Gentil hat darauf reagiertFelipe Pelizaro Gentil hat darauf reagiertIt's hard to put into words how I feel after this last weekend. I am spent. Emotionally and physically drained. At the same time, I feel on top of the world. It's the week after RubyConf Austria, and I still can't quite believe we pulled this off. Rubyists from all over the world came to Vienna, first to the Haus der Musik and then to Das MuTh, to listen to talks, hear music, and - most importantly - spend time with each other. A few moments keep coming back to me. The Chorus Juventus from the Wiener Sängerknaben opening the morning in Das MuTh. Nadir and Iman Hosic playing piano and moving me to tears. Bozhidar making me laugh like I was watching Austrian Kabarett - except the stage was classy and the topic was RuboCop. Chad playing sax, then leading the room through “Happy Birthday” while everyone sang along. Dave Thomas' closing keynote bringing us back to the roots and reminding us what it means to write Ruby. That mix is what made the weekend special to me. Of course, the talks were excellent and the speakers were people I have admired for years. Still, the weekend never felt like just a talk track. It felt like a conference, sure, but also like an expensive scheme to make Rubyists hang out in Vienna for a weekend. And it worked! I got to catch up with old friends and make new ones. I got to meet people I have followed online for years. I had conversations in hallways, over drinks, between sessions, and in the small bits of chaos that inevitably happen when you try to run a conference. I am incredibly grateful that I got to play a small part in making all of that possible. Thank you to Muhamed Isabegovic. Your dedication and vision are inspiring to me and, I know, to many others. Thank you to Zehra Bučo for the incredible visuals and concept. I've said this before, but people kept telling me how good RubyConf AT looked, unprompted, so you know they mean it! Thank you to the rest of the team, the program committee, our sponsors, the speakers, the performers, and everyone else who helped make this happen. And last but not least, thank you to everyone who showed up! From legends like Dave and Chad to all the rest of us - you are what makes the Ruby community what it is.
-
Felipe Pelizaro Gentil gefällt dasFelipe Pelizaro Gentil gefällt dasDepois de 7 anos e 4 meses, tomei uma das decisões mais importantes da minha vida: seguir um novo caminho. Um caminho único, que eu jamais conseguiria recuperar se deixasse passar. E que privilégio poder escolher… me sinto verdadeiramente abençoada. Na Frete.com , cresci e muito como profissional e como pessoa. Eu já carregava comigo um propósito claro há bastante tempo, e foi há sete anos que decidi que queria transformar o transporte de cargas por meio da tecnologia, conectando isso ao meu desejo de impactar vidas. Comecei em Recrutamento e Seleção, e lembro até hoje do dia em que a Camila Monteiro Casanova me ligou com a proposta. Eu tinha um dia para pensar… mas, na verdade, nem pensei. A conversa, a história da empresa e a visão do Federico Vega fizeram meus olhos brilharem tanto que a única resposta possível era: bora. Foram 9 meses intensos focada em Recrutamento, ajudando a construir os times de Tecnologia e Produto da CargoX. Depois, veio minha primeira promoção: além de seguir atraindo os melhores talentos do mercado, assumi também o papel de HRBP, no início da Fretebras (com menos de 50 pessoas) e apenas um ano de casa, me tornei sócia da empresa. Foram quase 4 anos nessa posição, assumindo cada vez mais novas responsabilidades e áreas e foi ali que tive ainda mais certeza do meu propósito. Mais do que contratar pessoas, eu estava impactando histórias, acompanhando jornadas e contribuindo para o desenvolvimento de tantas pessoas incríveis. E que histórias! ❤️ Ao longo do caminho, as conexões com diferentes áreas e pessoas me fizeram crescer e assumir novos desafios. Ainda como HRBP assumi a área de Talent, depois Comunicação Interna e Cultura, me tornei Gerente e, mais tarde, também liderei Treinamento. Foram horas e horas de dedicação, noites, finais de semana, muita, muita entrega (pessoal e profissional) e em 7 anos, 6 grandes reconhecimentos. E então, a vida e Deus me surpreenderam com o maior presente de todos. Depois de tantas conquistas profissionais, veio a maior promoção da minha vida: me tornei mãe. Que responsabilidade e confiança o maior Líder poderia depositar em mim. E, com isso, veio também o momento de pausar, refletir e direcionar minha energia para o que agora é prioridade: minha Maria Luiza. Saio da Frete com o coração cheio de gratidão e com a sensação genuína de dever cumprido. Levo comigo tudo o que vivi, aprendi e construí ao longo desses anos. Meu muito obrigada a cada pessoa que fez parte dessa história. ❤️ Mundo corporativo, em breve eu volto.
-
Felipe Pelizaro Gentil gefällt dasFelipe Pelizaro Gentil gefällt dasMy "lightning" talk from last month is online. Me, starting an affaire with Claude over refactoring Trailblazer. Thanks Visuality for throwing this party, it was great fun in Krakow! https://lnkd.in/dUBzNk3K
-
Felipe Pelizaro Gentil gefällt dasFelipe Pelizaro Gentil gefällt dasI wrote here a few posts ago how coding agents write features and tests with increasing ease and pace these days. That's the new default. The bottleneck for teams running production apps has shifted from making code changes to reviewing and owning them. The same number of people look through more and more diffs per day, and it's on them to ensure quality doesn't decline across the board. But agents have blind spots. They test until the happy path works and then move on. So I ran a weekend experiment: same coding task, complex enough to be realistic, given to Opus and Sonnet with and without an active test coverage feedback loop powered by undercover. Yes, I built the same app four times, so you don't have to. All four builds passed a blind test suite eventually, but the paths there were different. The plain runs: - Finished at 65-75% branch coverage - Contained more (and more severe) functional bugs - Required more fix rounds The skilled runs: - Produced fewer, surface-level bugs - Ended at a healthier test-to-implementation LOC ratio - Removed dead code actively instead of leaving it in - Took more turns and cost ~2x more to complete The insight: current models know how to test well, but an active coverage constraint with the right scope doesn't just produce higher coverage numbers to make you feel good, it influences the correctness and quality as code is being produced. Full writeup with data and examples in the comments.
-
Felipe Pelizaro Gentil gefällt dasFelipe Pelizaro Gentil gefällt dasRuby Community Conference 2026 - now on YouTube 🎥 All main talks and lightning talks from this year’s edition are now live. Whether you joined us in Kraków or missed it - now’s your chance to (re)experience the conference: 🎤 Obie Fernandez - Ruby & AI conversation https://lnkd.in/dUUCDP5v 🎤 Marco Roth - Herb and ReActionView https://lnkd.in/dZVrkjUA 🎤 Carmine Paolino - Ruby Is the Best Language for Building AI Web Apps https://lnkd.in/dtHZ39j2 ⚡ Lightning talks: Chris Hasiński - Doom https://lnkd.in/dH2u3mDH Nick Sutterer - The Story https://lnkd.in/dtWg7XjQ Paweł Strzałkowski - Make a game with Ruby and Model Context Protocol https://lnkd.in/diXYhPT5 Huge thanks again to all speakers for sharing their knowledge and energy on stage. And if this makes you wish you were there… we’re already thinking about the next edition 👀
Berufserfahrung und Ausbildung
-
SeQura
Gesamte Berufserfahrung von Felipe Pelizaro Gentil anzeigen
Jobbezeichnung, Beschäftigungsdauer und mehr ansehen.
oder
Projekte
-
Hermes
–Heute
Project for Walmart Supply Chain area, providing a platform to support the exchange of order tracking (deliveries and returns), freight agreement, NotFis (income cargo) and a web portal for brazilian and global carriers.
Andere Mitarbeiter:innen -
Sprachen
-
Portuguese
Muttersprache oder zweisprachig
-
English
Muttersprache oder zweisprachig
-
Spanish
Gute Kenntnisse
Erhaltene Empfehlungen
-
LinkedIn Mitglied
1 Person hat Felipe Pelizaro Gentil empfohlen
Jetzt anmelden und ansehenWeitere ähnliche Profile
Weitere Beiträge entdecken
-
Sasikumar S
🌟 Your Code Compiles. Does Your Persona? 🔍 Coming from a background in English Literature, I was trained to see the world in narratives and symbols—semiotics. I’ve learned this is not just for analyzing Shakespeare; it's the secret framework for tech leadership. Your posture, your handshake, your choice of a shirt over a hoodie in a certain meeting—these aren't random acts. They are deliberate statements in the silent language of professional trust. Before you present a solution, your body language has already presented a premise. Studies in communication suggest that in a first impression, over half of the perceived message is conveyed non-verbally. So, here is my challenge to the brilliant engineers, architects, and problem-solvers in my network: Apply your formidable systems-thinking mindset to your own professional interface. Conduct a code review on your persona. ✅ Refactor Your Non-Verbal Cues: This is your human UI/UX. · Maintain eye contact for 40-60% of a conversation to signal engagement. · Use open-palm gestures within the "power sphere" from your chest outward to project openness and control. · Stand with a stable, wide stance—it’s not just posture, it’s a non-verbal stack trace showing confidence. ✅ Optimize Your Personal Branding: The Halo Effect is Real. · In tech, we trust clean, well-commented code. People similarly attribute competence and attention to detail to a polished, intentional appearance. · Your attire is the visual syntax of your personal brand. Choose fits and colors that work for your environment without erasing your style. ✅ Debug Your Verbal & Para-Verbal Communication: · Eliminate filler words ("um," "like")—they are the console.log statements you forgot to remove. · Speak with optimal volume and clarity. Your voice is part of your toolkit—instrumental, not incidental. We operate in an industry that venerates hard skills. But remember: your soft skills are the API through which your technical genius is accessed. A Harvard study noted that a staggering 85% of career success comes from well-developed interpersonal skills and emotional intelligence. Your ability to lead a team, influence a stakeholder, or collaborate on a cross-functional project hinges here. Stop letting your professional persona be an untested, legacy module. Design it, iterate on it, and deploy it with the same intent you bring to your craft. #SoftwareEngineering #PersonalBranding #EnglishMajorInTech 💬 Discussion Prompt: "Do you believe the 'soft skills gap' is a bigger career limiter than the technical skills gap in our industry? Why or why not? Share your experiences below." P.S. Seeking a community that focuses on the complete developer? Join skAI – Daily Developer Learning Community for insights on growth and opportunity. Follow Sasikumar S for practical developer resources. Repost to fuel this essential conversation within your network. 📧 Connect for collabs: sasiias2024@gmail.com 🌐 Visit: sk-techland.web.app
5 Kommentare -
Nicolas Dular
We walked, we talked, and realized: We never got promoted to Senior 😬 This week, we’re diving deep into Engineering Career Ladders and why it's hard to get promoted. Also, Philipp kicks off a brand new segment: Frontend Drama of the Week. And also in this episode: - 🐍 Oban's Python background job library - 🔔 Why Postgres LISTEN/NOTIFY is usable again - 🚀 Postgres sharding solutions from PgDog, Supabase and PlanetScale Link to the episode is in the comments!
3 Kommentare -
Joseph Allen (ジョセフ・アレン)
How I would hire a frontend developer in 2025 It is late 2025. You post a role on LinkedIn and within days you have 250 applications. You start thinking about finding a recruiter to filter CVs for you. The best candidates either ignore your tech test or have already taken another job by the time you open their CV. Here is the playbook I use to hire frontend developers today. 📝 Write a clear job description Be upfront about the tech stack. If the role is mainly in Python, say so. Make it obvious so developers who want to code in something else can quickly see if it is not for them. Clear matching saves time for both sides. 🌐 Post in trusted spaces first If the role is in office in Tokyo, do not post it globally on LinkedIn Jobs straight away. Start with meetup organisers, active Slack or Discord communities, or recruiters who are trusted within those groups. This is where you find candidates with a proven and ongoing commitment. ⚡ Respond quickly to CVs When CVs arrive, skim them and reply promptly. The strongest candidates will not still be available if you wait weeks to build up a pile of applications. 💻 Look for evidence of programming Even a dusty portfolio site or a dormant GitHub profile is better than nothing. It shows the candidate has written some code outside of a CV bullet point. That is always a positive signal. ⏱️ Use short practical tests if needed If a CV has no clear evidence but you still want to progress, set an equal time test. Keep it light and fair. For example, a 15 minute React button app or a short dataset review. With an experienced developer reviewing the output, you can often get a reliable sense of ability. You can run four of these in an hour. 🤝 Focus on collaboration Once you know they can code, the real question is whether you can work with them. Ask their opinion on a language or framework, then challenge it. Share your view. See if they can argue well but also listen. Ask how they would start a brand new project. This shows you their thinking style and attitude to teamwork. 🏛️ Manage stakeholder approval Often a final step involves senior leadership. This can be intimidating for candidates. Make sure they know you are already impressed, and that this is either formality or part of the job. Be clear if winning over a senior stakeholder is an actual requirement. ✨ The outcome If you follow this process, you make an offer having seen both technical evidence and cultural fit. You hire in a human first way, without wasting weeks of time or filtering for the most desperate and time rich applicants. Those candidates are rarely the best choice.