<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Marios Fakiolas on Medium]]></title>
        <description><![CDATA[Stories by Marios Fakiolas on Medium]]></description>
        <link>https://medium.com/@fakiolinho?source=rss-7d7a3c2f65a0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*69Va57n4NcLtgE6Egna7kw.jpeg</url>
            <title>Stories by Marios Fakiolas on Medium</title>
            <link>https://medium.com/@fakiolinho?source=rss-7d7a3c2f65a0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 20:20:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@fakiolinho/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Our team is our actual boss]]></title>
            <link>https://medium.com/@fakiolinho/our-team-is-our-actual-boss-11903e38897b?source=rss-7d7a3c2f65a0------2</link>
            <guid isPermaLink="false">https://medium.com/p/11903e38897b</guid>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Marios Fakiolas]]></dc:creator>
            <pubDate>Mon, 30 May 2022 08:42:00 GMT</pubDate>
            <atom:updated>2022-05-30T08:42:00.922Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*W4vIMbrdJA6_Oo9NXmElVQ.png" /></figure><p>Hiring in technology is mostly hard-skill oriented because it is actually easier to check engineers’ experience in ReactJS for example compared with their kindness or their trustworthiness.</p><h3>Can we really trust you?</h3><p>Are you a passionate individual? Do you care for the quality and the result of your work? Are you doing the minimum possible just to survive? Can we rely on you?</p><p>Can you lift the team on your shoulders when needed? Can you be kind and gentle to your peers day in and day out? Can you be there for them once they ask for your help? Can you be fun and “easy to work with” whenever they come across you?</p><h3>The unfortunate leap of faith</h3><p>Of course, there is a turn towards soft-skills evaluation during the hiring procedure by tech organizations but let’s be honest, all this is definitely a leap of faith still since we mostly rely on our gut feeling.</p><p>Unfortunately, this leap of faith is the main reason why many new hires tend to quit or even get fired in the first 3–6 months.</p><p>Why? Because they don’t blend well with their team.</p><h3>Our teammates’ evaluation</h3><p>Peers and subordinates are the first to judge newcomers’ personalities and actual skillset on the battlefield.</p><p>They work together right from the very start so if they spot collaboration and communication flaws they are the very first who will pay attention and will raise a flag.</p><p>All this, way before the line manager grasps the mismatch.</p><blockquote>Our team is our actual boss.</blockquote><h3>Conclusion</h3><p>We should realize that our teammates know better than anyone our actual impact on the team.</p><p>If we want to thrive we should focus on our team’s goals, our teammates’ needs, and the way we collaborate with them.</p><p>No one wants to work with brilliant jerks. Do you? I bet not. Cheers!!</p><blockquote>Brilliant jerks are “difficult to work with” people with very strong hard skills.</blockquote><p><em>Originally published at </em><a href="https://mariosfakiolas.com/blog/easy-to-work-with">https://mariosfakiolas.com/blog/easy-to-work-with</a><em> on May 29, 2022.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11903e38897b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t let coaching turn into babysitting]]></title>
            <link>https://medium.com/@fakiolinho/dont-let-coaching-turn-into-babysitting-e41b29b601ea?source=rss-7d7a3c2f65a0------2</link>
            <guid isPermaLink="false">https://medium.com/p/e41b29b601ea</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[mentoring]]></category>
            <category><![CDATA[coaching]]></category>
            <dc:creator><![CDATA[Marios Fakiolas]]></dc:creator>
            <pubDate>Sun, 01 May 2022 19:49:25 GMT</pubDate>
            <atom:updated>2022-05-01T19:50:02.610Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*9dDYuSyiO2g9uz3T1amcwQ.jpeg" /></figure><p>Do you remember the time you learnt how to ride a bike or a skateboard during your childhood? How many times did you fall, and then you had to swallow your pride and retry? I bet more than a dozen, right?</p><p>Did you stop trying because of your bruised knees or your muddy hands? Did you stop because of the laughs and the teasing of your friends? Definitely not!!</p><h3>An efficient coaching lesson</h3><p>Your family tried to show you the way by adding supporting wheels, and then they removed them. They held your hand at first, and then they let you move alone. So you fell.</p><p>No matter what happened, they clapped their hands while trying to cheer you up, so you kept on trying.</p><p>And then you decided to try alone early in the morning or late in the night, without anyone watching, so they see you the next day and say: “Bravo, you ‘ve made it”!!</p><p>All these failed attempts motivated you even more and pushed you to try harder. They taught you a bunch of new things and forced you to improve.</p><p>You worked your ass to make it happen, and eventually you ‘ve made it. But then again you fell and you rised, and you fell a couple more times and at some point you stopped counting. You stopped falling. Success!! It tasted good, right?</p><blockquote>Accomplishing goals tastes good after a hell of an effort</blockquote><p>Your confidence increased, so then you decided to push your limits by learning how to swim or doing back-flips with your skate or even learning a new technology or becoming a team lead or starting your own business or getting married or becoming a parent and so on.</p><p>Challenges never stop. That’s called life.</p><h3>Coaching today</h3><p>Nowadays coaching and mentoring are in high demand in the fast-paced tech world. Organizations invest in young or less experienced people with potential, to help them grow and develop their talents.</p><p>In fact, the ability to learn and develop new skills, tends to become one of the most critical factors that might affect a candidate’s decision to pick or reject an organization’s offer.</p><h3>Efficient coaching</h3><p>If we want coaching to succeed, we should not forget that young kid with the bruised knees, the dirty hands and the strong will. This is a great lesson we all learnt at a very young age, and it worked pretty well.</p><p>Efficient coaching is supposed to let people fall sometimes too. Coaching should prevent us from breaking a leg but should let us bruise a knee.</p><p>Falling is ok. Falling is actually required, so we learn how to rise. Preventing us from falling, is actually extremely harmful since it doesn’t teach us what are our weaknesses or what things we have to change and improve.</p><p>Not falling is against the empirical way of mastering new skills. This is extremely counter-productive when it comes to coaching and mentoring.</p><h3>Conclusion</h3><p>In order to make coaching successful, both sides should not confuse coaching with babysitting. Infants need our constant support to almost anything, so they survive. Coaching is all about growing through and not about surviving.</p><p>If we want to grow, we should ask for guidance and room to make mistakes, so we collect battle-tested experiences.</p><p>A professional environment where we can make mistakes and get wiser through them, is a healthy environment that makes us feel trusted.</p><p>Feeling trusted will motivate us to show up and bring the best version of ourselves every day in order to climb a higher mountain or go one mile further than yesterday. This is what coaching is all about.</p><blockquote>Coaching is all about getting motivated to believe into ourselves and find the way to exceed our own limits and weaknesses, in order to achieve our high goals</blockquote><p>That said, efficient coaching demands room to fall and rise, again and again. Cheers!!</p><p><em>Originally published at </em><a href="https://mariosfakiolas.com/blog/coaching-and-babysitting"><em>https://mariosfakiolas.com</em></a><em> on Feb 09, 2022.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e41b29b601ea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Startups thrive so does depression rates]]></title>
            <link>https://medium.com/@fakiolinho/startups-thrive-so-does-depression-rates-ad35f2c48d77?source=rss-7d7a3c2f65a0------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad35f2c48d77</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[human-resources]]></category>
            <dc:creator><![CDATA[Marios Fakiolas]]></dc:creator>
            <pubDate>Sat, 05 Feb 2022 14:20:56 GMT</pubDate>
            <atom:updated>2022-02-05T14:23:09.578Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Q9REeLsu-5a-nvHXW9f8rg.jpeg" /></figure><p>Tech world runs with the speed of light at the moment but on the flip side depression rates are skyrocketing. Mental fatigue and loneliness is everywhere and we cannot ignore it.</p><h3>The digital transformation era</h3><p>Covid-19 has played a significant role in all this technology big bang since a bunch of business sectors realized they have to embrace new technologies to reach new markets while an increasing number of organizations decided to invest and make a bold step towards digital transformation to improve and modernize their services.</p><p>With all these opportunities, money seems to flow, right? We are in a golden tech era. God saves technology!!</p><h3>Career success doesn’t necessarily mean less loneliness</h3><p>Unfortunately though, various <a href="https://www.neurologyadvisor.com/topics/neurobehavioral-disorders/global-rates-of-depressive-and-anxiety-disorders-increased-during-the-pandemic/">researches</a> prove that people struggle hugely because of reduced mobility and increased loneliness during the last 3 years. Tech people included. These findings were associated with increased rates of major depressive disorder and stress.</p><p>More money in the bank account or more opportunities on LinkedIn don’t necessarily mean better quality of life and actual work-life balance nowadays.</p><blockquote>Career success cannot heal all wounds and that’s a fact.</blockquote><h3>Constant change scares people</h3><p>It worths to be mentioned also that a fast-paced ecosystem with constant changes, new goals, bigger clients, higher rates, new releases, tighter deadlines and so on is something that scares people. And this is normal.</p><p>Leaders who show the way and push organizations limits might feel excited about new opportunities ahead but the teams that will deliver the actual work down the road, might feel overwhelmed instead.</p><p>Most people tend to feel lost when things move rapidly, so they try to find their own way through the evolution storm. Change is scary.</p><p>Feeling stressed and anxious, when business goes well, is a sign of weakness and vulnerability in our society. People tend to hide these feelings and swallow their pride, so they don’t get thrown out of the bus. Pretending leads to loneliness though.</p><h3>Conclusion</h3><p>That said, the current situation in tech world is that tech businesses and startups are thriving and technology people are struggling to get through on a personal level.</p><p>All this is something the leaders of the tech world should not ignore because the most important asset of an organization is its people after all and these people keep on having a rather hard time for some time now.</p><p>This is something we cannot overlook and should not confuse with compensations, benefits and promotions.</p><p>Deep inside we are all human beings and some needs we have cannot be covered by our careers success.</p><p>Let’s help our people by giving them the attention they deserve.</p><p>Let’s all fight loneliness together. Cheers!!</p><p><em>Originally published at </em><a href="https://mariosfakiolas.com/blog/startups-thrive-so-does-depression"><em>https://mariosfakiolas.com</em></a><em> on Feb 05, 2022.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad35f2c48d77" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Relax, not being a senior engineer is totally fine]]></title>
            <link>https://medium.com/@fakiolinho/relax-not-being-a-senior-engineer-is-totally-fine-8eaf1bd3130a?source=rss-7d7a3c2f65a0------2</link>
            <guid isPermaLink="false">https://medium.com/p/8eaf1bd3130a</guid>
            <category><![CDATA[seniors]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Marios Fakiolas]]></dc:creator>
            <pubDate>Wed, 27 May 2020 00:00:00 GMT</pubDate>
            <atom:updated>2020-06-02T13:00:14.346Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*ZDZup5qGbF2t_OtH.jpg" /><figcaption>Photo by <a href="https://unsplash.com/@vnedit?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">M Angie Salazar</a> on <a href="https://unsplash.com/s/photos/peacock?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>We live in the seniors&#39; era and that’s a fact. It might sound a bit crazy or even funny but it is more than accurate. Engineers want to be seniors or at least use this term somehow in their social profiles, their laptops, their desks, etc. Why? Because it is a click-bait and makes them feel cool and successful.</p><h3>Should we blame the engineers for this?</h3><p>No, we don’t. We should not forget that the engineers are trying to make a living out of this, so they need to remain attractive in a pretty demanding market. Who would pay attention to a peacock without shinning feathers, right? Probably very few people.</p><p>I suppose it starts making sense now 🤔</p><h3>What is the companies&#39; influence on this trend?</h3><p>Huge!! Why? Because everyone is searching loudly for seniors and very few are looking for impactful persons. It is like picking a book by paying more attention to its cover and not to its actual content.</p><p>Apart from that, innumerous companies out there offer the seniority title to people they don’t deserve it in order to become an attractive destination. That way the seniority title is part of the compensation the engineers get. Unfortunately, this pattern confuses less experienced developers since too many people end up being called seniors 😬</p><p>Last but not least, the managerial effort and the experience needed to help some people to grow and evolve internally is huge. Most companies seem to miss such skillful people that can influence others and guide them correctly, so they prefer to go out there and use the senior bait to attract some talent.</p><h3>Who should be considered a senior engineer?</h3><p>A senior engineer is not a person who knows N programming languages, N frameworks, and N libraries. Definitely not.</p><p>It is a highly impactful person who helps a team of people to fulfill the firm’s goals. Simple as that.</p><p>Senior engineers:</p><ul><li>think more about the We and not about I</li><li>care about surrounding developers and try to help them evolve and flourish</li><li>have made more mistakes in the past than most of their colleagues, so they have much more battle-tested knowledge</li><li>love simplicity and readability and hate complexity</li><li>strive for maintainability and try to predict design flaws and potential bottlenecks early enough</li><li>know that technologies evolve, so they have learned how to adapt to changes</li><li>appreciate more the things that add real value to a product and not fancy libraries and technologies</li><li>are willing to listen to other people ideas and opinions in order to reach the optimal outcome</li><li>share experiences, thoughts, and ideas which actually improve the end-product</li><li>play a vital role when it comes about architectural decisions and technologies selection</li></ul><h3>How can I become a senior engineer then?</h3><p>By becoming a decent junior engineer first. This is by far the most important role in engineering.</p><p>Why? Because we learn how to think and behave during our first steps and this is probably a mindset we should build and follow throughout our career.</p><p>Guess what this means: junior role is actually a huge and crucial step towards seniority.</p><p>Junior engineers:</p><ul><li>should be thirsty for knowledge and feedback</li><li>should keep an eye on technologies evolution</li><li>should establish a studying pattern and figure out how they can learn easier</li><li>should not be opinionated else this attitude is blocking their actual evolution</li><li>should understand that all this is a monster they cannot tame since it is getting stronger every day, so they need to make peace with this</li><li>should never be afraid to ask about the whys and the hows</li><li>should learn how to make the right questions</li><li>should establish some good habits</li><li>should make lots of mistakes and get the most out of them</li></ul><h3>Are these virtues of a senior engineer too?</h3><p>They definitely are. Senior engineers possess all these skills, but they have learned throughout the years how to evaluate and prioritize them correctly and how to behave for each occasion accordingly.</p><p>It is all about experience and impact after all.</p><h3>Hmm, not being a senior is cool then?</h3><p>Of course. It is totally normal not being a senior. Don’t let titles to get into your head.</p><p>As we saw, the junior and senior roles are tightly connected. People tend to underestimate the non-senior titles which is an awful mistake. All roles have a meaning, and the lowest rank is the most important one since it defines our DNA under the hood.</p><p>Work hard and make some impact. Seniority will eventually meet you down the road. A so-called senior engineer might not be always an impactful one, but an impactful engineer is definitely a senior one and that’s a fact. Don’t lose your sleep with titles. Real value is all that matters. Cheers!!</p><p><em>Originally published at </em><a href="https://mariosfakiolas.com/blog/relax-not-being-a-senior-engineer-is-totally-fine"><em>https://mariosfakiolas.com</em></a><em> on May 27, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8eaf1bd3130a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Offload some burden from your brain and boost your productivity]]></title>
            <link>https://medium.com/state-of-progress/offload-some-burden-from-your-brain-and-boost-your-productivity-ecbd3d66fb9e?source=rss-7d7a3c2f65a0------2</link>
            <guid isPermaLink="false">https://medium.com/p/ecbd3d66fb9e</guid>
            <category><![CDATA[stay-focused]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[goal-setting]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Marios Fakiolas]]></dc:creator>
            <pubDate>Wed, 24 Jul 2019 20:35:02 GMT</pubDate>
            <atom:updated>2019-07-24T20:53:56.165Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*djzVlyVpW_v0ijdnmZv8XA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@artic_studios?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Daniel Hjalmarsson</a> on <a href="https://unsplash.com/search/photos/brain?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I ‘ve been asked a lot by colleagues and friends about the way I manage to stay focused and productive in the long run. This is a really tough question and I am sure that people out there use a great variety of techniques to accomplish this. Personally speaking, I follow a dead simple pattern.</p><p>Every night I spend a couple of minutes writing down all these things I need to deal with the day after. Some times I write down about ideas I have or even books and articles I would like to read in the near future. It’s like taking a backup and offloading some great volume of thoughts, tasks and ideas to an external storage. That’s it.</p><p>Simple? No matter how simple it seems, I have to admit that I spent some time till I figure this out and make it work.</p><p>How did I start doing so then? The reason was “awful sleep” due to stress probably. There were times in the past I couldn’t sleep that well or even I couldn’t really go to deep sleep while in bed for more than 1-2 hours.</p><p>Why? Tons of stuff were crossing my mind and I couldn’t control them. I couldn’t make them stop somehow or at least pause them for a while. This was killing me.</p><p>Sometimes I was thinking again and again about a technical problem I wanted to solve or about a super-urgent task I had to tackle right after getting to work in the next morning.</p><p>Many engineers tend to think about technical problems before getting to sleep. Unfortunately this is a harmful habit that forces lots of them to become night owls.</p><p>Having a bad sleep is a huge obstacle that prevents us from being productive. Since we make a living out of solving technical problems and algorithms then we definitely need to take care of this and provide some rest to our brain.</p><p>Don’t get mistaken, our brain is not tireless. We are human beings after all with certain limits.</p><p>To get back to my story, obviously this was quite exhausting for me so I had to find a way to leave my mind in piece and give it some room to breathe.</p><p>I started using a small notebook at first. It was like a brainstorm but really soon I realised how beneficial all this really was. My sleep improved a ton so my mood and my concentration improved also by far.</p><p>Finally, I could find some inner-peace and sleep tight because all these notes proved to be the glue between working days. I stopped being afraid about missing some key details or forgetting things and I was confident that I was about to continue from the exact point I stopped the previous day. Everything was already written down in the backup storage so I could access them easily in the next morning for further processing 🤓</p><p>Recently I decided to start keeping a daily journal and take notes of my inner thoughts and experiences in order to learn the most of them. Why not right?</p><p>Life is out there so as long as we stay healthy and energetic, all these ideas, dreams, goals and tasks will be waiting for us to fulfil them. So keep track of them and let your brain rest regularly because you really need it in an excellent shape. Cheers!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ecbd3d66fb9e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/state-of-progress/offload-some-burden-from-your-brain-and-boost-your-productivity-ecbd3d66fb9e">Offload some burden from your brain and boost your productivity</a> was originally published in <a href="https://medium.com/state-of-progress">State of Progress</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React.StrictMode can help us modernise big production applications]]></title>
            <link>https://medium.com/state-of-progress/react-strictmode-can-help-us-modernise-big-production-applications-90ac77299e74?source=rss-7d7a3c2f65a0------2</link>
            <guid isPermaLink="false">https://medium.com/p/90ac77299e74</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[react-hook]]></category>
            <dc:creator><![CDATA[Marios Fakiolas]]></dc:creator>
            <pubDate>Sun, 14 Jul 2019 13:25:29 GMT</pubDate>
            <atom:updated>2019-07-14T13:25:29.321Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hK_Y0DWvpFcT01FFtUp7fQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/8Gg2Ne_uTcM?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">贝莉儿 NG</a> on <a href="https://unsplash.com/search/photos/build?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>In 2019 <a href="https://reactjs.org/">React</a> is moving fast to concurrent rendering era. This change will be a massive boost for client-side apps and will help frontend engineers to tackle slow performance bottlenecks.</p><p>If you want to hear more about concurrent rendering in React check this awesome pitch about it here:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FByBPyMBTzM0%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DByBPyMBTzM0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FByBPyMBTzM0%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/73aca4e550df466b7cfb0b51b75acce6/href">https://medium.com/media/73aca4e550df466b7cfb0b51b75acce6/href</a></iframe><p>That said, concurrent rendering is the holy-grail and the ultimate vision of the React team but in order to reach there many things need to change first. During the last 6 months we have been witnessing some really big api changes in React 16 and lately we welcomed <a href="https://reactjs.org/docs/hooks-state.html#hooks-and-function-components">React hooks</a> in the frontend world.</p><p>Other changes before this were:</p><ul><li>React Fragments</li><li>new refs and context apis</li><li>findDOMNode got deprecated</li><li>changes for lifecycle methods</li><li>introduction of getDerivedStateFromProps , getSnapshotBeforeUpdate and componentDidCatch</li><li>announcement that some hooks like componentWillReceiveProps and componentWillMount are considered error-prone so they will be highlighted as unsafe in the upcoming versions of the library</li><li>of course React hooks and many many more…</li></ul><p>I know these sound like brand new toys in the hands of a little child for most of us and this is the hungry developer speaking inside me. So what are we doing if we need to make some decisions as tech leads and architects? How do we approach all these massive changes? What plan do we have to follow if we need to upgrade safely our applications without postponing their roadmap? Tough questions right?</p><p>There is not a silver bullet here. The only think I ‘ve learnt all these years is to stay proactive and move forward with careful steps trying to maintain a balance. We definitely need to embrace all these new features and make the most out of new React versions but we don’t have to go crazy.</p><h4>React.StrictMode</h4><p>Thankfully, React team has taken care of that too so with <a href="https://reactjs.org/docs/strict-mode.html">StrictMode</a> we can maintain stability for huge codebases while upgrading small parts in steps.</p><p>StrictMode is a tool for highlighting potential problems in an application. It won’t render anything but it will throw a bunch of errors in console when it finds some issues for the children components.</p><p>Errors will look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aCljZPQJff2xa1AUwumA4w.png" /></figure><p>We can easily wrap the whole app with it. This approach might be ok for small codebases:</p><pre>ReactDOM.render(<br>  &lt;React.StrictMode&gt;<br>    &lt;App /&gt;<br>  &lt;/React.StrictMode&gt;,<br>  document.getElementById(&#39;root&#39;),<br>);</pre><p>Of course, this is definitely not the best way to take advantage of it in large applications. Obviously, the console is going to get crazy. Especially if we are using it while trying to upgrade an older React version to v16.</p><p>In that case, I highly recommend to use it carefully in specific parts or even components of the codebase so you can upgrade them in steps:</p><pre>&lt;React.StrictMode&gt;<br>  &lt;MyComponent /&gt;<br>&lt;/React.StrictMode&gt;</pre><h4>Potential issues we will spot easily</h4><p>Some issues we expect to spot with React.StrictMode:</p><ul><li><a href="https://reactjs.org/docs/strict-mode.html#identifying-unsafe-lifecycles">Identifying components with unsafe lifecycles</a></li><li><a href="https://reactjs.org/docs/strict-mode.html#warning-about-legacy-string-ref-api-usage">Warning about legacy string ref API usage</a></li><li><a href="https://reactjs.org/docs/strict-mode.html#warning-about-deprecated-finddomnode-usage">Warning about deprecated findDOMNode usage</a></li><li><a href="https://reactjs.org/docs/strict-mode.html#detecting-unexpected-side-effects">Detecting unexpected side effects</a></li><li><a href="https://reactjs.org/docs/strict-mode.html#detecting-legacy-context-api">Detecting legacy context API</a></li></ul><p>Be aware that this will also throw errors for all the 3d party libraries used by the components you are trying to upgrade. Some times this is even more important so you check if all these 3d party libraries are following React progress. Maybe this will be an indication that some of them are not maintained at all. If this is the case, then I suppose it is about time to get rid of them or maybe start contributing to them or even fork them.</p><h4>Code that runs twice in development mode</h4><p>React.StrictMode, in order to be efficient and avoid potential problems by any side-effects, needs to trigger some methods and lifecycle hooks twice. These are:</p><ul><li>Class component constructor method</li><li>The render method</li><li>setState updater functions (the first argument)</li><li>The static getDerivedStateFromProps lifecycle</li><li>React.useState function</li></ul><p>It is important to know that React.StrictMode doesn’t run in production mode so you don’t need to worry about all these double runs at all.</p><h4>Conclusion</h4><p>React 16 has tons of goodies that can help us into writing safer and more robust code and provide definitely even more business value in the end-product. Concurrent rendering is on its way and we definitely want to stay on track.</p><p>By definition, it is wrong to upgrade a client-side application in one big step especially if we are talking about a really big codebase that needs some great amount of time and involves a humongous team effort. React.StrictMode is provided so we can move to the modern era of React by upgrading our components in steps with confidence while adding new features and business value to our product. Cheers!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90ac77299e74" width="1" height="1" alt=""><hr><p><a href="https://medium.com/state-of-progress/react-strictmode-can-help-us-modernise-big-production-applications-90ac77299e74">React.StrictMode can help us modernise big production applications</a> was originally published in <a href="https://medium.com/state-of-progress">State of Progress</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The business value of React Hooks is huge]]></title>
            <link>https://medium.com/state-of-progress/the-business-value-of-react-hooks-is-huge-4f657d77488d?source=rss-7d7a3c2f65a0------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f657d77488d</guid>
            <category><![CDATA[react-hook]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Marios Fakiolas]]></dc:creator>
            <pubDate>Sun, 14 Jul 2019 13:23:04 GMT</pubDate>
            <atom:updated>2019-07-14T13:49:12.670Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Photo by Marcello Gennari on Unsplash" src="https://cdn-images-1.medium.com/max/1024/1*PkDYEyA0QXXJzHy67h558A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@marcello54?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Marcello Gennari</a> on <a href="https://unsplash.com/search/photos/legos?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>React Hooks were officially released in February of 2019 and since then the frontend world has started changing rapidly. Other popular JavaScript frameworks such as <a href="https://vuejs.org/">VueJS</a> are moving also to a more functional approach as we can see <a href="https://github.com/vuejs/rfcs/blob/function-apis/active-rfcs/0000-function-api.md">here</a> so the future seems bright for Hooks.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fdpw9EHDh2bM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Ddpw9EHDh2bM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fdpw9EHDh2bM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/ad70d92540011512f84156a5f5c802a0/href">https://medium.com/media/ad70d92540011512f84156a5f5c802a0/href</a></iframe><h4>What are Hooks?</h4><p>Hooks are simple functions which have specific input and output.</p><p>This is a dead simple Hook we can use to handle forms with controlled inputs across all our applications:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R2zhPEV1o_31Hjx8KiRRSQ.png" /><figcaption>Custom React Hook useForm</figcaption></figure><p>Here is the form that uses this custom useForm hook:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cdn8T4RADNsOLdt0maxX7g.png" /><figcaption>React component that uses custom Hook useForm</figcaption></figure><p>Under the hood closures are used so things become much more straightforward without the need of <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes">ES6 classes</a> and the super-evil this keyword in JavaScript.</p><p><a href="https://reactjs.org/docs/hooks-intro.html">Introducing Hooks - React</a></p><h4>Why Hooks?</h4><p>With Hooks we can share logic with ease across our components, our applications and our teams and this is where they are nailing it.</p><p>Before Hooks era, we had to use more complex patterns like <a href="https://reactjs.org/docs/higher-order-components.html">HOCs</a> and <a href="https://reactjs.org/docs/render-props.html">render props</a>. These patterns helped us to re-use logic across our components but we had difficulties in debugging and maintaining them.</p><p>The end-result was a little unreadable as we can see below since we had to mix markup with logic (render props):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*95Ar4vVA3I3v37oZTLjZyQ.png" /><figcaption>React component with render props pattern</figcaption></figure><p>Because of this mixture, they introduced extra components in the components tree and this made things really ugly in big codebases and complex web applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/978/1*rctVGznNcukjUHGnHvYgow.png" /><figcaption>Extra FormHandler component in the components tree</figcaption></figure><p>Testing also was a nightmare since we had to dive deep in components tree to spot the one we wanted to tweak with <a href="https://airbnb.io/enzyme/">Enzyme’s</a> shallow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/974/1*qoqyHAS0-T74wAazxYEm3w.png" /><figcaption>Diving deep with Enzyme’s shallow</figcaption></figure><p>Hooks help us to write more readable and maintainable code as we saw above because we can distinguish the logic from the layout entirely.</p><p>The end result is much cleaner since we don’t have anymore garbage components in the components tree:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*Uci4FUukwXuP7R7DSONhKw.png" /><figcaption>No need for extra components because of React Hooks</figcaption></figure><p>For testing we can simplify our tests a lot by using <a href="https://testing-library.com/docs/react-testing-library/intro">react-testing-library</a> which encourages writing tests that use our components as the end users do and avoid all this craziness with deep dives with Enzyme shallow testing or the side effects with Enzyme mount testing.</p><p><a href="https://reactjs.org/docs/hooks-faq.html#how-to-test-components-that-use-hooks">Hooks FAQ - React</a></p><h4>Hooks for ui-kits</h4><p>It is quite common for big organisations which use React to create ui kits with presentational components in order to build web applications faster and help their teams to move forward with less constraints.</p><p>Some great examples are <a href="https://polaris.shopify.com/">Shopify’s Polaris</a> , <a href="https://react-fabric.github.io/">Microsoft’s Fabric</a> and many more.</p><p>React Hooks make this process a lot easier since we can rely on function components to build a rock solid ui-kit.</p><h4>Hooks for utilities libraries</h4><p>Apart from collections of presentational components, we can now build collections of utility methods with Hooks. That way we can stop re-inventing the wheel and rely on existing pieces of logic when building a Minimum Viable Product or a brand new feature.</p><p>Some examples can be pagination, forms handling and validation, smart editors, vertical auto-scrolling, localStorage management and many more.</p><p>Below you can find tons of nifty open source React hooks:</p><p><a href="https://nikgraf.github.io/react-hooks/">Collection of React Hooks</a></p><h4>Re-usable components give us speed and stability</h4><p>From UI / UX perspective the value of having re-usable components is really huge. It demands both developers and designers to be involved so this helps us to avoid UI / UX inconsistencies.</p><p>Also the designers learn to think in terms of reusability and <a href="http://atomicdesign.bradfrost.com/chapter-2/">atomic design</a> some more.</p><p>Last but not least, the teams design much more before delivering a component and this is quite beneficial down the road since we avoid big iterations and long refactoring cycles.</p><h4>New / Junior engineers can accelerate faster</h4><p>Re-usable components help also new team members or less experienced engineers to accelerate and become valuable members of the team which is something really difficult to achieve when talking about big codebases and complex web applications.</p><p>Apart from that, these components are definitely a great guide to demonstrate how we should structure our code, what conventions and best practices we use as a team, what is the company’s styleguide and so on.</p><h4>Conclusion</h4><p>React Hooks are quite fresh but their impact upon the Frontend world is really huge. We can now rely on simple functions to build collections of reusable function components and share small pieces of logic across our applications and our teams easily.</p><p>Business-wise this is really important because we can build faster new features or even brand new web applications. The teams can communicate smoothly because of them and the code we use to achieve this is much simpler and easier to understand and maintain.</p><p>These are some key-points in order to scale and React Hooks definitely help us to accomplish this. Cheers!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f657d77488d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/state-of-progress/the-business-value-of-react-hooks-is-huge-4f657d77488d">The business value of React Hooks is huge</a> was originally published in <a href="https://medium.com/state-of-progress">State of Progress</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Consistency is the key]]></title>
            <link>https://medium.com/state-of-progress/consistency-is-the-key-24131cc38bf7?source=rss-7d7a3c2f65a0------2</link>
            <guid isPermaLink="false">https://medium.com/p/24131cc38bf7</guid>
            <category><![CDATA[consistency]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[health]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[goal-setting]]></category>
            <dc:creator><![CDATA[Marios Fakiolas]]></dc:creator>
            <pubDate>Sun, 14 Jul 2019 10:00:26 GMT</pubDate>
            <atom:updated>2019-07-14T13:44:52.987Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Photo by Jametlene Reskp on Unsplash" src="https://cdn-images-1.medium.com/max/1024/1*ArT1Fi7YsHGVPph7gwJ0Sw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@reskp?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jametlene Reskp</a> on <a href="https://unsplash.com/search/photos/key?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Consistency can easily become our friend or our foe. Being consistent is extremely hard but this is what it keeps us away from fulfilling our goals and our dreams eventually. Who said that this is easy right?</p><p>Recently I ‘ve managed to lose 15 kg so I couldn’t be more proud of myself right now. You know what was the key to achieve this? Consistency.</p><p>I make a living out of software engineering and management which is quite harmful for my shape. We are talking about lots of hours sitting in front of a monitor on a daily basis. Weekends included. Moving rarely throughout the day is deadly for our body.</p><p>The whole set-up literally starts falling apart after doing this for some years or so. That kind of consistency obviously has some awful results.</p><p>So how did I manage to fix this? By introducing and sticking to some good habits:</p><ul><li>Exercise twice a week with a personal trainer who comes at home early in the morning so that I cannot escape from this 😬</li><li>Stop being a night owl which is something that most engineers tend to do</li><li>Eat dinner at 19.30pm and never after 21.00pm. Greeks tend to eat really late</li><li>Hire a specialist to help me fix my diet and arrange a weekly session to measure my weight. She comes at home early in the morning so that I cannot escape from this too 😁</li><li>Realise that I have to spend some more for all these and stick to my plan to make it work</li></ul><p>…and it worked!!!</p><p>So I started exercising 8 months ago, then I fixed my daily schedule and when I get used to these changes I went on a diet. This happened 4 months ago and since then I ‘ve lost 15kgs.</p><p>Every session has been held on specific day and hour for months. It was tough at first but I got used to it because it became part of my routine.</p><p>Tons of gyms out there offer deals where we can buy a cheap subscription for a year and visit them whenever we like. You know what? I ‘ve tried this and it never worked. After 1–2 weeks I started finding excuses related with my workload. I have a call, I have a deadline, I have sooo much work to do. I ‘ll go tomorrow or the day after and so on. Going to the gym 2–3 times per month is not real training. We need to stay persistent here.</p><p>Since I ‘ve tried this in the past, I didn’t want to repeat the same mistakes. I scheduled them really early in the morning before getting to work so I don’t find silly excuses as time goes by and it really worked.</p><p>All these take place at home so the cost obviously is a little higher. You know what? My health is far more precious so I really thought about it like a real investment. In order to achieve my goal I had to stop searching for excuses. And this was the time I finally did it 😉</p><p>I was consistent as hell and it worked. Νow I am in a shape I couldn’t even imagine 1 year ago. Using the stairs is not a nightmare anymore.</p><p>The funny thing is that I am even better at work, full of energy and passion to push forward all these projects I run and make them blossom. How cool right?</p><p>So consistency is the key to success and failure. Stop finding excuses. They won’t get you anywhere. You know who you are and what are your weaknesses. We are human beings and this it totally normal. You need to overcome them with bold decisions. Stay consistent and you ‘ll make it work. Trust me. Cheers!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24131cc38bf7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/state-of-progress/consistency-is-the-key-24131cc38bf7">Consistency is the key</a> was originally published in <a href="https://medium.com/state-of-progress">State of Progress</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The biggest lies about React Hooks]]></title>
            <link>https://medium.com/state-of-progress/the-biggest-lies-about-react-hooks-29aa306e354f?source=rss-7d7a3c2f65a0------2</link>
            <guid isPermaLink="false">https://medium.com/p/29aa306e354f</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[hooks]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Marios Fakiolas]]></dc:creator>
            <pubDate>Thu, 11 Apr 2019 18:30:28 GMT</pubDate>
            <atom:updated>2019-04-11T18:30:28.436Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aIIRntdw2stBWukYPGJg8Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/4K2lIP0zc_k?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Ben White</a> on <a href="https://unsplash.com/search/photos/laughing?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I tend to listen and read really a lot about the meaning of React Hooks and how they help us to win the fight against evil classes that tend to pollute our codebase and blah blah blah. So guess what? This is a big lie.</p><pre>import React, { useState } from &#39;react&#39;;<br><br>function Toggler() {<br>  // Declare an &quot;on&quot; state variable and a method to toggle it :)<br>  const [on, setOn] = useState(false);<br><br>  return (<br>    &lt;button onClick={() =&gt; setOn(on =&gt; !on)}&gt;<br>      {on ? &#39;ON&#39; : &#39;OFF&#39;}<br>    &lt;/button&gt;<br>  );<br>}</pre><h4>Why Hooks?</h4><p>Hooks were not invented to kill classes. Hooks became part of our toolset so we can create and share small, re-usable and maintainable pieces of logic in our applications without nesting some more into the components tree. No <a href="https://reactjs.org/docs/react-without-es6.html#mixins">mixins</a>, no <a href="https://reactjs.org/docs/higher-order-components.html">higher-order</a> components, no <a href="https://reactjs.org/docs/render-props.html">render props</a> craziness. Just <a href="https://reactjs.org/docs/hooks-intro.html">Hooks</a> 😉</p><h4>Ok but what about classes?</h4><p>To be honest, the problem that Hooks solve is much more important than dropping classes but we cannot ignore the big change that was introduced regarding their usage.</p><p>They are definitely not required anymore to provide some magic and this is a remarkable fact, but this is just a nice consequence with the new API.</p><p>This is why the React team has officially declared that classes are not dropped or something and new versions will keep on supporting them.</p><p>From React <a href="https://reactjs.org/docs/hooks-faq.html#do-i-need-to-rewrite-all-my-class-components">webpage</a>:</p><blockquote>There are <a href="https://reactjs.org/docs/hooks-intro.html#gradual-adoption-strategy">no plans</a> to remove classes from React — we all need to keep shipping products and can’t afford rewrites. We recommend trying Hooks in new code.</blockquote><h4>So I can drop classes for good right?</h4><p>Nope, you can’t. There are still some cases where you need classes. So far lifecycle hooks, like <a href="https://reactjs.org/docs/react-component.html#componentdidcatch">componentDidCatch</a> and <a href="https://reactjs.org/docs/react-component.html#getsnapshotbeforeupdate">getSnapshotBeforeUpdate</a> are not supported by Hooks so if you really need these goodies you have to go with classes API. These are said to become part of the Hooks API really soon.</p><p>Apart from that, classes play nicely with Hooks in the components tree, but you cannot use a Hook inside a class and this might force you to create a couple more classes down the road 😬.</p><h4>Cool, so what do I choose?</h4><p>Go with Hooks of course for your new components, since they make it easier to share logic while using simple functions. As we discussed above, classes might be needed in some occasions and this is pretty normal.</p><p>From React <a href="https://reactjs.org/docs/hooks-faq.html#do-i-need-to-rewrite-all-my-class-components">webpage</a>:</p><blockquote>In the longer term, we expect Hooks to be the primary way people write React components.</blockquote><h4>Render props and HOCs are not relevant anymore?</h4><p>Hmm, no they still are. You can definitely keep on using them and even combine them with Hooks in your components so you can implement progressive enhancement. There is nothing that prohibits this, but Hooks of course will help you to simplify your components without all the extra nesting that these patterns introduce by definition.</p><p>From React <a href="https://reactjs.org/docs/hooks-faq.html#do-hooks-replace-render-props-and-higher-order-components">webpage</a>:</p><blockquote>There is still a place for both patterns…But in most cases, Hooks will be sufficient and can help reduce nesting in your tree.</blockquote><h4>Do I have to test my components in a different way?</h4><p>Hmm, that is a really good question. Of course not, but if your tests are error-prone by using let’s say the component’s instance (sorry enzyme 🤓), then you definitely need to refactor them.</p><p>From React <a href="https://reactjs.org/docs/hooks-faq.html#how-to-test-components-that-use-hooks">webpage</a>:</p><blockquote>From React’s point of view, a component using Hooks is just a regular component. If your testing solution doesn’t rely on React internals, testing components with Hooks shouldn’t be different from how you normally test components.</blockquote><p>Nevertheless, there are some things you should be aware of, regarding tooling and instrumentation for your tests.</p><p>React offers <a href="https://reactjs.org/docs/test-utils.html#act">ReactTestUtils.act()</a> to test our components but <a href="https://airbnb.io/enzyme/">enzyme</a> <a href="https://github.com/airbnb/enzyme/issues/2011">doesn’t support</a> Hooks testing entirely at the very moment while <a href="https://github.com/kentcdodds/react-testing-library">react-testing-library</a> does. This might be an issue for you especially if you are not aware of the latter. Also this might be a ringing bell about the plan you are going to follow regarding Hooks in general.</p><p>React team promotes <a href="https://github.com/kentcdodds/react-testing-library">react-testing-library</a> usage directly in the Hooks <a href="https://reactjs.org/docs/hooks-faq.html#how-to-test-components-that-use-hooks">docs</a> as a best practice.</p><p>From React <a href="https://reactjs.org/docs/hooks-faq.html#how-to-test-components-that-use-hooks">webpage</a>:</p><blockquote>To reduce the boilerplate, we recommend using <a href="https://git.io/react-testing-library">react-testing-library</a> which is designed to encourage writing tests that use your components as the end users do.</blockquote><pre>it(&#39;can render and update Toggler&#39;, () =&gt; {<br>  // Test first render and componentDidMount<br>  act(() =&gt; {<br>    ReactDOM.render(&lt;Toggler /&gt;, container);<br>  });<br>  const button = container.querySelector(&#39;button&#39;);<br>  expect(button.textContent).toBe(&#39;OFF&#39;);<br><br>  // Test second render and componentDidUpdate<br>  act(() =&gt; {<br>    button.dispatchEvent(new MouseEvent(&#39;click&#39;, {bubbles: true}));<br>  });<br>  expect(button.textContent).toBe(&#39;ON&#39;);<br>});</pre><h4>Conclusion</h4><p>Don’t get crazy about the non-existing battle between Hooks and classes. We need both of them at the very moment to ship a robust client-side application in production and that is all that matters.</p><p>Embrace Hooks and start using them for the right reasons by simplifying your applications codebase and making it much more readable and maintainable.</p><p>Last but not least, it is a great time to start playing around with react-testing-library and get rid of some sins and bad practices of the past. Cheers!!</p><p>Did you enjoy this article? Don’t forget to hit 💚 to share some love and check our next workshop on <a href="https://2hog.codes/workshops/2019-05-18-react-hooks-fundamentals/">React Hooks</a>!</p><p><a href="https://2hog.codes/workshops/2019-05-18-react-hooks-fundamentals/">React Hooks fundamentals</a></p><p>If you found this interesting, you can follow me on Twitter at <a href="https://twitter.com/fakiolinho">@fakiolinho</a>. Check out some of my other articles below:</p><ul><li><a href="https://stateofprogress.blog/people-love-remote-working-but-only-few-really-fit-in-this-model-271ec02949ba">People love remote working but only few really fit in this model</a></li><li><a href="https://stateofprogress.blog/code-reviewing-why-it-is-so-important-5f2b3e49c75c">Code reviewing: why it is so important?</a></li><li><a href="https://medium.com/@fakiolinho/fight-psychological-fatigue-in-software-development-d830df872891">Fight psychological fatigue in software development</a></li><li><a href="https://medium.com/@fakiolinho/javascript-engineers-stop-ruining-your-own-interviews-35b25163c036">JavaScript engineers, stop ruining your own interviews</a></li><li><a href="https://medium.com/@fakiolinho/how-to-become-a-rockstar-web-designer-from-the-eyes-of-a-developer-3f3ceee5ea7a">How to become a rockstar web designer from the eyes of a developer</a></li><li><a href="https://medium.com/@fakiolinho/boost-your-remote-teams-performance-as-a-team-s-leader-88df95976c86">Boost Your Remote Team’s Performance as a Team’s Leader</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29aa306e354f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/state-of-progress/the-biggest-lies-about-react-hooks-29aa306e354f">The biggest lies about React Hooks</a> was originally published in <a href="https://medium.com/state-of-progress">State of Progress</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[People love remote working but only few really fit in this model]]></title>
            <link>https://medium.com/state-of-progress/people-love-remote-working-but-only-few-really-fit-in-this-model-271ec02949ba?source=rss-7d7a3c2f65a0------2</link>
            <guid isPermaLink="false">https://medium.com/p/271ec02949ba</guid>
            <category><![CDATA[team]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Marios Fakiolas]]></dc:creator>
            <pubDate>Sun, 24 Feb 2019 13:16:07 GMT</pubDate>
            <atom:updated>2019-02-24T20:03:29.255Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rU6KNs9KfdROiENL-UQTNA.jpeg" /></figure><p>In 2019 even more and more companies are willing to hire remote employees in order to attract the best possible talent and reduce office costs. On the other hand people seek for new career opportunities worldwide because of this option. That said remote working flourishes and everyone wants to take advantage of this.</p><p>So where is the pitfall? Is there any tricky part in this model? According to my own experience, there is definitely one big problem and people tend to ignore it. Few people can really work and be productive while working remotely. This includes both remote and in-house employees who belong in the same team and eventually should cooperate and make things work.</p><p>Think about it. Can everyone work remotely? Can everyone co-work with a remote colleague? Given that they have the technical and business skills. Do you believe that they have the proper mentality, mindset and personality to support this relationship?</p><p>I have worked remotely for quite a few years and I can definitely declare that too many people cannot support this. Most tend to overwork themselves heavily and reach to burnout. Burnouts hurt people and their firms even more. Unfortunately, there is also a small amount of people who tend to take advantage of remote working by taking shortcuts, skipping procedures and eventually letting their colleagues down.</p><p>So how can we describe the ideal remote workers? What skills should they possess?</p><h4>Strong communication skills</h4><p>Every employee should have great communication skills but remote ones should be really awesome at it. Since they are working remotely the communication obstacle is the most difficult one they should tackle. If they manage to communicate effectively with their colleagues, this relationship is meant to become successful.</p><p>Furthermore in cross-country teams all employees should be able to use English fluently. That’s definitely a key factor. I ‘ve seen people who wanted to get hired for a remote opening despite their mediocre English. This is a skill every remote worker should have mastered first else they cannot really communicate effectively with other people on the other side of the line.</p><h4>Legendary writers</h4><p>Obviously all remote workers communicate with their colleagues mostly through writing and not through speaking. This involves exchanging written messages through emails, slack, skype, jira, github, gitlab, code reviews etc throughout the day. Believe it or not, every little word or emoji matters in these messages. Don’t be too strict and try to be more explanatory. Words can confuse and definitely hurt people so become super-picky.</p><p>You can write sth like “Ok…” and the person on the other side can interpret this in a various ways. What do these dots really mean? Do they mean the same for you two? Hmmm, they probably do not, so stick with a simple “Ok”. Don’t send ambiguous messages. They can be really harmful.</p><p>Always take the extra step to explain something as detailed as possible. Share your thoughts with specific examples, provide snippets, make proposals, create wireframes and mockups and don’t hesitate to arrange a call to make things even more clear.</p><h4>Enjoy personal interactions</h4><p>We tend to overlook it but remote workers have little to none visual interactions with their colleagues. This means that we should better pay real attention to these few occasions. This can be a scrum call, a meeting, a sprint’s retrospective or a 1–1 catch up. Dress well and open the camera. Smile to the people on the other side of the screen.</p><p>They need to see your face more than you realise since they barely see you. Yes they know your avatar or your username but they are not familiar with your real image as much as you may think. This affects people so don’t hide yourself and don’t avoid wearing your favourite sweater. Show them that you are a friendly person and they can count on you. If you want them to take you seriously, you have to make it easier to them by paying attention to all these tiny details.</p><h4>Friendly persons</h4><p>Let’s face it. A remote colleague is a totally unknown person, so everyone may feel a little awkward at first. It is in our nature to be defensive. No matter how professional we are, we don’t really want to get exposed so we try to be cautious till we feel comfortable enough. This is a long process and takes more than a day or a month. How can we speed things up? By being super-friendly right from the very start.</p><p>Being polite and say “Thank you” a lot can help a ton. It is cheap. Showing gratitude to your colleagues for making great things together will prove your friendliness. They will love it and foremost they will start relying on you. Remember how difficult is to trust someone especially when we are talking about a person we barely know.</p><h4>Self-motivated</h4><p>There are many people out there who need to get managed or coached regularly in order to be productive. A nod from their manager or a nice word from a colleague can give them a boost. People are social beings so thats totally normal.</p><p>Remote employees work mostly alone so there is no-one there to give them a push. They need to stay focused and push themselves on their own to get shit done. This is really difficult to achieve and can cause great frustration in the long run.</p><h4>Disciplined</h4><p>Given that many remote employees work from home, using their living room’s sofa or whatever, do you think that all these people are mentally mature enough to stay focused and follow a daily schedule? Definitely not.</p><p>Above every employee lies the team itself, so everyone who belongs in it, including the remote employees, should follow their teams schedule religiously. This probably means that they have to be online in a specific time-slot on a daily basis, attend scrums and planning meetings and communicate with their colleagues constantly. Going offline for 1 hour out of a sudden doesn’t really help this professional relationship to be successful.</p><p>I ‘ve seen people coming up with all kind of crazy excuses just to skip a standup or a call. No-one cares why a remote employee missed a meeting as long as they weren’t there. The team definitely required his presence but he wanted to skip it for his own reasons. This looks pretty disrespectful. So the 1 million dollars question here is “Does he really feel part of the team”?</p><h4>Strong team players</h4><p>Remote worker should definitely be strong team players. They should strive to prove themselves valuable by sharing their experience and knowledge and affecting the rest of team members in a positive way. They should be persons who care a lot about it.</p><p>By definition they work alone in their own space far away from other team members or even company’s headquarters. This doesn’t mean that they should not be part of teams decisions and procedures.</p><p>Remote employees are equal members of a team so they should be active and energetic. I ‘ve seen people setting low standards for their contribution in teams decisions and planning because they think that doing so it’s ok since they are physically far away from team’s core. That’s so wrong.</p><p>Don’t be mistaken, no-one said that working remotely means you have less responsibilities or you are the weakest member of the team. On the contrary, people working remote are mostly hired for their exceptional talents.</p><h4>Conclusion</h4><p>Remote employees should be team-players with high communication skills and awesome writing ones. They should understand that in order to build a tight bond with their colleagues they should really work hard for it and prove themselves valuable to them by sharing knowledge, ideas and experiences. They should take part in all team’s procedures and decisions and never avoid doing so by taking advantage of their remoteness.</p><p>Working remotely doesn’t mean that they should follow their own schedule instead of their team’s. The cost of having brilliant jerks is humongous and can really ruin a team’s spirit. That’s why remote employees should get hired really carefully.</p><p>A remote worker is a person with some great advantages but even more responsibilities and this is something we should not overlook. Cheers!!</p><p>If you found this interesting, you can follow me on Twitter at <a href="https://twitter.com/fakiolinho">@fakiolinho</a>. Check out some of my other articles below:</p><ul><li><a href="https://stateofprogress.blog/code-reviewing-why-it-is-so-important-5f2b3e49c75c">Code reviewing: why it is so important?</a></li><li><a href="https://medium.com/@fakiolinho/fight-psychological-fatigue-in-software-development-d830df872891">Fight psychological fatigue in software development</a></li><li><a href="https://medium.com/@fakiolinho/javascript-engineers-stop-ruining-your-own-interviews-35b25163c036">JavaScript engineers, stop ruining your own interviews</a></li><li><a href="https://medium.com/@fakiolinho/how-to-become-a-rockstar-web-designer-from-the-eyes-of-a-developer-3f3ceee5ea7a">How to become a rockstar web designer from the eyes of a developer</a></li><li><a href="https://medium.com/@fakiolinho/boost-your-remote-teams-performance-as-a-team-s-leader-88df95976c86">Boost Your Remote Team’s Performance as a Team’s Leader</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=271ec02949ba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/state-of-progress/people-love-remote-working-but-only-few-really-fit-in-this-model-271ec02949ba">People love remote working but only few really fit in this model</a> was originally published in <a href="https://medium.com/state-of-progress">State of Progress</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>