HACKER Q&A
📣 tmaly

Top Skills to Learn for 2022?


If I wanted to keep my skill set sharp. What top 3 tech skills should I learn in 2022 to keep providing the most value in your opinion?


  👤 AceJohnny2 Accepted Answer ✓
Communication.

Learn how to share your ideas and opinions in a concise, engaging way. Learn to advocate for (or against) something in a way that will have people engaged (first point: never be combative, people will mostly dismiss you as immature or emotionally compromised).

Yeah it doesn't sound like a "tech skill" but it absolutely is and I think too many "tech" people severely undervalue it, preferring instead pure "lone wolf" kind of skills that don't require the squishy, dirty aspects of dealing with other humans (speaking from personal experience here).

You can accomplish a lot on your own with the right talent and skills. But you can always accomplish more if you can engage more people.

Maintain a blog of interesting things you've learned, hiring managers will value the demonstrated writing skills.


👤 mgraczyk
I'm a former startup founder and staff engineer at a big tech company. It depends a lot on where you want to be. Here's my take.

You want to be an engineer at a small startup:

* Typescript and be familiar with common libraries and frameworks. I believe TS is going to become more common everywhere, frontend, backend, DevOps, etc.

* Learn python if you don't already know it

* Learn some kind of data science stack you can use to analyze small data sets (under 100GB). Pandas+numpy+scipy, Julia, whatever. Just be good at answering data questions and building small models.

Big company:

* Writing and communication. Practice writing about projects you've worked on and write down the projects you want to build with enough details that a junior engineer could build it.

* Be aware of how much companies are paying and be willing to leave for better compensation, work-life balance, or responsibilities. Practice interviewing.

* Read all the major postmortems from incidents at a big tech company and try to find patterns related to your area or part of the stack.


👤 thom
Depends if you mean “providing the most value” or “most likely to keep providing value”. The latter is kinda boring. The former is more interesting but depends on what you’re interested in:

1) Data infrastructure. This is the inner loop of a lot of tech companies. Speed it up, reduce the cycle time, reduce the AWS spend and you’re a god.

2) Data science. Provide better insights into a domain or its customers, or as above, provide a better platform for others to experiment and discover the same, and again, be worshipped.

3) Customer success. Discover that your business is in a local maxima but could shift to provider vastly more value for customers, ditto.

4) Hiring. Forget how great you are, if you can hire great(er) people then you are an almost exponential factor in your company’s success.


👤 PaulMest
The biggest gains I'd recommend for just about everybody in a tech field:

1) Continuing to stoke the flames of curiosity and discipline within yourself so that you genuinely love to learn and get slightly better every day without fear of perpetual burnout.

2) Confidence to ask questions in group settings so that you can quickly get to a collective understanding of the problem space and challenges at play.

3) Communication. Litmus test is being able to present what you're doing in an understandable and approachable manner that can get the right people engaged.

And to answer the spirit of your question more directly, some technologies that my team have found to be super valuable:

A) Hasura (GraphQL/ORM layer to interface with Postgres)

B) Pulumi (TypeScript IaaC)

C) React (nothing super new here, it just continues to be incredibly valuable to us)

D) NestJS (TypeScript-friendly framework that is like Angular for the backend)


👤 mikewarot
In 2032 it will be possible to correctly answer that question, with 9 years of hindsight to assist. ;-)

I'm thinking that having experience with a capability based operating system such as Fuchsia or Genode as a daily driver will be quite valuable, as you'll be ahead of the adoption curve. I hope to have this happen myself next year.

If you haven't already, I recommend doing the Advent of Code puzzles, all of them, in whatever language you are comfortable in. Redo them in whatever language you want to learn, ad infinitum. I personally haven't gotten through all them in Pascal yet. I did last year in real time, and except for day 19, and current in 2021.

I suggest you learn a little bit of practical machining, that done in machine shops. The process of using machine tools to make things, otherwise known as subtractive manufacturing. I'd also suggest you learn additive manufacturing as well. It is good to understand how the atoms around you came to be configured as they are.

There you go, 3 things to learn for 2022.


👤 computershit
Data pipeline / ETL orchestration.

Prefect: https://www.prefect.io

Dagster: https://dagster.io


👤 codingdave
It depends on what you already know. Picking up new skills that are similar to what you already know isn't a big value add. But picking something up that is completely alien to your current skills not only adds a new skill, but makes it easier to pick up anything similar.

👤 baron816
Google, Stack Overflow, Copy/Paste.

👤 mbrodersen
You need to figure out what your goal is first. And then pick the skills that are most likely to help you achieve that goal. If your goal is to broaden your general understanding of programming then learning Elm or Haskell is a good choice. If your goal is to become a web developer then Typescript + React is a good choice. If your goal is to become a game programmer then Unity or Unreal is a good choice. Etc. Etc.

👤 replete
What is the best vegetable to eat for dinner?

👤 mianos
Prefect Orion, already love Prefect and I think the applications for a DAG workflow engine are much wider than anyone even imagines Pytorch, finally picked up a Jetson. Back to VHDL, Sparkfun just released a new tutorial with the old Lattice board. VXLans. The new C++ coroutines.

👤 0x008
The best answer to this in my opinion is universally: Learn things that compound.

Learn stuff that will enable you to be better at what you are doing. This might be

* tools, techniques for development

* techniques for learning

* understanding of the underlying systems

* understanding of the processes involved



👤 nanna
Emacs.

👤 brisad
Prolog

👤 giantg2
Skill alignment to ncrease potential value depends on the business problem and tech stack.

👤 nikivi
Karabiner (https://github.com/pqrs-org/Karabiner-Elements) + Deno/Go as nice scripting languages.

👤 cpach
In what domain? Are you into frontend, backend, data science, embedded, etc?

👤 bovermyer
Not enough information provided.

"Tech skills" is an enormously broad category on its own. You provide no context, so there's no way to narrow it down.

What do you want to do in your career? Answer that question first.


👤 stonecharioteer
Algorithms and data structures. Get really good at solving leetcode problems. You'll maximize your total compensation in no time.

👤 chubot
Shell, SQL, Python

👤 bigdict
Basic math, basic CS, written communication.

👤 f0e4c2f7
AWS, Kubernetes, and Terraform.

👤 vfulco2
AWS serverless all the things

👤 andrei_says_
Learn to be kind to yourself, while being kind to others, and vice versa.

👤 taubek
It all depends on your background. Maybe brush up Markdown skills?

👤 adamnemecek
It kind of depends on your goals but Rust, WebGPU (wgpu), Julia.

👤 muzani
My personal plans for 2022:

Low risk: React

Medium risk: Android Jetpack or Flutter

High risk: OpenAI Codex


👤 hu3
Svelte, TypeScript and Docker

Can't go wrong with any of those.


👤 chupkarkhotay
How to write code and not blog about it, in Rust.

👤 midrus
For me it is going to be Laravel and PHP.

👤 b20000
negotiation

👤 simonw
GitHub Actions.

👤 lido
python, unix, and protocols.

👤 ravenstine
AI

VR

Blockchain

Smart contracts

k8s

k3s

k9s

No-code

Web Assembly

Quantum Computing

GPT-3


👤 shahbaby
Leetcode

👤 yayitswei
Solidity.