DEV Community: Asael Shinder

The Real Skill Is Learning How to Learn

Asael Shinder — Thu, 03 Sep 2026 06:34:14 +0000

People keep asking which skill to bet on for the future.

Which language. Which framework. Which tool will still matter in five years.

I understand the question, but I think it is aimed at the wrong target.

Any specific skill you pick has a shelf life. The tool you learn today may be half-forgotten by the time you are good at it.

Betting your future on one skill is betting on a thing designed to expire.

The real skill, the one that never expires, is learning how to learn.

The people who thrive across decades are not the ones who knew the right thing at the right moment.

They are the ones who got good at picking up new things quickly, over and over, as the ground kept shifting.

Watch how they operate.

They are not attached to what they already know. When something changes, they do not grieve the old way. They just start learning the new one.

They know how to go from zero to useful fast, because they have practiced that move so many times it stopped being scary.

That is the actual asset. Not the knowledge. The ability to keep acquiring it.

So if you want to future-proof yourself, do not chase the hottest skill.

Get deliberate about how you learn.

Notice what makes something stick for you. Notice how you go from confused to competent, and get faster at that path.

Learn one hard thing all the way through, not for the thing itself, but to practice the process of learning hard things.

Every time you do that, you sharpen the tool that outlasts every specific skill.

The future is going to keep changing faster, not slower. Whatever is essential now will be replaced by something you have not heard of yet.

You cannot memorize your way through that. Nobody can.

But you can become the kind of person who is never thrown by the new, because being a beginner again is just a familiar step in a process you have done a hundred times.

Do not just learn things.

Learn how you learn.

That is the one that compounds forever.

– Asael Shinder

Ask What You Would Do Differently

Asael Shinder — Thu, 03 Sep 2026 06:29:03 +0000

When you ask for feedback, most people give you the safe version.

You say how did that go, and they say it was good, nice work.

They are not lying. They just do not want to be the one to hand you criticism you did not clearly ask for.

So you get a warm, useless answer, and you learn nothing.

Here is a better question. Ask what you would do differently.

That small change does something clever.

It gives the other person permission. You are no longer asking whether it was good. You are assuming there is room to improve and inviting them to point at it.

Now the honest answer is the easy one to give, instead of the awkward one.

Notice you are not asking what was wrong.

What was wrong sounds like a hunt for failure, and it can put people on the defensive on your behalf.

What would you do differently is forward-looking. It is about the next version, not blame for this one.

It is easier to answer, and easier to hear.

Try it and watch what happens.

People who gave you a shrug and a nice job will suddenly have real, specific thoughts. They had them all along. You just had not opened the door.

And when they answer, do the hard part. Do not defend.

The instinct will be to explain why you did it the way you did.

Resist that. You did not ask so you could argue.

You asked so you could learn. So listen, thank them, and actually sit with it.

If you defend every time, you teach people that asking you is pointless, and the honest answers dry up.

If you receive it well, you become someone people are willing to be straight with.

That is worth more than any single piece of advice, because it turns every person around you into a source of growth.

So next time you finish something and want to know how it really went, do not ask if it was good.

Ask what they would do differently.

Then get quiet, and let them tell you.

– Asael Shinder

Confidence Follows Action, Not the Other Way

Asael Shinder — Thu, 03 Sep 2026 06:23:51 +0000

A lot of people are waiting to feel confident before they act.

They think it works like this. First the confidence arrives, then you do the hard thing.

So they wait. They prepare more. They tell themselves that once they feel ready, they will step forward.

And the confidence never quite shows up, so they never quite step.

I want to save you years of that.

Confidence does not come first.

Action comes first, and confidence follows it.

You do the thing while still afraid. It goes okay, or okay enough. And afterward, a little confidence settles in that was not there before.

Then you do the next thing, slightly less afraid.

That is the actual order. Not confidence then action. Action then confidence.

Think about anything you are sure of now that once scared you.

Speaking up in a meeting. Owning a piece of work. Telling someone they were wrong.

You did not wake up confident about those. You did them, badly at first, and the confidence accumulated from the doing.

There was no shortcut around the doing. There never is.

So if you are waiting to feel ready, understand what you are really waiting for.

You are waiting for a feeling that only comes after the exact step you are avoiding.

The confidence is on the other side of the action. You cannot reach it from where you are standing.

The only path is through the uncomfortable part.

This is freeing, if you let it be.

It means you do not have to feel brave to act. You just have to act while unbrave, and let the bravery catch up.

The feeling of being unready is not a signal to wait.

It is just what growth feels like from the inside, before you have the evidence that you can handle it.

So stop waiting to feel ready.

Take the small version of the scary step today.

The confidence you are looking for is not lost.

It is just waiting for you to move first.

