The choice of programming language matters deeply to developers because they want to keep their skills up-to-date and marketable. Programming Languages are a beloved subject of debate and the kernels of some of the strongest developer communities. They matter to toolmakers too, because they want to make sure they provide the most useful SDKs.
It can be hard to assess how widely used a programming language is. The indices available from players like Tiobe, Redmonk, Stack Overflow’s yearly survey, or GitHub’s State of the Octoverse are great, but offer mostly relative comparisons between languages, providing no sense of the absolute size of each community. They may also be biased geographically or skewed towards certain fields of software development or open-source developers.
The estimates we present here look at active software developers using each programming language; across the globe and all kinds of programmers. They are based on two pieces of data. First is our independent estimate of the global number of software developers, which we published for the first time in 2017. We estimate that, as of Q3 2022, there are 33.6 million active software developers worldwide.
Second is our large-scale, low-bias surveys which reach tens of thousands of developers every six months. In these surveys, we have consistently asked developers about their use of programming languages across 13 areas of development, giving us rich and reliable information about who uses each language and in which context.
JavaScript continues to be the largest language community
JavaScript remains the most popular programming language for the 11th survey in a row, with over 19.5M developers worldwide using it. Notably, the JavaScript community has been growing in size consistently for the past several years. Between Q3 2020 and Q3 2022, Javascript experienced a 59% increase as 7.3M developers joined the community – one of the highest growths in absolute terms across programming languages. Not only do new developers see it as an attractive entry-level language, but existing ones are also adding it to their skillset. JavaScript’s popularity extends across all sectors, with at least a quarter of developers in every sector using it.
Developers joined the JavaScript community in the last two years
In 2020, Python overtook Java as the second most widely used language and now counts nearly 17M developers in its community. Python has continued to show strong growth, having added about 8M net new developers over the last two years. The rise of data science and machine learning (ML) is a clear factor in Python’s growing popularity. To put this into perspective, about 63% of ML developers and data scientists report using Python. In comparison, less than 15% use R, the other language often associated with data science.
Java is one of the most important general-purpose languages and the cornerstone of the Android app ecosystem. Although it has been around for over two decades, it continues to experience strong growth. In the last two years, Java has almost doubled the size of its community, from 8.3M to 16.5M. For perspective, the global developer population grew about half as fast over the same period. Within the last year alone, Java has added 6.3M developers, the largest absolute growth of any language community. Our data suggest that Java’s growth is supported not only by the usual suspects, i.e. backend and mobile development but also by its rising adoption in AR/VR projects, likely due to Android’s popularity as an AV/VR platform.
The group of major, well-established programming languages is completed with C/C++ (12.3M), C# (10.6M), and PHP (8.9M). PHP has seen the slowest growth rate of all languages over the last year, growing just 22%, adding 1.6M net new developers. PHP is a common choice for cloud and web developers but has seen decreasing popularity, particularly amongst web developers where it has gone from the second most popular language in Q3 2021 behind JavaScript, to the fourth most popular in Q3 2022, with Python and Java becoming more popular choices.
C and C++ are core languages in embedded and IoT projects, for both on-device and application-level coding, but also in mobile and desktop development, which are sectors that attract 17.7M and 15.6M developers respectively. C#, on the other hand, has maintained its popularity among multiple different areas of software development, particularly among desktop and game developers. C/C++ added 4.3M net new developers in the last year and C# added 2.8M over the same period.
Rust and Kotlin continue their rise in popularity
We have previously identified Rust and Kotlin as two of the fastest-growing language communities and this continues to be the case. Rust has more than tripled in size in the past two years, from just 0.8M developers in Q3 2020 to 2.8M in Q3 2022. Rust has added 0.7M developers in the last six months alone and is close to overtaking Objective C to become the 11th largest language community. Rust has formed a strong community of developers who care about performance, memory safety, and security. As a result, it has seen increased adoption in IoT software projects, but also in desktop and game development, where Rust is desired for its ability to build fast and scalable projects.
Kotlin has also seen a large growth in the last two years, more than doubling in size from 2.3M in Q3 2020 to 6.1M in Q3 2022. As such, it went from the ninth to the seventh largest language community during this time, overtaking Swift and those using visual development tools. This growth can largely be attributed to Google’s decision in 2019 to make Kotlin its preferred language for Android development it is currently used by a fifth of mobile developers and is the second most popular language for mobile development. Despite Google’s preference for Kotlin, the inertia of Java means that, after three years, it is still the most popular language for mobile development.
Swift currently counts 4.2M developers and is the default language for development across all Apple platforms. This has led to a phase-out of Objective C (3M) from the Apple app ecosystem. However, Objective C has maintained its place among IoT developers and increasing adoption for on-device code, and AR/VR developers, leading to a similar increase in the number of Swift and Objective C developers in the last two years; 1.8M and 1.6M respectively.
The more niche languages – Go, Ruby, Dart, and Lua – are still much smaller, with less than 4M active developers each. Go and Ruby are important languages in backend development, but Go is the third fastest-growing language community and has added more than twice as many developers as Ruby in the last two years; 2.3M and 1.0M new developers, respectively. This is likely due to the fast development cycle it offers even though it is a compiled language.
Dart has seen steady growth in the last two years, predominantly due to the increasing adoption of the Flutter framework in mobile development, with 13% of mobile developers currently using Google’s language. Finally, Lua is among the fastest-growing language communities, mainly drawing in IoT, game, and AR/VR developers looking for a scripting alternative to low-level programming languages such as C and C++.
There is no longer a stage in the creation of artificial intelligence when the technology is in the experimental phase with minimal proof of concept. Organisations all over the globe are struggling with how to incorporate it into their culture and locate the appropriate individuals to lead artificial intelligence and machine learning initiatives because they are aware that it is a force that must be reckoned with.
According to research, sixty percent of Indian businesses are under the impression that Artificial Intelligence (AI) would have a disruptive effect on their industry over the next two to three years. According to a survey, the number of available positions in the fields of analytics and data science has increased by thirty percent between April 2021 and April 2022.
The rapid advancement of artificial intelligence and automated systems is opening up prospects for companies, the economy, and society.
Automation and artificial intelligence have been around for some time, but current technological advancements are expanding the capabilities of machines to perform more and more. According to the findings of our study, society needs these advancements to create value for companies, contribute to economic development, and make progress on some of the most challenging social issues that we face.
The rise of AI and new jobs
Although the technologies of the Fourth Industrial Revolution, powered by AI, will continue to dramatically transform the world and the way we work and live, it is possible that AI may not result in a significant rise in employment. Instead, artificial intelligence will result in the creation of more employment than it eliminates via automation.
These newly generated positions will call for new skills, which in turn will entail considerable investments in upskilling and reskilling programs for both young people and adults. However, private companies and public administrations may – and are obligated to – collaborate to confront this transition and welcome the beneficial effects of AI on society.
According to the Global Artificial Intelligence Study conducted by the year 2030, AI would cause a software projected rise of $15.7 trillion, or 26 percent, in the total GDP of the world. The expansion of GDP will be driven by consumer spending to the tune of around sixty percent, with increased productivity accounting for approximately forty percent of the overall expansion.
Reskilling and Upskilling
For corporations and authorities to reap the advantages of AI in terms of productivity and profitability, they will need to work together on huge reskilling and upskilling initiatives. These projects will assist workers in retraining and preparing for new and upcoming employment opportunities.
Artificial intelligence can automate 3 percent of employment opportunities over the next few years. Increased digitalization brought about by COVID-19 may speed up this process. As artificial intelligence develops and becomes increasingly self-sufficient, thirty percent of all employment and forty-four percent of people with low levels of education will be in danger of being automated by the middle of the twenty-third century.
According to the World Economic Forum, during the next five years, almost half of all employees will need some kind of further training or retraining to be adequately prepared for changing and new employment opportunities. The fast speed of technological progress necessitates the development of new models for employee training to adequately prepare workers for a future dominated by AI.
The development of workers’ soft skills, which can’t be replicated by artificial intelligence, should be a priority for businesses. It seems probable that the importance of creative thinking, leadership and emotional intelligence will only continue to rise in our ever-changing world.
Since 2018, AI and IoT have managed to land in the top 3 on the list of Emerging Technology Top 10, and with valid reasons that showcase the strength of AI and IoT, alternatives are abundant SUCH helping businesses generate productivity improvements, end up saving time, and raise profits. In other words, AI and IoT are helping businesses create a better future.
Businesses seek managers who can embrace the power of artificial intelligence to make successful business choices that may reform ineffective business models and establish new ones that can have an oversized benefit as the competency of AI continues to rise. With proper training and appropriate programs applicants can make their career in AI may explore the concept of combining value creation and value appropriation in corporate CRM Development Company and changing current organizational procedures and offers.
Author Bio – Ethan Millar is a technical writer at Aegis Softtech especially for computer programming like Asp.net, Java, Big Data, Hadoop, dynamics AX, and CRM for more than 8 years. Also, have basic knowledge of Computer Programming.
The Developer Nation surveys are designed in a way that giving back to the community becomes an integral part of them. For each survey wave we run we donate 0.10$ to the favourite charities of our Developer Nation Community. The goal is to reach at least $2000 in donations.
During our 23rd Developer Nation global survey, we collected a total of 26,183 qualified responses, that means we were able to meet and surpass our goal by donating $2,618- and support the causes that you care about.
Though most of these organisations and NGOs are developer centric, helping people learn software development and grow in their career, we welcome more diversity in theorgs we are supporting . You can use the comments section below and add your suggestions.i
For the 23rd Developer Nation global survey, here is the list of organisations we donated to:
The mission of freeCodeCamp is to help people learn code for free. I’m personally a huge fan of the work they are doing and have myself learned quite a bit from there. A total of 7979 survey participants picked them for support so we were able to donate $798 to freeCodeCamp.
The Free Software Foundation (FSF) is a nonprofit with a worldwide mission to promote computer user freedom. A total of 5622 participants picked FSF, hence we were able to donate $562 to support their cause.
Women Who Code (WWCode) is an international nonprofit dedicated to inspiring women to excel in technology careers. We donated $528 to help support the cause of this wonderful inclusive organisation. They have many local chapters around the world, so if you’re a woman who is trying to learn to code or find some mentorship, the Women Who Code community and local chapter is definitely a place to look for.
A non-profit organisation on a mission to develop and scaling technologies to rid the oceans of plastic. A much needed cause to support in order to sustain the ecological balance or marine ecosystems. Our developer community has enabled us to donate $470 to them.
Ada developer academy offers an immersive and intentional coding school prioritising community over competition. It’s very welcoming and inclusive and we were able to donate $261 for their cause.
It really feels great to give back to the community in a way that can help them further their noble cause and create a more sustainable ecosystem for everyone to live and thrive in.
We’re truly grateful to our community members who have enabled us to do this and without your survey participation it won’t be possible so we extend our thank you and promise to continue to do this in future.
The blockchain ecosystem has seen unprecedented growth with many companies now looking to hire Web3 developers with experience in cryptocurrency.
The web is undergoing dramatic changes. Of the latest changes is Web3, a new version of the internet, which is quickly expanding in size and popularity.
As it’s still a new idea, finding Web3 engineers is a tedious task. It’s mostly cryptocurrency and blockchain enthusiast developers who are mastering this new form of the web, which is destined to change the internet in ways we have yet to understand.
Before we talk about how to hire Web3 developers, let’s talk about Web3 itself.
What is Web3?
Web3, unlike its predecessors, Web 1.0 and Web 2.0, is based on peer-to-peer (P2P) decentralized networks, such as blockchain.
Blockchain is a hallmark building block of cryptocurrency, and Web3 is a product of both. Web3 developers create apps that aren’t limited to a single cloud server but are instead distributed on a blockchain or decentralized P2P network that isn’t controlled by a central authority.
In simpler words, Web3 is similar to how most cryptocurrencies work based on the blueprint of Bitcoin.
How does this differ from the existing Web 2.0? While Web 2.0 is user-centric (most of the content is user-generated), Web3 has taken this approach to the next level by introducing more autonomy and keeping things more transparent and relatable. In Web3, computers are heavily involved in interpreting information on a human level.
Web3 has many additional attributes that distinguish it from Web 2.0 — it’s verifiable, self-governing, permissionless, distributed, stateless, and has built-in payment systems (cryptocurrency).
This lack of transparency and verification led to Web 2.0 containing too much content and information, most of which isn’t helpful for general users. Its security is also sub-par, which is why there are too many hackers today and a marked increase in identity theft and other cybercrimes.
Any application built on Web3 would be developed and owned by the users as they help create and maintain the app, earning their stake along the way. This is just how Bitcoin operates, as miners of the currency earn Bitcoins when they facilitate transactions through computing operations.
The apps on Web3 are called “dApps,” which is short for “decentralized applications.” You can expect to hear this term more often in the near future.
An effective Web3 developer is one who is familiar with the concept of Web3, is proficient in the relevant programming languages, and has the right tech stack to back their development work.
What Tech Stack Do Web3 Developers Use: Skills and Tools
The tech stack, or developer stack, refers to the technology or tools the developer uses and excels at. A good example is the MEAN stack, which is comprised of MongoDB, Express.js, AngularJS/Angular, and Node.js.
For Web3, there’s a specific tech stack that the developer you’re hiring must use.
Web3 SDKs/dApps
The Web3 SDKs, or libraries, are essential for building any dApp. These libraries support the interaction with a blockchain, such as Ethereum, and conduct transactions.
The most important of these SDKs are web3.js, web3.py, and ethers.js. These are also linked with smart contracts, which are explained further below.
Cryptocurrency Wallets
If you’ve ever dabbled with cryptocurrency, you probably already know what a crypto wallet is. It holds your cryptocurrency and can be either a digital or hardware wallet. For Web3 applications, a wallet is required to facilitate transactions.
There’s a fee for the writing operations on the blockchain, which must be drawn from the wallet. For Web3, the developer can create an ETH (ethers) wallet using any of the common languages, such as Python, JavaScript, or Ruby. Alternatively, developers can use an existing wallet platform like MetaMask.
Nodes
Nodes make up the blockchain and retain a copy of it. These are also called Web3 providers for this reason, as the application’s connectivity with the blockchain hinges on these nodes. Without these nodes, dApp cannot communicate with the smart contracts.
The most commonly used provider is QuickNode, which provides a global network of nodes powered by speedy operations.
Smart Contracts
In the crypto world, smart contracts are pieces of code that live on the blockchain. Written in Solidity, these cannot be altered or mutated. This code runs when the conditions for it to run are met.
This automates the workflow when the participants of the blockchain confirm an outcome. These smart contracts (pioneered by Ethereum) also helped give Ethereum the edge over Bitcoin in terms of transaction speed.
Web3 Developer Salaries
The average yearly salaries for Web3 developers can vary greatly depending on what you’re hiring them for. Here’s an overview of the most popular Web3 expert roles and their salaries.
Blockchain Developer
According to ZipRecruiter, the average yearly salary for a blockchain developer is $154,550 or $74 per hour. Note that this average is mostly drawn from larger companies. If you add smaller companies and startups into the mix, the average yearly salary drops to $80,000 per year.
Since the term “blockchain developer” is a broad descriptor, the associated salaries tend to vary. In general, there are two types of blockchain developers: blockchain software developers and core blockchain developers.
Blockchain software developers: Blockchain software developers are responsible for creating applications based on blockchain protocol and architecture. One of their main duties is to create smart contracts, which are programs stored on a blockchain that automatically run when conditions are met. Small contracts are usually used to automate workflows and agreement execution so every participant will immediately know the outcome.
They also create decentralized applications (dApps) that run on the blockchain, making them comparable with web developers, who use web architects’ design and protocol to create web applications. Additionally, these software developers are responsible for the front-end and back-end development of dApps and supervising the stack that runs them.
Core blockchain developers: These blockchain developers are responsible for creating the architecture, design, and security of the blockchain system. They also:
Design the blockchain protocols
Design security patterns and consensus protocols for the network
Supervise the entire blockchain network
Despite their differences, both types of blockchain developers require a similar skill set. Here are the main blockchain developer hard skills you should look for when hiring a blockchain developer for your team:
Cryptography: Cryptography is the study of blockchain protocols that prevent unauthorised and unwanted parties from accessing your data. A popular concept in cryptography is public-key cryptography, which forms the backbone of cryptocurrency transactions. Another hot topic is cryptographic hashing, which transforms cleartext passwords into enciphered text for storage. This slows down threat actors since they’ll have to decipher these hash values if they want to exploit the passwords.
Data structures: Every blockchain developer needs to have extensive knowledge of data structures. This is because blockchain networks consist of data structures.
Blockchain architecture: Blockchain developers need to know what ledgers are, how smart contracts work, and what consensus is. They should also be familiar with all four types of blockchain architecture: consortium, private, public, and hybrid.
Web development: Blockchain developers should also know how to develop and create web apps, particularly if they’re blockchain software developers.
A variety of programming languages: Finally, your blockchain developer should have experience with at three or more of the following programming languages:
Like the rest of the roles on this list, blockchain developers need the following soft skills:
Commitment to and passion for the Web3 landscape
Interest in learning more about blockchain technologies
Client and project management skills
The ability to meet deadlines ahead of time
The ability to work in multi-disciplinary teams
Solidity Developer
The average base salary for a Solidity developer is $127,500 per year. Remote Solidity developers can earn up to an average of $145,000 per year, depending on which company they’re working for.
Solidity developers use the Solidity language to create and deploy smart contracts on Ethereum-based apps. The syntax of Solidity is similar to C and Javascript, so developers who already know those languages can quickly learn Solidity. Compared to other languages, Solidity offers multiple benefits, such as:
Statically typed programming
Accessibility to JavaScript debuggers, infrastructures, and other tools
Preciseness
With Solidity, developers can craft applications with self-enforcing business logic in smart contracts, creating a non-repeatable record of transactions. Solidity also supports libraries, a complex user-defined type, and inheritance. Thus, it’s a good choice for creating contracts for crowdfunding, voting, multi-signature wallets, and blind auctions.
Solidity developers are usually responsible for:
Integrating Solidity code across various platforms
Managing the full lifecycle of blockchain development
Ensuring blockchain integration with existing applications
Building smart contracts and ensuring that all timelines and expectations are met for finished smart contracts
Reviewing smart contracts for security and functionality
Supervising web services that use blockchain technology
Collaborating with multidisciplinary teams and product managers to discover new ideas for smart contract development
Assessing technical reviews of proposed solutions
Analyzing usage and transaction statistics to pinpoint and prioritize areas for improvement
Besides having a deep knowledge of Solidity and blockchains, Solidity developers should also have the following hard skills:
Blockchain technology, especially Ethereum blockchain
Strong background in Javascript, C, C++
Knowledge of AngularJS, React JS, and Ember JS
Portfolio experience with Ethereum testnet and mainnet
CSS/HTML/JS/React for application binary interface (ABI) integration
Experience with RESTful APIs
Experience with staking protocol implementation for liquidity pair and single-token staking
Familiar with different ways to deploy smart contracts, such as Remix, Truffle suite, and Hardhat
Experienced in staking implementing and test-driven development (TDD)
Knowledge of libraries, data structures, blockchain architecture, web development, and smart contracts
Smart Contract Developer
According to Glassdoor, the average annual salary of a smart contract developer in San Francisco, CA, is $94,674 with an average additional cash compensation of $20,950.
As their name suggests, smart contract developers are responsible for developing smart contracts for blockchain platforms. They use various programming languages, such as Solidity and Vyper, to create smart contracts, which, as we covered above, are blockchain programs that automatically run when conditions are met.
Unlike blockchain software developers who create dApps as well as smart contracts, smart contract developers are only responsible for designing and building smart contracts architecture and related tasks. As such, they have fewer responsibilities and lower salaries.
Here’s what they’re typically responsible for:
Designing, building, and deploying smart contracts architecture, yield pools, incentive structures, and strategies
Working with smart contract auditors and the rest of your IT team to implement fixes
Create, implement, and test smart contract additions and upgrades
Explore and research smart contract design implications
Most companies require smart contract developers to have the following hard skills:
Over four years of full-stack web development (client-facing apps and APIs)
Programming languages such as Solidity, NodeJS, and JavaScript
Cryptography
Experience in creating, developing, deploying, and testing smart contracts for all four blockchain architectural types
Experience with patterns that will make their Solidity code more readable and improve performance, such as:
Oracles
Pull over Push
Eternal Storage
Tight Variable Packing
Guard Check
Emergency Stop
The ability to write secure code that prevents threat actors from taking over contracts
Optimization of smart contracts
User experience (UX)
Rust Developer
There’s a lot of variation in the salaries of Rust developers.
According to ZipRecruiter, the average Rust developer earns $91,709 per year or $44 per hour. However, in certain major cities, the average salary of Rust developers is higher. For instance, the annual average salary of a rust developer in San Francisco, CA, is $106,131 with an average additional cash compensation of $11,867.
Rust developers are responsible for coding and developing web browsers, blockchain platforms and projects, servers and systems software, and operating systems in the Rust programming language. They may also be responsible for testing, debugging, and ensuring the security and safety of the systems, software, and platforms they develop.
Additional duties may include:
Collaborating with customers, management, and relevant departments to pinpoint end-user specifications and requirements
Analyzing user feedback to boost software performance
Creating technical documentation
Like Solidity, Rust is a popular language that has a wide range of Web3 applications. It’s particularly popular due to its use in the Solana blockchain, a potential competitor to Ethereum as the leading platform for dApps. As of March 2022, Solana is currently ranked ninth in market value on CoinMarketCap, making it the highest-ranked blockchain platform that uses Rust.
Most companies require Rust developers to have the following skills:
C++, since the Rust language is similar to it
Other programming languages such as Golang, Python, Java, Node.js, and React.js
Knowledge and experience with secure coding practices
Experience with network programming skills and multi-threaded programming
Familiarity with solana-web3.js, Solana’s official SDK (Rust developers use this SDK to develop Solana dApps)
The ability to create and launch Programs, which are the Solana equivalent of smart contracts
Experience with specific operating systems such as Android or Linux
Experience with certain databases, such as MongoDB and Apache CouchDB
Many organisations also prefer to hire Rust programmers who have at least three to five years of Rust coding experience since it’s a difficult language to master.
According to the Rust Survey of 2019, most Rust programmers rated their expertise as 7 out of 10 or below, even though over 68% of them wrote Rust code weekly. Additionally, 22% of Rust users indicated that they didn’t feel productive while coding Rust and the steep learning curve was the second most common reason for not using Rust on some projects.
As such, it’s important to get a good idea of how familiar and comfortable your potential hire is at Rust. Give them a few test assignments and make sure that they know how to create, test, and debug the programs and apps you want them to create.
Where to Find Web3 Developers
Whether you’re looking to hire Web3 developers for a long-term project or a small gig, knowing where you can find the best talent for this specific set of skills can substantially cut down your search time.
Web3, like cryptocurrency in its early days, is driving impressive innovation. It’s an excellent opportunity to be a part of the blockchain ecosystem and help formulate the future of the web.
Unless you live in a tech hub where you can find talent locally, it’s probably easiest to hire remote developers. Here are the best places to find these developers and Web3 engineers:
Crypto Job Boards
Even while talking about something as cutting edge as Web3, you may find the age-old approach of searching job boards to be quite convenient. However, you’ll want to choose a job board that’s known for harboring blockchain and crypto developers.
There are several recruitment websites that focus solely on crypto-related jobs. You can increase your chances of finding the right person by posting the position on more than one of these platforms.
LinkedIn is another online job board, but it’s also a social media platform. Many startups begin their talent scouting here.
Not only do you have the opportunity to post Web3 development jobs on LinkedIn, but you can also search for professionals with experience by viewing the profiles of prospective employees. Profiles present workers’ skills, experience, and education, and if you like someone, you can communicate with them directly on the website or app.
While LinkedIn is an excellent place to find a developer, it also provides a great platform for promoting your business, especially if you’re looking for financing. It offers opportunities to show off the talent you hire as well, to make your venture appear even more valuable.
Talent Marketplaces
Online talent marketplaces are another viable option when searching for Web3 developers. These usually have both remote workers and freelancers, so you’ll first need to figure out exactly the kind of worker you need.
Do you want a permanent member of the team? Do you want a contractual freelancer? These are serious considerations. For example, for long-haul collaboration, you’d likely want the developer to be an employee of the company.
There’s nothing wrong with going with a freelance developer, provided this kind of relationship meets your needs and you can find someone suitable. But if you’re looking to embed developers in your team and hire them permanently, Revelo is an excellent place to start. You’ll be connected with top-notch remote talent specializing in Web3 engineering or development, or whatever technology you need to grow your business.
One of the most significant benefits of using Revelo is that the developers are pre-screened, so the skills and experience they list on their profile are what you’ll get. Therefore, there’s no need to confirm their experience — you can just move along with the interviewing process.
How to Hire Web3 Developers
You probably don’t want to spend endless hours reviewing resume after resume and conducting dozens of interviews. At the same time, you also don’t want to miss out on good talent by overlooking their applications.
To help you pick out the best from the rest, here are some examples of job postings and some guidelines for the interviews themselves.
If you find hiring daunting, don’t worry — hiring developers doesn’t require the formal interviews, group discussions, or IQ tests that many big corporations use. If you’re all for decentralization anyway, you might as well do things a little differently than more centralized corporations.
Web3 Developer Job Post Example
The first thing you need to nail is the job post itself. Whether you choose to go with a job board, LinkedIn, or a talent marketplace, you’ll need to define the position you’re offering.
This is important because, believe it or not, many recruiters and contractors end up using the wrong terms in their posts or adding too much detail. This can cause candidates to overlook the most important requirements of the position. In these cases, you’ll end up with irrelevant resumes and often too many of them to sift through.
When you’re looking to hire Web3 developers, the post should be direct. It should address that you’re looking for a blockchain developer who specialises in Web3 development and has the right tech stack to support it.
Ideally, you would want people with experience working with blockchain to apply. So, make a list of the relevant keywords to put in your post. Those keywords will also help the post rank better on search engines, so anyone who types those keywords will see your job posting.
To help you write an immaculate job post to hire Web3 programmer, here is an example:
“We are looking for a passionate and experienced Web3 developer to help us build our project XYZ.
Our ideal candidate is someone with experience developing blockchain-based applications, especially those for Web3 (dApps). They should be aware of and use the latest technologies in crypto, blockchain, and Web3 development. With collaborative energy and willingness to learn, the right candidate will readily communicate with and assist other team members on the project.
Necessary Qualifications:
Experience with blockchain development
Experience with Solidity and dApp development
Basic knowledge of front-end development of dApps to bridge the gap between the complex blockchain and usable Web 2.0–based interface
Ability to work remotely and collaborate with the team when necessary
Responsibilities
Help create scalable applications with Ethereum blockchain
Analyse and solve problems in the development phase
Communicate and collaborate with back-end and front-end teams
Develop and optimise smart contracts
Help document the development process of the blockchain and dApps
Optimise development and implementation
Adopt best practices for Web3 and blockchain development”
You can follow this layout or create your own based on this sample structure:
Begin by briefly introducing your company or the idea of the project without giving too much away, especially if you’ve come up with a new idea.
Then, talk about what the ideal candidate should have, including the desired skills and qualifications. Don’t be too general with these but try to be straightforward. Keep in mind that Web3 is relatively new, so asking for 5 or 10 years of specific experience may be unreasonable and limit who applies. This could cause you to miss out on exceptionally qualified candidates.
Consider adding a pay rate or range in the job posting. This transparency will ensure that neither you nor the candidates waste time with interviews or application materials if your expectations are drastically different.
Lastly, list the responsibilities that the developer will have. Include both technical and non-technical responsibilities that you’ll expect of a new hire.
Remember that a clearer job description will attract more relevant applicants.
Web3 Developer Interviews
Once you have shortlisted the candidates, you can begin setting up interviews. You already established during your initial review that they meet the requirements you defined in the job post. Now, it’s time to get to know them a bit better.
You’ll most likely be conducting the interview remotely via a web meeting tool, like Zoom.
It’s always a good idea to formulate your interview questions beforehand. You should write down your most significant concerns with hiring Web3 engineers and keep each candidate’s resume handy either in paper format or on your computer screen.
Ask them how they plan on working remotely, especially if they are located in a different region with a significant time zone difference. Discuss the communication tools and methods of your team and whether they have any experience with those.
Make sure to formulate these discussions and concerns into a set of questions and create a smooth flow. For example, consider dividing the interview into technical and non-technical sections. However, it’s not necessary to stick to your script. If you think of something during the interview, you can go ahead and ask and come back to your pre-written questions after.
Lastly, discuss their salary or pay expectations. Do they prefer to be paid hourly, annually, or by the project?
Here are some sample questions you can use in your interviews:
How do you think Web3 is different from the previous versions of the web?
What blockchain projects have you been part of? What was your role?
What Web3 development tools and technology have you used before?
What coding languages are you experienced in?
How do you respond to feedback from other team members?
What testing methods do you use for your code?
What is your preferred mode of communication?
Don’t forget to keep the mood light and friendly!
Web3 Coding Challenges
No matter how well the interview went and how experienced the candidate claims to be, it all comes down to their skill.
To measure and confirm their level of knowledge and experience in Web3 development, you should conduct several small coding challenges. These can be presented to the candidates in written form or as video presentations to explain the purpose of the assignment. The task shouldn’t be longer than an hour unless you plan to pay them for their time.
If you’re hiring a developer to carry out different coding tasks, you should create different coding challenges, each dealing with a specific need of your project — for example, creating nodes, writing smart contracts, or developing the front end of a Web3 application.
Another popular approach to coding challenges is pair programming. In these tests, two developers work together on a problem, either in person or remotely. This is a great way to test their technical skills and their team and communication skills. The code wouldn’t be written by both of the developers, however. One would formulate the code or define the approach, while the other would actually write it. You can reverse the roles for a second test.
Here are some tips for developing coding challenges:
Utilise problems related to your project. You want to see the developers working in the context of your application. You should take a problem related to your project and present it as a challenge to see how the candidate might benefit your team.
Focus on the process, not the result. When examining the coding challenge results, don’t just look at whether they solved the problem. Even if they didn’t quite find the solution, their results can help you get to know how they work and whether they have the potential to learn more.
Use the same challenge. For a single job posting, use the same coding challenge to see how different candidates compare. However, don’t reuse the test once you’ve hired someone successfully.
Create from scratch. It’s best to create the challenge yourself, using a real problem related to your project. Pre-designed coding tests may not provide the best outcome, and many times the solutions have been published online, which defeats the purpose of testing. If you’re not a developer yourself, consider asking your current developers, especially those responsible for testing, to create these tests for you.
Conclusion
Hiring Web3 developers is not difficult if you search in the right places, conduct the interviews effectively, and design a solid coding test. Even if you believe a candidate is not seasoned, you can always train them. However, they should have the drive to learn more.
Revelo can solve your talent hunting issues by presenting some of the best developers from Latin America to become an integral part of your team and take your Web3 project to the next level. Contact Revelo and get matched with vetted developers within 3 days.
Personality theories provide a blueprint for understanding why people behave the way they do. In the latest edition of our State of the Developer Nation 22nd Edition – Q1 2022, we incorporated a measure of the widely accepted ‘Big Five’ personality dimensions. We did this in order to better understand the personality traits of software developers. Here, we share some of our findings on developer personalities. Our aim is to discuss how this kind of information can help to support interactions with developers.
Personality measures are a powerful tool for understanding people’s preferences and behaviours. Software teams need diversity not only in terms of skills, experience, and knowledge, but also require a variety of personalities. This will help teams collaborate effectively on complex and challenging projects.
The Ten-Item Personality Inventory
We used the Ten-Item Personality Inventory (TIPI) methodology in order to measure the ‘Big Five’ personality dimensions. These dimensions are: emotional stability, extraversion, openness to experiences, agreeableness, and conscientiousness. The TIPI method is well-suited for situations where short measures are required. The results have been shown to have good alignment with other widely used Big Five measures1. Although more comprehensive and accurate personality measures than TIPI exist, they typically require an entire survey to themselves.
The TIPI method presents respondents with ten pairs of personality traits and asks them to rate how strongly these traits apply to them. Below, we show responses to these items for over 12,000 developers. We find that developers, in general, see themselves as complex and open to new experiences (86% agree or strongly agree that this applies to them), dependable and self-disciplined (79%), calm and emotionally stable (76%), and sympathetic and warm (74%).
Diving deeper into the TIPI data allows us to identify more specific personality types within the general developer population. We collapsed these ten items into five distinct measures, one for each of the Big Five personality dimensions. For example, statements about being ‘sympathetic, warm’ and ‘critical, quarrelsome’ combine to give an overall measure of agreeableness. We then derived a score for each developer on each of the five dimensions. This helped us identify the developer personalities at the polar ends of each dimension, e.g. labelling those who are at the top end of the agreeableness scale as ‘agreeable’ and those at the bottom end as ‘disagreeable’.
Finally, we segmented all developers into a set of distinct personality types. We did this by using the personality labels that they had been assigned as inputs to our segmentation algorithms.
Approximately 8% of all developers differ from the aforementioned group. They showcase a higher level of openness to experiences – often related to intellectual curiosity. These software developers have personality traits that suggest they are likely to investigate new tools and technologies. They are also more likely to stay up to date with the cutting edge of technology.
The Five Developer Personalities
The following charts show the characteristics of five example developer personalities revealed within our data. A well-rounded, ‘balanced’ personality type accounts for 52% of the developer population. These are developers who sit firmly at the centre of each dimension. They are neither introverted nor extroverted, highly agreeable nor disagreeable, emotionally unstable nor lacking emotion, etc.
5% of developers fit a ‘responsible and cooperative’ personality type. These developers score highly in conscientiousness, openness to experiences, and agreeableness in comparison to the majority of developers. Increased conscientiousness often relates to setting long-term goals and planning routes to achieve them, e.g being career-driven. Higher scores for openness to experiences reflects a preference for creativity and flexibility rather than repetition and routine. Our data backs this up. These developers are more receptive to personal development-related vendor resources. For example, 35% engage with seminars, training courses, and workshops compared to 25% of ‘balanced’ developers. Their high scores for agreeableness also correlate with greater engagement with community offerings. For example 23% attend meetup events compared with 17% of ‘balanced’ developers.
5% of developers conform to an ‘achievement-driven and emotionally stable’ profile. As with the previous personality type, they are conscientious and open to experiences. However, they score much higher in terms of emotional stability but slightly lower in terms of agreeableness. Developers who score high in emotional stability react less emotionally. For example they favour data over opinions. Lower agreeableness can be a useful trait for making objective decisions, free from the obligation of pleasing others.
We also find a segment of developers with an ‘introverted and unreliable’ profile. They indicate that they are less involved in social activities, disorganised, closed to new experiences, and less agreeable than other developers. Fortunately, these developers, who are likely hard to reach and engage in new activities and communities, are a very small minority, at 2% of all developers.
Developer Personalities, Roles and Content Preferences
Finally, we show how the characteristics of these developer personalities vary, in terms of both associations with developer roles and the kinds of information and content that they consume. Developers in the ‘balanced’ profile are most likely to have ‘programmer/ developer’ job titles. However, those who fit the ‘responsible and cooperative’ profile are disproportionately more likely to occupy creative (e.g UX designer) roles. This aligns with their increased creativity/openness, and senior CIO/CTO/IT manager positions, reflecting their self-discipline and achievement striving.
Those who are ‘achievement-driven and emotionally stable’ are less likely than other personality types to have ‘programmer/developer’ job titles, but disproportionately more likely to be data scientists, machine learning (ML) developers, or data engineers. They tend to deal mainly in facts and data rather than opinions and emotions. Those in the ‘introverted and unreliable’ profile are more likely to have test/QA engineer and system administrator job titles than those in other personality types.
When it comes to where developers go to find information and stay up to date, perhaps unsurprisingly, the ‘introverted and unreliable’ personality type uses the fewest information sources overall, affirming that they are a difficult group to engage via community-focussed events and groups. However, their use of social media is in line with other personality types, suggesting that this may be a suitable channel for catching the attention of this hard-to-reach group.
Both of the high-conscientiousness and high-openness personality types use the widest range of information sources overall, however, those who are more cooperative are considerably more likely to turn to social media for information about software development (53% of the ‘responsible and cooperative’ type vs. 44% of the ‘achievement-driven and emotionally stable’ type).
‘Intellectually curious’ developers are the most likely to make use of official vendor resources and open source communities. Hence, the audience that vendors reach via these resources may be slightly more keen to experience new products and offerings, than the typical ‘balanced’ developer.
What’s Next with Developer Personalities
We just began to scratch the surface of developers’ personality profiles. The personality types we have shown are indicative of just a few of the differences that exist among developers. By capturing this kind of data, we’ve opened the door for more extensive profiling and persona building, along with a deeper analysis of how the many other developer behaviours and preferences that we track align with personality traits. If you’re interested in learning more about developer personalities and how this can help you to reach out to developers, then we’re very excited to see how our data can support you.
Apple’s WorldWide Developers Conference (WWDC) for 2022 kicked off with the Keynote (1 hour and 48 minutes) where I sat and enjoyed the presentation and did not take any notes. The Platforms State of the Union sessions (1 hour 10 minutes) was next, after an hour for lunch on the West Coast. This also is a session I watch and do not take notes. They also had the Apple Design Awards (18 minutes) and a Day 1 recap (3 minutes).
During the week, I looked over the list of sessions available each day and jotted down the ones that I was most interested in, listed by the days the videos would be available. I figured I would start with those and potentially watch others based on what I learned from the first set and how much energy I had left from the day.
Tuesday – The Swift Cookbook of Navigation
On June 7, I was ambitiously planning on watching the following sessions, once they because available that day:
Build Your First App in Swift Playgrounds
Dive into App Intents
Get to Know Developer Mode
Implement App Shortcuts with App Intents
The SwiftUI Cookbook for Navigation
What’s New in SwiftUI
I opened a Word document and copied the transcript of each session and any code that was attached and pasted it into the document. I figured it might come in handy to look for terms, ideas, or code snippets someday.
The first session, Build Your First App in Swift Playgrounds, was interesting, and I do not have a lot of hand-written notes about it, as it did not directly apply to my goal, to learn how to use SwiftUI to update my way-out-of-date-app.
The second one, Dive into App Intents sounded promising and yet…it was about how to make it easier for a user to RUN your app, not how to describe what I intended it to do for me. I took lots of notes from Implement App Shortcuts with App Intents because I was determined to make them work for me somehow.
Now, the SwiftUI Cookbook for Navigation was exactly what I needed. It talked about three-column navigation split view, and showed Recipe Categories, Recipe List, and Recipe Detail. This would work fine for me. I need to implement this! Yippee! I found what I came for!
Now, I just needed to dig deeper and find out how to implement what they were cooking up! It talked about new container types: NavigationStack and NavigationSplitView.
I did not watch the last session I had planned for Monday. I saved that for Tuesday morning, as the new sessions were not available when I get up early (I live on the East Coast of the United States and Apple and their timeline is based on their West Coast location) and I wanted to have something to do so I wasn’t tempted to log into my full-time job and check on some things. This was my “vacation” week after all.
On June 8, I added to the one left-over session with the following choices:
Create Your Privacy Nutrition Label
Design App Shortcuts
Swift UI & Swift Charts
I started with What’s New in Swift UI from Monday’s list. It was a list of sessions that talk about the details of new items in SwiftUI, such as The SwiftUI Cookbook for Navigation, which was the last session I watched the previous day, so I congratulated myself on that choice.
The session also mentioned Swift Charts, and this was not of interest to me because I had no immediate plans to add charts to my app. It then talked about sharing, and since this is broken in my app currently, it peaked my interest until they talked about Mail, Messages, Air Drop, Notes, Add to Photos etc and not Facebook or Twitter, that are not not considered sharing now. The session ended with a peek at layout and how a mixed layout can be achieved with Grid, GridRow and GridColumn.
Create your Privacy Nutrition Label
Next up was Create Your Privacy Nutrition Label. I went into this thinking there was an actual label that would need to be filled out to submit an app to the store. The areas are Data Used to Track You, Data Linked to You, Data Not Linked to You, and Data Not Collected. If the developer selects the last one, the label reads, “This developer does not collect any data from this app” and that applies to my app. So, that was all I really needed from this session.
Thursday – What’s new in Xcode
On June 9, I added just two more to my original list:
What’s New in AppStore Connect
Writing for Interfaces
I still have not watched either of those sessions. I started the day with What’s New in Xcode which gave me a list of other sessions to take a look at when I have time. Some new code was introduced and hints and tricks were shared to make coding faster by using code completion and using simple icons in a single size instead of needing all the sizes for all the different versions of pixel count now available.
The new sessions I added to the watch list are:
Use XCode to Build a Multiplatform App
Meet Swift Package Plans
Create Swift Package Plugins
Building Global Apps: Localization by Example
Localization do or don’t?
I decided to watch the last one on that list first, Building Global Apps: Localization by Example. This sounded promising, and I was interested in how well the translation would work for my app. I thought it was too much AI and not enough about how you will need to hire translators who would take the text you send them and return it in different languages, which you reference in code to use the localized version of the text.
My small little app is not going to be translated. Not for this next version.
Custom Layouts and Swift Playground
Next, I watched the session Compose Custom Layouts with SwiftUI and learned about grids and geometry reader and the layout engine. It was way over my head, and not really relevant to what I was hoping I needed to do. I thought starting in Swift Playgrounds is where I should turn my attention. I watched Create Engaging Content for Swift Playground only to find out that this was not relevant either since it was about how to write an app for learners.It was interesting though!
Friday – Having a Design Lab appointment
I had signed up for a Design Lab appointment so someone from the Apple Design department would take a look at my app currently available and make suggestions on how to improve it and bring it up-to-date. I took lots of notes on what he found when he used the app, and I have a few things to think about when re-designing the app that I hope to incorporate into the final product. Then, as I was looking around for sessions to watch, I noticed that my all-time favorite SwiftUI online instructor, Paul Hudson (@twostraws) had recorded a session at Apple Headquarters in their new developer lab podcast space so I just had to watch it. It was What’s New in SwiftUI for iOS16 and this is the session I took the most notes from and, as usual, after watching his session, I wanted to jump right in and start coding.
Well, WWDC is over for the year. There are still sessions I would like to watch…you know, that magical time we all have called “someday”. It is time to get the app updated and into the app store before the time runs out and Apple pulls it from the App Store. That story was in part 1 and documents now I spent most of my Saturday after WWDC, all psyched up to get going with this new-found knowledge and enthusiasm for a redesigned version of my personality test app (Which 1 Are You).
Sunday
After spending way too much time on Saturday downloading the Beta version of Xcode, making sure the app works, and then finding out I can’t submit to the App Store from Beta, and all the other pitfalls I tripped over, I was not too enthusiastic about redesigning the app. So, I reread some of my notes, and remembered that I had had a dream over night about how exactly I could do this.
I started a new project in XCode, called TestingCode. To use as a proof of concept It has three structs, some state variables, and the body consists of a NavigationSplitView from the Cookbook session and Paul’s podcast. I thought I had understood it, and yet I cannot get it to work. And it’s back to my full-time job, too!
Coming up next : Debugging, NagivationSplitView and more
And that is where this blog ends, for now. Tune in for part 3, where I debug the issue, and learn more about this intriguing NavigationSplitView and how it actually should work. This is where the transcripts and code samples from the sessions I copied should come in handy to see what the pieces of the NavigationSplitView actually should be and how they work together.
It is with great excitement that we are now kicking off our new section of stories coming right from our Developer Nation community members.
Our first piece comes from Deborah Graham who recently attended Apple’s WWDC and decided to put her learnings from that experience into immediate action.
This is the first part of Deborah’s story, recorded in her own vivid style.
Taking 250 pages of notes at Apple’s WWDC
Well, another WWDC (Apple’s WorldWide Developers Conference) has come and gone (week of June 6-10, 2022). I took a week off my regular, full-time job as a Finance BI Specialist (yeah, doesn’t really explain what I do, let’s say I work with Access, VBA, and SQL a lot and some source systems to get data into reports and SQL tables so others can create Tableau reports for employees to consume) to “attend” the conference and I watched 12 sessions(so far) and a surprise video from my favorite Swift online teacher, Paul Hudson (@twostraws).
I took a lot of notes, and then created a Word document with the transcripts and code segments attached to the sessions. This Word document is over 250 pages already (and I have sessions I haven’t seen yet that will be added to the document). Why did I do that? It’s actually already come in handy…but let’s not get ahead of ourselves.
Rewriting my app to Swift
For starters: Using Xcode and Figma
Over the weekend, after the WorldWide Developers Conference concluded, I started working on getting my current, old app (written in Objective-C and hard to maintain and update) updated to reset the clock so the app would stay available in the App Store. It’s “Which 1 Are You”, if you are inclined to download it and see the “before” version as I work though re-writing it into Swift and using updated standards and design expectations.
I downloaded the latest Beta version of Xcode to make sure the app would actually still run (if not, I had a LOT of work ahead of me to get this app updated before the deadline Apple set before they yanked it off the App Store due to not having updated it since June of 2017…yikes, it IS old!).
I found out that I needed an App Store Icon (1024 by 1024). I wanted to find a free program to create an icon. A quick search found a video which suggested some paid programs and a free one called Figma. I figured that would work for me. I created the simplest icon I could. Luckily, it built and ran without changes.
I figured I needed something different before I could submit to the App Store, so I marked it as working Upside down, too. I ran into a long list of issues during Archive and they were all small items.
Submitting to the App store
Then I ran into issues when submitting to the App Store. I found out that I could not submit an app from a Beta version of Xcode. So, it was back to the other version I had and tried again.
It seems, since I said I don’t collect data on users, the frameworks I used originally for ads, which no longer work, do collect (or might collect) data, so I either needed to revamp my statement or remove the frameworks. So, I removed the frameworks and tested it again. All was good. Back to submitting to the App Store.
Then, I needed screenshots in all sorts of different sizes. Luckily, another search showed me that the Simulator Tool allows for screenshots. I spent an hour running the program in different device simulators to take screenshots and upload them to the App Store Connect page to get all the images I needed.
It was late Sunday night when I finally got the green light that the app was in for review. I went to sleep wondering if the review would find anything else I needed to do. Woke up Monday and checked my email. My updated app was available on the App Store! Version 1.6.3 was a go!
This means, I have some time to work on getting the app into Swift and taking the knowledge and advice I received at WWDC 2022 and re-vamping the app.
This blog will document the progress, insights, inspirations, and setbacks as I encounter them. Hope you enjoy the journey!
About the Author – Deborah Graham
Deborah Graham is a professional developer. She has over 20 years of experience with various programming languages. It all started while attending Community College to get an Associate degree in Electronics technology (hardware). One day, they delivered some Apple IIe computers to the computer room to keep the PDP-11s company. There was a pong-like game written in Interpreted Basic where the source code was available. She quickly figured out that by increasing her paddle to 99% of the goal area and the opponent’s to 1% and turning up the speed of the ball, it was a fun way to a win. One small change, one big difference. And a love of programming was born. When not in class, she could usually be found sitting at that Apple IIe and tweaking the program a little to see the changes. After graduating, she held several hardware-related jobs to match the degrees (two Associates: Electronics Technology and Computer Maintenance Technology, both hardware-based degrees), including Test Technician, Manager of the Test Department, Customer Support (where she created the Customer Support Newsletter that would collect errors in the hardware or documentation and send it out to the local sales and support reps to cut down on support calls to the home office) and then she went to the documentation department to correct all the errors and to create technical documentation with the hardware engineers. She was a Technical Writer for an automated testing machine manufacturer. The documentation software (this was WAY before Word) used LISP (now just Lisp) as the extension tool. The writing team found they needed/wanted to extend the documentation software to do things like index across all documents and spell-check all documents. Luckily, there was a class happening and she flew up to Montreal to attend the week-long class and the love of programming continued! When she got back, all sorts of extensions were created and shared with other users of the software.
One day, during the yearly performance review and plan for next year, her manager said to get a promotion, she would need to get a bachelor’s degree. Didn’t matter in what, it was one of the requirements to move up in the company. So, she called the local state school and asked what degrees they offered. And BSCS (Bachelor of Science, Computer Science) was one of the choices. It was either that, or Nursing or Teaching. Easy choice!
Right before graduating (and being eligible for a promotion), she was laid off! But now, with a degree to go with her love of programming, she was hired by the documentation software provider as a technical writer. After that, she worked for an early browser-based distance learning provider as a technical writer. One Friday, the boss asked her if the online help she was writing in HTML could pop up when links where clicked instead of completing replacing the main help. Granted, that’s a no-brainer now…but this just wasn’t available in HTML at the time. On the way home, she went to the local bookstore, went to the Computer Science section, and checked the index on all the books to find one that would be of help. She bought the book, read it on Saturday and Sunday (yes, she reads programming books for fun!) and on Monday, she got into the office before the boss, coded up come JavaScript and when he walked in, she said, “like this?” and he was amazed. The thrill of writing some code and seeing the result is very motivating. She went on to teach a class called “JavaScript for Technical Writers” at various places. As she was creating the class and with a vacation scheduled, she emailed the author of her JavaScript book asking his permission to use the book and the sample code in her class, promising to give him credit for the code. When she received his okay, that started her habit of bringing a programming book to take on vacation with her to learn a new language. Some people may take a romance novel to read at the beach…she falls in love with a new programming language!
That leads to the list of the programming languages that she was used to professionally write code:
M/MUMPS/Caché ObjectScript
HTML
XML
ASP
Lisp
Pascal
Certified AES
Visual Basic/VBA
JavaScript
Postscript
PCL
Python
SQL
And some that she uses for her hobby
Objective-C
Swift
Which brings us to the hobby. One team she was on had a meeting habit of taking personality tests before the meeting and then declaring which one of something each team member was. Which flower are you? Which Major city? Which cartoon character? Each week, someone on the team would find an online test, and they would all take the test and report the results for the icebreaker at the start of the meeting. One week, she was looking for a test on which character from Scorpion (a television show about geniuses that solved problems for the US government each week and learned a little more about how to function in society with a help of their “normal” assistant and her genius son). Anyway, she could find tests on which genius, but not specifically about that show. When she mentioned this difficulty to the team manager, she was told to write one herself. Apple had just opened the AppStore to developers, so here was another opportunity to learn a new language. It took a few years of reading books, finding online classes on Objective-C, and finally getting an app into the AppStore. The CIO of her company mentioned it at a few All-Hands meetings, and he shared his test results. There are 15 tests available for a variety of TV, movies, cartoons, and general interest. If you are at all inclined, it is called “Which 1 Are You” and it has her name as the developer.
As an Apple Developer, she is invited to attend Apple’s WWDC (World Wide Developers Conference). Before the pandemic, it was almost impossible to get tickets. Since the last few years have been online, it opened the gates and allowed anyone to participate. She has “attended” WWDC for two years in a row now and looks forward to attending them each year. She takes a week off from her full-time job as a SQL and VBA Programmer and soaks in the new information and the enthusiasm from the presenters and other attendees.
She was asked by Developer Nation to document her journey from WWDC 2022 to an updated version of the app, totally re-written in SwiftUI, into the AppStore. Follow along and see what works, what doesn’t work, and let’s see if she can get the app ready for version 2.0! You can email the author at FromInterpretedBasicToSwiftUI@gmail.com.
The 23rd Developer Nation Survey is live and running full speed and we already have our first winners to announce! Those that were lucky enough to win one of our amazing prizes!
What are the Developer Nation Prize draws?
If you’re new to our prize draws: developers who take our surveys earn 100 points for every new survey completed, plus 10 points for providing their feedback about the survey. And in return they become eligible for benefits and rewards – you can see a full list here.
Now, this is a survey that covers many technologies and participants may choose to participate in different ways. Some of them are members of our Community as well – so they are entitled to additional prizes.
This is why we run several prize draws. In this blog we will be adding all prize winners from our prize draws, so keep an eye on it as it will be constantly updated.
Paschal of Nigeria Thomas of Singapore Michael of United States Panji of Singapore Deepam of India Víctor of Mexico Adrian of Malta Christopher of Philippines R of Brazil
Swag
A of UK Brad of USA Charlie of Australia A of Ukraine Geoffrey of Canada Ashley of UK V of USA Thomas of Cyprus Richard of United Kingdom Nicholas of Trinidad & Tobago Dean of Australia Laborde of USA Brian of USA Alexandre of Belgium Jignesh of India Daniel of United Kingdom Mike of United Kingdom
$15 gift card
Jonathan of Australia Brian of Canada Michael of United States James of USA Léo of Sweden Tsvetomir of Bulgaria Ioannis of Greece Mikael of France Akhil of India Matīss of Latvia S of Germany Bledi of Albania Stefan of Germany Rodney of Canada Thassilo of Germany Andrew of United States Vitalii of Ukraine Andrejs of Latvia
What happens now
We’ve reached out to winners directly by email. If you recognise your email address but believe you haven’t been contacted yet, you can contact us here.
We’re already on the hunt for prizes for our next global survey, so if you’re not a winner this time, there are more chances to win in our future surveys.
To ensure that you are notified when our next survey is live, sign up. Don’t forget to make sure the survey notification option is ticked.
This is a cheat sheet focusing on the Developer Nation 23rd survey wave, giving you all the key details to make the most out of your experience:
What 11+ years of surveying developers. The Developer Nation survey has been measuring the preferences, needs and wants of developers for more than 11 years. It’s a dynamic survey where each participating survey taker will have a unique path, based on their own background and experience.
When The Developer Nation Community will be launching its 23rd survey wave on June 2 in English. On June 9, the survey will be available in all other languages: Spanish, Portuguese, Chinese Traditional + Simplified, Korean, Russian and Japanese.
Who is it for Developer Nation is borderless! Everyone’s welcome! The Developer Nation survey is global and open to all. In the previous edition, more than 20,000 developers and creators of all levels – from students to hobbyists and seasoned professionals – from 160+ countries, shared their views.
We want to hear your opinion if you see yourself as a developer, software engineer or tech creator involved in Web, Mobile, Desktop, Cloud, DevOps, Industrial IoT & Consumer Electronics, AR/VR, Apps/extensions for 3rd party ecosystems, Games, Machine Learning & AI, and Data Science.
If you nodded at any of the above areas or descriptions, this survey is for you. Keep reading for the benefits of participating or start now.
Why participate There are several benefits for those who take the survey. Some of these are:
Prizes By participating, developers can win amazing prizes and unlock more as they proceed, including a complimentary virtual goody bag packed with free resources.
Premium access to information Understanding the trends can be paramount to developers’ next career move. We share the results, data and ecosystem insights with the participants and tech organisations who use the data to improve their developer offerings.
Giving back and helping others For each qualified survey response, we will donate USD $0.10 to a charity of your choice. Our goal is to reach USD $1,800+ in donations. Take the survey, pick a charity to support, and help us make a difference.
What’s different this time Every wave is a new opportunity to give developers what they want. Here’s the latest benefits we introduce in this 23rd wave:
Weekly prize draws, including everyone who signs up to take the survey.
Special Prizes to be drawn for everyone taking the survey in the first 48 hours (2 winners: Nintendo Switch & iPhone 13).
A new way to reward participants: the more questions you answer the more chances you get to win. A participant’s name will be included multiple times in draws depending on the number of questions answered.
Prizes include: Nintendo Switch, iPhone 13, Xiaomi RedMi 11, Samsung Galaxy S22, Amazon Echo Dot 4th Gen, Premium Subscriptions and Licences, Vouchers for online courses and tutorials, Gift cards and vouchers for Amazon, Spotify, Apple Store, Google Play, cash to fund your development projects or towards the gear you need up to $1,000 USD and many more prizes drawn every week.
Everyone who completes the survey will receive a virtual goody bag filled with free subscriptions, discounts and vouchers.
You read this far, which should mean you’re interested. Why not start the survey and share your views on key topics only developers can understand? If you’re short of time, you can save your progress and continue later (you’ll need to sign up to save).
Are you creating for AR/VR? There is an additional, exclusive, survey dedicated to Augmented, Virtual and Mixed Reality creators, with the same benefits. AR/VR creators can share their reality views using this link.
What are some of the key differences between developers in East Asia, including the Greater China region, and the rest of the world? In the 22nd edition of our Developer Nation Survey we collected insights from developers and software engineers in East Asia to try to answer this exact question. Here is what we found!
“A fifth of the global developer population is located in either the Greater China region or the rest of East Asia”
We split the Greater China area from the rest of East Asia to provide more regional granularity. In terms of relative size, we find that almost a fifth (18%) of the global developer population is located in either the Greater China region (9%) or the rest of East Asia (9%). Breaking down East Asia into countries, we see that more than half of the developers here are spread across two countries: Indonesia (32%) and Japan (21%). When comparing developers across regions, we can see that just over a third (34%) of developers in the Greater China region have six or more years of experience, which is notably less than developers globally (43%). Furthermore, the Greater China region has a much smaller concentration (4% vs 22% globally) of highly-experienced developers (16+ years). With generally lower levels of experience in the Greater China area, aspiring developers may find starting a career here less competitive than developers in regions with higher levels of experience.
“East Asian developers outside China have similar levels of experience to the rest of the global developer population”
Both groups have a little more than a third (34%) of their developers with 11+ years of software development experience. However, East Asia’s data are largely propped up by Japan. The developer community in Japan tends to be highly experienced, with almost six in ten developers (59%) having 16+ years of experience. No other country has a higher concentration of developers with this level of experience.
“Developers in the region are mostly either self-taught or have an undergraduate degree in computing”
The journey to coding mastery lacks a clearly defined path. Developers typically state they’ve used more than two learning methods on average to learn how to code. In general, the self-taught method is the most popular among developers globally, with more than 60% using this method. However, our data shows that the proportion of self-taught developers fluctuates significantly across regions.
In the Greater China area, the most popular method for developers to learn how to code is via an undergraduate degree in computing, with 50% having used this method. This is significantly higher than developers in other regions (41% -42%). We generally see a higher concentration of professional developers in Greater China (83%) than we do in the rest of the world (70%). It could be that the job market in Greater China more often requires a degree in computing or engineering, which would also explain why self-teaching is used less often in this region.
Developers in the rest of East Asia, however, tend to follow the learning trends of developers in other regions. Here, we see the self-taught method is the most popular method (61%), followed by an undergraduate degree in software engineering (41%). Analysing the data at a country level, we see developers in Indonesia are more diverse learners. Developers in this country stated that they used three methods on average when learning to code. Indonesian developers are more likely to learn via self-teaching, online courses, and developer boot camps than any other developers in East Asia. This is quite different from their peers in Japan who are the least likely to use online courses and bootcamps to learn how to code. Instead, developers in Japan are most likely to use the self-taught (63%) and on-the-job training (45%) methods when learning to code.
“Less Stack Overflow, more Segmentfault.com and Teratail.com
Next, we explore how developers interact with the popular online community, Stack Overflow, to understand their engagement levels with programming support. Stack Overflow has become a standard support community for many developers, with more than eight in ten (85%) of the general developer population reporting they’ve used or visited this popular question and answer site.
Our focus on developers in East Asia and the Greater China area shows Stack Overflow’s popularity falls below the global average. Developers in these regions are around three times less likely to visit Stack Overflow than developers in other regions. Developers in the Greater China area are the least engaged, with only 19% having an account, and only 11% having earned at least one badge. Developers in this region have other home-grown Q&A site alternatives, such as segmentfault.com, which could be contributing to the lower adoption of Stack Overflow. Developers in Japan are skewing the perception of this region. Developers in Japan have even less activity on Stack Overflow than developers in the Greater China area. Here, only a little more than a third (36%) stated they use Stack Overflow. Furthermore, only about 5% have an account. Like developers in the Greater China area, our data does show usage of Stack Overflow increases among Japanese developers who have gained experience in software development, indicating that less experienced developers are using other platforms for support. Like China, Japan has other home-grown options like teratail.com where developers can field programming support from their peers, which may be the place new Japanese programmers visit more often to get answers to their questions.
