Tag: Stack Overflow

  • Key Insights From the Stack Overflow 2023 Developer Survey

    Key Insights From the Stack Overflow 2023 Developer Survey

    Stack Overflow has released its seminal yearly developer survey. The 2023 report, which surveyed over 90,000 developers, provides a comprehensive view of the current software developer experience.

    Below, I’ll highlight a few important findings, namely the significant programming language and tooling preferences, the use of AI in the development workflow and what these trends could mean for the DevOps field. I also gathered insights from Joy Liuzzo, vice president of product marketing at Stack Overflow, to dive deeper into some of the findings.

    Developer Technology Preferences in 2023

    Of note is that more and more developers are learning to code online. Learning to code using online resources increased from 70% in 2022 to 80% in 2023. Although many developers (47%) still have a Bachelor’s degree in computer science or the equivalent, these trends underscore the movement toward alternative knowledge solutions, especially for younger programmers. The topmost online resources include technical documentation, blogs, forums and how-to videos.

    JavaScript is still king—it’s now in its eleventh year as the most common programming language. But it’s worth highlighting that Python has overtaken SQL as the third top language. “SQL was solidly in the top three (JavaScript, HTML/CSS, SQL) since 2015, so it’s a big deal for it to have fallen below Python,” said Liuzzo. “We’ve seen Python’s popularity increase based on the number of questions asked on our public site, so we’ve been expecting some shifts.”

    TypeScript and Bash/Shell have also consistently grown in usage over the last few years. “These two languages are involved with the functions of other popular programming languages, explaining their prevalence among programmers,” Liuzzo said.

    PostgreSQL also overtook MySQL as the most common database type. In terms of web frameworks, Node.js and React.js are the most dominant. Other frameworks, like jQuery and ASP.NET, are showing signs of going out of style, likely because they are older web frameworks.

    Spotlight on AI

    The explosion of new AI innovations, such as large language models (LLMs) and chat-driven generative AI tools, had a major impact on this year’s technology findings. In fact, 83% of respondents have used ChatGPT over the past year. This is followed by Bing AI (20.6%), WolframAlpha (13.36%) and Google Bard AI (9.86%). GitHub Copilot was ranked as the top most-used AI developer tool.

    There was a significant spike in using AI tools amongst those learning to code—these folks often see benefits like speeding up learning, increasing productivity and greater efficiency. “Pair this with how they are currently using AI tools to debug and get help (68%) and learn about a codebase (50%), and we see that the commonality is that AI tools enable learning,” explained Liuzzo.

    That being said, there’s skepticism around AI’s accuracy, and only 13% see improved accuracy in coding as a benefit of using such tools. These pain points may resolve as LLMs evolve, but for now, there still needs to be human judgment to catch bugs and avoid hallucinations.

    “AI has a complexity cliff. Much like Helmsman’s complexity cliff found in project management, after a certain point, the ability for AI to handle all the nuances and interdependencies of a solution drops off,” said Liuzzo. “That’s when humans, their ability to apply judgment and have original thoughts, saves the day.”

    So what are some takeaways for those working in the DevOps field, namely DevOps tooling providers and platform engineers? Well, new tooling preferences and habits will continue to evolve in the DevOps field in new ways. Here are some potential examples:

    • More Markdown-based collaboration. Markdown is the most admired asynchronous tool and has increased in popularity this year. New programmers are adopting a blend of Markdown, GitHub Discussions and Notion for their asynchronous tooling. Flavors of Markdown are already being used for comments, merge requests, issues and more.
    • Continued Docker reliance. Docker remains the top-used tool, followed by npm and Pip. Despite the rise of managed container services, Docker is still a popular way to package and distribute software.
    • Challengers to the big three loom in the distance. Amazon Web Services (AWS) is still the most-used cloud platform at 48.62%. It’s followed by Microsoft Azure (26.03%) and Google Cloud (23.86%). Yet, newer developers want to work more with Hetzner and Vercel.
    • Online learning is paramount to knowledge sharing. Given the steady increase in new programmers and their reliance on online resources rather than traditional schooling, DevOps and open source communities should seek to enhance their online footprint by making knowledge like tooling documentation and tutorials easily consumable.

    Last but not least, generative AI is set to enhance programming in many areas and is already becoming embedded into many environments. Just as AI can be used for code generation and debugging, LLMs will likely assist the DevOps side of the equation, helping automate the CI/CD pipeline, optimize infrastructure, detect anomalies and provide more chat interfaces to initiate these capabilities.

    “AI tools are empowering and enabling learning,” said Liuzzo. “Generative AI will democratize coding and grow the developer community by several folds—and that growing number of developers will be the ones using the tools and also verifying and validating the outputs as they learn—bringing the power of the developer community and the technological power of AI together.”

  • Yeah, You’re Doing DevOps

    Yeah, You’re Doing DevOps

    The Stack Overflow annual survey of developers came out this month, and it has a lot of interesting data points in it. There is a lot that I wish was different about their questions/methodology, but one thing caught my attention. Docker, Kubernetes and similar tools (Ansible and Terraform are in there at lower percentages, for example) make up more of the responses than can be accounted for by people with “DevOps” in their title.

    Sometimes by a lot.

    That means we have a fair number of developers that are doing DevOps, but who aren’t DevOps team members. Yeah, there are a few systems admins in the ranks of the respondents also, but not enough to cover the discrepancy. If every respondent that was in DevOps and sysadmin roles used Kubernetes, there would be just enough to cover the number of respondents that said they used Kubernetes “extensively” over the past year. It’s unlikely that all of them are Kubernetes specialists. And that doesn’t touch on Docker, with a whopping 40% of respondents saying they use Docker extensively. Any developer with recent experience can explain away Docker—though “extensive” is a bit strong for your average developer’s usage, it is becoming part and parcel of development, using containers to host dev environments, test, even build tools. And, of course, some deployments. But 40% is still a lot.

    So, if your title is developer, and you’re using deployment tools on a regular basis, go ahead and call yourself DevOps. That’s not the only criteria, but if you were going to pick one, the breadth that using deployment tools represents combined with the implication that there isn’t an ops person worrying about that type of thing makes “uses deployment tools” a good stand-in test.

    To the nearly 18% (20% of pro developers) of you using Yarn, I tip my hat. I used it for a couple of years early on in its life, and am happy to say I do not need to use it any longer. I assume your usage is not tied to Hadoop and that it has greatly improved over my 2015-2016 experience. Still, y’all rock, just by definition of using it to get resource scheduling down. It ain’t easy.

    Across the board, the number of DevOps/Ops tools that make these lists is amazing for a developer survey – nearly 9% of respondents use Ansible, and nearly 9% use Terraform. There is undoubtedly overlap, so the actual number that uses one or the other is less than 18%, but still, nearly one in 10? That’s huge. And that’s DevOps or Ops, not purely developers. Regardless of title.

    And that’s been a hallmark of development since the field took off—doing what needs to be done to deliver software. This is just another iteration, and you’re rockstars, regardless of title. You keep delivering apps that run the business—let them call you whatever they like. Money talks; titles are pretty much meaningless. Not like you’ll retire on a title, but bonuses or stock grants? Those you might retire on.

  • Stack Overflow Launches Stack Overflow for Teams

    Stack Overflow Launches Stack Overflow for Teams

     

    Stack Overflow for Teams provides a private version of the popular platform to help teams ranging from 10 to 500 developers improve communication, reduce chaos, and increase efficiency

    NEW YORK, New York – May 3, 2018 – Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers, today announced the launch of Stack Overflow for Teams, the new platform that allows development teams of any size to quickly find answers to questions without disrupting their workflow.

    Leveraging the well-known Q&A format from stackoverflow.com, Teams is a private, internal central knowledge source where team members can find answers to their questions quickly and efficiently. Stack Overflow for Teams presents a near-instantaneous answer to any work-related question. Where internal wikis and documentation quickly become outdated and messaging platforms make it impossible to rediscover information, Teams provides an intuitive, searchable platform with answers that are editable and crowd-sourced by one’s peers, meaning answers will always be up-to-date and provided by colleagues who are subject matter experts. This ever-evolving resource scales as the team grows, enabling team members to find up-to-date information now and in the future.

    “By and large, developers just want to get on with their work,” said Joel Spolsky, co-founder and CEO of Stack Overflow. “Our Teams platform not only allows developers to quickly find the answer they need to keep working, but it also allows them to share their own knowledge internally, increasing the expertise and productivity of their teams.”

    Alex Miller, General Manager of Teams & Enterprise at Stack Overflow, added, “Our Enterprise platform, which is used by hundreds of thousands of developers on teams from global leaders like Bloomberg and Microsoft, has proven an invaluable resource for large development teams to collaborate and share knowledge in a way that optimizes for efficiency and scalability. With Teams, we now extend the benefits of that platform to companies with teams of any size.”

    In addition to the familiarity of Stack Overflow’s platform coupled with the benefits of a private, internal knowledge source, Stack Overflow for Teams offers a number of useful features:

    • Unlimited private questions and answers: Team members can ask as many questions as they need, and unlike monolithic internal wikis, they can expect relevant answers from team members to their specific questions.
    • Intuitive archiving feature: Tags allow users to sort through questions and answers by topic in order to dig deeper into a subject of interest. When an answer to a given question populates, the user will also see related questions and answers that could prove useful.
    • Member profiles: The Teams platform showcases each user’s specific skill set and the topics about which they frequently answer questions, so team members know whom to consult within their organization if they need further insight.
    • Seamless integration into the workflow: Stack Overflow for Teams is on stackoverflow.com, already a popular daily destination for developers. Furthermore, Teams integrates with existing tools like Slack, so Q&A fits easily into a team’s existing workflow and communication processes.

    “We needed a good way of passing down knowledge between team members, because we saw the same questions being asked over and over in our instant message channels,” said Tim Golen, Engineering Lead at Expensify. “Almost immediately, we found that the Search function in Teams returned relevant results in a quicker, more accurate way than chat would. We anticipate Stack Overflow for Teams increasingly becoming our go-to resource for knowledge-sharing.”

    For more information, visit www.stackoverflow.com/teams.

    About Stack Overflow

    Stack Overflow is the largest, most trusted online community for developers to learn, share their knowledge, and build their careers. More than 50 million professional and aspiring programmers visit Stack Overflow each month to help solve coding problems, develop new skills, and find job opportunities.

    Founded in 2008, Stack Overflow partners with businesses to help them understand, hire, engage, and enable the world’s developers. To learn more about Stack Overflow’s business solutions–– technical recruiting, advertising, market research, and enterprise knowledge sharing––visit business.stackoverflow.com.


     

    c: (650) 302-8071

    e: maddie@bulleitgroup.com