<?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 Albert Podraza on Medium]]></title>
        <description><![CDATA[Stories by Albert Podraza on Medium]]></description>
        <link>https://medium.com/@informatyk_A?source=rss-6eda0a348a27------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*wHHnI1iJKxiec1GV.png</url>
            <title>Stories by Albert Podraza on Medium</title>
            <link>https://medium.com/@informatyk_A?source=rss-6eda0a348a27------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:12:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@informatyk_A/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[How did I unconsciously become a senior software engineer?]]></title>
            <link>https://medium.com/@informatyk_A/how-did-i-unconsciously-become-a-senior-software-engineer-d0ff10881ea4?source=rss-6eda0a348a27------2</link>
            <guid isPermaLink="false">https://medium.com/p/d0ff10881ea4</guid>
            <category><![CDATA[senior-software-engineer]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Albert Podraza]]></dc:creator>
            <pubDate>Mon, 16 Oct 2023 22:58:17 GMT</pubDate>
            <atom:updated>2023-10-16T22:58:17.891Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KMUoIhSUWwTm4XpZEHP91Q.png" /><figcaption>DALL-E 3 copyrights</figcaption></figure><p>What makes you feel you’re a true senior engineer? I was asking this question to myself for several years. During that time it turned out I’ve marked a few ticks in some promotion processes and I’ve got my title. But I didn’t believe in those ticks — the question was still relevant, in other company I could easily lose my title or even get a better one. In general — it’s complicated, but it led me to do some kind of self review of my skill set. What is surprising, besides typical hard skills I’ve noticed I’ve grown other ones I wasn’t aware of. And I’ve started to clearly notice them in other engineers. In this article I want to present my findings. I believe it boils down to four core competencies, which can be grown more or less unconsciously:</p><ul><li>Knowledge sharing</li><li>Mentoring</li><li>Going the extra mile</li><li>Effective stakeholder management</li></ul><h3>The path</h3><p>Throughout their careers, software engineers encounter a plethora of challenges. Initially, the journey can be overwhelming — you know little, and that’s acceptable. As time progresses, you realize you’re part of a team with colleagues eager to assist. You commit to hard work and immerse yourself in learning about the surrounding ecosystem. You know you need to work on your hard skill set and you become a sponge, absorbing knowledge about the technology, company processes, communication styles, and work methodologies. Though the learning curve might plateau, your confidence grows. Depending on your environment, you may gain significant autonomy, becoming adept at navigating your workplace. Now you have expertise and you know how to tackle things. But what happens besides it?</p><h3>Knowledge sharing</h3><p>While working on upcoming requirements, you understand how to optimise tasks and which libraries can expedite the process. You recognise that this tricky pagination requirement is ok, but sacrificing a slight dip in performance can lead to a tenfold increase in implementation speed and potentially make maintenance cost five times lower. <strong>You possess a keen sense of the decisions being made around you and are proactive in sharing your insights</strong>, offering clarity and alternative solutions for your team. If it turns out it’s an organic problem and it requires preparing knowledge sharing session — you’re doing it.</p><h3>Mentoring</h3><p>Once you’re confident in your expertise and surrounded by budding less experienced engineers, <strong>it’s almost instinctive to guide them</strong>. Having faced various challenges, you can foresee potential pitfalls in a teammate’s approach. Naturally, you’d advise them, offering constructive feedback and alternatives. Over time, witnessing their growth becomes a source of pride.</p><h3>Going the extra mile</h3><p>Occasionally, you might identify and fix gaps in processes that aren’t necessarily within your purview. <strong>You have an internal motivation to do it because it just annoys you.</strong> For instance, if the business team consistently struggles to verify the functionality of your deliverables, you might proactively create a postman collection or draft documentation to streamline the process, even if it benefits more than just your team.</p><h3>Effective stakeholder management</h3><p>Furthermore, effective stakeholder management is paramount. Whether you’re mentoring or tackling tasks outside your immediate responsibilities, clear communication is crucial. This includes offering feedback to your mentees, coordinating with your manager to allocate time efficiently, or suggesting process improvements that can expedite development or testing. <strong>All activities are adequately communicated and organised and you know how to tackle it professionally.</strong> Such contributions highlight the added value you bring.</p><h3>Conclusion</h3><p>The journey to becoming a true senior engineer goes beyond mere titles or specific technical expertise. It encompasses a holistic approach to one’s career, emphasizing the importance of knowledge sharing, mentorship, initiative, and stakeholder management. As software engineers grow and navigate the intricacies of their roles, these core competencies become instrumental in defining their impact within a team and the broader organization. The true hallmark of a senior engineer is not just in mastering the craft but in uplifting others, optimising processes, and ensuring effective communication at all junctures. It’s about being proactive, insightful, and continually seeking ways to add value. Embracing these qualities not only enhances one’s professional journey but also elevates the collective strength and success of their teams.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d0ff10881ea4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Event storming for technical description of features]]></title>
            <link>https://medium.com/@informatyk_A/event-storming-for-technical-description-of-features-7691aad0ce3a?source=rss-6eda0a348a27------2</link>
            <guid isPermaLink="false">https://medium.com/p/7691aad0ce3a</guid>
            <category><![CDATA[domain-driven-design]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[eventstorming]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Albert Podraza]]></dc:creator>
            <pubDate>Sat, 16 Nov 2019 19:25:37 GMT</pubDate>
            <atom:updated>2019-11-16T19:25:37.327Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3hLVy3qirbqh1EKD27GhFw.jpeg" /></figure><p><strong>Introduction<br></strong>Recently I’ve got a chance to try Event Storming from different perspective than it’s proposed in well-known guidelines. Here, in this article I would like to share my observations. If someone is concerned if this approach could be efficient for discussion mainly among technical teammates on some lower level stuff and this text will be helpful.</p><p><strong>What is it?<br></strong>There are already many articles about what Event Storming is, so it doesn’t make sense to repeat them, I’ll just present my own, short definition.</p><blockquote>In simple words, it’s a <strong>method based on conducting a workshop, keeping <br>in mind few rules</strong>. It allows team members to clarify the initial informations about the domain they want to get familiar with. As a result technical team should be able to design high-quality software for business that provides requirements.</blockquote><p>Event Storming is usually carried out for describing high-level overview <br>for newly created systems or new versions of existing ones. It’s a tool derived from the DDD (Domain Driven Development) approach, but compared to it, it’s a simplified version with less vocabulary and simpler rules, making the entry level much more affordable.</p><p><strong>Problem<br></strong>The question is — is it possible to use Event Storming as additional tool, besides the UML diagrams to create technical solution? During development, we had problems with establishing a consistent vision of functionality and with finding all corner cases, so we spent time on additional meetings to define these cases.</p><blockquote>If the problem comes from the fact there is no deeper verification and discussion about created documentation before development, <strong>Event Storming can be worth to check!</strong></blockquote><p>Due to the complexity of the system, functionalities were often delivered <br>in parallel on multiple layers. It means that data, backend, frontend and test engineers developed their functionalities on their own. When one of colleagues spots a hole in the requirements, then team starts ad-hoc discussions about solution and other potential dangers. Sometimes the developers needed to refactor or remove their code a few times before getting final version to cover all hot spots in application, which was very <br>time-consuming. We encountered a lot of such situations during development of any more complex piece of project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/470/1*0UGCTuA9t1HfxTiQWYIGYw.jpeg" /></figure><p><strong>Experiment<br></strong>The next functionality from the roadmap was a filter mechanism for Google Slides-like application with high integration of company data. After familiarising the team with guidelines, we did a workshop. <br>Initial requirements were predefined earlier during the kick-off of the project. The goal was to create end-to-end flow for each use case scenario through all application layers and check if hours spent on additional discussions will decrease. The meeting was conducted with commonly known principles that can be easily found on the internet, starting from terminology, going through the steps until getting picture of the full solution. But, because of balance moved to technical direction, we had few differences:</p><ul><li><strong>Participants</strong>, unlike in the standard approach, i.e. business representatives, facilitator, technical representatives which in most cases are architects or senior engineers, here, besides product owner and facilitator the members were representatives of different application layers no matter what seniority, i.e.: frontend, backend, data(BI).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/546/1*gDcYYbLCNRh61GcXC0VBvg.jpeg" /><figcaption>Participants</figcaption></figure><ul><li><strong>Event granulation</strong>, according to the methodology, each event should have a business meaning, here we intentionally went lower to the technical level. The event could be e.g. a record save in the database or a GET request to the server.</li><li><strong>Flows</strong>, besides the timeline, we wanted to be aware of events and their consequences, so we linked them and commands with marker lines. <br>As a result we got something similar to swim lines in EventModelling (interesting extension of Event Storming) which were often easy <br>to translate into items (Item is added business value to the product, <br>it contains technical tasks) in the backlog.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/704/1*1yAopUZN7nWoAvRdz0uWfg.jpeg" /><figcaption>Example of connection</figcaption></figure><p><strong>Results</strong><br>After the experiment, team jumped to code prepared requirements. <br>It was noticeable, that the number of discussions and gaps in requirements was significantly lower compared to the previous features. Here are the results from all experiment, I’ve tried to share the most important facts and indicators:</p><ul><li>The implementation took 5 weeks.</li><li>It was done by 10 people, partially working remotely.</li><li>Number of items in the backlog: before workshops — 21, after — 25.</li><li>Number of modified items(added/modified tasks for items) — 9.</li><li>The percentage of total hours spent on defects gave us 8% of full estimation of feature, when the average for features in that project was 21%.</li></ul><p><strong>Conclusion</strong><br>The workshop helped the team to clarify the technical implementation on deeper level than on materials prepared by business and architects. <br>As you can see in the results, several additional corner cases have been identified and few existing scenarios were modified. It means we got the real value from the workshop! What’s more, number of defects has decreased, which allowed the team to deliver functionality faster. Backlog is not the only place we improved, UML documentation, like activity flows, interaction overflow diagrams have been also updated. At the end I want to mention about the biggest take away which in my opinion was <strong>knowledge sharing</strong>. Engineers could learn about the implementation of functionality outside of their fields, help by providing different point of view and reduce knowledge silos(single people with high domain knowledge for topic) in team.</p><p><strong>Resources</strong><br>After all there is so much to learn about Event Storming, DDD or EventModelling and many places to start! If you got interested in the topic, here are some introductory resources to help cement your understanding.</p><ol><li><a href="https://en.wikipedia.org/wiki/Event_storming">Great source of knowledge about Event Storming</a></li><li><a href="https://airbrake.io/blog/software-design/domain-driven-design">Introduction to DDD</a></li><li><a href="https://eventmodeling.org/posts/what-is-event-modeling/">EventModelling description</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7691aad0ce3a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>