Forem: Peter Karakas

12 JavaScript Developers You Should Follow

Peter Karakas — Fri, 28 May 2021 15:30:47 +0000

In recent years, JavaScript has been consistently ranking in the top three most popular programming languages. Based on CodersRank users’ commits, JavaScript was the most popular language with our community in 2020 (with a whopping 851K commits).

Today, we’d like to highlight twelve cool JavaScript developers (in no particular order) who are not only great at what they do but also share their knowledge and contribute to the community. Some of them are big names already, but we’ve also included some rising stars⭐

Whether you’re a beginner in JavaScript or a seasoned professional, you’ll find lots of quality educational content by following them👇

David Walsh

David Walsch is a former Senior Software Engineer and evangelist for Mozilla. Prior to that, he worked as a Core Developer on MooTools JavaScript Framework, where he created numerous MooTools plugins, and as a Software Developer at SitePen. One of his mottos is to ‘work as much in the open-source space as possible’.

What he’s up to now:

Serves as Senior Full-Stack Engineer at MetaMask
Speaks at various conferences and meetups such as London AJAX, AustinJS, BrazilJS, Snow*Mobile, etc.
Shares cool demos, useful tutorials, and invaluable dev career lessons on his blog and to his 83,000+ followers on Twitter

Follow him on:

Piotr Kowalski

Piotr Kowalski is an open-source enthusiast and seasoned JavaScript developer. He started his career as a Web Developer, but once he discovered his passion to JavaScript, he decided to focus on the frontend and never looked back.

Kowalski is an expert in building web applications in diverse environments (for example this Smart TV platform or Ipla.tv). He’s created the architecture for lots of other big commercial projects, which are being used by a few millions of users monthly.

As a keen community builder, Kowalski also co-founded WarsawJS, ConFrontJS, and Educaton. If you’re looking for informative JavaScript content, you’ll love Kowalski’s blog (181 data-packed articles (!)) and his YouTube channel. At CodersRank, we’re big fans of his History of Front-end timeline and Awesome Shortcuts collections.

What he’s up to:

Works as Senior Frontend Software Engineer at Sumo Logic
His GitHub profile is a treasure trove of utility projects to explore
Shares useful tutorials on his blog and runs live open source sessions on his YouTube channel
Organizes webinars and training sessions on all things JavaScript

Follow him on:

Szymon Piłkowski

Szymon Pilkowski is an experienced JavaScript Developer with a passion for all kinds of experiments, focusing on HTML5 and NodeJS. He’s worked in a variety of exciting dev roles, such as helping NGO’s visualize their social change at Impact Mapper or visualizing orbits, flybys, and Near-Earth Objects for the European Space Agency.

Prior to that, in 2016 he’s served as a founder and teacher at the programming school Heycode.io.

What he’s up to:
Serves as a Sofware Engineer at Molecule.one, a cool startup that leverages AI to design novel chemical syntheses within seconds.
Ranks in the Top 5 JavaScript Developers in Poland at CodersRank
Grows a community at JS News: Jobs FB group

Follow him on:

Ben Nadel

Ben Nadel is the co-founder and a principal engineer at InVision App, Inc, a company that is at the forefront of the design and UX revolution. He lives and breathes JavaScript, NodeJS, AngularJS, ColdFusion, and User Experience.

On his blog, you’ll learn about various aspects of web application development including but not limited to the topics of ColdFusion / Lucee, JavaScript, Node.js, HTML, Cascading Style Sheets (CSS), and SQL.

What he’s up to now:

Runs ‘Working Code’ podcast (new episodes drop weekly on Wednesdays)
Works on a variety of Open Source projects

Follow him on:

Shawn Wang (Swyx)

Shawn Wang is a JavaScript developer who has worked on React and serverless JavaScript at Two Sigma, Netlify and AWS. He’s mainly active in the web dev community as a blogger and frequent speaker, committed to Learn in Public movement. He’s a GitHub Star and Stripe Community Expert.

Swyx has started and run communities for hundreds of thousands of developers, like Svelte Society, the React subreddit, and the React TypeScript Cheatsheet.

What he’s up to now:

Currently working on Developer Experience at Temporal.io
Recently published The Coding Career Handbook with advice for engineers going from Junior to Senior.
Teaches various courses and workshops (Design Systems with React + TypeScript, Building Custom CLI Tooling with OClif and React-Ink, Complete Intro to Netlify in 3.5 hours, etc.)

Follow him on:

Tania Rascia

