<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Anaïs Engler on Medium]]></title>
        <description><![CDATA[Stories by Anaïs Engler on Medium]]></description>
        <link>https://medium.com/@aengler?source=rss-e26c8d38a542------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*wLGK3JQrcfPwa2esnxbQAg@2x.jpeg</url>
            <title>Stories by Anaïs Engler on Medium</title>
            <link>https://medium.com/@aengler?source=rss-e26c8d38a542------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:09:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aengler/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How AI made Java version updates a simple task]]></title>
            <link>https://medium.com/zenjob-tech-blog/how-ai-made-java-version-updates-a-simple-task-52369d8f1492?source=rss-e26c8d38a542------2</link>
            <guid isPermaLink="false">https://medium.com/p/52369d8f1492</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[claude]]></category>
            <category><![CDATA[migration]]></category>
            <dc:creator><![CDATA[Anaïs Engler]]></dc:creator>
            <pubDate>Fri, 31 Jul 2026 13:32:01 GMT</pubDate>
            <atom:updated>2026-07-31T13:32:01.857Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dzfoA-eK5I17ezVlOdltog.jpeg" /></figure><p>“That’s the easiest Java migration I have ever done.”</p><p>That’s a direct quote from a senior engineer on my team. And if you’ve ever done a migration, you know why that’s remarkable. Language version updates usually take multiple days per service; are difficult to estimate; and require refactoring code, fixing tests, and patching dependencies — all with high risk and no visible product impact. The more services the team owns, the more it multiplies the work. Not surprisingly, it’s not something product engineers enjoy working on.</p><p>So what changed? AI. Here’s how we upgraded the six Java services of our product domain at Zenjob, and how AI helped relieve many of our normal pain points.</p><h4><strong>Creating a gist</strong></h4><p>The project started with two team members focusing on one particular service with the goal of producing a step-by-step guide — in the form of a <a href="https://docs.github.com/en/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists">gist</a> — detailed enough to hand directly to Claude. As with any upgrade, the work began by updating the version numbers in the dependency files, building the app, and fixing errors one by one until the service became usable again. The two members pair-programmed, taking turns fixing issues while documenting their methodology, a process that took them three days to complete.</p><p>What made this gist particularly valuable was its depth. Code-wise, it was extremely thorough. For example, one of the needed steps is to update Gradle, and rather than reducing it to a simple “upgrade Gradle” sentence, the gist traces the entire causal chain and anticipates the upcoming issue in the class file. It details that Java 25 emits class file version 69 and that Gradle 8.x cannot parse it. Therefore, the surrounding plugin matrix must be reevaluated, and <a href="https://github.com/palantir/gradle-docker">Palantir’s Gradle Docker plugin</a> (which had reached end of life) ultimately ends up being replaced by Jib.</p><p>The gist also captures practical, hard-won knowledge and treats the official documentation as a starting point rather than the final authority — for example, noting that the official documentation points to the 2026.x line, while the latest compatible version for Boot 4.0 is 2025.1.x. Lastly, it covers more than the code changes themselves, detailing when to open a new PR, what to do in each branch, and in what order to proceed — all questions we would have asked ourselves if they weren’t included.</p><p>The result was a document that not only provided a solid estimate of the work required, but also prevented us from reinventing the wheel for each service and helped us adopt a coordinated approach across the team.</p><h4><strong>Splitting the work</strong></h4><p>We were a team of four engineers owning six different Java/Kotlin services. By the time we picked up the project, the original duo had moved on, so we inherited the gist and split the six services between us, and that’s when I joined the team. Because we had the gist, everyone — from the newest to the most experienced team member — could contribute. The only requirement was to have the services and Claude set up. Then we prompted Claude to follow the gist.</p><p>The main advantage of using AI instead of following the checklist manually is the simplicity of the process: It literally takes one click. As a result, it’s faster and requires much less mental effort. When following instructions manually, there’s always a risk of missing a small detail or misinterpreting a sentence. Once a mistake is made, you can end up going down the wrong path without realizing it, potentially resulting in hours of being stuck, needing to ask teammates for support, and spending additional time troubleshooting. With Claude, that risk is significantly reduced, because it follows the process step by step and carries out each task systematically, making it much less likely that an important step will be overlooked.</p><p>Java upgrades are usually considered senior-level tasks because they require domain and language expertise, but AI now provides the confidence to handle this kind of work at almost any engineering level. I’m new to the team and relatively new to backend engineering, and in a pre-AI world, I wouldn’t have volunteered to upgrade a service to Java 25; I instead would have focused on more straightforward tasks. But because I was equipped with the gist and Claude, I felt confident enough to take it on. This turned out to be baptism by fire, as I’d picked the only Kotlin service my team owns, in turn adding an extra layer of complexity. Thanks to this setup though, I was able to match the velocity of my teammates, which is a great feeling as a new team member.</p><h4><strong>Handling edge cases</strong></h4><p>Since the gist was originally written for one particular service, it didn’t cover every scenario. So what remained was handling errors and service-specific edge cases.</p><p>One example was the Kotlin service mentioned above, where I had to manually update the Kotlin version before following the gist. The Kotlin compiler dictates the maximum JVM bytecode target it can emit, and in this case, it was capped at Java 23. To reduce risk and keep the upgrade smooth, Kotlin had to be bumped first so it could target Java 25.</p><p>Another Kotlin-specific fix was telling Jib which class is the app’s entry point. In a Java service, the application’s entry point, main, lives in a single class, so Jib finds it on its own. In a Kotlin service, main is defined inside a companion object and the compiler emits it into two class files. Unfortunately, Jib couldn’t decide which one to use. But once again, Claude played an important role, turning what used to be a “digging through Stack Overflow for hours” type of situation into something solvable with a one-line prompt.</p><h4><strong>Validating the result</strong></h4><p>With this AI-powered setup, the output required only minor corrections; the repetitive work was covered and allowed us to focus on the edge cases that genuinely required our attention. We trusted the results enough to move quickly while still validating the final outcome. We determined that the results were good enough based on a few simple checks: The service started successfully without errors, there were no unusual logs or alerts in Grafana, and we continued monitoring it after deployment. For example, after the upgrade, we observed an increase in resource usage. This was expected as a consequence of the new version rather than an issue introduced during the implementation, and we adjusted the resource limits accordingly.</p><h4><strong>Sharing our experience</strong></h4><p>In one week, we completed the upgrade of all six services to both Java 25 and Spring Boot 4.</p><p>Because the process worked so well, we shared it with the broader engineering group at Zenjob so they would feel encouraged to apply the same approach within their own domains. <a href="https://github.com/zenjob/java-spring-migration-guide">And we’re sharing the gist here too.</a></p><p>Beyond the internal success of this upgrade, what strikes me most about this process was the quality of the experience. I hope this article gives you the confidence and motivation to try this approach for your next upgrade!</p><p><em>Thanks to Jose and Vova for the gist; to Bee, Daniel, and Ira for the teamwork; and to Julio for nudging me to turn this positive experience into a blog post :)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52369d8f1492" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zenjob-tech-blog/how-ai-made-java-version-updates-a-simple-task-52369d8f1492">How AI made Java version updates a simple task</a> was originally published in <a href="https://medium.com/zenjob-tech-blog">Zenjob Technology Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Turning an unpopular project into a team win]]></title>
            <link>https://medium.com/zenjob-tech-blog/turning-an-unpopular-project-into-a-team-win-b302609d5067?source=rss-e26c8d38a542------2</link>
            <guid isPermaLink="false">https://medium.com/p/b302609d5067</guid>
            <category><![CDATA[wordpress]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[php]]></category>
            <dc:creator><![CDATA[Anaïs Engler]]></dc:creator>
            <pubDate>Fri, 23 May 2025 10:46:03 GMT</pubDate>
            <atom:updated>2025-05-23T10:46:03.864Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Handmade staircase of wood cubes to express project success." src="https://cdn-images-1.medium.com/max/1024/1*0KntlGhmL615X5Z2kajTbQ.jpeg" /></figure><p>In June 2023, I started working on a new project. This was both a blessing and a curse: a blessing, because it was a website, and I’m passionate about web and frontend development, and a curse because it uses PHP. Yes, you got it, it’s a WordPress website. But it’s not a simple WordPress site; it’s actually two multisites, consisting of our marketing website and our career website. Both sites share a single codebase, and at the beginning of the project, they had a custom theme developed by an external agency and a very basic infrastructure setup. I spent the first two months learning about the domain and getting familiar with the codebase so that I could develop the frontend. And then, our contract with the external agency came to an end and the project became solely my responsibility.</p><p>A lot needed to be done on several fronts. We had redone the different working environments and deployment flow to bring the website in-house, so it was working. But it didn’t yet match our company standards — or any standard at all. For example, you could still make manual changes to the production server, and the local setup documentation was so complex that no one had it running on their computer… except me. Of course, when you say you’re working on a WordPress project, no one will rush to help you. Fair enough though.</p><p>Fast forward to today, almost two years later, and the website is looking great. We made all the necessary changes, and I’m currently onboarding the fourth contributor. But that begs the question of how you get teammates to support you in the improvements you want to make when your project is one no one wants to work on. Here are a few things that helped me along the way.</p><p><strong>Have a clear vision and plan</strong></p><p>The goal for the website was clear from the start: We wanted to have it in-house so we could deliver features and changes faster. We also wanted it to run on a reliable infrastructure and have an easy and fast setup. But to achieve these simple goals, a lot needed to be done.</p><p>First, we needed to build a workflow entirely in-house, and then we needed to migrate it to our existing AWS/Kubernetes infrastructure. Finally, we needed to make it easier for engineers to access it and contribute. The road ahead was long, but the destination was clear. And it’s easier to bring others along on a journey when they can see where they’re going.</p><p><strong>Deliver visible value</strong></p><p>To demonstrate the importance of continued investment in the website’s infrastructure, I led and delivered impactful product enhancements — using these visible, high-value improvements to justify the project’s significance and elevate its visibility. Together with the Marketing team — the website stakeholder — I delivered major frontend redesigns, form improvements, and new content and assets for B2B customers…all in a span of one year. Our goal was to present the website as a reliable medium for our digital marketing and sales teams, but also as a flexible and adaptable platform to fit our evolving business needs. The result? It became more visible company-wide. And this was a great help to not only justify the engineering effort, but also to keep everyone motivated along the way. We all prefer to work for a visible and impactful platform, right?!</p><p><strong>Stay on top of the requirements</strong></p><p>During this project, I happened to be the person “in-between” — in-between the agency and our in-house teams in the beginning, and later in-between the Marketing and Engineering teams. This position granted me quicker access to stakeholders’ needs. For example, by joining Marketing’s weekly team meetings, I was kept aware of what was important to them and which goals they were working toward. This way, when we started building the new infrastructure, for example, I knew it was necessary to have a staging environment where the Marketing team could draft and review new pages before pushing them to the live website.</p><p><strong>Plan, follow up, and don’t give up</strong></p><p>This project was a long-term project, and as is the nature of projects that extend over many months, motivation comes and goes. I was also very aware of the fact that even though the website was my top priority, it was one among many priorities for my team and my teammates. As a result, I found that sometimes something else came up that required people to push the website tasks to later. While this is completely normal, I found it helpful to stay on top of following up. For example, if a certain timeframe wasn’t possible, I’d ask when the next availability was and then schedule a meeting to ensure things kept moving. Staying on top of things like this helped me make sure the project kept going in spite of delays and unexpected events.</p><p>That said, it would be a lie to say it was easy. Despite being motivated and driven, when the local setup refactoring was postponed for the second time, when we couldn’t make it work for no apparent reason, or when a fourth person was telling me how much they disliked PHP, it made me question my entire situation. However, when the frustration was high, I found comfort in allowing myself a break from this tedious project and going back to what I enjoyed coding the most: frontend components. Balancing long-term projects with lots of dependencies with shorter tasks I’m able to do independently has been key to my success as an engineer. Shifting my focus for a bit is even more helpful when things get hard: When a component is done and I feel I’ve accomplished something meaningful, it’s easier to return to solving tech debt and coming up with new ideas.</p><p><strong>Get involved</strong></p><p>Another attitude that helped me move the project forward was getting involved in writing code and solving issues with my teammates. I didn’t simply push for a task to be done, but instead I tried to figure out how I could help, such as by pair programming. This is largely how we worked on our new infrastructure, and now Kubernetes is no longer a mystery to me… (I wish!). But this was also the fastest way for me to learn a new topic, and the easiest way for other engineers to have domain knowledge accessible while implementing something. As a result, not only did I have the opportunity to learn, but I was also able to apply what I learned to a concrete use case right away.</p><p>This way of working had the added benefit of keeping me very aware of the project progress. I didn’t need to ask for a status update or knowledge transfer, because I was there, and I asked all my questions on the spot. Luckily, my teammates turned out to be very supportive of my learning and willing to explain how to do things rather than simply “fixing” them for me. The connection, trust, and support that came out of these working sessions were huge motivators too.</p><p><strong>Find ideas</strong></p><p>WordPress and PHP are both not required knowledge at Zenjob, so they aren’t topics I can necessarily discuss and easily learn about in my day-to-day work. And once we stopped working with the external agency, I had no contact with other WordPress developers — and to be honest, I missed it. That’s because I had only worked with shared ownership, and being a solo owner is not something I enjoy. To combat this, I registered to attend the official WordPress conference, WordCamp Europe, in 2024. (This also gave me a good excuse to travel to Italy, as it was happening in Torino.) But moreso, it was a great opportunity to experience the WordPress community and observe how it organizes contributions — and it’s impressive! This was inspiring and helped me get a broader perspective on the tech stack I was working on daily. The best part was joining Contributor Day and making my first contribution to Core WordPress. Thanks to that experience, I came back with a working example of an easy and fast local setup: Core WordPress uses Docker and only a few commands. The moment I tried it, I knew I wanted it for our website too.</p><p><strong>Make it easy to contribute</strong></p><p>Improving the developer experience was the hardest part of the story, the final step, and my way out of being a solo owner — because having no access to the local setup meant contribution to the frontend wasn’t possible for other engineers. Since the local setup needed to be as close as possible to the staging and live environments, it meant we couldn’t build a better local setup until we had built a better live setup.</p><p>We chose Docker to implement consistency across our environments and align with our infrastructure stack. However, the setup was complex due to the multiple images required to run WordPress properly. When we tried applying the same technology to the local development environment, we quickly realized it wasn’t an ideal use case, because managing theme and content imports on each load was far from straightforward.</p><p>And, to be fair, the website was already working. Marketing stakeholders were able to deliver their features on time and had no immediate plans to scale the platform. Despite the risk and because of these technical challenges, we ended up postponing the local setup improvement twice.</p><p>Still, I was determined to make it happen. Over time, with more hands-on experience and a growing understanding of the codebase, new ideas began to emerge. And then, eventually, the timing aligned: a week with a lower workload, a teammate with extensive Docker experience, and a fresh perspective. On our third attempt, just before Christmas 2024, we succeeded — removing a significant piece of technical debt in the process. Since then, several teammates have been able to onboard autonomously, and to me, this feels like the biggest win.</p><p><strong>Talk about it all the time, to everyone</strong></p><p>All these efforts and achievements needed to be communicated and shared widely, so I became the website’s best ambassador: that one person talking about the website all the time, even at the lunch table (sorry); and the face you would see in presentations, demos, or any meetings every time the website had a new design or a new feature. I encouraged our Marketing stakeholders to do the same on their end. All together, we brought awareness and placed the website in everyone’s mind.</p><p>It’s spring 2025, and the website is now managed by a whole team that I’m part of. Team members are onboarding and getting to know the codebase, and with that comes ideas, opportunities, and shared ownership. It’s far from perfect, and a lot can still be improved, but it feels like I accomplished my initial mission. And I’m looking forward to what’s coming next for our website!</p><p><em>Special thanks to Esteban, Chris, Pablo, Dima, Rawand, Youssef, and Julio. Your motivation, support, and technical knowledge helped me carry this project since day one. And thanks to Alka, Polina, and Olja, who believed in and worked toward our project’s success as much as I did. I’m happy the website brought us together.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b302609d5067" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zenjob-tech-blog/turning-an-unpopular-project-into-a-team-win-b302609d5067">Turning an unpopular project into a team win</a> was originally published in <a href="https://medium.com/zenjob-tech-blog">Zenjob Technology Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Women, tech, and champagne]]></title>
            <link>https://medium.com/zenjob-tech-blog/women-tech-and-champagne-4444853e5a9a?source=rss-e26c8d38a542------2</link>
            <guid isPermaLink="false">https://medium.com/p/4444853e5a9a</guid>
            <category><![CDATA[community]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[women]]></category>
            <category><![CDATA[berlin]]></category>
            <dc:creator><![CDATA[Anaïs Engler]]></dc:creator>
            <pubDate>Wed, 12 Apr 2023 11:41:41 GMT</pubDate>
            <atom:updated>2023-04-12T11:41:41.191Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m_4TFto92LFXCG1HPprfOw.jpeg" /><figcaption>Credit: Xena Women in Tech Award, 2023</figcaption></figure><p>On Friday, March 3, 2023, a few hundred people gathered in a basement in Berlin, dressed in their finest, ready to celebrate. It was all for the <a href="https://wearexena.com/awards">Xena Women In Tech Awards 2023</a>.</p><p><a href="https://wearexena.com/">Xena</a> is a tech recruitment agency dedicated to helping companies hire and retain women in engineering, product, and leadership roles. And this event was its first-ever awards night.</p><p>Megan Gill, Head of Recruitment at Xena and host of the night, took the stage and began by commenting how great it was to see so many women, adding that it’s not always been like this in tech.</p><p>More than 300 people were invited for the occasion, 45 finalists were celebrated, and 9 prizes were awarded. The prize categories covered a wide range of topics — from leadership and social impact, to entrepreneurship and open source. The winners of the night were:</p><ul><li>Leadership Award: Chiedza Muguti (Chief Product Officer, Alteos)</li><li>Open Sourcer Award: Liz Rice (Chief Open Source Officer, Isovalent)</li><li>D&amp;I Leader Award: Sarah Cordivano (Head of D&amp;I Strategy &amp; Governance for Talent and Leadership, Zalando SE)</li><li>One To Watch Award: Késsia Castro (Senior Frontend Engineer, HelloFresh)</li><li>Social Impact Award: Charlene Hunter MBE (CEO &amp; Founder, Coding Black Females)</li><li>Allyship Award: Víctor Moreno Alhambra (Head of Engineering, HER)</li><li>CTO Award: Meri Williams (CTO, Pleo)</li><li>Entrepreneur of the Year Award: Georgina Kirby (Co-Founder &amp; CTO, Vinehealth)</li><li>D&amp;I Tech Employer of The Year: Expedia Group</li></ul><p>In between awards, three guest speakers came on stage and shared their expertise about how diversity is a driver for innovation, how female founders are beating the odds, and how important female leadership representation is. Anne Kjær Barthel, one of the speakers and founder and CTO of ReDi School of Integration, shared how powerful we all can be if we keep promoting more women in tech. She encouraged us to teach, mentor, and stand up “for those not yet sitting next to us.”</p><p>Bhuvana Vijayan, our Director of Engineering at Zenjob, was among the top five finalists nominated in the Leadership category, so we came as a team of 13 to support her and enjoy the event.</p><p>Both <strong>Rawand Guiga</strong> and <strong>Anaïs Engler</strong> are engineers at Zenjob and joined the celebration. Because March is Women’s History Month and we want to celebrate women and their success, we decided to share a little bit about the evening and why it was important to us.</p><h4>What were your highlights of the night, and why did the event resonate with you?</h4><p><strong>Rawand Guiga:</strong> The event was an amazing experience. One of the highlights for me was hearing the inspiring stories shared by successful women in tech — learning about their accomplishments and how they persevered despite the challenges they faced. I also appreciated hearing the different perspectives they had on creating an inclusive culture in the tech industry. These stories resonated with me because they provided me a glimpse into the opportunities available to women in tech and the potential for female professionals to make a real difference in the field.</p><p><strong>Anaïs Engler: </strong>Among all the speakers and winners, the one that resonated with me the most was Késsia Castro. When she received the One To Watch Award, she said that in everything she does at work and beyond, she makes sure to pave the way for the other women who will follow. It felt powerful to me and describes well how I feel about being a software engineer myself. It’s not just about working in tech; it’s also about making sure women play a role in a key sector, that more women know about the opportunities tech offers, and that everything is set up for them to actually succeed once they enter the field. This greater motivation is a driving force for me.</p><h4>Why is participating in an event like this important to you?</h4><p><strong>Rawand:</strong> Being part of such an event was a real chance for me as a junior engineer who has just started my career to meet women in different positions in the tech field — successful women who have achieved a lot and have great experiences to share. Seeing the incredible things these women have achieved in this field is truly inspiring and has pushed me to strive for more. Furthermore, attending this event was also a great way for me to network, meet new people, and find mentors who can offer guidance.</p><p><strong>Anaïs:</strong> It was an occasion for me to feel included and valued within my company and the tech sector in general. I’m grateful for this opportunity to attend with my colleagues; it was a nice evening full of learnings and a real networking booster! I’m a heavy LinkedIn user and consider networking one of my career progression’s pillars. I can’t begin to count the useful information, tips, recommendations, and friends I’ve learned and gained from conversations started on this platform. So at an event like this one, you get the chance to continue to learn about many interesting career paths and project ideas and, of course, meet people in real life, all at once!</p><h4>What was your main takeaway from the evening?</h4><p><strong>Rawand:</strong> As a junior DevOps engineer, I’m fortunate to be surrounded by amazing women in tech who have achieved a lot in the field. I’m grateful for the opportunity to learn from these inspiring individuals and to be a part of the tech community. Being surrounded by these incredible women has given me a renewed sense of enthusiasm and purpose. This experience has also given me access to invaluable resources and connections, which will support me in my journey to furthering my career in technology.</p><p><strong>Anaïs:</strong> It confirms my motivation to work in tech, and to keep learning and improving my skills and growing in this field. As a woman who was never really into sciences before, tech may feel like a party no one invited you to. But you should still invite yourself, because once you’re in, you’ll find a strong community to support you. This is what this event was all about, and it was amazing to feel it in real life.</p><h4>Which other resources or organizations would you share with anyone wanting to get involved in promoting diversity and inclusion in the tech industry?</h4><p><strong>Rawand: </strong>I encourage everyone to not be intimidated by technology and to embrace every new technology they learn. By starting with my own small experience in tech, I can attest that it’s a rewarding and exciting field, and that anyone should be brave enough to explore it.</p><p>Additionally, I would suggest not being afraid to ask questions or seek help when starting out in tech. There are many resources available to help you get up to speed with the basics and keep learning every day. For anyone looking to promote diversity and inclusion in the tech industry in Berlin, I would recommend exploring organizations such as Athena Lab, <a href="https://festival.toa.media/">Tech Open Air</a>, and <a href="https://www.womentech.net/women-in-tech-berlin">WomenTech Network</a>. Additionally, there are initiatives such as Ada’s List, <a href="https://www.codenewbie.org/">Code Newbie</a>, <a href="https://www.hiretechladies.com/">Tech Ladies</a>, and FemTech Global, all of which offer resources, mentorship, and networking opportunities for underrepresented groups in the tech industry.</p><p><strong>Anaïs:</strong> I’d encourage every woman working in tech or interested in working in tech to join a community, whether online or in person. It’s a real support system that you can benefit from and contribute to. In Berlin, you have WeAreXena, <a href="https://girlsintech.org/">Girls in Tech</a>, <a href="https://wtmberlin.com/">Women Techmakers</a>… Your bootcamp or your university, or even your current company may also have one. And if not, start one!</p><p><em>Thank you to Rawand Guiga and Anaïs Engler for sharing their insights.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4444853e5a9a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zenjob-tech-blog/women-tech-and-champagne-4444853e5a9a">Women, tech, and champagne</a> was originally published in <a href="https://medium.com/zenjob-tech-blog">Zenjob Technology Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>