– Asael Shinder

Say Less So the Point Lands

Asael Shinder — Thu, 03 Sep 2026 06:18:39 +0000

When you care about being understood, the instinct is to say more.

Add context. Cover every angle. Explain the background so nothing is missed.

You think more words means more clarity.

Usually it means the opposite.

The more you say, the harder your listener has to work to find the one thing that matters.

You buried it. It is in there somewhere, in the third paragraph, but they have to dig.

And most people will not dig. They will skim, half-catch it, and move on.

So the thing you most wanted them to understand is the thing they missed.

Here is the shift. Say less, so the point can land.

Before you send that long message, ask what the one thing is. The single idea you need them to walk away with.

Say that first. Say it plainly. Then stop, or add only what genuinely supports it.

Cut the rest. The caveats nobody asked for. The backstory that made sense in your head. The three examples when one would do.

This feels risky, I know. You worry that trimming makes you look like you did not think it through.

The opposite is true.

Anyone can write long. It takes no effort to dump everything you know onto the page.

Saying it short means you did the thinking for the reader. You figured out what actually mattered so they did not have to.

That is a gift, and people feel it.

The clearest people I know are not the ones who know the most words.

They are the ones who know which words to leave out.

Watch how a good explanation feels. It feels light. It moves. You are never lost, because there is nothing extra to get lost in.

That lightness is not accident. It is edited.

So write your message. Then read it again and ask what you can remove without losing the point.

Remove it.

Read it once more. Remove again.

What is left will be shorter, sharper, and far more likely to be understood.

Say less.

Mean more.

– Asael Shinder

Struggle First, Then Look It Up

Asael Shinder — Thu, 03 Sep 2026 06:13:28 +0000

When you hit something you do not understand, the answer is right there.

One search away. One question to a tool that will explain it instantly.

And I want you to resist that, at least for a little while.

Not because looking things up is bad. It is one of the most useful skills you have.

But because of what happens in the gap before you look.

When you struggle with a problem first, you are building something.

You are forming the shape of the question. You are noticing where exactly your understanding breaks. You are trying wrong ideas and feeling why they are wrong.

That effort is not wasted time on the way to the answer.

That effort is the learning.

The answer you get after struggling lands in a mind that has been prepared to hold it. It clicks into a slot you carved yourself.

The answer you get instantly, before any struggle, lands on flat ground and slides right off.

You have felt this. The thing you looked up in two seconds, you forgot by the next day.

The thing you wrestled with for an hour, you still remember years later.

So here is the practice I would give you.

When you get stuck, sit with it first. Give it a real attempt. Ten minutes, twenty, whatever the problem deserves.

Write down what you think is happening. Guess. Be wrong on purpose.

Then look it up.

Now the answer means something, because you meet it with a question you actually own.

I am not telling you to be stubborn. If you are truly stuck and going in circles, get help. Spinning forever is its own trap.

But do not skip straight to the answer out of reflex.

The struggle is uncomfortable, and comfort is exactly why people reach for the quick answer.

The discomfort is the point.

That is your brain doing the work that makes the knowledge stick.

Earn the answer a little.

You will keep so much more of it.

– Asael Shinder

Chase Problems, Not Job Titles

Asael Shinder — Thu, 03 Sep 2026 06:08:17 +0000

It is easy to build a career around titles.

You want to be a senior. Then a lead. Then whatever comes after that.

The titles become the map, and you steer your whole path toward them.

I want to suggest a different compass. Chase problems, not titles.

Here is the difference.

If you aim at a title, you optimize for looking the part. You collect the resume lines. You do what seems promotable.

And you can absolutely get the title that way.

But you often arrive hollow, because the title was the goal, not the growth.

If you aim at problems instead, something better happens.

You go find the hard, interesting thing nobody has cracked yet. The messy system nobody wants to touch. The question the team keeps stepping around.

You throw yourself at it because it is genuinely worth solving.

And a funny thing follows. The titles come anyway.

They come because you became the person who solves hard things, and organizations promote that, eventually, even when they are slow about it.

But now the title sits on top of real capability, not the appearance of it.

So when someone offers you a choice, do not ask which one sounds more senior.

Ask which one has the more interesting problem.

Ask where you will be stretched, where you will be a little out of your depth, where you will have to grow to keep up.

That is the direction to walk.

I have watched people turn down the flashy title for the harder problem, and I have never once seen them regret it a few years later.

I have seen plenty regret the reverse.

The title chasers plateau, because the title was the ceiling all along.

The problem chasers keep climbing, because there is always a harder problem, and each one makes them more.

Your career is not a collection of labels.

It is a collection of things you learned to do that you could not do before.

Aim at those.

Let the titles catch up on their own.

They usually do.