Tania is a Senior Software Engineer specializing in modern JavaScript/TypeScript and architectural design patterns, documentation, and best practices. She started making websites in 1998 (on Geocities) and has been making them ever since.

On her blog (and in all her posts in other places), you can expect to learn a ton about Node.js, JavaScript (React/Redux, Vue), TypeScript, PHP, Python, Bash, HTML5, CSS3, JSON, and more.

What she’s up to now:

Serves as Staff Software Engineer at Balto AI
Recently authored Understanding the DOM book
Writes lots of tutorials on her blog and other websites
Works on a variety of open-source projects, which are available on her GitHub.

Follow her on:

Blog
Github

Khriztian Moreno

Khriztian Moreno is a JavaScript developer. On a daily basis, he uses JavaScript (ES6), React, Gatsby, CSS (inJS), GraphQL, Serverless, just to name the most important bits. He’s a community leader and an altruistic speaker. He helps others learn by doing through articles, videos, and courses about Javascript, React, and the static web.

What he’s up to now:

Co-organizes Medellin.js (the biggest JavaScript user group in Colombia), Avanet and JAMstack Medellin communities
Speaks at Commit.fm podcast
Producer at @commit.fm via @twitch

Follow him on:

Kent C. Dodds

Kent C. Dodds is a JavaScript software engineer and teacher. He’s taught hundreds of thousands of people how to make the world a better place with quality software development tools and practices. He’s a keen educator and organized multiple JavaScript workshops.

What he’s up to now:

Runs ‘Chats with Kent’ podcast
Develops awesome (and many of them free) video courses on React, JavaScript, Suspense, etc.
Runs The KCD Community on Discord, a community of people who want to make connections, share ideas, and use software to help make the world a better place

Get in in touch with him on:

Robin Weiruch

Robin Wieruch is a self-employed software and web engineer dedicated to learning and teaching JavaScript for client-server architectures. After obtaining his Master’s Degree in computer science, he gained experience from the startup world, where he used JavaScript intensively.

He shares his many years of practical experience in the field via his blog, four self-published ebooks, and a course platform.

What he’s up to now:

Shares excellent writings on all things JavaScript, React.JS, Node.JS, Firebase on his blog
As a keen believer in bridging the knowledge gap and unequal access to learning, his e-book The Road to React was translated into 6 languages (Russian, French, Chinese, Italian, Korean, Portuguese, and Persian)
Shares great tutorials to 17,000+ followers on Twitter

Follow him on:

Paolo Duzioni

Paolo Duzioni is a web developer focused on the front-end side and a coding coach, who has always been attracted to how creativity can be used along with web technologies, to create amazing experiences.

He builds websites and web applications, WordPress and Drupal themes, Laravel web apps, Vue JS and React JS/Native apps.

What he’s up to:

Works as a Teacher at Boolean Careers
Ranks in the Top 100 JavaScript developer in Hungary
Contributes to a variety of Open Source projects

Follow him on:

JC Smiley

JS Smiley is an experienced React Developer and a community builder. His top specialties are React, React Native, HTML5, CSS3, JavaScript, Node/Express, Angular, and Java.

Smiley is passionate about organizing tech meetups, helping others learn to code, and moderating an online slack channel for local developers.

What he’s up to now:

Manages Code-Connective, a local non-profit tech meetup group
Organizes other various meetups such as Dev-Memphis, Code-Connective, and Memphis Web Workers
Serves as a Teaching Assistant at Teach Code

Follow him on:

Jennifer Ponder

Jennifer Ponder is an experienced Technical Solutions Leader. She has worked as a software developer solving complex problems and implementing agile methodologies for B2B and B2C organizations.

A constant leader for diversity, equity, and inclusion in tech. She has helped communities plan their diversity and inclusion development strategies for minorities and underrepresented groups in tech.

What she’s up to now:

Serves as a Co-Lead for Atlanta Chapter for Black Women Talk Tech (Talk Tech Association) and National Program Director at STEM Atlanta Women
Serves as Director of Technology at Common Counsel Foundation Partners with startups and non-profits for events in the Atlanta area where she has given technical talks and talks around women creating their own pathway to reach leadership

Follow her on:

Connect with talented JavaScript devs around you!

CodersRank’s leaderboard of JavaScript developers. You can find and connect with top developers in your city or country🔥

Are you looking to connect with talented JavaScript developers in your area? Make new friends, find business partners, organize a peer support group or even find a mentor via our Developer Leaderboards!

12 Java Developers to Follow

Peter Karakas — Fri, 28 May 2021 11:36:02 +0000

