DEV Community: Lampis P

Inclusive Tech: The Synergy of AI and Developer Creativity

Lampis P — Fri, 22 Mar 2024 14:05:42 +0000

by Katie Brenneman

There should be no question that the digital landscape should be accessible to all users. After all, it’s a primary forum through which we communicate and collaborate. Developers have an important role to play here. Their perspectives, insights, and creativity drive how products and platforms are designed to meet the needs of diverse audiences.

Yet, it’s still a challenging process. One of the ways that developers are addressing these challenges is by utilizing artificial intelligence (AI) tools. This isn’t about expecting machine learning to magically make all projects more accessible. Rather, it can be a supportive tool for developers to use alongside their creativity to optimize the inclusivity of products.

Let’s explore this idea of AI and developer synergy further.

Ensuring Accessible Platforms

Perhaps the most common area in which AI and developer creativity meet is in web and software accessibility. Just 3% of the internet is considered to be accessible to individuals with disabilities. There’s a need to bridge this gap quickly and effectively.

As a tool, generative AI can be useful here for quickly creating basic code to specific standards of web and software accessibility. ChatGPT and similar platforms can produce drafts of code to the parameters set by the developer. This means that, alongside keeping general web accessibility standards, developers can request code to address the potential inclusivity issues that are common to the specific type of software or website.

That said, the developers themselves play a huge role in getting the most out of generative AI coding. AI cannot produce flawless solutions every time. After all, it doesn’t have access to human empathy and perspectives that can enable developers to spot potential accessibility issues the AI misses.

For instance, those living with genetic mutations can experience a range of nuanced accessibility issues. Some conditions lead to vision difficulties, particularly inherited retinal degeneration. This can make seeing and interacting with software and websites challenging without assistance. Other mutations can also result in conditions that cause non-syndromic hearing loss, affecting a person’s ability to listen to audio media. Developers need to take the time to get a good understanding of the practical hurdles of such conditions. This enables them to be better collaborators with AI in creating accessible platforms.

Influencing Efficiency

It’s important to recognize that efficiency can influence accessibility. We are still learning new things all the time about the challenges people with different disabilities face, particularly regarding emerging software and hardware tech.

For instance, virtual digital environments, such as the metaverse, are coming to the fore. As a result, there’s growing attention on how current virtual reality (VR) and augmented reality (AR) hardware and software can present hurdles to those with disabilities. Developers must be able to respond to this information quickly and effectively to ensure all users have a fair chance to engage meaningfully.

This is another area in which AI tools can be paired with developer creativity. For designers, this begins with doing deep dives into the notes you receive so you can get specific about the issues you need to address. Get to know not just what the hurdles to accessibility are, but also why they are problematic.

A good example of this relates to the aforementioned issues with the rise of VR. Microsoft conducted research into the effects of various low vision conditions. This enabled them to create tailorable visual and audio augmentation tools for developers to incorporate in software. Committing to conducting or seeking out this kind of solid research enables you to devise a range of relevant creative solutions that improve inclusive usability.

Prioritizing Efficiency in Production

However, particularly if you come up with several solutions, it’s not efficient to just introduce one at a time to the public and see if it comes back with issues. AI helps here by efficiently simulating user behavior — including if users with disabilities are using adaptive tools — and testing each of your potential solutions. This helps to highlight any continuing or new issues related to your changes and narrow down the most likely options for introducing back to the marketplace.

AI’s potential for improving efficiency even extends to when developers are part of teams creating physical products. AI-driven design and manufacturing software can speed up product improvement through automation. When developers provide details about inclusivity needs for the design, platforms can generate multiple design alternatives, produce 3D models, and even suggest efficient machining strategies for production.

Empowering Diverse Developers

It’s easy to look outwardly at how the synergy between AI and developers helps create accessible products and online materials. However, it’s also important to understand that it can benefit professionals and the industry, too. Software tools that use machine learning to support development working practices are starting to empower more diverse coders to contribute to the field.

One good example of this is how AI is used for coding without physical interfaces. Developers who live with physical challenges and may not be able to type code can benefit from AI-driven virtual assistants. Conversational AI that interprets voice inputs can connect to development software and enable coders to directly speak their code rather than type it. Importantly, these platforms can be trained on the nuanced jargon and intentions of specific industries, which makes them more accurate collaborators.

