<?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 Kotla Uday Kumar on Medium]]></title>
        <description><![CDATA[Stories by Kotla Uday Kumar on Medium]]></description>
        <link>https://medium.com/@udaykumarkotla01?source=rss-03a87761df68------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*B3wuH-HbO0dU_TzjD7XmUw.png</url>
            <title>Stories by Kotla Uday Kumar on Medium</title>
            <link>https://medium.com/@udaykumarkotla01?source=rss-03a87761df68------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:50:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@udaykumarkotla01/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[Combine Framework— Reactive Programming in iOS Swift — Part 1]]></title>
            <link>https://blog.stackademic.com/combine-framework-reactive-programming-in-ios-swift-part-1-3e03f30d31bd?source=rss-03a87761df68------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e03f30d31bd</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[reactive-programming]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Kotla Uday Kumar]]></dc:creator>
            <pubDate>Mon, 02 Mar 2026 20:25:56 GMT</pubDate>
            <atom:updated>2026-03-02T20:25:56.482Z</atom:updated>
            <content:encoded><![CDATA[<p>We’ve all heard about reactive programming during iOS development, especially in the early days of learning, and it naturally sparks curiosity. 🤔✨ I was in the same position too — eager to understand what it really means and how it works in real projects. 💡📱⚡️</p><p>In this blog, we’ll explore the Apple’s Combine framework, focusing on its core concepts: <strong>Publishers, Subscribers, Operators, and Subjects</strong>.</p><h3>What Is Reactive Programming?</h3><p><strong>Reactive programming</strong> is a programming paradigm focused on <strong>asynchronous data streams</strong> and how changes propagate through a system.</p><p>Instead of:</p><blockquote><em>“Call this function, then that function…”</em></blockquote><p>You think:</p><blockquote><em>“When this data changes, automatically update everything that depends on it.”</em></blockquote><p><strong>Key Concepts in reactive programming :</strong></p><ol><li><strong>Observable : </strong>Produce the events (think it is like source which emit values).</li><li><strong>Observer : </strong>Listens to the values emitted by observer.</li><li><strong>Operators : </strong>Transforms or Manipulate the data. (Map,Change, filter, or combine values before they reach the observer)</li></ol><h3>What Is Combine Then..</h3><p>Combine is a Apple’s reactive framework for handling asynchronous events over time using publishers and subscribers.</p><p><strong>Key Concepts in Combine:</strong></p><ol><li><strong>Publisher : </strong>Produce the events.</li><li><strong>Subscriber : </strong>Receives the events.</li><li><strong>Operators : </strong>Transforms or Manipulate the data. (Map, Change, filter, or combine values before they reach the observer)</li><li><strong>Subject</strong> : It is a special type of Publisher that you can manually send values to. It acts as both a <strong>Publisher</strong> and a <strong>Subscriber</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6bt9zPT6LhLfeDiIEiNDUw.png" /></figure><h3><strong>Publisher :</strong></h3><p>A <strong>Publisher</strong> is a type that emits values over time. Think of it as a stream of events. It can:</p><ol><li>Emit zero or more values</li><li>Emit a completion event (finished or failure)</li></ol><p>Every publisher has two associated types:</p><pre>Publisher.Output   // The type of value it emits<br>Publisher.Failure  // The type of error it can throw</pre><pre>let publisher = Just(5)<br>// Publisher.Output: Int <br>// Publisher.Failure : Never (it cannot fail)</pre><p>Here:</p><ul><li>Just is a built-in publisher</li><li>It emits one value</li><li>Then immediately completes</li></ul><p>Combine provides many built-in publishers like “ Just Publisher, Sequence publisher, Timer Publisher, Failure, Asynchronous publisher like URLSession.dataTaskPublisher etc… “ We will deep dive them in next articles 📝</p><h3><strong>Operators:</strong></h3><p>They allow you to Transform values, Filter values, Combine streams, Handle errors, Control timing. They return a new publisher.</p><p>Combine provides a wide range of operators, including transforming operators like map, flatMap, and tryMap; filtering operators such as compactMap and filter; and timing operators like debounce, along with many more. We will deep dive them in next articles 📝</p><pre>let newPublisher = Just(5)<br>    .map { $0 * 2 }<br>// Just(5) is a publisher that emits the value 5. <br>// When you apply .map { $0 * 2 }, <br>// it produces a new publisher that emits 10<br><br>print(newPublisher) <br>// op: Just&lt;Int&gt;(output: 10)</pre><h3><strong>Subscribe to the Publisher:</strong></h3><p>A <strong>Subscriber</strong> receives values from a publisher. To subscribe, you call <strong>sink</strong> (or assign) on the publisher. sink has two closures:</p><ol><li>receiveCompletion – called when the publisher finishes or fails.</li><li>receiveValue – called for each emitted value.</li></ol><pre>let subcription= newPublisher.sink(<br>    receiveCompletion: { completion in<br>        switch completion {<br>        case .finished: print(&quot;Finished successfully&quot;)<br>        case .failure(let error): print(&quot;Finished with error: \(error)&quot;)<br>        }<br>    },<br>    receiveValue: { value in<br>        print(&quot;Received value: \(value)&quot;)<br>    }<br>)</pre><p>Here is simple example:</p><pre>import Combine<br>let publisher = Just(5)  //Just(5) is a Publisher. It emits one value → 5<br>let newPublisher = publisher<br>    .map { $0 * 2 }  // map is an Operator. <br>                  //  It transforms the value. 5 becomes 10<br>let subcription= newPublisher.sink(<br>    receiveCompletion: { completion in<br>        switch completion {<br>        case .finished:<br>            print(&quot;Finished successfully&quot;)<br>        case .failure(let error):<br>            print(&quot;Finished with error: \(error)&quot;)<br>        }<br>    },<br>    receiveValue: { value in<br>        print(&quot;Received value: \(value)&quot;)<br>    }<br>)<br> // sink is the Subscriber. It receives the final value. Prints 10<br> // op: Received value: 10<br> //     Finished successfully</pre><pre>/**<br>Publisher (Just 5)<br>        ↓<br>Operator (multiply by 2)<br>        ↓<br>Subscriber (print result)<br>*/</pre><h3>Subjects:</h3><p><strong>Subject</strong> is a special type of publisher that lets you manually send values to subscribers.</p><p>Two main types of Subjects:</p><h3>PassthroughSubject</h3><ul><li>Sends values to subscribers</li><li>Does <strong>not</strong> keep the latest value</li><li>If no one is listening, values are lost</li><li>We don’t pass any initial value.</li></ul><pre>import Combine<br><br>let subject = PassthroughSubject&lt;String, Never&gt;() // No initial value<br><br>subject.send(&quot;Lost Value&quot;)   // No subscriber yet → value LOST <br>                             // it won&#39;t print &quot;Lost Value&quot;<br><br>let sub = subject.sink {<br>    print(&quot;Received:&quot;, $0)<br>}<br>subject.send(&quot;1st value&quot;)<br>subject.send(&quot;2nd value&quot;)<br><br>/**<br>Output: <br>Received: 1st value<br>Received: 2nd value<br>*/</pre><p>Think of it Like This</p><p>📻 PassthroughSubject = Live Radio, If you turn on the radio late, you miss what was already said.</p><h3>CurrentValueSubject</h3><ul><li>Stores the <strong>latest value</strong></li><li>New subscribers immediately receive the current value</li><li>We pass initial value.</li></ul><pre>import Combine<br><br>//we pass initial value<br>let subject = CurrentValueSubject&lt;String, Never&gt;(&quot;Initial value&quot;) <br><br>subject.send(&quot;Latest Value before subscribing&quot;) // store the value<br><br>let sub = subject.sink {<br>    print(&quot;Received:&quot;, $0) //subscriber immediately receive the current value<br>}<br>subject.send(&quot;1st value&quot;)<br>subject.send(&quot;2nd value&quot;)<br>print(&quot;Latest Value : \(subject.value)&quot;)<br><br>/**<br>Output :<br>Received: Latest Value before subscribing<br>Received: 1st value<br>Received: 2nd value<br>Latest Value : 2nd value<br>*/</pre><p>We’ll dive deeper in the <strong>next articles</strong> — stay tuned! 📚✨<br> It might not be a super short read, but it really helps you <strong>grasp Combine better</strong>. 💡</p><p>Happy coding! 💻</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e03f30d31bd" width="1" height="1" alt=""><hr><p><a href="https://blog.stackademic.com/combine-framework-reactive-programming-in-ios-swift-part-1-3e03f30d31bd">Combine Framework— Reactive Programming in iOS Swift — Part 1</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[Bench Period: Every Software Developer’s Tale of Waiting and Wonder ️⏳]]></title>
            <link>https://medium.com/write-a-catalyst/bench-period-every-software-developers-tale-of-waiting-and-wonder-%EF%B8%8F-a22c2b817bf0?source=rss-03a87761df68------2</link>
            <guid isPermaLink="false">https://medium.com/p/a22c2b817bf0</guid>
            <category><![CDATA[short-story]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[employee-experience]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[work-life-balance]]></category>
            <dc:creator><![CDATA[Kotla Uday Kumar]]></dc:creator>
            <pubDate>Sat, 28 Feb 2026 06:56:25 GMT</pubDate>
            <atom:updated>2026-02-28T06:56:25.678Z</atom:updated>
            <content:encoded><![CDATA[<p>One day, Manager told:</p><p>“The client project is on hold. You’re going on the bench.” 😳</p><p>At first, panic sets in. Bench? What does that even mean? Is this the end of a career? Should the resume be updated immediately?</p><p>This is the classic bench fear that every developer experiences at least once in their career. For a day, it feels like the world is collapsing.</p><p>Friends call:</p><ul><li>“Are you working on something?” 📞</li><li>“Or just chilling?” 😅</li></ul><p><strong>Phase 1:</strong></p><p>After staring at the chair and computer for a while, it finally clicks:</p><p><strong>Bench = free time to grow.</strong></p><p>“No deadlines. No angry clients. No surprise tickets at 11 PM. Just pure, uninterrupted time.”</p><p>The developer decides to experiment:</p><ul><li><strong>Refresh knowledge</strong>: revisit old algorithms, brush up on frameworks, solve a few coding challenges.</li><li><strong>Explore new technologies</strong>: try out AI, or even a side mini-project.</li><li><strong>Follow passions</strong>: write a blog, create tutorials, or even just play around with creative coding ideas.</li></ul><p>Suddenly, the “bench” doesn’t feel like punishment — it feels like a <strong>coding retreat</strong>.</p><p><strong>Phase 2:</strong></p><p>Weeks pass, and the developer returns to a new client project, noticing:</p><ul><li>Tasks that used to take two days &gt;&gt; now take half the time.</li><li>Confidence in interviews is higher because new skills have been learned.</li><li>Colleagues ask, “Where did you learn that?” The developer just smiles and says:</li></ul><p>“Ah… I was on the bench. I went exploring.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wQseIUPmr-9to6AClGSSRA.png" /></figure><p><strong>The Moral of the Story</strong></p><p>The bench isn’t a dead end; it’s a <strong>launchpad</strong>.</p><ul><li>Fear of bench = normal</li><li>Use bench = smart</li></ul><p><strong>Happy bench day! 😄🎉💻</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a22c2b817bf0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/write-a-catalyst/bench-period-every-software-developers-tale-of-waiting-and-wonder-%EF%B8%8F-a22c2b817bf0">Bench Period: Every Software Developer’s Tale of Waiting and Wonder 🖥️⏳</a> was originally published in <a href="https://medium.com/write-a-catalyst">Write A Catalyst</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SwiftData Basics and CRUD Operations | iOS Swift]]></title>
            <link>https://blog.stackademic.com/swiftdata-basics-and-crud-operations-9b1cbad8b0d7?source=rss-03a87761df68------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b1cbad8b0d7</guid>
            <category><![CDATA[swiftdata]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[swiftui]]></category>
            <category><![CDATA[swift]]></category>
            <dc:creator><![CDATA[Kotla Uday Kumar]]></dc:creator>
            <pubDate>Wed, 25 Jun 2025 10:04:41 GMT</pubDate>
            <atom:updated>2026-03-01T15:54:10.781Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey there! 👋 This is my very first iOS blog post, and I’m super excited to start sharing my iOS development journey and everything I’ve been learning along the way.</p><p>In this article, we’ll explore what SwiftData is, how easily it can be integrated into your iOS applications, and how it simplifies data management in SwiftUI. By the end of this post, you’ll have a solid understanding of the basics of SwiftData and be able to build a simple CRUD-based app using it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/686/0*90cRsURML-TqsqmH.jpeg" /></figure><p><strong>Table of Contents :</strong></p><ol><li>What is SwiftData?</li><li>Setting Up SwiftData in Your Project</li><li>Creating a Model</li><li>CRUD Operations</li><li>Sample App and Demo</li></ol><p><strong>What is SwiftData?</strong></p><p>SwiftData is framework introduced by Apple in WWDC 2023 as a new Data Persistence framework. SwiftData modern alternative to CoreData framework.It offers a simpler, more declarative way to manage model data.</p><ol><li>Less boilerplate code — define models using @Model without complex setup.</li><li>Easy to integrate — just a few lines to set up in your SwiftUI app.</li><li>Changes to your model automatically reflect in the UI.</li></ol><p><strong>Setting Up SwiftData in Your Project</strong></p><blockquote>Requirements : Xcode 15 or later, and runs on iOS 17, macOS 14, or newer.</blockquote><p>Note: Don’t forgot to import SwiftData on required files 🪄😅</p><p><strong>Creating a Model</strong></p><blockquote>To define a Model Class we use @Model macro</blockquote><p>@Model macro tells SwiftData that this class should be stored and managed by the data persistence system. It automatically conforms model class to protocols like Identifiable, Hashable, ObservableObject, or Codable.</p><pre>import SwiftData<br><br>@Model<br>class Player{<br>  var name : String<br>  var score : Int<br><br>  init(name: String, score: Int) {<br>    self.name = name<br>    self.score = score<br>  }<br>}</pre><p>Add the modelContainer now…</p><p>modelContainer is the main persistence container in SwiftData.<br> The .modelContainer(for:) modifier specifies which data models should be stored and managed by SwiftData.</p><pre>struct ScoreCardApp: App {<br>    var body: some Scene {<br>        WindowGroup {<br>            ContentView()<br>            .modelContainer(for: Player.self)<br>        }<br>    }<br>}</pre><p><strong>CRUD Operations:</strong></p><p>Before performing any CRUD operations in SwiftData, you need to access the data context and load the model data into your view.</p><pre>@Environment(\.modelContext) private var context<br>@Query private var players: [Player]</pre><p><em>@Environment(\.modelContext)</em> : This gives you access to the context, which is used to insert, update, delete, and save your data.</p><p>@Query : This automatically fetches all Player model objects and keeps the list updated in real time.</p><p><strong>Create new data</strong></p><p>step 1: creates a new instance of the Player model.</p><p>step 2 : Inform the SwiftData’s model context adds the new player to the current persistence.</p><pre>let newPlayer = Player(name: newName, score: score)<br>context.insert(newPlayer)</pre><p><strong>Read the data</strong></p><p>You can directly fetch data from the @Query private var players: [Player]</p><pre>ForEach(players) { player in<br>  Text(player.name)<br>     .font(.headline)<br>}</pre><p><strong>Update the data</strong></p><p>To update data, simply access the item you want and modify its properties just like any regular Swift variable (e.g., strings, integers). You don’t need to call context.save()</p><p>SwiftData automatically tracks and saves your changes.</p><pre>selectedPlayer.name = newName<br>selectedPlayer.score = newScore</pre><p><strong>Delete the data</strong></p><p>To delete the data, simply access the item you want to delete and call context.delete()</p><pre>context.delete(players[2])</pre><p><strong>Sample App and Demo:</strong></p><p><strong>Note :</strong> The logic presented here is simplified for demonstration purposes and may not be fully optimized code…😃</p><pre>//<br>//  PlayerDashboardView.swift<br>//  ScoreCard<br>//<br>//  Created by Uday Kumar Kotla on 23/06/25.<br>//<br><br>import SwiftUI<br>import SwiftData<br><br>struct PlayerDashboardView: View {<br>    @Environment(\.modelContext) private var context<br>    @Query private var players: [Player]<br><br>    @State private var showingAddAlert = false<br>    @State private var showingUpdateAlert = false<br>    @State private var newName = &quot;&quot;<br>    @State private var playerScore = &quot;&quot;<br>    @State private var selectedPlayer: Player?<br><br>    var body: some View {<br>        NavigationView {<br>            List {<br>                ForEach(players) { player in<br>                    VStack(alignment: .leading) {<br>                        Text(player.name)<br>                            .font(.headline)<br>                        Text(&quot;Score: \(player.score)&quot;)<br>                            .font(.subheadline)<br>                            .foregroundColor(.gray)<br>                    }<br>                    .onTapGesture {<br>                        selectedPlayer = player<br>                        newName = player.name<br>                        playerScore = String(player.score)<br>                        showingUpdateAlert = true<br>                    }<br>                }<br>                .onDelete(perform: deletePlayer)<br>            }<br>            .navigationTitle(&quot;Players&quot;)<br>            .toolbar {<br>                ToolbarItem(placement: .navigationBarTrailing) {<br>                    Button {<br>                        newName = &quot;&quot;<br>                        playerScore = &quot;&quot;<br>                        showingAddAlert = true<br>                    } label: {<br>                        Image(systemName: &quot;plus&quot;)<br>                    }<br>                }<br>            }<br>            .alert(&quot;Add Player&quot;, isPresented: $showingAddAlert, actions: addPlayerAlert, message: {<br>                Text(&quot;Enter the player&#39;s name and score&quot;)<br>            })<br>            .alert(&quot;Update Player&quot;, isPresented: $showingUpdateAlert, actions: updatePlayerAlert, message: {<br>                Text(&quot;Update the player&#39;s name and score&quot;)<br>            })<br>        }<br>    }<br><br>    private func addPlayerAlert() -&gt; some View {<br>        Group {<br>            TextField(&quot;Name&quot;, text: $newName)<br>            TextField(&quot;Score&quot;, text: $playerScore)<br>                .keyboardType(.numberPad)<br><br>            Button(&quot;Add&quot;) {<br>                guard !newName.isEmpty,<br>                      let score = Int(playerScore) else { return }<br>                let newPlayer = Player(name: newName, score: score)<br>                context.insert(newPlayer)<br>            }<br>            Button(&quot;Cancel&quot;, role: .cancel) { }<br>        }<br>    }<br><br>    private func updatePlayerAlert() -&gt; some View {<br>        Group {<br>            TextField(&quot;Name&quot;, text: $newName)<br>            TextField(&quot;Score&quot;, text: $playerScore)<br>                .keyboardType(.numberPad)<br><br>            Button(&quot;Update&quot;) {<br>                guard let selectedPlayer = selectedPlayer else { return }<br>              guard !newName.isEmpty,<br>                      let score = Int(playerScore) else { return }<br><br>              selectedPlayer.name = newName<br>              selectedPlayer.score = score<br>            }<br>            Button(&quot;Cancel&quot;, role: .cancel) { }<br>        }<br>    }<br><br>    private func deletePlayer(at offsets: IndexSet) {<br>        for index in offsets {<br>            context.delete(players[index])<br>        }<br>    }<br>}<br><br>#Preview {<br>    PlayerDashboardView()<br>}<br></pre><p><strong>Demo :</strong> <a href="https://youtube.com/shorts/o_bnujlFk9I?feature=share">https://youtube.com/shorts/o_bnujlFk9I?feature=share</a></p><p>Happy Coding….!😉</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b1cbad8b0d7" width="1" height="1" alt=""><hr><p><a href="https://blog.stackademic.com/swiftdata-basics-and-crud-operations-9b1cbad8b0d7">SwiftData Basics and CRUD Operations | iOS 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>
    </channel>
</rss>