06Jun

Python’s not feeling as much love as it used to. But Rust is loved more.

In the US, 58% of developers are full-stack. 14% identify as DevOps specialists, an envious role as they and site reliability engineers are among the highest-paid individual contributors. No wonder then that 48% of IT professionals believe DevOps is an extremely important job.

These are just a sampler of how some 64,000 respondents – mostly professional developers, but also including students, marketers, hobbyists and a smattering of others — from 186 countries responded to Stack Overflow’s annual Developer Survey. The US sample accounted for almost one-in-five responses, followed by India at 13% of the total.

Of all the programing languages developers work with, 86% say they love Rust best. Python, a perennial 2nd place love, was displaced this year by Typescript, loved by 67%. Still, 30% of developers who don’t work with Python want to learn it. Half that many want to learn Rust.

As might be expected, men accounted for 92% of professionals. In the US, 12% identified as women or non-binary. 71% were white and three-quarters have at least a bachelor’s degree.

At the time the survey was conducted in February, before COVID-19 concerns closed businesses, 83% of the survey’s worldwide professional developers were employed full-time. One-in-ten was a contractor, freelancer or self-employed. In the US, only 6% of the respondents described themselves as freelancers, contractors or self-employed; 79% were full-timers.

By far, most work for smaller companies. Of all respondents in the survey, 60% said they work for a company with fewer than 500 employees. Only 14% work for a company bigger than 10,000 employees.

63% of respondents are satisfied with their job; only 17% globally are actively looking for a new job. Fewer (14%) in the US are looking. However, a majority say that though they’re not actively looking, they’re open to being approached with new opportunities.

Photo by Luca Bravo on Unsplash

[bdp_post_carousel]

Tech Team Leadership Takes More Than Coding

You’ve just been tapped to lead a development team on a new project. It’s a sign of the company’s confidence in you and the opportunity you’ve been wanting for a while.

Now that you’re back at a workstation, reality is setting in. What do you need to get your team on board and rowing together?

In a word, it’s leadership. And that has far less to do with your coding skills than your ability to communicate, motivate and collaborate. Your team will look to you for guidance in setting priorities, advocating for them up the food chain, and working with them to solve problems.

“In today’s world,” says The Ohio State Engineer Magazine, “It is essential for an engineer to possess strong communication skills; it is the biggest determiner of success in the modern engineer’s professional career.” This goes double for project leads and managers.

Clear communication starts with knowing the details of the project, defining the end goals clearly, assigning roles and setting expectations. Clarity is essential, so even when you see nodding heads, don’t assume everyone understands. Ask for discussion. A diplomatic way of ensuring your team understands what needs to be done is ask if the process and goals are realistic; does anyone see any potential problems. Invite pushback on the timeline.

Besides uncovering misunderstandings or communication gaps, you’ll demonstrate your openness to disagreement and differing points of view. Creating an environment of psychological safety is the single most important component of team success, according to Google, which exhaustively studied team leadership.

Slack blog post describes how a team lead creates psychological safety:

  1. An empathetic approach – “Strive to read your teammates. Are they content, stressed out or struggling?… Aiming to empathize with their point of view is key to gaining their trust.”
  2. Practice active listening – This means listening to understand what the person is saying rather than thinking of how we will respond.
  3. Avoid finger pointing – Constructive feedback is helpful. But blaming does nothing good. When problems arise — and they always do — focus on how to solve them. Involving the team in finding solutions is often a smart way to find creative ways to resolve problems.
  4. Be humble – When you make a mistake, admit it. When you’ve been short with someone, apologize. Say “please” and “thank you” often.

Image by Free-Photos from Pixabay

[bdp_post_carousel]