Cognixia Podcast Cognixia

Hello everyone and welcome back to the Cognixia podcast. In September 1983, Richard Stallman launched a project that would fundamentally alter the software landscape: GNU. This operating system emerged as a free alternative to the dominant Unix systems of the era. Stallman's vision was driven by a core belief: software should be open and accessible to all. He saw a growing trend towards proprietary software and copyright restrictions, and GNU was his response. This philosophy – that unrestricted access to code, free from commercial limitations, would benefit the world – became the foundation of the free software movement.



Fast forward four decades. Today's tech landscape is dominated by proprietary software, generating billions for tech corporations. Many everyday technologies, from complex language models like ChatGPT to seemingly simple smart thermostats, function as black boxes for consumers. Against this backdrop, Richard Stallman's vision of a free software movement might appear like a utopian ideal, overpowered by commercial forces.



However, the story doesn't end there. In 2024, the free and open-source software (FOSS) movement is not only enduring but thriving. FOSS has become a cornerstone of the tech industry, playing a crucial role in innovation and development.



Open-source software (OSS) has become a ubiquitous element in modern technology. A staggering 96% of codebases now incorporate some form of OSS, demonstrating its widespread adoption. This collaborative spirit extends to platforms like GitHub, the world's largest hub for open-source development, boasting over 100 million users worldwide.



Even within the commercial sector, the value of open source is recognized. Amazon Web Services (AWS), a major cloud computing platform, actively supports the development and maintenance of open-source projects. This commitment was further solidified in December last year when AWS pledged its patent portfolio to an open-use community.



This trend towards open-source collaboration comes at a time when public trust in private tech companies is declining. In response, organizations like Google, Spotify, the Ford Foundation, Bloomberg, and even NASA have established new funding initiatives. These efforts not only support open-source projects but also extend the principles of open collaboration to scientific research endeavors – a movement known as open science.



The widespread adoption of open-source software (OSS) has brought benefits and challenges. While OSS has become a cornerstone of modern technology, its long-standing leadership and diversity issues require critical attention.

Hello everyone and welcome back to the Cognixia podcast. Around 423 years ago, the titular character of Shakespeare’s legendary play – Hamley said “To be or not to be”. Today, four centuries later, we ponder on another such dilemma, and we say, “To Devin or Not to Devin”. Now if that confuses you, allow us to explain, because that is what today’s episode is all about – Devin.ai. So, fasten your seatbelts amigos and amigas, we are in for a ride.

Devin is a revolutionary AI that functions as a software engineer. This groundbreaking technology, created by Cognition under Scott Wu's leadership, can code, debug, and even develop apps and websites. Devin signifies a major advancement in AI's role within software development. Unlike AI advancements that threaten job security, Devin is designed to work alongside humans, boosting productivity rather than replacing them. This AI's ability to learn and adapt is transforming how software engineering tasks are tackled, paving the way for a future of closer collaboration between humans and AI.

Devin.ai isn't your average program. This cool AI tool is like having a whole new kind of engineer on your team – one that can code! Devin understands your instructions like your text commands, to be specific, and can tackle tasks like checking how well an app performs.

The way it works is super nifty. Devin has its own toolbox – a command line, code editor, and even a web browser. Using these tools, Devin can not only access information but also understand it, thanks to its built-in reasoning engine. Plus, it seems to have some serious long-term planning skills, likely powered by fancy reinforcement learning.

So, what can Devin actually do? Well, buckle up! This AI can build websites, find, and fix bugs in code like a champ, deploy applications, and even train other AI models. Sounds pretty impressive, right?

Hello everyone and welcome back to the Cognixia podcast.



The increasing popularity of electric vehicles (EVs) is accompanied by growing concerns about malfunctioning charging stations. This presents challenges for both EV owners and the companies that manage charging infrastructure.

The global shift towards electric vehicles (EVs) has experienced significant momentum in recent years. Governments around the world are actively promoting EV adoption through purchase incentives and investments in charging infrastructure. However, this rapid growth has exposed a critical gap – the lack of a sufficiently developed charging infrastructure. Owing to this, there is significant ‘charging anxiety’ in the market, if we can call it that. People are not as much worried about the range, as they are about reliable, safe charging.

The burgeoning popularity of electric vehicles (EVs) is encountering a significant roadblock: unreliable charging infrastructure. A substantial portion of EV owners experience the frustration of encountering malfunctioning or inoperable charging stations. Industry reports indicate that over 20% of charging attempts fail, with a staggering 72% of these failures attributable to charger issues.

This pervasive problem extends beyond mere inconvenience for users. It translates into a substantial financial burden. Estimates suggest that as much as $20 billion of the global $100 billion investment in EV charging infrastructure is currently rendered ineffective due to non-functional chargers.

Hello everyone and welcome back to the Cognixia podcast.