The 12 developers below are absolutely worth following because of the informative, quality content they put out into the world. Be it tweets, blogs, videos, podcasts, or event speeches, I’m confident you’ll learn something new and insightful from each of them.

You may already recognize some big names but we have also included some rising stars from the community to keep things interesting.

Adam Bien

Adam Bien is a Java Architect and Developer who in his own words is ‘working with Java since 1995 and still really enjoying it.’ His impressive credentials include a Java Champion, NetBeans Dream Team Founding Member, Oracle ACE Director, and a Java Developer of the year 2010.

Bien spreads the love for the exciting world of Java via his blog, books, podcast, video courses, video workshops, and live events. He’s an excellent trainer who’s been voted a JavaOne Rockstar 5x times by the attendees of his sessions.

What he’s up to:

Organizes virtual live workshops airhacks.live and shares on-demand video workshops airhacks.io available for download
Runs a monthly free interactive Web & Java Q&A show on airhacks.tv
Sparks thought-provoking conversations with other Java experts on airhacks.fm podcast
Shares actionable Java tutorials on his blog (2236 articles to the day) and a YouTube channel with 17.6K+ daily visits
Shares his nuggets of knowledge via his Twitter account with 35,000+ followers

Check him out on:

Trisha Gee

Trisha Gee is a Java Champion and leader of the Java Developer Advocacy team at JetBrains. Having developed Java applications for a range of industries of all sizes, she has expertise in Java high performance systems, dabbles with Open Source development, and is a leader of the Sevilla Java User Group.
Trisha’s exceptionally passionate about sharing things that help real developers. She’s been voted JavaOne Rockstar 3x times.

What she’s up to:

Edited and co-authored three books: 97 Things Every Java Developer Should Know, What to Look for in a Code Review, and Developer, Advocate!
Helps developers to keep up with the world of Java via Java Annotated Monthly, a great summary of a month in the Java world
Released four video courses via Pearson’s Live Lessons
Inspired developers as a keynote speaker on a variety of conferences
Leads Sevilla MongoDB and JavaUser Groups and is a key member of the London Java Community
Shares Java knowledge with 28,000+ followers on Twitter

Follow her on:

Alan Richardson

Alan Richardson is an Agile Software Testing and Development consultant with 25+ years of experience. His mission as a coach and educator is to help developer teams to better test, automate and deliver improved quality software.

What he’s up to:

Author of Dear Evil Tester, Java for Testers, Automating and Testing a REST API, Selenium Simplified (11,000+ books sold)
Shares videos covering technical skills and practical software testing techniques to 17,000+ subscribers on his YouTube channel
Runs ‘The Evil Tester Show’ podcast
Speaks at various industry conferences. His tally is 60+ conference talks
Ranks as 1% of Java Developers Worldwide on CodersRank

Check him out on:

Thorben Janssen

Thorben Janssen has been a Software Developer and Architect for more than 15 years. More than a decade ago, he used one of the first Hibernate releases to implement the persistence layer of enterprise applications. Since then he’s used Hibernate and JPA in all kinds of projects of various sizes.
He shares his experience on ‘Thoughts on Java’, a treasure trove of information on all things Java including tutorials, YouTube videos, workshops, and online courses.

What he’s up to:
Wrote Amazon’s bestselling book Hibernate Tips
Regularly speaks at international conferences and Java User groups
Shares detailed Java tutorials on his blog and YouTube with 26,000+ subscribers

Check him out on:

A N M Bazlur Rahman

A N M Bazlur Rahman is a Java Developer with 8+ years of experience. He helps Junior Software Developers to master the top coding and collaboration skills so they get hired to work on amazing projects.

What he’s up to:

Runs the Java User Group in Bangladesh
Published several books about Java programming
Ranks at the Top 4% of Java Users on CodersRank
Has been recognized as ‘Most Valuable Blogger’ by Dzone Inc.
Shares useful Java nuggets on LinkedIn

Check him out on:

Jessica Kerr

With a dozen years of C and Java development at large companies under her belt, Jessica Kerr is a software developer who writes * Scala at Stripe. Besides Scala and Java, she also dabbles in Clojure, Elm, Ruby, Python and Go.
As an international speaker, Kerr’s mission is to help Java developers learn new concepts and ideas in order to help them enjoy their work.

What she’s up to:

Shares exclusive personal reflections on all things Java and effecting change in the world by operating and evolving useful software via her newsletter
Serves as a keynote speaker at various industry events
Shares her Java wisdom on Twitter with 33,000+ followers

