<?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 Akhil Reddy on Medium]]></title>
        <description><![CDATA[Stories by Akhil Reddy on Medium]]></description>
        <link>https://medium.com/@madaakhilreddy?source=rss-77ec3f107e8b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*fIJASZQRpQ8n8rnVvCngqQ.jpeg</url>
            <title>Stories by Akhil Reddy on Medium</title>
            <link>https://medium.com/@madaakhilreddy?source=rss-77ec3f107e8b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 04:15:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@madaakhilreddy/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[DAY 58 — Connecting Architecture Diagrams With Documentation]]></title>
            <link>https://medium.com/@madaakhilreddy/day-58-connecting-architecture-diagrams-with-documentation-c0dbdcb5db06?source=rss-77ec3f107e8b------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0dbdcb5db06</guid>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[payroll]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[hr]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Akhil Reddy]]></dc:creator>
            <pubDate>Tue, 27 Oct 2026 18:01:53 GMT</pubDate>
            <atom:updated>2026-10-27T18:01:53.891Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yy7OqvGA2mS13JBjJUf18A.png" /></figure><p>Today was another day of working on system architecture documentation, but this time, my focus was on organizing everything properly and making the different pieces connect.</p><p>As I continue learning about software architecture, I’m realizing that creating a design is only one part of the work. Making that design accessible, understandable, and properly documented is equally important.</p><h3>Organizing Architecture Documentation</h3><p>Today, I worked on organizing the system architecture documentation in <strong>Azure DevOps Wiki</strong>.</p><p>The goal was to keep the documentation structured so that the architecture information could be understood and referred to more easily.</p><p>While working on this, I also explored how to link Architecture Decision Records (ADRs) to the appropriate Wiki pages.</p><p>ADRs help document important architectural decisions, including why a particular approach was chosen. Connecting these records with the main documentation makes it easier to understand not just what the system looks like, but also the reasoning behind its design.</p><h3>Connecting Diagrams and Documentation</h3><p>Another part of today’s work involved uploading the architecture PDF to the diagrams folder and working on connecting it with the Excalidraw diagram and Wiki documentation.</p><p>I worked with three pieces:</p><ul><li>The architecture PDF</li><li>The editable Excalidraw diagram</li><li>The Azure DevOps Wiki documentation</li></ul><p>Although these serve different purposes, they need to work together.</p><p>A diagram provides a visual overview, a PDF offers a convenient reference, and the Wiki provides a place to organize the supporting explanations and links.</p><p>Getting these connections right makes the documentation more useful for anyone trying to understand the system.</p><h3>What I Learned Today</h3><p>Today’s work reminded me that <strong>good architecture documentation is more than a collection of diagrams and files</strong>.</p><p>The information needs to be organized, the references need to be connected, and important decisions need to be easy to find.</p><p>I’m also beginning to appreciate the work that happens around software development beyond writing code. Maintaining clear technical documentation helps teams share knowledge and understand the reasoning behind a system’s design.</p><p>It’s a different kind of engineering work, but an important one.</p><p>This article is part of my <strong>365 Days of Becoming a Software Engineer</strong>, where I document my real internship journey — the good days, the difficult days, and everything in between.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0dbdcb5db06" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DAY 57 — Understanding Architecture Beyond the Code]]></title>
            <link>https://medium.com/@madaakhilreddy/day-57-understanding-architecture-beyond-the-code-ba74abfa877c?source=rss-77ec3f107e8b------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba74abfa877c</guid>
            <category><![CDATA[hr]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[blogging]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Akhil Reddy]]></dc:creator>
            <pubDate>Thu, 22 Oct 2026 14:52:37 GMT</pubDate>
            <atom:updated>2026-10-22T14:52:37.932Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6FYJxiJ4LQMa3ASA0mgWzA.png" /></figure><p>Today was a day of going deeper into software architecture and revisiting the fundamentals that help make a system maintainable, secure, and easier to understand.</p><p>Instead of focusing on writing new code, I spent time studying project documentation, organizing my understanding, and preparing revision notes.</p><h3>Exploring Software Architecture</h3><p>I studied the project documentation, focusing on several important concepts:</p><ul><li><strong>Architecture and Vertical Slices</strong></li><li><strong>Pragmatic Layering</strong></li><li><strong>Identity and Authentication</strong></li><li><strong>Authorization and Access Control</strong></li></ul><p>These concepts helped me think about software from a broader perspective.</p><p>When we start learning development, it’s easy to focus mainly on writing functions, connecting APIs, and making features work. But in a larger application, there’s another important question: how should everything be organized so the system remains understandable and maintainable?</p><p>That’s where architecture comes in.</p><h3>Understanding Authentication and Authorization</h3><p>One of the areas I revisited was the difference between authentication and authorization.</p><p>Although they sound similar, they solve different problems.</p><p><strong>Authentication answers: “Who are you?”</strong></p><p><strong>Authorization answers: “What are you allowed to do?”</strong></p><p>Identity, authentication, authorization, and access control work together to help applications manage users and protect resources.</p><p>Understanding these distinctions is especially important when working with applications that have different user roles and permissions.</p><p>I also explored vertical slices and pragmatic layering, which offer different ways to organize application functionality and responsibilities.</p><p>I’m still building my understanding of how these ideas fit together, but studying them through the project documentation makes the concepts feel more practical than learning definitions alone.</p><h3>Creating Revision Notes</h3><p>I also prepared <strong>Day 1 revision notes</strong>, covering the key concepts and checkpoint questions.</p><p>Creating revision notes gave me a chance to organize what I had studied and identify the concepts I need to remember clearly.</p><p>I’ve realized that reading something once doesn’t necessarily mean I’ve understood it well enough to explain it. Revisiting the material and testing myself with questions helps reveal where my understanding is strong and where I need more practice.</p><h3>Learning Beyond Documentation</h3><p>Alongside the architecture study, I watched a YouTube video as part of my continued learning.</p><p>I find that combining documentation with other learning resources gives me different ways to approach a topic and reinforces the ideas I’m trying to understand.</p><h3>What I Learned Today</h3><p>Today’s work reminded me that software engineering is not just about making code work.</p><p>It’s also about understanding how an application is structured, how responsibilities are separated, and how identity and permissions are managed securely.</p><p>I’m learning to look beyond individual features and pay more attention to the design decisions that shape an entire application.</p><p><em>This article is part of my </em><strong><em>365 Days of Becoming a Software Engineer</em></strong><em>, where I document my real internship journey — the good days, the difficult days, and everything in between.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba74abfa877c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DAY 56 — From Payroll Documentation to Understanding the Code]]></title>
            <link>https://medium.com/@madaakhilreddy/day-56-from-payroll-documentation-to-understanding-the-code-215177f26647?source=rss-77ec3f107e8b------2</link>
            <guid isPermaLink="false">https://medium.com/p/215177f26647</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[database]]></category>
            <category><![CDATA[payroll-software]]></category>
            <category><![CDATA[payroll]]></category>
            <category><![CDATA[hr]]></category>
            <dc:creator><![CDATA[Akhil Reddy]]></dc:creator>
            <pubDate>Tue, 13 Oct 2026 14:26:13 GMT</pubDate>
            <atom:updated>2026-10-13T14:26:13.117Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DB04wWkyOHBCyyTRFo1TJA.png" /></figure><p>Today was a little different from my usual documentation and training sessions.</p><p>I spent time reviewing the payroll inputs presentation and then moved closer to the technical side of the system by exploring the payroll module’s code.</p><p>It was a good opportunity to connect what I was learning about payroll with how those concepts are implemented in software.</p><h3>Revisiting the Payroll Inputs</h3><p>I went through the <strong>HRMS V3 Payroll Inputs PPT</strong> to strengthen my understanding of the information required for payroll processing.</p><p>Learning about payroll inputs is one thing, but understanding how those inputs influence the final calculations is another.</p><p>This review helped me connect the business side of payroll with the technical processes happening behind the scenes.</p><h3>Exploring the CPF Calculation Logic</h3><p>The main technical focus today was going through the <strong>payroll module’s code to understand the calculations and logic used for Singapore’s Central Provident Fund (CPF)</strong>.</p><p>Until now, much of my learning has involved training materials, documentation, and understanding workflows. Looking at the code gave me a different perspective.</p><p>Instead of only learning what the system does, I started exploring how the logic is implemented.</p><p>CPF calculations involve rules and conditions that need to be handled carefully. Understanding how those rules translate into code is important because payroll calculations must follow the applicable requirements.</p><p>I focused on understanding the existing implementation rather than just looking at individual lines of code.</p><p>It reminded me that working with an established application often means first understanding the decisions and logic behind what has already been built.</p><h3>Connecting Business Rules With Code</h3><p>Today’s work helped me see the connection between three things:</p><ul><li><strong>Business requirements:</strong> What the payroll process needs to achieve.</li><li><strong>Calculation rules:</strong> How the relevant payroll values are determined.</li><li><strong>Code implementation:</strong> How those rules are translated into executable logic.</li></ul><p>These pieces need to work together for the system to produce the expected results.</p><p>As a developer, understanding the code alone isn’t always enough. You also need to understand why the logic exists and what requirements it is intended to satisfy.</p><h3>What I Learned Today</h3><p>Today was a useful step toward understanding payroll from a developer’s perspective.</p><p>Reviewing the presentation strengthened my understanding of the inputs, while exploring the code helped me look at the calculations behind the system.</p><p>I’m gradually moving beyond understanding what a feature does and starting to investigate how it works internally.</p><p><em>This article is part of my </em><strong><em>365 Days of Becoming a Software Engineer</em></strong><em>, where I document my real internship journey — the good days, the difficult days, and everything in between.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=215177f26647" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DAY 55 — Going Beyond the Basics of Payroll]]></title>
            <link>https://medium.com/@madaakhilreddy/day-55-going-beyond-the-basics-of-payroll-e83c408a9966?source=rss-77ec3f107e8b------2</link>
            <guid isPermaLink="false">https://medium.com/p/e83c408a9966</guid>
            <category><![CDATA[payroll]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[payroll-software]]></category>
            <category><![CDATA[salary]]></category>
            <category><![CDATA[hr]]></category>
            <dc:creator><![CDATA[Akhil Reddy]]></dc:creator>
            <pubDate>Tue, 13 Oct 2026 13:35:29 GMT</pubDate>
            <atom:updated>2026-10-13T13:35:29.743Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ofFnPkTsugUcEkTXAgjQhw.png" /></figure><p>Today was another day of learning, with a focus on understanding payroll in more depth.</p><p>I continued with the payroll training and attended a presentation about the higher-level payroll process and the inputs required to make it work.</p><h3>Continuing Payroll Part 1</h3><p>I spent time watching the <strong>Payroll Part 1 training session</strong>.</p><p>As I continue exploring the payroll system, I’m gradually getting a better understanding of how its different processes fit together.</p><p>At first, payroll might sound like a straightforward calculation: determine an employee’s earnings, subtract deductions, and arrive at the final salary. But the actual process involves much more than that.</p><p>There are inputs, configurations, rules, and validations that need to be considered before the final results can be generated.</p><p>The training is helping me build that foundation step by step.</p><h3>Understanding the Higher-Level Payroll Process</h3><p>I also attended a presentation about the <strong>higher-level payroll process and its inputs</strong>.</p><p>This gave me an opportunity to look at payroll from a broader perspective rather than focusing only on individual screens or features.</p><p>Understanding the inputs is particularly important because the output of a payroll process depends on the information provided to it. If the inputs are incomplete or incorrect, the results can be affected.</p><p>It made me think about how much coordination happens behind a process that might look simple to an end user.</p><h3>What I Learned Today</h3><p>Today’s learning helped me connect the basics with the bigger picture.</p><p>The training gave me more context about the payroll system, while the presentation helped me think about the overall process and the information it depends on.</p><p>I’m realizing that working with enterprise software requires more than understanding how a feature works. You also need to understand the business process behind it and how different inputs influence the final outcome.</p><p><em>This article is part of my </em><strong><em>365 Days of Becoming a Software Engineer</em></strong><em>, where I document my real internship journey — the good days, the difficult days, and everything in between.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e83c408a9966" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DAY 54 — Looking Beyond the Screens: Security and Database Structure]]></title>
            <link>https://medium.com/@madaakhilreddy/day-54-looking-beyond-the-screens-security-and-database-structure-cac8145fd1a5?source=rss-77ec3f107e8b------2</link>
            <guid isPermaLink="false">https://medium.com/p/cac8145fd1a5</guid>
            <category><![CDATA[payroll]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[database]]></category>
            <category><![CDATA[csharp]]></category>
            <category><![CDATA[access-control]]></category>
            <dc:creator><![CDATA[Akhil Reddy]]></dc:creator>
            <pubDate>Sat, 10 Oct 2026 07:48:51 GMT</pubDate>
            <atom:updated>2026-10-10T07:48:51.554Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3NaPY7CACVnm_vUmccF1TA.png" /></figure><p>I spent time understanding security and access control, followed by a discussion about identifying the database tables related to the payroll module. These activities gave me a better perspective on how an enterprise application works behind the scenes.</p><h3>Understanding Security and Access Control</h3><p>I started by watching the <strong>Security and Access Control training video</strong>.</p><p>Security is an important part of any application, especially when it handles sensitive information. It’s not just about logging in; it’s also about controlling what different users can access and what actions they are allowed to perform.</p><p>The training helped me focus on the importance of managing access properly within a system.</p><p>As I continue learning about enterprise applications, I’m realizing that features need to work correctly, but they also need to be protected by appropriate access controls.</p><h3>Exploring the Payroll Database</h3><p>Later, I had a meeting with the team to review and identify the <strong>database tables related to the payroll module</strong>.</p><p>This gave me an opportunity to look beyond the application interface and focus on how the underlying data is organized.</p><p>When using an application, we usually see forms, buttons, and reports. Behind those screens, however, data is stored and connected through database tables.</p><p>Understanding which tables relate to payroll is an important step toward understanding how the module is structured.</p><p>It also reminded me that learning an existing system requires looking beyond its visible functionality. Sometimes, understanding the database gives you a much clearer picture of what’s happening underneath.</p><h3>What I Learned Today</h3><p>Today’s work helped me connect two important aspects of software engineering: <strong>security and data structure</strong>.</p><p>Security determines who can access information and perform actions, while the database provides the structure for storing and organizing that information.</p><p>I’m gradually learning to look at applications from different angles instead of focusing only on what appears on the screen.</p><p>There’s still more to understand, but every training session and technical discussion helps me build a clearer picture of the system.</p><p><em>This article is part of my </em><strong><em>365 Days of Becoming a Software Engineer</em></strong><em>, where I document my real internship journey — the good days, the difficult days, and everything in between.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cac8145fd1a5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DAY 53 — Documenting Payroll Processes and Revisiting the Portal Admin]]></title>
            <link>https://medium.com/@madaakhilreddy/day-53-documenting-payroll-processes-and-revisiting-the-portal-admin-fe5053d7f03b?source=rss-77ec3f107e8b------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe5053d7f03b</guid>
            <category><![CDATA[evernote]]></category>
            <category><![CDATA[payroll]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[blogging]]></category>
            <dc:creator><![CDATA[Akhil Reddy]]></dc:creator>
            <pubDate>Wed, 07 Oct 2026 17:05:17 GMT</pubDate>
            <atom:updated>2026-10-07T17:05:17.366Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BAD8DGI09TK-0QjM8WLhyw.png" /></figure><p>Today was another mix of documentation and system learning.</p><h3>Improving the Payroll Process Documentation</h3><p>I continued working on the Payroll Process documentation in Evernote.</p><p>Instead of only adding text, I also worked on improving the existing documentation by adding relevant images.</p><p>Adding images makes the documentation easier to follow because it connects the written explanation with what the actual process looks like.</p><p>While making these changes, I also had to think about how the information should be organized so that someone reading it later can understand the process without getting lost.</p><h3>Revisiting the Portal Admin Meeting</h3><p>Alongside the documentation work, I started watching the Portal Admin meeting video.</p><p>This gave me another opportunity to revisit the administrative side of the HRMS and understand the discussions and workflows in more detail.</p><p>I’ve already seen parts of this system earlier, but going through the meeting again while having more background knowledge feels different.</p><p>Things that seemed unfamiliar before are starting to make more sense now.</p><h3>What I Learned Today</h3><p>Today’s work reminded me that documentation and learning go hand in hand.</p><p>When I document a process, I have to understand it clearly.</p><p>When I revisit an old meeting or training session, I often understand things differently because I’ve learned more since the first time.</p><p>The more I revisit and connect these pieces, the clearer the bigger system becomes.</p><p><em>This article is part of my 365 Days of Becoming a Software Engineer, where I document my real internship journey — the good days, the difficult days, and everything in between.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe5053d7f03b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DAY 52 — Documenting Payroll: Export and Settings]]></title>
            <link>https://medium.com/@madaakhilreddy/day-52-documenting-payroll-export-and-settings-0ffda9467871?source=rss-77ec3f107e8b------2</link>
            <guid isPermaLink="false">https://medium.com/p/0ffda9467871</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[blogging]]></category>
            <category><![CDATA[payroll-software]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[csharp]]></category>
            <dc:creator><![CDATA[Akhil Reddy]]></dc:creator>
            <pubDate>Tue, 06 Oct 2026 18:22:10 GMT</pubDate>
            <atom:updated>2026-10-06T18:22:10.552Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lRQsjhxXZo6JvI9hqHmoHQ.png" /></figure><p>I continued working through the payroll module and documenting what I was learning in <strong>Evernote</strong>.</p><h3>Documenting Export</h3><p>My first focus today was the <strong>Payroll Export</strong> section.</p><p>Going through this part helped me understand how payroll-related information can be prepared and exported from the system.</p><p>While documenting it, I focused on organizing the information clearly so that it can be referred to later instead of leaving it as scattered notes.</p><h3>Moving Into Settings</h3><p>After Export, I worked on documenting the <strong>Payroll Settings</strong> section.</p><p>Settings are one of those areas that can look simple from the outside, but they can have an important impact on how a system behaves.</p><p>Documenting this section gave me another opportunity to understand the configuration side of payroll and how different options fit into the overall module.</p><h3>Another Step in the Documentation Journey</h3><p>At this point, I’ve worked through several different payroll areas — Entries, Reports, Export, and Settings.</p><p>Each section adds another piece to the bigger picture.</p><p>The work may feel repetitive sometimes, but I’m realizing that going through each module carefully is helping me understand the system much better than simply trying to learn everything at once.</p><p><em>This article is part of my </em><strong><em>365 Days of Becoming a Software Engineer</em></strong><em>, where I document my real internship journey — the good days, the difficult days, and everything in between.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0ffda9467871" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DAY 51 — Turning Payroll Reports Into Clear Documentation]]></title>
            <link>https://medium.com/@madaakhilreddy/day-51-turning-payroll-reports-into-clear-documentation-1abcf6fd4ef8?source=rss-77ec3f107e8b------2</link>
            <guid isPermaLink="false">https://medium.com/p/1abcf6fd4ef8</guid>
            <category><![CDATA[payroll-system-software]]></category>
            <category><![CDATA[hr]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Akhil Reddy]]></dc:creator>
            <pubDate>Mon, 05 Oct 2026 19:32:04 GMT</pubDate>
            <atom:updated>2026-10-05T19:32:04.037Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DZacqgSC141JbLEq9IZ59g.png" /></figure><p>Today was another documentation-focused day.</p><p>After working on <strong>Payroll Entries</strong> previously, I continued documenting the payroll side of the system in Evernote.</p><h3>Documenting Payroll Reports</h3><p>My main focus today was the <strong>Payroll Reports</strong> section.</p><p>I worked through the information and organized the details into documentation that can be referred to later.</p><p>Reports are an important part of any system because they turn the data already present in the application into something useful for understanding and decision-making.</p><p>While documenting this section, I also got another opportunity to understand how the payroll information comes together from a different perspective.</p><h3>Moving to the Next Sub-Modules</h3><p>After working on Payroll Reports, I started documenting the <strong>next payroll sub-modules</strong> in Evernote.</p><p>This has become a gradual process for me.</p><p>One module at a time, I’m going through the system, understanding what each part does, and then converting that understanding into structured documentation.</p><p>It may seem like slow progress, but working this way is helping me build a much clearer picture of the overall payroll system.</p><h3>What I Learned Today</h3><p>Today’s work reminded me that documentation isn’t just about writing notes.</p><p><strong>To document something properly, you first have to understand it.</strong></p><p>Every module I work through gives me another piece of the bigger picture.</p><p>Payroll Entries yesterday. Payroll Reports today. And another set of modules waiting next.</p><p><em>This article is part of my </em><strong><em>365 Days of Becoming a Software Engineer</em></strong><em>, where I document my real internship journey — the good days, the difficult days, and everything in between.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1abcf6fd4ef8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DAY 50 — Turning Payroll Knowledge Into Documentation]]></title>
            <link>https://medium.com/@madaakhilreddy/day-50-turning-payroll-knowledge-into-documentation-9bd97124c8f8?source=rss-77ec3f107e8b------2</link>
            <guid isPermaLink="false">https://medium.com/p/9bd97124c8f8</guid>
            <category><![CDATA[learning-in-public]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[payroll-system]]></category>
            <category><![CDATA[technical-documentation]]></category>
            <category><![CDATA[hr-technology]]></category>
            <dc:creator><![CDATA[Akhil Reddy]]></dc:creator>
            <pubDate>Mon, 05 Oct 2026 19:26:06 GMT</pubDate>
            <atom:updated>2026-10-05T19:26:06.449Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PsmpBtLOcSUqSz0dPak10Q.png" /></figure><p>Day 50 was another documentation-focused day.</p><p>After spending the previous days going through payroll training and understanding the system from a functional perspective, I continued by documenting what I was learning.</p><h3>Documenting Payroll Entries</h3><p>My main focus today was the <strong>Payroll Entries documentation</strong>.</p><p>I worked on organizing the information and documenting the details in <strong>Evernote</strong>.</p><p>While doing this, I realized that documentation is also a way of learning.</p><p>When I have to organize a process clearly, I need to understand what each part means and how the different pieces connect. Things that might seem simple while watching a training session become much clearer when I try to document them properly.</p><h3>Moving to the Next Sub-Modules</h3><p>After working on the Payroll Entries documentation, I started documenting the <strong>next set of payroll sub-modules</strong> in Evernote.</p><p>It felt like moving from one chapter to the next.</p><p>The payroll system has many different areas, and going through them one by one is helping me gradually build a bigger picture of how everything fits together.</p><p>I’m learning that understanding a large enterprise system doesn’t happen in one day.</p><p>It’s built slowly — one module, one workflow, and one piece of documentation at a time.</p><h3>What I Learned Today</h3><p>Today’s work reminded me that <strong>documentation isn’t just about recording information</strong>.</p><p>It forces me to understand what I’m learning well enough to explain and organize it.</p><p>After completing one section and starting the next, I can see how much my understanding of the payroll system has grown compared with when I first started exploring it.</p><p><em>This article is part of my </em><strong><em>365 Days of Becoming a Software Engineer</em></strong><em>, where I document my real internship journey — the good days, the difficult days, and everything in between.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9bd97124c8f8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DAY 49 — Going Deeper Into Payroll and Understanding Project Progress]]></title>
            <link>https://medium.com/@madaakhilreddy/day-49-going-deeper-into-payroll-and-understanding-project-progress-255f6846f71d?source=rss-77ec3f107e8b------2</link>
            <guid isPermaLink="false">https://medium.com/p/255f6846f71d</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[payroll]]></category>
            <category><![CDATA[hris]]></category>
            <category><![CDATA[blogging]]></category>
            <category><![CDATA[internships]]></category>
            <dc:creator><![CDATA[Akhil Reddy]]></dc:creator>
            <pubDate>Mon, 28 Sep 2026 15:33:30 GMT</pubDate>
            <atom:updated>2026-09-28T15:33:30.967Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_JFtyayqU1ZHM6spDphuQA.png" /></figure><p>Today was a little different from the usual training days.</p><p>I continued learning through the <strong>payroll system training videos</strong>, but the day also included an important team discussion about the progress of our ongoing project.</p><h3>Continuing Payroll Training</h3><p>I reviewed more of the <strong>payroll training videos</strong> today.</p><p>After going through the Setup and earlier Payroll sessions, I’m gradually getting a better understanding of how the payroll side of an HRMS works.</p><p>The more I learn, the more I realize that payroll isn’t just about calculating salary. There are configurations, processes, validations, and different pieces that need to work together.</p><p>Each training session adds another piece to that understanding.</p><h3>An Unexpected Project Discussion</h3><p>The team also had a meeting to discuss the <strong>progress of the ongoing project</strong>.</p><p>The meeting happened following a change in the team structure related to project-progress management and oversight. Because of that change, the team needed to discuss the current status of the work, what had been completed, and how the project should move forward.</p><p>For me, this was an interesting experience because it showed me something that isn’t usually visible when you’re learning software engineering through courses.</p><p><strong>Project progress has to be tracked and communicated clearly.</strong></p><p>It’s not enough for work to happen in the background. Teams need visibility into what has been completed, what is still pending, and what needs attention.</p><h3>A Different Kind of Learning</h3><p>Today’s meeting gave me a perspective that technical training alone cannot provide.</p><p>I’m learning not only about HRMS and payroll, but also about how software projects are managed, how teams communicate progress, and how changes in project responsibilities can affect the way a team works.</p><p>It reminded me that becoming a software engineer isn’t only about improving technical skills.</p><p>It’s also about understanding <strong>responsibility, communication, ownership, and teamwork</strong>.</p><h3>What I Learned Today</h3><p>Today brought together two very different types of learning.</p><p><strong>The training helped me understand the system. The meeting helped me understand the importance of managing the work around that system.</strong></p><p>Both are part of the same journey.</p><p><em>This article is part of my </em><strong><em>365 Days of Becoming a Software Engineer</em></strong><em>, where I document my real internship journey — the good days, the difficult days, and everything in between.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=255f6846f71d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>