<?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 Lahiru Cooray on Medium]]></title>
        <description><![CDATA[Stories by Lahiru Cooray on Medium]]></description>
        <link>https://medium.com/@lahiru-himasha?source=rss-9d5e616fd3e9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*WJUVSZEnb-LQRPRdtR8mvg.jpeg</url>
            <title>Stories by Lahiru Cooray on Medium</title>
            <link>https://medium.com/@lahiru-himasha?source=rss-9d5e616fd3e9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 18:03:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lahiru-himasha/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 to Demotivate Your Best Employees]]></title>
            <link>https://lahiru-himasha.medium.com/how-to-demotivate-your-best-employees-9842f7e09b80?source=rss-9d5e616fd3e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/9842f7e09b80</guid>
            <dc:creator><![CDATA[Lahiru Cooray]]></dc:creator>
            <pubDate>Mon, 18 May 2026 05:26:52 GMT</pubDate>
            <atom:updated>2026-05-18T05:26:52.624Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mNmLutN57L4rzb0OcDceIA.png" /></figure><p>Want to slowly push away your most capable, loyal, and passionate employees?</p><p>Here’s a surprisingly effective playbook many organizations unknowingly follow.</p><p>Start by promoting toxic high performers.</p><p>Especially the ones who consistently achieve results while leaving behind poor collaboration, low morale, and unhealthy team dynamics.</p><p>Over time, this sends a subtle but powerful message:<br>results matter more than behavior.</p><p>Continue talking about culture and values — just avoid reinforcing them through everyday decisions.</p><p>Prioritize visibility over contribution.<br>Communication style over competence.<br>Short-term delivery over long-term team health.</p><p>Assign capable teams to leaders who may excel operationally but struggle to build trust, develop people, or create psychologically safe environments.</p><p>Promote “who is right” instead of “what is right.”</p><p>Allow ego, hierarchy, and politics to overpower truth, collaboration, and outcomes. Reward people who win arguments instead of people who solve problems.</p><p>Make important decisions without involving the people closest to the work. Limit growth opportunities for your strongest employees while expecting continued ownership and motivation.</p><p>Most organizations don’t intentionally create these environments.</p><p>In fact, many companies genuinely care about culture.</p><p>But culture is rarely defined by posters, presentations, or leadership slogans.</p><p>It is usually defined by:</p><ul><li>who gets promoted,</li><li>what behaviors are tolerated,</li><li>how fairly people are treated,</li><li>and how leadership responds under pressure.</li></ul><p>The strongest organizations understand that sustainable performance and healthy culture are not competing priorities.</p><p>The healthiest cultures are built around collectively finding what is right — even when it challenges hierarchy, ego, or existing assumptions.</p><p>Because in the long run, culture is what sustains performance.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9842f7e09b80" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Future of Software Engineering in the AI Era]]></title>
            <link>https://lahiru-himasha.medium.com/the-future-of-software-engineering-in-the-ai-era-a6737635d39f?source=rss-9d5e616fd3e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6737635d39f</guid>
            <dc:creator><![CDATA[Lahiru Cooray]]></dc:creator>
            <pubDate>Wed, 13 May 2026 04:04:35 GMT</pubDate>
            <atom:updated>2026-05-13T04:30:50.404Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*csleV9cF_78ngSl29-tbYQ.png" /></figure><blockquote>Some thoughts from an engineering leader trying to make sense of what comes next…</blockquote><h3>How engineering roles, competencies, and A-Players are evolving</h3><p>Over the last few months, I’ve spent a lot of time thinking about how AI will reshape software engineering teams, delivery models, career paths, and even the definition of what a “good engineer” looks like.</p><p>Honestly, I don’t think this is just another technology trend.</p><p>The software industry is entering one of the biggest transformations in its history.</p><p>For years, engineering organizations focused on scaling delivery through:</p><ul><li>larger teams</li><li>deeper specialization</li><li>offshore expansion</li><li>agile delivery optimization</li><li>cloud and DevOps adoption</li></ul><p>But AI, specially agentic AI systems — is fundamentally changing how software is built.</p><p>This shift is bigger than code generation.</p><p>It is changing:</p><ul><li>what makes a great engineer</li><li>how teams are structured</li><li>which technical skills matter most</li><li>how performance is assessed</li><li>what career paths look like</li><li>what engineering leadership must optimize for</li></ul><p>As engineering leaders, I believe we are no longer simply building software delivery organizations.</p><p>We are building AI-augmented engineering systems.</p><p>And that changes everything.</p><h3>The shift from “coding” to “orchestration”</h3><p>Historically, software engineering value was heavily tied to implementation capability.</p><p>The best engineers were often:</p><ul><li>the fastest coders</li><li>framework experts</li><li>technical specialists</li><li>problem solvers who could manually navigate complexity</li></ul><p>Engineering organizations rewarded:</p><ul><li>coding throughput</li><li>velocity</li><li>ticket delivery</li><li>implementation depth</li><li>specialization</li></ul><p>AI changes this equation.</p><p>Modern AI systems can already:</p><ul><li>scaffold applications</li><li>generate APIs</li><li>write tests</li><li>build infrastructure templates</li><li>create documentation</li><li>assist with debugging</li><li>generate CI/CD pipelines</li><li>analyze logs</li><li>refactor code</li><li>review pull requests</li></ul><p>And agentic systems are rapidly evolving beyond assistance.</p><p>The next generation of AI agents will increasingly:</p><ul><li>understand goals</li><li>decompose requirements</li><li>coordinate tasks</li><li>generate implementations</li><li>validate outputs</li><li>deploy changes</li><li>monitor environments</li><li>retry and self-correct</li></ul><p>In my opinion, this means the role of the engineer gradually shifts from:</p><blockquote><em>“manual implementation executor”</em></blockquote><p>toward:</p><blockquote><em>“systems thinker, orchestrator, validator, and business problem solver.”</em></blockquote><h3>Will software engineers disappear?</h3><p>No.</p><p>I personally don’t believe software engineers will disappear.</p><p>But I strongly believe software engineering roles will evolve significantly.</p><p>AI is unlikely to eliminate engineering.</p><p>However, it will absolutely redefine:</p><ul><li>what valuable engineering work looks like</li><li>which skills remain differentiators</li><li>how engineering organizations operate</li></ul><p>The future will likely reward engineers who:</p><ul><li>think clearly</li><li>understand systems deeply</li><li>adapt quickly</li><li>leverage AI effectively</li><li>understand business context</li><li>make sound engineering decisions</li></ul><p>rather than simply those who can produce code quickly.</p><h3>The rise of the AI-native engineer</h3><p>The future high-performing engineer will likely look very different from the traditional software developer.</p><p>When I think about the future “A-Players” in our industry, I don’t think they will necessarily be:</p><ul><li>the best syntax memorizer</li><li>the fastest typist</li><li>the narrow framework specialist</li></ul><p>Instead, I think they will be engineers who combine:</p><ul><li>systems thinking</li><li>business understanding</li><li>AI orchestration</li><li>architectural judgment</li><li>adaptability</li><li>common sense</li><li>communication and teamwork</li></ul><p>One thing that has become very clear to me is that AI amplifies thinking quality.</p><p>A mediocre engineer using AI may simply produce mediocre systems faster.</p><p>A strong engineer using AI can dramatically amplify impact.</p><p>This is why I believe the future engineering differentiator becomes:</p><ul><li>reasoning quality</li><li>problem framing</li><li>decision making</li><li>communication</li><li>collaboration</li><li>engineering judgment</li></ul><p>rather than implementation speed alone.</p><h3>What future engineering roles may look like</h3><p>One of the most interesting changes we are already starting to see is the blurring of traditional engineering boundaries.</p><p>Historically, engineering organizations evolved into highly specialized roles:</p><ul><li>frontend engineers</li><li>backend engineers</li><li>QA engineers</li><li>DevOps engineers</li><li>cloud engineers</li><li>platform engineers</li><li>support engineers</li></ul><p>This specialization emerged because systems became increasingly complex.</p><p>But AI significantly reduces the operational difficulty of many specialized implementation tasks.</p><p>A capable engineer can now use AI to:</p><ul><li>scaffold frontend applications</li><li>generate backend services</li><li>create infrastructure templates</li><li>automate deployments</li><li>generate tests</li><li>configure monitoring</li><li>troubleshoot environments</li></ul><p>without being a deep specialist in every area.</p><p>As a result, the industry may gradually move toward broader-spectrum engineering roles.</p><h3>Will fullstack, DevOps, and AI engineering become one role?</h3><p>I don’t think these roles will completely disappear.</p><p>But I absolutely think the boundaries between them will blur significantly.</p><p>The future likely belongs to engineers who can operate across the full software lifecycle with AI assistance.</p><p>The traditional “fullstack engineer” may evolve into something closer to:</p><blockquote><em>AI-Augmented Solution Engineer</em></blockquote><p>An engineer who can:</p><ul><li>understand product requirements</li><li>design systems</li><li>build frontend experiences</li><li>develop backend services</li><li>manage infrastructure</li><li>automate deployments</li><li>use AI agents effectively</li><li>monitor production systems</li><li>optimize operational workflows</li></ul><p>This does not mean deep specialization disappears.</p><p>Highly complex domains will still require experts in:</p><ul><li>distributed systems</li><li>cybersecurity</li><li>AI infrastructure</li><li>data engineering</li><li>platform reliability</li><li>performance engineering</li><li>compliance and governance</li></ul><p>However, many organizations may evolve toward:</p><ul><li>fewer narrow specialists</li><li>smaller expert platform teams</li><li>broader AI-enabled engineers</li><li>leaner delivery squads</li></ul><p>The future organization may consist of:</p><ul><li>versatile AI-native engineers<br>PLUS</li><li>smaller groups of deep technical specialists</li></ul><p>rather than large execution-heavy teams.</p><h3>The evolution of technical skillsets</h3><p>Technical skills are definitely evolving.</p><p>Historically, engineering growth often focused heavily on:</p><ul><li>framework expertise</li><li>language specialization</li><li>implementation depth</li></ul><p>But in the AI era, I think foundational engineering capability becomes more important than narrow tooling expertise.</p><p>Future high-value technical capabilities may include:</p><ul><li>systems thinking</li><li>architecture and scalability</li><li>AI collaboration</li><li>cloud and automation understanding</li><li>security awareness</li><li>product and business understanding</li></ul><p>At the same time, I believe soft skills become even more important.</p><p>As AI automates more implementation work, the engineers who stand out will often be the people who can:</p><ul><li>communicate clearly</li><li>work effectively with teams</li><li>simplify complexity</li><li>make practical decisions</li><li>align stakeholders</li><li>show leadership under uncertainty</li></ul><p>Common sense may actually become one of the most underrated engineering skills in the AI era.</p><p>AI can generate code.</p><p>But it still cannot reliably replace:</p><ul><li>human judgment</li><li>context awareness</li><li>relationship building</li><li>leadership</li><li>trust</li><li>teamwork.</li></ul><h3>What happens to junior engineers?</h3><p>One area that genuinely concerns me as an engineering leader is how we develop junior talent in the AI era.</p><p>Historically, junior engineers learned through:</p><ul><li>repetitive implementation work</li><li>debugging</li><li>small feature delivery</li><li>manual problem solving</li><li>exposure to operational issues</li></ul><p>AI is increasingly automating many of these entry-level tasks.</p><p>This creates a risk.</p><p>Organizations may unintentionally create engineers who are good at prompting AI but weak in engineering fundamentals.</p><p>Future engineering organizations may need far more intentional growth models:</p><ul><li>architecture shadowing</li><li>production exposure</li><li>guided debugging exercises</li><li>AI-assisted pair engineering</li><li>systems thinking training</li><li>deeper mentorship programs</li></ul><p>I think the goal will no longer simply be teaching engineers how to code.</p><p>It will be teaching them how to think.</p><h3>What future A-Players will look like</h3><p>Future A-Players will likely be engineers who combine technical depth with adaptability and strong people skills.</p><p>They will likely demonstrate:</p><h3>High learning velocity</h3><p>The industry is evolving rapidly.</p><p>The best engineers will be the people who:</p><ul><li>learn quickly</li><li>adapt rapidly</li><li>stay curious</li><li>continuously improve</li></ul><h3>Strong systems thinking</h3><p>Future A-Players will:</p><ul><li>understand architecture</li><li>simplify complexity</li><li>think holistically</li><li>make sound engineering decisions</li></ul><h3>AI leverage capability</h3><p>Future high performers will know:</p><ul><li>when to trust AI</li><li>when not to</li><li>how to validate outputs</li><li>how to combine human and AI strengths effectively</li></ul><h3>Communication and teamwork</h3><p>I genuinely think soft skills become even more valuable in the AI era.</p><p>As technical execution becomes easier, organizations will increasingly value people who can:</p><ul><li>communicate effectively</li><li>collaborate well</li><li>mentor others</li><li>align teams</li><li>handle ambiguity</li><li>create clarity</li><li>influence outcomes positively</li></ul><p>The future engineer increasingly becomes:</p><ul><li>a business technologist</li><li>a systems thinker</li><li>a collaborative problem solver</li></ul><p>rather than simply a coder.</p><ul><li>strategic thinking</li></ul><h3>How performance assessments may change</h3><p>I also think we need to rethink how we assess engineering performance.</p><p>Traditional metrics such as:</p><ul><li>lines of code</li><li>pull request counts</li><li>story points</li><li>commit frequency</li></ul><p>become far less meaningful when AI can generate large amounts of code rapidly.</p><p>Future engineering performance models may focus more on:</p><ul><li>business outcomes</li><li>engineering judgment</li><li>problem-solving capability</li><li>collaboration</li><li>leadership</li><li>communication</li><li>mentoring</li><li>AI leverage effectiveness</li></ul><p>I believe the industry will gradually shift from measuring activity toward measuring impact.</p><h3>The future competency matrix</h3><p>Many traditional competency frameworks focus heavily on:</p><ul><li>years of experience</li><li>framework knowledge</li><li>implementation capability</li></ul><p>I think future competency models will evolve significantly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dTOk3Ie3PUqNkfrI9npEYw.png" /></figure><p>This does not mean coding becomes irrelevant.</p><p>But I strongly believe coding alone will no longer be enough to differentiate top talent.</p><h3>What engineering leaders should focus on now</h3><p>For Heads of Engineering and technology leaders, I believe the challenge is not simply adopting AI tools.</p><p>The challenge is redesigning the engineering operating model.</p><p>Organizations should start thinking about:</p><h3>Building AI-native engineering cultures</h3><p>Normalize responsible AI usage rather than resisting it.</p><h3>Redesigning competency frameworks</h3><p>Reward:</p><ul><li>systems thinking</li><li>adaptability</li><li>AI fluency</li><li>engineering judgment</li><li>business understanding</li></ul><h3>Investing in architecture capability</h3><p>System design and architectural thinking become increasingly valuable.</p><h3>Developing broad-spectrum engineers</h3><p>Train engineers across:</p><ul><li>cloud</li><li>frontend</li><li>backend</li><li>infrastructure</li><li>observability</li><li>AI tooling</li></ul><p>while still preserving opportunities for deep specialization.</p><h3>Preserving engineering fundamentals</h3><p>AI should amplify engineering capability — not replace foundational understanding.</p><p>Organizations that lose core engineering rigor may accumulate technical debt faster than ever before.</p><h3>Final thoughts</h3><p>I don’t claim to have all the answers.</p><p>Like many engineering leaders, I’m still learning, experimenting, and trying to understand what the next 5–10 years will look like for our industry.</p><p>But one thing feels very clear to me.</p><p>The future of software engineering is unlikely to be about humans versus AI.</p><p>It will be about how effectively humans and AI work together.</p><p>The future engineer may look less like:</p><blockquote><em>“a person who writes code all day”</em></blockquote><p>and more like:</p><blockquote><em>“a systems-oriented problem solver who orchestrates technology, AI, business context, and engineering judgment to deliver outcomes.”</em></blockquote><p>The future engineering organization may become:</p><ul><li>smaller</li><li>leaner</li><li>more strategic</li><li>more AI-augmented</li><li>more outcome-driven</li></ul><p>And the future A-Players will likely not be the people who simply execute tasks faster.</p><p>They will be the people who:</p><ul><li>think clearly</li><li>adapt quickly</li><li>understand systems deeply</li><li>leverage AI responsibly</li><li>connect business and technology effectively</li><li>elevate the performance of the entire organizationli</li></ul><p>That is likely where the future of software engineering is heading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6737635d39f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Rise of “Vibe Coding”: Why AI-Generated Software Excites Businesses and Worries Engineering…]]></title>
            <link>https://lahiru-himasha.medium.com/the-rise-of-vibe-coding-why-ai-generated-software-excites-businesses-and-worries-engineering-cc897e3de930?source=rss-9d5e616fd3e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc897e3de930</guid>
            <dc:creator><![CDATA[Lahiru Cooray]]></dc:creator>
            <pubDate>Sun, 08 Mar 2026 03:01:47 GMT</pubDate>
            <atom:updated>2026-03-08T03:01:47.287Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Rise of “Vibe Coding”: Why AI-Generated Software Excites Businesses and Worries Engineering Leaders</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_50R-EJzpXtqIg5PEG289g.png" /></figure><p>A new development trend is quietly gaining momentum across startups, consulting firms, and product teams. Some people call it <strong>“vibe coding.”</strong></p><p>The idea is simple. Instead of going through traditional development cycles, someone describes what they want in natural language and AI-powered tools generate working software almost instantly.</p><p>What once required weeks of engineering effort can now appear in minutes.</p><p>For businesses, this feels revolutionary. For engineering leaders, it raises an important question.</p><p><strong>If AI can build your app in minutes, who will maintain it?</strong></p><h3>Why Businesses Are Excited</h3><p>AI-assisted development tools are dramatically reducing the time it takes to turn an idea into a working product.</p><p>A product manager could type something like:</p><blockquote><em>“Build a simple customer feedback dashboard with login and charts.”</em></blockquote><p>Within minutes, the platform might generate:</p><ul><li>a frontend interface</li><li>backend services</li><li>database connections</li><li>authentication logic</li></ul><p>For startups and innovation teams, this ability to rapidly validate ideas is extremely valuable. Teams can test concepts quickly, demonstrate working prototypes to stakeholders, and move from idea to execution much faster than before.</p><p>Another reason for the excitement is that many of these tools are designed for <strong>non-technical users</strong>. Product managers, founders, and business analysts can experiment with building applications without writing large amounts of code.</p><p>The barrier to building software has never been lower.</p><h3>The Hidden Challenges</h3><p>Despite the excitement, engineering leaders are approaching this trend cautiously.</p><p>The problem is not that AI can generate code. In fact, it does that remarkably well.</p><p>The real challenge begins after the prototype works.</p><p>Enterprise software requires careful thinking about:</p><ul><li>architecture and scalability</li><li>security and compliance</li><li>maintainability</li><li>long term system evolution</li></ul><p>AI-generated applications often prioritize speed over structure. They may work well for demonstrations but struggle when exposed to real-world complexity.</p><p>What begins as a quick prototype can quickly turn into <strong>technical debt</strong> if it becomes a production system.</p><h3>The Rise of Shadow AI</h3><p>Another concern emerging inside organizations is <strong>Shadow AI</strong>.</p><p>Shadow AI happens when employees start using AI tools outside official governance. Code may be generated outside approved repositories, internal data might be shared with external platforms, and development practices can bypass normal engineering reviews.</p><p>For companies operating in regulated environments or handling sensitive data, this creates real risks related to security, compliance, and intellectual property.</p><p>Because of this, many organizations are now focusing on introducing <strong>clear guardrails and standards for AI usage</strong> instead of banning these tools completely.</p><h3>Is AI Replacing Developers</h3><p>One of the most controversial questions surrounding AI-assisted development is whether developers are becoming obsolete.</p><p>At first glance, it might appear that way. If applications can be generated in minutes, it may seem like the role of developers is shrinking.</p><p>However, writing code has never been the hardest part of building software.</p><p>The real challenge lies in designing systems that can survive real-world complexity. Someone still needs to think about system architecture, scalability, security, and how the software will evolve over time.</p><p>In many ways, AI may actually increase the importance of experienced engineers. As software becomes easier to generate, the need for people who can design, govern, and maintain complex systems becomes even more critical.</p><h3>Finding the Balance</h3><p>AI-assisted development is clearly reshaping how software is created. Ideas can move from concept to working prototype faster than ever before.</p><p>But speed alone does not guarantee sustainable software.</p><p>The real challenge for organizations today is not whether they should use AI-powered development tools. The challenge is <strong>how to integrate them responsibly into their engineering ecosystems</strong>.</p><p>Because while AI can build your app in minutes, <strong>someone still has to maintain it.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc897e3de930" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rome wasn’t built in a day…]]></title>
            <link>https://lahiru-himasha.medium.com/rome-wasnt-built-in-a-day-da6b6e29d151?source=rss-9d5e616fd3e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/da6b6e29d151</guid>
            <dc:creator><![CDATA[Lahiru Cooray]]></dc:creator>
            <pubDate>Fri, 01 Sep 2023 04:43:59 GMT</pubDate>
            <atom:updated>2023-10-03T01:03:08.413Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8CSCidn17CwJlP3u.jpg" /></figure><blockquote>Establishing a high-performing, long-term oriented, and efficient Engineering team.</blockquote><p>I consider myself fortunate to have held the role of founding member within an offshore engineering center established by an international technology firm. Over the course of the last half-decade, I have fulfilled the role of Head of Engineering within the company. The purpose of this article is to discuss the strategies I have employed to establish a profoundly productive software engineering team characterized by a strong organizational culture and a steadfast long-term vision.</p><p><strong>The initial hiring decisions are of paramount importance.</strong></p><p>When initiating a team from the ground up, the most critical step is to make a select few strategic hires. It’s imperative to assemble a team characterized by trustworthiness and dependability. This entails choosing individuals who possess intelligence, as they can be molded to perform optimally, and whose best efforts can be harnessed. Furthermore, I prioritize attributes such as willingness and attitude over prior experience.</p><p>I concur with <a href="https://simonsinek.com/">Simon Sinek’</a>s viewpoint, which emphasizes the significance of a medium-performing member with high levels of trust, over a high-performing yet toxic individual, within a startup team.</p><p><strong>Establishing a solid foundation of trust within your team is essential.</strong></p><p>It holds immense significance that your team members place their trust in you, and it’s crucial to remember that trust operates as a two-way dynamic. Trust is something that must be earned through actions, not merely through words.</p><p><strong>It is essential to possess a firm grasp of technical skills and domain knowledge while consistently staying updated to ensure effectiveness and success.</strong></p><p>To effectively lead an engineering team, a profound understanding of both technology and business is imperative. Non-technical leaders often face skepticism from technical team members; thus, your explanations and ideas must be easily graspable. Collaborate with experts when necessary. Moreover, remaining up-to-date with rapidly evolving technology is vital to steer clear of obsolescence.</p><p><strong>Develop a comprehensive plan for each phase in advance and establish short-term goals to guide your progress effectively</strong></p><p>Possessing a long-term vision for your team is of paramount importance. Right from the outset, I held distinct plans, and I’m willing to offer a few illustrative examples.</p><p>During our early stages as a startup, our principal aim was to expedite the deployment of artifacts to Production Environments while minimizing the presence of bugs. This strategy was driven by the goal of securing long-term service maintenance agreements, which in turn provided the necessary resources for future expansion endeavors.</p><p>Subsequently, in the second stage, our focus shifted towards addressing quality concerns. This led to the implementation of certain action items, including the augmentation of Quality Assurance capabilities and the introduction of refined Engineering Processes.</p><p>Following that, we embarked on the process of formalizing standards and procedures across the entire Software Development Life Cycle (SDLC). Our endeavor encompassed the adoption of world-class engineering practices, with the assignment of responsible roles dedicated to upholding these standards.</p><p>Finally, our attention turned towards the realms of Productization, Automation, and Reusability, where we concentrated on the effective implementation of these initiatives.</p><p><strong>Cultivate an organizational culture that engenders such loyalty and satisfaction among your staff that they have no desire to depart.</strong></p><p>Continuously contemplate what the optimal company culture would be from the perspective of a junior employee. What factors contribute to their contentment? Conversely, also reflect on what aspects tend to cause employee dissatisfaction.</p><p>Establishing and upholding a genuinely flat hierarchical environment is vital to facilitate the seamless flow of ideas from top to bottom. The inclusion of the term ‘genuine’ is pivotal, as many companies claim to adopt such an approach, but often fall short in its practical implementation.</p><p>Culture serves as the lifeblood of an organization, binding all units cohesively. It represents the optimal and sole method for retaining top talent once the mandate requirements have been met.</p><p><strong>Familiarize your team not solely with technical expertise, but also with the commercial facets of the business.</strong></p><p>While any engineer can produce code, providing them with education about business operations and clients’ expectations, along with encouraging them to adopt a business-oriented mindset, fosters innovation. This approach enables the formulation of optimal solutions to address business challenges effectively.</p><p>In addition to focusing solely on technological aspects, engage in discussions with your team about solutions. Aid them in comprehending high-level issues by adopting a bird’s-eye view perspective.</p><p>Cultivate an environment that encourages individuals to challenge the status quo and propose alternatives without the fear of rejection. This approach aids them in embracing changes with a fearless outlook.</p><p><strong>Expose your team to challenges and consistently provide opportunities for continuous learning.</strong></p><p>Exposing the team to challenges serves as a means to cultivate critical thinking skills. Given the rapid pace of technological evolution, maintaining a continuous learning process and staying updated with external developments is of paramount importance.</p><p><strong>In the grand scheme, the significance lies in prevailing in the war, even if a battle or two may be lost along the way.</strong></p><p>In the event of minor failures, it’s essential to support the team and not let them down. These instances should serve as lessons for learning, prompting the implementation of action items to prevent future occurrences.</p><p>Prioritize process improvement over merely addressing isolated issues, as this approach contributes to sustained progress.</p><p><strong>Face the pressure emanating from both upper leadership and your subordinates with resilience and strength akin to that of carbon fiber.</strong></p><p>At times, assuming the role of a mediator and absorbing pressure from both top management and your immediate team can be incredibly challenging. Leadership, much like riding a bicycle, demands maintaining the right balance while continually propelling forward.</p><p><strong>Adapt the hiring strategy according to your expansion trajectory and financial capacity.</strong></p><p>In the initial stages, startups often lack the luxury of recruiting top-tier industry professionals. However, as growth and financial capacity expand, it becomes imperative to modify hiring strategies and recalibrate the target employee market.</p><p><strong>Facilitate internal growth opportunities for your staff within the organization.</strong></p><p>Strive to create a well-defined career progression trajectory that aligns with the region of operation, and establish transparent Key Performance Indicators (KPIs) for promotions and salary increments. In conjunction with the company’s expansion, prioritizing the advancement of employees’ careers and personal lives holds substantial significance from my standpoint.</p><p><strong>Exhibit strong resistance to detrimental behaviors and actions within the team.</strong></p><p>React promptly and publicly make decisions when identifying a negative influence that could detrimentally affect the company culture. This approach ensures that the entire team becomes aware of the unacceptable behavior and sees that it is being addressed.</p><p><strong>Your most accomplished employee can also pose the greatest risk.</strong></p><p>Your most dependable employee, upon whom you heavily rely, also represents your most significant risk. Consider the scenario where this individual does not show up tomorrow. Establishing succession plans within an established team is therefore of utmost importance.</p><p>In my perspective, creating a succession plan should involve open discussions with the individuals concerned, ensuring their input and support in the process.</p><p><strong>Think globally, act locally.</strong></p><p>In managing a global team, it’s imperative to recognize the richness and diversity of cultures that make up the workforce. Embracing and respecting these cultural differences is not just a matter of sensitivity, but a strategic imperative for success. Each culture brings with it a unique set of values, work styles, and communication norms. To truly harness the collective strength of a global team, we must treat each culture individually, understanding and valuing their distinct contributions. It’s a recognition that ‘umbrella solutions’ rarely fit the bill in such a dynamic and diverse environment. This is where ‘The rubber hits the ground’ — by customizing our approaches to align with the specific needs and values of each culture, we can unlock the full potential of our team, fostering an inclusive and collaborative atmosphere that leads to the best outcomes.</p><p><strong>Finally, Rome wasn’t built in a day!</strong></p><p>Constructing an exceptionally positive culture and building a team that is both dedicated and skilled, fostering high performance and low employee turnover, requires a significant investment of time and effort.</p><p>Nevertheless, it is crucial to recognize that only a handful of poor decisions can swiftly dismantle this foundation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da6b6e29d151" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Essence of Leadership: Inspiring as Electryone, Not Overpowering like Hercules]]></title>
            <link>https://lahiru-himasha.medium.com/the-essence-of-leadership-inspiring-as-electryone-not-overpowering-like-hercules-8f9d520c8fd2?source=rss-9d5e616fd3e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f9d520c8fd2</guid>
            <dc:creator><![CDATA[Lahiru Cooray]]></dc:creator>
            <pubDate>Sun, 13 Aug 2023 03:21:30 GMT</pubDate>
            <atom:updated>2023-08-13T03:46:13.283Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*l73dYr0EpaPu8LTC.jpg" /></figure><p>Over the course of my 15-year career, I have undertaken numerous leadership roles. During my 5-year tenure as an Engineering head, I had the privilege of nurturing several emerging leaders. This article aims to impart some of my insights and strategies based on these experiences.</p><p>Leadership fundamentally revolves around empowering emerging leaders rather than exerting dominance. Hence, in this article, my focus will be on discussing the methods to cultivate new leaders, rather than delving into the pursuit of achieving personal stardom.</p><p><strong>Recognize individual differences; comprehend character traits before offering assistance.</strong></p><p>In distinguishing humans from machines, it’s essential to initially comprehend their character and background before attempting any form of transformation.</p><p><strong>While natural leadership is a gift, the art of leadership can be cultivated.</strong></p><p>While having a born leader within your team is indeed a luxury, individuals possessing the right attitude and a genuine drive to create a significant impact can readily undergo a transformation into becoming exceptional leaders.</p><p><strong>Effective communication is crucial.</strong></p><p>Proficiency in language is only part of the equation; what truly counts is effective communication. Creating an environment that treasures open communication and transparency is pivotal. This environment not only encourages the flow of ideas and information but also nurtures a culture where team members feel empowered to express their thoughts, contributing to the overall growth and cohesion of the team.</p><p><strong>Integrate them seamlessly into the fabric of the company culture.</strong></p><p>In the process of nurturing a leader, one of the primary considerations is their ability to adapt to the prevailing organizational culture. It becomes crucial to provide support and guidance to ensure their seamless integration into the cultural fabric of the company. By doing so, we enable them to not only understand but also embody the values, norms, and practices that define the organization’s identity, ultimately enhancing their effectiveness as a leader within the context of the company’s ethos.</p><p><strong>Demonstrate a commitment to openness and transparency.</strong></p><p>Openness, commitment, and transparency are attributes we hold in high regard for a company’s leadership. Primarily, we should set the precedent by embodying these qualities ourselves.</p><p><strong>Incorporate your team consistently into the decision-making process.</strong></p><p>In my perspective, leaders ought not to unquestioningly execute tasks as directed by their superiors. Rather, they should engage actively in the decision-making process and assume responsibility for outcomes that have been collectively agreed upon.</p><p><strong>Impart all of your knowledge to your team members.</strong></p><p>When addressing technical competencies, endeavor to provide them with a comprehensive understanding of your knowledge. Additionally, create opportunities for them to undergo training and upskilling, fostering their growth.</p><p><strong>Embrace the risk of reliance, supporting through failures, and celebrating successes.</strong></p><p>Emerging leaders often grapple with the fear of failure. It is imperative to offer unwavering support during their challenging moments, providing a steadfast presence when they encounter setbacks. Especially during the initial stages of their leadership journey, standing by them consistently despite repeated failures is vital. Equally important is the practice of celebrating their successes, reinforcing their confidence and fostering a resilient spirit in the face of both triumphs and trials.</p><p><strong>Aim to develop a group of leaders you can rely on, even when your presence is not there.</strong></p><p>Micro-management consumes valuable time. Cultivating a team of responsible leaders, accountable for their work, is both a luxury and an essential aspect to foster as a fundamental part of our organizational culture.</p><p><strong>Strive to make your role replaceable by developing systems and empowering individuals to seamlessly take over your responsibilities.</strong></p><p>Cultivating and grooming a team member with the potential to step into your role down the line serves as a proactive strategy for ascending the professional ladder. This approach not only secures a seamless transition but also demonstrates your leadership and mentorship skills, enhancing your profile and opportunities for growth within the organization.</p><p>The points highlighted in this article represent proven strategies that have personally enabled me to cultivate accomplished leaders in the industry. As the adage goes, “With great power comes great responsibility”. True leadership entails not merely issuing commands, but empowering others. Embrace this privilege as an opportunity to positively influence and enrich the lives of those around you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f9d520c8fd2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leadership lessons]]></title>
            <link>https://lahiru-himasha.medium.com/leadership-lessons-6698a341b728?source=rss-9d5e616fd3e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/6698a341b728</guid>
            <dc:creator><![CDATA[Lahiru Cooray]]></dc:creator>
            <pubDate>Tue, 15 Sep 2020 16:06:47 GMT</pubDate>
            <atom:updated>2023-01-27T05:10:18.521Z</atom:updated>
            <content:encoded><![CDATA[<h3>Leadership lessons I’ve learned from past experience</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2lJuZkFdkrnNm0f_ABIXAQ.jpeg" /></figure><h4>Listen to your team</h4><p>When it comes to communication with your team, fluency in the language they are communicating is not what you should concentrate on, but rather the core idea.</p><p>Good leaders listen to their teammates and try to understand the core of the idea that they are trying to express. This encourages teammates to raise their suggestions which could ultimately improve your business</p><p>Weak leaders focus on the communication style instead of understanding the core. They do not listen to the team and think they are always correct. Ultimately ended up building a team of people who do not raise their suggestions and follow what their leader says (even if it is correct or wrong)</p><p>Listening is a good quality of a leader. Even when someone raises a really stupid suggestion first listen, then try to provide feedback in a constructive manner.</p><p>Neither of us is perfect or always correct. There’s room for improvement for anyone. Encourage everyone in your team to speak. Don’t let them think it’s like playing the violin to a deaf elephant. Value their ideas and action them. That’s the only way you could keep those coming.</p><h4>Promote ‘What is right’ instead of ‘Who is right’</h4><p>Usually, arguments are made to find out who is right and the best debater always wins. Instead, promote a culture where team members do not feel ashamed to withdraw their opinion when they hear a better suggestion. Ultimately best idea should win rather best debater.</p><h4>Loyalty isn’t Stupidity</h4><p>There’s a saying <em>‘Never push a loyal person to the point where they no longer care’ </em>which is undoubtedly true. Loyal employees are very rare and a great asset for any team. You can buy talent but you cannot ever buy loyalty.</p><p>Usually, when an employee works hard and loyally without trying to highlight the workload they are carrying out, companies tempt to expect the same output over and over again from him/her but fail to understand what company could appreciate his/her effort. When loyal employees realize that they were being used they leave companies.</p><h4>Be Creditable</h4><p>As a leader, you should be creditable. You should keep your word and earn the trust and respect of the team. Take responsibility when the team fails and pass the credit to the team when there’s a win. Do not share whatever comes into your mind, think about the validity of the content before you share.</p><h4>Be Transparent</h4><p>Employees do not trust leaders who are not transparent. A closed person who doesn’t express their true feelings to others can never be a good leader. Be open with your team as much as possible. Tell them when they are going under the bar and appreciate them when they are performing well.</p><h4>Adjusting to different cultures is critical</h4><p>When working with a globally distributed team most important fact is adjusting to different work cultures and this should be two-way. The needs of the employees can hugely differ from country to country. As leaders of the company, it is highly important to understand cultural diversities and adjust — you cannot change the cultures all you could do is adjust.</p><h4>Use the Magic Hat</h4><p>You do not need to be the most knowledgeable or experienced person on the team to lead a team. It’s all about how you identify the talents of each member and use the talent cleverly in the game.</p><p>I’m a great fan of Cricket. In 1996 Srilanka won the cricket world cup coming from nowhere. Arjuna was the captain and he was the fattest and oldest member of the team. He had great cricketing knowledge and an in-depth understanding of all the players. Sometimes when things were not going well he used to roll his hat analyze/think for a while and pass the ball to a new bowler. A 7/10 new bowler took a wicket.</p><p>It’s all about playing your cards smartly. You don’t need four triumphs to win a game. Well if you do, it&#39;s a luxury.</p><h4>Remember your roots</h4><p>No matter how big you grow remember the roots. Even a big tree could die when the roots are removed.</p><h4>Know where you are heading and set your milestones</h4><p>As a leader, it’s highly critical to know the company’s vision and mission. Without knowing the long-term vision you cannot build a sustainable team. Routine work is important but planning long-term is a key dimension of a strategic leader. Winning battles is easy but what matters is winning the war!</p><h4>Risk Management</h4><p>When it comes to managing a team your highest performing/dependent team member is always your highest risk. What if she/he doesn’t appear tomorrow? Are you sure that there’s a backup plan to conduct the work with minimum interruption? It’s always important to identify the key dependencies and proactively set backup plans.</p><p><em>“Train people well enough so they can leave, treat them well enough, so they don’t want to”</em></p><h4>Show resistance to ‘Jerks’, on the spot</h4><p>In one of my earlier jobs, the Sales guys were asked to fill out some surveys about the accounts owned by them. There was a question asking the reason why clients like that our company. One of the sales guys answered saying that’s because of account manager (himself) is great.</p><p>Our CEO replied via an email copying the entire company requesting him to answer the question correctly without being a jerk, which I think is great.</p><p>Talking about something is easy but making it happen is hard. Identify your silent warriors and treat them well</p><h4>Working culture matters</h4><p>Managers cannot build team trust — trust among each other, but they can support it. Trust has to be built within the team itself. Let me share a short story. I worked for a small startup company and we used to play one-bump cricket inside the office often. My managers didn’t see it as a waste of time or an overhead (unless when we broke a glass or two). Within a few weeks time individuals started to work as a single team, and the office became a happy place to be. productivity went high during working hours</p><p>That’s probably the best period of my entire career. It’s not just that we had freedom but we had an awesome team who worked for a common goal and the office was just another home for us. During that period we even didn’t have budgets for any outbound team-building activities but still we managed to build a great team.</p><p>Within the game, there were no hierarchies. Individuals in different functional teams got a chance to work together for a common goal. We could easily identify the characters of individuals.</p><h4>With great power comes great responsibility</h4><p>When you climb up the organization hierarchy you get more authority and power. Always try to use them for the benefit of your company not your own. True characters are explored when they are given the authority.</p><h4>Career != Job</h4><p>Your current job role in the company does not define your career. Always learn new things, be up-to-date and move with the trends. As Steve Jobs said ‘be hungry be foolish’</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6698a341b728" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>