<?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[t14g - Medium]]></title>
        <description><![CDATA[The future runs faster than the present. t14g is run by the fine people working at Turbine Kreuzberg. - Medium]]></description>
        <link>https://medium.com/t14g?source=rss----ff416c732167---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>t14g - Medium</title>
            <link>https://medium.com/t14g?source=rss----ff416c732167---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 00:39:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/t14g" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[‘Still Very Much in Control’: Bernd Alter on the Current Impact of AI on Development]]></title>
            <link>https://medium.com/t14g/still-very-much-in-control-bernd-alter-on-the-current-impact-of-ai-on-development-74dc8c5a5c96?source=rss----ff416c732167---4</link>
            <guid isPermaLink="false">https://medium.com/p/74dc8c5a5c96</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[Melisa Akbaydar]]></dc:creator>
            <pubDate>Mon, 13 Nov 2023 13:51:22 GMT</pubDate>
            <atom:updated>2023-11-13T13:51:22.695Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pYFmCEn4KvlWE0x_uXrAFQ.png" /><figcaption>Midjourney / “abstract organic AI brain, in the style of light purple and dark green, line drawing style, fluid photography, translucent layers, data visualization, molecular, white background — ar 16:9”</figcaption></figure><p><em>With the rapid and widespread integration of AI into our daily lives, it is essential to give due consideration to its impact on developers. Over and over again, we see the growing sentiment that AI is displacing developers from their roles. “It definitely changes the way we work, but the role of developer will stay in the future too,” says Bernd Alter, Co-CTO at Turbine Kreuzberg. This convergence of technology and expertise not only reshapes the way businesses operate but also challenges developers to push the boundaries of their skills and learn more. To get a read on the current situation, we asked Bernd to answer our questions.</em></p><p><strong>Bernd, how has the daily routine of the developer changed so far?</strong></p><p>AI’s influence on a developer’s daily tasks is pretty significant, although it hasn’t profoundly altered the core foundations and everything yet. What’s interesting is the transformation in the research aspect. AI has sped up tasks like looking up how to work with data structures. For example, googling quick-forgettable things like “how to flatten a multidimensional array” or “how to extract a certain thing from an array” can sometimes be time consuming. AI tools like Github’s <a href="https://github.com/features/copilot">Co-Pilot</a> and Amazon’s <a href="https://aws.amazon.com/codewhisperer/">Code Whisperer</a> not only provide quick answers, but also anticipate a developer’s needs, suggesting code and structure.</p><p>It’s important to note that developers are still very much in control, which proves that AI is in the role of assistance, not a substitute for developers. In essence, AI is streamlining and enhancing the development process, making developers more efficient.</p><p><strong>In your view, how do you see the role of a software developer changing? What new skills should we focus on now?</strong></p><p>I certainly see the landscape of software development having evolved — and it’s quite fascinating. Even if you’re not well-versed in a specific programming language, today’s AI can provide you with precise code suggestions, which is a game-changer.</p><p>As for what developers should focus on in this evolving environment, skill advancement is key. AI is becoming proficient at handling routine coding tasks, sometimes matching the quality of human work. This raises the question of whether AI might replace certain developer roles. However, I believe this will never affect developers who have a strong foundation especially in software design, architecture, and patterns. These skills go beyond coding and will set you apart from AI, because they also require creativity in applying them, something AI is not capable of (yet). So, it’s an exciting time to prioritize these skills to maintain a competitive edge in the field.</p><p><strong>Do you have tips for communicating with the AI/prompting? How can you best integrate the AI tools in your daily tasks?</strong></p><p>Developers now have the advantage of seamlessly integrating AI tools and assistants into their Integrated Development Environments (IDEs). It’s all about ease and accessibility. In many cases, you simply need to enable these tools and use them within your workflow. They often operate by merely interpreting a command or description of what you intend to code, and then they generate the code for you. It’s a matter of harnessing these capabilities and seamlessly incorporating them into your development process.</p><p><strong>How can developers use AI power to ease their complex tasks?</strong></p><p>You know, AI is a pretty remarkable tool for developers. It’s not so much about tackling complex problems but rather taking care of the repetitive and straightforward tasks. AI plays a crucial role in freeing up developers and allowing them to focus on more complex challenges. It’s a valuable tool when entering new territories within development.</p><p>However, it’s important to remember that AI isn’t a creative force; it works with existing knowledge and solutions, so it can’t invent entirely new solutions for novel problems. The role of a developer demands creativity, and human creativity will continue to remain indispensable. To put it into perspective: consider navigation systems like Google Maps. While they are usually accurate, there are also times when your personal knowledge leads to better and faster ways if you know the way.</p><p>So, instead of blindly following the recommendations without questioning, let the navigation guide you but try to learn the path to go further or faster on the road. Similarly, it’s essential for developers to learn and validate AI suggestions to ensure they align with their project’s specific needs and use them in further projects.</p><p><strong>Where do you see AI and development headed in five years ?</strong></p><p>It’s really interesting to see all the excitement surrounding AI these days. It’s like this new frontier of technology that holds so much promise, but there’s a catch — a lot of folks don’t fully grasp how it all works under the hood. It’s a bit like a well-kept secret held by a handful of experts. And that secrecy raises some concerns. If this trend persists, there’s a real risk that AI could turn into a playground for just a few big players, like Google and the rest, who hoard all the knowledge and dominate the scene.</p><p>When that happens, competition tends to fade away, and that’s where things could get tricky. Without healthy competition, innovation slows down, and the power becomes concentrated in just a few hands. To keep things fair and foster innovation, some argue that AI should be more accessible for everyone, not just a privileged few. It’s a real challenge, but finding that balance is key to the future of AI development.</p><p><strong>Bernd, thanks for the chat!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74dc8c5a5c96" width="1" height="1" alt=""><hr><p><a href="https://medium.com/t14g/still-very-much-in-control-bernd-alter-on-the-current-impact-of-ai-on-development-74dc8c5a5c96">‘Still Very Much in Control’: Bernd Alter on the Current Impact of AI on Development</a> was originally published in <a href="https://medium.com/t14g">t14g</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Plunge into Productivity: Navigating the Depths of Remote Work]]></title>
            <link>https://medium.com/t14g/plunge-into-productivity-navigating-the-depths-of-remote-work-083c847538e4?source=rss----ff416c732167---4</link>
            <guid isPermaLink="false">https://medium.com/p/083c847538e4</guid>
            <category><![CDATA[work]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[remote-working]]></category>
            <dc:creator><![CDATA[Sérgio Godinho]]></dc:creator>
            <pubDate>Thu, 12 Oct 2023 14:28:19 GMT</pubDate>
            <atom:updated>2023-10-12T14:28:19.198Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FECpqKoPxCxsmkPMzCJYkA.png" /></figure><p><em>Besides recruiting in tech and effective employer branding, our team architect Sérgio Godinho is passionate about remote work and forming healthy work habits. In this article, he shares some of his strategies and tips for being productive in a remote setting.</em></p><p>–––</p><p>Envision a vast pool called “Remote Work,” encircled by potential swimmers — Company A, Company B, and so forth. Pre-pandemic, the waters of remote work appeared somewhat inhospitable; a few brave entities dipped their toes in, but most hesitated at the edge. Then, a raging fire of a global, life-altering event compelled companies, whether they knew how to swim or not, to plunge into these unfamiliar waters. With the storm now passed, many have not only adapted but found unexpected benefits in the depths of remote work, opting to continue exploring its expanses even in calmer times.</p><p>The surge in remote work has prompted in-depth discussions and research, particularly around its impact on productivity. While ‘productivity’ has become a “fashionable” buzzword at conferences and in articles, I want to focus on practical strategies and tipps aimed at fostering your best self in a remote working environment, be it from the comforts of home, a secluded cabin, or a bustling beach cafe.</p><p>To talk about enhancing anything, we should first dive — swimming pool pun definitely not intended — into the concept to get a grasp on what it is exactly. At its core, productivity encapsulates the quality and value emanating from an individual’s work output. This metric is pivotal for companies: the higher the productivity, the greater the likelihood an organization will flourish. In an ideal scenario, businesses and staff operate symbiotically. The notion is that as a company cultivates optimal conditions for its employees to thrive, productivity surges, driving profitability, which in turn provides further resources to invest back into its workforce — a perpetually fruitful cycle.</p><p>For those relishing the chance to work beyond traditional office confines, finding ways to mirror the trust and flexibility afforded by companies becomes essential. Join me as we delve into our metaphorical toolkit to uncover strategies designed to pave the way toward enriched remote productivity.</p><h3><strong>Crafting the New Era Workspace</strong></h3><p>To optimize your work, laying a robust foundation is pivotal. In the realm of remote work, the dynamics of workplace setup and communication have undergone significant transformations. Maximizing the potential in both is not merely an option, but a necessity — and fortunately, there are straightforward methods to ensure you’re leveraging all available opportunities.</p><p><em>Workplace Setup</em></p><p>Getting the chance to create your own office space is a great power and with great power… No need to finish the sentence, right? Your remote workplace should be envisioned as a personalized work sanctuary, meticulously attuned to all your senses. Starting with touch, prioritize elements like a comfortable chair, an ergonomically-designed table, and maintaining a healthy posture. Working from exotic locations can be tempting, be mindful of the practicalities and potential pitfalls involved — for instance, the inability to speak in a quiet library or the logistical challenges of working from a sandy beach. Coming from a country where there are beaches all over, I’d think twice considering the amount of sand, the needed bright screen and the usual temptations.</p><p>It’s important to ensure your workspace is both pleasing and personalized to your tastes, incorporating items that make you happy and motivate you like a photograph of someone you love or the guitar pick your favourite artist gave you when you were 12. Manage noise levels according to your focus needs, whether that’s complete silence or a consistent ambient sound. Keeping a stock of healthy snacks and drinks is crucial to sustain concentration. Remember the old wisdom: “An apple a day keeps the doctor away,” or whatever equivalent supports your tastes. Finally, prioritize your eyesight by ensuring adequate lighting.</p><p><em>Clear Communication</em></p><p>The essence of effective communication, particularly in remote work, boils down to eliminating ambiguity: make it as hard as possible for your message to have two meanings. Strive for simplicity, directness, and clarity in your interactions. Take, for instance, directive communication: instead of saying, “Don’t save the files in Folder X,” which prompts the question, “Then where should I save them?”, opt for a clear directive such as “Please save the files in Folder Z.” Simple enough, right?</p><p>Moreover, emojis, when when we use them right, can serve as valuable tools in conveying tone — consider the nuanced difference between “The presentation today was awesome 🤩” and “The presentation today was awesome 🙄.” Plus, some simple tips: make sure your camera and microphone are working <em>before</em> the next video call begins to avoid the all-too-familiar “Can you hear/see me?” and, even more crucial, mute yourself when not speaking to prevent unnecessary disturbances or potential embarrassments. When in doubt, opting for the most clear communication path is always the wisest decision.</p><h3><strong>Optimizing for Focus</strong></h3><p>Mental schemes, or cognitive structures that guide our behaviors and responses, fundamentally steer our day-to-day actions and decisions. Consider a trip to the supermarket: the sequence of entering, selecting items, checking out, paying, and exiting isn’t something we deeply ponder upon each visit. Imagine wondering “Where should I get in: the main entry or the back door?” or “Should I pay beforehand or after I’ve selected what I want?” every time you visit one. It would be chaos. This intuitive flow of actions is guided by an ingrained mental scheme developed through repeated experiences, thus saving mental energy by bypassing incessant decision-making at every juncture.</p><p>This principle, applied judiciously, can be a useful tool in enhancing focus and optimizing work habits. The key is to craft patterns of predictable actions, enabling your brain to anticipate and settle into “focus blocks,” thereby streamlining your workday and enhancing productivity.</p><p><em>The “Timeboxing” Technique</em></p><p>An actionable approach to architecting your workday around mental schemes is to employ calendar blocking, where you allocate specific time slots for distinct tasks or ‘areas of focus.’ By delineating your calendar into focus blocks, you not only allocate intentional time for every key area of your job but also drastically mitigate the risks of unintentional task-switching or multitasking. Contrary to the ostensibly impressive ability to juggle multiple tasks simultaneously, the true heroism in productivity lies in dedicating undivided attention to a singular task at a time. This focused approach not only elevates the quality of your output but also often allows for more expedient completion, thereby saving time for subsequent tasks.</p><p><em>Mitigating Multitasking, or Delineating “Work” and “Life”</em></p><p>Equally crucial is minimizing the potential for multitasking between work and non-work activities, especially in a home environment where personal life is perpetually adjacent to your workspace. Ensure those sharing your space are aware of your work schedule and respect its boundaries. An untimely interruption, such as someone tuning in to a sitcom show on TV during your focus block, might offer some welcome amusement but can wreak havoc on your productivity and ability to complete tasks.</p><p><em>Embracing Breaks</em></p><p>Lastly, let’s address breaks — an imperative, yet often overlooked, aspect of sustainable productivity. Consider a long drive: wouldn’t you stop — at least once — along the way? Periodic breaks for refreshment, rest, and leg stretches are intrinsic to the journey. Similarly, incorporating breaks into your workday is vital to maintain sustained levels of focus and prevent burnout. Intermittent pauses — recommended every 90 minutes of intensive work — facilitate mental rejuvenation and may unexpectedly sprout solutions to work challenges that seemed insurmountable moments before. Everyone has a similar story to “I was blocked on something and, after a five-minute stroll with my dog, the solution just appeared in my head”. You might be a break away from the next step.</p><p>The caveat: use breaks judiciously, ensuring they serve as true pauses for refreshment and not veer into the territory of procrastination.</p><p><strong>Your “Other” Life</strong></p><p>The aphorism that we should work to live, not live to work, underscores a pivotal truth often eclipsed in the hustle of professional endeavors. Genuine productivity extends beyond the confines of our work lives into our personal realms, converging into the widely celebrated, yet often elusive, concept of “work-life balance.”</p><p>For most, cultivating unambiguous boundaries is a necessity, not a luxury. The allure of “I’m close anyway” or “It’s just a 5 minutes” needs to be consciously resisted to preserve personal time. The Right to Disconnect Law, enacted by the Portuguese government, exemplifies a commendable initiative in safeguarding this principle, prohibiting employers from reaching out to employees post-work hours unless in cases of critical urgency.</p><p>Allocating time for sports and physical activities in your free schedule is not merely a recommendation but a necessity. While the assertion that engaging in sports enhances health might appear as self-evident as stating “water is wet,” its reiteration is crucial owing to the proactive effort required to weave it into our typically hectic post-work schedules. Sports serve as conduits for stress alleviation, promoting restful sleep, and fostering physical health. Although saying something like “doing sports makes you healthier” might seem like “water is wet”, it is always important to reinforce it as it requires an active effort to include it in our always busy after-work routines. Generally, embracing hobbies should mean more than carrying out routine chores (unless chores are your passion, though I advise you explore other interests…). Having hobbies is fundamental, as it keeps you motivated, creates an opportunity to acquire new skills, and helps promote a sense of self-worth in various areas of life.</p><h3><strong>Wrap-up</strong></h3><p>Obviously, this is the kind of topic that even an entire encyclopedia couldn’t fully cover, so excuse the superficiality. I hope, though, that it has served as an appetizer for further diving into the topic, as you continue to juggle video calls, virtual team-building events, and the occasional surprise cameo by your co-worker’s overly enthusiastic pet.</p><p>Good takeaways from this article would be: Strategically leveraging mental schemes to optimize focus, consciously thinking about your surroundings, employing focused task blocks, minimizing multitasking, and judiciously incorporating breaks collectively forge a robust strategy for enhancing your productivity in a remote setting.</p><p>In the end, remember: the possibility of working outside the boundaries of a traditional office is a gift. Let’s make the best out of it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=083c847538e4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/t14g/plunge-into-productivity-navigating-the-depths-of-remote-work-083c847538e4">Plunge into Productivity: Navigating the Depths of Remote Work</a> was originally published in <a href="https://medium.com/t14g">t14g</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Empowering Women in Tech: Turbine Kreuzberg’s Inspiring Role Models]]></title>
            <link>https://medium.com/t14g/empowering-women-in-tech-turbine-kreuzbergs-inspiring-role-models-8c9d8f8c4ef2?source=rss----ff416c732167---4</link>
            <guid isPermaLink="false">https://medium.com/p/8c9d8f8c4ef2</guid>
            <category><![CDATA[work]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[female-empowerment]]></category>
            <dc:creator><![CDATA[Sophie Barth]]></dc:creator>
            <pubDate>Mon, 07 Aug 2023 14:54:03 GMT</pubDate>
            <atom:updated>2023-08-07T15:31:00.741Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TNO0ugH6TMKlUWQjy_PfFg.png" /></figure><p>Women in software development are rare, and they are even rarer at the management level. At Turbine Kreuzberg, we have eight female software developers, but we want to change that. As a growing tech-company, our aim is to increase the number of women by 2025 and achieve at least a one-third share. Why does it seem that females have less interest in science and technology? Or is this just a bias?</p><p>To get some answers, I spoke with our female developers Liliana, Ana, Brigitte, Melle, with our technical writer Melisa and with our QA specialist Daria. My questions were mostly about the origin of their interest in computers and programming, about good mentorship experiences in their careers, and what changes they would like to see so that women feel more supported and empowered to start their career in IT.</p><p><strong>Taking the first step in IT</strong></p><p>The majority of my female interviewees found their way into IT through male family members who were passionate about computers or worked in IT themselves. Ana used to be allowed to play around with her father’s computer and she came into contact with software and game demos through magazine subscriptions. She still had doubts during her Computer Science studies whether programming was the right thing for her and what it actually meant to code in a company.</p><p>Melisa’s uncle is also a computer enthusiast and she can remember very well how they played computer games together. She also owned several game consoles. Melle started studying multimedia technology because she was very interested in 3D animation from playing Final Fantasy and wanted to develop games herself. Through an internship at the end of her studies she ended up in frontend development by chance. Fortunately, this changed after she joined Turbine Kreuzberg. After graduating from school, Daria attended a QA Meetup at the new IT school in her city, which led to her taking a QA course afterwards.</p><p>Liliana is a career changer. She had initially studied archaeology. The job prospects were not so good and thanks to her cousin, who was already studying IT, she found interest in software development. Brigitte’s father was, as she says, a “computer person” and she studied physics. She decided to take Fundamentals of Computer Science as a non-physics elective course.</p><p><strong>Essential skills for successful programmers</strong></p><p>Programming goes beyond just having an affinity for technology. According to my colleagues, you don’t need to have an outstanding coding talent, but more like a kind of fearless “Sherlock Holmes” with hands-on mentality. What’s even more important than a logical mindset is the ambition in finding solutions to problems, moreover the ability to adjust themselves to the changes like new requirements, new frameworks, new programming languages or new technologies.</p><p>If you can concentrate on a topic for a longer time, enjoy working as a team and love having challenges, then you can consider programming as a career path for you. Programming requires continuous learning, especially from the mistakes. So, you shouldn’t be afraid of making some.</p><p>At Turbine Kreuzberg, our main focus in hiring is whether the person fits in our team or not. With all the skills and ability that the person brings with, should definitely be a puzzle piece to the team. We don’t need to mention hard skills and essential qualifications as they are already the must-haves.</p><p><strong>What it means to work in a tech profession</strong></p><p>It doesn’t mean that you always need to set up the printer at your parents’ house or solve every Internet problem. The answers I got from my colleagues in Turbine confirmed it one more time that the impression that many people have, especially career starters, often don’t know the variety of positions in IT. That’s why I asked my colleagues to give me a little insight about their day-to-day work.</p><p>Liliana is a back-end developer in a large development team. She works closely with the customers and the product owners. Her job is to write clean and efficient code in order to create an environment where certain features work smoothly and will be embedded into other systems.If challenges or problems arise during the development, she finds solutions or suggests ways to improve them.</p><p>On the other hand,Daria is our QA Specialist. She communicates closely with other developers and discusses complex tickets. She performs software tests on developed applications and systems, documents it and thus, ensures bug-free code and ultimately satisfied customers.</p><p>Melisa’s job as a technical writer is to understand complicated technical topics and technologies used by Turbine Kreuzberg or in the IT market and shape the content into understandable articles and social media posts for readers from all levels, whether IT experts or not.</p><p>Developing in the front-end is much more than making layout-related changes to applications and websites. Melle prepares the data of the backend visually and user-friendly, this can be e.g. a color change of a button or a new screen input. Larger tasks include defining project setups with frameworks and dependencies, project monitoring, and contributing third-party applications such as tracking. To do this, she is working closely with the backend development team so that everyone knows what needs to be implemented when and how.</p><p>These are just a few examples of countless other possible assignments in IT and tech positions that can vary from company to company.</p><p><strong>The perks of working in a tech position</strong></p><p>Of course, I also asked our female techies about what they enjoy the most in their position. Our female developers find the power of the code very fascinating, for example, how the small code parts come together and create big and complex systems. Daria, Melisa and Liliana love watching the progress of their work and learning new things constantly. Especially Melisa wants to underline how cool it is to be able to follow the recent trends in IT and to keep up with new technologies in daily life. Brigitte prefers to share her knowledge. She enjoys finding creative and logical solutions to problems, which will be even developed further and become a helpful tool.</p><p>Overall, IT and programming is an endless world that has various fields of application, such as in health, fashion, physics, design, mathematics or gaming. Our female techies keep up to date with new technology and trends by attending conferences and trade fairs, reading newsletters or simply exchanging ideas with colleagues. Dev Talks is a regularly planned event at Turbine Kreuzberg and we also host our own tech meetups in Berlin, Faro and Bishkek.</p><p><strong>Misconceptions and prejudices still exist</strong></p><p>Our female developers are usually the only woman on their project team. However, they have told me that they perceive little or no difference in their treatment compared to male colleagues. However, Liliana told me that she has already experienced some misconceptions. In her previous companies, some male colleagues did not dare to give her feedback because they thought women are “too sensitive”. The other interviewees also mentioned a concept about prejudice against women, which is being accused of not thinking rationally and logically enough to succeed in programming. Liliana thinks this is a shame, because men should treat women like any other person, since everyone has different personality and abilities, independent of gender.</p><p>Women also have prejudices and behave in a biased way. Our female developers have observed that especially young women don’t dare to join male-dominated teams or when they do, start being more reserved. It also happens that women fall back into stereotypical behavior, letting their male colleagues solve difficult tasks instead of trying to do it themselves. I also noticed in the interviews that my female colleagues sometimes downplayed their abilities while they should be more confident and believe in their own skills.</p><p><strong>How to make technology a hype topic for younger generation and women</strong></p><p>I wanted to know from my interviewees why the tech industry is primarily associated with men. Clear answer: there is simply a clear preponderance of men in IT and also, more notable male CEOs of well-known tech companies.Technology and programming seem to be more in line with the interests of men.</p><p>Ana strongly believes that computer science and tech initiatives need to be integrated into the school curriculum much earlier, not just in middle school. Some girls don’t have enough access or touch points with computers and technology at home.</p><p>Furthermore, it is important to simplify lateral entrants to make career changes easier. Above all, Melisa has noticed this both in her own applications as well as in applications from fellow students, that recruiters and hiring managers sometimes can be a “bottleneck” for female tech professionals to enter tech positions, as they mainly look for experience rather than people skills.</p><p>Brigitte finds it a bit tiresome to just repeat the needs of more women in IT and shared quite an exciting viewpoint with me. For her it looks like there are differences between men and women. But does this need to be a problem? Instead of trying to convince more women into traditional IT positions and adapt them, we can consider the process over again. Hiring companies can explore what diversity and other perspectives offer and use this as an advantage. Furthermore, Brigitte thinks that it’s the experiments that are the fun part, and which bring forth ideas and visions.</p><p>My colleagues advise all girls and women interested in programming and pursuing a career in IT to embrace experimentation and not let obstacles deter them. They emphasize the importance of trying out diverse opportunities, reassuring them that it’s completely acceptable to encounter failures along the way. This applies to career starters as well as career changers. A lateral entry into software development is also possible at any time. However, there are already positive developments. My colleagues report that they see more and more female speakers at conferences and the number of female gamers is also increasing on gaming platforms.</p><p><strong>We need more mentors and female technical role models</strong></p><p>When talking about getting more women interested in IT, we should also talk about the importance of role models and mentorship. According to definition, a mentor (all genders) is an experienced person who passes on their (technical) knowledge and experience to an inexperienced person (<a href="https://wirtschaftslexikon.gabler.de/definition/mentoring-41572">Gabler Wirtschaftslexikon</a>).</p><p>For Melisa, this role is characterized above all by honesty, reliability, professionalism and experience. When our women think of mentors, they mainly think of colleagues who trained them in their previous jobs. Liliana is super happy with the two Technical Directors at Turbine Kreuzberg with whom she currently works. They respect her, are always available, give constructive feedback, and have extensive expertise. Daria fondly remembers her former team leader, who empowered her not only professionally but also personally. She herself was also a mentor at her previous company and would like to do it again in the future. During her studies, Brigitte took care of tutorials for younger engineering groups with other student assistants. She has also taught non-devs the basics of development at Turbine Kreuzberg.</p><p>Ana fondly remembers a memorable mentor-like experience in 2nd grade. At that time, she was explaining to her older teacher how to operate a computer. She loved the feeling of being helpful. For her, sharing knowledge is very important. Moreover, since technology is changing a lot in a short time, she is convinced that she would also be able to learn a lot from a young developer while mentoring. Melle has also noticed that mentoring or onboarding goes beyond hard skills. People skills are of the same importance there. Colleagues who have trained her, have always encouraged her to be more confident.</p><p>The same goes for role models. By definition, they are persons who someone admires and whose behavior they try to copy (<a href="https://dictionary.cambridge.org/de/worterbuch/englisch/role-model">Cambridge Dictionary</a>). Thinking about tech role models, names like Mark Zuckerberg, Elon Musk, Bill Gates, or Tim Cook come up most often. Only Ana could tell me some female role models like Susan Wojcicki (former CEO at Youtube), Gwynne Shotwell (COO at SpaceX) and Katherine Maher (former CEO at Wikimedia). This shows that female role models are still rare. But do role models always have to be well-known and in a leading position? Not necessarily. If you look at Ana, Liliana, Daria, Melisa, Brigitte and Melle, they have exemplified magnificently how a career in IT can start.</p><p><strong>Wrap-Up: Early access &amp; less of the same!</strong></p><p>My conversations with our female tech colleagues shows that girls can also have the same interest in computers, video games and technology as boys do. The tech industry is still male-dominated and lacks female role models. To improve this imbalance, (female) mentors are important to pass on their (technical) knowledge and should encourage women in their skills.</p><p>If children are given access and information about computers and IT at a younger age, this could lead to more women in IT professions. Interested women should be given the opportunity to better inform themselves in advance about the different fields of activity in IT. They also should consider whether their soft skills match those of a programmer and, of course, simply try out.</p><p>The tech industry needs to abandon the idea that women have to conform to the system. Here are good chances to enhance team culture and assemble a new class of high performing teams by disregarding gender and focusing on the potential of individuals. For me, all my colleagues are already role models in tech as they followed their interests, tried new things and launched inspiring careers in the technology world.</p><p><em>Thoughts? We’d like to hear them. Reach out to Sophie on </em><a href="https://www.linkedin.com/in/sophie-barth"><em>LinkedIn</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c9d8f8c4ef2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/t14g/empowering-women-in-tech-turbine-kreuzbergs-inspiring-role-models-8c9d8f8c4ef2">Empowering Women in Tech: Turbine Kreuzberg’s Inspiring Role Models</a> was originally published in <a href="https://medium.com/t14g">t14g</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Improving Product Performance]]></title>
            <link>https://medium.com/t14g/improving-product-performance-9f9f32b0a0c7?source=rss----ff416c732167---4</link>
            <guid isPermaLink="false">https://medium.com/p/9f9f32b0a0c7</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[qa-testing]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Daria Medvedieva]]></dc:creator>
            <pubDate>Mon, 19 Jun 2023 14:59:09 GMT</pubDate>
            <atom:updated>2023-06-19T15:13:19.917Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Improving Product Performance: QA Engineering at Turbine Kreuzberg</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ngojze8MIGoRO57H-nHMww.png" /><figcaption>Quality assurance takes a many-layered approach involving numerous different tests that help to find defects in software and improve quality (Source: Midjourney).</figcaption></figure><p><em>QA Engineering plays an important role at Turbine Kreuzberg by ensuring that software products meet the necessary quality standards and are free from errors or defects. Our QA Engineers work closely with developers and product owners to identify potential risks and establish testing procedures that help identify the bugs, errors, and other issues in software products. Our main goal is to ensure that development processes follow industry standards and that software products meet the highest quality criteria and the needs of end-users.</em></p><h4><strong>Quality Assurance in Turbine Kreuzberg</strong></h4><p>Ensuring high-quality products and services is a top priority for us — and has been embedded deeply in our development processes. In our continuous push for even higher quality, we first established a dedicated Quality Assurance (QA) department in October 2022. Since then, the team has been steadily growing with the addition of new engineers. While our current testing methods are predominantly manual, we are actively seeking automation QA engineers right now, who are proficient in both programming and testing.</p><p>Our initial objective is to establish efficient testing processes, after which we will progressively incorporate automation while actively sharing knowledge within our team. It is essential to emphasize that quality assurance encompasses more than just post-development processes.</p><p>We initiate quality checks from the conceptual stage and continue throughout the entire product lifecycle, including post-delivery maintenance and sustainability efforts. By prioritizing quality assurance, we ensure that our products and services consistently meet the high standards our partners expect.</p><h4><strong>Automation and Manual Testing</strong></h4><p>The distinction between automation and manual testing lies in the approach employed by testers to identify defects in a software system. Automation testing typically takes place during and after development, utilizing automated tools and scripts to execute test cases and verify results. Conversely, manual testing relies on human intervention, with testers executing test cases by hand and validating expected outcomes.</p><p>Achieving optimal results necessitates a combination of manual and automation testing. Manual testing proves valuable for exploratory testing, while automation testing excels in executing repetitive, data-driven tests.</p><p>During the testing process, both automation and manual testing involve checking the requirements and criteria. Testers participate in requirements testing and assess whether the requirements are suitable for implementation, considering aspects such as UI/UX and other relevant perspectives. Additionally, they thoroughly test for functionality to ensure that everything operates as anticipated from the end-customer’s viewpoint.</p><p>Nonetheless, it is crucial to acknowledge that even with comprehensive testing, there is always a possibility of overlooking certain aspects. Hence, it is essential to have a comprehensive quality assurance (QA) process in place that thoroughly examines the software from top to bottom.</p><p>Simultaneously, conducting requirement checks plays a pivotal role in bug prevention. That’s why QA engineers should have the opportunity to engage in the early stages of development and collaborate closely with developers to verify requirements and criteria. One effective approach is to pair with developers to ensure that the completed work adheres to the required guidelines for various operating systems and browsers.</p><h4><strong>Our Test Approach</strong></h4><p>At Turbine Kreuzberg, we have adopted a comprehensive testing approach that encompasses two test environments — the<em> main</em> environment and the <em>stage</em> environment — alongside a production environment. The two test environments replicate the production environment, yet allow for modifications such as data addition, deletion, and other alterations.</p><p>The main environment serves as the test execution platform, where all tests are conducted before presenting new features or changes to the customer for review. On the other hand, the production environment serves as the core environment for all ongoing projects at Turbine, containing actual data. The testing process involves initial testing using test data, occasionally supplemented with real data.</p><p>In the event of any identified bugs, bug tickets are created within this environment. By fostering collaboration between the development and testing teams, we streamline bug detection and resolution processes.</p><p>Recognizing the need for enhancement in our QA processes, particularly due to the absence of previous QA practices, we are actively working on implementing improved testing methodologies. Our goal is to introduce additional expertise to assist us in this endeavor.</p><p>While our current approaches and strategies may not be flawless, they work rather well for now, and our primary focus lies in advancing and refining our testing processes moving forward.</p><h4><strong>Quality Assurance Tests We Typically Apply</strong></h4><p>Let’s take a look at several QA testing types that are performed by our teams throughout the development process.</p><ul><li><strong>Unit tests</strong> primarily occur during the development phase, where the focus lies on verifying the accuracy of individual code units or functions. These tests guarantee that each unit performs correctly in isolation, validating their functionality. <strong>Integration testing,</strong> on the other hand, shifts the emphasis towards evaluating the interaction between various modules. This entails verifying the proper passage of data between modules and ensuring seamless communication among them. Lastly, <strong>system testing </strong>examines the holistic behavior of the integrated system. It assesses how different components collaborate harmoniously to deliver the intended functionality and fulfill the system requirements. For instance, in a software project, developers commonly perform unit tests to validate the functionality of specific code units, while integration testing ensures smooth module interaction, and system testing evaluates the integrated system as a whole.</li><li><strong>End</strong>-<strong>to</strong>-<strong>end</strong> <strong>testing</strong> is a way of checking parts of the systems from A to Z and flow chains to detect issues — e.g. in an e-commerce platform from registration to login, adding a product to cart, checking out, and so on.</li><li><strong>Smoke</strong> <strong>testing</strong> and <strong>sanity</strong> <strong>testing</strong> play crucial roles in quality assurance during software development. Smoke testing involves conducting a preliminary assessment to ensure that all components are functioning correctly. It serves as a shallow check to quickly identify any major issues or showstoppers. On the other hand, sanity testing is a more comprehensive examination of the features to verify their proper functionality and behavior within the system. These tests are conducted continuously throughout the development process.</li><li>In addition to smoke testing and sanity testing, several other essential testing activities are performed. <strong>Requirements</strong> <strong>testing</strong> ensures that the software meets the specified requirements, while <strong>functional</strong> <strong>testing</strong> assesses the functional aspects of the system. <strong>Regression</strong> or retesting is conducted to confirm that previously identified bugs have been resolved and that new changes have not introduced any unexpected issues. Finally, <strong>acceptance</strong> <strong>testing</strong> is carried out before the software goes live and continues even after the product has been released.</li></ul><h4><strong>Conclusion</strong></h4><p>As I’ve shown above, we place immense importance on quality assurance engineering as a crucial factor in guaranteeing the utmost quality of our software products and services. Currently, we are in the process of reinforcing our dedicated QA department to enhance our testing processes, and we actively seek talented manual and automation QA engineers to join our team.</p><p>Throughout the development process, we employ various types of QA tests and continually refine our practices to ensure that our products adhere to industry standards and meet the evolving needs of end-users. Recognizing the value of a balanced testing approach, we employ a combination of manual and automation testing methods, yielding optimal outcomes in identifying bugs and errors.</p><p>As I look to the future, I see Turbine Kreuzberg’s strong QA commitment will help to keep pushing the quality of our software. And in the end, it’s the results that will speak for themselves.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f9f32b0a0c7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/t14g/improving-product-performance-9f9f32b0a0c7">Improving Product Performance</a> was originally published in <a href="https://medium.com/t14g">t14g</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implementing a Front-End Architecture using Vue.js and Spryker]]></title>
            <link>https://medium.com/t14g/implementing-a-front-end-architecture-using-vue-js-and-spryker-3801d576d9ce?source=rss----ff416c732167---4</link>
            <guid isPermaLink="false">https://medium.com/p/3801d576d9ce</guid>
            <category><![CDATA[spryker]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[vuejs]]></category>
            <dc:creator><![CDATA[Ana Margarida Picoito]]></dc:creator>
            <pubDate>Wed, 26 Apr 2023 12:56:23 GMT</pubDate>
            <atom:updated>2023-04-26T14:19:56.711Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vps-lLXxKLJrCENuWWUCRQ.png" /><figcaption>Midjourney / prompt: code, vue.js, software development, javascript, abstract, masterpiece — ar 16:9 — v5</figcaption></figure><h3>The Power Of “Just Doing It”</h3><p><strong>In the day-to-day life of a software developer, there are projects and then there are <em>projects — </em>the ones that present you with an immense technical challenge, as well as an enormous opportunity to grow and really come into your own. Recently, I had the chance to play an integral part in one of our commerce platform projects using Spryker: creating the front-end architecture from scratch using Vue.js framework as a base. Here’s my story and a technical walkthrough on how I tackled the challenge.</strong></p><p>Not long ago, shortly after joining a new project at Turbine Kreuzberg, I was presented with a new challenge. I knew right away that it wasn’t going to be easy, but I also knew this was an opportunity for me to grow beyond my limitations and build something I could be proud of.</p><p>Here’s the situation: the project I was joining didn’t have a front-end architecture defined yet. That was a new starting point for me. All the projects I had worked on previously, already had most of the structure defined. I was there to help maintain and improve. This was different.</p><p>I was in a position where I had to propose a good technical solution.</p><p>I struggled many times with my choices, second guessing and playing devil’s advocate, but I wasn’t scared to fail and try new approaches. My team trusted me, which was extremely important for me in order to feel like I could fail and not be pressured. In the end, everything worked out — and, I dare say, better than first predicted.</p><p><strong>Two options: now choose!</strong></p><p>Let’s start with my “sink or swim” decision. Basically, I was presented with two options to start building the front-end.</p><ul><li><strong>Option 1: </strong>The first involved using Twig, a template engine for PHP (check out the<a href="https://docs.spryker.com/docs/scos/dev/sdk/twig-and-twigextension.html"> documentation</a> for details), combine it with Javascript/Typescript, and then apply the old DOM (Document Object Model) manipulation.</li><li><strong>Option 2:</strong> The second option meant implementing Vue.js into Spryker, a framework that I was already familiar and felt really comfortable with.</li></ul><p>To cut the suspense: I chose the latter. I was going to stay engaged with Vue.js.</p><p>Each project has its own unique set of requirements, making it important to find solutions that are tailored to specific needs. What works well for one project may not be the best approach for another. Taking these factors into consideration, the chosen approach was to implement the project in a way that best suited its specific requirements.</p><p>I chose to go with Vue.js for a variety of reasons, but the most important factor was that this project required a fast delivery of front-end components. Therefore, I chose to have a slower start, so later I could develop much faster. The “delivery curve” was much steeper in this scenario.</p><p>After discussing with my team’s product owner and getting acceptance for my proposed approach, the “only” matter left was actually implementing Vue.js into Spryker. And at first, I had no idea where to begin.</p><p><strong>Research — and then: a breakthrough!</strong></p><p>So, what to do? Research, of course. I started researching on the implementation of Vue.js into Spryker and tried to gather all the information I could find. I was confident that the Spryker modules would remain functional, as the team required a complete interface that worked seamlessly. To ensure that we could deliver the project within the given time frame, we planned to gradually replace these modules with Vue components one by one. What surprised me was the lack of available information to help me in my endeavor, neither in Spryker’s official documentation nor in our internal documentation.</p><p>After days of research, the feeling of being lost frightened me a bit. In times like these, I always try to apply the “mimicking” method, i.e. applying the same steps I’ve seen done before in other implementations — the “do what you know” approach, essentially. I realized my previous project had a suitable structure to use as a basis.</p><p>My first key goal was to simply make Vue.js work. The first step was to display something that was rendered from a Vue component on the website. As mentioned before, it was very important that whatever strategy or implementation I found, it would still allow us to see the current website with all its Spryker modules. To be able to do this, our app would have to be “hybrid”, meaning it would need to accept the usage of both Spryker modules and Vue.</p><p>Still, I needed more information, so I threw myself into our internal front-end developer Slack channel and asked around for some suggestions on how to start doing it. Finally, after some help from my colleagues, I had a road map of the implementation I could follow, yet was still lacking some pretty important information on how to implement Vue.js into an existing software repository. Luckily, one of our trusted technical directors, Özkan Yilmaz, guided me towards some useful Spryker documentation on adding front-end frameworks to a demo shop. Unfortunately, this illustration was made by using React, so with the patience and kindness of Özkan, we had a deep look into it and discussed how it would be applied to other front-end frameworks. (If you are curious, here’s the documentation:<a href="https://docs.spryker.com/docs/scos/dev/front-end-development/yves/atomic-frontend/integrating-react-into-atomic-frontend.html#setup"> Integrating React into Atomic Frontend | Spryker Documentation</a>.) With this guide, it was going to be really quick and easy for me to achieve my first goal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGfesNelL6SXP-1ioK5Ckw.png" /></figure><h3><strong>How to implement a Vue.js front-end framework into Spryker</strong></h3><p>Alright, enough with the pleasantries. Let’s take a technical deep dive into what I did, step by step. In the documentation, Spryker implements React with atomic architecture (for more information:<a href="https://docs.spryker.com/docs/scos/dev/front-end-development/yves/atomic-frontend/atomic-front-end-general-overview.html#"> Atomic Frontend — general overview | Spryker Documentation</a>), so I took the suggested approach and tried it with Vue.</p><p><strong>Setup</strong></p><p>Here are the dependencies that need to be installed first:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QxdJ7Be962NzfmNl_ZXqSA.png" /><figcaption>Necessary dependencies to install</figcaption></figure><p>Webpack is a module bundler in general terms which is used to bundle JavaScript codelines and other assets (such as CSS stylesheets and images) into a single file or a set of files that can be loaded by a web browser. It powers the core frontend functionality of Spryker. It might be hard to configure it sometimes but if it’s not done, Vue.js would not work.</p><p>So, to use vue-loader with webpack, import this first:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CJOPmAcyBsTBj81mjTUWdg.png" /></figure><p>In JavaScript, the <em>resolve</em> object is a part of a Webpack configuration. It contains options that specify how Webpack should resolve modules and other dependencies when bundling the code.</p><p>This is what it looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RZOlCS06TI39-ra6Orb13Q.png" /></figure><p>In this resolve, the vue alias is being used to reference the <em>‘vue/dist/vue.esm-bundler.js’ </em>file, which is the main file for the Vue.js framework. This allows you to import Vue.js components using the vue alias instead of the full import path, which can make your code more concise and easier to read.</p><p><em>vue.esm-bundler.js</em> allows us to still use runtime template compilation while using Wedback as a bundler.</p><p>One thing that took me long to understand was that the order of the file <em>extensions</em> matter. These options can help Webpack find and include the necessary files in the final bundle.</p><p>To configure Webpack to use vue-loader for all <em>.vue </em>files, add the following code to the module’s rules array (which has vue loaders in it) before anything else:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YPApOPBoYZ4zgd-Dy39zzA.png" /></figure><p>Inside the plugins array, create an instance:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GD1stup-s20mhMJl5IFnpg.png" /></figure><p>Finally, your plugins section should look similar to this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YA2qGtAcjlZBEvkzX4HFVg.png" /></figure><p>The <em>DefinePlugin</em> is a Webpack plugin which allows you to define global constants that can be used in your code.</p><p>The last two lines (VUE_OPTIONS_API and VUE_PROD_DEVTOOLS) are necessary to prevent console errors and warnings from appearing in the browser’s console devTools due to “missing config”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGfesNelL6SXP-1ioK5Ckw.png" /></figure><h3><strong>Usage</strong></h3><p>When it comes to application of the code, Spryker recommends creating modules within the ShopUI framework and registering them to the index.ts file. This approach involves generating new instances of the component each time it is required.</p><p>Something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4JNGxN2oK5B8ElHTjRUrMg.png" /></figure><p>We need to put <em>vue-product-details </em>in a Twig file because it is used to render the product details page of the e-commerce website and the Vue component is responsible for dynamically displaying the product details like name, price, images, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vu137NN91cdNHjTjX7Gwmw.png" /></figure><p>This way, Spryker continuously creates a new Vue App instance for every created component.</p><p>In my opinion, this is not the ideal solution. Along with the fact that this is not the best performance wise, some inter-component communication necessities would’ve been lost, the state management can become more complex, translation problems among other things in the long-run.</p><p>Whenever a new Vue component is created, this solution uses the same code. By doing that, it causes code duplication which is also not an ideal solution.In this case, I thought of using a singleton design pattern to get rid of the recurring problems. I decided not to follow this approach blindly and started studying other ideas.</p><p>In my previous project, all the front-end and Vue framework was detached from the Spryker modules directory. We were using a front-end root folder and keeping every front-end related thing inside that. It had every potential to be an answer to my questions, but even though I wanted to implement this model, I was lacking time. All this implementation, trial-and-error discovery journey had already been highly time-consuming for me, especially during the sprints in which we, of course, should be presenting results to the client. Since it was an MVP project, it was important for stakeholders to see some progress. So, what to do?</p><p>I thought about applying a hybrid solution, kind of like a mixture of the approach in my previous project, but in a Spryker way, to keep some modularity.</p><p>I created a global wrapper root Vue component. This component enclosed the entire app, Spryker modules and all in order to avoid having to instantiate Vue components everytime they were used. By doing so, all components are initialized during the creation of the RootComponent. With this way, I could have both Spryker modules and Vue components inside this wrapper.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fozpICXfqic5GBvi8XSFiw.png" /></figure><p>So I created a global object and registered all Vue components that are used directly on the twig files.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dTO6Mrokpv24aemzVJ-j4w.png" /></figure><p>In <em>export</em>, register the shared components with its properties. This way, it makes it easy to import and use multiple related components in other parts of the application with a single import statement.</p><p>And then, they can be loaded by doing the following:</p><p>We create all components at once on the base level in the <em>vendor.ts </em>file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zSYSiMdy9nb5boFlMEe6zQ.png" /></figure><p>The second <em>import</em> statement makes the <em>sharedComponents</em> object available to the current file, so that the components in it can be used in the application from anywhere.</p><p>The third <em>import</em> statement is providing a global icon component to the application.</p><p>The <em>TjIcon</em> component can be used from anywhere without having to import it. It’s globally available.</p><p>If you create a <em>TjButton</em> component, unless you’re using it in a twig file, you don’t actually need to add it to <em>sharedComponents</em>.</p><p>This is how components are registered and created:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sw1F0O98TPBTRXM6FB52Vg.png" /></figure><p><strong>Let’s take a deeper look into this piece of code. What is this “tj-”/”Tj” prefix actually?</strong></p><p>After compiling, everything seemed to be working. I achieved the goal of seeing the component’s content on the website without ruining anything else. Everything was going well until I opened the browser console to check for errors.</p><p>And… <em>BOOM!</em></p><p>There were a bunch of warnings! <em>Oh, but warnings are not a big deal.</em> They were to me. I had to find a solution because I really wouldn’t leave it like that. The errors and warnings on the browser’s developer tools console mentioned some components which were not properly registered in the application. Vue.js was unable to resolve Spryker modules on the Document Object Model (DOM).</p><p>Spryker modules look like custom tag elements on the DOM and Vue doesn’t know what they are. They can look like <em>&lt;toggler-accordion /&gt;</em>. Since everything is now called inside the <em>vue-app</em> wrapper, Vue sees this and checks if it’s an HTML tag. If not, tries to resolve them as Vue components. This tag is neither of them, so it threw the error.</p><p>To resolve this, it was necessary to register these Spryker module tags as costume elements. According to <a href="https://vuejs.org/api/application.html#app-config-compileroptions-iscustomelement">Vue documentation</a>, you can register a custom element by doing the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OxV7DToQcVAJcA99EuGvew.png" /></figure><p>According to this, what should be done is prefix every Spryker module tag with something like <em>&lt;spryker-toggler-accordion&gt;</em> and then returning <em>tag.startsWith(‘spryker-’)</em> on the method above, but it would be way too many changes, so we can do it the other way around.</p><p>We prefix every Vue component with Tj and register all elements that don’t start with this prefix as custom.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ia6Ag5yzjp-k1MlP_puBLw.png" /></figure><p>After this, there were no more errors or warnings on the console.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGfesNelL6SXP-1ioK5Ckw.png" /></figure><h3><strong>Testing</strong></h3><p>This basic functionality worked very well until the merging process. I was getting a red pipeline because of failing tests. To figure out why, I looked at the screenshots (.png) that are taken every time there’s a failed Cest test, but all of them were completely blank.</p><p>First, I thought maybe there was a missing configuration but after a bit of moving things around and debugging, it looked like the problem was originating from the Vue wrapper. The contents inside a Vue component were not getting rendered. I didn’t feel comfortable checking it out all alone, so I asked Özkan’s help one more time. He said he didn’t experience something like that in his Spryker shop and had no idea why it was happening in ours. There was a lot of searching and a lot of time spent on this problem.</p><p>On the internet forums, there were people commenting about the same issue, rendering the Javascript of their webpages. In some posts, there were a few mentions about webdriver problems, so I checked Spryker’s documentation to see which webdriver was suggested (see:<a href="https://docs.spryker.com/docs/scos/dev/the-docker-sdk/202204.0/running-tests-with-the-docker-sdk.html#configuring-a-webdriver"> Running tests with the Docker SDK | Spryker Documentation</a>). Chromedriver was the default webdriver shipped with Docker SDK but for some reason it was not working. We also tried using other web drivers to no luck. So, we decided to ask for help one last time: Jorge Murta, another Technical Director at Turbine Kreuzberg, to the rescue!</p><p>It turned out that our Spryker shop instance didn’t have a configured Chromedriver, not by default as we initially thought. Codeception was fully configured to run with Chromedriver but the service itself was not configured, so we did as described in the documentation. I found it really strange that Spryker uses Chromedriver as default but without any pre-configuration. It was very time-consuming for us to solve this problem and especially frustrating since the solution was already in front of us.</p><p>So, what happened after the configuration?</p><p><strong>Green Pipeline! </strong>🟢</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGfesNelL6SXP-1ioK5Ckw.png" /></figure><h3><strong>Conclusion</strong></h3><p>So, this was my approach to this challenge and how I implemented a Vue.js-based architecture into a Spryker demoshop.</p><p>It’s very important to underline the fact that this was <em>“my”</em> solution. One project is not like the other and our maturity and knowledge is constantly growing. I’ve already started questioning some of the choices I made and documented. Was there a better way to do some parts?</p><p>Most likely there was, but I did the best I could with the knowledge I had. And overall, I’m still convinved of our implementation.</p><p>Even if you think you lack the experience to solve a challenge you’ve never had to tackle before, “just doing it” will go a long way. Of course, always be aware of what you don’t know and never hesitate to ask others to help fill the gaps. In the end, I didn’t just gain an immense amount of technical knowledge, but also learned something about myself.</p><p>What we develop today will always have the potential to be better tomorrow. We just need to stop being scared, overthinking and just try it. This process has convinced me of the usefulness of taking an experimental approach. Thank you to my team and everyone who trusted and helped me along the way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3801d576d9ce" width="1" height="1" alt=""><hr><p><a href="https://medium.com/t14g/implementing-a-front-end-architecture-using-vue-js-and-spryker-3801d576d9ce">Implementing a Front-End Architecture using Vue.js and Spryker</a> was originally published in <a href="https://medium.com/t14g">t14g</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unconscious Bias: How to Start a Journey of Rethinking in Your Company]]></title>
            <link>https://medium.com/t14g/unconscious-bias-how-to-start-a-journey-of-rethinking-in-your-company-e145dca4710c?source=rss----ff416c732167---4</link>
            <guid isPermaLink="false">https://medium.com/p/e145dca4710c</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[diversity-and-inclusion]]></category>
            <category><![CDATA[recruiting]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[hr]]></category>
            <dc:creator><![CDATA[Sophie Barth]]></dc:creator>
            <pubDate>Wed, 05 Apr 2023 14:55:50 GMT</pubDate>
            <atom:updated>2023-04-05T14:59:52.578Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LbYi1teVBcH4iPAvp8Sihg.png" /><figcaption>Sorting people into categories is a convenient and often unavoidable way to process and store information. We need to be conscious of the biases that drive our decision making. (Illustration generated via Stable Diffusion)</figcaption></figure><p>Often, when I tell people I work at <a href="http://turbinekreuzberg.com/en">Turbine Kreuzberg</a>, they immediately think of a soccer club, whether consciously or not. While that’s not a problem, and I enjoy clearing up the misunderstanding, it’s a good everyday example of what our brains do to fill in the blanks. Recently, I was holding a master class on unconscious biases for all colleagues at the company, something I never thought I would be able to do. Why? Because I had my own prejudices.</p><p>The research and preparation for the master class opened my eyes substantially, because I became aware of how many prejudices I had and still have towards other people and myself. Whether on the subway, in the supermarket, in the office or during job interviews, you quickly fall into judgmental thought patterns and put other people in a box.</p><p>For the past four years, I’ve worked as a recruiting manager and screened dozens of CVs every day. Within seconds, I knew if the applicant seemed suitable to me and I wanted to invite them for a first interview. I came to that decision based on signs like a neat layout, a serious and good looking profile picture, similar job stations or common interests. Very likely, I missed out on many good interviews with interesting interviewees as a result.</p><p>Turbine Kreuzberg is a software company with more than 100 developers — 90 percent of them are male. Did I get you now? Did you just think of an introverted man with long hair and a t-shirt with Star Wars comic print?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGfesNelL6SXP-1ioK5Ckw.png" /></figure><p><strong>Biases are deeply ingrained in us</strong></p><p>Every day our brains are flooded with millions of pieces of information. Less than 5 percent of them are consciously processed. It’s what our brain does to save cognitive resources, or simply, to avoid exploding. We filter and categorize this information unconsciously and subsequently make decisions that are not always good or right. From small everyday issues, to our private life to important professional decisions: all can be strongly influenced by our categorizations. Here are just a few examples: Only girls wear pink, I don’t like green vegetables, I don’t want to date a person because I don’t like their hairstyle, my boss’s favorite colleague gets the new project, the candidate who is most similar to the team gets the offer.</p><p>The way we label and judge is trained into us from an early age and so, also anchored in our personality. The cultural influences we grow up in, our environment, our self-perception, our upbringing, all the media we consume, and lastly our work environment all influence our thought patterns. Currently, more than <a href="https://www.teachthought.com/critical-thinking/cognitive-biases/">180 biases</a> are known. For instance, do you know the IKEA effect? People value objects more when they have assembled them themselves. Another more or less well-known example in the work context is the Dunning-Kruger effect: incompetent people tend to overestimate their own knowledge and skills.</p><p>I presented these and more biases at the masterclass I held. Almost 30 colleagues registered for the training session, from different teams, women as well as men, techies and non-techies. Thus, they have taken the first step towards reducing unconscious biases. A one-time training is of course not sufficient to completely eliminate them, but it is a first step. This was also important for me to communicate to my Turbine colleagues. A change in mindset does not happen overnight. It is a journey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGfesNelL6SXP-1ioK5Ckw.png" /></figure><p><strong>From theory to practice</strong></p><p>In addition to theory on the origin of biases, the Cognitive Bias Codex and their negative effects, there was a practical exercise, too. Together, we found the most common biases in our everyday work and tried to think of ways to reduce them in the future. For us, most biases and false assumptions occur in recruiting and feedback situations. For example, gender, name, or age biases can occur when screening CVs. To avoid that, consistent and structured evaluation sheets as well as blind reviews, in which names and pictures are removed, can be possible solutions for fair recruiting.</p><p>In code reviews, people are sometimes assigned better or worse coding skills or certain sympathies or antipathies towards them in advance just because you have read their name. How about anonymous tickets in the future that guarantee equal treatment?</p><p>Cognitive distortions in our judgment cannot be entirely prevented and a complete rethink does not happen after one training. A first step is to create awareness for the presence of our biases, so that everybody can reflect on oneself and one’s decisions. Since we have to make so many small decisions day in and day out, we can try to schedule more time for important ones (or just sleep on it once) to avoid falling into biased patterns. When possible, make decisions collectively, for example when hiring new employees. Tools like checklists or policies that are embedded in the corporate culture (a common example here is the Code of Conduct) help to make fairer decisions as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGfesNelL6SXP-1ioK5Ckw.png" /></figure><p><strong>Biases create disadvantages both personal and competitive</strong></p><p>I’ve been talking a lot about unconscious biases now and, at least in the world of LinkedIn, the term seems to have become a buzzword. You may think to yourself, the world won’t end due to one bad decision more or less, or no one hears the biases in my head. The truth is: unconscious biases can create unfair or negative advantages and disadvantages for people. Employees quit because they feel uncomfortable or discriminated against, the wrong person is hired, and ultimately all of this leads to a less diverse and inclusive company. And this, as we hopefully all know by now, is a clear competitive disadvantage and can lead to lower overall performance.</p><p>Having read this article to the very end means that you are interested in this topic. This is a good sign. Maybe there will be training in your company soon as well. Please take part. As said, awareness that we all have unconscious biases is the first step towards a society more free of judgment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGfesNelL6SXP-1ioK5Ckw.png" /></figure><p><em>Thoughts? We’d like to hear them. Reach out to Sophie on </em><a href="https://www.linkedin.com/in/sophie-barth"><em>LinkedIn</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e145dca4710c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/t14g/unconscious-bias-how-to-start-a-journey-of-rethinking-in-your-company-e145dca4710c">Unconscious Bias: How to Start a Journey of Rethinking in Your Company</a> was originally published in <a href="https://medium.com/t14g">t14g</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Intro to Carbon Package: A PHP Extension of DateTime]]></title>
            <link>https://medium.com/t14g/intro-to-carbon-package-a-php-extension-of-datetime-7158a5bc9cf7?source=rss----ff416c732167---4</link>
            <guid isPermaLink="false">https://medium.com/p/7158a5bc9cf7</guid>
            <category><![CDATA[php-developers]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[php]]></category>
            <dc:creator><![CDATA[Astar Bekturov]]></dc:creator>
            <pubDate>Thu, 23 Mar 2023 15:26:56 GMT</pubDate>
            <atom:updated>2023-03-23T15:52:01.376Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oaJdIYM08RfjotrAzOky4g.jpeg" /></figure><p><strong>As any PHP developer will know: working with dates and times in PHP can be a challenging task. Especially while working on comprehensive e-commerce platforms like I do, complex date and time calculations are usually inevitable. Fortunately, the Carbon Package provides a powerful and intuitive solution. It is a popular date and time library that is built on top of PHP’s native DateTime class. It provides a fluent API for creating, manipulating, and formatting dates and times in a wide range of formats.</strong></p><p>Here are some more reasons why you should consider using Carbon Package:</p><ul><li><strong>Simplifies date and time manipulation: </strong>The Carbon package provides a simple and intuitive API for working with dates and times in PHP. It makes it easy to perform common operations like adding or subtracting time intervals, formatting dates and comparing dates.</li><li><strong>Time Zones:</strong> Carbon has timezone support, which is essential for working with dates and times across different time zones. It simplifies the process of converting dates and times between different time zones, and ensures that your code behaves consistently regardless of the server or client time zone.</li><li><strong>Extensible:</strong> Carbon is a powerful and extensible package, which means that you can customize it to make it fit your specific needs. You can create your own date and time formats, add support for additional time zones, and extend the functionality of the package to include additional features.</li><li><strong>Widely used and well documented:</strong> Carbon is a widely used package, and as such it has a large community of developers who contribute to its development and provide support through forums and documentation. It means that there are many resources available for learning and using the package effectively.</li></ul><p>In this article, we’ll take a closer look at the Carbon package for PHP and how it can simplify your date and time handling tasks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGfesNelL6SXP-1ioK5Ckw.png" /></figure><h4><strong>Installing and implementation</strong></h4><p>You can find the package on its original website at <a href="https://carbon.nesbot.com/">Nesbot Carbon</a>. It is recommended to use composer, which is a dependency manager for PHP. On the page, you can find all the necessary information about installation and setup. Open your terminal and let the guide navigate you. Of course, don’t forget to update your dependencies afterwards.</p><p><strong>Usage</strong></p><p>Carbon Package aims for clear and easy usage across a number of areas. Here are some of them:</p><ul><li><strong>Date manipulation: </strong>With Carbon, you can easily perform date calculations and manipulations, such as adding or subtracting days, weeks, months, or years from a given date.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SUTPfpzNM_5Fd6Q_1ME0RA.png" /></figure><ul><li><strong>Timezone support:</strong> Carbon provides support for working with different time zones. You can easily convert a date and time to another timezone, and also determine the offset between time zones.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ACLvb3fXDzf4tgjhWcHOpQ.png" /></figure><ul><li><strong>Date formatting: </strong>Carbon offers a range of formatting options that allow you to format a date and time in a human-readable way.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PZaI3bw_c3HeApLaD4W9SQ.png" /></figure><p>//Outputs referencing a random date</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*i7fhR9kQP2vcKVyX" /></figure><p>PHP manual (found here: <a href="https://www.php.net/manual/en/datetime.format.php">PHP: DateTimeInterface::format — Manual</a>) offers a chart of formats that has been used mostly in DateTime Class, but also in Carbon Package. The Carbon package additionally has formatting functions, which is much more practical than digesting all the parameters in the chart.</p><ul><li><strong>Easy comparability: </strong>Carbon makes it easy to compare dates and times, and to determine if a date is before or after another date or in between.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UkHd1AW-_hjrvLdZmOhPNw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGfesNelL6SXP-1ioK5Ckw.png" /></figure><h4><strong>DateTime Class vs Carbon</strong></h4><p>Comparing the two methods of handling date and time manipulation helps us see the differences easily. As an example, I calculated the delivery date using processing and delivery days of a product and applying rule to skip weekends, as you can see in the code below. I did it in two different ways:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mp57BZKK1tM8vUs_-_TDCg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGfesNelL6SXP-1ioK5Ckw.png" /></figure><h4><strong>Increasing readability</strong></h4><p>With its easy and understandable structure, Carbon Package increases the readability of the code. The names of the functions are compatible with their missions. This makes it possible to intuitively understand the functionality of the code by just reading the names.</p><p>Moreover, Carbon helps us to facilitate maintenance of the code. Since the code already looks neat and tidy, you can see defects or mistakes right away, and then make the necessary changes accordingly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGfesNelL6SXP-1ioK5Ckw.png" /></figure><h4><strong>Conclusion</strong></h4><p>I strongly recommend using the Carbon package while coding, both to my co-workers and developers at large. It is the cleanest and most legible way to show date and time operations in PHP. Plus, as I’ve shown, it’s easy to set up, practical in usage, and smooth in maintenance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGfesNelL6SXP-1ioK5Ckw.png" /></figure><p><em>Got thoughts or questions? We want to know what you think. Reach out to me at </em><a href="/service/mailto:aster.bekturov@turbinekreuzberg.com"><em>astar.bekturov@turbinekreuzberg.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7158a5bc9cf7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/t14g/intro-to-carbon-package-a-php-extension-of-datetime-7158a5bc9cf7">Intro to Carbon Package: A PHP Extension of DateTime</a> was originally published in <a href="https://medium.com/t14g">t14g</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Company You Want to Work For]]></title>
            <link>https://medium.com/t14g/the-company-you-want-to-work-for-31a0710d5a8a?source=rss----ff416c732167---4</link>
            <guid isPermaLink="false">https://medium.com/p/31a0710d5a8a</guid>
            <category><![CDATA[employer-branding]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[people]]></category>
            <category><![CDATA[hr]]></category>
            <category><![CDATA[employer-brand]]></category>
            <dc:creator><![CDATA[Sérgio Godinho]]></dc:creator>
            <pubDate>Thu, 16 Mar 2023 15:09:51 GMT</pubDate>
            <atom:updated>2023-03-16T15:09:51.778Z</atom:updated>
            <content:encoded><![CDATA[<h4>Employer Branding in Tech</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ySyzj80jzyN-CvG2.png" /><figcaption>An employer brand mirrors a company’s lived values to the outside (Image: generated via Stable Diffusion).</figcaption></figure><p><strong>Do you ever find yourself daydreaming about joining “that company”? Congratulations, you’re feeling the impact of a great employer brand. The focus of employer branding is to create a connection between a workplace and a person’s life goals. As such, companies across many industries are giving the field increasing relevance. Let’s take a deeper look at the phenomenon, drawing on my own experience in tech recruiting and helping to build the employer brand at Turbine Kreuzberg.</strong></p><p>Let’s start from the beginning. An <em>employer brand</em> is how a company is perceived as an employer, while <em>employer branding</em> refers to a set of strategies put in place to build an employer brand over time. Every company, whether they like it or not, has an employer brand. It plays a central role in any company’s future success, as it directly influences how you attract new talent and retain current team members, as well as employee engagement and the company’s overall reputation. As such, it is crucial that people can connect to an employer brand in a personal way.</p><p>This is particularly important in the <strong>tech</strong> <strong>sector</strong>, where many companies are competing for the same pool of skilled employees and there is a shortage of skilled labour. Our industry is known for its innovative and dynamic culture. Employees in tech are often looking for more than just a job, they want to work for companies that are pushing the boundaries of technology and making a positive impact on the world. The industry’s high turnover rates are well known, making it especially important to retain top talent.</p><p>So, along with the external impact, good employer branding clearly impacts internal workplace culture as well. Let’s have a look at some main internal and external impacts:</p><h4><strong>External Impacts</strong></h4><ul><li><strong>Recruitment (Attracting Talent).</strong> Candidates are more likely to apply for jobs at companies that are perceived to be more desirable places to work. In some cases, candidates may even be willing to accept lower salaries at companies with exceptional workplace cultures.</li><li><strong>Increase Diversity. </strong>By positioning itself as a great place to work, it attracts a wider pool of job seekers from diverse backgrounds. And diverse teams have been shown to foster innovation, creativity, and improved problem-solving abilities.</li><li><strong>Brand Awareness.</strong> Companies like to partner with companies that are recognized as great places to work. While the saying “there is no bad publicity” exists, the truth is that it doesn’t apply to employer branding. Word of mouth plays a critical role, so take steps to improve it.</li></ul><h4><strong>Internal Impacts</strong></h4><ul><li><strong>Increase Retention Rates.</strong> People are more likely to stay with a company that they perceive to be a good place to work. Everyone is immensely internally motivated to avoid losses. If a company poses it so well that it becomes almost unjustifiable to move on, people will do so less frequently.</li><li><strong>Team Satisfaction &amp; Increased Productivity.</strong> When employees feel proud of the company they work for and believe in its values and mission, they are more likely to be motivated to contribute their best efforts. It is important to master a skill, sure, but to be engaged with the task, they must understand and identify with the why.</li><li><strong>Reduce Hiring Costs.</strong> If fewer people are leaving and more are looking to work with you, your hiring costs are immediately decreasing, giving room for that value to be invested somewhere else in the business.</li></ul><p>If this is so influential, what can companies do to improve their employer brand?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGfesNelL6SXP-1ioK5Ckw.png" /></figure><h4><strong>Define an EVP: Employer Value Proposition</strong></h4><p>An EVP is the unique set of benefits and rewards that you offer to your employees in exchange for their skills, experience, and hard work. It’s what makes you a great place to work and sets you apart from other employers. Think of it as your secret sauce for attracting and retaining the best talent.</p><p>In the tech or software development field, an important aspect of a good EVP is the opportunity for career development and growth. Your employees are likely highly skilled and motivated individuals who are passionate about their work and want to continue learning and advancing in their careers. Make sure that your EVP includes opportunities for training, mentorship, and career advancement, as well as challenging and engaging work that allows your employees to use their skills and expertise.</p><p>If done right, the company’s website and its social media channels are the most powerful EVP broadcasters there are. Keep in mind that employer branding is always done from the inside/out and never outside/in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGfesNelL6SXP-1ioK5Ckw.png" /></figure><h4><strong>Create an attractive company culture</strong></h4><p>What exactly is company culture? There are various versions of what it could mean, but for the sake of this article, we will consider the values and behaviours a company encourages, whether deliberately or not. Creating a positive company culture is crucial for attracting and retaining top talent. Be aware that there are no shortcuts here. Everyone responsible for setting practices and processes should be involved to effect real change.</p><p>There’s so much to be said and done on this topic, that there are hundreds of books regarding it. Read them. Be constantly learning. To provide a quick overlook, these are often recommended:</p><ol><li><strong>Gauge your status quo. </strong>The first step of every change process is to assess the current status. It’s essential to start by taking a hard look at how current employees perceive the company culture, values and consequently the employer brand. Gathering feedback — anonymous, so it can be as close to the truth as possible — and identifying areas for improvement can help develop a clear understanding of what needs to change.</li><li><strong>Define standards and communicate them. </strong>Setting a well-defined guideline of behaviours and values should be a priority. This allows every team member to know what is expected of them, allowing them to find the right approach in case of doubt. It also serves the purpose of hiring for cultural fit. As a rule, it’s best never to presume anything: one person’s basic learned behaviour may be completely new for another person. Transparency is key in this process: portraying an image that doesn’t correspond to the actual status quo will only create dissatisfaction in the long run. Recently, Turbine Kreuzberg has been revising its <a href="https://turbinekreuzberg.com/en/code-of-conduct"><strong>Code of Conduct</strong></a> and organized interactive debate on its contents, open to anyone interested in the topic. The code of conduct is not only shared internally, but is publicly available for anyone to read and learn about our ideals. Moreover, it’s important to gather realistic benchmarks by looking at other companies and how their example may apply to your own situation.</li><li><strong>Make it personal. </strong>Finally, it’s important to recognize who the best ambassadors for a company’s employer brand are. Ask yourself: who are the people that embody what our company stands for? Then, give them a microphone — literally. Take them to conferences, create social media content around them, and bring them to network sessions. If they embody what the company aims to be, they will likely attract people that identify with it. Never underestimate the impact of your team members on attracting new talent. You can claim to be “young and vibrant” all you want if the people representing you are exactly the opposite.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGfesNelL6SXP-1ioK5Ckw.png" /></figure><h4><strong>Keep in mind that review websites are a big tool</strong></h4><p>Word-of-mouth is one of the most powerful and impactful factors for a company’s employer brand. No industry is immune to this, no matter how niche or large. People know people, and they value each other’s opinions. Employer review platforms make what used to be a closed group phenomenon readily available worldwide.</p><p>According to Rui Miranda of <a href="https://pt.teamlyzer.com/"><strong>Teamlyzer</strong></a>, one of the main review platforms for IT companies in Portugal, these platforms play a fundamental role because the feedback received by companies helps them understand how they are perceived by employees and potential candidates. In the end, it’s the data that counts, as it allows companies “to understand what professionals value most, and subsequently present their value proposition based on real data.”</p><p>So, platforms not only serve the purpose of attracting talent, but can also be seen as an honest feedback tool. “It is very important for companies to monitor their reviews and work to improve the work experience and internal culture”, Rui says.</p><p>For example, at Turbine Kreuzberg, we’re constantly looking at the anonymous feedback provided on the various employer review tools available on the market. Not to mention we were very glad when we noticed we are #3 on <a href="https://pt.teamlyzer.com/companies/ranking">Teamlyzer’s national overall ranking</a>. In the end, hearing what people say about you seems to pay out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGfesNelL6SXP-1ioK5Ckw.png" /></figure><h4><strong>Find partners that share your ideals</strong></h4><p>If a tree falls in a forest and no one is around to hear it, does it make a sound? The same could be applied to an employer brand: if you’re creating a great place to work, but no one knows about it, does it improve your employer brand? That’s why it’s crucial to let everyone know what you stand for. One way to do that is via partnerships all sides can benefit from.</p><p>For example, Turbine Kreuzberg has recently partnered with <a href="https://www.portuguesewomenintech.com/">Portuguese Women in Tech</a>, an organization that works to support and encourage more females to pursue a career in tech. Liliana Castro, the co-founder of the movement, explains that “such initiatives are only possible with the support of tech companies that aim to balance the ecosystem by bringing more women into technology development and leadership roles. Naturally, opening the door to these opportunities and professionals is an added value that these companies can/should present in an employer branding context.”</p><p>Liliana suggests that “if, when choosing new professional challenges, women in tech can choose between companies and proposals, a company that focuses on giving new opportunities to these professionals will be strategically better positioned in the market.” This resonates with our own beliefs: we work hard to get the word out to everyone in that community that Turbine Kreuzberg is in the same boat. That’s why partnering with people or organizations with the same goals is such an important tool in creating your employer brand.</p><p>In sum, the success of any company depends on the people who work for it, and a strong employer brand can help to attract and retain the best talent. Investing in this field is no longer an option, but a necessity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGfesNelL6SXP-1ioK5Ckw.png" /></figure><p><em>Got thoughts? We want to hear what you think. Send us your comments at hello@turbinekreuzberg.com or find Sérgio on </em><a href="https://linkedin.com/in/sfgodinho/en"><em>LinkedIn</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31a0710d5a8a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/t14g/the-company-you-want-to-work-for-31a0710d5a8a">The Company You Want to Work For</a> was originally published in <a href="https://medium.com/t14g">t14g</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Diversity is more than a quota: Turbine Kreuzberg increases diversity and inclusion as a software…]]></title>
            <link>https://medium.com/t14g/diversity-is-more-than-a-quota-turbine-kreuzberg-increases-diversity-and-inclusion-as-a-software-a26bc69a3e89?source=rss----ff416c732167---4</link>
            <guid isPermaLink="false">https://medium.com/p/a26bc69a3e89</guid>
            <category><![CDATA[diversity]]></category>
            <category><![CDATA[female-talent]]></category>
            <category><![CDATA[inclusion]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[equality]]></category>
            <dc:creator><![CDATA[Sophie Barth]]></dc:creator>
            <pubDate>Wed, 08 Feb 2023 16:12:22 GMT</pubDate>
            <atom:updated>2023-02-08T16:52:42.744Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Diversity is more than a quota: Turbine Kreuzberg increases diversity and inclusion as a software company.</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bK9_h_idBVkKp17Zl_r88g.png" /><figcaption>A painting by Paul Gauguin of lucky Turbinies celebrating a very successful year.</figcaption></figure><p><strong>Diversity is more than a quota of women and a rainbow flag — let me tell you how Turbine Kreuzberg faces the challenge of increasing diversity and inclusion as a software company.</strong></p><p>If diversity were a place, it would be Berlin-Kreuzberg. This is where the most diverse people and cultures meet and exactly where our headquarters, Turbine Kreuzberg, is located. Last year, our management team announced that the software agency’s most important strategic goal is to become more diverse and hire, not only more female talent, but an overall more diverse people. More specifically though, I want to focus on the female goal. By 2025, the team should consist of one-third women. Ambitious goal? No problem, we love challenges. But what do we want to do differently to find the unicorns in the IT industry?</p><p>Currently, Turbine employs more than 140 people, spread across three locations in Berlin, Faro and Bishkek. Men make up a significantly larger share of the workforce. Only a few IT positions are held by female employees, but the team is enriched by a variety of nationalities. For us, diversity is not limited to the gender of the employees. When we talk about inclusion, we mean it. We like to think we can create an environment where all employees can be 100% themselves and have a sense of belonging.</p><p>But where does our diversity journey start? To determine a status quo, female Turbinies from different departments, with different lengths of service and at different locations were asked in interviews how they perceive diversity at Turbine Kreuzberg, how comfortable they feel as women in their teams and what measures they would like to see taken in the future. The responses from the interviews were very positive and informative. All of the women were able to report that they felt very comfortable and only rarely had the feeling that they were treated differently or seen as less competent because of their gender. The compatibility of work and family was named as particularly positive. The greatest wish is to have more women in their own teams, to offer further education and training on the topics of diversity, equity and inclusion for all colleagues, and also to see women in management positions. And you know what? Just to simply have more female energy around because, let’s face it, a well-balanced everything is, in fact, everything.</p><p>In the mighty words of Emma Watson, we asked ourselves, “If not now, when?” To break down and strategize, we formed an Awareness Team and collectively developed a strategy in a 4-pillar workshop based on: Recruitment, Internal Awareness and Education, Professional Development and Advancement, and Culture and Policies.</p><p><strong>Recruitment:</strong></p><p>Recruitment is a particularly important driver of our diversity goal. In order to hire more women, more women must be reached and actively approached on places like LinkedIn. In the internal interviews, it was frequently criticized that there is often only one woman in the development teams.</p><p>As a first step, our Team Architects have made job descriptions more gender neutral and formulate job requirements more open. Statistics show that women are more likely to refrain from applying for positions if they do not meet all requirements. Men, on the other hand, meet 3 out of 10 and still feel they are a good enough fit to apply. To reduce this phenomenon, we added our “Check, Check, Uncheck” box to job ads.</p><p>We targeted our social media posts to the female audience by featuring and interviewing more female team members. Female interviewees and background voices also aim to subconsciously appeal to female future Turbinies.</p><p>In addition, we didn’t miss the chance to go to events in person again and present ourselves as an employer. At WomenHack Berlin, we took on a little adventure and conducted numerous job interviews in a speed dating format. Our specially branded bandanas went down very well with the female visitors. We met more cool queer talent at HelloFresh’s FreshPride event and at Unicorns in Tech’s afterwork events. In spring 2023, we plan to host our own DEI Meetup in our office, together with DEI Advocates Berlin.</p><p><strong>Internal Awareness and Education:</strong></p><p>We see awareness as the first step in gaining acceptance among our employees. First, we wanted to build up expertise as an awareness team so that we could provide advice and support when questions arose. Then it was a matter of recording the knowledge and making it easily accessible to all employees. We regularly share current articles and statistics on diversity and gender equality topics within the company and hope to be able to initiate one or more discussions.</p><p>In addition, we provide a central Diversity Library located in our internal Confluence for our employees to revert back to. This breaks down the major topics of diversity, equity and inclusion into smaller sections using short and simple content pieces with definitions, statistics and graphics. Further links provide colleagues who are hungry for knowledge with even more details. This year, company-wide workshops, masterclasses and catch-up sessions with selected target groups are to follow, designed to help and empower people to live even more inclusively in their everyday work.</p><p><strong>Professional Development and Advancement:</strong></p><p>Thanks to a great Learning &amp; Development team, established in May of last year, we have the chance to develop junior team members into experts with clearly guided career paths. In this way, we can develop women into senior positions in the future, as requested in interviews with colleagues, and as is the Turbine way.</p><p><strong>Culture and Policies:</strong></p><p>At Turbine Kreuzberg, we are very proud of our culture, which has been able to evolve positively despite growth and a hybrid work model. Our work structures as well as the trust our management team places in our employees were particularly praised in the employee interviews. Turbine Kreuzberg offers flexible working time models and working locations in order to be able to combine family and career in the best possible way. Our employees can also take parental leave without a guilty conscience. When revising our Code of Conduct, we actively involved employees and offered open feedback sessions. Our female colleagues were particularly pleased about the creation of a closed Slack channel for them, in which all non-male Turbinies can exchange ideas across locations and plan next Coffee Breaks. In Berlin, we held the first female dinner in December 2022 which brought up some very interesting talks and exchange of experiences. Next on the activity agenda is one fun-filled night of karaoke.</p><p>Since we took a closer look at DEI work at Turbine Kreuzberg in September 2022 and developed a strategy, we have already been able to take away the first lessons learned. For instance, inclusive language does not begin and end by replacing “Hi guys” in group chats with “Hi everyone”. We must always keep in mind the linguistic and cultural differences between Germany and Portugal, as well as Kyrgyzstan. In addition, there is no one-fits-all solution in implementing DEI initiatives. Not all best practices from other companies fit us. Open communication with all employees is super important. The goal of achieving more diversity is a change management process that requires employee buy-in. As you probably already know, diversity work is not possible as a lone wolf. We were able to successfully implement many ideas with the support of our Team Architects, Learning and Development Specialists, our Brand &amp; Communication Team, and the new Awareness Team.</p><p>In summary, just hiring more women in a software company does not necessarily lead to more diversity and satisfaction of the female team members. An inclusive work environment is a prerequisite for an empowering work one. Meetups greatly help to build a network of, and understand the female employee market. Furthermore, employees need the space to understand the “why” and the “how” of diversity measures. Through continuing education, training, open communication and opportunities for participation, this is possible. Development prospects and flexible work structures bind women, as well as people in general, to a company for a long time because this is what they want from an attractive employer. With support from upper management, and a strong team that wants to advance diversity, DEI initiatives will be successful and, to be honest, would be half the fun to plan and implement.</p><p>Stay tuned to see how our team evolves. The journey has just begun! We’re sure you’ll see us at another meetup soon here and there, or just drop by our offices and/or digital channels.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a26bc69a3e89" width="1" height="1" alt=""><hr><p><a href="https://medium.com/t14g/diversity-is-more-than-a-quota-turbine-kreuzberg-increases-diversity-and-inclusion-as-a-software-a26bc69a3e89">Diversity is more than a quota: Turbine Kreuzberg increases diversity and inclusion as a software…</a> was originally published in <a href="https://medium.com/t14g">t14g</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile Coaching: A Toolkit]]></title>
            <link>https://medium.com/t14g/agile-coaching-a-toolkit-1619ed5c4ac2?source=rss----ff416c732167---4</link>
            <guid isPermaLink="false">https://medium.com/p/1619ed5c4ac2</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[agile-coaching]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Ricardo Minas]]></dc:creator>
            <pubDate>Thu, 12 Jan 2023 15:35:36 GMT</pubDate>
            <atom:updated>2023-01-16T08:38:16.144Z</atom:updated>
            <content:encoded><![CDATA[<h3>3 Comprehensive Tools to Help You Shape Your Approach as an Agile Coach</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ie3V3Pc4V1cgOfAvlYl0DQ.png" /></figure><p><strong>With the vast amount of literature available and a myriad of best practices shared all over the web, the world of agile coaching can sometimes seem overwhelming. First off: that’s a good thing. There is no single right approach to agile coaching — only the one that suits you, your daily work and your team best. Still, I want to offer an overview of three useful tools that have helped shape my thinking about agile coaching. Hopefully, they can assist you as well by allowing you to locate your own capabilities and areas for growth.</strong></p><p><strong>Not all Agile Coaches are the same</strong></p><p>Let’s preface this by taking a look at the various types of agile coaches. Generally speaking, there are three levels of agile coaching that we can identify: agile to team, agile to agile, and agile to organization.</p><p>The <strong>Team Coach</strong>, also known as the Team Facilitator, is responsible for promoting agile practices and fostering collaboration on one or more teams, improving their teamwork and organizational capabilities as well as conscious communication. Often, this is a task for the Scrum Master, for example by coaching the Product Owner and other agile practitioners on agile principles and how to work within the Scrum Framework. They are often expressly technical, driving agile software development techniques within the team, such as refactoring, unit testing, or Test Driven Development.</p><p>The <strong>Agile Coach </strong>takes a more general approach, often helping to develop teams by coaching and mentoring other agile practitioners (scrum masters/developers, product owners) on working with agile methods and promoting the agile mindset and adoption. Their domain knowledge allows them to take an advisory role for managers.</p><p>Finally, the <strong>Enterprise Agile Coach </strong>acts as a change agent for an entire organization, promoting the adoption of agile practices by developing the organization’s capacity for implementing them. They help define the strategic path for creating cultural change and coaching agile leadership. Typically, they work throughout all organization levels in order to structure and increase its agility.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HcGd-JKyrhKamKKpPwg3Yg.png" /></figure><p><strong>Three tools: ACCF, Growth Wheel, and Zen Ex Machina Canvas</strong></p><p>Being conscious of different agile coaching stances helps to identify approaches any coach might take while interacting with individuals, teams and organizations. For me, there are three tools that may help in this, which all land on the same basis and principles. It’s all about inspecting and adapting, always assessing where we are right now, where we want to be and what we need to do to get there.</p><p><em>Agile Coaching Competency Framework</em></p><p>Originally developed by Lyssa Adkins and Michael Spayd for the Agile Coaching Institute, the <strong>Agile Coaching Competency Framework</strong> (ACCF) helps agile coaches categorize the different stances that one might take when supporting agile teams and organizations. In a nutshell, the ACCF breaks down the competencies necessary for agile coaching into three levels of mastery: technical, business and transformation. In addition, there are two areas of focus: content, which is the base for the teaching and mentoring part of agile coaching, and process, which focuses on professional coaching and facilitation. This approach helps agile coaches identify their coaching “<strong>core stance</strong>”, meaning that particular activity that you’ve performed for quite a while now, been improving and growing on, and feels really comfortable and easy to execute. It also shows which areas you should improve on to fulfill your role.</p><p>The ACCF has been extended and adapted — agile coaching is an evolving ecosystem, after all — to also reflect other key components, such as <em>Mindset and Behaviors</em>, and <em>People and Influence</em>. This brought into perspective something that became the basis for any agile environment, which is the agile mindset, by highlighting the need of understanding not only what it really is, and how important it is for an Agile Coach to be a living example of what those values and principles exist for. An agile coach must be a <strong>Servant Leader</strong> who always strives for continuous learning and improvement. Communication is key for an agile coach, but it should be thoughtful and positive, to generate value and help bring value in others, as well as encourage growth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HcGd-JKyrhKamKKpPwg3Yg.png" /></figure><p><em>Agile Coaching Growth Wheel</em></p><p>It’s great to be able to locate one’s own abilities in these dimensions, but what about consciously building them up? This is where the<strong> </strong>Agile<strong> Growth Wheel</strong> comes in, providing a tool to help coaches, Scrum Masters, agile leaders and anyone who aims to grow as an agile coach increase their own capabilities. The Growth Wheel allows you to identify the competencies and stances in order to grow along the agile journey. The Growth Wheel includes nine core skill competencies:</p><ul><li><strong>Self Mastery:</strong> Central to being a great agile coach is the resilience to keep on investing in yourself through learning, inspecting, and reflecting constantly. Take lessons from every little experience, good or bad. Emotional intelligence and social awareness are also part of knowing how and when to show up in any given context.</li><li><strong>Agile/Lean Practitioner:</strong> Has an agile mindset and understands the principles behind it. This is supported by the experience in working with its frameworks and practices.</li><li><strong>Serving: </strong>The primary focus of the Servant Leadership Stance. It’s about prioritizing the needs of the teams and business over our own agenda while promoting growth and well-being.</li><li><strong>Coaching:</strong> It’s about being dedicated to individuals or teams and partnering with them on an educational and creative process which will help them unlock their own potential and reach their goals.</li><li><strong>Facilitating:</strong> It’s the key to build effectiveness of a group of people by owning and promoting the process of collaboration. The facilitator should create a neutral environment of openness and safety and help build bridges of empathy between parties, leading to a most valuable formal outcome.</li><li><strong>Guide Learning:</strong> Guide Learning is about empowering and growing teams and individuals to be resourceful and efficient. It helps agile coaches to set guidelines, promote learning and identify the most effective learning method to trigger learning and growth.</li><li><strong>Advising:</strong> It’s the byproduct of experience and the ability to bring insights and observations to help guide clients and organizations into having a shared understanding of the agile mindset values that can help them to be successful on a long-term basis and to do it independently. An advisor is also able to help manage dysfunction and conflict within teams and reinforce positive behaviors.</li><li><strong>Leading:</strong> A leader of change and a growth catalyzer. Has the ability to focus on embedding change, developing paths that trigger change and inspire it in others.</li><li><strong>Transforming: </strong>Transformation is guiding teams and organizations to be more effective and self-organized. It’s about guiding towards a sustainable change, where they learn how to change and improve themselves through facilitation and coaching.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HcGd-JKyrhKamKKpPwg3Yg.png" /></figure><p><em>Zen Ex Machina Canvas</em></p><p>The <strong>Zen Ex Machina Canvas</strong> however, encapsulates the above definitions into eight agile coaching elements. Its proponents believe that there’s a close relation between agile coaching and agile consulting. Why? Effectively, an agile coach might tend to multiple teams and business areas across the organization to help understand what agile practices are and what benefits can be expected, embed best practices, nurture the agile mindset, and implement a culture of continuous improvement. The eight elements identified by ZXM are:</p><ul><li><strong>Consultant:</strong> The Consultant focuses on analyzing how teams and organizations are adopting agile principles, providing diagnostics, such as Agile Maturity Matrix, to understand what the maturity is for teams/organizations and how far they are from what would be the ideal. They help to solve problems and advice based on their skills and expertise.</li><li><strong>Coach:</strong> A coach is focused on the development of groups and individuals to help reach shared goals. Creates a change and improvement mindset supported by resources such as tooling and/or documentation. The Coach helps change mindsets and behaviors.</li><li><strong>Counselor:</strong> The Counsellor is an element that helps manage team dysfunctions and conflict by helping identify and treat negative behaviors and reinforcing positive ones. It’s focused on active listening and helping to create empathetic and nonviolent communication.</li><li><strong>Change Agent:</strong> To be a Change Agent is to trigger change within organizations, teams and individuals. It’s about continuous improvement and self-actualization. A Change Agent must be a visible champion of change.</li><li><strong>Facilitator:</strong> As a Facilitator owns the process of collaboration, always acting as a servant-leader to help generate formal and independent outcomes. The Facilitator will take part in meetings and events to help form bridges of empathy between the attending parties.</li><li><strong>Lean Leader:</strong> As a Lean Leader, the agile coach will focus on developing people by helping and inspiring them reach their full potential, on the basis of continuous improvement (KAIZEN) and life-long learning. The Lean Leader also helps set guide rails that will help teams and/or organizations to stay on the path of the agile adoptions journey.</li><li><strong>Trainer</strong>: The Trainer element provides the agile coach with the focus to develop the skill set of teams and/or individuals by developing formal learning outcomes, creating training materials and providing training sessions, such as masterclasses and/or workshops.</li><li><strong>Mentor</strong>: The Mentor element of an agile coach is based on the experience gathered by continuous practice. As a Mentor, the agile Coach also acts as a “trusted advisor” and helps with the strategic view by asking deep questions.</li></ul><p>The agile coaching field is constantly evolving: as new research and techniques emerge, it is important to stay up-to-date and incorporate these advances into your practice. Frameworks such as the ACCF and its extensions are living documents that are designed to be updated and improved over time as new insights and best practices emerge. Remember, agile coaches are champions for change and we embrace it constantly.</p><p>Evolving frameworks can help agile coaches stay current and relevant. By staying up-to-date with the latest best practices, techniques and approaches. Agile coaches can continue to develop their skills and become more effective in their role and ensure that they are providing value and delivering high-quality services to their clients. It’s all about continuous improvement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HcGd-JKyrhKamKKpPwg3Yg.png" /></figure><p><strong>Observation is key</strong></p><p>By far, the most important aspect of identifying how to act, is understanding why. Therefore, the first steps to take are listening closely and asking questions. Good observation skills are key when assessing the maturity of teams and organizations along the agile journey. That’s why I would argue that the first stance for either an agile coach or a scrum master is to be an observer<strong>.</strong></p><p>It’s important to pinpoint where we are and why in order to determine where we want to and are able to go, as well as how far we are from reaching it. That will set the tone and help strategize on what should come next. Context is important. An agile coach might work with a team or organization that is only just starting to adopt agile practices, but can also help those who have already adopted agility and feel they can improve. Of course that influences the depth and level at which I’m required to operate.</p><p>So, how to do that? In my opinion, the best way to do it is by attending sessions and events within the teams and/or organizations and assessing the engagement, team dynamics and psychological safety. Really observe how questions are posed and answered, the overall explicit mood, and the underlying emotions. Talk to those who find agile methods useful and to those who oppose them, and try to understand why. Take as many notes as possible and gather your thoughts while formulating non-judgemental suggestions and viewpoints on what you have observed. This will help understand which next stances to adopt, either as a facilitator, by moderating events and assisting in workshops that can trigger positive change, or as a coach, the most common approach for an agile coach, by helping others identify their obstacles to growth and overcome them.</p><p><em>Thoughts? We want to hear what you think. Drop us a message at hello@turbinekreuzberg.com.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1619ed5c4ac2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/t14g/agile-coaching-a-toolkit-1619ed5c4ac2">Agile Coaching: A Toolkit</a> was originally published in <a href="https://medium.com/t14g">t14g</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>