Cegeka’s Post

Scaling low-code without governance leads to chaos. OutSystems gives you the tools... Your team just needs the structure. Here’s how to bring control back into your low-code journey. #MigrationToODC #Governance #SoftwareArchitecture #AIDevelopment

Last week, in the CHAOSS DEI Working Group, we launched something I am glad to have helped bring to life, through code and automation. We introduced the Reviewer Spotlight for the Event DEI Badging Program — a simple but meaningful way to recognize the incredible contributors who review event DEI applications. Reviewer Spotlight automatically highlights all reviewers, showcases how many applications they have reviewed, and celebrates them with a badge. This visibility layer does more than display data, it: • Validates efforts that might otherwise go unnoticed. • Encourages consistency and pride in contribution. • Builds professional credibility reviewers can showcase. It’s a small act of recognition but one with a big impact. As a project steward and maintainer, I often think about project health — and not just in terms of the health of the codebase or repository. True health lies in the people behind the project. Every successful open source project runs on one quiet engine: contributor retention. It’s easy to measure commits, pull requests, or coverage, but those are outcomes. What truly sustains open source are the people who keep showing up. However, retention isn’t accidental; it’s nurtured. And one of the most effective ways to nurture it is recognition—the act and art of showing contributors that their time, energy, and expertise are seen and valued. Recognition isn’t vanity. In open source, it’s sustainability. When contributors see their roles or contributions acknowledged, it sends a simple but powerful message: “You belong here. What you do matters.” Small gestures like the Reviewer Spotlight help strengthen the health of open-source communities. They remind us that behind every metric, every line of code, and every badge stands a person giving their time, care, and skill to make something better for everyone. And when we remember to celebrate those people, that’s when open source truly thrives. #opensource #contributor #recognition #maintenance

Want to know what's new on the Platmosphere Content Hub? 🔥 💡Sarah Hsu (Co-Author of "Building Green Software", Green Software Principles Project Lead at Green Software Foundation, UK TechWomen100 Winner LinkedIn) talked about her journey in “Green Software: From Tree Hugger to Tech Trendsetter“🚀 🌱In this talk, she explored the rapid rise of #Sustainability in #Tech, uncovering the essential elements that make #Software truly #Green. ☀️Dive into the basics of #GreenSoftware, practical steps you can take, and a #Roadmap to turn your software projects into sustainability champions. 🍿Watch the video to find out more! ➡️https://lnkd.in/dRiSps8J #MiaPlatform #GreenSoftware #Platmosphere2025 #Speech #PlatformEngineering #Speaker

Sustainability in Software Development is more than just point and click and some features in here and there. It's about mindset, culture and awareness. https://lnkd.in/enpfdz-R

At Making Software Greener (MSG), our mission is to reduce the environmental impact of IT systems. But sustainability doesn’t happen in isolation. Our work connects directly to the United Nations Sustainable Development Goals (SDGs) — a global framework for building a sustainable future. From lowering energy use (SDG 7), to strengthening digital infrastructure (SDG 9), to tackling IT’s carbon footprint (SDG 13), greener software makes a measurable difference. Along the way, we’re also supporting education, economic growth, and global partnerships. Technology has the power to either promote or hinder sustainability. With the right practices, IT becomes part of the solution. Read more about how MSG aligns with the SDGs in our latest blog post: https://lnkd.in/geBDGzEY #SustainableIT #SDG #Sustainability #GreenSoftware

I’ve been thinking a lot about how IT connects to the bigger picture. At Making Software Greener, Ltd., we’re not just optimizing systems to save energy and money—we’re aligning with the UN Sustainable Development Goals. Greener software touches everything: clean energy, resilient infrastructure, responsible consumption, and climate action. It also means new skills, new jobs, and stronger partnerships. The message is simple: technology can accelerate sustainability if we choose to build it that way. Here’s how we’re making the connection: https://lnkd.in/gqBm6Mym #SustainableIT #UN #SDG #Sustainability #GreenSoftware

There are currently 150 to 300 funded seed-stage software companies in Australia and New Zealand that need an exit. Over the next 5 years that number will grow to somewhere between 230 and 900.

🛠️ Built with funders Some of our best platform features start with funders telling us what’s holding them back. Here's a powerful example. For Primera, the challenge was clear: Their consortium of Business Improvement Districts (BIDs) were funding incredible projects through ActionFunder — but Primera couldn’t see the collective impact across their network. Impact data and stories were siloed.  To get the full picture, they’d need to combine 10 reports manually.  Complex. Time-consuming. And a missed opportunity. 💡 So, together, we built the Network-Level Reporting Tool (or what our team like to call the ‘Grandparenting Tool’). Now, Primera can: 📊 see the cumulative impact across their entire network - instantly! 🔎 Filter data by region, timeframe, member organisation, or individual fund 📂 Export portfolio-wide reports in a click - saving hours. 💪 Use these insights to strengthen bids, engage stakeholders, and maximise their community investment ROI. And the tool isn’t just for consortiums. It also unlocks value for organisations  - with departments managing separate community investment   - who want to prove social value delivered across supply chains 👉 From big-picture insights to project-level detail, get visibility across your whole network. Here's a sneak peek!

A Theory of Change should never exclude the people it’s meant to serve. Too often, though, it does. Hidden behind dense arrows, abstract outcomes, and phrases like “strengthened enabling environments.” This guide unpacks how to make ToCs accessible and usable, not just technically correct. It shows why: → A Theory of Change is not just a diagram. It’s also a shared conversation about how change happens. → Visual simplicity matters more than perfect shapes; If people can’t see themselves in the logic, they won’t own it. → The words you choose (“empower,” “support,” “build capacity”) should be tested with those who live the reality, not just those who write the reports. → Every ToC should tell a story that community members, implementers, and donors can all read and recognise as true. Because accessible design isn’t just good practice, it’s good ethics. When people understand the pathway to change, they can question it, improve it, and believe in it. That’s the kind of clarity we build inside the Clarity-to-Impact™ Programme, where teams learn to co-create Theories of Change that are strategic, inclusive, and alive. The programme was closed, but due to demand, I’ve reopened five spots for this cohort. Once these are gone, that's it! Next intake in 2026. 🔥 Grab one of the last spots now and be part of next week's cohort: https://lnkd.in/e7gh5fan #ClarityToImpact

Often the barriers are hidden behind the bias that defines how to change. The Canada Human Rights Commission states that people with disabilities must disclose their functional limitations for accommodations. Yet accommodations are to address discrimination - thoughts and actions outside the individual. The revised definition of disability by CHRC states that a disability occurs in interaction with an environment that excludes. Canada Human Rights Act does not include the term functional limitations. The employment equity and accessible Canada Acts define functional limitations with an 'or' or 'and includes' statement meaning you can have a disability and a barrier - yet no limitations. The introduction of the term in the guidance is due to bias in the writing to create a requirement for all cases that in the Acts it supports is actually an exception