– Asael Shinder

The Best Thing You Can Give Is Your Time

Asael Shinder — Thu, 03 Sep 2026 06:03:06 +0000

When people think about mentoring, they imagine having brilliant answers.

The perfect piece of advice at the perfect moment.

I want to take that pressure off you, because it is not where the value lives.

The best thing you can give someone is your time, given fully.

Not multitasking while they talk. Not glancing at your screen. Not waiting for your turn to speak.

Just being there, present, for the fifteen minutes you promised.

That sounds almost too simple to matter. It is the thing people remember for years.

Think about who shaped you. I would bet it was rarely the person with the cleverest advice.

It was the one who slowed down for you.

Who let you ramble until the real question surfaced. Who did not make you feel like you were wasting their afternoon.

That kind of attention is rare, and it is expensive, because time is the one thing you cannot make more of.

Which is exactly why giving it means so much.

You do not need to be senior to do this. You do not need a title.

You just need to actually stop and listen when someone comes to you.

Here is the trap I want you to avoid. When someone asks for help, the instinct is to fix it fast and move on.

You solve the surface problem in two minutes and feel efficient.

But often the fast answer misses the point, because you never stayed long enough to hear what they were really stuck on.

Slow down.

Ask the second question. Then the third.

Let the conversation breathe long enough for the real thing to come out.

That is not wasted time. That is the whole job.

The advice you give will fade. Half of it they will forget by next week.

What stays is the memory that someone took them seriously.

That someone made room for them when they had every reason not to.

Give that, and you will have mentored well, even on the days you had no clever answers at all.

Your presence was the answer.

– Asael Shinder

Let the Machine Do the Boring Part

Asael Shinder — Wed, 02 Sep 2026 07:01:13 +0000

There is a lot of fear right now about machines taking the work.

I understand it.
But I want to point you at a more useful way to think about it.

The tools are getting good at the boring part.

The boilerplate.
The first rough draft.
The repetitive lookup you used to do a hundred times.

For a lot of people, that feels threatening, because that boring part was where they felt useful.

But step back.

If the machine does the tedious middle, what is left for you?

The judgment.

Deciding what to build in the first place.
Knowing whether the answer it gave you is actually right.
Understanding the user well enough to know the fast solution is the wrong one.

Choosing what matters when everything looks equally possible.

None of that goes away.
If anything, it becomes the whole job.

So the people who thrive are not the ones fighting the tools to prove they can still do the boring part by hand.

They are the ones who hand off the tedium gladly, and pour the freed-up energy into the parts that need a human.

But this only works if you actually have the judgment.

And judgment comes from having done the boring part enough times to know what good looks like.

So here is the balance I would hold if you are early.

Do not skip the fundamentals just because a machine can generate them.

You still need to know why the generated code is right or wrong.
You still need the taste to catch the confident, plausible answer that is quietly broken.

Learn the craft.
Then let the tool carry the parts you already understand.

That is the posture that wins.

Not resisting the machine.
Not blindly trusting it either.

Learning enough to direct it, check it, and aim it at the right problem.

The boring part was never the point.

It was just the toll you paid to get to the judgment.

Let the machine pay more of that toll.

And spend what it gives back on becoming the kind of person the machine will always need pointing it.

– Asael Shinder

Notice What's Working, Not Just What's Broken

Asael Shinder — Wed, 02 Sep 2026 06:56:02 +0000

When most people think of feedback, they think of problems.

What went wrong.
What needs fixing.
What to do better next time.

That is half of feedback.
And it is the easier half.

The half almost everyone skips is telling people what is working.

We assume the good stuff is obvious.
If someone did something well, surely they know.

They usually do not.

People are far more aware of their mistakes than their strengths.
The thing they did well often does not even register to them.

So when you say nothing, they hear silence, and silence tends to read as neutral or negative.

Here is what changes when you name the good.

The person learns what to keep doing.

That sounds simple, but think about it.
If I only tell you what to stop, you know what to avoid, but not what to repeat.

Positive feedback is not a pat on the head.
It is direction.

It says do more of this, and it is just as useful as any correction.

But it only works if you do it the same way you should do the hard kind.

Be specific.

Do not say great job, it was fine by lunch.

Say the way you broke that problem into three steps in the meeting made it easy for everyone to follow.

Now they know exactly what worked, and they can do it again on purpose.

There is a quiet bonus, too.

When you regularly notice what people do well, the hard feedback lands better when it comes.

Because they know you are actually watching.
You are not only there when something breaks.
You see the whole picture, the good with the bad.

That builds trust, and trust is what makes any feedback usable.

So do not save your words only for what needs fixing.

Catch people doing things right, and tell them exactly what you saw.

It is not flattery.

It is one of the most useful things you can give someone.