Conclusion

Genuine inclusivity is a priority when developing for our increasingly digitally reliant society. AI tools offer developers opportunities to ideate and test more efficiently to improve the user experiences of people with a wide range of accessibility challenges.

That said, the perspectives of people navigating these challenges surrounding disability have a vital role to play, too. Developers must take the time to have meaningful discussions and perhaps involve them in the dev process. This helps to ensure more equal access to products, software, and websites in the digital landscape.

5 Things You Need to Know About Pair Programming

Lampis P — Thu, 14 Mar 2024 12:36:33 +0000

by Jessica True

Programming and development is a minefield of complexity, creativity, and technology. When a business problem needs solving, it often falls to these hardened defenders of the code to find a solution and save the day. Without the expertise of trusted developers, our entire digital ecosystem would fall into disrepair — it may have never even been made.

Still, for the incredible importance of these individuals in business structure, all too often the work itself can be pushed to the side, leading to isolated individuals tackling huge problems that require more resources than they’re given. While there have been a host of strategies to alleviate this, pair programming is emerging as a panacea to the many issues that have plagued programming teams for decades.

What is pair programming?

Pair programming is the approach of creating duos of programmers to tackle a specific project or task. They will work collaboratively to develop the code and tackle any problems faced and will work simultaneously towards the end goal. It is a simple concept in truth and can be modified to suit your development team too, making it a flexible approach to development that has grown in popularity over time.

Pair programming can be employed in development teams of all sizes, from start-ups with fewer than ten employees to huge businesses that routinely have enterprise meeting sessions of dozens of team members.

With that said, the concept does invite a host of questions such as how is the work achieved without stepping on each other’s toes, what is the best approach to establishing a pair programming strategy, and is it even beneficial to apply two individuals to work on one problem? We’ll answer these below and explain the key bits of info you need to know.

5 things to know about pair programming

As adaptable as the concept is, there are a series of established ideas that most pair programming arrangements will adhere to.

There are 3 maExpert – Expertin styles to consider

The vast majority of pair programming setups will fall into one of three main methods — ping pong style, unstructured style, and the driver-navigator approach. Each of these methods has advantages and disadvantages, so it’s worth exploring each to determine what works best for both the individuals and your business.

Ping-pong style

Ping-pong programming focuses on having developers push each other forward with a series of rotating test-based development. Once the problem has been identified and the requirements to resolve it established, one developer will create a test to benchmark successful code commits against. The other developer will program in accordance with those tests and seek to pass them. As the codebase matures and the tests are passed, they can swap roles and work towards a new goal.

This is a great approach to ensure both developers are engaged and are working productively, though the time taken to complete tasks may be longer than other approaches.

Unstructured style

An unstructured style is pretty much what you’d expect — no-holds-barred collaborative development. Programmers are given the autonomy to determine how to best tackle the project and can create code in tandem or in silo of one another, however suits them best.

While this can be a superb way of tackling complicated issues that require two sets of eyes, it can also lead to mismatched inputs and a loss of engagement if one developer outshines the other.

Driver-navigator approach

In this style, developers take two distinct roles. The driver creates all code and contributes the direct work, while the navigator will critique, examine, and help propel the driver forward in their efforts.

For example, the navigator might research information — such as seeking to define ERM at the driver’s request in relation to the task they’re working on — or solutions to an impending issue while the driver continues making progress elsewhere. This helps ensure that work is always moving forward and that both developers feel supported. Roles will often swap over the course of a project, especially when areas of expertise present themselves and an individual can tackle them.

Different pairings can lead to different results

The pairings of developers will have a marked impact on how a task and the individuals will progress. Most developer partnerships can be identified as the following:

Expert – Expert

Ideal for highly complex tasks that require vast amounts of knowledge or expertise to accomplish. Both developers will be highly skilled and can support each other in creative problem-solving and collaborative contribution to the codebase.

Expert – Novice

Ideal for medium-scale projects where both developers can partake in contribution and the senior developer has room to educate and monitor output before task completion. The novice benefits from expert guidance and support, while the expert gets the opportunity to educate and support another team member.

