<?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 Eyup Harun Selek on Medium]]></title>
        <description><![CDATA[Stories by Eyup Harun Selek on Medium]]></description>
        <link>https://medium.com/@harunselek?source=rss-86228bbbcce9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*V01XO4UUpitSfPvirHRqiw@2x.jpeg</url>
            <title>Stories by Eyup Harun Selek on Medium</title>
            <link>https://medium.com/@harunselek?source=rss-86228bbbcce9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 07:51:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@harunselek/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[Polymorphism in Swift]]></title>
            <link>https://medium.com/@harunselek/what-is-polymorphism-d74c0dbd23?source=rss-86228bbbcce9------2</link>
            <guid isPermaLink="false">https://medium.com/p/d74c0dbd23</guid>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[xcode]]></category>
            <category><![CDATA[polymorphism]]></category>
            <dc:creator><![CDATA[Eyup Harun Selek]]></dc:creator>
            <pubDate>Sun, 31 Jul 2022 10:18:01 GMT</pubDate>
            <atom:updated>2022-09-11T06:18:49.060Z</atom:updated>
            <content:encoded><![CDATA[<p>Let’s start with the dictionary definition of polymorphism, which is “the condition of occurring in several different forms”. So, what does this mean?</p><p>For example, in life, we have different professions where we use the same verb for explaining what the people who work at those professions do. One such word is the verb “write”. But, although we use the same verb for these professions they do the task differently. For example, a person might be a programmer who writes code or a person can be a poet who writes poems. If we implement the difference between a programmer who is writing code and a poet who is writing a poem, then, if we simply tell them to write they would write without requiring any additional instructions.</p><p>Let’s take the example of being a programmer, and a poet and form the following classes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yPh0jhvxVK1okwzdsMIM-Q.png" /></figure><p>We have a function called write in the Person class but the subclasses Programmer and Poet override it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jy97qzY2NUVCNuvIhryfGA.png" /></figure><p>We are putting Harold, Samantha and John in the people array and the compiler is OK with that despite their class difference because they both inherit from the Person class. They also know how to write according to their profession.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/404/1*ZuONJdTvXiZTwYgHkZzX-g.png" /></figure><p>While they are in the people array together, they still retain their original class and thus, when we ask them to write we can have the following output.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pWkwrXWBGCAOJCbGxqRK0g.png" /></figure><p>This is called polymorphism. To sum it up, in polymorphism, the objects can both work as their own class and their parent class. In the example above we have the Programmer class and the Poet class. Harold, Samantha and John objects can live happily together in the people array because people array is of Person class which, both the Programmer and Poet classes inherit from. Despite being together in the people array, they do not forget how to write correctly because they still know their original classes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d74c0dbd23" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Get Out of the Tutorial Hell?]]></title>
            <link>https://medium.com/@harunselek/how-to-get-out-of-the-tutorial-hell-2994fa0c724b?source=rss-86228bbbcce9------2</link>
            <guid isPermaLink="false">https://medium.com/p/2994fa0c724b</guid>
            <category><![CDATA[course]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[tutorial]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[trap]]></category>
            <dc:creator><![CDATA[Eyup Harun Selek]]></dc:creator>
            <pubDate>Sat, 18 Apr 2020 19:34:28 GMT</pubDate>
            <atom:updated>2020-04-18T19:34:28.220Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T0s-Mxn92PkYc2cV4aCZeg.jpeg" /><figcaption>Tutorials are great, but avoid getting trapped.</figcaption></figure><p>Tutorials are great. They teach us to do things beyond our current competence level. We also love watching or reading them for another reason… Our brain produces a similar dopamine reward as if we are actually building the thing. The downside? Even if you code along while watching the tutorial, you are still not producing anything new. So the tutorial trap, aka tutorial hell, is a real problem.</p><p>Okay, so what should you do? You need to balance watching tutorials and building new projects with what you have learnt. Stop thinking that there is a better way, just start practicing as soon as possible.</p><p><strong>Personalize the example given in the tutorial</strong></p><p>Although it seems safe to copy the exact example that the tutorial shows you, if you just get the gist from the tutorial and modify the given example, you might learn a lot more. For example, let’s say the tutorial wants you to build an egg timer. Do not do exactly what the tutorial shows you. Make changes like adding different timer values for boiling the eggs… Like a different timer value for hard boiled eggs and soft boiled eggs. You can even really take some eggs, boil them, take pictures of the results and use them in your app. Say boil an egg for 6 minutes and take a picture showing how it is and use it in your app, boil an egg for 8 minutes and show how it is, boil it for 10 minutes and show how it is. Remember, we learn by doing…</p><p><strong>If something is too easy to do, it probably is not worth doing it</strong></p><p>There is a famous hypothesis which is called the Input Hypothesis. It is put forward by Stephen Krashen. It is an hypothesis valid for second language acquisition but I believe it is also valid in computer science, as well as many other areas of life. According to the hypothesis, if “i” is the language learner’s current level of competence in the foreign language, then “i + 1” is the next immediate step along the development continuum. Therefore, in order to make progress, a learner should always be provided with “<em>comprehensible input</em>“, which is “i + 1”. In short, in order to be successful in your learning journey, you should always be looking for that “i+1” and avoid repeating the same “i” again and again while also avoiding getting ahead of yourself.</p><p>If you want to learn programming, ideally once you finish a comprehensive tutorial on the subject that you want to learn, you need to start actually building something and spend less time on watching tutorial after tutorial. Start experimenting with your newly acquired knowledge and try to find new places to use it. You will certainly run into problems. In time you will see that, it is solving those problems that will teach you the most.</p><p>When do you know that you know enough about a subject? There is no clear answer to this but if you find yourself watching another tutorial and see that it is repeating the same concepts that you already know, the idea is that you now know enough to get your hands dirty.</p><p>So go ahead and start building that project of yours. You will learn a lot in the progress.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2994fa0c724b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>