DEV Community: Alexey Migutsky

Efficient Learning Strategy

Alexey Migutsky — Mon, 16 Sep 2019 09:15:18 +0000

Originally published at our Metadevelopment blog.
Subscribe to our digest and get our free Career Hacking Starter Kit!

Two phases

There are two basic modes of learning, which are quite different in their essence. We call those “Discovery” and “Acquisition”. Both of them require a bit different approaches and environment to enhance and speed up your learning.

If you do not know exactly what you should learn, or you don’t have a specific goal, you are in a discovery mode.

If you know exactly what you need to learn, you are in an acquisition mode.

These two modes are similar in nature to diffused and focused thinking.

Discovery is a less intense and slower process than acquisition. Acquisition requires more deep work and deliberate practice than discovery.

Discovery

Discovery mode is driven by curiosity. The main goal of this mode is to enhance your outlook and broaden your understanding.

In this mode, you should get as many diverse options, opinions and ideas as possible.

The main tools for this mode are experimentation and variety of examples. Here is a great video "Making Badass Developers", highlighting the essence of experimentation and high-quality examples.

To increase diversity, it’s great to have an access to a community or environment, which facilitates knowledge sharing and expressing opinions freely. This is exactly why we have #share- and #discuss channels, as well as Skills matrix and MTDV Mindset resources.

An efficient strategy for discovery mode boils down to the following:

Surround yourself by different and diverse opinions and outlooks. Meeting and talking to different people is a good tactics here.
Spend time overviewing different mental models. Skim-read books, articles and opinions on the topic. You don’t need to dive deeper yet.
Experiment with things which look fun or interesting. Proactively try applying what you are learning and conduct thought experiments.
Seek as many examples of the topic you are interested in as possible. Look for opposing opinions and pay attention to differences in mental models.
Look into what experts on the topic say. Read bestseller books, watch talks and social media discussions.

Acquisition

Acquisition mode is driven by result orientation. The main goal of this mode is to acquire a skill or a mental model.

Feedback is crucial for progress and efficient learning. Be proactive and ask for feedback, do not wait for it. Design fast feedback loops to assess your results and progress faster. One of the best ways to create a feedback loop is to find a mentor - someone knowledgeable in the area who can lead you through complexity of the topic.

If you can, try not to learn alone. Join a group, find an accountability partner or a learning partner, find a mentor. All of these will improve your motivation, commitment and feedback loops.

An efficient strategy for acquisition mode boils down to the following:

Find a mentor, knowledgeable in the topic/skill you want to acquire. If you have an exact goal in your mind, you can find a coach. If you know just a broader topic of interest, you can find a teacher/mentor who will guide your through.
Create a routine for deep work. You will need to focus and actively apply the skill you are acquiring. You will need a time and environment for that. Plan accordingly.
Work through different high-quality examples and exercises.
Seek feedback after every unit of progress. Try not to take this feedback personally. Even if you are not succeeding as fast as you would want, it does not mean you are incapable!
Reflect on your process and progress. It’s a good idea to have some kind of metrics or measurable results which you can use to assess your progress.

At Metadevelopment, we are designing our trainings with this strategy in mind. Our methodology includes mentoring and learning routine based on commitment and accountability partnership.

Crucial Differences

There is one crucial thing you should know: you cannot be in two different modes simultaneously. If you will switch between two modes, your efficiency will drop.

On the other hand, sometimes you should switch between modes to rest. Acquisition requires a lot of resources and focus and may be quite exhaustive.

If you are in discovery mode, your goal is to figure out an exact topic/model/skill you want to acquire. This is when you can switch to acquisition mode and learn the stuff fast and efficient.

The general strategy is similar to BFS algo: first, cover the breadth of topics shallowly and then go deeper into the one you think you need to learn in details.

Do you want to grow differently? Join Metadevelopment and get new superpowers!

Is Blogging Useful?

Alexey Migutsky — Sun, 01 Sep 2019 11:15:19 +0000

This post is the answer to the question "Does blogging really help your career?" posted by Kevin Lamping here on Dev.to.

I personally would say that blogging is not directly useful for your career. But it has a lot of other benefits which make blogging a very good exercise.

The Benefits of Writing

The main benefit of blogging for me is expanding your horizon of opportunities. You can find my story below in the article. But first, let me show some benefits I've got from writing content.

It's a good way to demonstrate your expertise.

