<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Bilge Tekkursun on Medium]]></title>
        <description><![CDATA[Stories by Bilge Tekkursun on Medium]]></description>
        <link>https://medium.com/@bilgetekkursun?source=rss-79a08f017ceb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*nfMhlL_xsW8bU-8zZErjlw.jpeg</url>
            <title>Stories by Bilge Tekkursun on Medium</title>
            <link>https://medium.com/@bilgetekkursun?source=rss-79a08f017ceb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 19:14:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bilgetekkursun/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Joining Fastned: My Journey into EV Charging Innovation]]></title>
            <link>https://medium.com/fastned/joining-fastned-my-journey-into-ev-charging-innovation-1bda507dc59f?source=rss-79a08f017ceb------2</link>
            <guid isPermaLink="false">https://medium.com/p/1bda507dc59f</guid>
            <category><![CDATA[fastned]]></category>
            <category><![CDATA[electric-vehicles]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[onboarding]]></category>
            <dc:creator><![CDATA[Bilge Tekkursun]]></dc:creator>
            <pubDate>Mon, 17 Feb 2025 10:19:32 GMT</pubDate>
            <atom:updated>2025-02-19T11:27:26.165Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u8EWJlX1ySV6TKpZMNNEyg.png" /><figcaption>Fast, efficient and sustainable charging solutions for every journey</figcaption></figure><p>In this post, I want to share my experience joining Fastned as a backend developer in October 2024, the interview process and how the onboarding prepared me for a successful start.</p><p>Choosing the right company is usually a combination of factors: the company’s vision, the technologies used, and the nature of the work itself. For me, the most critical aspect is the culture, the motivation and collaboration among team members. I truly believe that a great team can tackle even legacy projects and outdated technologies by working together, listening and focusing on improvement. This mindset brought me to Fastned, and so far, I have found it to be an ideal environment for growth and collaboration.</p><p>I’ll be sharing insights into three main areas: the interview process, my onboarding experience and the company culture.</p><h4>The Interview Process</h4><p>I first learned about Fastned through a friend and what stood out immediately was their mission and how they presented themselves. From their website to the interviews, the emphasis on transparency and purpose was evident.</p><p>The first interview was a casual online meeting with Talent Acquisition Team to discuss expectations and introduce ourselves. If there was mutual interest, the next step was a technical assessment. At Fastned, Kotlin is the main backend language but since I primarily coded in Java before, I was allowed to complete the task in Java. I had 7 days to complete the assignment, which was sufficient for me. The task itself was not overly complex, but it required careful thought to come up with an optimal solution rather than just a working one.</p><p>After my technical challenge was approved, I was invited to an in-person interview which was a big step for me, as I had worked remotely and attended online interviews exclusively since 2020. Visiting the office, meeting potential teammates and getting a feel for the culture was a valuable experience.</p><p>The in-person interview involved reviewing the technical assessment, additional technical questions and small system design discussions. The focus was on my thought process and problem-solving skills.</p><p>One highlight for me was meeting the Engineering Manager and Product Manager together in the next stage. This gave me an opportunity to understand the product side of things and explain my working approach. Finally, I had a conversation with the Director of Product and Engineering, where I could ask questions about<strong><em> </em></strong>and learn more about the company, including its strategies, future growth plans, and technical direction.</p><p>One of the aspects I found helpful was the feedback loop at each stage. The Talent Acquisition team member was consistently available to give and receive feedback, making adjustments to ensure the process aligned with my needs.</p><p>A special touch? Before I even started, I was invited to one of the company’s lunch days. I remember walking in, feeling a bit nervous but within minutes, a few colleagues came over to introduce themselves, get to know me and share who they are.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cBKCbOapWbSt4_nBI6NixA.jpeg" /><figcaption>Charging up a Tesla for the first time… learning on the go!</figcaption></figure><h4>Onboarding Experience</h4><p>Fastned’s onboarding experience is both thorough and well-paced. The first week was packed with sessions covering everything from Product &amp; Engineering, visiting stations, the Fastned business model, network development, booking meeting rooms and company cars, to finance, legal, construction management and the story of Fastned, among others, providing a comprehensive understanding of how different teams collaborate to drive the company’s mission forward. These sessions then slowed down to about two per week, giving me plenty of time to focus on team tasks.</p><p>Within the first two days, I had completed my laptop setup. The internal documentation was very helpful in enabling me, as a new joiner, to quickly get everything up and running. I was promptly added to all the necessary groups and I received all the permissions I needed, such as VPN setup, GitLab access, AWS access, and more. Having well-structured, up-to-date documentation made the difference between struggling with setup and getting started smoothly.</p><p>As part of the Protocols team, my onboarding included a trip to a charging station with my Product Manager, Engineering Manager and a colleague who had also recently joined. It was my first time charging an EV and experiencing the process firsthand made the work we do feel very tangible.</p><p>One of the things I really appreciated was that my Product Manager organized a meeting where he gave a presentation about our domain. He explained what we do, how our work fits into the Fastned organization and which tasks we spend most of our time on. He also answered all my questions, which made it much easier for me to adapt.</p><p>Team rituals also helped ease my transition. Before every new meeting I joined, someone always gave me a quick introduction and provided a brief explanation of how the meeting would proceed. Small actions like this made a big difference.</p><p>Another key ritual was how we structured our planning meetings. We started by reviewing any remaining tasks from the current sprint, then moved on to our broader roadmap. Looking at the epic board together ensured that everyone stayed informed and had the opportunity to ask questions. This also made prioritization a collaborative effort, giving the whole team a clear understanding of our direction.</p><p>Each new hire is assigned a buddy within the team, a go-to person, for any questions. My engineering manager also set up weekly 1:1s (one-on-one’s) to track my progress and address any blockers. In these 1:1s, we discussed not only technical challenges but also my long term growth. One of my favorite conversations was about how to identify personal strengths and use them to contribute more effectively to the team. Additionally, having 1:1 meetings with each team member gave me a valuable opportunity to connect with everyone on a more personal level. This level of support made me feel valued and motivated.</p><h4>Culture and Values</h4><p>The culture at Fastned is one of positivity and connection. People go out of their way to introduce themselves, whether over coffee or during lunch. Events like board game nights and company-wide activities make collaboration enjoyable and natural.</p><p>Communication is highly valued, which also helped me during my onboarding. Teams regularly assess their strengths and weaknesses and to raise awareness about feedback, we held a session where, instead of directly discussing feedback, we first worked on getting to know our teammates better. Our way of working is shaped by our past experiences and backgrounds and this exercise helped us recognize those influences. Later, we will build on this foundation to work on giving and receiving effective feedback.</p><p>Continuous learning is encouraged. Fastned provides an education budget that we can use for courses and certifications to improve our skills. For example, I plan to use my education budget to attend the Devoxx Belgium 2025 conference with my colleagues, which will be an excellent opportunity for growth.</p><p>One example of the culture is how team rotation opportunities are managed. Recently, a new domain opened up and employees could express interest in joining it. Instead of formal emails or a strict approach, we held an event in a café. Everyone created profile cards with their photos and three strengths. Each team explained their work, challenges and future goals.</p><p>As a new joiner, I had the chance to learn about the teams and their goals. However, even if I weren’t new, this process would still be a great opportunity to ask questions about other teams, evaluate myself in different contexts, understand their needs, and reassess where I can grow and contribute more effectively.</p><p>Through interactive sessions, we discussed questions like:</p><ul><li><em>“If you could join any team without worrying about responsibilities, which one would it be?”</em></li><li><em>“Which team do you think you could learn the most from?”</em></li><li><em>“What strength could you offer to another team?”</em></li><li><em>“Based on everything you’ve learned, where do you see yourself next?”</em></li></ul><p>In response to each question, everyone chose a team and discussed their perspectives. After each session, the newly formed teams shared their updates, highlighting the areas where they had strengthened and the types of needs they identified during the discussions.</p><p>Joining Fastned has been an enriching journey, with a seamless onboarding process, transparent interviews and a culture centered on collaboration and growth. Beyond the technical side of things, the friendships and support I’ve found here have made all the difference. I’m grateful to be part of a team that fosters continuous learning and shared purpose.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1bda507dc59f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fastned/joining-fastned-my-journey-into-ev-charging-innovation-1bda507dc59f">Joining Fastned: My Journey into EV Charging Innovation</a> was originally published in <a href="https://medium.com/fastned">fastned</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Optimizing Promotion Search with Elasticsearch: Our Experience]]></title>
            <link>https://medium.com/trendyol-tech/optimizing-promotion-search-with-elasticsearch-our-experience-c7db0be17c16?source=rss-79a08f017ceb------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7db0be17c16</guid>
            <dc:creator><![CDATA[Bilge Tekkursun]]></dc:creator>
            <pubDate>Tue, 04 Apr 2023 13:01:53 GMT</pubDate>
            <atom:updated>2023-04-04T15:00:04.469Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nERdZcYvUuAqb2x-yyvLcw.png" /><figcaption>Magnifying glass hovering over a price tag (DALL-E)</figcaption></figure><p>In this blog post, we will discuss how we utilize Elasticsearch, the decisions we’ve made to cater to our needs, and the reasons behind these choices. Before diving into our use of Elasticsearch, let me first provide an overview of a promotion.</p><blockquote>What is a promotion?</blockquote><p>A promotion offers customers discounts or incentives to encourage them to purchase products. These promotions can take various forms, such as “Buy 3, Pay 2”, “20% discount on orders over 100 TL”, or “30% off the second product”, among others.</p><p>Promotions can include various conditions such as brand, category, minimum basket amount, seller and so on. If a content satisfies the conditions of a defined promotion, it can be said that the discount is applicable to that content.</p><p>Elasticsearch is an essential search solution that we use to find applicable promotions in the shopping cart.</p><p>Following topics will be covered:</p><ol><li>Why use -1 and “emptyList” as default values?</li><li>Why we don’t use sharding?</li><li>The purpose of having two different indices</li><li>Deletion of expired promotions from indices</li><li>Why we don’t use cross-datacenter replication between Elastic clusters?</li><li>Mssql -Elastic Comparator</li></ol><h4>Why use -1 and “emptyList” as default values?</h4><p>When storing promotion fields and conditions, not all fields may be filled. For example, a promotion assigned to a campaign will have a non-empty campaignId field, but there could be many empty fields such as sellerId, contentId, brandId etc. When we perform a search in Elasticsearch for promotions applicable to a shopping cart, we assign default values of -1 for numeric fields and “emptyList” for string fields if they are empty.</p><p>Below, there is a part of the document that shows how we store promotion conditions in Elasticsearch.</p><pre>          &quot;siBrandIds&quot; : [<br>            -1<br>          ],<br>          &quot;siCategoryIds&quot; : [<br>            -1<br>          ],<br>          &quot;siCampaignIds&quot; : [<br>            619933<br>          ],<br>          &quot;siSectionIds&quot; : [<br>            -1<br>          ],<br>          &quot;siSellerIds&quot; : [<br>            -1<br>          ],<br>          &quot;siListingIds&quot; : [<br>            &quot;emptyList&quot;<br>          ],<br>          &quot;siStoreIds&quot; : [<br>            -1<br>          ],<br>          &quot;siContentIds&quot; : [<br>            -1<br>          ],<br>          &quot;siApplicationIds&quot; : [<br>            -1<br>          ],<br>          &quot;siUserIds&quot; : [<br>            -1<br>          ],<br>          &quot;siUserSegments&quot; : [<br>            &quot;emptyList&quot;<br>          ],<br>          &quot;siEmailExtensions&quot; : [<br>            &quot;emptyList&quot;<br>          ]</pre><p>Additionally, here’s an example of how we send queries to Elasticsearch:</p><pre> &quot;query&quot;: {<br>            &quot;bool&quot;: {<br>                &quot;filter&quot;: [<br>                    {<br>                        &quot;terms&quot;: {<br>                            &quot;siSellerIds&quot;: [<br>                                -1,<br>                                123123<br>                            ],<br>                            &quot;boost&quot;: 1.0<br>                        }<br>                    }<br>                    {<br>                        &quot;terms&quot;: {<br>                            &quot;siContentIds&quot;: [<br>                                -1,<br>                                123123<br>                            ],<br>                            &quot;boost&quot;: 1.0<br>                        }<br>                    },<br>                    {<br>                        &quot;terms&quot;: {<br>                            &quot;siFilterableLabelIds&quot;: [<br>                                &quot;emptyList&quot;<br>                            ],<br>                            &quot;boost&quot;: 1.0<br>                        }<br>                    },<br>                ],<br>                &quot;adjust_pure_negative&quot;: true,<br>                &quot;boost&quot;: 1.0<br>            }<br>        }</pre><p>How does this approach help us to optimize performance?</p><ul><li>Reducing Elasticsearch’s processing time: When a value is not specified for a numeric field, Elasticsearch cannot determine what it should match with and has to check more resources as a result. By assigning a predefined value like -1 to empty fields, Elasticsearch can make decisions regarding the field’s value more easily, leading to faster queries. This reduces ambiguity and helps execute queries more quickly.</li><li>Improving query comprehensibility: Using predefined values makes query results more predictable, which makes the query more understandable and manageable. Predefined values help determine if a field is empty and how it should be handled in the query results. For example, using -1 for a numeric field indicates that the field is missing, making it clear whether the query should ignore the field or process it in a specific way.</li></ul><p>Using predefined values can enhance the performance and predictability of Elasticsearch queries. To ensure success, it is crucial that these values do not overlap with natural values in your dataset. In our case as you see code below, we set initial values to our fields and no conditions or promotion fields set to-1 and we do not experience any issues with our chosen default string value, “emptyList”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/930/1*aJHHcMBHSaLDmqEW87u5zQ.png" /><figcaption>Setting initial values to fields that will be used in Elasticsearch query</figcaption></figure><h4>Why don’t we use sharding?</h4><p>We prefer not to use sharding in our Elasticsearch infrastructure. One of the main reasons for why we don’t need it is that we have two indices and strive to keep our data as optimized as possible.</p><p>There can be various reasons for not using sharding in Elasticsearch but for us reasons can be listed as below:</p><ul><li>Maintaining query performance: Sharding involves splitting data across multiple shards. In situations with heavy querying needs, such as our promotion apply process during events, query performance may decline due to coordination between shards.</li><li>Low data volume: When dealing with a low volume of data on Elasticsearch, implementing sharding can be an unnecessary and costly endeavor. Instead, managing small data volumes with high performance and availability can be achieved through the use of a few replicas. In addition, we can state that after conducting load tests with different numbers of shards and examining Elasticsearch’s CPU usage and response time, the most suitable approach is to use a single shard for us.</li><li>Optimizing replica count: By optimizing the number of replicas, we can use Elasticsearch with high availability and performance. In this context, not using sharding prevents unnecessary complexity and costs.</li><li>Reducing system complexity: Sharding configuration and management can introduce additional complexity and workload for system administrators and developers. If data volume and usage requirements don’t necessitate sharding, as is the case for us, not using it will result in a simpler and more manageable structure.</li></ul><h4>Why do we have two different indices in Elasticsearch? What are their purposes?</h4><p>We have two indices: all-promotions and active-promotions. The all-promotions index stores promotions whose end date has not exceeded one year, while the active-promotions index contains ongoing promotions and those that have not yet started.</p><p>The use of these two indices diverges in the following situations: the all-promotions index stores past promotions to handle refund processes or reporting requests for backdated discount apply processes. The active-promotions index is used to quickly respond to active and upcoming promotion apply requests.</p><p>The objectives of having two indices include:</p><p>Performance and efficiency: Each index has specific use cases and responsibilities. Therefore, they can respond to requests more efficiently and with better performance.</p><p>Improved scalability: Managing active-promotions and all-promotions indices separately allows each index to be scaled according to its specific requirements. For example, we can use more replicas for the active-promotions index to ensure high availability and performance while reducing costs by using a lower replica count for the all-promotions index.</p><p>Data management: By using two indices, we can manage the lifecycle of the data more effectively based on the promotion statuses. When promotions in the active index expire, we move them to the all-promotions index while also removing promotions with expired end date from the all-promotions index to maintain performance, as we will discuss in the next section.</p><p>Faster data access: Separating active-promotions and all-promotions indices allows us to provide optimized querying and data access processes for each index. This enables users to apply and refund promotions more quickly and efficiently. By decreasing the amount of data stored in the active index, we were able to achieve a notable decrease in response time, reducing it from 20ms to 10ms.</p><h4>Deletion of expired promotions from indices</h4><p>At a certain point, we delete promotions that will no longer be used from both indices. A script running every minute removes promotions whose end date has passed by one day from the active-promotions index and promotions whose end date has passed by one year and two days from the all-promotions index. The advantages this provides include:</p><p>Controlled data volume: Continuously deleting old promotions helps us keep the data volume in the indices under control, which in turn aids in maintaining performance.</p><p>Improved query performance: Limiting the size of the living promotion data set enhances query performance. Querying less data results in faster responses and a better user experience.</p><p>Data lifecycle management: This process is a crucial part of data lifecycle management. By regularly removing expired promotion data, we ensure that our users work only with valid and current promotions.</p><p>Optimized resource utilization: By regularly deleting old promotion data, we optimize resource usage, allowing Elasticsearch servers to utilize CPU, memory, and disk resources more effectively.</p><p>Below, you can find code snippet we use that takes alias names for environments and runs query to delete expired promotions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j7zzpFb8n2Dot9KysRKriw.png" /><figcaption>Deleting inactive promotions from active index and deleting expired promotions for more than1 year from all-promotions index</figcaption></figure><h4>Why we don’t use cross-datacenter replication?</h4><p>Cross-datacenter replication is a technique used to replicate data between data centers to ensure data availability in case of a disaster or failure in one data center. However, in our case, we have opted not to use this approach due to our specific architecture.</p><p>We use an elastic search consumer and a couchbase elastic connector (CBES) deployed in two separate data centers, “Moon” and “Mars”. If the decision were made to use data replication between the elastic clusters, we would only need a single elastic consumer and a single CBES. While this may seem like an efficient solution, it would come with a significant drawback — the loss of one data center would result in a complete loss of availability.</p><p>By not using replication for our elastic clusters, we are able to provide fault tolerance in the possibility of data center failures. This is achieved through the deployment of separate elastic consumers and Couchbase elastic connectors in each data center, ensuring that if one data center goes down, the other can continue to function independently.</p><h4>Mssql -Elastic Comparator</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*is81T3ELsZYzvvXpsPn7kQ.png" /><figcaption>The process of synchronizing promotions from MSSQL to Elastic</figcaption></figure><p>We utilize MSSQL as our primary database and upon adding a promotion record to it, we dispatch a promotion created event to Kafka. The Promotion Elastic Consumer then receives the event and creates the corresponding promotion record in Couchbase. We use the Couchbase Elastic Connector (CBES) to stream the promotion data into Elastic. However, we may encounter issues in Couchbase Connector or Promotion Elastic Consumer that prevent the synchronization of the data from mssql to Elastic. In such cases, newly created or updated promotions may not be applied to the shopping cart because we get promotions from Elastic, causing a significant problem.</p><p>To proactively detect these potential issues quickly, we developed a comparator in Golang. This comparator checks whether the last 30 promotions created or updated within the last 2 minutes have been saved in Elastic and whether the values in the saved fields match the original values.</p><p>By implementing this solution, we can ensure that all promotions created or updated in MSSQL are correctly synchronized with Elastic. If any issues arise, we can quickly detect and take necessary steps to resolve them.</p><p>In conclusion, the approaches we have adopted for utilizing Elasticsearch have enabled us to optimize query performance, improve data management, and enhance the user experience. By implementing predefined values, managing multiple indices, and regularly deleting expired data, we have achieved an efficient search.</p><blockquote>Ready to take your career to the next level?<br>Join our dynamic team and make a difference at Trendyol.<br>Want to be a part of our growing company? <strong>We’re hiring!</strong><br><a href="https://jobs.lever.co/trendyol?lever-via=AGwPI6mKw9">Check out our open positions</a>.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7db0be17c16" width="1" height="1" alt=""><hr><p><a href="https://medium.com/trendyol-tech/optimizing-promotion-search-with-elasticsearch-our-experience-c7db0be17c16">Optimizing Promotion Search with Elasticsearch: Our Experience</a> was originally published in <a href="https://medium.com/trendyol-tech">Trendyol Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ways To Boost Software Development Teams — Part 2]]></title>
            <link>https://medium.com/trendyol-tech/ways-to-boost-software-development-teams-part-2-c05150654887?source=rss-79a08f017ceb------2</link>
            <guid isPermaLink="false">https://medium.com/p/c05150654887</guid>
            <dc:creator><![CDATA[Bilge Tekkursun]]></dc:creator>
            <pubDate>Thu, 15 Dec 2022 07:50:21 GMT</pubDate>
            <atom:updated>2023-01-11T11:16:17.130Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ways To Boost Software Development Teams — Part 2</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*kTmny7Rt39KjWEw0" /></figure><p>In our first article, we talked about how we, as the Promotion team, made working together more effective and how we built great and healthy team culture.</p><p>In this article, which is the continuation of our first post, <a href="https://medium.com/trendyol-tech/ways-to-boost-software-development-teams-part-1-1874ca7764f5">Ways To Boost Software Development Teams — Part 1</a>, we would like to talk about what other activities and principles we have adopted and how we are improving ourselves as a team, hello again :)</p><p>Below, you can find the topics that we will explain in detail.</p><ul><li>Business Q/A Sessions</li><li>Book Reading</li><li>OKRs — running on the same goals</li><li>Supporting for external courses</li><li>Retro meetings</li><li>Rotation across teams</li><li>Mob Programming</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fdW2p6-BWtDvu-cf" /></figure><h3><strong>Business Q/A Sessions</strong></h3><p>As a team, we organize one-hour business q/a meetings once a week. The purpose of this meeting is to refresh our knowledge of this domain which includes a large amount of business logic.</p><p><strong>How did this meeting benefit us?</strong></p><p>First of all, the initial purpose of this meeting was to make the adaptation of our new teammates easier so they don’t get lost in our complex domain. We did this by preparing some questions on an excel document before the meeting and talking about the answers to these questions in a conversational style, and we aimed to make the information permanent and to be easier to remember.</p><p>After a while, we realized that this meeting was beneficial not only to our new teammates but also to our experienced teammates by reminding us of some detailed information. Also, these questions and discussions helped us find some improvement points in our domain.</p><p><strong>How does the meeting start and go?</strong></p><p>We usually start with a simple question and then jump to different points in the question to try to complete the big picture. By doing this and completing each other’s shortcomings, we aim to keep the knowledge level of everyone on the team equal and complete.</p><p>At the same time, we discuss the exciting cases faced by our colleagues who give support that week, and we pass on a good experience to our next observer friends.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eyJc9t6GdwPH7lzG" /></figure><h3><strong>Book Reading</strong></h3><p>We believe that technical and non-technical books in the industry expand our knowledge and enable us to work more efficiently in our working life.</p><p>Also, it’s not deniable that now it’s quite easy to reach the desired information from the internet. Still, we need books in order to gain in-depth knowledge of technology and to have information on the topics that interest us.</p><p>We also think that being able to learn from the knowledge and experience of experts who have worked in the industry for years is invaluable.</p><p>As a team, we take the chapters of our technical or soft skill-oriented books, which we have determined as one per month.</p><p>Once a week, the person responsible for the chapter tells the team about the subject.</p><p>While talking about our chapters, we try to ask questions such as “Can we use this method?”, “Should we also do this?”, “Do we think the defended idea is correct, and what are the sides we disagree with?” to contribute to our own development not only theoretically, but also practically.</p><p>Below you can find a few examples of books on our list.</p><ul><li>The Pragmatic Programmer</li><li>System Design Interview</li><li>Domain-Driven Design: Tackling Complexity in the Heart of Software</li></ul><p>With this practice, we improve as a team by sharing knowledge, getting new ideas, and realizing what we need to change and what points we lack. We become more conscious of what we do, why, and how, and consistently improve our technique.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*FBG-HUcUdjlqUpsz" /></figure><h3><strong>OKRs (Objectives and Key Results)</strong></h3><p>Every quarter of the year, we set objectives according to the OKR methodology. OKR helps us to embrace shared goals.</p><p>Some objectives we define this quarter:</p><ul><li>All tests should run in 2 minutes</li><li>Increase deployment frequency to 2,5 per day</li><li>Decrease x API deploy time to 5 minutes</li></ul><p>While defining the goals, one of the questions we ask first is that “Which side of the team will be stronger if we accomplish this goal?“ so that our objectives are clear and we are sure that the objectives support us to improve our technology, culture, or business value.</p><p>Chasing common goals in the team will strengthen the sense of being a team, so it would better remind us that these goals should belong to the team, not individuals. We meet weekly to prioritize our objectives and include them in the sprint. We also arrange a meeting to review our progress on the objectives at the end of every month.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9hdN5Tml5hoIxYAl" /></figure><h3><strong>Supporting taking courses</strong></h3><p>In Trendyol Tech, developers are supported to take courses and attend conferences related to their interests. Taking external courses helps the team to increase technical knowledge. In addition, those taking the courses are encouraged to present what they learn in the classes to their teammates. These presentations make spreading knowledge within the team easier and quickly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tGbit_NhH616xGPP" /></figure><h3><strong>Retro Meetings</strong></h3><p>A retrospective is a crucial part of Agile because it’s where we gather feedback from the team and understand their feelings about the process, thereby improving future sprints. A good retrospective must be engaging and actionable. Our retrospective meetings consist of 3 important things:</p><ul><li><strong>Ice-Breaking<br></strong>When we kick off the retrospective, our first step is to try to break the ice. Because we want to hear one by one all comments and feedback. So what are we doing about it? We start with a small warm chat or ask some funny virtual icebreaker questions. In this way, the team starts to feel comfy and confident.</li><li><strong>Engaging</strong></li></ul><p>In order to make retrospective meetings more engaged and action items embraced by the whole team, we have a recurring system for leading the meeting. Each retrospective is led by a different team member.</p><ul><li><strong>Actionable</strong></li></ul><p>The primary goal at the end of the retrospective is to produce an actionable list of items that the team can do to increase productivity. We gamify the retrospective meetings by using different online retrospective templates. We set a timer counting down from 2 minutes to give time to team members to write feedback. Columns of the templates help the team to be more focused and ease the process of gathering feedback to improve the process. And then, we read every feedback and discuss whether it’s an action list. An action list either can be assigned to a team member or the whole team. Assignees ensure the execution of the action list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-oukBF-PvOE0iEg4" /></figure><h3><strong>Rotation Across Teams</strong></h3><p>Rotation is a process that allows developers to change their teams. Someone being a part of a team for a while can rotate to another team if they want. The new team the one will rotate to is usually a team that does different things from the one they were previously in. Furthermore, It is optional to stay in the same position; For example, you can change from the backend developer to the frontend developer, etc.</p><p><strong>Why should we rotate? What are the benefits?</strong></p><p>In Trendyol, teams have various tech stacks and challenges. When people develop all the muscles in their bodies equally, their appearance improves. The rotation allows us to strengthen different muscles in different teams. Even more, changing the team gives us an experience like changing the company we are part of, so the one who rotates has a chance to learn different tech stacks and domains. On the other hand, they can meet new people and spread knowledge across the teams by sharing their experience from their previous team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hp6iLtMXzA1jfjxQ" /></figure><h3><strong>Mob Programming</strong></h3><p>Mob programming is a significant activity for development teams. It is the next step of pair programming. Using this technique to solve problems helps us to share business and technological knowledge with teammates. Mob programming improves team collaboration and, using it for core and complex changes, expands knowledge of critical logic. This knowledge helps us to solve critical bugs.</p><p>We use mob programming when we need to change a critical part of the domain or when we need to implement a complex business process. Also, we use this practice when there is a need to fix a production bug immediately.</p><p>Deciding solution is more important than writing code so that any teammate can write code in mob programming sessions. All product participants (Dev, QA, PO) can join mob sessions. Especially when fixing production bugs, QA and PO involvement is critical.</p><p>Thank you dear promotion team members <a href="https://medium.com/u/d22e5cfef89e">MUSTAFA AKILLI</a>, <a href="https://medium.com/u/5b8c9f5e089c">Oğuzhan Sarıçin</a>, <a href="https://medium.com/u/dbb8df901d4a">Kubra Cakir</a> , <a href="https://medium.com/u/790354e895b5">Selay Arkun</a>, <a href="https://medium.com/u/4968a2788dd5">Sefa Fatihhan Okumuş</a>, <a href="https://medium.com/u/986087db7d99">Emel Serengil</a>, <a href="https://medium.com/u/5a3b8e730252">Ferhaterdas</a>, <a href="https://medium.com/u/60433054d927">Mehmet Aran</a>, <a href="https://medium.com/u/7faad67539e9">Ertuğrul Gamgam</a> for their contribution.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c05150654887" width="1" height="1" alt=""><hr><p><a href="https://medium.com/trendyol-tech/ways-to-boost-software-development-teams-part-2-c05150654887">Ways To Boost Software Development Teams — Part 2</a> was originally published in <a href="https://medium.com/trendyol-tech">Trendyol Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Java SE 11 Developer Exam Number: 1Z0–819 Süreci]]></title>
            <link>https://medium.com/@bilgetekkursun/java-se-11-developer-exam-number-1z0-819-s%C3%BCreci-d1073e46d2c2?source=rss-79a08f017ceb------2</link>
            <guid isPermaLink="false">https://medium.com/p/d1073e46d2c2</guid>
            <category><![CDATA[oracle-certification]]></category>
            <category><![CDATA[certification]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[java11]]></category>
            <category><![CDATA[oracle]]></category>
            <dc:creator><![CDATA[Bilge Tekkursun]]></dc:creator>
            <pubDate>Sat, 29 Jan 2022 10:23:01 GMT</pubDate>
            <atom:updated>2022-01-29T10:23:01.416Z</atom:updated>
            <content:encoded><![CDATA[<p>Merhaba, bu yazıda size Java SE 11 Developer Certification sınavını nasıl geçtiğimden bahsetmek istiyorum. Blog postlarını okumak daha önce sınava girmiş olan insanların düşünceleri ve yönlendirmelerini de öğrenmek açısından bence büyük bir avantaj sağlıyor, bu yüzden bu sayıyı arttırmak ve faydalı olmak adına bu postu yazmak istedim :)</p><p>Öncelikle Java SE 11 Z-819 sınavı daha önce var olan sınavlardan farklı olarak Z-815 ve Z-816 sınavlarının birleşimi şeklinde yapılıyor, eskiden iki sınava girerken böylece iki sınav tek sınava indirgenmiş oldu.819 versiyonu ile konular değişmemekle birlikte soru konularının dağılımı konusunda eşitlik sağlandığını söyleyebilirim.</p><p>Konular aşağıdaki gibi:</p><ul><li>Working with Java data types</li><li>Java object-oriented approach</li><li>Working with arrays and collections</li><li>Java Platform Module System</li><li>Java I/O API</li><li>Database applications with JDBC</li><li>Annotations</li><li>Controlling program flow</li><li>Exception handling</li><li>Working with streams and lambda expressions</li><li>Concurrency</li><li>Secure coding</li><li>Localization</li></ul><p>Sınava hazırlanırken esas aldığım adımları da aşağıdaki gibi maddelendirebilirim:</p><p><strong>1.Çalışmaya başlamadan önce milestoneları belirleme ve bir plan olması açısından konuları inceleme</strong></p><p>Bu maddede anlatacaklarım herkes için değişebilir ama benim için herhangi bir çalışmaya başlamadan önce önümdeki yolu görebilmek, adımları belirleyebilmek ve kafamda planını kurabilmek önemli bir başlangıç sağlıyor. Bu yüzden çalışmaya başlamadan önce sınava dahil olacak konuları çıkarıp hangisine daha çok, hangisine daha az hakim olduğumu belirlemek, aynı zamanda sınavdaki dağılımlarını öğrenebilmek için birkaç post veya blog yazısı okumak, neye ne kadar zaman ayıracağımı öğrenmek için güzel yollar. Bu şekilde çalışmaya ne yapacağımızı bilerek, en azından çalışmanın taslağı kurulmuş bir şekilde başlayarak ve daha önce sınava girmiş insanların yaptığı hatalardan ve zaman kayıplarından da kaçınarak bir adım önde olacağımızı düşünüyorum.</p><p><strong>2. Konuları anlayarak ve örneklerine bakarak, bölüm sonu quizlerini çözerek diğer bölüme devam etmek</strong></p><p>Konu ne kadar kolay olursa olsun ve hakim olursak olalım eğer Oracle’ın kendi eğitimini izliyorsanız konuları hiçbir şekilde atlamamanızı öneririm, çünkü sınav bu eğitime paralel şekilde ilerliyor, bölüm sonu quizlerdeki soruların mantığı da gerçek sorulara oldukça benzerdi. Konuları anlayarak ilerlemek derken anlatmak istediğim konudan çok uzaklaşmadan eğitimi izlerken ya da izledikten hemen sonra daha önce karşılaşmadığımız veya çözümünü farklı bulduğumuz bir soru gördüğümüzde kendi anlayacağımız ve hatırlayacağımız şekilde not tutmanın unutmamak açısından yararlı olduğunu düşünüyorum. Sınav konuları oldukça geniş ve her şeyi akılda tutmak biraz zor. Bu yüzden her konu için tuttuğumuz düzenli notlarımız olursa geriye dönük tekrarlarda kolay bir şekilde işin içinden çıkabiliriz.</p><p>Benim çok hakim olmadığım konulardaki yaklaşımım sorulardan çok konuya öncelik vermek oldu, konunun mantığını güzelce oturttuktan sonra birkaç örnek soru çözülerek üstesinden gelinebileceğini düşünüyorum. Ancak örneğin I/O gibi konularda konuya daha hakim fakat soru tiplerine daha az aşina olabiliriz. Bu gibi konularda bolca soru çözerek gelebilecek soru tiplerine daha hazırlıklı olmakta fayda var. Konuları tamamladıktan sonra da bölüm testlerini atlamayıp çözmek de pekiştirmeyi sağlıyor.</p><p><strong>3.Practice testleri gerçek sınavdaymış gibi çözmek</strong></p><p>En önemli konunun kesinlikle bu başlık altında yazdıklarım olduğunu düşünüyorum. Sınavın kapsadığı konular içerisinde ikinci bölüme giren aslında daha advanced kalan konular diyebiliriz, bu konuların konu anlatımına öncelik verip daha hakim olduğumuz konuların da practice sınavlarına öncelik vermek akıllıca olacaktır.</p><p>Ben sınava hazırlanırken Udemy’de bulduğum practice examları, ve OCP Oracle Certified Professional Java SE 11 Developer Complete Study Guide kitabındaki practice sınavlarını çözdüm. Olabildiğince fazla örnek soru görüp bu soruların cevaplarını düzgün bir şekilde anlayabilmek çok önemli. 90 dakikadan oluşan sınavda zamanı verimli kullanabilmek de büyük önem taşıyor. Bu yüzden bu sınavları çözerken sessiz bir ortamda olup gerçek sınavdaymış gibi davranmak güzel bir egzersiz olacaktır.</p><p><strong>Sınav günü<br></strong>Sınav günü geldiği zaman öncelikle çalışma ortamınıza ve masanıza dikkat etmeniz gerekiyor, kimliğinizi gösteren belgeniz dışında her şeyi kaldırmalısınız. Sınav ile ilgili bazı kuralları kabul ettikten sonra çalışma odanızın, masanızın fotoğraflarını isteyen bir adım ile karşılaşacaksınız. Sonrasında da bunu görüntülü bir arama ile devam ettireceksiniz bu aramada da sizden masa ve sınavı yapacağınız ortamı göstermeniz istenebilir.</p><p>Sonuç olarak iyi ve efektif bir çalışma planı ve gerçek sınava paralel sorular çözmenin sertifikayı getireceği kanaatindeyim :) Başarılar!</p><p>Faydalı olabilecek linkler:</p><p><a href="https://blog.avenuecode.com/how-to-pass-the-ocp-java-se-11-certification">How to Pass the OCP Java SE 11 Certification</a></p><p><a href="https://www.udemy.com/course/java-se-11-developer-1z0-819-ocp-course-part-1/">https://www.udemy.com/course/java-se-11-developer-1z0-819-ocp-course-part-1/</a></p><p><a href="https://education.oracle.com/java-programming-learning-subscription/ls_40805">https://education.oracle.com/java-programming-learning-subscription/ls_40805</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d1073e46d2c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>