Follow her on:

Sebastian Daschner

Sebastian Daschner is a self-employed Java consultant, author, and trainer. He supports his clients with workshops and tailored consultation engagements, by applying expert knowledge and experience with a high claim in software craftsmanship.

His mission is to educate developers about Java, enterprise software, and IT in general.

What he’s up to:

Created DayCaptain, a personal time and task management tool Shares productivity tips and experience-based technical advice on his blog
Runs a value-packed YouTube channel
Authored the book Architecting Modern Java EE Applications: Designing lightweight, business-oriented enterprise applications in the age of cloud, containers, and Java EE 8

Follow him on:

Heather VanCura

Heather VanCura is a Java Expert with 20+ years of technology leadership. She leads the Java Community Process (JCP) Program at Oracle, as well as the global community driven adoption and user group programs. She’s a keen community builder who contributes to multiple diversity initiatives.

What she’s up to:

Organizes Hackergartens and Early Adopter areas
Volunteers in multiple initiatives including Devoxx4Kids, Day of the Girl Events, and working with TechBridge Girls
Contributes to JDuchess, Women Who Code, and the Grace Hopper Conference/Anita Borg Foundation
Serves as an international speaker and community organizer of developer hack days around the world
Speaks at conferences, such as Devoxx, DevNexus, FOSDEM, JFokus, OSCON, and JavaOne

Check her out on:

Yong Mook Kim

Yong Mook Kim is a Java Developer and the blogger behind Mkyong.com. He has been sharing Java and Spring tutorials with his community since 2008. All his articles are simple and easy to understand, sharing tips that are well tested in the development environment.

His mission is to translate technology and programming in a way that’s easy for everyone to understand and help developers unlock their full potential.

What he’s up to:

Publishes easy-to-follow Java tutorials at Mkyong.com
Shares useful Java tips to 18,000+ followers on Twitter

Follow him on:

Monika Beckwith

Monica Beckwith is a consultant specializing in optimizing Java/JVM performance and Garbage Collectors, for enterprise applications. Before that, she led Oracle’s First Garbage Collector (G1 GC) performance team. She’s also a Java Champion.

What she’s up to:

Serves as a President at Code Karam LLC, a group of experts in OpenJDK/Oracle JVM and Garbage Collectors, providing in-depth analysis and support
An editor and writer for InfoQ, covering the latest news about Java
Speaks at various conferences such as JavaOne, StrangeLoop and QCon

Follow her on:

Mateusz Kupilas

Mateusz Kupilas is a Java Developer, YouTuber and entrepreneur. The mission behind his blog and YouTube channel is to help Junior developers to make their first steps in Java. He also shares lots of tutorials and retrospectives from his various coding and entrepreneurship projects.

What he’s up to:

Recently published Junior Developer, a must-have read for each rookie programmer who wants to be ready for their first job in the field
Runs a YouTube channel with 18,000+ subscribers.

Follow him on:

Dr Heinz Kabutz

A Ph.D. in Computer Science, Heinz has programmed significant portions of several large Java applications and has taught Java to thousands of professional programmers.

Dr. Heinz was chosen as a Java Champion by Sun Microsystems, the inventors of Java, for his work in advancing Java.

What he’s up to:

Teaches Java training including Java Specialist Master, Design Patterns, and Concurrency Specialist Courses anywhere in the world, either in person or remotely
Regularly speaks at all the major Java conferences Authors Java Specialists Newsletter
Shares his wisdom with 12,000+ followers on Twitter

Follow him on:

Join 20,000+ Java Developers on CodersRank!

Are you a Java developer? Among others, we’re proud of our vibrant community of both junior and experienced Java devs!

Register your own profile on CodersRank to showcase your developer story and discover how your skills compare to other Java programmers around the world.

2021 Developer Job Search Preference Survey

Peter Karakas — Wed, 17 Mar 2021 13:31:47 +0000

In February, we sent out a developer survey to our audience to learn more about devs and their job search habits.

We wanted to gain a better understanding of what bugs developers about the recruitment process. Our big-picture goal is to revolutionize tech recruitment as a whole. This includes both sides: helping recruiters/companies AND developers have a better experience.

Developers told us about…

How many job offers they get on average
Why they don’t respond to them
What makes them jump on an opportunity
What the BIGGEST problem with tech recruitment is
…and more!

It was a small survey of nearly 500 respondents. Still, we feel that we can reach definitive conclusions thanks to the diversified answers and a few clear trends that emerged in the results.