People always try to find someone they can trust. You can go through a series of interviews and hope that they will figure out you are a great colleague, or you can write about your approaches and let a wider audience know that.
If you have a deep expertise in some technology, you can demonstrate it by writing deep and thoughtful blog posts.
If this technology is in demand, you will definitely get some opportunities coming your way!
It teaches you how to structure your thoughts.

Getting into a habit of noting down your thoughts and creating an outline for an article will do you a lot of good. You will learn how to capture what you know in a concise way, so that you can recreate the whole train of thoughts just by looking at the outline you've created.
It makes your explanation skills better.

An ability to make things clear is crucial if you want to be heard and want to influence others. Additionally, you can build your own source of explanations, which you can point people to. This will come handy as soon as you start mentoring or managing other people.
It sharpen your written communication skills.

You will be communicating in a written form a lot during your career. This skills is especially important for a remote work environment, where you need to overcommunicate.
Your views expressed publicly can be a good conversation starter.

This may come handy in any professional social context: interviews, meetups, conferences. It's a different level on conversation when you get approached because someone likes your views.

My views are formed by my experience. Let me share some of my stories of how blogging has helped me. Let it be a good example for you.

How It All Have Started.

I was always bad at writing. The worst thing in school for me was writing essays. I always had a vivid imagination, but I just could not put the images into written words. I was never thinking that I would be writing texts publicly to explain myself.

It all changed when I started writing code for money. More specifically, it all started with first official half-time employment.

As many of you, I was young and in desperate need to prove that I am a good programmer. You see, I do not have a CS degree. I graduated theoretical physics, but switched to professional programming. Writing code was my passion and hobby, and I just decided to seize an opportunity to make it my job.

My first job was rather a competitive environment. I've heard a lot of talks around about "not real programmers". And I was labeled like that, because "those theoretics can never be good at something as practical as enterprise programming". So, I've decided I need to prove myself and grow my status.

One of the endorsed and acceptable ways to do that was getting access to an invite-only blogging platform for programmers (habr.ru). You could get an invitation only from someone who can endorse you, or to write a good article so that the reviewers grant you an access.

I did not have anyone around me who can share an invitation, so I've decided to go the hardest (for me) way.

I've spent around three months analysing the content on the platform, and then more than six months on writing and polishing my blog post. I've picked the topic I knew the best: writing cross-browser user scripts. It was around 10 years ago. At that time, Chrome had introduced extensions, Firefox had it's own plugin system, and other browsers can just run some stripped-down version of javascript uploaded by the user.

The article was good enough for me to get the invitation from reviewers. I've also got an additional badge proving that my content was high-quality! For me, it was a huge achievement.

Opportunities Start Coming

I've published a couple more posts just to follow up on the topic. I were not thinking at that time that this small series of content could bring me some additional benefits.

But then...

I was contacted by someone on the platform asking me to write a userscript, for money. That was a very pleasant surprise!

And little did I know that this was just a beginning. This series of content had branched off my career into freelance extension developer, which enhanced my resume with interesting cases:

I've built an automated betting bot for a small business owner. He was participating in an online-ad auction to promote his business. My solution saved him an estimated $20000 a year. Also, it was a lot of fun gaming the system 😊
I've got involved in a startup as a technical co-founder. My partner had found me only because a friend of mine has shown them my article!
We've built a price-comparison service based on a cross-browser extension. We've raised $120k of angel investments. And it was on my second year of employment. Can you imagine how hyped I was?

Unfortunately, this is not a sexy success story. Our investor was involved in some shady business, and we've got our funding halted by Russian financial police... *We could not sustain the business without that money and shut it down. In 5 years, a technical advisor who had consulted us has built and sold a similar solution for *$5M.
That was a very good and expensive lesson for me.
I am still get contacted by people asking for exntension work at least once a year. It's being 10 years since I published the articles, and they still bring me some value!

Even Rants Can Be Useful