This pairing is particularly effective when aiming for a minimum viable product, as the expert can guide the novice in focusing on essential features and functionalities to deliver a functional solution efficiently.

Novice – Novice

Ideal for simple or low-priority projects, where junior developers can spend time learning and growing with each other to resolve the issue. Best used as part of onboarding activities and training exercises, such as exploring the differences and benefits between Spark vs PySpark.

Depending on whether you need absolute precision within a project or want to create learning opportunities for the team, pairing your developers correctly is a key part of effective pair programming management.

Pair programming can boost morale while speeding up projects

Let’s say your development team is tasked with building a framework allowing for artificial intelligence in customer experience monitoring, and a series of required functions are outlined — live monitoring of data, and export tools for third-party manipulation at a minimum. A project of this scope might seem unmanageable for an individual to tackle, but a pair of expert programmers can work together to break it down and succeed.

The morale boost from working together cannot be understated, especially when things get challenging, and there will be time saved from having additional resources working on a task. In many cases, simply having support when facing difficult circumstances can be the difference between success and failure.

Additionally, with the right infrastructure, like dedicated hosting, teams can ensure consistent and reliable performance, even when working remotely.This is particularly crucial for industries such as finance, where data security and confidentiality are paramount concerns. Therefore, pair programming becomes an indispensable strategy for a finance software development company, ensuring both efficiency and security in collaborative coding efforts.

Pair programming can work remotely with the right tools

With modern technology, it’s incredibly easy for developers to work remotely and still work in pairs contributing to a shared codebase, communicating effectively the whole way. While it is still recommended for teams to work side-by-side when contributing to a single resource, remote working provides a viable alternative that supports modern practices in 2024.

There are several tools that can help facilitate quality output, such as robust communication tools — shared or remote desktop access, screen sharing capabilities, and reliable text and voice communication apps all help to build a seamless experience for developers working as a pair.

Additionally, it’s essential to prioritize security measures, including DMARC compliance, to ensure the protection of sensitive information and maintain a secure development environment. This helps prevent email spoofing and phishing attacks by allowing domain owners to specify how their emails should be authenticated and handled by receiving mail servers.

Not every pairing is going to work out

The unfortunate truth is that everyone isn’t always going to get along. Some personalities clash, and some methods of working won’t lead to an effective partnership. Instead of pushing the issue, if you see problems arise then act to make a change.

This can present itself in stagnation on a project, low output, complaints from a team member, or a lack of contribution by an individual. Always monitor these factors to ensure that everyone is happy and working towards a common goal.

How can pair programming be helpful?

Much in the way that AI in communication appears magical in its ability to transform internal and external comms, an established development pair is capable of programming wizardry they’d be unable to achieve alone.

Think of pair programming as a force multiplier to expedite projects, as a method to train individuals in a real-world environment, and to learn more about your individual developers themselves and their capabilities. It’s a flexible tool to help break programmers out of ruts, promote their personal development, and let them showcase their creativity in a supportive atmosphere.

Can pair programming be harmful?

There are some risks to consider when actively pursuing a pair programming approach. Many of these can be mitigated with proper care, and some will only arise when the pairs themselves are not working effectively.

The main challenges to be aware of include:

Increased cost per project
Lengthier time to complete some projects
Less capacity to tackle multiple projects
Internal conflicts

As long as you monitor your teams closely, the above issues can be largely sidestepped, and the benefits of pair programming can truly shine.

The next steps

Start thinking about how you can implement pair programming strategies into your upcoming projects. If you have reports of stalled development or frustration from individual programmers, that’s the perfect time to explore pair programming and provide a fresh approach for the team to get involved with.

Always remain attentive and agile in your actions when managing pairs. If they’re unhappy or ineffective, don’t be afraid to switch things up and keep changing the dynamic. When things start working, that’s your cue to step away and let them get on with the task at hand. Pair programming can help breathe new life into tired development processes and get teams working creatively again.

You can check more interesting articles in the Developer Nation blog

How Does Collaborative Coding Work?

Lampis P — Fri, 01 Mar 2024 13:09:13 +0000