And most people almost never get it.

Be the one who does.

– Asael Shinder

Confidence Is Quieter Than You Think

Asael Shinder — Wed, 02 Sep 2026 06:50:51 +0000

When you are new, you picture confidence as something loud.

The person who speaks first.
Who never hesitates.
Who fills the room and seems certain about everything.

So you try to become that, and it feels fake, because it is.

I want to give you a different picture.

Real confidence is usually quiet.

It is not the person who talks the most.
It is the person who is comfortable not talking, and then says one clear thing when it matters.

Loud is often insecurity working overtime.

The person performing certainty is frequently the one least sure underneath.
They fill the silence because silence scares them.

Quiet confidence does not need the room to know it is there.

It shows up in small ways.

Saying I do not know without flinching.
Asking the basic question without apologizing for it.
Being fine to sit with a pause instead of rushing to fill it.

Changing your mind when the facts change, and not treating that as a loss.

None of that is loud.
All of it is confidence.

Because the truest sign of it is not certainty.

It is being okay with uncertainty in front of other people.

The insecure person cannot admit a gap.
The confident person admits it easily, because their sense of worth is not riding on looking flawless.

So if you have been waiting to feel bold and loud before you count yourself as confident, stop waiting.

That is not where it lives.

Confidence is the calm underneath.

It is doing the work steadily, speaking when you have something to add, staying quiet when you do not, and not needing to prove anything in between.

You do not have to become the loudest person in the room.

Some of the most confident people I have ever worked with barely raised their voice.

You just knew, when they spoke, that it was worth hearing.

Build that.

Not the volume.

The calm.

That is the confidence that actually lasts.

– Asael Shinder

Tell People What You Need From Them

Asael Shinder — Wed, 02 Sep 2026 06:45:40 +0000

A lot of communication fails at the very last step.

You explain the situation clearly.
You lay out the context, the problem, the background.

And then you stop.

You assume the other person will know what to do with all of it.

They usually do not.

They read your careful message, feel the weight of it, and think one quiet thing.

Okay, but what do you want from me?

I see this constantly.

Someone writes three paragraphs describing a bug, a blocker, a concern.
It is all accurate.
It is all useful.

But there is no ask at the end.

So the reader is left guessing.
Are you venting?
Warning me?
Asking me to fix it?
Waiting on a decision?

The message did its job of informing, and then failed at the only thing that would move it forward.

So build one small habit.

Before you send anything that matters, add a line that says exactly what you need.

I need a yes or no on this by Friday.
I need you to take the deploy from here.
I am not asking you to fix it, I just want you to be aware.

That last one matters too.
Sometimes the need is only awareness, and saying so frees the reader from wondering.

This is not about being blunt or demanding.

It is a kindness.

You are saving the other person the work of decoding your intent.
You are turning a wall of context into something they can actually act on.

The clearest people I know all do this.

They can write a long, careful explanation.
But they never make you guess the point.

They end with the ask.

So next time you finish a message and feel that vague hope that the reader will just understand, stop.

Reread it and ask yourself one question.

Would a busy person know exactly what to do next?

If not, add the line.

Tell them what you need.

It is the difference between being heard and being answered.

– Asael Shinder

Learn the Why Behind the Rule

Asael Shinder — Wed, 02 Sep 2026 06:35:17 +0000

Early on, you learn a lot of rules.

Always handle the error.
Never trust user input.
Keep functions small.

You follow them because someone told you to, and following them keeps you out of trouble.

That is fine at the start.

But there is a level you get stuck at if you only ever collect rules.

Because rules without reasons are brittle.

You apply them everywhere, even where they do not fit.
And the moment you hit a situation the rule did not anticipate, you are lost, because you never understood what the rule was protecting you from.

So here is the shift that matters.

Stop learning the rule.
Start learning the why behind it.

When someone says keep functions small, do not just nod.
Ask why.

The real answer is not that small is holy.
It is that a function you can hold in your head is a function you can change without fear.

Once you understand that, the rule becomes flexible.

You know when a slightly longer function is fine, and when a short one is hiding the real problem.

You are no longer obeying.
You are deciding.

This is the difference between someone who has two years of experience and someone who has the same year of experience twice.

Both know the rules.

Only one of them knows what the rules are for.

So every time you meet a best practice, a convention, a should and a never, do not just file it away.

Dig one level down.

What breaks when you ignore this?
What pain did someone feel that made them write this rule down?

When you understand the pain, the rule stops being a cage and becomes a tool.

You can wield it, bend it, and know exactly when to set it aside.

That is what senior really means.

Not memorizing more rules.

Understanding the reasons well enough that you could have invented the rules yourself.

Learn the why, and every rule you meet after that gets easier.

– Asael Shinder