Just take a look at the word cloud that we generated out of the free text answers for the question “What do you hate most about the recruitment process?”

TL;DR:

Most developers are overwhelmed by the interview process, how long it takes, and they desperately need more information up front (such as salary info).

1: 62.53% of developers receive 0-2 job offers per week

Type: single-choice question.

The majority of devs get no more than two job offers per week. That may not seem like much but for many, it could be overwhelming.

At the same time, we would love to chat with the 3% of devs who said they receive 10+ job offers per week. We suspect that these devs are the ones who usually appear in the top 10 of search results on LinkedIn.

Let’s give these programmers a break and make space for new talent.

2: Almost half of participating developers answer these messages

Type: single-choice question.

Developers either answer their messages or they don’t. Nothing surprising there. However, almost half of them do try to get back to recruiters.

You will see in Question #3 and Question #9 WHY devs don’t respond. The quality of recruiter messages can make or break new relationships. The more automated the message looks, the less likely developers will make time to explore the opportunity.

3: Over 64% of developers get offers for the wrong job

Type: multiple-choice question. Developers could select up to 3 reasons.

More than 64% of developers included the reason ‘Irrelevant job title’ in their responses. They are receiving a lot of messages about job opportunities that do not reflect their expertise.

Why do we think this is? A developer’s past is still the main defining element in their job offers in the present and in the future. This is problematic. Just because they did two small projects in Java 8 years ago, they shouldn’t be getting messages about it today. This is why CodersRank has the “Preferred Job Roles” and the “Technologies I don’t like” sections.

Other times, developers don’t respond because some crucial information is missing from the recruiter’s messages. The salary range given is either not up to their preferences or absent entirely.

36% of developers have no time to respond to recruiter inquiries.

4: Most developers are blasted with messages on LinkedIn

Type: multiple-choice question. Developers could select up to 3 channels.

57.5% of developers usually get messages from tech recruiters & companies via LinkedIn. About 28% of them receive emails and the rest get direct messages on social media or phone calls.

Within the ‘Other’ option, developers mentioned Stack Overflow, Xing (the German LinkedIn), and word-of-mouth.

5: 51% of developers are OK with messages via LinkedIn

Type: single-choice question.

More than half of all devs don’t mind receiving messages on LinkedIn. They likely prefer to keep their recruitment-related communication within a professional platform.

‘Email’ landed as a close second in top communication choices.

6: Overwhelming majority of developers prefer to-the-point talk

Type: single-choice question.

82% of developers want to see a direct proposal about a position in their inbox. No fluff. No general introductions. They are not interested if the company may have a fitting role in the future. Programmers don’t want to entertain recruiters with no current openings.

7: When receiving a job offer, 82% of developers want to see the full tech stack needed

Type: multiple-choice question

The recruiter has made the initial contact. Now, the developer is ready to see what the job has to offer. To even consider this job, recruiters should include the above info as the bare minimum.

Tech stack, responsibilities, and company name are in most of the answers. Sometimes recruiters are secretive about the company they are hiring for and the devs are not crazy about that aspect. They want to know as much about the position as possible.

8: LinkedIn & GitHub play big roles when developers are looking for a new job

Type: single-choice question

LinkedIn is the biggest contributor to finding a new job. Recruiters have become more and more savvy in the past few years which reflects in GitHub being the second important element in the job search.

Other platforms, such as a developer website and job boards are supporting components to the main three profiles.

9: The biggest problem in tech recruitment is the convoluted, long processes

Type: free text input.

To give space for any issue that’s bothering developers, we gave them an open-ended question that they had to fill out manually. So, what do developers hate most about recruitment?

We see a clear trend emerge in the results. 24% of answers include complaints about the convoluted, time-consuming process of recruitment. They also dislike the fact that they often do not hear back about a position, nor is there general feedback. Developers are irked by the nonsensical and often unpaid tests. Many mentions that these tests have nothing to do with the role they’re applying for.

We collected all complaints under ‘Irrelevant questions/messages’ that contained mentions of spammy, untargeted, automated, or otherwise irrelevant messages from recruiters/companies.

Over 8% of developers have problems with the salary information provided. Recruiters either present no salary info until the very end or devs feel the offer is too low. Another 5% of them feel that recruiters do not provide all necessary details about a job.

More than 5% of developers say that their portfolios and preferences are often ignored. Even if they clearly state “no PHP roles, please” on their profile, for example, they still get messages about PHP roles.

The next few comment categories target recruiter behavior with little mercy. They say that recruiters and some companies are lacking enough technical knowledge, they are dishonest about positions, or that they downright lack empathy. Some developers mention that they feel they are treated only as “tech stacks”, instead of human beings.