by Sam O'Brien

We could always do with an extra pair of eyes or another brain to work on our projects. That’s why collaborative coding can be such a useful tool for programmers looking to speed up their development process.

By working on your code with either a team or with one other developer, you can finish your project more quickly while also reducing the amount of errors and bugs – after all, they’re a bit more helpful than the traditional rubber duck.

However, programming is often seen as an independent process, so how exactly does collaborative coding work? We’ll explain that, plus its different benefits and drawbacks, and how you can make it work in your organization.

What is collaborative coding?

Collaborative coding simply refers to any process that involves more than one person working together on a piece of code. In the past, this might have had to take place in an office around a couple of computers but today you can download RealVNC’s MAC remote desktop or other remote working technology to collaborate on code from anywhere in the world.

There are three specific types of work that come under the umbrella of collaborative coding. You might have heard of pair programming, which is when two programmers pair up to work on a project. When more than two people work together, this is referred to as mob programming.

The final form of collaborative coding – code sharing – is less about a collaborative process. Instead, it’s when code that has been developed independently is shared in order to let other developers debug or review it. Code sharing is already widely used in open source projects – that’s why we’ll be focusing on pair and mob programming.

The benefits of collaborative programming

Ultimately, regardless of whether you use a pair programming or mob programming model, collaborative coding is about working together. But what’s the point of collaborative coding? Here are the main benefits:

1. Increased efficiency
Improving efficiency and productivity is a key goal of any business, whether that’s a huge restaurant, a small business phone service provider, or a software developer.

Collaborative coding allows you to work through issues with someone else, meaning that you can draw on another career’s worth of experience and problem-solving. When it comes to producing new ideas, you’ll also find that collaborative working will let you get to appropriate creative ideas more quickly.

Efficiency will also improve in the more technical aspects of your code. With two or more pairs of eyes looking over your code, you’ll be able to spot mistakes sooner. As well as this, you’ll be able to establish an instant and informal process of code review and feedback, meaning that your code will be successful as early as possible.

2. Better resilience
When a project is the sole responsibility of one developer, all it takes to knock that project off track is a bout of flu. As well as this, you can be forced to abandon long-term projects altogether if a developer leaves the organization.

Using collaborative coding will mean that these risks are significantly decreased by spreading responsibility for projects across multiple developers. If a programmer becomes ill, for instance, coding can continue without them, meaning that your projects are more resilient and safeguarded against disruptions.

3. Easier training and onboarding
When new developers join your organization, there are few better ways for them to get to grips with how you do things than by working with an experienced programmer. This means that adopting a model of collaborative coding will make it easier to onboard new recruits.

Using pair programming is also a great way to ensure that more experienced programmers are constantly developing their practice. Without this, developers can become stuck in their ways: collaborative coding is an innovative way that you can encourage cross-training in different programming languages, for instance.

Collaborative coding challenges

While there are many benefits, it’s also important to consider some of the issues that come with collaborative coding:

1. Higher costs
When you’re viewing collaborative coding from a financial perspective, you’ll soon come to the realization that you’ve now got two developers being paid for a job that you previously had just one developer working on.

This means that collaborative coding will often bring higher initial costs – however, these overheads can be overcome in the long term as you see the quality and speed of your programming improve. Additionally, the increased resilience means you’re less likely to end up starting projects from scratch when unexpected situations come up.

2. Communication problems
Programmers are often used to working independently – collaborative coding, on the other hand, requires almost constant communication between team members. This is essentially a separate skill that needs to be developed over time, so developers new to collaborative coding may struggle to communicate effectively as they code.

Starting people off on smaller projects and pairing up the right people with the right skills can help. And don’t forget to provide training, particularly if you’re using collaborative platforms, as you want to ensure everyone on the team gets the most out of it.

3. Platform requirements
As well as requiring a new form of communication, collaborative coding may demand different platforms and technology. Luckily, there are lots of platforms that are specifically designed for collaborative coding that work both in-office and remotely.

You might also find that you have to invest in other pieces of software to make the collaborative process as smooth as possible, from on demand remote support software to a team messaging app. While these platforms are easily accessible, this nevertheless presents an additional upfront cost.

