There is No Failure, Only Feedback.

The best lessons I learned from my failures & which helped me to grow as a software engineer.

A Thread...
Prioritizing effectively is one of the most important keys to your success.

When you feel like you’re working on the right thing at the right time, it’s easier to focus and stay engaged.

Prioritizing is a continuous activity.

It’s about making trade-offs.
Rather than prioritize with p1, p2, p3.

I’ve found it way more helpful to think in terms of

MUST,
SHOULD,
COULD.
Every day ask these typical 3 questions:

Ask yourself …

- What MUST I do today?
- What SHOULD I do?
- What COULD I do?

If you have more than three, then limit to three max.

Because it will help you focus and remember them easily.
Why Priorities Matter:

Time spent identifying your three MUSTs for the day is more than worth it because it gives you flexibility.

Without knowing your three MUSTs,
everything is mushy and you have nothing to steer by.

- Nailing your MUSTs builds a rhythm of results.
▫ Absorb what is useful.

It’s not about blindly adopting patterns and practices

It’s about taking the best of the best and tailoring it

It’s also about throwing away what doesn’t work

“Absorb what is useful,
Discard what is not,
Add what is uniquely your own.”

- Bruce Lee
▫ Focus on growth.

Push past your limits.

There are no limits.
There are only plateaus.
You must not stay there, you must go beyond them.
▫ Apply what you know.

Life is not about watching from the sidelines.

Use what you know and put knowledge into practice.

Test yourself.

Knowing is not enough, we must do it.
Willing is not enough, we must apply.
Life is wide, limitless.

There is no border, no frontier.

Life is never stagnation.

It is constant movement, unrhythmic movement, as we as constant change.
▫ The secret of Successful Developer

By focusing on effectiveness.

It’s less about figuring out the right things to do upfront and more about taking action and making course corrections based on feedback.

This is the secret behind the successful Devs.
▫ Results Over Productivity

Focus more on results.
Don’t just do more things for the sake of doing.

Instead of using efficiency as the ultimate measure of success, make it more about effectiveness, value, and impact.
▫ Avoid Task Saturation

When we’re overloaded, we make more mistakes and we perform poorly.

As task saturation increases, performance decreases; As task saturation increases, executional errors increase.
▫ Create Better Habits

The idea is simple: Spend more time giving your best where you have your best to give.

Your mission is better when you play to your strengths and create unique value, that only you can create.

Do What Makes You Come Alive.
Follow me (@TheAnkurTyagi) to watch more stories like this.

Thank you for the Twitter chats/replies over the last few months! I appreciate you all. 💙

Check out more details in an upcoming blog post here.
theankurtyagi.com

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Ankur💻🎧💪

Ankur💻🎧💪 Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @TheAnkurTyagi

27 Jun
How to Write Powerful Cold Email As a Software Engineer...

That Actually Get You:

- Job
- Sales
- Business opportunity
- Freelance contract
- Internship

A Thread...
Getting someone to respond to an ice-cold email can be tough.

In fact, maybe you’ve heard, or thought:

“Cold email is dead.

It’s SPAM!

I’ve heard these complaints a lot. But I disagree.

Everyone writes cold emails,

but who’s actually good at it?
I moved to Sweden & many other opportunities in my career, which I’ve achieved through cold email.

Just imagine:

You can get a job, build a business and reach your goals … by mastering cold email.

Fortunately, there are proven techniques to make cold email work for you!
Read 21 tweets
24 Jun
How Should I Learn Web Development?

A Thread...
As a mentor, I am constantly asked the following:

- Which programming language should I learn if I’m new?

- Which programming language is most in-demand for jobs?

- What’s the most popular programming language?
As per the 2020 StackOverflow survey,

Most Popular Technologies are like this 👇

That list is great for checking whether a particular programming language is in use today.

However, if you’re new to programming, I don’t recommend choosing a language solely based on a list.
Read 18 tweets
23 Jun
How should I work effectively as a remote employee?

A Thread...
Remote work can feel like a dream come true.

You can work from home or spend the life of a digital nomad, feel comfortable in your casual PJs and t-shirt all day.

You get to ditch commute and enjoy working from your home office or a cozy cafe.

It feels fantastic, isn’t it?
Remote work can be a way of freedom.

You just have to find your way.

Here are some tips for balancing work-life when working remotely.
Read 18 tweets
22 Jun
Some Bad Habits I Developed as a Developer...

And What I Learned From Them.

A Thread... Image
We are creatures of habit.

Habits are a powerful part of life.

There is no fixed set of habits for a programmer.

Software engineers want to be as effective as they can be, but some aren't hitting the mark.

I developed some bad habits over years of forging code.
1- Not writing tests:

Forget TDD & let's just focus on the bad habit of not writing automated tests.

The thing with writing automated tests is that while it can seem like a waste of your time or a client’s budget, the time you invest in writing a test has massive returns.
Read 14 tweets
20 Jun
A Simple and Effective way to Learn & Practice JavaScript...

A Thread...
The best way to practice JavaScript is to work on the project.

"Don't take on the Project whole at once."

Don't try to build all features at once.

Go Step by Step.
▫ Sample projects that can be done:

- ToDo List
- Music Library
- Contact/Phone Book
- Any project that involves CRUD operations.
Read 11 tweets
17 Jun
10 Mistakes You Should Never Make When Starting a New Job As a Software Developer...

A Thread...
Are you about to start a new job?

If so, by now, I’m sure at least some of that initial excitement of being offered the job has worn off and is starting to be replaced by feelings of nervousness or anxiety.

Am I right?

Well, you’re not alone.
Even for the most confident of Devs, starting a new job can be hugely nerve-wracking, and that’s completely normal.

Congratulations! You’ve finally secured a new job, and now you want to start off on the right foot, making a positive impression on your new boss and colleagues.
Read 23 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!

:(