<?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 Mehmet Fatih Durdu on Medium]]></title>
        <description><![CDATA[Stories by Mehmet Fatih Durdu on Medium]]></description>
        <link>https://medium.com/@mfdurdu?source=rss-891bf1062407------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*o7BLJWPS2FK0WZnA.jpg</url>
            <title>Stories by Mehmet Fatih Durdu on Medium</title>
            <link>https://medium.com/@mfdurdu?source=rss-891bf1062407------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 13:49:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mfdurdu/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[Developing a Lullaby App with AI: A Step-by-Step Journey]]></title>
            <link>https://medium.com/@mfdurdu/developing-a-lullaby-app-with-ai-a-step-by-step-journey-a5ee16cc391b?source=rss-891bf1062407------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5ee16cc391b</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[aidevelopmentplatform]]></category>
            <dc:creator><![CDATA[Mehmet Fatih Durdu]]></dc:creator>
            <pubDate>Sun, 01 Dec 2024 22:12:01 GMT</pubDate>
            <atom:updated>2024-12-01T22:12:01.811Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HIyCMXk459dCAd_o4ywIZA.png" /></figure><p>The current point we’ve reached in AI development led me to ask whether apps developed by a team of 2–3 experienced developers can be enhanced with AI support. Can a single developer guide AI to create an app more quickly? I can guarantee that we’ll still face challenges that are common in the software development process, but I hope that AI will simplify the journey. Of course, without software experience or prior knowledge, tackling the process from scratch might be difficult. In this series of articles, we aim to develop the process of building an app with AI, from design to deployment. We will even attempt to solve any mistakes we encounter with the help of AI.</p><p>The app we’re going to build is a lullaby app for parents, where they can play lullabies and soothing sounds for colic babies. We’ll take it step-by-step.</p><p><strong>GOAL:</strong></p><p>• Have fun while actively learning.</p><p>• Bring the app to life.</p><p>• Enable options for endless playback and repeat selections.</p><p>• Include soothing sounds for colic babies.</p><p><strong>Note:</strong> In this project, we won’t share the code step by step. We will focus on showing the results.</p><p><strong>Tools to be Used:</strong></p><ul><li><strong>Programming Language</strong>: JavaScript</li><li><strong>Development Environment</strong>: React Native</li><li><strong>IDE</strong>: Cursor</li><li><strong>Design Tool</strong>: Figma</li><li><strong>Design Platform</strong>: <a href="http://builder.io/">Builder.io</a></li><li><strong>Code Writing</strong>: ChatGPT</li><li><strong>Design </strong>: <a href="https://www.figma.com/community/file/1234574367157134964/children-podcast">Figma: Children Podcast</a></li></ul><p><strong>DAY 1:</strong></p><p>First, let’s ask our first question. I’ll ask how to create a React Native project in Cursor, ensure the project is compatible with the required language support, and that it can work offline. Below is the response I received about the steps to create the project and the folder structure.</p><p><strong>Initial Steps:</strong></p><ol><li><strong>Command to initialize the project:</strong></li></ol><pre>npx react-native init LullabyApp<br>cd LullabyApp</pre><p><strong>2. The folder structure should look like this:</strong></p><pre>LullabyApp/<br>├── src/<br>│   ├── assets/<br>│   │   ├── images/<br>│   │   ├── sounds/<br>│   │   └── icons/<br>│   ├── components/<br>│   │   ├── common/<br>│   │   └── screens/<br>│   ├── navigation/<br>│   ├── screens/<br>│   ├── services/<br>│   ├── store/<br>│   ├── theme/<br>│   └── utils/<br>├── App.js<br>└── index.js</pre><p>3. <strong>Install necessary packages:</strong></p><ul><li>For navigation:</li></ul><pre>npm install @react-navigation/native<br>npm install @react-navigation/stack<br>npm install react-native-screens react-native-safe-area-context</pre><ul><li>For sound playing:</li></ul><pre>npm install react-native-sound</pre><ul><li>For timers:</li></ul><pre>npm install react-native-background-timer</pre><ul><li>For UI Components</li></ul><pre>npm install react-native-paper</pre><ul><li>For icons</li></ul><pre>npm install react-native-vector-icons</pre><p>4. <strong>Set color themes:</strong></p><p>In the theme/colors.js file, you can define the colors like this:</p><pre>export const colors = {<br>  primary: &#39;#7B1FA2&#39;,<br>  secondary: &#39;#9C27B0&#39;,<br>  background: &#39;#F5F5F5&#39;,<br>  text: &#39;#212121&#39;,<br>  white: &#39;#FFFFFF&#39;,<br>};</pre><p>Next, we anticipate using navigation and create the src/navigation/AppNavigator.js file with the following code:</p><pre>import React from &#39;react&#39;;<br>import { NavigationContainer } from &#39;@react-navigation/native&#39;;<br>import { createStackNavigator } from &#39;@react-navigation/stack&#39;;<br><br>const Stack = createStackNavigator();<br><br>const AppNavigator = () =&gt; {<br>  return (<br>    &lt;NavigationContainer&gt;<br>      &lt;Stack.Navigator&gt;<br>        {/* Your screens will be added here */}<br>      &lt;/Stack.Navigator&gt;<br>    &lt;/NavigationContainer&gt;<br>  );<br>};<br><br>export default AppNavigator;</pre><p>After this, we will ask ChatGPT for additional guidance on steps we need to take. As we plan to make minimal changes to the code, we requested the following:</p><p>“Can you also provide the code for App.js using AppNavigator and create the HomeScreen and PlayerScreen components? Can you make the necessary adjustments?”</p><p>Here’s the code we received for <strong>App.js</strong>:</p><pre>import React from &#39;react&#39;;<br>import { SafeAreaProvider } from &#39;react-native-safe-area-context&#39;;<br>import { Provider as PaperProvider } from &#39;react-native-paper&#39;;<br>import AppNavigator from &#39;./src/navigation/AppNavigator&#39;;<br><br>const App = () =&gt; {<br>  return (<br>    &lt;SafeAreaProvider&gt;<br>      &lt;PaperProvider&gt;<br>        &lt;AppNavigator /&gt;<br>      &lt;/PaperProvider&gt;<br>    &lt;/SafeAreaProvider&gt;<br>  );<br>};<br><br>export default App;</pre><p>In the <strong>AppNavigator.js</strong> file, we have updated the navigation code to include the HomeScreen and PlayerScreen:</p><pre>import React from &#39;react&#39;;<br>import { NavigationContainer } from &#39;@react-navigation/native&#39;;<br>import { createNativeStackNavigator } from &#39;@react-navigation/native-stack&#39;;<br>import HomeScreen from &#39;../screens/HomeScreen&#39;;<br>import PlayerScreen from &#39;../screens/PlayerScreen&#39;;<br>import { colors } from &#39;../theme/colors&#39;;<br><br>const Stack = createNativeStackNavigator();<br><br>const AppNavigator = () =&gt; {<br>  return (<br>    &lt;NavigationContainer&gt;<br>      &lt;Stack.Navigator<br>        screenOptions={{<br>          headerStyle: {<br>            backgroundColor: colors.primary,<br>          },<br>          headerTintColor: colors.white,<br>          headerTitleStyle: {<br>            fontWeight: &#39;bold&#39;,<br>          },<br>        }}<br>      &gt;<br>        &lt;Stack.Screen <br>          name=&quot;Home&quot; <br>          component={HomeScreen} <br>          options={{ title: &#39;Lullabies&#39; }} <br>        /&gt;<br>        &lt;Stack.Screen <br>          name=&quot;Player&quot; <br>          component={PlayerScreen} <br>          options={{ title: &#39;Play Lullaby&#39; }} <br>        /&gt;<br>      &lt;/Stack.Navigator&gt;<br>    &lt;/NavigationContainer&gt;<br>  );<br>};<br><br>export default AppNavigator;</pre><p>For the <strong>HomeScreen</strong>, here’s the code to display the list of lullabies:</p><pre>import React from &#39;react&#39;;<br>import { View, StyleSheet, FlatList } from &#39;react-native&#39;;<br>import { Card, Title, Paragraph } from &#39;react-native-paper&#39;;<br>import { colors } from &#39;../theme/colors&#39;;<br><br>const lullabies = [<br>  {<br>    id: &#39;1&#39;,<br>    title: &#39;Dandini Dandini Dastana&#39;,<br>    duration: &#39;3:45&#39;,<br>    description: &#39;Traditional Turkish Lullaby&#39;,<br>  },<br>  {<br>    id: &#39;2&#39;,<br>    title: &#39;Uyusun da Büyüsün&#39;,<br>    duration: &#39;2:30&#39;,<br>    description: &#39;Classic Lullaby&#39;,<br>  },<br>  // Add more lullabies here<br>];<br><br>const HomeScreen = ({ navigation }) =&gt; {<br>  const renderItem = ({ item }) =&gt; (<br>    &lt;Card <br>      style={styles.card}<br>      onPress={() =&gt; navigation.navigate(&#39;Player&#39;, { lullaby: item })}<br>    &gt;<br>      &lt;Card.Content&gt;<br>        &lt;Title&gt;{item.title}&lt;/Title&gt;<br>        &lt;Paragraph&gt;{item.description}&lt;/Paragraph&gt;<br>        &lt;Paragraph&gt;Duration: {item.duration}&lt;/Paragraph&gt;<br>      &lt;/Card.Content&gt;<br>    &lt;/Card&gt;<br>  );<br><br>  return (<br>    &lt;View style={styles.container}&gt;<br>      &lt;FlatList<br>        data={lullabies}<br>        renderItem={renderItem}<br>        keyExtractor={item =&gt; item.id}<br>        contentContainerStyle={styles.listContainer}<br>      /&gt;<br>    &lt;/View&gt;<br>  );<br>};<br><br>const styles = StyleSheet.create({<br>  container: {<br>    flex: 1,<br>    backgroundColor: colors.background,<br>  },<br>  listContainer: {<br>    padding: 16,<br>  },<br>  card: {<br>    marginBottom: 16,<br>    elevation: 4,<br>  },<br>});<br><br>export default HomeScreen;</pre><p>For <strong>PlayerScreen</strong>, here’s the code to manage sound playback and the timer:</p><pre>import React, { useState, useEffect } from &#39;react&#39;;<br>import { View, StyleSheet } from &#39;react-native&#39;;<br>import { Button, Text, IconButton, ProgressBar } from &#39;react-native-paper&#39;;<br>import { colors } from &#39;../theme/colors&#39;;<br><br>const PlayerScreen = ({ route }) =&gt; {<br>  const { lullaby } = route.params;<br>  const [isPlaying, setIsPlaying] = useState(false);<br>  const [timer, setTimer] = useState(30); // Default to 30 minutes<br>  const [progress, setProgress] = useState(0);<br><br>  useEffect(() =&gt; {<br>    // Load the sound file here<br>    return () =&gt; {<br>      // Cleanup tasks<br>    };<br>  }, []);<br><br>  const togglePlayPause = () =&gt; {<br>    setIsPlaying(!isPlaying);<br>    // Handle play/pause actions here<br>  };<br><br>  const adjustTimer = (minutes) =&gt; {<br>    setTimer(Math.max(0, timer + minutes));<br>  };<br><br>  return (<br>    &lt;View style={styles.container}&gt;<br>      &lt;View style={styles.infoContainer}&gt;<br>        &lt;Text style={styles.title}&gt;{lullaby.title}&lt;/Text&gt;<br>        &lt;Text style={styles.description}&gt;{lullaby.description}&lt;/Text&gt;<br>      &lt;/View&gt;<br><br>      &lt;View style={styles.progressContainer}&gt;<br>        &lt;ProgressBar progress={progress} color={colors.primary} /&gt;<br>        &lt;Text style={styles.timeText}&gt;{lullaby.duration}&lt;/Text&gt;<br>      &lt;/View&gt;<br><br>      &lt;View style={styles.controlsContainer<br>      &lt;View style={styles.controlsContainer}&gt;<br>        &lt;Button <br>          mode=&quot;contained&quot; <br>          onPress={() =&gt; adjustTimer(-5)} <br>          style={styles.timerButton}<br>        &gt;<br>          -5 min<br>        &lt;/Button&gt;<br>        <br>        &lt;IconButton <br>          icon={isPlaying ? &#39;pause&#39; : &#39;play&#39;} <br>          onPress={togglePlayPause} <br>          size={50} <br>          style={styles.playPauseButton}<br>        /&gt;<br>        <br>        &lt;Button <br>          mode=&quot;contained&quot; <br>          onPress={() =&gt; adjustTimer(5)} <br>          style={styles.timerButton}<br>        &gt;<br>          +5 min<br>        &lt;/Button&gt;<br>      &lt;/View&gt;<br>      <br>      &lt;Text style={styles.timerText}&gt;Time Left: {timer} minutes&lt;/Text&gt;<br>    &lt;/View&gt;<br>  );<br>};<br><br>const styles = StyleSheet.create({<br>  container: {<br>    flex: 1,<br>    justifyContent: &#39;center&#39;,<br>    alignItems: &#39;center&#39;,<br>    backgroundColor: colors.background,<br>    padding: 20,<br>  },<br>  infoContainer: {<br>    marginBottom: 20,<br>    alignItems: &#39;center&#39;,<br>  },<br>  title: {<br>    fontSize: 24,<br>    fontWeight: &#39;bold&#39;,<br>    color: colors.text,<br>  },<br>  description: {<br>    fontSize: 16,<br>    color: colors.text,<br>    textAlign: &#39;center&#39;,<br>  },<br>  progressContainer: {<br>    width: &#39;100%&#39;,<br>    marginBottom: 20,<br>  },<br>  timeText: {<br>    textAlign: &#39;center&#39;,<br>    marginTop: 10,<br>    fontSize: 16,<br>    color: colors.text,<br>  },<br>  controlsContainer: {<br>    flexDirection: &#39;row&#39;,<br>    justifyContent: &#39;space-around&#39;,<br>    width: &#39;100%&#39;,<br>    marginBottom: 20,<br>  },<br>  timerButton: {<br>    width: 80,<br>  },<br>  playPauseButton: {<br>    backgroundColor: colors.primary,<br>    borderRadius: 50,<br>  },<br>  timerText: {<br>    fontSize: 18,<br>    fontWeight: &#39;bold&#39;,<br>    color: colors.text,<br>  },<br>});<br><br>export default PlayerScreen;</pre><p>After creating the above code, I ask the following question:</p><p><strong>How can I run this code? Can you provide the step-by-step instructions?</strong></p><p>We will be working on Android. Please make sure the emulator is running, and then you are asked to run the following command:</p><p>npx react-native run-android</p><p>When I run the code, I get the error <strong>“cannot read property StackView undefined”</strong> at the end. How can we solve this?</p><p>As a response, it was suggested that some packages might not have been installed correctly, and they need to be updated. I followed all the steps, but the issue persisted.</p><p>Here are the steps I followed to solve the issue:</p><pre>npm uninstall @react-navigation/native @react-navigation/stack react-native-screens react-native-safe-area-context<br>npm install @react-navigation/native @react-navigation/native-stack @react-navigation/stack react-native-screens react-native-safe-area-context react-native-gesture-handler</pre><p>Replace createStackNavigator() with createNativeStackNavigator() to use the native stack navigator.</p><p>Updated code for AppNavigator.js:</p><pre>import React from &#39;react&#39;;<br>import { NavigationContainer } from &#39;@react-navigation/native&#39;;<br>import { createNativeStackNavigator } from &#39;@react-navigation/native-stack&#39;;<br>import HomeScreen from &#39;../screens/HomeScreen&#39;;<br>import PlayerScreen from &#39;../screens/PlayerScreen&#39;;<br>import { colors } from &#39;../theme/colors&#39;;<br><br>const Stack = createNativeStackNavigator(); // Replaced Stack with NativeStackNavigator<br><br>const AppNavigator = () =&gt; {<br>  return (<br>    &lt;NavigationContainer&gt;<br>      &lt;Stack.Navigator<br>        screenOptions={{<br>          headerStyle: {<br>            backgroundColor: colors.primary,<br>          },<br>          headerTintColor: colors.white,<br>          headerTitleStyle: {<br>            fontWeight: &#39;bold&#39;,<br>          },<br>        }}<br>      &gt;<br>        &lt;Stack.Screen <br>          name=&quot;Home&quot; <br>          component={HomeScreen} <br>          options={{ title: &#39;Lullabies&#39; }} <br>        /&gt;<br>        &lt;Stack.Screen <br>          name=&quot;Player&quot; <br>          component={PlayerScreen} <br>          options={{ title: &#39;Play Lullaby&#39; }} <br>        /&gt;<br>      &lt;/Stack.Navigator&gt;<br>    &lt;/NavigationContainer&gt;<br>  );<br>};<br><br>export default AppNavigator;</pre><p>index.js:</p><pre>import &#39;react-native-gesture-handler&#39;;  // Add this line at the very top<br>import {AppRegistry} from &#39;react-native&#39;;<br>import App from &#39;./App&#39;;<br>import {name as appName} from &#39;./app.json&#39;;<br><br>AppRegistry.registerComponent(appName, () =&gt; App);</pre><p>When you complete all actions you have to run code that is belove</p><pre>npx react-native start --reset-cache</pre><p>At the end of this action you can see your code is work and amazing you can see result of this code</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4YydRkk2OMWuZgf_Hz_0ZA.gif" /></figure><p>Happy ending :D It’s truly amazing.</p><p>What we’ve learned: we developed a project from scratch, set up the navigation, and created the core structure of our app. In the next article, we will focus on designing the pages and key activities.</p><p>Note: Of course, I created the cover image using AI. Additionally, I had the article edited by it as well. :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5ee16cc391b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Management Of Product Backlog]]></title>
            <link>https://medium.com/@mfdurdu/management-of-product-backlog-ca34ed40337c?source=rss-891bf1062407------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca34ed40337c</guid>
            <category><![CDATA[backlog-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[product-owner]]></category>
            <dc:creator><![CDATA[Mehmet Fatih Durdu]]></dc:creator>
            <pubDate>Thu, 11 Jan 2024 17:39:42 GMT</pubDate>
            <atom:updated>2024-01-11T17:39:42.402Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*A5yHrq599ONS8boo" /><figcaption>Photo by <a href="https://unsplash.com/@sebastien_bonneval?utm_source=medium&amp;utm_medium=referral">Sebastien Bonneval</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Hello Everyone, In today’s article We will talk about one of most important task of Product Owners. We will work to give example in real world examples and I will give information about what I make attention about management product backlog. Here we go.</p><h3>What is product Backlog?</h3><p>Product backlog is the place where all the work to be done for the product is kept in prioritised order. The whole list of these jobs forms your product backlog. Sprint Backlog is the work list that is ready with everything ready to take action. In other words, Product backlog items may not contain details or may be at an undesirable level, but it is necessary to elaborate and clarify the items and create sprint backlogs.</p><h3>Who is responsible for Product Backlog?</h3><p>The responsibility of the product backlog is generally in the team. But the biggest responsibility is the product owner. Team members can also enter and edit items in the product backlog. Product Owner should follow the items entered.</p><h3>Product Backlog Prioritisation</h3><p>Product backlog management and prioritisation is the responsibility of the PO. Team members can influence the prioritisation by giving direction, but the final decision is generally the responsibility of the PO. Since the Product Owner also has an overview of the product, the prioritisation may change if the item that is important to the team will not serve the product.</p><h3>Product Backlog Management Tips</h3><p>It is necessary to determine some methods when managing product backlog. In general, Scrum Guide does not offer a method. I may need to proceed with methods while providing management. This may vary according to the project structure. In a modernisation project, all your backlog items may have been entered. Maybe you may only need to elaborate. If it is a project from scratch, all items may not have been entered or many items may have been entered. You can manage the process by paying attention to the following headings. You can think of this process as managing the garden of your home.</p><p>Number of backlog items</p><p>It would be good to set a limit for the number of articles and go over the articles that exceed that limit again. For example, you set the limit as 150. If you go over this limit, I suggest you go over all the items again. Because it will be really difficult to manage the backlog with too many items. In fact, if you think like the garden of your house, you should have as many flowers as you will maintain in the garden of the house. If the number of flowers approaches 150, you should be selective if you are going to buy new ones in your garden.</p><p>Making refinement meetings</p><p>Scrum does not actually recommend too many meetings. Teams can increase the number of meetings due to the need to work remotely and talk more. Refinement meeting is a very important meeting for product backlog. Because we can talk about the details of the product backlog items with the team and how much we can prioritise or how many items we need to divide. If there are actions we need to take beforehand, you can address them all. If we continue from the example in your home garden, if a new flower that you do not know will be put in your garden, you should learn all the details of a new flower and take the necessary steps for the flower to live. You can think that this is provided by the refinemet meeting.</p><p>Don’t Be Afraid to Delete</p><p>Some loves may lose their importance and priority in the future. In this case, it will be necessary to look at whether it can be deleted and delete the relevant articles. The item that needs to be deleted and that you do not delete will pollute the environment you are constantly trying to manage. If you think of it as a home garden, you should clean the dried and odourless flowers so that there is room for new flowers.</p><p>Dominate Backlog</p><p>The items entered in the backlog must be within your knowledge. When someone makes a new request, it does not make sense to add it to the backlog again if it was added in the past. That’s why you have to master the whole backlog. I think this is the most difficult. It will keep it alive.</p><h3>Things to Avoid When Managing Product Backlog</h3><ol><li>You should definitely not leave the entire backlog management to someone else.</li><li>You must have a complete command of the backlog you manage, otherwise you will come across items you do not know.</li><li>In the backlog, tasks should be ordered according to priorities. An absolutely unimportant item should not stand on top.</li><li>I recommend that you do not do item detailing in sprint planning. Because if there is a subject that is not clarified, you will have to take it to the sprint.</li><li>It would be good to evaluate large-scale and critical items in refinement meetings.</li></ol><p>Hope to meet in our next article. Be agile, stay agile</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca34ed40337c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[B2B vs B2C Product Ownership Differences]]></title>
            <link>https://medium.com/@mfdurdu/b2b-vs-b2c-product-ownership-differences-69135f7bea0e?source=rss-891bf1062407------2</link>
            <guid isPermaLink="false">https://medium.com/p/69135f7bea0e</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[product-owner]]></category>
            <dc:creator><![CDATA[Mehmet Fatih Durdu]]></dc:creator>
            <pubDate>Thu, 04 Jan 2024 02:16:57 GMT</pubDate>
            <atom:updated>2024-01-04T02:16:57.767Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3wohuod954vBdU8Q" /><figcaption>Photo by <a href="https://unsplash.com/@jasongoodman_youxventures?utm_source=medium&amp;utm_medium=referral">Jason Goodman</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Greetings to everyone,</p><p>In today’s article, we will talk about what a product owner should pay attention to for B2B and B2C in some topics. Let’s get started.</p><p><strong>Target Audience</strong></p><p>As a product owner, the most important issue is to find the answer to the question of who is the target audience of the product. Because all decisions and the vision of the product will be determined according to the target audience. When a feature is requested from you, if it comes to an application for b2b, it may be important to consider the economic return of the feature and customer satisfaction, and even it may be important for you to show the advantages of the companies you work with a different feature from your competitors or to take it one step forward.</p><p>If we evaluate for B2C, the product owner will need to know the users very well. By monitoring customer movements, it may be necessary to aim to minimise the loss of customer time and even reduce the steps that users do too much. When evaluating the features, it will be important to prioritise the features that will not cause customer loss. The effect of each feature on the fee should be measured. Each feature should be planned by anticipating customer loss.</p><p><strong>Sales Strategies</strong></p><p>If you are a product owner in a B2B team, sales will generally proceed with dealer-style sales. Since new features and improvements will be transferred to dealers from sales teams, it will be necessary to make sure that sales teams are aware of new versions. But for B2C, you may have to find the channel and way to deliver every development and improvement to customers, as these works will be spread through social media, etc. channels.</p><p><strong>Pricing</strong></p><p>When selling for B2B, it can be sold for a large fee. A single company can be sold for a very large fee. At this point, requests from the field or requests from the sales teams will need to be very prioritised.</p><p>Since sales for B2C are made with a large-scale low price, new features should be added according to the behaviour of customers and pricing should be evaluated at this point. In other words, there will be no direct prioritisation of requests from the field and no price change for every task. It will be necessary to be aware.</p><p><strong>Customer Behaviour</strong></p><p>For B2B, customers usually proceed through data. They are interested in what they will add to their own company and their impact on their KPIs. For a product owner, you may need to rationally present any changes to the product and development points for the business.</p><p>For B2C, customers behave emotionally. They own your application and feel as if it belongs to them. It may be necessary to focus on the loyalty of customers in every work done.</p><p><strong>Customising the Product</strong></p><p>For B2B, customer demands may not end with their unique demands. It may not be good to include every request made directly in the sprints as an improvement.</p><p>A personalised development for B2C is almost non-existent. If there is a demand, it would be more logical to develop this demand by looking at the cost and cost of work.</p><p>In general, we talked about how we should proceed as a product owner and what dynamics there are. Of course, the role of product owner is not always the only correct one. Metrics, dynamics, degree of importance may change for each subject and it may be necessary to decide accordingly. Therefore, not looking from a single angle will make you strong.</p><p>Hope to see you in the next article</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69135f7bea0e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scrum Values: The Power of Teamwork in Software Development]]></title>
            <link>https://medium.com/@mfdurdu/scrum-values-the-power-of-teamwork-in-software-development-bfa59e84d489?source=rss-891bf1062407------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfa59e84d489</guid>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Mehmet Fatih Durdu]]></dc:creator>
            <pubDate>Wed, 12 Jul 2023 05:24:24 GMT</pubDate>
            <atom:updated>2023-07-12T05:24:24.758Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0GEC6MsVpbjFhW1r" /><figcaption>Photo by <a href="https://unsplash.com/es/@designer4u?utm_source=medium&amp;utm_medium=referral">Olga Guryanova</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Hello everyone today I will explore Scrum values and how to effect to character of scrum team. Here we go.</p><p>The process of software development requires flexibility and efficiency to adapt to rapidly changing business requirements. That’s why an effective framework like Scrum is needed to avoid common pitfalls and achieve success. Scrum provides a set of core values that enable a team to work together successfully. In this article, we will explore the Scrum Values and their significance in software development.</p><p><strong>1.Commitment:</strong></p><p>Commitment is one of the fundamental values of Scrum. Team members commit to achieving the agreed-upon goals. This involves showing the necessary effort to complete the work, delivering on promises, and fostering a collaborative environment. Each team member contributes to the project through their commitments.</p><p><strong>2.Courage:</strong></p><p>Scrum encourages team members to be courageous. Taking risks, embracing challenges, and fostering innovation are essential for progress. Team members should feel comfortable expressing their ideas, confronting difficulties, and making bold decisions when necessary. Courage empowers teams to be creative and innovative.</p><p><strong>3.Collaboration:</strong></p><p>Collaboration is highly valued in Scrum. The Product Owner, Development Team, and Scrum Master work together to achieve success. Effective communication and knowledge sharing are encouraged among team members. Collaboration brings different skills together, amplifying the team’s power and leading to better outcomes.</p><p><strong>4.Transparency:</strong></p><p>Transparency is a key value in Scrum. It is important to keep all stakeholders informed about project progress and decisions. Regularly sharing information and progress updates enables everyone to have visibility into the project’s status. Transparency fosters trust and enables the team to make better decisions.</p><p><strong>5.Focus:</strong></p><p>Scrum emphasizes the value of focus. Teams should concentrate on the prioritized work, reducing the risk of distractions. By focusing on the most important tasks, teams increase efficiency and deliver customer value with determination. Focus accelerates the team’s progress towards the desired goals.</p><h3>Lastly:</h3><p>Scrum Values form the foundation for a powerful team in software development. Commitment, courage, collaboration, transparency, and focus are the core principles that enable successful Scrum teams. These values promote accountability, risk-taking, collaboration, clear communication, and goal-oriented progress. By adhering to the Scrum Values, teams achieve better results and establish a solid foundation for success in software projects.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfa59e84d489" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Empiricism and Scrum : The Contribution of an Experience-Based Approach to Agile Software…]]></title>
            <link>https://medium.com/@mfdurdu/empiricism-and-scrum-the-contribution-of-an-experience-based-approach-to-agile-software-be67fc7807d6?source=rss-891bf1062407------2</link>
            <guid isPermaLink="false">https://medium.com/p/be67fc7807d6</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[product-owner-skills]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Mehmet Fatih Durdu]]></dc:creator>
            <pubDate>Sat, 08 Jul 2023 09:30:32 GMT</pubDate>
            <atom:updated>2023-07-08T09:30:32.930Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Empiricism and Scrum : The Contribution of an Experience-Based Approach to Agile Software Development</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lm-Q6RMRWHscUAi8" /><figcaption>Photo by <a href="https://unsplash.com/@chrislawton?utm_source=medium&amp;utm_medium=referral">Chris Lawton</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Agile software development is an approach that can respond to rapidly changing jobs requirement and continuously provide a value . One of the cornerstones of this approach is Scrum. Scrum is an agile method that is based on team working, iterative process and continuous feedback. One of the most important factors behind the success of Scrum is that it adopts an experience-based approach known as empiricism.</p><p>In this article, We will explore the relationship between empiricism and Scrum and examine how an experience-base approach to contribute to agile software development process</p><p>Fundamental Principles of Empiricism</p><p>Empiricism is an philosophical approach that argues that knowledge is obtained through experience and observation</p><p>1- <strong>Transparency</strong> : Scrum adopts the principle of transparency to ensure that all stakeholders have complete and accurate information about the status of project, process and obstacles. Team members share their work and process with stakeholders, ensuring that everyone is on at the same page and making appropriate decisions . If you work without transparency , Scrum cant works. stackholders cant trust to your team and your plan</p><p><strong>2. Inspection:</strong> Scrum follows the principle of inspection, which involves regularly receiving feedback and evaluating the current state of affairs. Activities such as Sprint reviews, Daily Scrum, and Sprint planning allow the team to review progress and make improvements.</p><p><strong>3. Adaptation:</strong> Adaptation involves making continuous improvements based on the feedback received. The Scrum team constantly adapts to overcome obstacles, align with customer feedback, and respond to changing requirements.</p><p><strong>II. The Unity of Scrum and Empiricism:</strong></p><p>Scrum embraces the principles of empiricism, and this unity leads to successful outcomes in agile software development.</p><p><strong>1. Continuous Feedback Loop:</strong> Scrum employs short and defined time intervals called Sprints. Each Sprint concludes with a usable product increment that aligns with the expectations of the product owner. This continuous feedback loop ensures the product provides value from early stages and continually improves.</p><p><strong>2. Transparency and Inspection:</strong> Scrum encourages transparency and inspection among team members. Daily Scrum meetings, Sprint reviews, and Sprint planning sessions enable the team to share progress with stakeholders and gather feedback. This promotes a shared understanding of the project’s status and allows the team to take appropriate actions.</p><p><strong>3. Adaptation and Continuous Improvement:</strong> The Scrum team evaluates the feedback obtained during Sprint reviews and makes necessary improvements. Adaptation involves overcoming obstacles, making changes required to achieve goals, and updating the product roadmap. The ability to continuously learn and adapt forms the foundation of Scrum’s success.</p><p><strong>Lastly:</strong></p><p>Empiricism and Scrum bring an experience-based approach to agile software development. Supported by the principles of transparency, inspection, and adaptation, Scrum enhances the team’s ability to learn, adapt, and create valuable products. The unity of empiricism and Scrum plays a critical role in successfully implementing agile software development. Therefore, Scrum teams should embrace the principles of empiricism and leverage their experiences to continuously improve and deliver successful outcomes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be67fc7807d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile Manifesto]]></title>
            <link>https://medium.com/@mfdurdu/agile-manifesto-40b85b7bc097?source=rss-891bf1062407------2</link>
            <guid isPermaLink="false">https://medium.com/p/40b85b7bc097</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Mehmet Fatih Durdu]]></dc:creator>
            <pubDate>Thu, 06 Jul 2023 23:14:28 GMT</pubDate>
            <atom:updated>2023-07-06T23:14:28.014Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*75-zNN_0KoYyE9Ux" /><figcaption>Photo by <a href="https://unsplash.com/@epicantus?utm_source=medium&amp;utm_medium=referral">Daria Nepriakhina 🇺🇦</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Hi everyone, My career has changed to Product Owner 1 years ago, In previous experinece I have worked as Scrum Master also Software Engineer. In this experience I focus on only the Product Owner role. Of course I had need to changed my mind. Because when you are working as Software Engineer you need to focus on only your task. But If you become Product Owner. You would spent time for your stakholders , also you have to spend Product Vision and you have to be interested in the team for much more effort. Then you have to understand all of part of Software(Market,Customer,Software) But it is not mandatory.</p><p>Nowadays , I have decided to complete Product Owner learning path in scrum org you can find link at this <a href="https://www.scrum.org/pathway/product-owner-learning-path">https://www.scrum.org/pathway/product-owner-learning-path</a></p><p>First article is absouloutely show up agile manifesto :) , I have decided to article about agile manifesto . I have talked about my experience about agile manifesto .</p><h3><strong>What is Agile Manifesto and Why?</strong></h3><p>The software industry is an environment that constantly faces changing requirements. Traditional software development processes may struggle to adapt to this rapid change. Based on these challenges, the Agile Manifesto emerged. The Agile Manifesto provides a guide to transform the software development process and embrace a faster, more flexible approach.</p><h3>The emergence of the Agile Manifesto</h3><p>Traditional approaches in the software industry are characterized by lengthy planning stages, rigid schedules, and strict processes. However, the lack of flexibility in this approach and the challenges of adapting to rapidly changing requirements highlighted the necessity for a new approach. This need led to the creation of the Agile Manifesto in 2001, which aimed to transform software development methods. The Manifesto was drafted by prominent software experts coming together to establish common values and principles.</p><h3>The Basic Principles of the Agile Manifesto</h3><p>The Agile Manifesto emphasizes four core values and twelve principles. These values are listed as individuals and interactions, working software, customer collaboration, and responding to change. Individuals and interactions highlight the importance of the human factor in the software development process. Working software emphasizes the value of a functional product over comprehensive documentation. Customer collaboration expresses the necessity of close collaboration with customers. Responding to change emphasizes the ability to adapt to rapid changes.</p><h3>Twelve Principles of Agile Software</h3><p>I will more detail through real experience by item by item</p><p><strong>Our highest priority is to satisfy the customer<br>through early and continuous delivery<br>of valuable software. -&gt; </strong>We invested a significant amount of time on a single feature, but we were unable to fulfill all the requirements for it. After several months, we finally delivered the feature as expected by the customer. However, upon its introduction, the customer expressed dissatisfaction with the feature. This was primarily due to our failure to prioritize the creation phase with the aim of satisfying the customer. It is crucial to establish a creation phase focused on delivering valuable software in order to meet customer expectations.</p><p><strong>Welcome changing requirements, even late in <br>development. Agile processes harness change for <br>the customer’s competitive advantage. -&gt; </strong>In one feature, It was related consent . We spent a lot of time for grooming etc. we have started to development. We almost have completed all of requirements but in the developlement section , Goverment make decision as legilation and it effect our all development. All of development have been changed according to by taken government decision</p><p><strong>Deliver working software frequently, from a <br>couple of weeks to a couple of months, with a <br>preference to the shorter timescale. -&gt;</strong>If you spent more than month for feature. Requirements may be changed. We faced with problem</p><p><strong>Business people and developers must work <br>together daily throughout the project. -&gt;</strong> I cant give example. If you dont work together. You can develop software which cant be fit requirements.</p><p><strong>Build projects around motivated individuals. <br>Give them the environment and support they need, <br>and trust them to get the job done. -&gt;</strong> Generally We work with motivated people. Motivation and emotion are more important than technical knowledge</p><p><strong>The most efficient and effective method of <br>conveying information to and within a development <br>team is face-to-face conversation. -&gt;</strong> I believe that effective communication can solve any problem. For instance, there was a situation where we started working on a task that came in through an email without fully clarifying the requirements. We failed to communicate with the owner of the requirement. As a result, we invested significant time in completing the development. However, when the owner finally saw the outcome, they expressed dissatisfaction, stating that it wasn’t what they had wanted. This scenario clearly demonstrates the impact of a communication problem.</p><p><strong>Working software is the primary measure of progress. -&gt;</strong> In many sprints, we diligently measured the Scrum team’s completed story points, and everything seemed to be going well. However, after 3–4 sprints, stakeholders became increasingly dissatisfied. It became evident that our focus on story points had overshadowed the ultimate goal of delivering working software. Instead of prioritizing the tangible outcomes and value provided by the software, we had inadvertently placed excessive emphasis on the metric of story points.</p><p><strong>Agile processes promote sustainable development. <br>The sponsors, developers, and users should be able <br>to maintain a constant pace indefinitely. -&gt;</strong> It is crucial to protect the outcomes of your team. Without dedicating time and effort to this, it becomes challenging to accurately measure your team’s achievements.</p><p><strong>Continuous attention to technical excellence <br>and good design enhances agility. -&gt;</strong> In this particular development project, we had a deadline to meet for a specific feature, so our primary focus was on delivering quickly. Unfortunately, due to this time constraint, we were unable to prioritize technical excellence. Initially, when we delivered the feature, everyone seemed satisfied. However, when we started working on the second feature that relied on the previous development, we encountered technical difficulties. We found ourselves needing to rewrite code for the same area</p><p><strong>Simplicity — the art of maximizing the amount <br>of work not done — is essential. -&gt;</strong>If you dont focus simplicity , Your product will become shit :)</p><p><strong>The best architectures, requirements, and designs <br>emerge from self-organizing teams. -&gt;</strong> If you dont create self-organized team. You have to spent much more time then excepted time for team</p><p><strong>At regular intervals, the team reflects on how <br>to become more effective, then tunes and adjusts <br>its behavior accordingly. -&gt;</strong> We completed the retrospectives of our sprints, but we failed to take action on the tasks that emerged as outcomes from those retrospectives. As a result, we were unable to create a positive impact within our team.</p><h3>Benefits of the Agile Manifesto</h3><p>The Agile Manifesto brings forth several advantages. Firstly, it facilitates a faster and more efficient software development process. Short iterations and frequent feedback loops enable the rapid delivery of valuable working software. Additionally, it enhances customer satisfaction. Customers are actively engaged throughout the project, leading to better responsiveness to their changing needs. The Agile approach fosters teamwork and improves communication within the development team. The use of small, self-organizing teams boosts productivity and encourages creativity. Lastly, the Agile Manifesto promotes flexibility, adaptability, and the ability to respond effectively to changes. It acknowledges that change is inevitable and encourages the adjustment of processes accordingly.</p><h3>Limitations and Challenges of the Agile Manifesto</h3><p>The implementation of the Agile Manifesto may encounter some challenges. Adapting to changes at the business and organizational level can pose difficulties. This transformation process requires full collaboration and commitment. Additionally, it should be noted that the Agile Manifesto may not be suitable for all projects and organizations. In some cases, more traditional or non-agile approaches may be more appropriate.</p><p>We will continue for next article . Thanks for reading</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40b85b7bc097" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Spring Boot MongoDB Connection]]></title>
            <link>https://medium.com/@mfdurdu/spring-boot-mongodb-connection-1218bbfe4c13?source=rss-891bf1062407------2</link>
            <guid isPermaLink="false">https://medium.com/p/1218bbfe4c13</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[mongodb]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[spring-boot]]></category>
            <dc:creator><![CDATA[Mehmet Fatih Durdu]]></dc:creator>
            <pubDate>Mon, 20 Mar 2023 12:04:38 GMT</pubDate>
            <atom:updated>2023-03-20T12:04:38.259Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*q5hNT3i92-hJpBSa" /><figcaption>Photo by <a href="https://unsplash.com/@rubaitulazad?utm_source=medium&amp;utm_medium=referral">Rubaitul Azad</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Hello Everyone, Today I will explain how to implement mongodb connection through spring boot. We will create application which allow to create Basketball player and list of all of players in database</p><p>In this blog we will complete this steps</p><p>1- We will install MongoDB through Docker<br>2- We will create project through <a href="https://start.spring.io/">https://start.spring.io/</a><br>3- We will Mongodb model in our project<br>4- We will implement Repository that in interface for connection with Database<br>5- We will create Service and Rest Api for our app<br>6- Lastly test :)</p><p>Here we go ,</p><p><strong>1- Download Mongodb Through Docker</strong></p><p>Firstly we need to download mongodb trough Docker.</p><p>In the first step we have to run this command prompt which is give allowance to use mongodb in your computer</p><blockquote><strong>docker run -p 27017:27017 mongo:latest</strong></blockquote><p>When you run this command docker creates a container which is running mongodb in 27017 ports . You can connect easily from your ide or mongo gui client.</p><p><strong>2- Create Spring Boot Project Through Spring Initializer</strong></p><p>You have to go <a href="https://start.spring.io/"><strong>https://start.spring.io/</strong></a> for creating Spring app easily.</p><p>You can choose these choice.</p><ul><li><strong>Project</strong>: Maven</li><li><strong>Spring Boot Version</strong>: 3.0.4</li><li><strong>Dependencies</strong>: You have to add two dependency <strong>Spring Web</strong> and <strong>String Data MongoDB</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fqj3gX42AB3J_vnnmBq9jQ.png" /></figure><p>When you click Generate button . You would create application which is include all of requirements for our aim. You have to unzip your project to where do you want in your pc. After doing that, You can open your project in Intellij IDEA CE. When you open this project you will see something like at below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/358/1*UozL8CEaz_CSm1vooH1zxA.png" /></figure><p><strong>3-Create Model</strong></p><p>Player model must be have 6 property like id,name,birthDate,position,team<br>You can find model of Player.</p><pre>import org.springframework.data.annotation.Id;<br>import org.springframework.data.mongodb.core.mapping.Document;<br><br>@Document<br>public class Player {<br>    <br>    @Id<br>    private String id;<br>    private String name;<br>    private String nationality;<br>    private String birthDate;<br>    private String position;<br><br>    public Player(String id, String name, String nationality, String birthDate, String position) {<br>        this.id = id;<br>        this.name = name;<br>        this.nationality = nationality;<br>        this.birthDate = birthDate;<br>        this.position = position;<br>    }<br><br>    public Player() {<br>    }<br><br>    public String getId() {<br>        return id;<br>    }<br><br>    public void setId(String id) {<br>        this.id = id;<br>    }<br><br>    public String getName() {<br>        return name;<br>    }<br><br>    public void setName(String name) {<br>        this.name = name;<br>    }<br><br>    public String getNationality() {<br>        return nationality;<br>    }<br><br>    public void setNationality(String nationality) {<br>        this.nationality = nationality;<br>    }<br><br>    public String getBirthDate() {<br>        return birthDate;<br>    }<br><br>    public void setBirthDate(String birthDate) {<br>        this.birthDate = birthDate;<br>    }<br><br>    public String getPosition() {<br>        return position;<br>    }<br><br>    public void setPosition(String position) {<br>        this.position = position;<br>    }<br><br>    @Override<br>    public String toString() {<br>        return &quot;Player{&quot; +<br>                &quot;id=&#39;&quot; + id + &#39;\&#39;&#39; +<br>                &quot;, name=&#39;&quot; + name + &#39;\&#39;&#39; +<br>                &quot;, nationality=&#39;&quot; + nationality + &#39;\&#39;&#39; +<br>                &quot;, birthDate=&#39;&quot; + birthDate + &#39;\&#39;&#39; +<br>                &quot;, position=&#39;&quot; + position + &#39;\&#39;&#39; +<br>                &#39;}&#39;;<br>    }<br>}</pre><p>Lets check detail of our model.</p><p>As you can see <strong>@Document</strong> annotation gives to property for creating model MongoDB. This is same like <strong>@Entity</strong> annotation in JPA in other hand <strong>@Id</strong> annotation is generate random uuid for your document.</p><p><strong>4- Repository for MongoDB Connection</strong></p><p>You have to create interface to communicate with MongoDB easily. You can find repository interface et below</p><pre>import com.fatihdurdu.player.model.Player;<br>import org.springframework.data.mongodb.repository.MongoRepository;<br><br>public interface PlayerRepository extends MongoRepository&lt;Player,String&gt; {<br>}</pre><p>This repository interface is occurred only 4–5 line :) This is amazing Spring Data helps to creating database methods easily. When you with extend <strong>MongoRepository &lt;DocumentName,ID&gt; </strong>you can give ability Crud operation methods to your interface.</p><p><strong>5- Create Service and RestController</strong></p><p>Service layer gives to allow create logical actions . Controller layer gives to allow connection with world-wide.</p><p>Lets create Service Class</p><pre>import com.fatihdurdu.player.model.Player;<br>import com.fatihdurdu.player.model.PlayerDto;<br>import com.fatihdurdu.player.repository.PlayerRepository;<br>import org.springframework.stereotype.Service;<br><br>import java.util.List;<br><br>@Service<br>public class PlayerService {<br><br>    private final PlayerRepository playerRepository;<br><br>    public PlayerService(PlayerRepository playerRepository) {<br>        this.playerRepository = playerRepository;<br>    }<br><br>    public PlayerDto createPlayer(PlayerDto dto) {<br>        Player activePlayer = convertToEntity(dto);<br>        PlayerDto resultObject = convertToDto(playerRepository.save(activePlayer));<br>        return resultObject;<br><br>    }<br><br>    public List&lt;PlayerDto&gt; list() {<br>        return playerRepository.findAll().stream().map(item -&gt; convertToDto(item)).toList();<br>    }<br><br>    private Player convertToEntity(PlayerDto dto) {<br>        Player player = new Player();<br>        player.setBirthDate(dto.getBirthDate());<br>        player.setNationality(dto.getNationality());<br>        player.setPosition(dto.getPosition());<br>        player.setName(dto.getName());<br>        return player;<br>    }<br><br>    private PlayerDto convertToDto(Player player) {<br>        PlayerDto playerDto = new PlayerDto();<br>        playerDto.setId(player.getId());<br>        playerDto.setBirthDate(player.getBirthDate());<br>        playerDto.setNationality(player.getNationality());<br>        playerDto.setPosition(player.getPosition());<br>        playerDto.setName(player.getName());<br>        return playerDto;<br>    }<br>}</pre><p>As you can see if you use a class like Service you have to use @Service annotation. We have two method first one allows to create player in our Database which name is createPlayer. The another one allows to list of data in our Database which name is list. The other methods are for converting object to eligible form.</p><p>Now we can create Controller class for connection with world-wide. All of clients can access your api through RestApi. You have many different rest api method like <strong>GET,POST,DELETE,PUT,PATCH.</strong> Now we will use only GET and Post Method. If you want to learn much more stuff about Rest Api Method you can find detail in this <a href="https://testfully.io/blog/http-methods/">link</a>.</p><p>You can find rest api in below.</p><pre>import com.fatihdurdu.player.model.PlayerDto;<br>import com.fatihdurdu.player.model.PlayerRequest;<br>import com.fatihdurdu.player.model.PlayerResponse;<br>import com.fatihdurdu.player.service.PlayerService;<br>import org.springframework.web.bind.annotation.*;<br><br>import java.util.List;<br><br>@RestController<br>@RequestMapping(&quot;api/players&quot;)<br>public class PlayerController {<br><br>    private final PlayerService playerService;<br><br>    public PlayerController(PlayerService playerService) {<br>        this.playerService = playerService;<br>    }<br><br>    @GetMapping<br>    private List&lt;PlayerResponse&gt; getAll() {<br>        List&lt;PlayerDto&gt; dtoList = playerService.list();<br>        return dtoList.stream().map(item -&gt;convertResponse(item)).toList();<br>    }<br><br>    @PostMapping<br>    private PlayerResponse save(@RequestBody PlayerRequest playerRequest){<br>        PlayerDto savedObject = playerService.createPlayer(createDtoFromRequest(playerRequest));<br>        return convertResponse(savedObject);<br>    }<br><br><br>    private PlayerResponse convertResponse(PlayerDto dto) {<br>        return new PlayerResponse(dto.getId(), dto.getName(), dto.getNationality(), dto.getBirthDate(), dto.getPosition());<br>    }<br><br>    private PlayerDto createDtoFromRequest(PlayerRequest playerRequest){<br>        return new PlayerDto(playerRequest.getName(),playerRequest.getNationality(),playerRequest.getBirthDate(),playerRequest.getPosition());<br>    }<br>}</pre><p>As you can see @RestController annotation allows for ability to make rest controller its class. The another annotation is @RequestMapping which is used for defination of your api. When clients want to access your player api they have to use “/api/players”.</p><p>After all of development we need to make one more task. We have to add database connection string to your application properties file. When you add line to your properties file your app will connect to mongodb.</p><pre>spring.data.mongodb.uri=mongodb://localhost:27017/player</pre><p>Remember we didnt use username and passsword when we install and run mongodb docker image. Because of this we don’t need to use username and password in our connection string.</p><p>Lastly, We can test our application :)</p><p>I prefer to use postman for testing our api . You can choose another api test tool.</p><p>In the first step you have to create new Player as below request.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QFEsxRHGCOK5vfHjAozUDw.png" /></figure><p>Second one you have to call list method to see all of data in your Database. You can find request in picture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l9b8npGPmk6Hu_P7j67FMg.png" /></figure><p>We are best developers in the world. We have completed all of requirement in our project. We will continue in next article. Stay with Java :)</p><p>You can find code repository : <a href="https://github.com/durdufatih/spring-boot-mongodb">https://github.com/durdufatih/spring-boot-mongodb</a></p><p>You can contact with me : <a href="https://www.linkedin.com/in/mehmet-fatih-durdu-05b84550/">LinkedIn</a> , <a href="https://twitter.com/FthDurdu">Twitter</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1218bbfe4c13" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Software Engineer Rolünden Product Owner Rolüne Geçiş]]></title>
            <link>https://medium.com/@mfdurdu/software-engineer-rol%C3%BCnden-product-owner-rol%C3%BCne-ge%C3%A7i%C5%9F-f0a6b24dc182?source=rss-891bf1062407------2</link>
            <guid isPermaLink="false">https://medium.com/p/f0a6b24dc182</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[stakeholder-management]]></category>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Mehmet Fatih Durdu]]></dc:creator>
            <pubDate>Mon, 06 Mar 2023 14:54:08 GMT</pubDate>
            <atom:updated>2023-03-06T14:54:08.976Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dITphIiNj8AgZ7H2" /><figcaption>Photo by <a href="https://unsplash.com/fr/@austindistel?utm_source=medium&amp;utm_medium=referral">Austin Distel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Selamlar bu makaleyi yazabilmek için yaklaşık 1 yıl bekledim. Rolün 1 yılını doldurduktan sonra bu makaleyi yazmaya karar verdim. Sizlere neler yaşadığımı ne gibi farklılıkları olduğunu bu rol için hangi özellikler gerektiğini yaplaşacağım.</p><p>Bu geçiş kolay gibi gözüksede popüler olan bir alan olan Java yazılım uzmanlığını bırakıp Product Owner olarak kariyere devam etme kararı çok kolay olmadı . Bazı gel gitler yaşadım. Arada yanlış karar aldığımı hissettiğim anlar oldu . Hata kendimi değersiz hissettiğim anlarda oldu. Fakat en sonunda şunu gördüm Product Owner ürüne yol veren kişidir. Yazılımcı olarak genelde ürün için alınan kararları elindeki imkanlarla en iyi mühendisliği sunmayı amaçlar . Fakat Product Owner rolü elindeki işler ve yönlendirmelerle ürünü istediği noktaya kolaylıkla çekebilme yeteneği sunar. Bu farklılık bana çekici geldi ve kariyerimi ürün yönetimi kısmına kaydırdım.</p><h3><strong>Yazılım Geçmişim</strong></h3><p>Çok büyük projelerde Backend developer olarak yazılım geliştirici olarak yaklaşık 9 yıl çalıştım. Çok büyük trafik altında çalışan uygulamalarda geliştirme yaptım. Bu projelerin hepsinde agile ile geliştirme yapan ekipte bulundum. Yaklaşık olarak 5 yıl scrum master olarak görev yaptım. Scrum org üzerinden PSM-1 belgem bulunuyor.</p><p>Geliştirme yaparken inanılmaz bir haz duyan birisiyim. Product Owner rolünde devam ederken boş vakitlerimde mobil geliştirme yapıyorum. SwiftUI kullanarak mobil uygulamalar geliştiriyorum. Mesai bitiminden sonra geliştirme yapamayı bırakamadım :)</p><h3><strong>Şimdiki Durumum</strong></h3><p>Şuan Vodafone’da Technical Product Owner rolünü yürütüyorum. Bulunduğum projede aynı anda 6 şirket ile iletişimde olarak ihtiyaclarını karşılamak ve onları önceliklendirmek durumundayım. Çok fazla talebi yönetimsel olarakda değerlendirip en doğru bir roadmap oluşturmaya çalışıyorum .Aynı zamanda projelerde verdiğimiz tarihlere göre ekibin deploy etmesi gereken kodlarıda canlıya geçilmesi adına takip ediyorum.</p><h3><strong>Amacım</strong></h3><p>Bu kariyer değişikliğini kurumsal şirketlerdeki iletişim becerimin iyi oldugunu fark ettim . Ek olarak ürüne daha fazla yön verebiliyor olmak çok ama çok daha iyi hissettirdiğini fark ettim.</p><h3><strong>Role gereksinimleri</strong></h3><p>Sadece rolümün gereksinimlerini yaparım . Gerisine karışmam diyebileceğiniz bir rol degildir. Bundan dolayı işin olması için gerekli bütün problemleri ortadan kaldırmanız gerekebilir.</p><p>Product owner backlog oluşturmak adına çok fazla toplantıya girmesi gerekebilir. Bundan dolayı çok fazla toplantılara katılmanız gerekiyor. İletişim gücünüzün yüksek olması önemli bir hale geliyor.</p><p>Her toplantıda Software Engineer olamayacağından ürünün genel yapısına hakim olmanız gerekiyor. Bu toplantıda teknik olarak hızlı cevaplar vermeniz gerekebilir. Ürünün yönünü belirleyeceğiniz toplantılarda da bu ihtiyaç doğacaktır. Bundan dolayı sürekli hazır olmak gerekir.</p><p>Sunum becerilerinizin iyi olması gerekiyor. Çok önemli toplantılarda CXO seviyesinde bir sunum gerçekleştiriyor olabilirsiniz.</p><p>Yazılım uzmanı olarak çok fazla detaya hakim olmanız beklenir. Fakat Product Owner olarak bütün detaylardan çok ürünün geneline ve vizyonuna hakim olmanız beklenir. Yani çok detayda ürüne yol vermemiz zorlaşabilir.</p><p>Backlog management sürekli yenilemek gereken birsey. Bazen aynı işleri tekrar tekrar konuşuyor hissedebilirsiniz.</p><p>Maddeleri önceliklendirme stresli bir iş olabilir. Bu stresi iyi yönetiyor olabilmeniz gerekiyor.</p><h3><strong>Artılar</strong></h3><p>Ürüne siz yön verirsiniz. Yapılmaması gerektiğini düşündüğünüz bir geliştirme varsa mantıklı sebepler göstererek yaptırmayabilirsiniz.</p><p>Dünyaca kullanılan uygulamalarda ürünün geleceğine yön verebiliyor olmak çok heyecan vericidir.</p><p>Yönetim seviyesinde toplantılara katıldığınız için onlara çok yakınsınızdır. Fikirlerini kolaylıkla alabilirsiniz.</p><p>Çok fazla stackholder ile iletişim olduğu için networkünüz çok hızlı bir sekilde büyür.</p><h3><strong>Eksiler</strong></h3><p>Çok fazla toplantıdan dolayı bazen hiç bise yapmamış gibi hissedebilirsiniz.</p><p>Kendinizi geliştirmek adına bazı aksiyonlar gerçekleştiremiyor hissedebilirsiniz.</p><p>Teknik bir işten geçtiyseniz yaptığınız iş değersiz hissedebilirsiniz.</p><p>Fakat bütün bunların ışığında bu rolü gerçekleştirmek adına sürekli kendiniz geliştirmeniz ekibin ve projenin iletişimi olan herseye ve herkese eşit mesafede olmanız sizin açınızdan iyi olacaktır. Hangi ülkede bu rolü yapacaksanız bu rol için İngilizce dışında o ülkenin anadilini öğrenmek bu rolü güçlü bir şekilde yapabilmek adına önemlidir.</p><p>Diğer yazılarımızda buluşmak adına.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0a6b24dc182" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Android Jetpack Compose Permissions]]></title>
            <link>https://medium.com/@mfdurdu/android-jetpack-compose-permissions-d8500c36362e?source=rss-891bf1062407------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8500c36362e</guid>
            <category><![CDATA[jetpack]]></category>
            <category><![CDATA[accompanist]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[jetpack-compose]]></category>
            <dc:creator><![CDATA[Mehmet Fatih Durdu]]></dc:creator>
            <pubDate>Sun, 14 Aug 2022 01:53:11 GMT</pubDate>
            <atom:updated>2022-08-14T01:53:11.898Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DEM3sybGDV3z8Xfr" /><figcaption>Photo by <a href="https://unsplash.com/@gcoppa?utm_source=medium&amp;utm_medium=referral">Guido Coppa</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Hello Everyone, today we will talk about how to request permission from a user. Imagine, you have to request a Camera, Location , or Storage permission. How do you request in Jetpack compose app?</p><p>First of all, I have preferred to use accompanist libraries to request permission from the user. For Jetpack compose you can’t use request permission in base android features.</p><p>As you can see the definition of accompanist libraries on its website this library present commonly used and required features for Compose</p><blockquote>Accompanist libraries is a group of libraries that aim to supplement Jetpack Compose with feature that are commonly required by developers but not yet available</blockquote><p>Here we go, You need to add an <strong>implementation line </strong>to your project <strong>build.gradle</strong> file</p><pre>dependencies{</pre><pre>...<br>implementation &#39;com.google.accompanist:accompanist-permissions:0.23.1&#39;</pre><pre>}</pre><p>This util jar presents two type permission states for development the first one rememberPermissionStatethe second one is rememberMultiplePermissionsState</p><p>The<em> </em>rememberPermissionState(permission:String)allows you to request permission from the user and also check this permission has been obtained from the user before The rememberMultiplePermissionsState(permission: List&lt;String&gt;)offers the same properties but it is for multiple permission</p><p>On the accompanist website, you can find example like below for permissions.</p><pre>@Composable<br>private fun FeatureThatRequiresCameraPermission() {<br><br>    // Camera permission state<br>    val cameraPermissionState = rememberPermissionState(<br>        android.Manifest.permission.CAMERA<br>    )<br><br>    when (cameraPermissionState.status) {<br>        // If the camera permission is granted, then show screen with the feature enabled<br>        PermissionStatus.Granted -&gt; {<br>            Text(&quot;Camera permission Granted&quot;)<br>        }<br>        is PermissionStatus.Denied -&gt; {<br>            Column {<br>                val textToShow = if (cameraPermissionState.status.shouldShowRationale) {<br>                    // If the user has denied the permission but the rationale can be shown,<br>                    // then gently explain why the app requires this permission<br>                    &quot;The camera is important for this app. Please grant the permission.&quot;<br>                } else {<br>                    // If it&#39;s the first time the user lands on this feature, or the user<br>                    // doesn&#39;t want to be asked again for this permission, explain that the<br>                    // permission is required<br>                    &quot;Camera permission required for this feature to be available. &quot; +<br>                        &quot;Please grant the permission&quot;<br>                }<br>                Text(textToShow)<br>                Button(onClick = { cameraPermissionState.launchPermissionRequest() }) {<br>                    Text(&quot;Request permission&quot;)<br>                }<br>            }<br>        }<br>    }<br>} </pre><p>Let me explain important lines of code.</p><p><strong>rememberPermissionState: </strong>As you can see this line is the definition for asking the user for permission or checking if this permission has already been taken. In this example we are asking for CAMERA permission</p><p><strong>cameraPermissionState.status: </strong>This line will check whether the user has given permission or not. When status value is PermissionStatus.Granted it means the user has permitted to our application. PermissionStatus.Denied means that the user hasn’t given permission. You need to open the permission popup.</p><p><strong>cameraPermissionState.launchPermissionRequest(): </strong>This line when you click the button will open a popup that the user can allow permission or deny.</p><h4>Warnings</h4><p>1-The permission compose elements are currently experimental and they could change at any time. All of the permission compose elements are marked with the @ExperimentalPermissionsApi annotation.</p><p>2- You need to add uses-permission to your AndroidManifest.xml file. If you don’t add uses-permission, when you click request the permission button you can’t see the popup.</p><p>When you run your application you will see this gif</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*N8qa4N0cJYMw_GuDND1dow.gif" /></figure><p>For the next step, I have written an application that has been requested multiple permission like CAMERA and WRITE STORAGE. You can find the full code below</p><pre>@Composable<br>@ExperimentalPermissionsApi<br>private fun FeatureThatRequiresPermissions() {<br><br>    <em>Column</em>() <strong>{<br><br>        </strong>// Camera permission state<br>        val cameraPermissionState = <em>rememberPermissionState</em>(<br>            Manifest.permission.<em>CAMERA<br>        </em>)<br><br>        //Write -Read Permission<br>        val multiplePermissionsState = <em>rememberMultiplePermissionsState</em>(<br>            permissions = <em>listOf</em>(<br>                Manifest.permission.<em>WRITE_EXTERNAL_STORAGE</em>,<br>                Manifest.permission.<em>READ_EXTERNAL_STORAGE<br>            </em>)<br>        )<br><br>        multiplePermissionsState.permissions.<em>forEach </em><strong>{ </strong>perm <strong>-&gt;<br>            </strong>when (perm.permission) {<br>                Manifest.permission.<em>WRITE_EXTERNAL_STORAGE </em>-&gt; {<br>                    <em>getPermission</em>(perm, &quot;Write Permission&quot;)<br>                }<br>                Manifest.permission.<em>READ_EXTERNAL_STORAGE </em>-&gt; {<br>                    <em>getPermission</em>(perm, &quot;Read Permission&quot;)<br>                }<br>            }<br>        <strong>}<br><br>        </strong><em>getPermission</em>(perm = cameraPermissionState, permissionText = &quot;Camera Permission&quot;)<br>    <strong>}<br><br></strong>}<br><br>@ExperimentalPermissionsApi<br>@Composable<br>private fun getPermission(<br>    perm: PermissionState,<br>    permissionText: String<br>) {<br>    when (perm.status) {<br>        is PermissionStatus.Granted -&gt; {<br>            <em>Text</em>(&quot;$permissionText permission Granted&quot;)<br>        }<br>        is PermissionStatus.Denied -&gt; {<br>            <em>Column </em><strong>{<br>                </strong>val textToShow = if (perm.status.<em>shouldShowRationale</em>) {<br>                    &quot;The $permissionText is important for this app. Please grant the permission.&quot;<br>                } else {<br>                    &quot;The $permissionText required for this feature to be available. &quot; +<br>                            &quot;Please grant the permission&quot;<br>                }<br>                <em>Text</em>(textToShow)<br>                <em>Button</em>(onClick = <strong>{ </strong>perm.launchPermissionRequest() <strong>}</strong>) <strong>{<br>                    </strong><em>Text</em>(&quot;Request $permissionText&quot;)<br>                <strong>}<br>            }<br>        </strong>}<br>    }<br>}</pre><p>We have completed permission article you can find full code in<strong> </strong><a href="https://github.com/durdufatih/accompanist-permision"><strong>github profile</strong></a></p><p>We will see you in next android article. <strong>Stay with android </strong>:)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8500c36362e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kanseri Yenmek]]></title>
            <link>https://medium.com/@mfdurdu/kanseri-yenmek-257e1e60f821?source=rss-891bf1062407------2</link>
            <guid isPermaLink="false">https://medium.com/p/257e1e60f821</guid>
            <category><![CDATA[savaş]]></category>
            <category><![CDATA[türkçe]]></category>
            <category><![CDATA[kanser]]></category>
            <category><![CDATA[kanser-tedavisi]]></category>
            <dc:creator><![CDATA[Mehmet Fatih Durdu]]></dc:creator>
            <pubDate>Tue, 15 Mar 2022 13:15:59 GMT</pubDate>
            <atom:updated>2022-03-15T13:16:51.010Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*M3PFpXXhXUFMO4lp" /><figcaption>Photo by <a href="https://unsplash.com/@nci?utm_source=medium&amp;utm_medium=referral">National Cancer Institute</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Merhaba dostlar çağın en korkulan hastalıklarından birine yakalanınca ne ile karşı karşıyasınız bunu bu yazıda anlamak istedim. Amacım kanser nedir? Neden ortaya çıkar ? gibi soruların cevabını vermek değildir. Sadece bu dönemde ne ile yüzleşilir bunu anlatmak istedim.</p><p>Öncelikle bu yazıda benim tecrübelerimdir. Her kanser türünün tedavisi kişide bıraktığı etkiler farklılıklar gösterebilir. Genel olarak süreçten bahsetmeye çalışacağım.</p><h3><strong>TESPİT</strong></h3><p>İlk olarak nasıl tespit edildiğini konuşmak daha doğru olacaktır.Geçirdiğim bir ameliyat sonrasında vucüdumdan bir parça alındı bu parça patolojiye gidiyor bunu inceleniyor. Patoloji yaklaşık olarak 2 hafta ile 1 ay gibi bir süre içinde sonuçlanıyor. Bu patoloji sonucunu beklerken birde BT denilen ilaçlı tomografi çekiliyor. Bu da vücüdunuzda kanser belirtisi gösteren bir hücre var mı onu tespit ediyor. Patoloji sonucu ve BT sonucunda doktorlar kanser hücresi olup olmadığına karar veriyorlar. Bu noktada son bir çekim olan PED testine giriliyor. PED testi vücudun tamamında kanserli hücrelerin boyutuna kadar veriyor. Tespit aşaması sonlanmış oluyor.</p><h3>DOKTOR VE HASTANE</h3><p>Tespitten sonra bence en önemli olan nokta doktor seçimi. Doktor seçerken şu konulara dikkat ettim doktora güven duyun ve tebessüm eden bir doktorun tedavisine izin verin. Çünkü tedavi boyunca enerjik olan doktor düştüğünüz anda sizi yükseltecektir. Her hastaneye gittiğinizde sizinde yanınızda oldğunuz hissettiğiniz siz iyileştiğinizde mutlu olacağını hisettiğiniz doktor herzaman iyi seçimdir.</p><p>Hastane içinse aynı durumlar geçerlidir. Eğer size enerji vermeyen bir çalışan ile karşılaşıyorsanız. Hemşireler genellikle çok fazla enerjik oluyorlar bunun dışında bir durumla karşılaşırsanız bir kaç kez izleyip genel bir tavır mı onu algılamaya çalışın ve gerekiyorsa başka hastanede destek alın. Ek olarak kemoterapi yogun bir tedavi olduğu için İstanbul gibi bir şehirde yaşıyorsanız evinize yakın olan hastaneyi tercih etmeye çalışın. Bazı günler sizi çok yoracaktır. Trafikte sizi zorlamasın.</p><h3>KABULLENİŞ</h3><p>İlk hastalığa yakalandığınızda bir kabullenme süreci yaşadım. Öncelikle bu hastalığı kabullenmek gerekiyor . Kabullenmeyince savaştığınız karşınıza aldığınız şeyin ne olduğunu adresleyemiyorsunuz. Savaştığınız şeyin net olması durumunda kafanızda bazı belirsizliklerin kalktığını göreceksiniz. Böylece vücüdunuz ve beyniniz aynı şey ile savaşıyor. Beyin farklı bir savaş içinde olursa bu süreç tabikide zor olacaktır. Hatta kabullenmeyi yaşadıktan sonra saçlarım dökülmeden gidip saçlarımı sıfıra ben vurdurdum :)</p><h3>İNSANLARIN TAVIRLARI</h3><p>İnsanlar size daha fazla ilgi gösterecektir bazı noktalarda size çok yardımcı olmaya çalışacaklardır. Hastalıktan önce ben bireysel yaşayan kendi işimi kendim yapmaya calışan bir bireydim. Fakat hastalığı kabullendikten sonra insanların bana yardımcı olaması için fazlaca izin verme kararı aldım. Bu savaşı tek başıma kazanamayacağım belliydi. Kensinlikle sevdiğiniz insanları kırmayın onlar sizden daha fazla yıpranıyorlar.</p><h3>TEDAVİ AŞAMASI</h3><p>Kişini yaşına,cinsiyetine, kanser hücresinin büyüklüğüne vb etmenlere göre tedavi şekli değişiklik gösterebilmektedir. Benim tedavimde 5 gün yogun kemoterapi ilaçlarını aldıktan 1 hafta sonra bir ilaç daha alıyordum Bir sonraki hafta yine 1 ilaç alıyordum sonrasında 2 hafta dinlenme oluyordu. Bunu 4 seans olarak gerçekleştirdik. İlk seanslarda çok fazla etkisini görmedim. Açıkcası kemoterapi nedir bilmiyordum. Tedaviye başlayınca Serum gibi damardan verilen bir ilaç olduğunu gördüm. Kansere yakalanmasan kemoterapinin böyle ameliyat tarzı bir tedavi olduğunu düşünecektim :) İkinci seanstan sonra tedavi beni çok fazla yormaya başlamıştı. Bazı günler ilacı aldıktan sonra baygın bir şekilde yatıyordum. Kesinlikle normal olan şeyler ,bunlara hazırlıklı olmak gerekiyor. Tedavi süresince hemşirelerle , çevredeki hastalarla iletişim kurun herkesin ortak gayesi bu hastalığı yenmek. Bu iletişim sayesinde daha güçlü hissedebilirsiniz. Modunuzu düşüren birisi varsa onu dinyelip onun derdi ile dertlenmeyin uzak durun. İlk başta alışkın olmadığınızdan öylece gidiyorsunuz. Tavsiyem yanınızda bir kulaklık ,tablet,kitap veya bilgisayar olması tedavi süresi 4 saati bulabiliyor. Zaman geçirmek adına bunlar önemli olabiliyor.</p><p>Tabiki bazı günler bunları yapmak için enerjiniz olmayabilir. Ben hep uyuyarak bu tedaviyi tamamlıyordum :) Bir abimiz tabletsiz gelmiyordu. Herkese kendi tercih ettiği müzikleri dinletiyordu :) Tedavi sürecinde her aradan sonra sizden kan alıyorlar kanda bazı değerler uygun olmayınca tedaviyi ona göre şekillendirebiliyorlar. Ben tedavi sürecinde ilk kan aldıklarında acaba bende sorun mu var diye düşünmüştüm. Tedavim kötü mü gidiyor diye düşünmüştüm. Bu düşüncelere takılmamak gerekiyor. Elzem bir durum olursa doktorunuz size herseyi açık şekilde aktarıyor.</p><h3>DİKKAT EDİLMESİ GEREKEN ŞEYLER</h3><p>Kesinlikle insanların size acıyarak bakmasını engellemek adına güçlü gözükün. Kötü bile olsanız güçlü durun bu yakınlarınıza da güç ve moral verir. Bol sıvı tüketin. Baya 3–4 litre civarında sıvı tüketin. Tedavi ilerleyince mide bulantısı olacaktır. Korkmayın su midenizi bulandırıyorsa ayran için Vücudunuzu iyi tanıyın fakrlılıkların hepsini doktora yazın veya arayıp haber edin. Kafanızı tedaviye çok takmamak adına hobilerle kendinizi meşgul edin. Sonun iyi olacağını düşünüp sona odaklanın geri kalan hersey detay oluyor. Kemoterapi sürecinde pandemi olduğu için insanlarla gerekirse online görüşün. Misafir gelmesi sizin hayatınızı tehlikeye atabilir.</p><h3>UZAK DURULMASI GEREKEN ŞEYLER</h3><p>Negatif insanlar <br>Acıyarak bakan insanlar. <br>Tek düzen beslenme <br>Uykusuzluk. <br>Gündelik insan ilişki problemleri <br>Geleceğe dair endişeler.</p><h3>SON</h3><p>Yaz çok fazla detay aklıma geldi. Kesinlikle bu bir deneyimdir. Hiç kimsenin yaşamayacağı bir deneyimdir. Sizi daha güçlü kılacağı bir deneyimdir. Çok fazla uzadığının farkındayım. Umarım faydalı olmuştur. Bu süreçte destekçim olan eşime <a href="https://twitter.com/handenurrr">@handenurrr</a> ‘e sonsuz minnettarım.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=257e1e60f821" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>