We also received some comments from developers who have faced ageism, sexism, or biased decision-making in their careers. We speculate that we may have under surveyed developers who identify as women, and therefore, we suspect that these issues would have received a larger share in the survey.

10: 67% of developers think tech recruitment is spammy

According to our statistics, 67% of developers would mark tech recruitment as spammy in general. In this figure, we included any answer above 6 on the scale.

To understand why so many developers voted 6+, please refer to the Quotes from developers section below.

Quotes from developers

Below, we highlighted a few comments straight from the question ‘What do you hate about recruitment?’ Note, that some of these are very blunt. We hope that recruiters and companies will appreciate the honest developer feedback and make an effort to update their processes.

"Recruiters always (take it) for granted that you should be interested in what they offer, but the reality is that if I already have a job you have to show me something that triggers my interest if you want me to reply. And nope, it is not the fact that the unknown company is a leader in their market or that they have table tennis in the coffee area."

"The position is now remote, but after COVID it’s on-site."

"Some recruitment processes have many steps, taking months to give a final answer. Also that in some cases, they issue code tests, and theoretical tests, that in my opinion are useless."

"Why are they asking for my CV via LinkedIn when they can check everything on my profile?"

"Employers/recruiters asking every tech stack they heard of regardless of whether they’re relevant."

"DevOps = Kubernetes (LOL)"

"Bulk sent emails, with no personal touch. Having to send a CV while they could just check LinkedIn. Not hearing back from recruiters when you’re rejected. Not having it clear from the beginning what are the process steps."

"After getting selected for the practical test, spend days/weeks building the project and after that, get rejected without even a reason for so. This is truly unmotivating."

"Too many phases, normally it takes more than 3 or 4 interviews plus a technical challenge. I think all could be settled with a max of 2 interviews plus a technical assessment."

Summary

We can say that devs would prefer a simpler interview process with fewer steps and more feedback along the way.

In one word, IT hiring is broken. There is no doubt about it.

This is why CodersRank’s mission is to revolutionize tech hiring and fix recruitment from the ground up. “The ground” in this case is a standardized profile where developers can represent their true value based on their experience and other preferences. Less mismatched requests, less time wasted, more excellent developers placed.

Are you a developer?

CodersRank is a platform built by developers for developers. We get your frustration about spammy practices and time-wasting interviews. We are aiming to connect you with recruiters/companies who are ready to embrace experience-based evaluation. Even if you’re not open to new opportunities right now, you can use CodersRank to monitor your progress as a professional.

The more info you provide about your preferences on your profile, the less likely you’ll get irrelevant messages from recruiters going forward.

Create your developer profile now ››

Are you a recruiter?

We hope this survey was helpful to you in understanding developers. To simplify your interview process, review developers’ experience instead of their test results. And for a better response rate, make sure to only contact candidates who qualify for your opportunity.

CodersRank provides you the platform for this. Here, developers create their profiles by providing their real experience (via repositories) and combining it with their digital footprint. This gives you a code-based evaluation you can trust.

Appendix & Developer Profile

Who filled out this survey?

Type: single-choice question.

In this survey, more than 71% of respondents are either full-stack, back-end, or front-end developers. But you can find a variety of titles from across the spectrum: from engineering managers to mobile developers and sysadmins.

The results line up similar to the larger Stack Overflow survey. This tells us that our respondents are very close to the typical representation of the developer landscape.

Note: in the CodersRank survey, we did not ask developers about their gender. The numbers you see are unweighted and may have slight discrepancies with the larger developer community.

What’s their current job-search status?

Type: single-choice question.

Recruiters know this type of job-seeker very well: the passive candidate. They are not actively looking but open to new opportunities. In this survey, more than 56% of developers say they are interested in something new, and an additional 25% say that they are actively looking for a job.

10 Statistics from 2020 About Developers and Their Coding Habits

Peter Karakas — Fri, 08 Jan 2021 09:55:23 +0000

CodersRank is a community-based platform. It’s designed to help developers showcase their experience, grow professionally and make connections.

For the second year in a row CodersRank aims to give devs a big-picture overview of their coding habits from the past year. The platform combines their experience and activity from various sources: GitHub (public AND private repos), GitLab and Stack Overflow.

Aside from the personal overview, the platform also provides three additional reports:

Global
Local / Country-level
Fun Facts

The Global-level stats are based on 40,000+ CodersRank developers from around the world, same with the Local report. The Fun Facts are based on GitHub’s publicly available data on top performing repos and users.