Making collaborative coding work for you

With these challenges in mind, how can you make collaborative coding work for you? Here are our best practices for collaborative coding:

1. Find the right platform
When looking for a platform to host your collaborative coding efforts, you need to invest in one that is perfect for your needs – think about the size of your team (and whether you’re planning to scale further), your preferred programming languages, and its ease of use. You should also look out for platforms that have advanced security measures to protect you against malicious software or cyberattacks.

While you’ll be able to continue using testing software, you’ll also want to consider whether your existing development software is able to streamline effectively with your new collaborative platforms.

In addition, consider project collaboration tools like Jira, which allow developers to plan, track, and work faster when coding software. Encourage teams to collaborate on deploy previews when using these tools, so together they can test and review any code changes before deploying to a live environment.

2. Create balanced teams
Of course, the platform will mean nothing if you don’t have the right people using it. You’ll want to make sure that your collaborative coding teams include a range of different skills and experiences – there’s no point in pairing up two experienced developers who use the same programming languages and who have the same expertise as each other.

In order to help you create balanced teams, you might want to create the equivalent of an online directory for your organization: list your programmers, their relevant skills, and their personal qualities.

3. Assign clear roles
Once you’ve created a collaborative coding team, you should make sure that every member knows exactly what their responsibilities are. In pair programming, a common distinction is between the ‘driver’ (who actually writes the code) and the ‘navigator’ (who keeps larger goals in mind). These roles can be swapped regularly to keep things fresh.

In larger teams, it’s still important that everyone has a clear role. This will keep everyone focused on their specific task, while also ensuring that you allocate human resources effectively by giving individual programmers roles that best suit their abilities and skills; you’ll also be able to give junior and senior developers jobs that reflect their experience.

4. Communicate consistently and regularly
Having clear roles will also help with another key part of collaborative coding: communication. This is because developers will know who to talk to according to their problem or focus.

As well as this, you need to be sure to establish a consistent and regular routine of communication. When coding with others, constant communication will help programmers to spot errors and work together to overcome issues and problems.

This is an essential part of pair programming, but mob programming is also reliant on strong communication. A team of developers producing a remote desktop for Android phone, for instance, will need to have programmers working together to ensure that the final app is coherent and effective.

Collaborative coding – take your programming to the next level
Collaborative coding – whether that’s pair programming or mob programming – is a great way to boost the productivity of your coding projects, as well as to ensure that the overall quality of your code is improved.

There’s a range of different ways that collaborative coding can work. However, for it to be a success you’ll need to make sure that you use the right platform, assign people to the right teams, create clear roles, and maintain regular communication. With this, you can be sure that collaborative coding will take your code to the next level.

Finally, if you want to learn more about collaboration, you might also be interested in our post on How to Develop and Improve Collaboration in DevOps Teams– it’s full of great insights and provides a step-by-step guide.

Bio:

Sam O’ Brien – Vice President of Marketing
Sam O’Brien is the Vice President of Marketing for RealVNC, leading providers of secure, reliable remote access solutions. He is a growth marketing expert with a product management and design background. Sam has a passion for innovation, growth, and marketing technology. Sam has written for other domains such as Debutify and Cloudways. Here is his LinkedIn.

On the role of female coders in software development

Lampis P — Thu, 20 Jul 2023 22:00:01 +0000

Since the beginning of computing, women have consistently played a pivotal role in software development that has frequently been overlooked; from Ada Lovelace developing the first algorithms for modern computers to Margaret Hamilton’s crucial role in the development of on-board guidance software for NASA’s Apollo program.

However, despite women’s exceptional contributions to the field, they have often received less credit than their male counterparts, and their place in the field is questioned.

Today, efforts are being made across the software development ecosystem to address these historical biases. While efforts have been made to promote women to get involved in the historically male-dominated field, there is still considerable work to be done.

Data and technology are not free from bias. Past applications and software development projects have demonstrated the need for input from diverse groups2.

In this chapter, we specifically explore the involvement of women in software development. According to our latest global developer survey (Q1 2023), nearly a quarter of all developers (22%) self-identify as females, the highest proportion since we began asking respondents about their gender.

