Resilient Systems

2020-12-04 23:08:39 https://evgenii.info/faster-pacers/ Open / Comment

2020-04-13 21:56:35 https://evgenii.info/side-projects Open / Comment

2020-04-12 13:47:38 https://evgenii.info/yesterdays-weather/ Open / Comment

2020-03-24 02:26:11 https://evgenii.info/implementation-details-in-tests/ Open / Comment

2020-02-25 02:57:10 3. Don't be ashamed of your previous projects
This rule is closely related to the previous one. If you see too many issues in your projects, you may become ashamed of it, try to hide it or even destroy.

Don't do it. What is easy for you now isn't necessary easy for others. Be thankful to the results of your work –– it is something that helped you become who you are.

If you're a programmer, remember the first program you wrote. If you're a writer, remember your first essay or an article. And the second, and the tenth. I bet if you find it, you'll try to hide it as deep as possible and not show to anyone.
But I suppose you were proud when you finished it, weren't you? Why shouldn't you be proud now?
There are a lot of people who can't write it even like this. And, most importantly, this helped you to build experience: the impact of this essay on your life was way much bigger than you can imagine. Open / Comment

2020-02-25 02:56:50 2. Seek for imperfection in your work
It is a wonderful feeling when you have an idea which is perfect. It's brilliant when you implemented it and proud how you have it done.

But it should alarm you if you return to this project in some time and there is nothing to improve.

Seeing imperfection in your work is a sign of growth. Look for more of it and always challenge your projects to take more from your past experience. Open / Comment

2020-02-25 02:39:04 I want to add three more rules to it, specifically for developers. There is the first one:

Be disciplined
It is common to think that creative work (such as programming) forgives laziness and inconsistency. Rule number 5 in the article says "Work, Work, Work".
I would add "Be disciplined in planning and doing your work".

It is easy to postpone something if it requires inspiration. "I don't have enough inspiration" sounds like a reasonable excuse but it is not –– it is a big trap.

Invest in building habits that will help you beat procrastination (same time every day, time boundaries).
Create your own routines and triggers to get in the right mood (Pomodoro technique, music). Open / Comment

2020-02-25 02:23:46 Let's start from #resilient_individuals

A great way to improve your skills is to learn from professionals from different fields.
Who does something that lasts long? Well, a lot of people.

Scientists, architects, musicians - they all developed many techniques which we, software engineers, can borrow.
Let's talk about artists today.

I want to share one of my favourite articles - "How to Be an Artist, 33 rules to take you from clueless amateur to generational talent" by Jerry Saltz (@jerrysaltz on Twitter).
The article is long, but it is worth it.

There are my top-3 rules from that article:
1. Tell your own story (helps to develop a personal strategy rather than jump from one hype-train to another)
2. Start with a pencil (try to think about anything with a piece of paper and a pencil –– just start writing down completely changes the way how you think)
3. Learn to deal with rejection (from code review to job interview )

https://www.vulture.com/2018/11/jerry-saltz-how-to-be-an-artist.html Open / Comment

2020-02-25 02:02:27 This channel is about the future. About systems that live long.

What's going to be with your product tomorrow?
Will your development team be delivering value in six months?
Will you, as an individual, be competitive in the market in five years?

It's all about resilience, about doing your job well, keeping the right balance, and achieving your long-term goals.

I will explore three major topics:
1. #resilient_software - software architecture, testing, dealing with technical debt and best practices in other areas
2. #resilient_teams - building sustainable engineering teams, organization processes
3. #resilient_individuals - maintaining work-life balance, self-education, setting and achieving goals

Thank you for joining! Open / Comment