In this article, we’ll highlight 10 of the most interesting stats from these three reports. Let’s see how developers coded in 2020!

CodersRank 2020 Developer Report

1. Most active month for coding: May

In 2020, developers were most productive in May. They submitted 286,000 commits, 816,000,000 insertions and 296,000,0000 deletions.

(Source, slide 2)

2. Most productive coding day of the week: Monday

Developers were most active on Mondays in 2020. They made a total of 376,000 commits on these days.

(Source, slide 3)

3. Most productive time of day: daytime

Devs churned out the most code and contributions between 12 pm and 6 pm during the day in 2020. Who said that developers were night owls?

(Source, slide 4)

4. Most used programming language: JavaScript

In 2020, JavaScript is still ranking as the top language worldwide. The full list included:

JavaScript
HTML
TypeScript
CSS
Python

We recognize that most developers do not consider HTML and CSS as languages, but rather markup languages. The CodersRank report did not differentiate between stats this year and simply listed the most used technologies as is. Next year, HTML and CSS will likely be featured on a separate list.

(Source, slide 5)

5. Security was top priority

Based on the number of commits, fluidattacks/integrates was the most popular public repositories in 2020.

(Source, slide 6)

6. Open source code beat private code

In 2020, developers committed almost 4x as much open source code as private code.

(Source, slide 7)

7. Most popular back-end framework: strapi

The strapi/strapi framework gained over 11k stars on GitHub this year, effectively beating out nest, django, laravel, and spring.

(Source, slide 5)

8. Most popular front-end framework: vue.js

After much competition with react.js, vue.js landed on the first place with the most stars gained in 2020 (24k). These two were followed by angular, svelte and nuxt.

(Source, slide 6)

9. Big cities pushed big code

Cities that pushed the most code in order: London, Sao Paulo, Frankfurt am Main, Moscow and Saint Petersburg.

(Source, slide 7)

10. The longest coding streak in 2020: 211 days

This person pushed out code every single day for 211 days straight. Congrats, great work! (Hopefully some washroom breaks were incorporated, though.)

(Source, slide 8)

Still reading? Here’s a surprise for you 🎁

If you registered a developer profile on CodersRank when the Year in Review came out, you probably weren’t able to generate your own personal report.

Well, great news! We are planning on doing a data push before the end of January so that all the new devs on the platform can get their 2020 coding report! Stay tuned.

Vue 3 Basic Tutorial (Migration plan for Vue 2 users)

Peter Karakas — Wed, 25 Nov 2020 12:27:11 +0000

Intro

At CodersRank we build our front-end with Vue.js. And with the recent release of Vue.js version 3 we decided to upgrade. Here, we’ll cover what needs to be changed to migrate to the all new Vue.js based on our experience.

We have 2 main projects. One project is the large developers profile website and the other one is a smaller admin section. To start, we decided to migrate the smaller admin section to see how hard it is to migrate (spoiler: not hard).

So, let's start.

Init Vue App

Let’s start at the main app entrypoint script. Vue.js version 3 uses new Global API and requires a different approach to initialize the app:

In Vue 2 we had:

// Import Vue 
import Vue from "vue";

// Import main App component
import App from "./App.vue";

// Init Vue app
const app = new Vue({
  // element where to mount the app
  el: "#app",
  // render main component
  render: (h) => h(App),
});

And in Vue 3 it is now:

// Import createApp function
import { createApp } from 'vue';

// Import main App component
import App from './App.vue';

// Init Vue app and pass main app component
const app = createApp(App);

// Mount app
app.mount('#app');

Vuex Store

If you use Vuex state management library, then it also needs to be updated to the latest version for Vue 3. And Vuex v4 also has new global API changes.

Let's look at how we use that and the init Vuex store in Vue 2:

import Vue from "vue";

// Import Vuex
import Vuex from "vuex";

import App from "./App.vue";

// Tell Vue.js to use Vuex plugin
Vue.use(Vuex);

// Create store instance
const store = new Vuex.Store({
  state: {
    /* ... */
  },
  getters: {
    /* ... */
  },
  mutations: {
    /* ... */
  },
  actions: {
    /* ... */
  },
});

const app = new Vue({
  el: "#app",
  render: (h) => h(App),
  // pass store instance
  store: store,
});

The same but in Vue 3 should be the following:

import { createApp } from 'vue';

// Import createStore function
import { createStore } from 'vuex';

import App from './App.vue';

const app = createApp(App);