One night, I set down to write a rant about Angular. I was working in a startup, which was heavy with UI work using Angular. Before that, I have consulted several startups on how to fix their mess with that technology. I was utterly upset about the state of industry at that time. And I just poured my thoughts into an article. (It was called "2 years with Angular". I've moved it from my personal blog to Medium, which was a bad decision in a hindsight).

I wrote the article at 2 a.m. and went to sleep. When I woke up, it was already published to HackerNews. The first day brought me 20k unique readers. The day after it has reached 65k unique readers. In three days, the article was viewed more than 120k times.

In 2 months, I started looking for a new job. The startup was going down, and I need to find my next gig.

This is when I had a series of unbelievable interviews.
They all started similar - with small talks about the code, my experience and my previous employment. But the they all went into a similar direction:

Let's talk about Angular. What do you think about the framework?

Have you read my article called "2 years with Angular" by any chance?

Wow! That was you! That's why your face is familiar to me. Yes, I've read it. I think we don't need to dive deeper in the technical interview, let's go to the next step.

😳

That was more than surprising the first time. It still felt amazing by the third interview like that!

I did not join any of those companies, though. I got a better opportunity, and it was not related to Angular article. But it was related to other articles I've published.

I was contacted by a CTO of a startup. They've told me they liked my views on software engineering and professionalism, which they've found in my blog. That was a great conversation started, and I've went to the interview loop with the company.

Foreword

This is the experience I've got first-hand. I've heard a lot of stories from other people as well.
You should keep in mind that neither my personal blog, nor my articles on other platforms were massive success. I had barely 200 subscribers in my newsletter and rss feed. But even these small numbers were influential for my career.

I am also not even close to be a good writer or communicator. I am still struggling with writing content, but I get better with every article I write. I am also not very consistent.

These days, I am writing content for Metadevelopment, and it seems a huge task for me. But I can totally see how beneficial it is, and this is what keeps me motivated.

I am also totally sure that you can get similar benefits, maybe just not in a short run. But stay consistent, and you will get your portion of success!

Increasing Your Impact

Alexey Migutsky — Wed, 28 Aug 2019 07:49:57 +0000

Originally published at our Metadevelopment blog.
Subscribe to our digest and get our free **Career Hacking Starter Kit!

One major thing which is required for your career growth is your ability to create value.

Let's talk about your impact - an amount of value created per unit of work.

I think you can easily find the relationship between impact and efficiency: the more impact you have, the higher is your efficiency.

The first principle of having a bigger impact is to focus on high-leverage activities. Remember the Pareto principle? This is exactly what you need to utilize.

Few examples of what you can do as a software developer to easily increase your impact:

Mentoring new people in your company.
There is a known fact that new employees take from 3 to 6 months to reach their normal level of productivity. In some cases it can take 2 years for an employee to reach an optimal performance.
If you can spend 1 hour a day for the first month of new hire (around 20 hours), you will spend around 1% of your annual work time (around 2000 hours) as an investment in your colleague's boosted performance. This can have a significant influence on their performance - hence providing a huge return of your time investment.
Taking part in interviewing process.
Improving the process, introducing new candidates to the company and conducting interviews are direct investments in your team and your product.
Getting great people onboard will have a huge return in a long run.
Stop reinventing the wheel and use other people's expertise.
It's better to invest your time into creating unique value rather than reinventing something which is already available. Open-source modules and components, 3rd party software, your colleagues experience and even outsourcing and freelance services are all viable options to get existing solutions faster.
Automating and optimizing the processes.
Some people say that manual repetition of work is the biggest sin of every programmer. You should not do what a machine can do for you.
A simple automation script can save several hours of team work in the long run.
If you optimize a build system and save 30 mins per day of waiting time, you will create 14 days of free time per year for a single developer. In a small team of 6 people it results in 3 man-months of additional time.
Learning and continuous self-improvement.
I will put this in bold: you should have a dedicated time at work for learning and self-improvement.
Nothing gives you the bigger impact and creates bigger leverage than investing into your abilities and available opportunities.

As you can see, the main topic (and principle) above is multiplying your efficiency by focusing on other people around you. And this is one of the major reasons why some software developers prefer to transition into management role - you can get the increased leverage faster.

Management is not the only possibility, though. The main idea is that if you want to grow past your glass ceiling you need to focus on increasing your impact.

Also, remember the second vital principle: your efforts should be visible. For example, if your boss does not know that you have mentored your colleagues and automated some mundane tasks, you won't be promoted sooner. You need to highlight your small wins and achievements and communicate the value your create.

As you can see, at some level relationships and communications become vitally important for your growth. Do not neglect those aspects and invest your time into mastering some soft skills.

Do you want to grow differently? Join Metadevelopment and get new superpowers!

DEMO Model: A Surprising Way To Be a Better Software Developer

Alexey Migutsky — Mon, 12 Aug 2019 07:22:50 +0000

Originally published at our Metadevelopment blog.
Subscribe to our digest and get our free Career Hacking Starter Kit!

You have probably seen some anonymous salary stats where there are people who earn twice and three times more than you, being at the same level as you. You may even know some people like that in your community.

Have you ever asked a question "What are they doing differently from me?" or "Why would anyone pay THAT amount of money for Javascript (Java/Go/PHP)!?"

Here is the truth: they are not doing something crazily different.

Most probably, their coding skills are quite the same you have! They just have some in-demand skills which accompany their coding skills and which they are known for.

So, what can we learn from those people and how can we level up our game?

DEMO Model

DEMO model is a handy abbreviation for a high-level set of skills:

💼 Domain Knowledge
🔧 Engineering
📢 Marketing,
👑 being Outstanding.

💼 Domain Knowledge

Domain Knowledge is very straightforward in its essence: knowing the rules of the business you are in.
You should understand how processes tick, how the rules are made, what viable strategies for your domain exist.

You should have the perspective (getting a big picture) of the business you are in.

Knowing the domain is beneficial in several ways:

It makes communications easier.
It helps to understand decision being made by "business people".
It helps to predict how the system may scale and change.

Business is a system. All things your create as a Developer exist withing this system and therefore are affected by it's rules.

If you have never thought about business as a system, there is a great book to introduce you to this concept: "E-Myth Revisited".

🔧 Engineering

In general, Engineering is creating systems with predictable systematic effects. Those effects are what people eventually pay for.

In our context, Engineering consists of:

Code construction.
System design.
Maintenance and Operation.
Security.
Usability.
and more...

Most programmers focus too much on code construction. New frameworks, best practices, OOP vs Functional languages - those topics do not matter as much.

If you find yourself focusing on code, you are missing a bigger picture:
We are paid not for producing well-crafted code. We are paid for solving problems with technologies.

Engineering is the most obvious part of DEMO model. Nevertheless, developers too often ignore "unrelated" part of the craft. Do not do that - expand your fundamental knowledge.

📢 Marketing

Marketing is the most negligible part of DEMO model. But marketing is the activity which multiply value your create.

Marketing is making people who need your app or service know that this solution exists.

Knowing marketing will help you to answer these questions:

How and Why people are buying your product or service?
Who are those people?
How do you get in touch with them?
Why do we need to ship some feature before specified deadline?
Why most people focus on features?

If you need an introduction to marketing, start with "Crossing the Chasm". This book is a bible of high-tech marketing.

👑 Being Outstanding

How can you be outstanding?
Ther are a lot of ways to do that, but most important things are that:

You work results should be visible. You need to learn how to talk about your results and surface hard-to-evaluate things. Teaching other people to solve the same problems is a very good way too.
You should be recognizable among your colleagues. Lending a helping hand often helps with that. As well as proactively taking responsibilities for cross-cutting things on the project.
You should be known outside your work for your specialization. Ideally, you want to be known among decision-makers (CEO/CTO/Hiring Managers/Business Owners) for your ability to solve problems with technologies. At the very least you need to be publicly recognizablein your professional community. This is where public speaking and networking help a lot.

All in all, being Outstanding boils down to Communication skills. One profound read that has completely changed my vision of being an effective engineer is this study from Bell Labs. It is considered an essential reading for Metadevelopment members.

How to Put This Knowledge Into Practice?

First, it's a good idea to make a basic self-assessment to understand how do you fit into the model. Answer this questions:

How much do I know about the business I am in?
What aspects of Engineering am I familiar with? Which aspects do I consciously use in my day-to-day work?
Do I really understand why people buy the product/service we are building?
Do people around know that I have that knowledge? Is it visible and understandable from my CV?

Second, make a plan on how to improve in the areas where you do not have much knowledge.
Start with the essential reading mentioned above. Find people who know more than you and learn from them.

Third and most important - put your new knowledge in practice!

Do you want to grow differently? Join Metadevelopment and get new superpowers!

One Simple Model To Help You Measure Your Growth

Alexey Migutsky — Sat, 03 Aug 2019 07:43:37 +0000

Originally published at our Patreon blog.
Subscribe to our digest and get our free Career Hacking Starter Kit!

There is one thing people are always missing when they start engineering their life. This thing is a good metric system. How do you measure and estimate your progress? What values do you need to optimize when you are making decisions?

For this exact case we suggest using TEMS model.

TEMS is an abbreviation for a group of resources:

Time ⏱
Energy ⚡️
Money 💰
Social Connectedness 👨‍👩‍👧‍👦

Time

Time is the most precious resource in your life, just because you cannot get more personal time. You can, though, exchange other resources for other people's time.

Your personal time has very peculiar properties:

It feels like there is never enough time
Time resource is depleting naturally
Sense of time is very unique between different people and cultures
Time and attention are two things your closest people will always value more than anything else.

Energy

Energy characterises your will-power, internal motivation, attention, ability to focus and general well-being. Also, you can think of Energy as a measure for health and stress recovery capacity.

Energy and Time comprises your basic resources for personal efficiency. Throughout your life you will convert your Energy and Time into other things and experiences. Energy and Time defines how many interests you can pursue and how many joys you can get from life.

Money

Money is the easiest to measure and easiest to convert resource. Money has a direct physical representation - you can see it and touch it.

This is why money is often used as a substitute measure to all other things: happiness (rich == happy), influence (rich == influential), well-being (rich == has more free time).

This is a very misleading frame of reference, though. Money can not buy all of those things.

Social Connectedness

Social Connectedness is the most underestimated and valuable resource. As human beings, we are born social. Our happiness depends on socialising and feeling love and acceptance.

Your Social Connectedness comprises of two main categories: friends & relatives and people you can benefit from (colleagues, employees, professional contacts). Both categories require your attention and time so that you can benefit from them.

A Secret of Success

All four resources are convertible: you can convert, for example, Time and Energy into Money and Social Connectedness.

If you are using TEMS model, then success will look like balancing and increasing all resources at once, as opposed to exchanging one resource for another.

Here is an example.

Imagine, you've got a great opportunity to work in an industry-leading startup. You know that they are eager to give a good value of options and their exit is kinda obvious for you.
The problem is that they will demand overtimes and a lot of mental activity from you - pushing the boundaries and learning cutting-edge stuff.

You tried to estimate the TEMS balance:

You can totally see that this opportunity will give you a lot of Money in 5 years, but will deplete your Time and Energy. Hopefully, you will be able to retain your Social Connectedness (meeting friends and relatives, keeping in touch with colleagues and industry pros).

Would you take this opportunity?

Would you take an opportunity to join a company where you will get less Money, but more free Time and freedom to meet people and network?

How does your latest job-related or home-related decisions map to this model?

Do you want to grow differently? Join Metadevelopment and get new superpowers!

How To Improve Your Thinking In One Step

Alexey Migutsky — Wed, 24 Jul 2019 17:02:01 +0000

Originally published at our Metadevelopment blog.
Subscribe to our digest and get our free Career Hacking Starter Kit!

Models are simplifications and abstractions of some patterns in the world or some parts of the system.We all think in models, be it consciously or unconsciously.

A better way of thinking is to transform your implicit models into explicit models and being able to control them. By controlling, I mean the ability to change the model and to apply the model in the fitting context.

To highlight the importance of models, we usually highlight these ideas:

Mental models are the essence of human thinking process. We all have some "thought structures" and "fundamental rules" in our heads that define our world view and mindset.
The essence of efficient communications is your ability to identify and peruse the mental models of your communication partner.
The most efficient learning happens when you can grasp and learn the superior mental models of your mentor.

A better way of thinking is to transform your implicit models into explicit models and being able to control them.

Why do we use models?

Our brain can not effectively hold and manipulate a big number of details. But we want to be able to understand, explain and predict the world around us.

There is one problem with all models: they are all wrong. Simple models can be useful without being "right," in an engineering sense.

The thing is: you do not need to have a perfect model to be able to use it (to make decisions or take actions based on the model).

The manifestation of models in Software Engineering is architecture and, obviously, business modelling. Those are two essential modelling skills you will need to acquire to grow over the level of mediocrity of our craft.

What is the difference between models and why you may choose one over another?

I would say that the best model for you is one that you can understand and use for making decisions and taking actions. Learning a new or a different model will enhance your resolution - your ability to see world in meaningful details.

An example of such differences in models is ShuHaRi and Dreyfus Model of Skill Acquisition. Both models describe how people learn new skills. ShuHaRi is older and more simplistic, but it still captures the essence of getting skills: a novice needs a set of rules to follow to get results, while a master needs a deeper philosophy and principles to enhance his mastery.

If you want to dive deeper in mental models, I would recommend taking this basics course. There is also a course on Coursera introducing you to some math-backed models. And here is a huge list of useful mental models.

If you want to see some mental models which are closer to our career, check this article.

Why are we talking about models at all?

At Metadevelopment we will learn and introduce several models which will help you to become a better software engineer and a better lifestyle engineer.

Internally, we are using ShuHaRi and Dreyfus models to design the courses and make your learning simpler. The whole idea of Metadevelopment is based on crowdsourcing and helping each other to learn more efficiently.

We will talk about models a lot. You should understand that most of those models are not profound objective truth. They are just tools, applicable in various contexts and situations. But learning those ideas and seeing them from various sides will develop your critical and analytical thinking. Practicing and experimenting will open up new possibilities and better understanding of yourself.

Do you want to grow differently? Join Metadevelopment and get new superpowers!

A Hidden Side of Procrastination

Alexey Migutsky — Thu, 18 Jul 2019 13:54:19 +0000

Originally published at our Metadevelopment blog.
If you'd like to receive fresh content from our community, you can sing up for our Newsletter!

Very often, the essence of laziness, procrastination and lack of determination are our fears and limiting beliefs. The chance that your are not really lazy is quite high.

The biggest blocker in achieving things we want is not that we are lazy or having low willpower or having no time. The biggest blockers are our fears and our limiting beliefs.

Beliefs

Our beliefs seems to influence a lot of things:

Beliefs affect motivation.
Beliefs affect stress.
Beliefs affect our self-control.
Beliefs affect our potential to learn and change (Growth Mindset).

A self-limiting belief is something that you assume to be true that is limiting your progress. It can be manifested in a negative self-talk or pessimistic views on the world. Some examples are: “I can not earn more, because this number is a glass ceiling in our industry”, “people like me can not be entrepreneurs”, “I was always told I am bad at math, and hence I am bad programmer”.

Most of our beliefs are things we hold to be facts without any active verification from our side.
The good thing is that beliefs can be changed. A nice explanation of changing the attitude by reframing your beliefs can be found in a book called Learned Optimism. One more great source is a book called Feeling Good: The New Mood Therapy, which is the best first step to start with cognitive behavior therapy on your own.

Fears

Our fears do similar things: they prevent us from doing things we want.
The problem with fears is that they lie and that they are evasive.

A fear can be very subtle and can result in seemingly unrelated behavior - you watch a series instead of writing an article you've been thinking about the whole day. Why? Because you are afraid that this article won't be perfect. People won't like it. It's not good enough. It was not even written yet, but it is already not good enough!

Our brains is very bad as estimating possibilities and probabilities, especially the adversary conditions - when something can go wrongs.
Fears are what make us risk-averse and make us skip opportunities we are totally can harness.

Addressing the fears can help not just you, but also a bigger entity - a team.

What can you do about that?

First, there is a huge, but controversial idea: believe not what's true, but what's helpful. Even superstitions can be helpful.
Second, deliberately take small non-ideal steps instead of jumping into huge ambitious projects. Change does not happen instantly and in big amounts. It’s actually quite opposite: the more efforts you put into change, the bigger is the resistance.

Third, face your fears by stepping out of comfort zone. For example, take on rejection challenge to face your fear of rejection and see how it feels.

In general, start questioning your beliefs by conducting experiments to verify them.

A good starting point for working with beliefs and self-knowledge is Mark Manson’s Self-Knowledge guide.

Do you want to grow differently? Join Metadevelopment and get new superpowers!

How to Balance Your Work and Your Life

Alexey Migutsky — Thu, 11 Jul 2019 17:22:32 +0000

Originally published at our Metadevelopment blog.
If you'd like to receive fresh content from our community, you can sing up for our Newsletter!

At Metadevelopment, we put a big focus on your personal life and sustainability of work-life balance. We do not think that your career and life are separate entities.

You work is influencing your happiness and well-being the same way as your general lifestyle.

We are focusing on mindset and actions. There are several things you can do to start balancing your life.

1️⃣ Start working with your wishes and wants.
You need a reference point to measure importance of various life aspects. The questions is: what problems do you want to solve yourself and what problems are not essential?

2️⃣ Start figuring out your values, purpose or mission.
At the very least, thinking about your mission and experimenting with your lifestyle and work to find your purpose will give you a general direction and motivation in your life. Start by reading a book called “The 7 Habits of Highly Effective People”.

3️⃣ Learn some basics about happiness.
Taking this course is highly recommended! It is evidence-based and contemporary and won’t take you much time. If you want to dive deeper, read “Solving for Happy”.

4️⃣ Figure out your relationships with control and lack of control.
You can’t control much things in life: environment, weather, other people thoughts.
You can't even control your emotions, but you can control your behaviors - your response to emotions.
Stoicism philosophy is a great example of long-lasting mindset based around lack of control and constant change of the world. “A Guide To The Good Life” is a great book to have an overview of stoic principles and ways to apply then in the modern life.

5️⃣ Take responsibility for your own Balance.
As soon as you realize that you are ultimately responsible for everything that happens to you, your life will start changing. It is very important to take care of yourself.

If you do not prioritise your life, someone else will.
- Essentialism. Greg McKeown

Essentialism is a good mindset to start taking control and responsibility of your life and figure out right priorities. Taking responsibility is based around making choices and being OK with the consequences.

6️⃣ Start doing some experiments and challenges to figure out your fears and limiting beliefs.
Your procrastination and idealism are heavily tied to your fears. Your subconscious brain hides some information from you based on your fears. You are missing opportunities around you because of your fears.

7️⃣ Start consciously choosing actions and non-actions.
You need to commit to doing something as well as to commit to not doing something.
The thing is - you have already chosen non-action in some aspects of your life, you just have done it unconsciously.

8️⃣ Start designing your personal unique lifestyle based on your values, commitments and wishes.
Consciously choosing your ambitions and setting right expectations from the surrounding reality is a key for a sustainable life. Probing the reality and enhancing your mental models is the only pragmatic attitude to growth and self-actualization.

Do you want to grow differently? Join Metadevelopment and get new superpowers!

Pursuit of Productivity

Alexey Migutsky — Fri, 05 Jul 2019 17:33:12 +0000

Originally published at our Metadevelopment blog.
If you'd like to receive fresh content from our community, you can sing up for our Newsletter!

Our world has gone crazy about Productivity. There are thousands of to-do apps in app stores and everyone wanna be as much productive as possible. I bet you know what I am talking exactly. The roots of this issue can be found in protestant work ethics.

We misinterpret and simplify productivity: we think it is measured by how much do you produce or how busy you are with several projects in parallel.

Also, people resort to being busy when they lack clarity and purpose of their work (you can read about this effect in a great book called "Essentialism").

Historically, a studying of productivity was bounded to factories producing physical goods. This analogy is very tempting. But we are knowledge workers and not factory workers. We do not produce the same way as factories does, though on a high level the work flow can be managed in a similar way. Our motivation is different from other types of work.

At Metadevelopment, we prefer a definition of productivity given in Trello productivity guide : "making sure you’re getting the right things done, in the right timeframe, in a successful and effective way".

This definition incorporates priorities, efficiency and timeliness of your projects.

Here is the crux: optimizing for productivity can be harmful! Here is a good example of an over-productive system. And here is a good explanation of how boredom can make you more creative.

Productivity and Software Engineering

It is very easy to get into the trap of optimizing for productivity when you treat yourself as a production unit or misinterpret "high performance".
Also, it's very easy to become a productivity junky if your only job is to just write code without questions asked.

Along with out intuition to pursue productivity, we are neglecting other effects and factors we need to be aware of as engineers:

Network effect (the more people are using your product - the more valuable it is)
Sustainability (enhancing the current situation without doing harm for the future situation)
Human Factors (taking in account safety, comfort, human error)
Social Influence (affecting a person’s emotions, opinions and behaviors)
Cognitive Biases (systematic pattern of deviation from norm or rationality in judgment)
Applied Ethics (the analysis of particular moral issues in private and public life)

Software Engineering is an application of systematic, disciplined, quantifiable approach to development, operation and maintenance of software (IEEE90 definition).

As an engineer, you can have an impact in every area of product development cycle. Why would you care only about being productive coder if you can be an efficient engineer?

Do you want to grow differently? Join Metadevelopment and get new superpowers!

Work Misperception

Alexey Migutsky — Fri, 28 Jun 2019 15:22:10 +0000

Originally published at our Metadevelopment blog.
This is the first article from our Introduction series.
If you'd like to receive fresh content from our community, you can sing up for our Newsletter!

The basics

Many Software Developers have a strange perception of their work, formed under the influence of their employers, colleagues and industry culture, treating their work as a competition with their colleagues.

Many managers have an even stranger perception, treating people as machines on an assembly line, trying to optimize the performance of the business system without understanding the human factor, fundamentals of knowledge work and software product development in general.

Many people are wondering, whether software development is an art, craft or engineering. Or a combination of all those aspects.

Also, there is a tendency to ban the word “career”, as if it is something dirty, political and unethical. Building your career is not the way to make more money. It is a way to empower you so that you can make what you really want.

At Metadevelopment, we try not to differentiate between work and life. Our work is an essential part of life. We came into Software Development because we want to create, build and enhance the world around us. Some people indeed have come to this industry just for money. Most of them have discovered that Software Development is a creative and empowering endeavor.

First and foremost, Software Engineering is a knowledge work. Our main capital is knowledge. We spend substantial time searching for information and learning new things. We use critical and creative thinking to solve problems. We experience the state of flow. We require mastery, autonomy, and purpose for day-to-day motivation.

Second, Software Engineering is a cross-disciplinary subject, including at least technologies, science, psychology, sociology and ethics.

Third, Software Engineering is tightly coupled to business and business systems. We work within businesses and with business systems, but we often neglect these relationships.

Software Engineering and Business

There is a huge, but barely noticeable misfit between business and software development. Business wants to identify and solve real-world problems for real people. Most developers want to solve hard challenges using cool technologies.

Those two worlds do not always overlap.

There are a lot of resources and studies to figure out success, efficiency, and impact of software projects. Individual efficiency is always linked to project success and team performance. It's not enough to be productive and single-handedly produce high-quality solutions for problems. It's also necessary to solve the right problems and enable others (including your future-self) to easily change the solution in the future.

If you want to become an expert in your field and help other people you need to learn how to identify and solve real-world problems using technologies and collaborating with other people.

It means you need to understand both engineering and business at the end of the day.

Focus on Development

Many developers think that it’s enough to be able to just build software from scratch. What they are missing is a bigger picture.

There is a definition of Software Engineering from IEEE90: “Software Engineering is an application of the systematic, disciplined, quantifiable approach to development, operation and maintenance of software.”

Notice the highlighted words: development, operation and maintenance. This is what you are expected to do as a software engineer.

At Metadevelopment, we differentiate four levels of professional maturity: programmer, developer, engineer and entrepreneur. We have a model of required skills for all those levels.

Programmer is a solo creator capable of delivering a working app. Developer is a team player, capable of working in an enterprise environment and building parts of the bigger system. Engineer is a systems maintainer, capable of analyzing complex environments and non-technical factors to make systems sustainable. Entrepreneur is an opportunity identifier, working with business systems on a high strategical level.

Focus on Hard Skills

At the beginning of our careers, we spend the most time and focus on getting hard skills: debugging, code construction, systems design, requirements analysis, etc.

It’s only natural that we start thinking that there is nothing more important in our industry than hard skills.

But this is not quite true! There are studies showing that “Star Performers” are differentiated from normal workers on criteria different from hard skills!

Here is an interesting test for you. It will show your attitude towards the performance of software engineers. It has just 12 questions. You can easily answer those in 5 minutes.

How many statements out of this 12 are true:

Star performers are born, not made.
Star performers are smarter than average performers (have higher IQs, are better problem solvers, or are more creative).
Star performers are more driven and ambitious than others.
Star performers have more leadership skills than others.
Clean desk people are more likely to be star performers than messy desk people.
Detailed time management and organizational systems are the keys to high productivity.
Star performers work longer hours and harder than average performers.
Star performers are more satisfied with their jobs than average performers.
Star performers are successful primarily because they play organizational politics and give slick presentations to upper management.
Minorities and women can seldom be as productive as people who are part of the "old boy" network.
People cannot sustain a doubled rate of productivity improvement for long time periods.
I would rather have a team with one star performer supported by four average performers than a team with five performers who are all in the top 5 percent.

Ok, so what is your answer?

Now, the revelation: neither of those statements are true!
We can totally understand your skepticism on that.

This is why we suggest you to read a research-based brochure called “STAR Engineer”. Over a thousand engineers from Bell Laboratories, 3M, and Hewlett-Packard contributed to the original research as both collaborators and subjects.
There is a similar study for managers called “Project Oxygen”.

This two studies may totally change your perception of Software Engineering. It totally has changed our mindset, and now we want to spread those ideas. Stay tuned and we will share our thoughts on productivity, career, lifestyle, work-life balance and personal growth.

Do you want to grow differently? Join Metadevelopment and get new superpowers!