<?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 Fatih Eren Özçelik on Medium]]></title>
        <description><![CDATA[Stories by Fatih Eren Özçelik on Medium]]></description>
        <link>https://medium.com/@erenoz?source=rss-41487115d0a7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*FfbIAZRngg_NodwPz055SQ.jpeg</url>
            <title>Stories by Fatih Eren Özçelik on Medium</title>
            <link>https://medium.com/@erenoz?source=rss-41487115d0a7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:04:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@erenoz/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[Why Journaling Matters More Than Ever]]></title>
            <link>https://erenoz.medium.com/why-journaling-matters-more-than-ever-8b26558e2d25?source=rss-41487115d0a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b26558e2d25</guid>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[journaling]]></category>
            <dc:creator><![CDATA[Fatih Eren Özçelik]]></dc:creator>
            <pubDate>Sat, 03 Oct 2026 08:58:11 GMT</pubDate>
            <atom:updated>2026-10-03T08:58:11.848Z</atom:updated>
            <content:encoded><![CDATA[<h4>Writing things down in an age of reels and AI</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YfQoxQJfdOcAV5zNlQJPrg.png" /></figure><p>We scroll through dozens of short videos before breakfast. We ask AI to write our emails, summarize our meetings, and plan our trips. Our phones remember our passwords, our calendars, and our photos. Most of the time this feels like progress, and in many ways it is.</p><p>But there is a quiet question behind all of this: <strong>if we hand most of our thinking and remembering over to tools, what happens to the brain that used to do that work?</strong></p><p>I think one of the oldest and simplest habits we have may help: <strong>writing a journal every day</strong>. Let’s look at why.</p><h3>1. What Reels and AI Might Be Doing to Our Heads</h3><p><strong>Short videos.</strong> Researchers at LMU Munich gave 60 people something to remember, then let them spend a break on TikTok, Twitter, YouTube, or just rest. Only the TikTok group got noticeably worse at remembering and carrying out what they had planned. The researchers think the nonstop switching between topics is the reason. It’s a small study, so I see it as a hint, not a verdict. Still, many of us probably know the feeling of “wait, what was I about to do?” after a long scroll.</p><p><strong>Thinking with AI.</strong> Search engines stored our facts. Now AI can do the <em>thinking</em> part too: structuring an argument, choosing words, drawing conclusions. A team at MIT Media Lab looked at what that does. They recorded the brain activity of people writing essays in three groups: with ChatGPT, with a search engine, or with no tools at all.</p><p>The ChatGPT group showed the weakest brain connectivity, the search engine group was in the middle, and the no-tools group showed the strongest. And right after writing, <strong>83% of the ChatGPT group couldn’t quote a single sentence from their own essay</strong>, compared to around 11% in the other groups. The researchers call this <strong>“cognitive debt”</strong>: the convenience you get today may cost you later.</p><p>One honest note: this study is a preprint with a small group of people, so it’s an early signal, not the last word.</p><p>I use AI every day, in my work and in my life. This is not an argument against these tools. But I think it’s a good reminder: <strong>if we stop exercising a skill, we should expect to lose some of it.</strong></p><h3>2. Why I Think Journaling Helps</h3><p>My take: journaling pushes back on both of these. It makes you <strong>slow down</strong>, <strong>recall your day from your own memory</strong>, and <strong>put your thoughts into your own words</strong>.</p><p>Science has been looking at writing about your feelings for decades. Psychologist James Pennebaker started it in the 1980s: write about your thoughts and feelings for 15–20 minutes, for a few days. When a researcher later combined <strong>146 studies</strong>, the result was a small but real positive effect on average, for health and wellbeing. It’s small, and it varies from study to study, so it’s not magic. But for a free habit, I think it’s worth knowing about.</p><p>Another study (Klein &amp; Boals, 2001) found that students who wrote about a stressful or emotional experience showed better <strong>working memory</strong> weeks later, compared to students who wrote about trivial topics. Working memory is your brain’s “RAM”: what you use to hold things in mind right now, and stress eats it up. <strong>Their explanation is that writing it out helps you process it, so your mind stops running it in the background.</strong></p><h3>3. How to Start</h3><p>Most people who try journaling stop within a few weeks, usually because the habit feels too heavy. So keep it light:</p><ul><li><strong>Keep it small.</strong> Five minutes and a few sentences are enough. No rules on format, grammar, or spelling.</li><li><strong>Write it yourself.</strong> The value comes from recalling your day in your own words. If AI writes your journal, you skip exactly the part that helps.</li><li><strong>Make it a ritual.</strong> Same time, same place, every day. And when the page stays blank, ask yourself: “What happened today that I want to remember?”</li></ul><h3>4. Where to Write</h3><p>The best journaling tool is the one that’s <strong>within reach when you have something to write</strong>. A notebook is lovely, but it’s rarely with you on the bus home or in bed before sleep. Your phone is.</p><p>The same device that pulls our attention away can also be the easiest place to write, if the app is built for that. It should open fast and let you start writing right away. It should keep your entries private. It should gently remind you in the evening, and every now and then show you what you wrote exactly one year ago.</p><p><strong>The goal of a journaling app is not to keep you on your phone. It’s to help you spend a few minutes with your own thoughts, then let you go.</strong></p><p>That’s exactly what I’ve been building: an iOS journaling app designed around these ideas. I’ll be sharing it here soon. <strong>Follow me if you’d like to be among the first to try it.</strong></p><h3>Final Thoughts</h3><p>We’re not going to stop watching videos or using AI, and we don’t have to. But we can balance them with a few minutes a day where <strong>our own brain does the work</strong>: remembering, reflecting, and writing.</p><h3>Sources</h3><p>If you’d like to read the studies yourself:</p><ul><li>LMU Munich short-video study: Chiossi et al. (2023), <em>Short-Form Videos Degrade Our Capacity to Retain Intentions</em>. <a href="https://arxiv.org/abs/2302.03714">https://arxiv.org/abs/2302.03714</a></li><li>MIT Media Lab: Kosmyna et al. (2025), <em>Your Brain on ChatGPT: Accumulation of Cognitive Debt when Using an AI Assistant for Essay Writing Task</em> (preprint). <a href="https://arxiv.org/abs/2506.08872">https://arxiv.org/abs/2506.08872</a></li><li>Expressive writing meta-analysis: Frattaroli (2006), <em>Experimental Disclosure and Its Moderators</em>. Psychological Bulletin, 132(6), 823–865. <a href="https://doi.org/10.1037/0033-2909.132.6.823">https://doi.org/10.1037/0033-2909.132.6.823</a></li><li>Working memory study: Klein &amp; Boals (2001), <em>Expressive Writing Can Increase Working Memory Capacity</em>. Journal of Experimental Psychology: General, 130(3), 520–533. <a href="https://pubmed.ncbi.nlm.nih.gov/11561925/">https://pubmed.ncbi.nlm.nih.gov/11561925/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b26558e2d25" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Testing in Modern Software Development]]></title>
            <link>https://erenoz.medium.com/testing-in-modern-software-development-7a179ffae949?source=rss-41487115d0a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a179ffae949</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[unit-testing]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[stub]]></category>
            <dc:creator><![CDATA[Fatih Eren Özçelik]]></dc:creator>
            <pubDate>Wed, 01 Apr 2026 17:10:42 GMT</pubDate>
            <atom:updated>2026-04-01T17:16:45.178Z</atom:updated>
            <content:encoded><![CDATA[<h4>Principles, Practices, and the Role of AI in Building Reliable and Maintainable Systems</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F8HcoIb0ka1P-0re4cQPJQ.png" /></figure><h3>Introduction</h3><p>This article outlines software testing as a core engineering practice, from fundamental principles to advanced strategies for large-scale systems.</p><p>1- Importance of Software Testing<br>2- Unit Testing<br>3- Principles of Writing Tests<br>4- Test Isolation and Mocking<br>5- AI-Assisted Test Writing<br>6- Large Domain Models &amp; Test Data Strategy</p><h3>1. Importance of Software Testing</h3><p>In modern software development processes, writing tests has evolved beyond being merely a tool for detecting bugs; it has become a fundamental engineering practice that directly determines software quality. Especially when considering the development of complex systems, rapid release cycles, and continuous integration processes, testing plays a critical role in ensuring the sustainability of software.</p><h4>1.1 About Software Quality</h4><p>Software quality is the sum of criteria such as a system’s ability to correctly fulfill its expected functions, remain free of defects, be easy to maintain, and meet user expectations.</p><p>The core characteristics of high quality software include:<br>- Correctness<br>- Reliability<br>- Maintainability<br>- Performance<br>- Usability</p><p>Tests make these characteristics verifiable, turning software quality into something measurable and controllable. In particular, unit tests help ensure that different parts of the system function correctly and work as expected.</p><h4>1.2 Bug Cost (Early vs Late Detection)</h4><p>In the software development lifecycle, the point at which a bug is detected has a direct impact on its cost. A widely accepted principle states:</p><p><strong>The later a bug is found, the more expensive it becomes to fix.</strong></p><p><strong>Early Stage (Development Phase)<br>- </strong>Lower cost of fixing the bug<br>- The developer still remembers the context<br>- Limited impact scope</p><p><strong>Late Stage (Production)<br>- </strong>Affects end users<br>- Requires hotfixes<br>- May lead to reputational damage<br>- Introduces additional testing and deployment costs</p><p>By writing tests, bugs can be caught early during the development phase, significantly reducing these costs. Automated tests, in particular, run with every code change, helping detect issues as early as possible.</p><h4>1.3 Regression Risk</h4><p>Regression occurs when a feature that previously worked correctly breaks after changes are made to the system.</p><p>This risk increases especially after:<br>- Refactoring<br>- Adding new features<br>- Fixing bugs</p><p>One of the most important contributions of testing is minimizing this risk. Existing tests verify whether the system still preserves its previous behavior. This way, issues are caught before they reach production, significantly reducing both the cost and impact of potential bugs.</p><h4>1.4 Contributions of Testing to the Software Development Process</h4><h4>1.4.1 Reducing Maintenance Cost</h4><p>Tests create a safety net that verifies how the code behaves. As a result:<br>- New developers can understand the system more quickly<br>- The risk of making changes is reduced<br>- Debugging time for errors is shortened</p><h4>1.4.2 Ensuring Refactoring Safety</h4><p>During refactoring, one of the biggest concerns for developers is:<br> <strong>“Am I breaking something?”</strong></p><p>Tests provide a clear answer to this question:<br>- Tests are executed after every refactoring<br>- If all tests pass, the system’s behavior is preserved</p><p>This enables developers to write cleaner code with greater confidence.</p><h4>1.4.3 Acting as Documentation</h4><p>Well-written tests serve as living documentation that demonstrates how the code behaves.</p><p><strong>Example:</strong></p><pre>func test_appliesExtraFee_whenTotalWeightExceedsLimit()</pre><p>It <strong>clearly expresses</strong> the following behavior: there is a defined weight limit, and if the total weight exceeds that limit, the system should apply an extra fee when performing the relevant check.<br>Hence:<br>- The expected behavior of the code is clearly visible<br>- The need for additional documentation is reduced</p><h3>2. Unit Testing</h3><p>(While there are various types of testing such as Integration, UI, Snapshot, End-to-End, and Smoke tests, this article focuses primarily on unit testing.)</p><p><strong>Unit tests test the smallest testable parts of a software (usually functions or classes) in isolation.</strong></p><p><strong>Purpose<br></strong>- To verify the correctness of business logic<br>- To validate small and independent components</p><p><strong>Characteristics<br>- </strong>Fast execution<br>- External dependencies are mocked<br>- Deterministic (always produces the same result)</p><p><strong>Examples<br>- </strong>A fee calculation function<br>- A data mapper<br>- A ViewModel state change</p><p><strong>Advantages<br>- </strong>Provides fast feedback<br>- Makes it easier to identify the source of errors<br>- Ensures safety during refactoring</p><h4>What Unit Testing Is Not?</h4><p>A unit test:<br>❌ Does not make network calls<br>❌ Does not use a real database<br>❌ Does not test UI rendering<br>❌ <strong>Does not test whether the programming language itself works correctly</strong><br>❌ Should not depend on timing or async race conditions</p><pre>// This example tests Swift&#39;s Array behavior<br>// Does not validate any business logic<br>// Provides no real value<br><br>let items = [1, 2, 3]<br><br>func test_arrayIsEmpty() {<br>    let items: [Int] = []<br>    XCTAssertTrue(items.isEmpty)<br>}</pre><h3>3. Principles of Writing Tests</h3><p>Writing tests is not limited to knowing different test types. To create effective and maintainable tests, certain principles must be followed. These principles directly impact the readability, reliability, and long-term maintainability of tests.</p><h4>3.1 FIRST Principles</h4><p>A good test should have the following characteristics:</p><h4><strong>Fast</strong></h4><p>- Tests should run quickly<br>- Slow tests break the developer feedback loop<br>- Network and database should not be used</p><h4><strong>Independent</strong></h4><p><strong>- </strong>Tests should not depend on each other<br>- The result of one test should not affect another<br>- Each test sets up its own environment</p><h4><strong>Repeatable</strong></h4><p><strong>- </strong>A test should produce the same result every time it runs<br>❌ Date, randomness, network<br>✅ Mocks / fixed data</p><h4><strong>Self-validating</strong></h4><p><strong>- </strong>The result of the test should be automatically verifiable<br>XCTAssertEqual(result, expected)</p><h4><strong>Timely</strong></h4><p><strong>- </strong>Tests should be written as early as possible<br>- This approach also enables Test-Driven Development (TDD)</p><h4>3.2 AAA Pattern (Arrange / Act / Assert)</h4><p>One of the most commonly used structures for improving test readability</p><p><strong>Arrange: </strong>Set up the necessary environment for the test<br><strong>Act: </strong>Perform the action being tested<br><strong>Assert: </strong>Verify the result</p><p><strong>Example</strong></p><pre>func test_appliesExtraFee_whenTotalWeightExceedsLimit() {<br>    // Arrange<br>    let totalWeight = 25<br>    let limit = 20<br>    <br>    // Act<br>    let result = calculator.calculateExtraFee(weight: totalWeight, limit: limit)<br>    <br>    // Assert<br>    XCTAssertTrue(result.hasExtraFee)<br>}</pre><h4>3.3 Test Naming</h4><p>A good test name:<br>- Clearly describes what is being tested<br>- Includes both the scenario and the expected outcome<br>- Serves as documentation when read</p><p>There are multiple valid naming conventions for tests. The key is consistency and clarity.</p><pre>// 1. action_whenCondition_expectedResult<br>func test_calculateFee_whenTotalWeightExceedsLimit_returnsExtraFee()<br><br>// 2. shouldExpectedResult_whenCondition<br>func test_shouldReturnExtraFee_whenTotalWeightExceedsLimit()<br><br>// 3. given_when_then<br>func test_givenWeightExceedsLimit_whenCalculatingFee_thenExtraFeeIsApplied()<br><br>// 4. behavior-focused<br>func test_extraFeeIsApplied_whenTotalWeightExceedsLimit()</pre><p><strong>Avoid using method names in test names. Method names can change during refactoring, but behavior should remain stable.</strong></p><h4>3.4 Single Responsibility</h4><p>Each test should verify only one behavior.</p><pre>// WRONG<br>func test_everything() {<br>    XCTAssertTrue(result.isValid)<br>    XCTAssertEqual(result.count, 3)<br>    XCTAssertNotNil(result.error)<br>}<br><br>// CORRECT<br>func test_returnsValidResult_whenInputIsCorrect() { ... } <br>func test_returnsThreeItems_whenInputIsCorrect() { ... }</pre><h3>4. Test Isolation and Mocking</h3><p>Test isolation is one of the fundamental principles that ensures unit tests are reliable, fast, and deterministic. A test should focus only on the unit under test and must not be affected by external dependencies. This isolation is achieved through mocking techniques.</p><p><strong>Without isolation:<br>- </strong>Tests become slower<br>- Tests become fragile<br>- The source of errors becomes unclear</p><h4>4.2 Dependency Problem</h4><p>When a class directly depends on another concrete class:</p><pre>class ProfileViewModel {<br>    let service = ProfileService()<br>}</pre><p>In this case:<br>- The real service is used during testing<br>- Test isolation is broken</p><h4>4.3 Solution to dependency problem: Dependency Injection (DI)</h4><p>Provide dependencies from the outside:</p><pre>class ProfileViewModel {<br>    private let service: ProfileServiceProtocol<br><br>   init(service: ProfileServiceProtocol) {<br>        self.service = service<br>    }<br>}</pre><p>This allows:<br>- Injecting a mock service instead of a real one<br>- Provides full control over the test environment</p><h4>4.4 Mocking</h4><p>Mocking is the practice of replacing real dependencies with controlled test doubles.</p><h4><strong>Types of Test Doubles</strong></h4><h4><strong>Mock</strong></h4><p>Used to verify behavior. It checks whether a method was called, how many times it was called, and with which parameters. The focus is on interactions rather than returned values.</p><h4><strong>Stub</strong></h4><p>Returns predefined, fixed data. It does not care how it is used; it simply provides the data needed for the test. It is mainly used to isolate the unit from external dependencies.</p><h4><strong>Spy</strong></h4><p>Records interactions during the test. After execution, you verify what happened, such as whether a method was called or which arguments were passed. Instead of defining expectations beforehand, you verify what happened after the test runs.</p><h4><strong>Fake</strong></h4><p>A simplified but working implementation of a real component. It contains actual logic, such as an in-memory database instead of a real one. It is useful when more realistic behavior is needed without full complexity.</p><h4>Test Double Examples</h4><p>Assume we have a NewsletterManager class that depends on an EmailService protocol.</p><pre>protocol EmailService {<br>    func sendWelcomeEmail(to email: String) -&gt; Bool<br>    func getSubscriberCount() -&gt; Int<br>}</pre><h4>Mock</h4><p>A mock verifies whether a function was called and with which parameters.<br><em>Answering questions like: “Was an email actually sent when the user signed up?”</em></p><pre>class EmailServiceMock: EmailService {<br>    var sendEmailCalled = false<br>    var lastRecipient: String?<br><br>    func sendWelcomeEmail(to email: String) -&gt; Bool {<br>        sendEmailCalled = true<br>        lastRecipient = email<br>        return true<br>    }<br><br>    func getSubscriberCount() -&gt; Int {<br>        return 0<br>    }<br>}<br><br>// Test<br>func test_emailIsSent_whenUserSubscribes() {<br>    let mock = EmailServiceMock()<br>    let manager = NewsletterManager(service: mock)<br>    <br>    manager.subscribe(email: &quot;test@apple.com&quot;)<br>    <br>    XCTAssertTrue(mock.sendEmailCalled)<br>    XCTAssertEqual(mock.lastRecipient, &quot;test@apple.com&quot;)<br>}</pre><h4>Stub</h4><p>A stub provides the data required for the test to proceed. For example, getSubscriberCount might normally call an API, but in tests we want a fixed, predictable value.<br><em>Testing logic like: “If subscriber count is less than 100, show a warning.”</em></p><pre>class EmailServiceStub: EmailService {<br>    func getSubscriberCount() -&gt; Int {<br>        return 99<br>    }<br>    <br>    func sendWelcomeEmail(to email: String) -&gt; Bool {<br>        return true<br>    }<br>}<br><br>func test_shouldShowWarning_whenSubscribersAreUnderLimit() {<br>    // Arrange<br>    let stub = EmailServiceStub() // This stub always returns 99<br>    let sut = NewsletterManager(service: stub)<br>    <br>    // Act<br>    // Inside this call, sut calls service.getSubscriberCount() which returns 99<br>    let isWarningVisible = sut.shouldShowWarning()<br>    <br>    // Assert<br>    XCTAssertTrue(isWarningVisible)<br>}</pre><h4>Spy</h4><p>A spy is similar to a mock but focuses on recording interactions. It can track how many times a method was called and with which data.<br><em>Verifying scenarios like: “Was an email sent to 5 different users in a loop?”</em></p><pre>class EmailServiceSpy: EmailService {<br>    var callCount = 0<br>    var emailsSent: [String] = []<br><br>    func sendWelcomeEmail(to email: String) -&gt; Bool {<br>        callCount += 1<br>        emailsSent.append(email)<br>        return true<br>    }<br><br>    func getSubscriberCount() -&gt; Int {<br>        return 0<br>    }<br>}<br><br>func test_sendBulkUpdate_shouldCallServiceForEveryEmail() {<br>    // Arrange<br>    let spy = EmailServiceSpy()<br>    let sut = NewsletterManager(service: spy)<br>    let recipients = [&quot;alpha@test.com&quot;, &quot;beta@test.com&quot;]<br><br>    // Act<br>    sut.sendBulkUpdate(to: recipients)<br><br>    // Assert<br>    XCTAssertEqual(spy.callCount, 2)<br>    XCTAssertEqual(spy.emailsSent, recipients)<br>}</pre><h4>Fake</h4><p>A fake is a lightweight version of a real implementation. For example, instead of using a real database, it uses an in-memory structure.</p><pre>class FakeEmailDatabase: EmailService {<br>    private var subscribers = [&quot;test@mail.com&quot;]<br><br>    func getSubscriberCount() -&gt; Int {<br>        return subscribers.count<br>    }<br><br>    func sendWelcomeEmail(to email: String) -&gt; Bool {<br>        subscribers.append(email)<br>        return true<br>    }<br>}<br><br>func test_registerUser_persistsUserInDatabase() {<br>    // Arrange<br>    let fakeDB = FakeEmailDatabase()<br>    let sut = NewsletterManager(service: fakeDB)<br>    let initialCount = fakeDB.getSubscriberCount()<br><br>    // Act<br>    sut.registerUser(email: &quot;new_user@swift.org&quot;)<br><br>    // Assert<br>    let currentCount = fakeDB.getSubscriberCount()<br>    XCTAssertEqual(currentCount, initialCount + 1, &quot;The fake database did not persist the new user.&quot;)<br>}</pre><h4>Which One Should You Use?</h4><p><strong>Use Stub</strong> → when you only need controlled data<br><strong>Use Mock</strong> → when you want to verify interactions<br><strong>Use Spy</strong> → when you want to track calls and their details<br><strong>Use Fake</strong> → when you need a working but simplified implementation</p><h3>5. AI-Assisted Test Writing</h3><p>AI powered tools are increasingly used in software development and provide significant advantages, especially in test writing. These tools help developers move faster by generating test scenarios, identifying edge cases and improving existing tests.</p><h4>5.1 Role of AI in Test Writing</h4><p>AI analyzes the code written by the developer and can<br>- Suggest test scenarios<br>- Generate test codes<br>- Identify missing edge cases<br>- Improve test coverage</p><h4>5.2 Advantages</h4><p><strong>Speed: </strong>Significantly reduces the time required to write tests<br><strong>Increased Coverage: </strong>Can identify scenarios developers might overlook<br><strong>Learning Support: </strong>Acts as a guide for junior developers</p><h4>5.3 Disadvantages and Risks</h4><p>If sufficient context and clear rules are not provided, AI may fail to produce the expected results.</p><ol><li><strong>Incorrect Test Generation<br></strong>AI may misinterpret the code and this can lead to incorrect assertions, missing scenarios and unnecessary tests.</li><li><strong>Lack of Business Context<br></strong> AI often lacks domain knowledge and interprets business rules superficially</li><li><strong>False Confidence<br></strong>The number of tests increases, but actual quality may not improve. Critical logic might remain untested</li><li><strong>Trivial Test Generation<br></strong> AI may generate low quality tests such as:<br>- Getter / setter tests<br>- Framework behavior tests<br>- Scenarios that add no real value</li></ol><h4>Example</h4><pre>// Function<br>func isExtraFeeRequired(weight: Int, limit: Int) -&gt; Bool {<br>    return weight &gt; limit<br>}<br><br>// AI Generated Test (with not sufficient context and rules)<br>func test_isExtraFeeRequired() {<br>    XCTAssertTrue(calculator.isExtraFeeRequired(weight: 25, limit: 20))<br>}<br><br>// Problems with AI generated test:<br>// - Test name is not descriptive<br>// - No edge cases<br>// - No negative scenario<br><br>// --- Improved versions ---<br>func test_extraFeeIsRequired_whenWeightExceedsLimit() {<br>    XCTAssertTrue(calculator.isExtraFeeRequired(weight: 25, limit: 20))<br>}<br><br>func test_extraFeeIsNotRequired_whenWeightIsBelowLimit() {<br>    XCTAssertFalse(calculator.isExtraFeeRequired(weight: 15, limit: 20))<br>}<br><br>func test_extraFeeIsNotRequired_whenWeightEqualsLimit() {<br>    XCTAssertFalse(calculator.isExtraFeeRequired(weight: 20, limit: 20))<br>}</pre><h4>5.6 Using AI for Test Writing</h4><p>To achieve reliable results, AI must be guided with clear instructions such as:<br>- Following a proper structure (e.g., AAA pattern)<br>- Focusing on business logic rather than language or framework behavior<br>- Covering meaningful scenarios, including edge cases</p><h3>6. Large Domain Models &amp; Test Data Strategy</h3><p>In large projects, as domain models grow, test data management becomes a critical bottleneck. The root cause is often the <strong>massive size of the domain models themselves</strong>, which makes mocking or manual stubbing nearly impossible to sustain.</p><p>To solve this, teams often introduce shared builders or shared mother stubs. However, this creates a new problem.</p><p>When these structures are shared:<br>1. A developer modifies them to fit their own test<br>2. Other tests still rely on the same structure<br>3. Those tests start failing due to unintended changes</p><h4>6.1 Solution: Shared Builders &amp; Mother Stubs (Not Recommended)</h4><p>Many teams use a global <strong>Builder Pattern</strong> or <strong>Shared Mother Stubs</strong> to handle complexity. While they offer readability and reusability, they introduce significant risks in large-scale environments:<br><strong>Global Fragility:</strong> A change in a builder’s default value or a shared mother’s property can silently break hundreds of unrelated tests.<br><strong>Maintenance:</strong> Keeping global builders or shared stubs in sync with rapidly evolving models becomes a constant, centralized overhead.<br><strong>Merge Conflicts:</strong> Constant merge conflicts occur as every developer edits the same global files to accommodate their specific test scenarios.</p><h4>6.2 Solution: Specialized “Mother Stub” per Test Class (Recommended)</h4><p>Instead of global builders, you can create a dedicated Mother Stub extension specifically for the test class (or module).</p><h4>Core Principles</h4><p><strong>Isolation:</strong> The stub is local to the test context (file-scoped)<br><strong>Valid Default Data:</strong> It provides a “Happy Path” object with all mandatory fields filled<br><strong>Override by replacing:</strong> Each unit test fetches the mother stub and only replaces the specific fields necessary for that scenario</p><h4>Example</h4><p>You can use a fileprivate extension to create the stub, or you can just keep the test data directly inside the test class:</p><pre>final class FeeCalculatorTests: XCTestCase {<br>    private var calculator: FeeCalculator!<br><br>    override func setUp() {<br>        super.setUp()<br>        calculator = FeeCalculator()<br>    }<br><br>    func test_extraFeeIsRequired_whenWeightExceedsLimit() {<br>        // Arrange<br>        var data = TestData.motherStub // approach 1<br>        // or<br>        var data = TransactionFeeDetail.motherStub // approach 2<br><br>        data.currentWeight = 25<br>        data.weightLimit = 20<br><br>        // Act &amp; Assert<br>        XCTAssertTrue(calculator.isExtraFeeRequired(for: data))<br>    }<br><br>    // MARK: - Approach 1: Local Test Data Model inside the test class<br>    private struct TestData {<br>        static var motherStub: TransactionFeeDetail {<br>            TransactionFeeDetail(<br>                id: &quot;TRX-001&quot;,<br>                amount: 100.0,<br>                currency: &quot;USD&quot;,<br>                weightLimit: 20,<br>                currentWeight: 15,<br>                customerType: .standard,<br>                isPromotionActive: false<br>            )<br>        }<br>    }<br>}<br><br><br>// MARK: - Approach 2: Local Stub Extension<br>// &#39;fileprivate&#39; ensures this stub cannot be accessed from other test classes.<br>fileprivate extension TransactionFeeDetail {<br>    static var motherStub: TransactionFeeDetail {<br>        return TransactionFeeDetail(<br>            id: &quot;TRX-001&quot;,<br>            amount: 100.0,<br>            currency: &quot;USD&quot;,<br>            weightLimit: 20,<br>            currentWeight: 15,<br>            customerType: .standard,<br>            isPromotionActive: false<br>        )<br>    }<br>}</pre><h4>Pros &amp; Cons</h4><p><strong>Pros<br>- Isolation:</strong> A change in one test file never breaks another<br>- <strong>No Merge Conflicts:</strong> No global “Mother” stub means no conflicts<br>- <strong>Locality:</strong> The test logic and its data live in the same place</p><p><strong>Cons<br>- Duplication:</strong> You might have similar stubs repeated across different test files<br>- <strong>Maintainability: </strong>Still hard to maintain if the models changes</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a179ffae949" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Nested Tri-State Checkbox Tree in SwiftUI]]></title>
            <link>https://erenoz.medium.com/building-a-nested-tri-state-checkbox-tree-in-swiftui-0e739536cb15?source=rss-41487115d0a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/0e739536cb15</guid>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[swiftui]]></category>
            <category><![CDATA[ios-development]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Fatih Eren Özçelik]]></dc:creator>
            <pubDate>Wed, 28 Jan 2026 08:16:04 GMT</pubDate>
            <atom:updated>2026-01-29T08:37:58.389Z</atom:updated>
            <content:encoded><![CDATA[<p>A recursive tri-state checkbox tree with synchronized parent-child states</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Th9X_7VcBWo6guu26Z79SA.png" /></figure><p>SwiftUI makes it easy to build lists and forms, but <strong>hierarchical selection with partial states</strong> is still something you need to design yourself. This pattern is common in filters, permission screens, and category pickers — anywhere parent items need to reflect the state of their children.</p><p>In this article, we’ll take look at a <strong>reusable Nested Tri-State Checkbox component</strong> built with SwiftUI.</p><h3>What This Component Supports</h3><p>- Three visual states: checked, unchecked, partial<br>- Infinite nesting via recursion<br>- Expand / collapse behavior per node<br>- Clear separation between UI and selection logic<br>- Fully customizable label content</p><h3>Building Blocks</h3><h4>1. TriCheckboxUIState</h4><p>A simple enum that represents the visual state of a checkbox.</p><pre>public enum TriCheckboxUIState {<br>    case checked<br>    case unchecked<br>    case partial<br>}</pre><h4>2. TriStateCheckbox</h4><p>Visual component that draws the checkbox based on its state.</p><pre>public struct TriStateCheckbox: View {<br>    <br>    let state: TriCheckboxUIState<br>    <br>    public init(state: TriCheckboxUIState) {<br>        self.state = state<br>    }<br>    <br>    public var body: some View {<br>        RoundedRectangle(cornerRadius: 4)<br>            .strokeBorder(borderColor, lineWidth: borderWidth)<br>            .background(<br>                RoundedRectangle(cornerRadius: 4)<br>                    .fill(fillColor)<br>            )<br>            .frame(width: 24, height: 24)<br>            .overlay(alignment: .center) {<br>                switch state {<br>                case .unchecked:<br>                    EmptyView()<br>                case .checked:<br>                    checkMark()<br>                case .partial:<br>                    partialBox()<br>                }<br>            }<br>            .contentShape(Rectangle())<br>    }<br>    <br>    private func checkMark() -&gt; some View {<br>        Image(systemName: &quot;checkmark&quot;)<br>            .renderingMode(.template)<br>            .resizable()<br>            .scaledToFit()<br>            .foregroundStyle(.white)<br>            .frame(width: 14, height: 14)<br>    }<br>    <br>    private func partialBox() -&gt; some View {<br>        RoundedRectangle(cornerRadius: 2)<br>            .fill(Color.blue)<br>            .frame(width: 14, height: 14)<br>    }<br>    <br>    private var borderColor: Color {<br>        switch state {<br>        case .unchecked:<br>            Color.gray<br>        case .checked:<br>            Color.clear<br>        case .partial:<br>            Color.blue<br>        }<br>    }<br>    <br>    private var borderWidth: CGFloat {<br>        switch state {<br>        case .unchecked:<br>            1<br>        case .checked:<br>            0<br>        case .partial:<br>            1<br>        }<br>    }<br>    <br>    private var fillColor: Color {<br>        switch state {<br>        case .unchecked:<br>            Color.clear<br>        case .checked:<br>            Color.blue<br>        case .partial:<br>            Color.clear<br>        }<br>    }<br>}</pre><h4>3. TriStateCheckboxRow</h4><p>A layout wrapper that places custom content on the left, aligns the checkbox on the right and sends checkbox tap events to parent.</p><pre>public struct TriStateCheckboxRow&lt;Content: View&gt;: View {<br>    <br>    let state: TriCheckboxUIState<br>    let content: () -&gt; Content<br>    let onCheckboxTap: (() -&gt; Void)?<br><br>    public init(<br>        state: TriCheckboxUIState,<br>        @ViewBuilder content: @escaping () -&gt; Content,<br>        onCheckboxTap: (() -&gt; Void)?<br>    ) {<br>        self.state = state<br>        self.content = content<br>        self.onCheckboxTap = onCheckboxTap<br>    }<br><br>    public var body: some View {<br>        HStack(spacing: .zero) {<br>            content()<br>            Spacer()<br>            TriStateCheckbox(state: state)<br>                .onTapGesture {<br>                    onCheckboxTap?()<br>                }<br>        }<br>    }<br>}</pre><h4>4. NestedTriStateCheckboxItemUIModel</h4><p>A recursive UI model representing a tree node.</p><pre>public struct NestedTriSateCheckboxItemUIModel: Identifiable {<br>    public let id: String<br>    public let label: String<br>    public let state: TriCheckboxUIState<br>    public let children: [NestedTriSateCheckboxItemUIModel]<br>    <br>    public init(id: String, label: String, state: TriCheckboxUIState, children: [NestedTriSateCheckboxItemUIModel]) {<br>        self.id = id<br>        self.label = label<br>        self.state = state<br>        self.children = children<br>    }<br>    <br>    public var hasChildren: Bool {<br>        !children.isEmpty<br>    }<br>    <br>    public var childrenCount: Int {<br>        children.count<br>    }<br>}</pre><h4>5. NestedTriStateCheckboxView</h4><p>The main view that renders the tree.<br>- Renders a single checkbox row<br>- Expands to show children when needed<br>- Uses itself recursively for child nodes</p><p>Expansion state is stored locally, while selection state is passed in.</p><pre>public struct NestedTriStateCheckboxView&lt;Label: View&gt;: View {<br>    let item: NestedTriSateCheckboxItemUIModel<br>    let level: Int<br>    let labelContent: (_ item: NestedTriSateCheckboxItemUIModel) -&gt; Label<br>    let onToggle: (_ item: NestedTriSateCheckboxItemUIModel) -&gt; Void<br>    <br>    @State private var isExpanded: Bool = false<br>    <br>    public init(<br>        item: NestedTriSateCheckboxItemUIModel,<br>        level: Int,<br>        @ViewBuilder labelContent: @escaping (_ item: NestedTriSateCheckboxItemUIModel) -&gt; Label,<br>        onToggle: @escaping (_ item: NestedTriSateCheckboxItemUIModel) -&gt; Void<br>    ) {<br>        self.item = item<br>        self.level = level<br>        self.labelContent = labelContent<br>        self.onToggle = onToggle<br>    }<br>    <br>    public var body: some View {<br>        VStack(spacing: 16) {<br>            triStateCheckboxRow()<br>            if isExpanded {<br>                childrenRows()<br>            }<br>        }<br>    }<br>    <br>    private func triStateCheckboxRow() -&gt; some View {<br>        TriStateCheckboxRow(<br>            state: item.state,<br>            content: {<br>                itemLabelContainer()<br>            },<br>            onCheckboxTap: {<br>                onToggle(item)<br>            }<br>        )<br>    }<br>    <br>    private func itemLabelContainer() -&gt; some View {<br>        HStack(spacing: 8) {<br>            labelContent(item)<br>            if item.hasChildren {<br>                expandCollapseIcon()<br>            }<br>        }<br>        .contentShape(Rectangle())<br>        .onTapGesture {<br>            if item.hasChildren {<br>                isExpanded.toggle()<br>            }<br>        }<br>    }<br>    <br>    private func expandCollapseIcon() -&gt; some View {<br>        Image(systemName: isExpanded ? &quot;chevron.up&quot; : &quot;chevron.down&quot;)<br>            .renderingMode(.template)<br>            .resizable()<br>            .scaledToFit()<br>            .frame(width: 12, height: 12)<br>            .foregroundStyle(.black)<br>    }<br>    <br>    private func childrenRows() -&gt; some View {<br>        VStack(spacing: 16) {<br>            ForEach(item.children, id: \.id) { child in<br>                NestedTriStateCheckboxView(<br>                    item: child,<br>                    level: level + 1,<br>                    labelContent: labelContent,<br>                    onToggle: onToggle<br>                )<br>            }<br>        }<br>        .padding(.leading, 16) // spacing between self and verticalDivider<br>        .overlay(alignment: .leading) {<br>            verticalDivider()<br>        }<br>        .padding(.trailing, 24)<br>    }<br>    <br>    private func verticalDivider() -&gt; some View {<br>        Rectangle()<br>            .fill(Color.gray)<br>            .frame(width: 0.5)<br>    }<br>}</pre><h3>Checkbox Toggle Logic</h3><p>When a checkbox state changes, propagation must be handled in <strong>two directions</strong> to keep the tree consistent:</p><h4>1. Downward Propagation (Parent → Children)</h4><p>When a node is toggled:</p><ul><li>If it becomes <strong>checked</strong><br> → all of its children should become checked</li><li>If it becomes <strong>unchecked</strong><br> → all of its children should become unchecked</li></ul><p>This usually requires recursively updating all descendant nodes.</p><h4>2. Upward Propagation (Children → Parent)</h4><p>After a child changes, each parent must re-evaluate its state:</p><ul><li>If <strong>all children are checked</strong><br> → parent becomes checked</li><li>If <strong>all children are unchecked</strong><br> → parent becomes unchecked</li><li>Otherwise<br> → parent becomes partial</li></ul><p><strong>This evaluation then propagates upward through the hierarchy, recalculating each parent’s state until the root node is reached.</strong></p><p><strong>To implement tri-state checkbox behavior, the update logic must:<br></strong>- Finds the toggled node in the tree<br>- Updates its state<br>- Propagates changes to children<br>- Recalculates parent states<br>- Returns a new tree model</p><h3>Examples</h3><p>You can test the component using the code below.</p><pre>struct NestedTriStateCheckboxExampleView: View {<br><br>    var body: some View {<br>        ScrollView {<br>            NestedTriStateCheckboxView(<br>                item: root,<br>                level: 0,<br>                labelContent: { item in<br>                    checkboxLabel(item: item)<br>                },<br>                onToggle: { tappedItem in<br>                    toggle(item: tappedItem)<br>                }<br>            )<br>            .padding()<br>        }<br>    }<br><br>    private func checkboxLabel(<br>        item: NestedTriSateCheckboxItemUIModel<br>    ) -&gt; some View {<br>        HStack(spacing: 8) {<br>            Text(item.label)<br>                .bold()<br>                .foregroundStyle(.black)<br><br>            if item.hasChildren {<br>                Text(&quot;\(item.childrenCount)&quot;)<br>                    .foregroundStyle(.black)<br>            }<br>        }<br>    }<br>    <br>    @State private var root: NestedTriSateCheckboxItemUIModel = {<br>        .init(<br>            id: &quot;root&quot;,<br>            label: &quot;All Items&quot;,<br>            state: .partial,<br>            children: [<br>                .init(<br>                    id: &quot;1&quot;,<br>                    label: &quot;Fruits&quot;,<br>                    state: .partial,<br>                    children: [<br>                        .init(id: &quot;1-1&quot;, label: &quot;Apple&quot;, state: .checked, children: []),<br>                        .init(id: &quot;1-2&quot;, label: &quot;Banana&quot;, state: .checked, children: []),<br>                        .init(id: &quot;1-3&quot;, label: &quot;Kiwi&quot;, state: .unchecked, children: [])<br>                    ]<br>                ),<br>                .init(<br>                    id: &quot;2&quot;,<br>                    label: &quot;Vegetables&quot;,<br>                    state: .unchecked,<br>                    children: [<br>                        .init(id: &quot;2-1&quot;, label: &quot;Tomato&quot;, state: .unchecked, children: []),<br>                        .init(id: &quot;2-2&quot;, label: &quot;Potato&quot;, state: .unchecked, children: []),<br>                        .init(id: &quot;2-3&quot;, label: &quot;Carrot&quot;, state: .unchecked, children: [])<br>                    ]<br>                ),<br>                .init(<br>                    id: &quot;3&quot;,<br>                    label: &quot;Drinks&quot;,<br>                    state: .checked,<br>                    children: [<br>                        .init(id: &quot;3-1&quot;, label: &quot;Water&quot;, state: .checked, children: []),<br>                        .init(id: &quot;3-2&quot;, label: &quot;Orange Juice&quot;, state: .checked, children: []),<br>                        .init(id: &quot;3-3&quot;, label: &quot;Coffee&quot;, state: .checked, children: [])<br>                    ]<br>                )<br>            ]<br>        )<br>    }()<br>}<br><br>// Toggle logic<br>private extension NestedTriStateCheckboxExampleView {<br><br>    func toggle(item: NestedTriSateCheckboxItemUIModel) {<br>        root = updateTree(<br>            node: root,<br>            targetID: item.id<br>        )<br>    }<br><br>    func updateTree(<br>        node: NestedTriSateCheckboxItemUIModel,<br>        targetID: String<br>    ) -&gt; NestedTriSateCheckboxItemUIModel {<br><br>        if node.id == targetID {<br>            let newState: TriCheckboxUIState =<br>                node.state == .checked ? .unchecked : .checked<br><br>            return setStateRecursively(<br>                node: node,<br>                state: newState<br>            )<br>        }<br><br>        let updatedChildren = node.children.map {<br>            updateTree(node: $0, targetID: targetID)<br>        }<br><br>        let updatedNode = NestedTriSateCheckboxItemUIModel(<br>            id: node.id,<br>            label: node.label,<br>            state: node.state,<br>            children: updatedChildren<br>        )<br><br>        return recalculateState(node: updatedNode)<br>    }<br><br>    func setStateRecursively(<br>        node: NestedTriSateCheckboxItemUIModel,<br>        state: TriCheckboxUIState<br>    ) -&gt; NestedTriSateCheckboxItemUIModel {<br><br>        NestedTriSateCheckboxItemUIModel(<br>            id: node.id,<br>            label: node.label,<br>            state: state,<br>            children: node.children.map {<br>                setStateRecursively(node: $0, state: state)<br>            }<br>        )<br>    }<br><br>    func recalculateState(<br>        node: NestedTriSateCheckboxItemUIModel<br>    ) -&gt; NestedTriSateCheckboxItemUIModel {<br><br>        guard !node.children.isEmpty else { return node }<br><br>        let states = node.children.map { $0.state }<br><br>        let newState: TriCheckboxUIState<br>        if states.allSatisfy({ $0 == .checked }) {<br>            newState = .checked<br>        } else if states.allSatisfy({ $0 == .unchecked }) {<br>            newState = .unchecked<br>        } else {<br>            newState = .partial<br>        }<br><br>        return NestedTriSateCheckboxItemUIModel(<br>            id: node.id,<br>            label: node.label,<br>            state: newState,<br>            children: node.children<br>        )<br>    }<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/371/1*eHf8JDoA90GFCjW0-RCypQ.png" /><figcaption>Preview of `NestedTriStateCheckboxExampleView`</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*umzz43dNLdkb7I2GadmI1A.gif" /><figcaption>Working example</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0e739536cb15" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Sticky Header Table in SwiftUI]]></title>
            <link>https://erenoz.medium.com/building-a-sticky-header-table-in-swiftui-5d75b1643bf0?source=rss-41487115d0a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d75b1643bf0</guid>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[ios-development]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[swiftui]]></category>
            <dc:creator><![CDATA[Fatih Eren Özçelik]]></dc:creator>
            <pubDate>Mon, 08 Dec 2025 19:16:11 GMT</pubDate>
            <atom:updated>2025-12-08T19:16:11.849Z</atom:updated>
            <content:encoded><![CDATA[<h4>A fully scroll-synchronized grid with pinned / frozen row &amp; column headers</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KvHxvMAyXSdlT-RFHiQL8g.png" /></figure><p>SwiftUI provides many layout tools, yet it still lacks one very common UI capability: a table where the <strong>top row</strong> and <strong>left column</strong> remain visible while scrolling. This behavior is essential for building spreadsheet-style interfaces, pricing grids, schedule matrices, and dashboard-like data views.</p><p>In this article, we’ll walk through a reusable StickyHeaderTableView component built entirely with SwiftUI. It supports:</p><ul><li>Sticky top-left header cell</li><li>Sticky first row (column headers)</li><li>Sticky first column (row headers)</li><li>Synchronized horizontal &amp; vertical scrolling</li><li>Optional flexible or fixed column widths</li><li>Fully customizable cell views</li></ul><h3>Full Component Code</h3><pre>import SwiftUI<br><br>/// A customizable table view that supports sticky (pinned) first row and first column.<br>///<br>/// `StickyHeaderTableView` is a flexible SwiftUI table layout where both the top header row<br>/// and the left header column remain visible while scrolling horizontally or vertically.<br>///<br>/// The table is composed of:<br>/// - A top-left **corner cell**<br>/// - A sticky **top row** for column headers<br>/// - A sticky **left column** for row headers<br>/// - A scrollable **content area**<br>///<br>/// - Tip: To prevent scroll bounce effects or misalignment, consider disabling scroll bouncing.    <br>public struct StickyHeaderTableView&lt;Row, Column, FirstCell: View, RowHeader: View, ColumnHeader: View, Cell: View&gt;: View {<br>    <br>    private let rows: [Row]<br>    private let columns: [Column]<br>    private let minColumnWidth: CGFloat<br>    private let flexibleColumnWidth: Bool<br>    private let firstCell: () -&gt; FirstCell<br>    private let rowHeader: (Row) -&gt; RowHeader<br>    private let columnHeader: (Column) -&gt; ColumnHeader<br>    private let cell: (Row, Column, Int, Int) -&gt; Cell<br>    <br>    @State private var scrollOffset: CGPoint = .zero<br>    @State private var calculatedColumnWidth: CGFloat = 0<br>    <br>    public init(<br>        rows: [Row],<br>        columns: [Column],<br>        minColumnWidth: CGFloat,<br>        flexibleColumnWidth: Bool = false,<br>        @ViewBuilder firstCell: @escaping () -&gt; FirstCell,<br>        @ViewBuilder rowHeader: @escaping (Row) -&gt; RowHeader,<br>        @ViewBuilder columnHeader: @escaping (Column) -&gt; ColumnHeader,<br>        @ViewBuilder cell: @escaping (Row, Column, _ rowIndex: Int, _ colIndex: Int) -&gt; Cell<br>    ) {<br>        self.rows = rows<br>        self.columns = columns<br>        self.minColumnWidth = minColumnWidth<br>        self.flexibleColumnWidth = flexibleColumnWidth<br>        self.firstCell = firstCell<br>        self.rowHeader = rowHeader<br>        self.columnHeader = columnHeader<br>        self.cell = cell<br>    }<br>    <br>    public var body: some View {<br>        HStack(alignment: .top, spacing: .zero) {<br>            rowHeaders()<br>            VStack(alignment: .leading, spacing: .zero) {<br>                columnHeaders()<br>                table()<br>            }<br>        }<br>    }<br>    <br>    @ViewBuilder<br>    private func rowHeaders() -&gt; some View {<br>        VStack(alignment: .leading, spacing: .zero) {<br>            firstCell()<br>            ScrollView([.vertical], showsIndicators: false) {<br>                VStack(alignment: .leading, spacing: .zero) {<br>                    ForEach(Array(rows.enumerated()), id: \.offset) { index, row in<br>                        rowHeader(row)<br>                    }<br>                }<br>                .offset(y: scrollOffset.y)<br>            }<br>            .scrollDisabled(true)<br>        }<br>    }<br>    <br>    @ViewBuilder<br>    private func columnHeaders() -&gt; some View {<br>        ScrollView([.horizontal], showsIndicators: false) {<br>            HStack(alignment: .top, spacing: .zero) {<br>                ForEach(Array(columns.enumerated()), id: \.offset) { index, col in<br>                    columnHeader(col)<br>                        .frame(width: calculatedColumnWidth)<br>                }<br>            }<br>            .offset(x: scrollOffset.x)<br>        }<br>        .background(<br>            GeometryReader { proxy in<br>                Color.clear<br>                    .onAppear {<br>                        calculatedColumnWidth = calculateColumnWidth(availableWidth: proxy.size.width)<br>                    }<br>            }<br>        )<br>        .scrollDisabled(true)<br>    }<br>    <br>    @ViewBuilder<br>    private func table() -&gt; some View {<br>        GeometryReader { proxy in<br>            ScrollView([.vertical, .horizontal], showsIndicators: false) {<br>                VStack(alignment: .leading, spacing: .zero) {<br>                    ForEach(Array(rows.enumerated()), id: \.offset) { rowIndex, row in<br>                        HStack(alignment: .top, spacing: .zero) {<br>                            ForEach(Array(columns.enumerated()), id: \.offset) { colIndex, col in<br>                                cell(row, col, rowIndex, colIndex)<br>                                    .frame(width: calculatedColumnWidth)<br>                            }<br>                        }<br>                    }<br>                }<br>                .frame(<br>                    minWidth: proxy.size.width,<br>                    minHeight: proxy.size.height,<br>                    alignment: .topLeading<br>                )<br>                .background(GeometryReader { geo in<br>                    Color.clear<br>                        .preference(key: StickyHeaderTableViewOffsetKey.self, value: geo.frame(in: .named(&quot;scroll&quot;)).origin)<br>                })<br>                .onPreferenceChange(StickyHeaderTableViewOffsetKey.self) { value in<br>                    scrollOffset = value<br>                }<br>            }<br>            .coordinateSpace(name: &quot;scroll&quot;)<br>        }<br>    }<br>    <br>    /// Calculates the width of each column based on the available horizontal space.<br>    /// - If `flexibleColumnWidth` is disabled, all columns use the minimum width.<br>    /// - If `flexibleColumnWidth` enabled, the available width is divided equally among columns.<br>    /// - The result is never smaller than `minColumnWidth`, ensuring columns do not shrink too far.<br>    private func calculateColumnWidth(availableWidth: CGFloat) -&gt; CGFloat {<br>        let columnCount = CGFloat(columns.count)<br>        guard columnCount &gt; 0 else { return minColumnWidth }<br>        <br>        if !flexibleColumnWidth { return minColumnWidth }<br>        <br>        let calculatedWidth = availableWidth / columnCount<br>        return max(minColumnWidth, calculatedWidth)<br>    }<br>}<br><br><br>private struct StickyHeaderTableViewOffsetKey: PreferenceKey {<br>    typealias Value = CGPoint<br>    static var defaultValue = CGPoint.zero<br>    static func reduce(value: inout Value, nextValue: () -&gt; Value) {<br>        value.x += nextValue().x<br>        value.y += nextValue().y<br>    }<br>}</pre><h3>Examples</h3><p>You can test the component using the code below with various row and column sizes, toggle flexibleColumnWidth on or off, and apply different cell styles to see how the component adapts.</p><pre>import SwiftUI<br><br>struct ExampleView: View {<br>    <br>    let rows = [<br>        &quot;00:00&quot;, &quot;01:00&quot;, &quot;02:00&quot;, &quot;03:00&quot;, &quot;04:00&quot;, &quot;05:00&quot;,<br>        &quot;06:00&quot;, &quot;07:00&quot;, &quot;08:00&quot;, &quot;09:00&quot;, &quot;10:00&quot;, &quot;11:00&quot;,<br>        &quot;12:00&quot;, &quot;13:00&quot;, &quot;14:00&quot;, &quot;15:00&quot;, &quot;16:00&quot;, &quot;17:00&quot;,<br>        &quot;18:00&quot;, &quot;19:00&quot;, &quot;20:00&quot;, &quot;21:00&quot;, &quot;22:00&quot;, &quot;23:00&quot;,<br>        &quot;24:00&quot;<br>    ]<br>    <br>    let columns = [&quot;Mon&quot;, &quot;Tue&quot;, &quot;Wed&quot;, &quot;Thu&quot;, &quot;Fri&quot;, &quot;Sat&quot;, &quot;Sun&quot;]<br><br>    let cellWidth: CGFloat = 80<br>    let cellHeight: CGFloat = 44<br>    <br>    var body: some View {<br>        StickyHeaderTableView(<br>            rows: rows,<br>            columns: columns,<br>            minColumnWidth: cellWidth,<br>            flexibleColumnWidth: true,<br>            firstCell: {<br>                Text(&quot;Header&quot;)<br>                    .frame(width: cellWidth, height: cellHeight)<br>                    .background(.colorPrimaryBg)<br>                    .border(Color.colorSplit)<br>            },<br>            rowHeader: { row in<br>                Text(row)<br>                    .frame(width: cellWidth, height: cellHeight)<br>                    .background(.colorPrimaryBg)<br>                    .border(Color.colorSplit)<br>            },<br>            columnHeader: { column in<br>                Text(column)<br>                    .frame(height: cellHeight)<br>                    .frame(minWidth: cellWidth, maxWidth: .infinity)<br>                    .background(.colorPrimaryBg)<br>                    .border(Color.colorSplit)<br>            },<br>            cell: { row, column, rowIndex, colIndex in<br>                Text(&quot;\(row.prefix(2))-\(column.prefix(3))&quot;)<br>                    .frame(height: cellHeight)<br>                    .frame(minWidth: cellWidth, maxWidth: .infinity)<br>                    .background(Color.white)<br>                    .border(Color.colorSplit)<br>            }<br>        )<br>    }<br>}<br><br>#Preview {<br>    ExampleView()<br>        .padding()<br>        .disableScrollBounces()<br>}<br><br>// Scroll bounce disabler<br>extension View {<br>    func disableScrollBounces() -&gt; some View {<br>        modifier(DisableScrollBouncesModifier())<br>    }<br>}<br><br>struct DisableScrollBouncesModifier: ViewModifier {<br>    func body(content: Content) -&gt; some View {<br>        content<br>            .onAppear {<br>                UIScrollView.appearance().bounces = false<br>            }<br>            .onDisappear {<br>                UIScrollView.appearance().bounces = true<br>            }<br>    }<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/380/1*qSIDwGS3Pv-GVzz8kq7fSA.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/379/1*gdDwyxn4LOZ70iNP7zZhLw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/379/1*L8vkspV4njA6mdTczKH_0Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/379/1*KFgvSjTlJC9E0Zyr8nsi4g.png" /><figcaption>The first two examples use <strong>flexibleColumnWidth = true</strong>, while the third example sets it to <strong>false</strong>.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d75b1643bf0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[XCode Debugging]]></title>
            <link>https://erenoz.medium.com/xcode-debugging-1bfdaf6af1ab?source=rss-41487115d0a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/1bfdaf6af1ab</guid>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[debugging]]></category>
            <category><![CDATA[point-break]]></category>
            <category><![CDATA[tools]]></category>
            <category><![CDATA[xcode]]></category>
            <dc:creator><![CDATA[Fatih Eren Özçelik]]></dc:creator>
            <pubDate>Thu, 04 Jul 2024 07:04:16 GMT</pubDate>
            <atom:updated>2024-07-04T08:06:15.411Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u5i4VisZ9HDJMhTcWB52aQ.jpeg" /></figure><h3>Breakpoint Navigator &amp; Breakpoint Types</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/879/0*YeZ4axVX3MgW-vo1.png" /><figcaption><a href="https://developer.apple.com/documentation/xcode/setting-breakpoints-to-pause-your-running-app">From Apple Developer Documentation</a></figcaption></figure><p><strong>Swift Error Breakpoint<br></strong>Pauses execution when an error is thrown.<br>- try someFunction() throws an error, and the code execution stops there.</p><p><strong>Exception Breakpoint<br></strong>Breaks the app process when an exception is thrown.<br>- An NSException is thrown, and the code execution stops there.</p><p><strong>Symbolic Breakpoint<br></strong>Suspends the app when a particular method or function is invoked.<br>- The code stops when the viewDidLoad() method is called.</p><p><strong>Runtime Issue Breakpoint<br></strong>Pauses the app process when a runtime issue is detected.<br>- The code stops if there is a memory access violation.</p><p><strong>Constraint Error Breakpoint<br></strong>Debugging issues related to auto layout. Pauses the app process if auto layout throws an error.<br>- The code stops when an auto layout constraint cannot be satisfied.</p><p><strong>Test Failure Breakpoint<br></strong>Pause the app process if a test fails (like a unit test).</p><h3>Deugging Interface</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*X0IT9N3-TDPMZJhp.png" /><figcaption><a href="https://developer.apple.com/documentation/xcode/stepping-through-code-and-inspecting-variables-to-isolate-bugs">From Apple Developer Documentation</a></figcaption></figure><h4>Debug Navigator</h4><p>Displays app processes organized by threads.</p><h4>Variable Viewer</h4><p>Lists the variables available in the current execution context.</p><h4>Debugger Console</h4><pre>po username<br>// prints an object description for the result<br><br>expression finalColor = UIColor.purple</pre><h3>Debug Bar</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SBAb0yloBwErOumC.png" /><figcaption><a href="https://developer.apple.com/documentation/xcode/stepping-through-code-and-inspecting-variables-to-isolate-bugs">From Apple Developer Documentation</a></figcaption></figure><h4>Continue / Pause button</h4><p>Continue normal execution from the paused position until the app stops at the next breakpoint <em>or </em>pause the app without setting a breakpoint.</p><h4>Step Over button</h4><p>Execute the next instruction within the current function scope.</p><h4>Step Into button</h4><p>Execute the next instruction. If the next instruction is inside another method or function, the debugger jumps to that function and continues executing it each time Step Into button is clicked.</p><h4>Step Out button</h4><p>Skips the rest of the function and return to the next instruction in the calling function or method.</p><h4>Debug View Hierarchy</h4><p>See the UI elements and their layers.</p><h4>Debug Memory Graph</h4><p>To detect memory issues such as retain cycles or memory leaks. (complex)</p><h4>Environment Overrides</h4><p>Change the app environment (Light/Dark mode, dynamic types, accessibility options).</p><h4>Simulate Location</h4><p>Change the simulated app location or stop simulating any location.</p><h4>References</h4><ul><li><a href="https://developer.apple.com/documentation/xcode/setting-breakpoints-to-pause-your-running-app">Setting breakpoints to pause your running app | Apple Developer Documentation</a></li><li><a href="https://developer.apple.com/documentation/xcode/stepping-through-code-and-inspecting-variables-to-isolate-bugs">Stepping through code and inspecting variables to isolate bugs | Apple Developer Documentation</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1bfdaf6af1ab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dependency Injection with Swift]]></title>
            <link>https://blog.stackademic.com/dependency-injection-with-swift-bdc6db9cee4c?source=rss-41487115d0a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/bdc6db9cee4c</guid>
            <category><![CDATA[pizza]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[dependency-injection]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[Fatih Eren Özçelik]]></dc:creator>
            <pubDate>Mon, 08 Apr 2024 06:13:27 GMT</pubDate>
            <atom:updated>2026-09-29T13:49:02.279Z</atom:updated>
            <content:encoded><![CDATA[<h4>Implementation of Dependency Injection technique in Swift with an Italian chef</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MHyIgE8ETxzhoMzk0GZDoQ.png" /><figcaption>“Syringe” icon by Imron Sadewo from <a href="https://thenounproject.com/browse/icons/term/syringe">Noun Project</a>.</figcaption></figure><blockquote><strong>Dependency injection</strong> is a programming technique in which an object or function <strong>receives other objects or functions that it requires</strong>, as opposed to <strong>creating them internally. </strong>— Wikipedia</blockquote><h4>Let me start with a very simple example to understand this technique:</h4><p>First, let’s examine a piece of code that <strong>does not use</strong> the Dependency Injection technique 👇🏻</p><pre>class Browser {<br>    func downloadDocuments() {<br>        print(&quot;Documents downloaded&quot;)<br>    }<br>}<br><br>class Computer {<br>    var files: [String] = []<br>    <br>    func writeDocument() {<br>        print(&quot;Document written&quot;)<br>    }<br>}<br><br>class FileDetailsViewModel {<br>    let browser = Browser() // &lt;--<br>    let computer = Computer() // &lt;--<br>    <br>    func downloadDocuments() {<br>        browser.downloadDocuments()<br>    }<br>    <br>    func writeDocument() {<br>        computer.writeDocument()<br>    }<br>}</pre><p>As you can see, FileDetailsViewModel class creating object instances from both the Browser and Computer classes. So, the class <strong>creating the components it needs itself</strong>.</p><p>Now we will create the same structure again, but this time we will use Dependency Injection 👇🏻</p><pre>class Browser {<br>    func downloadDocuments() {<br>        print(&quot;Documents downloaded&quot;)<br>    }<br>}<br><br>class Computer {<br>    var files: [String] = []<br>    <br>    func writeDocument() {<br>        print(&quot;Document written&quot;)<br>    }<br>}<br><br>class FileDetailsViewModel {<br>    let browser: Browser // &lt;--<br>    let computer: Computer // &lt;--<br>    <br>    init(browser: Browser, computer: Computer) { // &lt;--]<br>        self.browser = browser                   //    |<br>        self.computer = computer                 // &lt;--]<br>    }<br>    <br>    func downloadDocuments() {<br>        browser.downloadDocuments()<br>    }<br>    <br>    func writeDocument() {<br>        computer.writeDocument()<br>    }<br>}</pre><p>Now we created Browser and Computer objects <strong>as properties</strong> inside the FileDetailsViewModel class. And we specified that these objects <strong>should be populated</strong> in the initializer of FileDetailsViewModel.</p><p>So, after this process, whenever you want to create a FileDetailsViewModel, <strong>you must pass a Browser and Computer class</strong> to the initializer of FileDetailsViewModel. This process is also called<strong> Initializer Injection</strong>.</p><h4><strong>As an example of what we do:</strong></h4><p>After implementation of Dependency Injection technique, if we want to createa a file detail view, we will call the createFileDetailsView function. And this function <strong>will need a Browser and Computer class to instantiate a FileDetailsViewModel</strong>. And <strong>we will inject the objects that we alreay created in DesktopView</strong> to FileDetailsViewModel 👇🏻</p><pre>struct DesktopView {<br>    let browser = Browser()<br>    let computer = Computer()<br>    <br>    func createFileDetailsView() {<br>        let viewModel = FileDetailsViewModel(<br>          browser: browser, // &lt;--<br>          computer: computer // &lt;--<br>        )<br>    }<br>}</pre><h4>Now let’s examine the same process with a perfect pizza margherita 👌🏻:</h4><p>Let’s say we will ask an Italian chef to make the perfect pizza margherita. <strong>We already have</strong> pizza dough, tomatoes, fresh mozzarella, fresh basil and olive oil. The chef <strong>asks us for ingredients</strong> to make the pizza. And we say, we have the necessary ingredients you want. Don’t worry about finding/producing these ingredients yourself, <strong>we will provide you</strong> with the cooking ingredients. So the chef will only be responsible for making the pizza, thanks to the ingredients we will provide. Thus, we used Dependency Injection! 🍻</p><h4>Why is Dependency Injection useful?</h4><ul><li><strong>Simpler data flow </strong><br>It creates a simple flow from top to bottom in a single direction. And having a simple, understandable, scalable flow in large-sized projects becomes very important when maintaining the code.</li><li><strong>Dependency change becomes easier</strong><br>Let’s consider the Browser object in the example code above. If we want, we can use Google Chrome, Safari or Firefox and it doesn’t matter as long as the object we’re passing is a browser.</li><li><strong>Easy to test</strong><br>While testing, instead of using a real browser or a real computer, we can create a browser under our own control and use it in our test environment.</li></ul><p>This article is translated from <a href="https://medium.com/@eupmrt/dependency-injection-swift-e63ca4f41b3d">Dependency Injection — Swift by Eyup Mert</a>. Kudos to him!</p><h3>Stackademic 🎓</h3><p>Thank you for reading until the end. Before you go:</p><ul><li>Please consider <strong>clapping</strong> and <strong>following</strong> the writer! 👏</li><li>Follow us <a href="https://twitter.com/stackademichq"><strong>X</strong></a><strong> | </strong><a href="https://www.linkedin.com/company/stackademic"><strong>LinkedIn</strong></a><strong> | </strong><a href="https://www.youtube.com/c/stackademic"><strong>YouTube</strong></a><strong> | </strong><a href="https://discord.gg/in-plain-english-709094664682340443"><strong>Discord</strong></a></li><li>Visit our other platforms: <a href="https://plainenglish.io/"><strong>In Plain English</strong></a><strong> | </strong><a href="https://cofeed.app/"><strong>CoFeed</strong></a><strong> | </strong><a href="https://venturemagazine.net/"><strong>Venture</strong></a><strong> | </strong><a href="https://blog.cubed.run/"><strong>Cubed</strong></a></li><li>More content at <a href="https://stackademic.com/"><strong>Stackademic.com</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdc6db9cee4c" width="1" height="1" alt=""><hr><p><a href="https://blog.stackademic.com/dependency-injection-with-swift-bdc6db9cee4c">Dependency Injection with Swift</a> was originally published in <a href="https://blog.stackademic.com/">Stackademic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI From My Perspective]]></title>
            <link>https://erenoz.medium.com/ai-from-my-perspective-d4d9d0e2718?source=rss-41487115d0a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4d9d0e2718</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[perspective]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Fatih Eren Özçelik]]></dc:creator>
            <pubDate>Thu, 06 Oct 2022 19:45:05 GMT</pubDate>
            <atom:updated>2022-10-06T19:45:05.634Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ww-ei5cz4XEgz83npDHXDg.jpeg" /><figcaption>Image by <a href="https://www.freepik.com/free-photo/robot-handshake-human-background-futuristic-digital-age_17850426.htm#query=artificial%20intelligence&amp;position=0&amp;from_view=search&amp;track=sph">rawpixel.com</a> on <a href="https://www.freepik.com/">Freepik</a></figcaption></figure><h3>AI</h3><p>From my perspective, artificial intelligence is a computer or robot acting like an intelligent entity based on the inputs and outputs given to it and performing the desired tasks.</p><h3>AI and Jobs</h3><p>Artificial intelligence is slowly entering all areas of work that are repetitive and do not require human supervision. Not only that, but even in medicine, it can produce successful results in areas where human life is the subject. The rapid increase in the popularity of artificial intelligence creates new business areas. Being an interesting subject, it pushes people to learn how to train artificial intelligence and have a job in this field. But at the same time, the unqualified business areas that I mentioned at the beginning are slowly disappearing. Therefore, while job opportunities increasing on the one hand, they decreasing on the other.</p><h3>AI and TV</h3><p>One of the best AI series I’ve ever watched was <a href="https://www.imdb.com/title/tt8134186/"><strong>Devs</strong></a>. The series was containing ideas that I had never seen before. The series began when the owner of a large software company lost his family in an accident and gathered the most talented software developers together to make his dream come true. It was built on determinism in general. The boss’s idea was to get the power to simulate any moment in history with providing all the necessary data to a supercomputer.</p><p>I’ll give the same example the boss gave in the show to explain Devs.</p><blockquote>Imagine a pen. The pen rolls because we push it. Now think of a computer. Let’s give all the data about this pen rolling on the table into the computer. The curve, the velocity, the mass of the component parts, the atomic structure… What can the computer show us? How much force is applied to the pen, when the pen begins to roll and when to stop. The computer can see the past. The computer can see the future.</blockquote><blockquote>Now let’s apply what we did on the pen to everything. Here is the Devs.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4d9d0e2718" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Process Models for Data Science Projects: CRISP-DM and KDD]]></title>
            <link>https://medium.com/kodluyoruz/process-models-for-data-science-projects-crisp-dm-and-kdd-172b631dcac1?source=rss-41487115d0a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/172b631dcac1</guid>
            <category><![CDATA[model]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Fatih Eren Özçelik]]></dc:creator>
            <pubDate>Thu, 06 Oct 2022 12:02:50 GMT</pubDate>
            <atom:updated>2022-11-27T16:12:35.256Z</atom:updated>
            <content:encoded><![CDATA[<p>The most common process models for data science projects are CRISP-DM and KDD. The aim of this article is to briefly describe the stages of both models and to identify the differences between them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oqfRuIleu4CfJ2cEDzHNYg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@dawson2406?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Stephen Dawson</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>CRISP-DM Stages</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*Nz8aIbN1uHvdKGKERB_EgA.png" /><figcaption><a href="https://commons.wikimedia.org/wiki/File:CRISP-DM_Process_Diagram.png">CRISP-DM Process Diagram</a></figcaption></figure><ol><li><strong>Business Understanding <br></strong>Business Understanding stage focuses on identifying the requirements of the project. Understanding what the requirements are and setting goals accordingly affects the entire project process. This stage is of great importance in all projects in general. If it is skipped, a very different result than desired can be achieved at the end of the process.</li><li><strong>Data Understanding <br></strong>In the Data Understanding stage, the initial data is collected according to the needs decided in the previous stage, the collected data is examined and its properties are defined, a deeper data exploration is made and finally data quality is measured and how clean the data is determined.</li><li><strong>Data Preparation <br></strong>At this stage, final datasets are prepared before proceeding to the modeling stage. For this stage, these steps are followed:<br>📌 Which datasets will be used and the reasons are determined<br>📌 Datasets are cleaned again and ready for modeling<br>📌 New useful attributes are derived within the datasets<br>📌 New datasets are created by combining data collected from multiple sources<br>📌 Data is re-formatted according to business needs</li><li><strong>Modeling <br></strong>Models are created using different techniques with the information obtained from the previous stages. Then these models are evaluated by testing and continue like this until the desired result is obtained from the model.</li><li><strong>Evaluation <br></strong>At this stage, it is decided which model best meets the needs. It is checked whether the requirements determined in the Business Understanding phase are met.</li><li><strong>Deployment <br></strong>If all previous steps have been completed and the model has been successful, decision is made to deploy the model. Plan for model deployment is developed, maintenance plans are made for the post-project phase, final reports are documented for the whole process and what is going well and what could be better is observed.</li></ol><h3>KDD Stages</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*2yZtf1PCoaGCGs8k.gif" /><figcaption><a href="http://www2.cs.uregina.ca/~dbd/cs831/notes/kdd/1_kdd.html">http://www2.cs.uregina.ca/~dbd/cs831/notes/kdd/1_kdd.html</a></figcaption></figure><ol><li><strong>Selection<br></strong>Creating target datasets by acting on the available data/database</li><li><strong>Pre-processing<br></strong>Improving and cleaning the created target datasets, getting rid of faulty or missing data</li><li><strong>Transformation<br></strong>Converting pre-processed data into utilizable data</li><li><strong>Data Mining<br></strong>Searching for patterns depending on the project goal by sifting through the transformed data</li><li><strong>Interpretation/Evaluation<br></strong>Interpretation, evaluation, documentation and visualization of cleaned, transformed and patterned data for helping humans to understand easier the output</li></ol><h3>CRISP-DM vs KDD</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*9EehY1yieKKJQQPZ9ALm6g.png" /><figcaption>By <a href="https://medium.datadriveninvestor.com/data-science-project-management-methodologies-f6913c6b29eb">Quantum</a> on Medium — Edited</figcaption></figure><p>📌 CRISP-DM combines the Selection and Pre-processing stages under the Data Understanding stage.</p><p>📌 CRISP-DM stages are reversible. In this way, when an error is made, it is possible to go back and correct the error and make changes without completing the entire cycle.</p><p>📌 CRISP-DM differs from KDD with the Business Understanding phase. With the Business Understanding phase, CRISP-DM covers all the steps of building a reliable data science project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wV0ZQqz_-rBw3ewFebFBtQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@kmuza?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Carlos Muza</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h4>Links:</h4><ul><li><a href="https://medium.datadriveninvestor.com/data-science-project-management-methodologies-f6913c6b29eb">Data Science project management methodologies</a></li><li><a href="https://www.datascience-pm.com/crisp-dm-2/">What is CRISP DM?</a></li><li><a href="https://www.datascience-pm.com/kdd-and-data-mining/">KDD and Data Mining</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=172b631dcac1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kodluyoruz/process-models-for-data-science-projects-crisp-dm-and-kdd-172b631dcac1">Process Models for Data Science Projects: CRISP-DM and KDD</a> was originally published in <a href="https://medium.com/kodluyoruz">Kodluyoruz</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Yazılım Geliştirme Stajı Deneyimlerim]]></title>
            <link>https://erenoz.medium.com/yaz%C4%B1l%C4%B1m-geli%C5%9Ftirme-staj%C4%B1-deneyimlerim-44a4c31696ec?source=rss-41487115d0a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/44a4c31696ec</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-internship]]></category>
            <category><![CDATA[intern]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[internships]]></category>
            <dc:creator><![CDATA[Fatih Eren Özçelik]]></dc:creator>
            <pubDate>Sun, 08 Aug 2021 20:09:53 GMT</pubDate>
            <atom:updated>2021-12-23T21:05:34.298Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*QUGKehD4W19BtYqe" /><figcaption><a href="https://unsplash.com/photos/dsOvZnqGawg">Unsplash</a></figcaption></figure><p>2021 yılının yazında, Antalya’da bulunan ve güneş paneli üretiminde hem yurtiçi hem de yurtdışında büyük faaliyet gösteren CW Enerji firmasında yazılım geliştirme stajımı yaptım.</p><p>Stajda ilk haftam veritabanını öğrenmekle geçti. Bu süreçte bazı veritabanlarının farklarını ve kullanım alanlarını kavradıktan sonra MS SQL Server komutlarını öğrenmeye başladım. select, join, alter, tablo oluşturma ve düzenleme gibi konuları dokümantasyonlardan inceleyerek ve bazı siteler aracılığıyla quizler çözerek ilerledim. Ayrıca bu ilk dokümantasyondan öğrenme deneyimim oldu. Bundan önce hep tutorial videoları izleyerek öğrenirdim. Çünkü dokümantasyonlar uzaktan bakıldığında çok yorucu gibi gözüküyor. Bu sayede dokümantasyonları da nasıl kullanacağımı öğrenmiş oldum.</p><p>Sql öğrenirken hep Northwind kullandım. Komutları bitirdikten sonra kendime ait örnek bir veritabanı oluşturmaya karar verdim. Veritabanı komutlarıyla pratik yapmak için bence en iyi seçenek buydu. 10–15 adet tablodan oluşan bir veritabanı oluşturdum ve her tabloya çokça veri girişi yaptım.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*rOExbvx9SjpBv2G6" /></figure><p>Sql Server eğitiminden sonra, sırada bu bilgiyi kullanabileceğim bir alan lazımdı. C# ile Windows Form Application üzerinden ilerlemeye karar verdik. Daha önce hiç Windows Form uygulaması geliştirmediğim için bilgisizdim. Visual Studio’dan bir proje oluşturup, toolbox’tan bileşenleri ekrana sürükleyip bırakmaktan başka bir şey bilmiyordum. En sık kullanılan bileşenlerle basit bir login sayfası oluşturdum. Daha sonra, neden kendi veritabanımı kullanarak bir login sayfası tasarlamıyorum diye düşündüm. Bunun için internette çok basit cümleler ile aramalar yaptım ve istediğim sistemin onlarca farklı alternatife sahip sonuçları karşıma geldi. Bu da internette halihazırda bulunan kaynakların ne kadar çok olduğuna ve bana da ne kadar yardımcı olabileceğine dair bir analiz oldu aynı zamanda.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T-jsBOEOMPb8kxmlGm7vZw.jpeg" /><figcaption><a href="https://www.freepik.com/photos/technology">Technology photo created by pressfoto</a> — Freepik</figcaption></figure><p>Planladığım gibi, giriş sayfasını oluşturduktan sonra veritabanı ile uygulamayı nasıl bağlayacağımı öğrenmeye başladım. Bu aşamada beni bir şeyler rahatsız ediyordu. İlk defa böyle bir uygulama geliştiriyordum ve sanki internette bulduğum kodları kopyalayıp-yapıştırıyor, bir şey öğrenmemiş gibi hissediyordum. Bu algıyı yok etmek için kodları onlarca kez baştan sona okumuşumdur. Ve eminim ki bu algıya kapılan bir sürü insan daha vardır.</p><p>Uygulamanın ilk aşamalarını geliştirmeye devam ettim ve geliştirdikçe aklıma sürekli yeni fikirlerin geldiğini fark ettim. Eklenecek yeni bir özellik planlıyor, nasıl ekleyeceğimi araştırıyor, bulduklarımı uyguluyor ve yeni bir özellik daha düşünmeye başlıyordum. Bu böyle devam ederken fark ettim ki, en başta yaşadığım rahatsızlık hissi ortadan kaybolmuş, artık çoğunlukla kendi kodlarımı yazmaya başlamış ve bilmediğim noktalarda da hazır kod parçalarını kullanmaya başlamışım. Sürekli bulduğum kodları incelemek ve tekrar tekrar okumak, kodların alternatiflerine göz atmak sonucunda artık ne yaptığımdan emindim. Kayıt oluşturma, kullanıcı detayları, pop-up ekranlar, çalışanlara görev atama gibi birkaç özellik daha ekledim ve aklımda uygulayacak fikir kalmayıncaya kadar devam ettim. Böylece ilk Windows Form uygulamamı oluşturmuştum. Projeyi tamamlamak gayet iyi hissettirmişti.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*_wSzrFgi5uyYYSay" /></figure><p>Motivasyonumun zamanla azalmasına olanak tanımadan hızlıca bir MVC Web Application projesine giriştim. Aslında Web geliştirmeyi oldum olası hiç sevmem ve sürekli uzak dururum. Yine de kendimi bir denemek ve Web geliştirme gibi kapsam alanı büyük bir konudan geri kalmamak istedim.</p><p>Hiç ara vermeden MVC mimarisi ile Web öğrenmeye başladım. Yaklaşık 2 haftam vardı stajımın bitmesine. Ve stajımın son günü, takip ettiğim kurs sayesinde ilk web projemi bitirdim. Zor muydu? Evet. Özellikle hızlı ilerlemeye çalışmak bazı kısımları anlamamı çok zorlaştırdı. Sonuç olarak, hala Web geliştirmeden nefret ediyor muyum? Evet. Ama bu sayede, ne isteyip istemediğimi <strong>deneyerek öğrenmiş oldum.</strong> Ortaya çıkan sonuçtan da gayet memnunum.</p><p>Her yerde duyduğum ‘kurumsal mimariyi’ Murat Yücedağ’ın MCV eğitimiyle görüp deneyimledim. Denildiği gibi, SOLID prensiplerine uygun bir projede ortaya çıkan hatalar hızlıca tespit edilebiliyor ve yine hızlıca çözülebiliyor. Böylece kurumsal mimarinin önemini MVC projemde anlamış oldum. Ayrıca bu alanda da bana büyük bir deneyim kazandırdı.</p><p>Ve son olarak, staj danışmanım ve yol gösterenim, <strong>Fatih Yılmaz</strong>’a beni belirsizlikler içinden kurtardığı için çok teşekkür ediyorum. Gözlerimin açılmasını sağlayan bir staj dönemi geçirdim sayesinde.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44a4c31696ec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[YetGen’21 Deneyimim]]></title>
            <link>https://erenoz.medium.com/yetgen21-deneyimim-bac86a72378c?source=rss-41487115d0a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/bac86a72378c</guid>
            <category><![CDATA[yetkinlikler]]></category>
            <category><![CDATA[yetkin-gençler]]></category>
            <category><![CDATA[yet-gen]]></category>
            <category><![CDATA[erhan-erkut]]></category>
            <category><![CDATA[deneyim]]></category>
            <dc:creator><![CDATA[Fatih Eren Özçelik]]></dc:creator>
            <pubDate>Sun, 07 Mar 2021 16:07:48 GMT</pubDate>
            <atom:updated>2022-09-29T01:32:43.011Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6Sfa_ongMjTVzwc7KfhxzA.jpeg" /></figure><p>YetGen diğer herkese olduğu gibi benim için de bir devrim noktası oldu. Benden sonra YetGen’i bir programda, sosyal medyada ya da farklı bir yerde görüp araştırmak ve içeriğini öğrenmek isteyenlere, YetGen maceram başladığı andan itibaren hafta hafta deneyimlerimi aktarmaya karar verdim. Eğitimim bitince değil de eğitimim sürerken anlatmanın daha verimli olacağını düşündüm. Her ders ve aktivite sonrası güncelleme yapacağım.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*6653RJN096oicv2Q.png" /></figure><h3>Kariyer Planlama</h3><p>YetGen’in benim üzerimdeki ilk pozitif değişikliği uyku düzenim oldu. İyi ki de dersler sabah 9 da başlıyor ki böylece o cehennemden kurtulmuş oldum. İlk gün heyecanı diye bir terim vardır bilirsiniz. Klişe gözükebilir ama inanın öyle değil. Öyle değil çünkü programa kabul edilmişsiniz. Cevaplarınızı okumuşlar, beğenmişler ve sizin daha yetkin bir insan olacağınıza karar verip çatının altına almışlar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wCQzvO6vwhceXpp8l1QvPg.png" /></figure><p>Erhan hocam başladığı andan itibaren kendimi hiç yabancı hissetmedim çünkü YetGen başvuru sonuçları açıklanana kadar sürekli sürekli konuşmalarını dinledim. Bir kere duyunca kendinizi alamıyorsunuz arkadaşlar inanın bana. Kaç yıllık eğitim hayatınızda ilk kez biri size duymak istediklerinizi söylüyor. Mola saatlerini açıkladıkları zaman üzülüyorsunuz. Mola istemediğinizi fark ediyorsunuz. Hiç eğitim hayatınızda böyle bir isteğiniz oldu mu? Cevabı biliyorum merak etmeyin.</p><p>Kariyer Planlama dersi başladı, konuşmalar ilerledi, biraz konuya daldık ve orada yıldızlar kaymaya başladı. Kayan yıldızların arkasında hepimiz aynı yazıyı okuduk.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/646/0*33kOIEk0tXlNW5Q8.png" /></figure><p>Bu cümle yıllardır içinde olduğumuz eğitim sistemi için doğru tabir. Bunu öğrendikten sonra hazımsamaya vaktim oldu mu? Tabii ki olmadı. Hemen Drive’dan boş bir sayfa açıp benim ve bölümüm için önemli olan her şeyi not ettim. Ben ileride içinde olacağım sektörle alakalı bu öngörüleri hiçbir profesörümden duyamadım maalesef.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*gYh6HaEtHjzcnUgA.png" /></figure><p>Stajlar, şu an popüler olan ve gelecekte popüler olacak konular, özgeçmiş ve özgelecek, SWOT analizi (güçlü ve zayıf yönleriniz; çevrenizdeki fırsatlar ve tehditler), ne istediğini bilmek gibi konulara giriştik. Benim için inanılmaz bir deneyimdi ve bundan sonraki dersleri de sabırsızlıkla beklememe rağmen, hiçbirinin Kariyer Planlama dersi kadar etkili olacağını düşünmüyorum. Önyargım doğru mu değil mi göreceğim. Adım atmaya olan korkumu yok ettim bu ders sayesinde.</p><h4>Tavsiyelerim:</h4><ul><li><a href="https://www.youtube.com/playlist?list=PLh0GuMCtEl9UJjKrjWM7K4QQp2lwPQA8F">Özgeçmiş ve Özgelecek nasıl hazırlanır?</a></li><li><a href="https://www.16personalities.com/tr">Kişilik tipinizi öğrenin</a></li><li>SWOT analizi yapın</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*tFZBSbdLQ-r3bzFV.png" /></figure><ul><li>Mümkün olduğunca boş zamanlarınızı kitap okuyarak geçirin arkadaşlar. Kendimden örnek vermek gerekirse uzun zamandır kitap okumuyordum çünkü bunalmıştım. Kitap okumaya tekrar başlamamı sağlayacak bir yazar buldum ve sürekli onun kitaplarını okudum. Böylece kitapların sıkıcı olmadığını hatırladım. Tekrar sıkılırsam tekrar onu okuyacağım ve tekrar isteğimi geri kazanacağım.</li></ul><h3>Sunum Teknikleri ve Takım Çalışması</h3><p>Bu dersteki deneyimlerime geçmeden önce karşılaştırma yapmak için çok önemli bir not bırakıyorum. Bu not benim dersten önceki kişisel düşüncem.</p><blockquote>“Bu dersten sonra sunum mu yapacakmışız? Sunum eksik olsa olmaz sanki.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/0*z2G7qhPCyN2ZZ7F1.png" /></figure><p>Grup çalışmaları hakkında konuştuk. Zaten uzun süredir grup çalışmalarına daha yatkın olduğumu iddia ederdim. Biraz da doğrulamış oldum böylece. Grup çalışmasında yapmamız gerekenlerden bahsettik. Eğitim hayatınızda öğretmen tarafından zorla bir sunum grubuna dahil edildiyseniz grup tiplemelerini biliyorsunuz. Arkadaşlarınızın gözlerinden bile anlayabilirsiniz ki hiçbirinin içinde sunuma yardım etmek için zerre istek yok. Sunum gününe kadar yüzde 90 sizin tarafınızdan hazırlanmış olup berbat bir planlamayla birlikte sunum yapılır ve biter. Ya da sunuma yardım etmeyen tipleme sizsiniz ve arkadaşınızın üstüne haksız bir yük bindirirsiniz. Bunlar çok yaygındı ve hala yaygın. Çok sunum ödevi yaptınız ama kimse size nasıl etkili ve doğru sunum yapılır göstermedi değil mi?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*mPl5lu9L8Awhptz3.png" /></figure><p>Ders bitene kadar aklımda eski sunum deneyimlerim dolanıp duruyordu. Yine notlarımı almıştım ama çok çok eksik olduğum bir konuydu bu. Pek de bir şey öğrenemediğimi düşünüyordum ki o anda sunum ödevlerinin detayları verildi ve 3 kişilik bir gruba yerleştirildim. Grup arkadaşlarımla tanışıp basit bir başlangıç planı yaptık ve ayrıldık. 1–2 gün içinde bir değişiklik fark ettim. İlk kez grup arkadaşlarım sunum ödevinde benimle birlikte çalışıyorlardı. Zaten bu değişiklikleri gördüğünüzde YetGen’in farkını anlamaya başlayacaksınız.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*mgSQTelQF9R5i7C5.png" /><figcaption>Aybüke ve Onur’a keyifli grup çalışmamız için tekrar teşekkürler..</figcaption></figure><p>Bir iki gün içinde BM Sürdürülebilir Kalkınma Hedefleri’nden biri olan Yoksulluğa Son konusunu ele aldık ve sunumu hazırladık. Sunumu hazırlarken dikkat ettiğimiz önemli noktalar şunlardı:</p><ul><li><strong>Mümkün olduğunca çok görsel</strong> <em>(Görsellerinizin sade ve anlaşılır olması ayrıca göze daha güzel gelecektir.)</em></li><li><strong>Mümkün olduğunca az yazı ve kısa cümleler </strong><em>(Özellikle konuşacağım konu hakkında başlıkları yazmaya özen gösterdim ve bu başlıklardan kısa, anlaşılır cümlelerle bahsettim.)</em></li><li><strong>Mümkün olduğunca az ve anlaşılır sayısal veri, grafik</strong> <em>(Sunumunuzda yer vereceğiniz grafiklerin sade ve ilk bakışta anlaşılır olmasına dikkat edin. Sunum yapacağınız kişiler sunum konusu hakkında uzman olmayabilir. Gereksiz sayısal verilerle dinleyicilerin odağını öldürmeyin.)</em></li><li><strong>Dolgu malzemesi YOK</strong> <em>(Bunu bir notla direkt olarak özetlemek istiyorum. Bu kelimeleri kullanmak yerine daha güzel bir yetkin genç tavsiyesi vereyim. </em><strong><em>“Susun”</em></strong><em>. Söyleyeceklerinizi toparladığınızda devam edin.)</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/357/0*PlSRPdPO-kUs8DkE.png" /><figcaption>Sondaki kırmızı kelimeye dikkat!</figcaption></figure><ul><li><strong>Monoton bir ses kabul edilemez, heyecanınızı yansıtın </strong><em>(Heyecanım yok diyemezsiniz. Belki konunuzdan memnun değilsinizdir fakat hala sunum yapacağınız için içinizde bir heyecan var. Vurun bunu dışarıya. Kendi lehinize kullanın.)</em></li><li><strong>Ellerinizi ve gözlerinizi kullanın</strong> <em>(Elleriniz kıyafetlerinize yapışık değil ve gözleriniz de yere bakmak zorunda değil, unutmayın.)</em></li><li><strong>Etkili açılış cümlesi ve bitiriş</strong> <em>(Sunum konunuzu vs. söyleyerek başlamak yerine farklı cümleler düşünün. Örneğin biz sunum konumuzla alakalı çok etkileyici bir söz bulmuştuk. Bitiriş için ise dinleyicileri harekete geçirmek için bir çağrı yapılabilir.)</em></li><li><strong>! Sunuma hazırlanmak</strong> <em>(Sunumu hazırladıktan sonra en az </em><strong><em>10</em></strong><em> defa, vaktiniz varsa 10&#39;dan daha fazla tekrar yapın. Tek başınıza veya grup arkadaşlarınıza sunun.)</em></li></ul><p>Tüm bunlardan sonra sunumumu yaptım ve liderlerden gelen güzel yorumlardan sonra benden sonrakiler sunum yapmaya devam etti. Birkaç gün sonra okul dersimde, dönem sonu sunum yapacağımızı öğrendiğimde ilk kez heyecanlandım ve mutlu oldum. O sırada aklımdan geçenleri not olarak bırakıyorum. Bu not benim dersten sonra edindiğim bilgi ve deneyimlerin sonucu olarak değişen kişisel düşüncem.</p><blockquote>“Dönem sonu sunum yapacaksak çok iyi. Erken hazırlayıp sunum gününe kadar çok tekrar yaparım. Hiçbir problem olmaz hatta benim için eğlenceli olur.”</blockquote><p>Before-After karşılaştırması da yaptıktan sonra sıradaki ders için devam edelim.</p><h3>Sunumlar ve Yazılı İçerik Hazırlama</h3><p>Bu ders boyunca önceki haftanın sunumlarından bazı sunumlar seçildi ve herkesin önünde sunumlarını tekrar yaptılar. Böylece birbirimizden daha çok fikir edinmiş olduk.</p><p>Bu seferki odağımız yazılı içerikler oldu. “Nasıl mail yazılır?” sorusundan başladık. Sürekli mail yoluyla insanlarla iletişime geçtiğimden ve mail adresimi sürekli kontrol etmemden dolayı çok aşinaydım. Bu yüzden bana pek katkısı olmadı diyebilirim. Tek bir tavsiye benim için önemliydi bu konuda. O da:</p><blockquote><strong>Sinirliyken, kızgınken, üzgünken mail atma.</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/0*TvC0WQVK5DbaOPjY.jpg" /></figure><p>Pekiştirdiğim bazı bilgilerden bahsedeyim. Öncelikle mail ekranında karşımıza çıkan “CC”, “BCC” gibi terimlere bakalım.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/599/1*qo7pdvLR3ahnqfmm7F0Tvg.jpeg" /></figure><p><strong>CC</strong> terimi Carbon Copy’nin kısaltmasıdır. Maili göndereceğiniz kişiyi belirledikten sonra CC kısmına ekleyeceğiniz kişiler, direkt alıcı olarak sayılmasa bile mail onlara da ulaşacaktır. Direkt alıcı, maile eklenen kişileri görme iznine sahiptir.</p><p><strong>BCC </strong>terimi Blind Carbon Copy’nin kısaltmasıdır. CC’nin aksine sonradan eklenen kişilerin mail adresleri gözükmez. Maili çok sayıda kişiye gönderecekseniz BCC kullanmanızı öneririm. Bunun sebepleri:</p><ol><li><strong>Birçok kişinin mail adresinin ifşa olması</strong></li><li><strong>Kaydıra kaydıra bitiremeyeceğiniz bir alıcı listesi oluşturulması</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/0*8aI-u7EtDTngGZfM.jpg" /></figure><p>Çoğu kişinin içinde gizli saklı blog yazısı yazma isteği olduğunu düşünüyorum. Benim de vardı ve bu dersten sonra körüklenmiş oldu. Ben de sizin isteğinizi körüklemenizi istiyorum. Medium’un çok basit, pratik arayüzü ile uğraşmak istemeyeceğiniz problemler karşınıza çıkmayacak ve rahat rahat yazı paylaşabileceksiniz. <strong>Özellikle anlatmaya değer deneyimleriniz olursa kesinlikle bunu blog yazısına dökmenizi tavsiye ediyorum. </strong>Bu <strong>“download” </strong>toplumundan <strong>“upload”</strong> toplumuna geçiş yapmanızı sağlayacak. Artık sadece bilgi peşinde koşan biri değil, aynı zamanda <strong>bilgi üreten</strong> biri olacaksınız.</p><p><a href="https://medium.com/yetkingencler/blog-ve-medium-yaz%C4%B1lar%C4%B1n%C4%B1z%C4%B1-daha-%C3%A7ok-ki%C5%9Fiye-ula%C5%9Ft%C4%B1rmak-i%CC%87%C3%A7in-kullanabilece%C4%9Finiz-birka%C3%A7-basit-y%C3%B6ntem-706acb37b636">Blog yazılarınızın daha çok kişiye ulaşması için birkaç yöntem içeren bu yazıyı incelemenizi öneririm.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/0*i440Y5_yRaBkNdDT.jpg" /></figure><p>Bu dersin bana en büyük katkısı blog yazmanın çok keyifli bir iş olduğunu öğretmek oldu.</p><h3>Algoritmik Düşünmeye Giriş</h3><p>Şu ana kadar en zorlandığım ders buydu. Bilgisayar mühendisliği öğrencisi olmama rağmen demek ki sınav için çözdüğüm sorular algoritmik düşünce diye bir şey oluşturmamış bende. Gruplara ayrılıp verilen sorulara en mantıklı yanıtları bulmaya çalıştık.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/0*_4G22_M0dyTYmtqo.jpg" /></figure><p>Başta dedim ya bilgisayar mühendisliği okumama rağmen… Aslında doğru, kodlama diyince ilk akla gelen algoritma. Ama o kadar da doğru bir ifade değil. Sandığınızın aksine, algoritmayla sadece bilgisayar, kodlama, yazılım üçlüsünün içindeki insanlar ilgilenmiyor. Hepimiz, belki farkında olmadan, hayatımızın her alanında algoritma kullanıyoruz.<em> “Susadım mı? Eğer susadıysam yapmam gereken su içmek. Bunun için mutfağa gidip bardak almalı ve su doldurmalıyım. Eğer susamadıysam işime devam edebilirim.” </em>İşte size algoritma.</p><blockquote><a href="https://medium.com/yetkingencler/ya%C5%9Fam%C4%B1n%C4%B1z%C4%B1n-merkezine-algoritmalar%C4%B1-koyun-eb202d45355d"><strong>Yaşamınızın Merkezine Algoritmaları Koyun!</strong></a><strong> </strong>başlıklı yazıyı incelemenizi öneririm.</blockquote><h3>EXCEL</h3><p>Excel dersi benim YetGen’de aldığım en faydalı derslerden biriydi. Biraz incelediğiniz zaman iş ilanlarının yüzde 90&#39;ının, iş tanımı bilgisayar teknolojileriyle alakası olmasa bile Excel bilgisi gerektirdiğini fark edebilirsiniz. Hatta sadece yeterli düzeyde Excel bilmek bile size iş kazandırabilir.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*EW5bLi4qbM6i44juRfn6OQ.png" /></figure><p>Excel dersinde sık kullanılan sum, count average; kontrolleri sağlamak için if, countif gibi formülleri öğrendik. Her yeni formülde pratik yapmak adına farklı farklı senaryolar için hazırlanmış tabloları kullandık. Buna ek olarak What-If ve Solver eklentisini de problemleri çözmek için kullandık.</p><p>Sadece mühendislik öğrencileri ile kısıtlamayacağım. Bu yazıyı okuyan herkese YetGen’in Youtube kanalından Excel dersini baştan sona izlemeyi ve Erhan hocayla birlikte pratikleri yaparak ilerlemeyi kesinlikle tavsiye ediyorum.</p><h3>Teknoloji Okuryazarlığı</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/0*atZydP0TFXtT0Cbb.jpg" /></figure><p>Geleceğin akıllı şehirleri, mobil uygulama geliştiricilik, kullanıcı etkileşimini artırmak için arayüz tasarımları, Blockchain, Kodluyoruz tarafından kodlama, oyun geliştiricilik, AR &amp; VR ve Büyük Veri gibi onlarca konu hakkında, bu alanlarda ortaya ürün koyan uzman kişilerin sunumlarını dinledik. Öğrenim süreçlerinden iş hayatına kadar çok fazla bilgi kattık kendimize.</p><h3>Sürdürülebilirlik ve Sosyal İnovasyon</h3><p>Yine E-Bursum, ForFarming, İmece gibi girişimlerin sunumlarını dinledik. Onarıcı yaklaşım hakkında bilgiler edindik. Sosyal inovasyon çözümleri hakkında fikirlerim oluştu. <br>Edit: Aylar sonra üniversitemin lise kolunda Sosyal İnovasyon dersi verileceğini öğrendim ve ders içeriğini hazırlamak için davet edildim :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/0*ueCeTPLbAsIyNsU4.jpg" /></figure><h3>Girişimcilik</h3><p>Küçük bir kahve standı açma simülasyonu ile girişimciliğin en basit şekliyle nasıl olacağını deneyimledik. Başlangıç, sabit ve değişken maaliyetlerin ne olduğunu simülasyon üzerinden belirledik. Kahve simülasyonu hem basit hem herkes tarafından uygulanabilir bir senaryo olduğu için ders çok zevkliydi ve girişimciliğin o zor ve imkansız görünen havasını kırmaya yönelikti. Bu derste öğrendiklerimiz GirişGen süreci için de önayak olmuş oldu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/0*LB_vMYslkxk3m84i.jpg" /></figure><h3>21. Yüzyıl Okuryazarlıkları</h3><h3>Öz Gelişim ve Aktif Vatandaşlık</h3><h3>İş Dünyasına Geçiş</h3><h3>GirişGen</h3><p><a href="https://youtu.be/5uUOygDW_u4?t=9463">https://youtu.be/5uUOygDW_u4?t=9463</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bac86a72378c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>