// Create store instance
const store = createStore({
  state: { /* ... */ },
  getters: { /* ... */ },
  mutations: { /* ... */ },
  actions: { /* ... */ },
})

// Tell app to use store
app.use(store);

// Mount app
app.mount('#app');

Slots

In our Vue 2 app we were still using legacy slots API:

<some-component>
   <h1 slot="header">Title</h1>
 <p slot="content">Content</p>
</some-component>

It is required to be changed to a new one using <template> tags:

<some-component>
  <template #header>
    <h1>Title</h1>
  </template>
  <template #content>
   <p>Content</p>
  </template>
</some-component>

v-model

v-model also has new syntax in Vue 3. For example, if in Vue 2 we had the following component:

<custom-input v-model="inputValue" />
<template>
  <input :value="value" @input="onInput" />
</template>
<script>
  export default {
    model: {
      // specify prop that will be modified by v-model
      props: 'value',
      // specify event that should be received by v-model with the new value
      event: 'input',
    },
    props: {
      value: String,
    },
    methods: {
      onInput(e) {
        this.$emit('input', e.target.value),
      },
    },
  }
</script>

In Vue 3, by default, it expects that v-model should be bound to modelValue prop of the component and emit update:modelValue event in order to update model value. So we have to change the component to the following:

<script>
  export default {
    props: {
      // change "value" prop to "modelValue"
      modelValue: String,
    },
    methods: {
      onInput(e) {
        // emit "update:modelValue" prop with new value
        this.$emit('update:modelValue', e.target.value),
      },
    },
  }
</script>

But also Vue 3 provides more control over it and we still keep the prop named value. In this case we need to emit update:value event:

<script>
  export default {
    props: {
      // keep name as value
      value: String,
    },
    methods: {
      onInput(e) {
        // emit "update:value" prop with new value
        this.$emit('update:value', e.target.value),
      },
    },
  }
</script>

And to let Vue know that we need model to be bound to the value prop instead of the default modelValue, we should use v-model like this:

<custom-input v-model:value="inputValue" />

The best thing about it is that now components can have multiple v-models:

<some-component v-model:title="titleValue" v-model:content="contentValue" />

Composition API

Vue 3 comes with a new Composition API.

It is not necessary to change all your components to the new Composition API as Vue 3 still works perfectly with the current Options API. That is why we decided to keep it at the moment.

Custom Elements (Web Components)

At CodersRank we have a nice set of web components for developers to integrate on their personal websites. We also use them on our website:

It was not so straightforward to make Vue 3 understand them properly and not to think these are not Vue components.

In Vue 2 to specify custom elements, we used Vue.config.ignoredElements

import Vue from "vue";

Vue.config.ignoredElements = ["codersrank-activity", "codersrank-skills-chart"];

import Vue from "vue";
Vue.config.ignoredElements = ["codersrank-activity", "codersrank-skills-chart"];

In Vue 3 it is decided whether it is a custom element or not during template compilation phase, so it should be specified in webpack config Vue loader options:

{
  test: /\.vue$/,
  use: {
    loader: 'vue-loader',
    options: {
      compilerOptions: {
        // ignore elements that starts with codersrank-
        isCustomElement: (tag) => tag.indexOf('codersrank-') === 0,
      },
    },
  },
},

TypeScript

Vue 3 has much better TypeScript support. And during the migration to Vue 3 all we needed to change was the component declaration in single-file components:

In Vue 2 we used `Vue.extend` to define the Vue component:

<template>
  <!-- ... -->
</template>
<script>
  import Vue from "vue";

  export default Vue.extend({
    props: {
      // ...
    },
    data() {
      // ...
    },
    // ...
  });
</script>

And in Vue 3 we need to use the new defineComponent function:

<template>
  <!-- ... -->
</template>
<script>
  import { defineComponent } from "vue";

  export default defineComponent({
    props: {
      // ...
    },
    data() {
      // ...
    },
    // ...
  });
</script>

Post Scriptum

In this article we have covered just the basics that we faced ourselves in our own project during migration from Vue.js 2 to Vue.js 3. Of course there are many things to pay attention to if you use other APIs, Vue features and plugins. Worth to mention:

Official Vue.js 3 migration guide
Official Vue Router migration guide for Vue.js 3 (in case you use Vue Router)
New built-in Teleport functionality (if you used `portal-vue` plugin which is not yet supported for Vue.js 3)
Composition API Reference
Render function API changes

About CodersRank

Interested in learning more about how we help developers? Check out our website here & create your own profile!