What is CI?
Continuous integration (CI) is a fundamental practice within the DevOps methodology. It emerged in the late 1990s as a response to the challenges of traditional software development, where infrequent and large code merges often led to integration issues and bugs. CI automates integrating code changes from developers into a central repository. Every time a developer commits their code, automated builds and tests are triggered, providing immediate feedback on the code's functionality and compatibility with the existing codebase.
This continuous integration cycle offers significant benefits to both developers and users. Developers can identify and fix errors early in the development process, leading to faster bug resolution and a more stable codebase. Additionally, CI empowers developers with frequent feedback, allowing them to iterate and improve code quality more efficiently. Ultimately, CI translates to a smoother development process and a more reliable, bug-free final product for users. By enabling faster development cycles and early detection of issues, CI paves the way for quicker delivery of new features and functionalities to users.
So, CI has been around for a while now. But then, so has DevOps.
DevOps has been around for a while, yeah, but that's a good thing! Many of you haven't experienced the struggles of waterfall development or even know what tools like Visual Test were – that's awesome! While understanding different approaches can be helpful, focusing on the current tools that matter most is key.
Today, we have entire DevOps stacks that streamline development, building, testing, and even deployment within an agile environment. These constantly evolve, with new features and capabilities emerging all the time.
Remember how everyone used to talk about Application Release Orchestration (ARO)? That term faded away, right? You might even hear it again occasionally, sparking a "wait, is that coming back?" moment. Vendors come and go, products merge, and some disappear entirely. This is a sign of a healthy market – needs evolve, users mature, and better solutions emerge. Sure, having a product vanish can be frustrating, but the prevalence of open source in CI/CD helps soften the blow. As outdated tools fall by the wayside, newer, better options take their place, making the whole ecosystem stronger.
Speaking of tools, let's talk about Jenkins. It's widely used, maybe a little too widely used. Usage seems to be dipping, and the developers are making improvements to address things that push organizations toward other solutions. The good thing about Jenkins is that it can do everything. But that is also part of the problem with Jenkins. While Jenkins was once a simpler tool, years of competition and evolving needs have turned it into a bit of a heavyweight. If you're working on a small project or a team using it solo with basic requirements, all you really need is something that gets a quality product out the door fast.

Hello everyone, and welcome back to the Cognixia podcast. how does ITIL 4 help you be a better leader?

first, ITIL 4 enables you to have more holistic thinking. ITIL 4 moves away from siloed thinking and encourages leaders to consider the "Four Dimensions of Service Management." These dimensions - Organizations and People, Information and Technology, Partners and Suppliers, and Value Streams and Processes - help you see the big picture and make decisions that benefit the entire ecosystem.

Second, ITIL 4 will help you lead with agility and adaptability. The IT landscape is constantly evolving. ITIL 4 emphasizes the importance of being flexible and responsive to change. As a leader, you can foster an agile environment where teams can quickly adapt to new technologies and market demands.

Third, ITIL 4 facilitates and encourages collaboration. Gone are the days of the lone wolf leader. ITIL 4 highlights the importance of collaboration across teams and departments. By fostering a collaborative culture, you can leverage the diverse expertise within your organization and achieve better outcomes.

Fouth, ITIL 4 emphasizes adopting a customer-centric approach and it inspires you to do the same. ITIL 4 focuses on the importance of aligning IT services with customer needs. As a leader, you can ensure your team focuses on delivering value to customers and meeting their expectations.

What is a leader without the ability to innovate and invest in continuous improvement? Fifth, this is what ITIL 4 helps you achieve. ITIL 4 encourages a culture of continuous improvement. As a leader, you can create an environment where innovation is encouraged, and lessons learned are used to constantly improve processes and services.

These are just some of the ways that the concepts and frameworks of ITIL 4 can help you be a better leader. When you get down to implementing it, the possibilities will be endless.

Hello everyone and welcome back to the Cognixia podcast!


who is a data steward?
The data steward role emerged in the early 2000s as organizations grappled with the explosion of digital information. As data became a strategic asset, concerns arose about its quality, security, and compliance with regulations. Enter the data steward: a champion tasked with overseeing the well-being of an organization's data assets.
Popularity for this role soared with the rise of data governance initiatives and the implementation of stricter data privacy regulations like GDPR and CCPA. Data stewards became crucial in navigating the complexities of data management, ensuring data accuracy, accessibility, and responsible usage.
Their responsibilities are multifaceted, encompassing everything from defining data ownership and access controls to managing data quality and ensuring adherence to data governance policies. They act as a bridge between technical and business teams, translating data needs into actionable plans and ensuring data is used effectively to drive informed decision-making.
Data stewards play a critical role in ensuring the quality, security, and responsible use of data within an organization. Their work could revolve around multiple areas, such as:
One, data governance and policy.
Here, a data steward would be involved in defining and enforcing data governance policies, collaborating with stakeholders, monitoring compliance, etc.
Two, data quality and management.
The data steward could be actively working on defining data standards & formats, monitoring data quality, and ensuring proper documentation takes place for data origin, transformation, as well as usage to maintain traceability and accountability.
Three, data security and access control.
A data steward’s role would require defining and enforcing data access controls, implementing security measures, and staying updated on data privacy regulations like GDPR and CCPA, etc. They would work in tandem with other teams to ensure the right data security measures are implemented across the organization.
Last and most importantly, communication and collaboration.
Data stewards act as an important liaison between the technical and the business teams, acting as a bridge between the technical aspects of data management and the business needs of different departments. They are responsible for promoting data literacy in the organization. Their contributions play a critical role in enabling data-driven decision-making in the organization since they are responsible for translating data insights into actionable plans for various data functions.