This is a small increase from two years ago, since Q1 2021, when female coders accounted for 19% of all developers.

This slight increase in the proportion of developers self-identifying as females can be partially attributed to the rise in the representation of women among early-to-mid-career developers. Women currently make up a quarter (25%) of developers between the ages of 25 and 34, the highest proportion of all age groups, up from less than 20% in Q1 2021.

This is followed closely by 23% of developers between the ages of 18 and 24. The highest proportion of women falling within the 25-34 age bracket indicates the possible beginning of a positive trend for the future of women in the tech industry. This is the age when people begin to settle into their careers and is a point where people are likely to develop additional skills that allow them to cross-train and enter industries of their choosing.

Further to this, we are also seeing an increasing presence of women in certain regions that are leading to an increase in the proportion of women in technology overall.

Specific highlights include the Middle East and Africa, where the proportion of women in technology in this region has gone from 10% in Q1 2021 to over 20% currently. Similarly, women made up 15% of developers in East Asia in Q1 2021 and now makeup almost 30% of developers.

Overall, a higher representation of women in the software development ecosystem is a great development. Not only do they bring critical perspectives and approaches to the work being undertaken, but diversity in the workforce offers fresh experiences that can help businesses address underserved needs.

It also enhances efforts to make spaces that are less hostile to women in both overt and subtle ways, allowing even more women to follow their interests in the technology space.

The proportion of women among developers varies substantially depending on the types of projects they are involved in. Virtual reality (VR) and augmented reality (AR) projects have the highest proportion of women, at 33% and 28% respectively, followed by games (28%).

On the contrary, backend services and web application projects have the lowest concentration of female coders, at just 13% and 16%, respectively.

With these sectors selecting those with formal degrees at higher rates than other areas, and a 10 percentage point difference between men and women having such a degree, this may be one factor in the lower presence of women.

Undergraduate degrees in computer science or equivalent are held by 45% of backend developers and 43% of web developers, compared to 37% of all developers.

Further, the lower proportion of women working in backend services and web application development may, in part, be attributed to the historically male-dominated culture within these sectors. Addressing cultural differences3 and fostering a more inclusive atmosphere can contribute to balancing representation and mentorship opportunities within these sectors.

Further, there may be potential unconscious biases in hiring practices derived from existing workplace culture, which may prevent certain development areas from harnessing the full spectrum of talent, and benefit from the input of individuals with diverse backgrounds.

Examining the sizes of organisations that female developers work for throughout various stages of their life and career could indicate that company characteristics have an influence on women’s decisions in the technology sector.

Like young men, young women are more likely to work as freelancers relative to other age groups and only return to similar proportions among developers aged 55 and above. Additionally, younger female developers (18-24) tend to work for smaller companies, whereas older female developers (45+) are more inclined to work for larger organisations with over 10,000 employees.

Examining a particular age group, women between the age of 35 and 44, may offer an insight into issues women have with progressing through their careers. Previous research into women’s careers in the software development sector has highlighted that women are promoted at a lower rate than men4.

However, when looking at the roles women self-identify with, we find that at mid-market companies (251-1,000 employees) and enterprises (1,001-10,000 employees) the percentage of women in management positions (20% and 29%) is significantly higher than at other organisation sizes (13% on average).

These organisations could offer better opportunities for career growth, decision-making, and leadership. In larger companies, management roles might be more hierarchical and bureaucratic, leading to less autonomy and slower career progression.

In smaller companies, limited opportunities due to their size might result in fewer leadership positions being available overall, and with women being a minority in software development, there are fewer women in leadership positions.

Further, there is an underrepresentation of women in certain leadership roles. 11% of men list their role as CIO, CTO, or IT manager, and 14% identify as technical team leads, compared to just 9% and 8% of women. This could create a cycle whereby there may be fewer mentorship opportunities for other women.

When there are fewer female leaders, it has been found in a range of fields5 that it can be harder for women to progress in their careers, and it can be more challenging for aspiring women to find mentors who can guide them, provide valuable insights, and help them navigate their career paths.

However, while still a minority of those in such roles, 25% of those in CEO or management positions are women, compared to their position as 22% of the developer population.

While only a small percentage difference, given their underrepresentation in other leadership roles, this represents an area where women are getting leadership positions. Among the previously discussed issues women may face, women are also less likely to apply for leadership positions where they do not fulfil all of the requirements than men6.

This may be leading women to also self-select towards management positions that are not solely dependent on technical skills.

The observation that women hold a higher proportion of CEO/management roles compared to men (7% against 5%, respectively), particularly in companies with more than 250 employees (8% of women to 4% of men), could indicate a positive shift in gender representation and diversity in leadership positions.

This trend might be driven by a changing corporate culture that is increasingly recognising the importance of gender diversity in leadership, leading companies to seek out and promote women into these roles6 proactively.

Embracing diverse perspectives at the decision-making level can result in better organisational performance and decision-making.

Another factor that may contribute to this observation is the growing appreciation for women’s leadership styles, which tend to be more collaborative, participative, and relationship-oriented. These qualities are often valued in today’s business environment and might make women particularly well-suited for CEO/management roles.

Moreover, women, through their skills and abilities, are likely actively contributing to this positive trend, demonstrating that they are well-equipped for leadership roles. Despite women remaining a minority in leadership this growing representation in CEO/management roles is a step in the right direction, highlighting the benefits of diverse and inclusive leadership.

Want to contribute to data such as the above?

Take the latest wave of our developer nation survey here!

Where does Security sit in Early-Stage Software Development: the Shift Left Approach

Lampis P — Thu, 25 May 2023 08:36:32 +0000

The average cost of a security breach in a hybrid cloud environment is estimated at a staggering $3.6 million making it critical for organisations to make software security one of the most important priorities.

Cisco’s most recent report, based on the findings from two SlashData global surveys that targeted enterprise developers, uncovers developers’ exposure to API security exploits, their outlook on security, and how they use automation tools to detect and remediate threats. Here is a detailed preview of the report:

1.Enterprise developers focus on prioritising security from the early stages of development

There is a significant rise in security threats; in fact, 58% of enterprise developers have had to tackle at least one API exploit in the past year alone. And to make matters worse, nearly half of them have experienced multiple API exploits during that time.

As modern applications increasingly rely on microservices, securing the APIs that connect these services becomes even more crucial. It is also true that juggling multiple APIs can make staying on top of security challenging. That’s why it’s essential to prioritise security from the very beginning of development to avoid wasting time and effort on reworking code and dealing with exploits later on.

Obviously, breaches should be ideally prevented. But if they do occur, organisations must be set up to act swiftly. According to the report, ,only one-third of enterprise developers can resolve API exploits within one day of a breach.

By treating security as a top priority from the start of the development lifecycle, organisations can increase preparedness and avoid costly mistakes down the road.

2.What is the right time to address security concerns?

Shift-left security is all about strategically placing security at the forefront. The cost savings from addressing security concerns early in the development process can be significant compared to dealing with security issues during deployment or after a security breach. In fact, according to the data, many organisations are already putting significant effort into identifying security vulnerabilities during the early stages of development, and as a result, have implemented additional security measures.

How do enterprise developers address security?

3.Relying on automations can account for faster, and frictionless operations

During the surveys, developers were asked whether they use automated approaches to security, such as scanning tools or automated fixes.

The most likely group of developers to adopt automated security approaches are key decision-makers and team leads who influence, manage, or set the strategy for their teams’ purchase initiatives (90%).

This probably indicates that many developers still don’t use automation tools for security. However, it’s important for developers to use the best tools when it comes to the production of secure code.

While more than half of enterprise developers are already shifting left, less experienced developers are still behind. Automation appears to be core to the shift-left approach, with two-thirds of developers using automated security tools.

Nevertheless, automation is not favoured by developers who wish to acquire more experience. This highlights a need for balancing the need for learning with the importance of using the best security tools available.The organisations that are set up to go that way are very likely to reap the fruit of shift-left security.

We have a new, short survey in order to understand the technologies and tools that Enterprise Developers use.

Are you a software developer, a database administrator, a data scientist, an engineer, an architect or involved in DevOps and SRE? Help us and make an impact on the developer ecosystem. Start here