<?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 Alex Lobera on Medium]]></title>
        <description><![CDATA[Stories by Alex Lobera on Medium]]></description>
        <link>https://medium.com/@alexlobera?source=rss-d71a82789a1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*QYw78d1dQdVjee2Dfhq7xA.png</url>
            <title>Stories by Alex Lobera on Medium</title>
            <link>https://medium.com/@alexlobera?source=rss-d71a82789a1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 05:04:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alexlobera/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[How Do CTOs Approach Private Dev Training & Upskilling?]]></title>
            <link>https://medium.com/react-graphql-academy/how-do-ctos-approach-private-dev-training-upskilling-5a81164d7836?source=rss-d71a82789a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a81164d7836</guid>
            <category><![CDATA[upskilling]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[edutech]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[Alex Lobera]]></dc:creator>
            <pubDate>Wed, 12 Aug 2020 07:53:33 GMT</pubDate>
            <atom:updated>2020-10-20T21:10:02.151Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lQunDwvn9z2M184t" /></figure><h3>We interviewed ClosedWon CTO, Dennis Zelada. Find out how he approaches dev training and how he upskills his team in this exclusive interview!</h3><p>We’ve interviewed quite a few of our past students, each with their own unique story to tell. But there’s one job role we haven’t heard from in a while: the CTO.</p><p>To gain a fuller understanding of what goes through a CTOs mind when they look for, plan and approve private dev training, we interviewed <a href="https://www.linkedin.com/in/denniszelada/">Dennis Zelada, CTO at ClosedWon</a>. If you’re a CTO or head of department, or if you’re looking to request further training from your senior manager, his insights will shine a light on what C-level execs think about dev training!</p><h3>Keeping the Tech Stack Up-to-Date</h3><p>We started our interview by asking Dennis about his role, his responsibilities, and how he makes sure his company stays at the forefront of innovation. For Dennis, the answer is simple: needs and behaviours.</p><p>Throughout the interview, Dennis returned time and again to the idea that needs and behaviours must drive all strategic planning within your organisation. That’s just as relevant for keeping the tech stack up-to-date as it is for approving new training budgets.</p><p>Although Dennis used to manage a team of 98 people, he now manages a much smaller team of under ten. Of course, that means how he works has changed. Working in a smaller team has meant that Dennis has had to code more than he once did, but this has brought him closer to the needs of the business and the services he and his team are creating. Now, he is able to bring his wider knowledge of current best practices to what his team needs to know to succeed.</p><p>So if there’s one thing that’s clear from Dennis’ insights, it’s this: knowing how and why something is needed, including extra training in a new area, is absolutely crucial.</p><h3>Managing Seniors &amp; Juniors Alike</h3><p>The CTO position is an interesting one. Not only do you have to manage a team of varying seniorities below you, from juniors to team leaders and managers, you also have to manage the stakeholders in the boardroom. As a CTO, you must communicate with CEOs and other C-level executives to make sure you align on strategy.</p><blockquote>“One of the biggest challenges is having the information created and ready on time because you need to provide information in both directions. You also need to be aware of who and what you are talking about. It’s not the same, talking to business people and marketing people is quite different […] They measure things quite differently.”</blockquote><p>Dennis told us that having information for both directions at the right time, and being able to translate this information for different disciplines, was integral to the success of the business. Miscommunication can be extremely detrimental, which is why as a CTO Dennis tries to teach people how to work with one another in the company. For seniors, that means learning to be kind and patient with juniors. For juniors, that means being eager to learn.</p><p>But ultimately, the divide between seniors and juniors can become a big problem if there is too much variation in experience. It can result in stagnation, as your devs are unable to hit the ground running.</p><h3>How training teams helps management</h3><p>For Dennis, it makes strategic sense to get your team extra training when you need to get everyone working together.</p><p>Towards the end of the interview, Dennis also argued that when team members go on a private dev training session, they should return to the team ready to share their knowledge. He hosts a weekly tech meeting where everyone can share what they’ve learned.</p><p>So ask yourself, can you share your new knowledge from developer team training easily? You must be able to answer why your developers should receive extra training before requesting it.</p><p>In addition, Dennis told us that having the right information and at the right time was crucial to getting any training budget approved. He recommended doing your homework and learning who you’re talking to and how they measure ROI to ensure your requests get approval.</p><h3>A CTO’s View on Mentoring</h3><p>Having previously worked as a professor, Dennis understood the importance of engaging people on their level and asking them, “How do you want to learn?”</p><p>Dennis said this was a crucial first step toward discovering what your employees want from their career and allows you to start mapping out their career path — together.</p><p>This is one of the best ways of helping both the business and the individual employee to succeed. Where skills are lacking, Dennis works with each of his team members to understand their pain points and how they want to overcome them. If they like to read a book to learn a new skill, he encourages that. Likewise, if an individual requires one-to-one training sessions, or to attend a course, he is committed to making that happen for his employees.</p><h3>What CTOs Need to Know to Approve Training Requests</h3><p>If you’re an employee looking to convince your manager to approve your training request, Dennis had some advice to share!</p><p>When his team comes to him with requests, Dennis first asks why they need this training and how it would help the business. He wants to know why it’s better to outsource dev training instead of doing it internally — which, of course, can be better but it depends on the needs of the students. Then, he follows up with more areas, including:</p><ul><li>The reputation of the training provider</li><li>The training provider’s success rate and testimonials</li><li>Any blogs the training provider has created</li><li>How this training provider compares to others — what makes these coaches better than anyone else?</li></ul><p>It’s all about due diligence. Dennis researches training before committing to it, so be sure to do your own research before you make a request for a training budget. <a href="https://reactgraphql.academy/react/how-to-ask-for-training-approval-from-your-boss/">We’ve written about this topic previously here</a>.</p><h3>Private Dev Training with React GraphQL Academy</h3><p>We work with many CTOs at global organisations to help them upskill their dev team’s abilities in React and GraphQL. Via both remote training and in-person opportunities, we bring your team face-to-face with the best practices they need to succeed with React and GraphQL technologies. To find out more about our corporate training courses, you can head to our dedicated page or <a href="/service/mailto:hello@reactgraphql.academy">contact our friendly team</a>!</p><p><em>Originally published at </em><a href="https://reactgraphql.academy/blog/how-do-ctos-approach-private-dev-training-and-upskilling"><em>https://reactgraphql.academy</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a81164d7836" width="1" height="1" alt=""><hr><p><a href="https://medium.com/react-graphql-academy/how-do-ctos-approach-private-dev-training-upskilling-5a81164d7836">How Do CTOs Approach Private Dev Training &amp; Upskilling?</a> was originally published in <a href="https://medium.com/react-graphql-academy">React GraphQL Academy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React GraphQL Academy teaching method]]></title>
            <link>https://medium.com/react-graphql-academy/react-graphql-academy-teaching-method-748bde397112?source=rss-d71a82789a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/748bde397112</guid>
            <category><![CDATA[graphql]]></category>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[teachibg-method]]></category>
            <category><![CDATA[teaching-programming]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Alex Lobera]]></dc:creator>
            <pubDate>Fri, 21 Feb 2020 07:12:18 GMT</pubDate>
            <atom:updated>2020-10-20T21:10:44.403Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-RTyyZlLqSGbevSo" /></figure><p>A teaching method encompasses the principles and methods used by teachers to enable student learning. For a teaching method to be effective, it must take into account not only the nature of the subject matter, but also how students learn.</p><p>At React GraphQL Academy we train people from all over the world who have different social and cultural backgrounds. For some of them, especially the ones with a more traditional education, our method might feel uncomfortable or even wrong. This article is aimed to explain our method and where the value lies.</p><p>This article has two parts. The first part describes the three main categories of problems we’ve encountered following our teaching method. What type of learners tend to face those problems, and some tips. The second part explains the six principles of our method.</p><h3>Lessons learned from teaching over a 1000 developers</h3><p>We’ve been collecting feedback from our trainees since we started teaching React in <a href="https://www.meetup.com/JavaScript-London/events/230287691/">May 2016 </a>to professional developers. We’ve identified 3 main categories of problems when teaching new tech <a href="https://reactgraphql.academy/blog/react-graphql-academy-teaching-method/#our_principles_where_we_stand">following our prIinciples</a> to our audience.</p><h3>1- Collaborative environment, or what I like to call the pair programming paradox.</h3><p>Feedback from trainee:</p><blockquote><em>There was not enough pair programming in the training, it didn’t feel it [the training] very collaborative.</em></blockquote><p>We always encourage doing pair programming during our training. I start by asking who knows what pair programming is. On average more than ⅔ will raise their hands. Then I ask who believes it is good practice. Most of them will show their hands still. Then I ask, how many of you do it at work? Less than ⅓ on average will show hands. Then I say, I’ve got good news, we can all do it now. The paradox is, many people believe it’s good practice, but they don’t practice it even when they have a chance.</p><p>I’ve noticed that developers who are very experienced and are not used to doing pair programming will prefer to work on the exercises on their own. Less experienced developers tend to be more willing to try. Another factor, besides the work experience, is the type of education the trainee had in the past. In my experience, trainees that come from “learn-to-code bootcamps” tend to be more comfortable with learning in collaborative environments. There is also an individual factor, how open-minded someone is towards trying new things. Whatever the case, we can encourage and motivate people to do pair programming, but in the end, it’s a personal decision.</p><p>Tips:</p><ul><li>Don’t feel judged if you think you know less than the group. Some people might feel put on the spot doing pair programming in the course. People attend the course to learn, not to judge. Also, you might know less about a given topic, but then you might know more about others.</li><li>Don’t be afraid of making mistakes in front of others. They’ll be likely to help you. We all make mistakes, just on different problems.</li><li>If you are a bit skeptical about doing pair programming, give it a try, it might surprise you positively 🙂</li><li>When pairing, please make sure you swap the driver / navigator roles at least after each task. This helps keep both people engaged even if one is quicker.</li></ul><h3>2- Discovery versus instruction</h3><p>Feedback from a trainee:</p><blockquote><em>I think some sessions become too (in my opinion) instructive.</em></blockquote><p>Feedback from a trainee:</p><blockquote><em>I wish less guessing what would be the solution.</em></blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fembed.ted.com%2Ftalks%2Fsugata_mitra_kids_can_teach_themselves&amp;display_name=TED&amp;url=https%3A%2F%2Fwww.ted.com%2Ftalks%2Fsugata_mitra_kids_can_teach_themselves&amp;image=https%3A%2F%2Fpi.tedcdn.com%2Fr%2Fpe.tedcdn.com%2Fimages%2Fted%2F20665_480x360.jpg%3Fh%3D421%26w%3D560&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=ted" width="560" height="421" frameborder="0" scrolling="no"><a href="https://medium.com/media/9912665290ddf26c3533ed927b0761d8/href">https://medium.com/media/9912665290ddf26c3533ed927b0761d8/href</a></iframe><p>Discovering is how kids naturally learn. Sugata Mitra’s research (video above) shows us that kids can teach themselves. If kids can do it, why shouldn’t developers be able to do it too?</p><p>We believe that technology changes so quickly that it gets difficult to keep up with it. We think that the fastest and most effective way to learn is by getting the right balance between discovering by ourselves and being guided. We also believe that <a href="https://reactgraphql.academy/blog/the-number-one-reason-that-will-make-you-want-to-test-your-code#writing_software_is_complex">building software is a discovery process</a> in itself. Therefore, one of the skills we try to promote in our training is the ability to effectively solve new problems.</p><p>Tips:</p><ul><li>I’ve observed that those who tend to feel uncomfortable following a discovery approach are the ones who tend to need to practice it the most. If you feel it’s not working for you, try to be more open-minded and creative without judging the outcome.</li><li>I’ve also observed how this discovery learning approach can be counterproductive when trainees get lost or blocked for too long. If you feel you’re not making any progress in an exercise for more than 10 min, reach out for help. Coaches are there to support you and guide you. You should not feel confused or frustrated.</li></ul><h3>3- Lecture versus programming</h3><p>Feedback from a trainee:</p><blockquote><em>I wish more theory before the exercise.</em></blockquote><p>Feedback from a trainee:</p><blockquote><em>The split between instruction and programming was not quite right in my opinion. Ideally each 3 hour session would involve 2 hours of programming.</em></blockquote><p>Some learners prefer more theory, some others prefer more time programming. The goal is not to find the right balance that works for everyone, because probably there is not such a thing. I think the point here is to communicate where our training stands so trainees can make an informed decision before joining the training if it feels the right course for them.Tips:</p><ul><li>If you are used to a very traditional teacher-centered approach, which situates the teacher in the primarily “active” role while students take a more “passive” one, you might prefer longer lectures and fewer exercises. As a trainee, we encourage you to take an active role in the course whenever you can. If you believe your main learning methods are listening, reading, or watching rather than <a href="https://reactgraphql.academy/blog/react-graphql-academy-teaching-method/#learn_by_doing">doing</a>, then our courses might not be the best fit for you.</li><li>If you prefer a complete student-centered approach where you take full control of your own education, then our courses might not be the right fit for you either. Our coaches are experts and authors with carefully designed learning objectives to be delivered. They are meant to facilitate and not to instruct. Nevertheless, if what feels right to you is a more self-directed environment we recommend you to apply to <a href="https://www.recurse.com/">Recurse Center</a>.</li></ul><h3>Our principles — where we stand</h3><h3>Learn by doing</h3><p>We want developers to code/ do as much as possible in our training. But we can’t efficiently start doing without prior knowledge. We strive to get a balance of 1 hour lecture + QA for every 2 hours of in-class exercises. For us in-class exercise is not only programming but also pair &amp; group discussions, and any other activity that makes trainees interact to work on the learning objectives.</p><p>This doesn’t mean we always lecture for one hour and then after trainees work for two hours. Lectures can be broken down and intercalated with exercises. Our lectures typically don’t explain everything trainees need to know before doing an exercise. The goal of our lectures is to set the ground for effective problem-based learning in the subsequent hands-on exercise.</p><p>“Learn by doing” is considered part of an approach to education called <a href="https://en.wikipedia.org/wiki/Discovery_learning">discovery learning</a> which is very in alignment with how our academy teaches.</p><h3>Collaborative learning</h3><p>Pair programming is one of the best collaborative learning tools for developers. It enhances the learning experience because it forces both people to explain what they do and how, rather than just doing. This helps reduce the time a person can be blocked trying to figure something out (I have seen many developers struggling a lot before saying “I need help”), come up with different approaches, increase motivation and engagement, and consolidate new skills. By doing with others we get more input on what you are doing.</p><h3>Progressive curriculum</h3><p>Each class on our course covers a single topic, and builds on previous classes so that we can cover increasingly specialist material as the course progresses. As such, the whole course needs to be taken as a whole, rather than as a drop-in clinic. The curriculum is designed by industry experts, to balance coverage of those topics that we think are necessary to become an expert in the field, with those extra topics that learners commonly want to learn about, or appreciate being taught.</p><h3>Open-ended problem versus closed-ended problems</h3><p>A closed-ended problem is a problem that only has one solution leading to one answer. Closed-ended problems are easier to automate, for instance, <a href="https://www.freecodecamp.org/learn/front-end-libraries/react/add-comments-in-jsx">this exercise</a>. We think these types of problems don’t necessarily resemble the complexity of building real-world software. We use and recommend closed-ended problems to build certain foundational knowledge, but we think they are not enough for our end goal: to build developer expertise.</p><p>We believe that expertise is built effectively by solving complex problems with multiple solutions. Therefore, we prefer our trainees to work on open-ended problems. A critical success factor to this approach is that it must be assisted, and that is the case in all our courses.</p><h3>Mentorship and guidance</h3><p>Coaches guide trainees to help them think of the best way to approach and solve a problem. We are focused on promoting developer self-reflection, and critical thinking as opposed to prescribing solutions. Coaches make recommendations and explain the rationale behind the recommendations, then trainees choose. Sometimes learners want a simple answer: “what should I do, A or B?”. The answer typically starts with “it depends”. One of the coaches’ key jobs is to understand trainees’ problems and to make sure trainees understand the pros &amp; cons of each approach recommended, depending on the case.</p><p>The mentors’ role in discovery learning is critical to the success of learning outcomes. Learners must build knowledge through examples, practice and feedback.</p><h3>Get it right in the end</h3><p>We think that we can learn a lot from how second languages (English, Spanish, etc) are acquired in order to teach new programming languages or styles (Functional Programming, Declarative Programming, etc).</p><p>“Get it right in the end” is a technique for second language learning in the classroom. It’s the opposite of the traditional “get it right from the beginning” approach, which explicitly teaches all the rules and concepts before students start using it.</p><p>We think learning is an iterative process where we constantly refine our mental models. “Get it right in the end” is very aligned to our idea of <a href="https://reactgraphql.academy/blog/react-graphql-academy-teaching-method/#learn_by_doing">doing</a> as early in the learning process as possible. The way we implement this technique in our courses is:</p><ul><li>Learners start doing before they know all the concepts. They build knowledge by trying things out, interpreting docs, and asking questions.</li><li>Coaches give corrective <a href="https://reactgraphql.academy/blog/react-graphql-academy-teaching-method/#mentorship_and_guidance">feedback</a>.</li><li>Coaches recap and formalize the concepts learned at the end of the session.</li></ul><p>You can read more about this technique and others for second language acquisition in this <a href="https://www.amazon.co.uk/How-Languages-are-Learned-4th-ebook/dp/B00BHHIYBC">book</a>.You can also check out some of the authors’ ideas in the following short video:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FpxMpgcIkfOo%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DpxMpgcIkfOo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FpxMpgcIkfOo%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/85ae0648be03a9886233728b094b5b2a/href">https://medium.com/media/85ae0648be03a9886233728b094b5b2a/href</a></iframe><h3>Feedback, Feedback, Feedback</h3><p>These are the principles that guide React GraphQL Academy, because we’re passionate about teaching, and we really want our students to thrive on their learning and further career. But ultimately we try to be flexible and to take into account each of our students’ learning needs. This is why the feedback of our courses is overall very positive, and why we’re becoming leaders in the market of React and GraphQL teaching. If you take a course with us, we encourage you to give us feedback: your opinion is very important! We appreciate that and will use it to evaluate changes and make improvements in our courses.</p><p><em>Originally published at </em><a href="https://reactgraphql.academy/blog/react-graphql-academy-teaching-method"><em>https://reactgraphql.academy</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=748bde397112" width="1" height="1" alt=""><hr><p><a href="https://medium.com/react-graphql-academy/react-graphql-academy-teaching-method-748bde397112">React GraphQL Academy teaching method</a> was originally published in <a href="https://medium.com/react-graphql-academy">React GraphQL Academy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Five 2020 T-Shaped Developer Trends You Need to Know]]></title>
            <link>https://medium.com/react-graphql-academy/the-five-2020-t-shaped-developer-trends-you-need-to-know-5dde28003ca9?source=rss-d71a82789a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/5dde28003ca9</guid>
            <category><![CDATA[trends-for-2020]]></category>
            <category><![CDATA[graphql]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Alex Lobera]]></dc:creator>
            <pubDate>Fri, 21 Feb 2020 06:59:21 GMT</pubDate>
            <atom:updated>2020-10-20T21:11:18.190Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HyRXpALbzWFZZaRI" /></figure><p>T-Shaped Developers are those rare people who combine a depth of expertise with a wide breadth of knowledge. So to help you build the perfect dev team or build up your own dev knowledge, I’ve compiled all the major trends for 2020 you need to know about.</p><p>With the rate of technological change today, no developer can afford to rest on their laurels and think that experience alone will keep their career afloat. Knowledge of what is going around them is also a key skill every developer needs. These T-shaped Devs, renowned for their expertise and knowledge, are able to command higher wages and deliver more in their roles.</p><p>So to help pad out your knowledge, I’ve compiled a list of the biggest dev trends for 2020.</p><h3>1. Cloud Is Everyone’s Concern</h3><p>Gone are the days where cloud was only a thing for the IT and some back-end devs to worry about. The cloud has become even more pervasive in recent years, and now that the tech is very mature and much simpler to use, front-end devs are also going to have to factor in the cloud. Agile teams now have full ownership of cloud features or products, meaning DevOps has become an even more important role in every team.</p><p>Nader Dabit, who has been exploring the intersection of front-end dev &amp; cloud computing, thinks that:</p><blockquote><em>In 2020 we’ll continue to see an explosion of full stack cloud engineers.</em></blockquote><h3>Nader Dabit on Twitter</h3><p>Cloud computing is becoming more serverless by default. At the same time the barriers to entry are becoming lower &amp;amp; the UX is becoming better allowing more traditionally front-end devs to start using it. In 2020 we&#39;ll continue to see an explosion of full stack cloud engineers.</p><h3>2. Functional Programming Goes Mainstream</h3><p>Functional programming (FP) languages are becoming more and more mainstream, so in 2020 we recommend that you try to learn an FP language like Haskel, Ocamel and the like. That’s because learning a new language takes time, and rewriting production code from one language into another takes even longer.</p><p>But with an FP style, you don’t need to learn a new programming language to write production code. In fact, by learning to write functional code in your main imperative programming language, you’ll cut production and delivery time for enhanced end-products.</p><p>We’ll keep using more and more things like closure, composition, memoization, but also some still less mainstream concepts such as algebraic effects, even in languages that are not “purely functional” like JavaScript.</p><h3>3. React Continues Its Upward Ascent</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/659/1*29Rhex9PuHneL-_CUNNfuQ.png" /><figcaption><a href="https://trends.google.com/trends/explore?cat=31&amp;date=today%205-y&amp;q=React,Svelte,Angular,Vue,Ember">Image source</a></figcaption></figure><p>In 2020, expect to hear more great things about React, especially when it comes to delivering greater, faster user experiences. In the past, the React core team focused on developer experience. Now their focus is on improving the user experience, especially in large apps. This year, more than ever, devs will utilise components to build better UIs because it is great for any kind of UI abstractions.</p><p>React’s continued rise is good news for both front- and back-end devs, as Vitaly Lavrov, a back-end developer I met networking at a conference was keen to point out:</p><blockquote><em>I really like React components because it helps me easily reuse someone else’s design quickly and with confidence. This way I can build a product with a nice UI whilst I can focus on what I’m good at, the backend.</em></blockquote><h3>4. Devs, Expect Closer and Closer Partnership with UX</h3><p>User Experience (UX) design has also been on the rise, especially as more companies understand that they are responsible for the products they create and must meet user needs effectively to stay competitive. So, expect dev and UX to be even more tied at the waist this year.</p><p>In particular, I recommend trying pair programming between dev and UX this year. At React GraphQL Academy, we pair programmed with a UX designer on a number of projects, including our own website. It helps in two ways: UX designers better understand the limits of technology, and devs understand the importance of sticking to design and meeting user needs. No wonder many large organisations are looking to integrate UX and dev.</p><p>If you think developers can’t learn design, some experienced designers like Steve Schoger will tell you that devs and designers are not that different:</p><h3>Steve Schoger on Twitter</h3><p>A lot of developers will tell me that you can learn to code but you can&#39;t learn design. Learning design requires the same skill as learning to code: the ability to sit down and focus on learning it for many hours at a time.</p><p>Learning UX is not only relevant for front-end devs. As James Coplien pointed out to me once in a workshop for solution architects: “to be a good architect you also need to understand UX, if you can’t understand your users’ needs then you can’t design the right system”.</p><p>I attended a UX Design Course in 2017 and I think it was one of the best investments in my career as a tech lead. It helped me understand how my design and product colleagues work and think, allowing me to communicate and collaborate more effectively with them.</p><h3>5. GraphQL Moves to the Forefront</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/656/1*gSbNalpkhYplYWO5d3Bp3Q.png" /><figcaption><a href="https://trends.google.com/trends/explore?cat=31&amp;date=today%205-y&amp;q=graphql%20design,graphql%20php,graphql%20ruby,graphql%20react,graphql%20java">Image source</a></figcaption></figure><p>In 2020, expect to see more of GraphQL across design, back- and front-end development.</p><p>The seamless nature of GraphQL makes sure that data is where you need it, when you need it. It not only helps apps run faster, especially those where latency and bandwidth are an issue, but it also helps engineering product teams <a href="https://medium.com/airbnb-engineering/how-airbnb-is-moving-10x-faster-at-scale-with-graphql-and-apollo-aa4ec92d69e2">deliver software faster</a>. Of course, this is invaluable whatever your discipline. The GraphQL declarative data fetching model fits very well into declarative UI libraries like React. In combination, they enable fast and reusable component-based data-driven applications that deliver faster software at scale. 2020 may be the year of GraphQL and data-driven applications.</p><h3>Bonus Trend: Curiosity &amp; Critical Thinking</h3><p>T-shaped devs in 2020 won’t just need to know about tech shifts and new design focuses. They’ll also need to prioritise skill development, which is where this final trend comes in: Curiosity and Critical Thinking.</p><p>You’re going to need to come out of your comfort zone this year. If you’re a software architect, try learning UX. If you’re a front-end dev, try learning cloud. Feed your curiosity in 2020 by learning about new fields and then utilise critical thinking to help understand those fields inside and out. Only then will you broaden your horizons and be able to work in a truly collaborative way.</p><h3>Deepen Your Tech Knowledge with React GraphQL Academy</h3><p>With these few T-shaped developer trends, there’s a lot to learn this year. But you don’t have to go it alone: we’re here to help. React GraphQL Academy is proud to offer a range of training courses — including week-long bootcamps, part-time courses and one-off workshops — to help devs upskill in React and GraphQL.</p><p>If you’d like to deepen your tech knowledge in 2020, <a href="/service/mailto:hello@reactgraphql.academy">get in touch</a> with our friendly team today!</p><p><em>Originally published at </em><a href="https://reactgraphql.academy/blog/the-five-2020-t-shaped-developer-trends-you-need-to-know"><em>https://reactgraphql.academy</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5dde28003ca9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/react-graphql-academy/the-five-2020-t-shaped-developer-trends-you-need-to-know-5dde28003ca9">The Five 2020 T-Shaped Developer Trends You Need to Know</a> was originally published in <a href="https://medium.com/react-graphql-academy">React GraphQL Academy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[If you think GatsbyJS is only a static site generator, you are missing the point]]></title>
            <link>https://medium.com/react-graphql-academy/if-you-think-gatsbyjs-is-only-a-static-site-generator-you-are-missing-the-point-788b0a9423c3?source=rss-d71a82789a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/788b0a9423c3</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[gatsbyjs]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Alex Lobera]]></dc:creator>
            <pubDate>Sun, 26 Jan 2020 08:39:06 GMT</pubDate>
            <atom:updated>2020-01-26T08:39:06.826Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xV609aSLxRIdcfW0" /></figure><p>On this page:</p><ul><li>We see the world from our perspective at a particular point in time, <a href="https://reactgraphql.academy/react/if-you-think-gatsbyjs-is-only-a-static-site-generator-you-are-missing-the-point#we_see_the_world_from_our_perspective_at_a_particular_point_in_time">go to section</a>.</li><li>Websites as a content mashup, <a href="https://reactgraphql.academy/react/if-you-think-gatsbyjs-is-only-a-static-site-generator-you-are-missing-the-point#websites_as_a_content_mashup">go to section</a>.</li><li>GraphQL as the content mesh composition tool, <a href="https://reactgraphql.academy/react/if-you-think-gatsbyjs-is-only-a-static-site-generator-you-are-missing-the-point#graphql_as_the_content_mesh_composition_tool">go to section</a>.</li><li>Asynchronous content mesh system for the Web, <a href="https://reactgraphql.academy/react/if-you-think-gatsbyjs-is-only-a-static-site-generator-you-are-missing-the-point#asynchronous_content_mesh_system_for_the_web">go to section</a>.</li></ul><p>After a year using GatsbyJS to build what I thought was a “simple static site”, I had a <em>kerpow</em>: GatsbyJS is NOT a static site generator, but an asynchronous content mesh system for the modern Web, powered by GraphQL. There were two concepts that together helped me realize that: content &amp; time.</p><p>For those who don’t know what having a <em>kerpow</em> means (it’s a concept I’ve only come across recently), it means, in two simple words, “ <a href="https://www.youtube.com/watch?v=NdSD07U5uBs&amp;feature=youtu.be&amp;t=964">holy shit</a>”. Let me show you the path that brought me to the realization that I was not simply building a static site.</p><h3>We see the world from our perspective at a particular point in time</h3><p>If I look at how I’ve spent my time while using GatsbyJS during the last year, the most time (approximately 70%) was spent looking at JSX code, followed by looking at JSON (data), followed by looking at GraphQL queries, and finally, the least amount of time was spent looking at Node.js code. Bear in mind that this is not a very rigorous 1-year analysis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/607/1*TipnRsYYMsRwNYq7PlgD6g.png" /></figure><p>Distribution of code &amp; time I’ve been dealing with while using GatsbyJS in <strong>the last year</strong>.</p><p>If your diagram would look similar to mine, you might also be under the impression that GatsbyJS is a static site generator.I run the following Twitter poll about other devs spend their time using Gatsbyjs:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/496/1*C3zW-PLhxN5dvtHdGV3DFA.png" /></figure><p>Whatever the case, feel free to tweet me if you want to share your experience :)</p><p>What was my main focus this year? We wanted our users to have the best user experience and we iterated <a href="https://medium.com/leanjs/reactjs-academy-2018-website-design-case-study-4b2074dc4e5d">this process</a> for one year.</p><p>Interestingly, the more I reduce the span of time I analyse, and get closer to the present, the more the pyramid shifts. If I look at the past few weeks, the pyramid looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/584/1*QC3uHqE-lizA7ZmMptftuQ.png" /></figure><p>What has changed? I’ve focused on content, which gave me a new perspective. I believe our capacity to come to a realisation of something correlates to our exposure to it. Let me share with you what I’ve been exposed to recently, and how it made me change the way I think about GatsbyJS.</p><h3>Websites as a content mashup</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/655/1*0tvBY_Hj5oALV59rS0XdXg.png" /></figure><p><em>Websites as a content mashup</em> is not a new thing. Ten years ago I was creating “widgets” using JSONP to display content from different sources on a website. The mashup concept has even made it to a prestigious dictionary:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/657/1*3etucCXW4qTwzdfFwCn3_g.png" /></figure><p>In the past, the mashup was focused on the browser. Why? Because cross-domain requests were complicated, and we developers like complicated things. Just kidding 😜, I don’t know why 😄. What I do know is that the world has changed since then. For instance:</p><ul><li>There are many more APIs to pull content from.</li><li>We’ve got better tooling to create that mashup.</li><li>Ten years ago we had mainly desktops on the client and relatively expensive servers. Now we have a huge variety of devices and different types of networks, as well as cheap cloud computing, compared to the on-premise data centres we used to have to use.</li></ul><p>An observation from reading the Cambridge Dictionary. It defines a mashup as using “from different websites”. I wouldn’t say that a headless CMS is a website, and neither is gatsby-image. So these days that definition doesn’t quite fit. The modern term is <a href="https://www.gatsbyjs.org/blog/2018-10-04-journey-to-the-content-mesh/">content mesh</a>.</p><p>What I find very interesting is that now the mashup content mesh is created in different places, at different points in time. For instance, this page <a href="https://reactgraphql.academy/react/training/bootcamp/london/">https://reactgraphql.academy/react/training/bootcamp/london/</a> uses two stages to pull data: 1) build time, and 2) client time.</p><h3>Build time</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/651/1*O99GKNSPUaEDKYrDwxe_UA.png" /></figure><p>This is what you’ll see if you disable JavaScript on the browser and navigate to <a href="https://reactgraphql.academy/react/training/bootcamp/london/">this link</a>. What you see is the data that was pulled at build time, which is everything but the price. You see a landing page that explains a training, but you can’t actually buy the training instance yet. If you click on “Buy tickets” with JS disabled you’ll see the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*8qj83p6mQHvO-NyVxlRiSA.png" /></figure><p>No matter how long you wait, no JavaScript, no price.</p><h3>Client time</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aoqNtkrmxHFKz488rUkikQ.png" /></figure><p>This is what you’ll see if you enable JavaScript on the browser, navigate to the same page, and click on the “Buy tickets” button at the top of the page. The browser will scroll down to the price section, and then you’ll be able to see the price at that point in time. The reason fetching the price is delayed until run-time being that the price depends on certain conditions, such as sales promotions, and if the course is sold out, or cancelled, there might be no tickets on sale.</p><p>The following pyramid is an approximation of my time spent on building that page:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v5R26tvqldxWfZ9GBcjBjQ.png" /></figure><h3>GraphQL as the content mesh composition tool</h3><p>Things changed when we decided to integrate this blog to a headless CMS. Prior to that, writing an article was a matter of writing some markdown, and merging a PR into master. The CI would then do the rest:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1jApPezD-ypmFPxYdIqWmA.png" /></figure><p>This blog post you are reading right now was created and published using <a href="https://www.sanity.io/">Sanity.io</a> (our headless CMS of choice). This CMS adds the following task to our workflow: posts are published on Sanity.io, and is subsequently available via an API. To be published doesn’t mean it’s displayed on the website. How do we display that post on the website? GatsbyJS plugins.</p><h3>GatsbyJS plugins, the building blocks we can configure AND extend</h3><p>GatsbyJS plugins are a very powerful way to source and/ or transform almost any kind of data in a GatsbyJS website. All the data in GatsbyJS become nodes in a graph. By using GraphQL to expose all the data GatsbyJS makes it very easy to query. Being able to easily query data is just the tip of the iceberg. GraphQL is a powerful mechanism to compose and extend data across all the plugins.</p><p>First, let me show you what I did to make all my CMS data available on my website. We can connect a GatsbyJS website to Sanity.io using the <a href="https://www.gatsbyjs.org/packages/gatsby-source-sanity/">gatsby-source-sanity</a> plugin. The following 5 lines of code gave me access to all my Sanity content at build time:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uSGtMCpmpT1eiSlnyvtnDw.png" /></figure><p>But I encountered a problem, that plugin didn’t have a feature I needed. I wanted to download images from Sanity.io at build time to my local so I could distribute them using my CDN of choice. Contentful (another headless CMS) provides a `localFile` field in their schema that implements that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aX7Z5aSKcesNUJs17-6Row.png" /></figure><p><a href="https://www.gatsbyjs.org/packages/gatsby-source-contentful/#download-assets-for-static-distribution">https://www.gatsbyjs.org/packages/gatsby-source-contentful/#download-assets-for-static-distribution</a></p><p>Unfortunately, Sanity.io didn’t have that field in their GraphQL schema. One solution to this problem is to switch CMS. The problem with switching to another CMS is that it might take a considerable amount of effort and it doesn’t guarantee that the new one will provide all the functionality that I might need in the future. A better solution would be to extend the GraphQL schema and implement the use case I need. These were my requirements:</p><ul><li>Crop an image using Sanity cloud image service.</li><li>Download the image from the Sanity CDN to my local machine at build time.</li><li>Pipe the image file, downloaded at build time, to an ImageSharp type to get an ImageSharpFluid version of it.</li><li>Pass the ImageSharpFluid data to a gatsby-image React component.</li><li>Deploy images to my CDN of choice at build time.</li><li>Download images from my CDN of choice at client time.</li></ul><p>You might get lost with the terms and think it’s a lot of work, just bear with me for a second. My distribution of time/type of code to implement that:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TDsN_osnyYG-EOpn4Pf01A.png" /></figure><p>We can map that pyramid to the following code:</p><p>JSX, 0 props or JSX updated: <a href="https://github.com/reactgraphqlacademy/reactgraphqlacademy/blob/master/src/components/blog/PostCard.js#L24">https://github.com/reactgraphqlacademy/reactgraphqlacademy/blob/master/src/components/blog/PostCard.js#L24</a></p><p>JSON, manipulated data:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gThmABnDNz3Q_T5ZOpHnlg.png" /></figure><p><a href="https://github.com/reactgraphqlacademy/reactgraphqlacademy/blob/master/src/components/blog/PostCard.js#L16">https://github.com/reactgraphqlacademy/reactgraphqlacademy/blob/master/src/components/blog/PostCard.js#L16</a></p><p>GraphQL, updated query:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oXY8ugu-T2P_5hbwyLl0sw.png" /></figure><p><a href="https://github.com/reactgraphqlacademy/reactgraphqlacademy/blob/master/src/components/blog/PostCard.js#L48">https://github.com/reactgraphqlacademy/reactgraphqlacademy/blob/master/src/components/blog/PostCard.js#L48</a></p><p>Node.js code:</p><p>To me, this is the most mind-blowing part. <strong>Only 61 lines of code</strong> (considering that we are using the verbose GraphQL JS reference implementation) to solve the whole problem by creating a plugin that extends another plugin (gatsby-source-sanity) using a third plugin (gatsby-source-filesystem) 🤯.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*5SaFirkSYgmEm5bK72P0hQ.png" /></figure><p><a href="https://github.com/reactgraphqlacademy/gatsby-source-sanity-transform-images/blob/master/src/gatsby-node.js">https://github.com/reactgraphqlacademy/gatsby-source-sanity-transform-images/blob/master/src/gatsby-node.js</a>.</p><h3>Asynchronous content mesh system for the Web</h3><p>I submitted my plugin to the GatsbyJS plugin library following the GatsbyJS docs steps. Soon after I typed “sanity” on their plugin search input and there it was! Mmm, or it wasn’t?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FCpwwq_tMD2BmvnCrXirYQ.png" /></figure><p>Then I read in their docs: “Algolia will take up to 12 hours to add it to the library search index (the exact time necessary is still unknown), and wait for the daily rebuild of <a href="https://gatsbyjs.org/">https://gatsbyjs.org</a> to automatically include your plugin page to the website.”</p><p>Algolia is a Software as a Service (SaaS) product that specializes in search and discovery. It took about an hour for Algolia to index my plugin. So after an hour, the plugin showed up in the search result. It took over a day for the GatsbyJS build to run again, and finish. That time in between the Algolia index and the GatsbyJS build I was in limbo, the technical name for which is ‘eventual consistency’.</p><p>That’s not unique to Gatsbyjs.org. We have a similar issue in this blog. When we publish a blog post in Sanity.io, the post is immediately available on the API. Then we need to build the site. The time in between publishing and building, the editor is in limbo.</p><p>We can use webhooks to solve the issue. An editor publishes a document and then a webhook triggers a build. Unfortunately, I don’t think that’s currently cost-effective at scale.</p><p>With the battle for content very intense right now between so many players, maybe it’s time to start focusing on the next frontier: incremental build on the cloud.</p><p><em>Originally published at </em><a href="https://reactgraphql.academy/react/if-you-think-gatsbyjs-is-only-a-static-site-generator-you-are-missing-the-point"><em>https://reactgraphql.academy</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=788b0a9423c3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/react-graphql-academy/if-you-think-gatsbyjs-is-only-a-static-site-generator-you-are-missing-the-point-788b0a9423c3">If you think GatsbyJS is only a static site generator, you are missing the point</a> was originally published in <a href="https://medium.com/react-graphql-academy">React GraphQL Academy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why use React with GraphQL?]]></title>
            <link>https://medium.com/react-graphql-academy/why-use-react-with-graphql-bbdcf035c49d?source=rss-d71a82789a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/bbdcf035c49d</guid>
            <category><![CDATA[graphql]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[react-graphql-academy]]></category>
            <category><![CDATA[dev-training]]></category>
            <category><![CDATA[reactjs]]></category>
            <dc:creator><![CDATA[Alex Lobera]]></dc:creator>
            <pubDate>Fri, 03 Jan 2020 11:11:01 GMT</pubDate>
            <atom:updated>2020-01-03T11:11:01.098Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WZA8gVLJsEHklGVH" /></figure><p>On this page:</p><ul><li>Both embrace declarative code and the tree data structure, <a href="https://reactgraphql.academy/#both_embrace_declarative_code_and_the_tree_data_structure">go to section</a>.</li><li>React and GraphQL are complementary, <a href="https://reactgraphql.academy/#react_and_graphql_are_complementary">go to section</a>.</li><li>React and GraphQL have great dev communities, <a href="https://reactgraphql.academy/#react_and_graphql_have_great_dev_communities">go to section</a>.</li><li>React and GraphQL are powerful and efficient, <a href="https://reactgraphql.academy/#react_and_graphql_are_powerful_and_efficient">go to section</a>.</li></ul><p>The two staple courses at React GraphQL Academy are our React and GraphQL Bootcamps, and with good reason! Pairing the technologies works wonders for building digital products. Here’s why…</p><p>React and GraphQL are designed to work together so you can build declarative, performant and scalable applications. In a word, they make it easier to create great apps that are data-efficient and economic to build. There are several reasons why you should use React with GraphQL.</p><h3>Both embrace declarative code and the tree data structure</h3><p><a href="https://reactgraphql.academy/graphql/">GraphQL</a> and React both harness declarative syntax, which is great news for just about everybody. With declarative, you have less code to build, which means less bugs and faster dev time, allowing you to ship products quickly.</p><p>Likewise, both <a href="https://reactgraphql.academy/react/training/">React</a> and GraphQL use the tree data structure. The UI in React is a tree, and GraphQL queries are too. Combine the tree data structure aspect with the declarative code and you have a consistent framework to work with across both GraphQL and React, thereby speeding dev time up again.</p><h3>React and GraphQL are complementary</h3><p>While React is a JS library concerned with the User Interface (UI), all web applications will need data at some point. Previously, data would be consumed with a REST API. However, if you have a performant UI and you want your data integration to be just as good, you’ll need something a little more powerful than a REST API.</p><p>That’s where GraphQL comes in. Consuming with a GraphQL API in React is both straightforward and quick using any of its popular clients like Apollo Client or Relay, which also help with state management and coaching. React and GraphQL work in unison to bring you a modern, performant front-end.</p><h3>React and GraphQL have great dev communities</h3><p>Web technologies are often only as good as the communities that support them. When you’re looking to adopt a new tech, look at the community behind it. If you do look at the community for React and GraphQL, you’ll see that the communities are huge. They have loads of experience and they’re very active and engaged with tooling the technologies. You’ll have all the support and backing you need.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qD7PFLJjlVvmQX0ezvgKBQ.jpeg" /></figure><h3>React and GraphQL are powerful and efficient</h3><p>If you’re a front-end engineer hoping to build a performant app quickly, React and GraphQL will be your go-to tools. You can harness them to quickly build robust and scalable apps.</p><p>On the one hand, you have React. React was engineered to be highly performant at manipulating UI. On the other hand, you have GraphQL, which is excellent at accessing heavily nested data in just one trip to the client. It’s very data efficient, and with Apollo and Relay tools available too, there are options to tailor an app to your organisation’s needs.</p><h3>Learn GraphQL and React with React GraphQL Academy</h3><p>If you can’t wait to bring the benefits of React and GraphQL to your organisation, we’re here to help you and your team master the fundamentals, fast. Our <a href="https://reactgraphql.academy/">React and GraphQL Bootcamps</a> train students in both the basics and advanced features of React or GraphQL over just five days. We even show students how to apply what they learn to real-world examples.</p><p>Find out more about our two bootcamps and book yours today by <a href="/service/mailto:hello@reactgraphql.academy">contacting our friendly team</a>!</p><h4>Related articles:</h4><p><a href="https://reactgraphql.academy/graphql/what-is-GraphQL-used-for/">What is GraphQL used for?</a> <a href="https://reactgraphql.academy/graphql/who-uses-graphql/">Who uses GraphQL anyway?</a> <a href="https://reactgraphql.academy/graphql/announcing-our-new-graphql-bootcamp/">Announcing our new GraphQL Bootcamp!</a></p><p><em>Originally published at </em><a href="https://reactgraphql.academy/graphql/why-use-react-with-graphql"><em>https://reactgraphql.academy</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bbdcf035c49d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/react-graphql-academy/why-use-react-with-graphql-bbdcf035c49d">Why use React with GraphQL?</a> was originally published in <a href="https://medium.com/react-graphql-academy">React GraphQL Academy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ask Alex: Do I need a CS degree to become a good developer?]]></title>
            <link>https://medium.com/react-graphql-academy/ask-alex-do-i-need-a-cs-degree-to-become-a-good-developer-8dc3b1372070?source=rss-d71a82789a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/8dc3b1372070</guid>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[react-graphql-academy]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[developer-training]]></category>
            <dc:creator><![CDATA[Alex Lobera]]></dc:creator>
            <pubDate>Mon, 30 Dec 2019 10:08:20 GMT</pubDate>
            <atom:updated>2019-12-30T10:08:20.920Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*g95tvq5MYMsCp3Qg" /></figure><p>On this page:</p><ul><li>Do I Need a CS Degree to Become a Good Developer?, <a href="https://reactgraphql.academy/blog/ask-alex-do-i-need-a-cs-degree-to-become-a-good-developer/#do_i_need_a_cs_degree_to_become_a_good_developer">go to section</a>.</li><li>Can I learn to become a great developer without going to uni?, <a href="https://reactgraphql.academy/blog/ask-alex-do-i-need-a-cs-degree-to-become-a-good-developer/#can_i_learn_to_become_a_great_developer_without_going_to_uni">go to section</a>.</li><li>Do I need foundation knowledge to become a good programmer?, <a href="https://reactgraphql.academy/blog/ask-alex-do-i-need-a-cs-degree-to-become-a-good-developer/#do_i_need_foundation_knowledge_to_become_a_good_programmer">go to section</a>.</li><li>3 Questions to Ask Yourself, <a href="https://reactgraphql.academy/blog/ask-alex-do-i-need-a-cs-degree-to-become-a-good-developer/#3_questions_to_ask_yourself">go to section</a>.</li></ul><p>Knowledge is everything when it comes to being a good developer, but do you need a Computer Science (CS) degree to become one? Take a peek at our latest interview to find out…</p><p>If someone else can learn to do it, you can too. That’s always the case, it’s always been the case, and it always will be the case. But when it comes to learning how to become a good programmer, do you really need to go to university to learn? In this conversation, I talked with a former pupil from React GraphQL Academy about his experience.</p><h3>Do I Need a CS Degree to Become a Good Developer?</h3><p><strong>Student:</strong> In my last job, my company was running out of funds and they dismissed and replaced me with a full-stack dev. For them, it was better to have a dev that could implement a feature backwards than to just have a front-end dev. So, I started thinking that maybe I don’t have the necessary skills for this market and I need to know some more stuff. Is that the case?</p><p><strong>Alex:</strong> So what do you think the problem here was:</p><p>You didn’t know front and back?</p><p>Your company didn’t have the funds to train you?</p><p>I’ll be honest with you — I run a small business. If you ask me whether I would hire someone who does front-end or someone who can do front-end, back-end, and a bit of UX alongside a working knowledge of Google Analytics… I would tell you that the person who only knew front-end dev wouldn’t have many chances at React GraphQL Academy.</p><p>But, is the full-stack hero who can do all of these things good enough? I would say that we can’t be good at everything.</p><p>In my view, being a full-stack UP-TO-DATE developer is a utopia nowadays. Someone once told me that specialization is learning more about less. You need to find a balance that works for you. In my small business I don’t need a developer who can build 500 super-scalable microservices — that’s Netflix, not React GraphQL Academy. The point is, who do you want to be and who do you want to work for?</p><p><strong>Student:</strong> You’ve made some really good points there, Alex. But I was always made to think that a Computer Science degree would either make or break my career. It takes nearly three years to complete a CS degree — will it be worth all that work, effort and pain?</p><p><strong>Alex:</strong> I started uni for my software engineering degree at the age of 25 while I was working as a developer. True, it was tough to work as a dev and go to uni at the same time. But being tough is one thing — is it worthwhile to do it?</p><p>I think the question I would really ask you is, what is your goal? Is your goal:</p><p>To get a degree?</p><p>Or to have a solid foundation?</p><p>In other words: do you want to work for companies that value a degree or your knowledge? Some companies won’t offer you a job unless you have a certain degree, while other companies might be more interested in your open source contributions and don’t care that much about your background. If you want to be a professor in the future then you’ll need the degree. Likewise, what if you wanted to work for the government? You’d probably need the degree, too.</p><h3>Can I learn to become a great developer without going to uni?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4RHkpG4528Vr1fSkp-wc0Q.jpeg" /></figure><p><strong>Student:</strong> But if I was being very honest with myself, I think I lack some of the basics like data structures, algorithms, patterns, and designs. Should I go to uni regardless of what you’ve just said?</p><p><strong>Alex:</strong> I did those things at uni. One of the data structures I remember well (or at least I believe so) is trees. A couple of weeks ago I had to traverse a tree to calculate some value. I Googled the algorithm and copied it from Stackoverflow.</p><p>Now, I don’t think the work process that you and I would follow here would be that much different. In fact, the only difference might be that you judge yourself for not knowing the algorithm and think that you should go to uni and learn it. But I went to uni, learned it and Googled it anyway! I don’t judge myself because I know that’s what a lot of devs do in the end.</p><p>But you raise an interesting point. This is a matter of confidence. It’s easier to be confident when you know what others do (those who went to uni in this case). It’s only then that we realize we are not that different at the end of the day. What I read from your message is you should work on your confidence.</p><h3>Do I need foundation knowledge to become a good programmer?</h3><p><strong>Student:</strong> I think that if I had the solid foundation that CS degrees provide then I could easily learn a new language and adapt to the market’s needs. Do you agree?</p><p><strong>Alex:</strong> I tend to agree that having a solid foundation will help you learn new things. The same can apply to people who want to learn human languages. I tried to learn other languages (English, Chinese, and French) and I saw in the classroom that those who had studied linguistics could learn faster than the ones who didn’t. The same applied to dancers. I’ve seen a guy who learned a lot of bachata and became very good but he struggles when learning salsa. However, another friend who had a foundation in dancing (understands body movement, spacing, timing, etc) learned the new dance faster.</p><p>Following the same analogies, to be a holistic dancer or linguist requires a lot of work. In my experience, in practice, no one in London cares if you are a linguist or which path you took as long as you can communicate in English well enough. In my experience dancing, no one on the dance floor cares if you have an amazing balance and can follow the bit in 2 different ways as long as you can dance bachata properly and connect with the other person.</p><p>To be honest, I’d love to have the skills of a professional dancer and linguist, but in practice, how many new dances and languages am I going to learn in the next ten years? Probably not many.</p><p>The point here is, is it worth the effort, in your case, to create that whole new foundation? Because we can learn a language without having the perfect foundation — it will take longer, sure, but eventually you’ll make it anyway.</p><p>If it helps, in my 15 years of professional experience I learned and worked as:</p><ul><li>A .NET back-end &amp; JS (vanilla and jQuery) front-end developer from 2004–2011</li><li>A PHP back-end &amp; JS front-end (Backbone, Angular) from 2011 to 2016</li><li>And a Node back-end &amp; React front-end from 2016 to 2019</li></ul><p>I’ve learned a lot of tools and frameworks but worked professionally with mainly 3 languages (.NET, PHP, and JS) in 15 years. I think the most difficult part was to leave the comforts of the first language (.NET) I used to make a living from and start again as a Juniorish PHP dev because I knew nothing about the new language, patterns, frameworks and ecosystem. I’m not sure how much uni helped me take that initial step to leave my .NET comfort zone.</p><p>Another point is that you don’t need a uni to create that foundation. All the knowledge taught by any university is probably available for free on the Internet. In my opinion, uni, or any other counterpart for this purpose, should give you the structure, consistency, and guidance/mentorship to help you shape your skills. In the case of a CS degree, it will probably shape your thinking in a more critical, abstract and analytical way. At least that’s what I got from the university.</p><p>It’s probably true that depending on the uni/organisation that you choose, it’ll shape your thinking in a given “school of thought”. Example, if you chose a CS degree in Stanford or you chose a CS degree in the public university of Barcelona, at the end of both you might get similar knowledge if you end up choosing similar curriculums, but you won’t necessarily think the same way. I’m not judging one will be better than the other one. I’m saying that, hypothetically, the same person who builds software for a given business problem could end up with radically different solutions based on which of the two universities she/he went to.</p><p>Like I say, I’m a strong believer in having structure, consistency and guidance in learning because that takes us further faster. University provided that for me, as well as other things. For instance, I think my English would be much worse if I hadn’t had feedback pointing out things I couldn’t hear, or I didn’t have certain role models that guided me and showed me what I could do. That’s actually the reason I founded React GraphQL Academy: to provide the structure, consistency, and guidance for developers who want to go further and faster in React and GraphQL.</p><h3>3 Questions to Ask Yourself</h3><p>Taking everything I’ve said on board, I think there are three questions you need to answer before you choose to take on a Computer Science degree if you want to learn how to become a developer.</p><p>1) What type of company would you like to work for?</p><p>If the company values a degree over knowledge and a can-do approach to development, you have your answer.</p><p>2) What are the skills those people that work for those companies right now have?</p><p>Look at the companies you aspire to work for and see what skills their current dev team — then:</p><p>3) How do you level up your skills to get on par with that team?</p><p>Find one of the people in the team you want to join and ask them how they got their skills and if they’ll be your mentor (I’m not sure how likely it is they’ll mentor you, but if you don’t ask you won’t know).</p><h3>Developer Training with <a href="https://reactgraphql.academy/">React GraphQL Academy</a></h3><p>At React GraphQL Academy, we aim to upskill developers who want to learn one of the best and most up-and-coming languages today: React and GraphQL. If you or your team are currently looking to expand your skill set, our array of training programs are here to help. From week-long intensive bootcamps to part-time courses, we can work to your schedule to ensure you deliver the highest quality work possible.</p><p>Check out our <a href="https://reactgraphql.academy/react/training/bootcamp/">Bootcamps</a> and <a href="https://reactgraphql.academy/react/training/">training courses</a> today!</p><p>Want to find out more? You can also contact our friendly team for a chat.</p><h3>A Quick Aside</h3><p>Disclaimer: I just wanted to point out that while I believe wholeheartedly in everything I said in this conversation with a former student, I did take a Computer Engineering degree at a public university in Barcelona. However, although I completed all the lectures and successfully passed all the exams I didn’t get my degree because I didn’t complete my graduation thesis.</p><p><em>Originally published at </em><a href="https://reactgraphql.academy/blog/ask-alex-do-i-need-a-cs-degree-to-become-a-good-developer"><em>https://reactgraphql.academy</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8dc3b1372070" width="1" height="1" alt=""><hr><p><a href="https://medium.com/react-graphql-academy/ask-alex-do-i-need-a-cs-degree-to-become-a-good-developer-8dc3b1372070">Ask Alex: Do I need a CS degree to become a good developer?</a> was originally published in <a href="https://medium.com/react-graphql-academy">React GraphQL Academy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 reasons why advanced dev training will keep your company tech-relevant]]></title>
            <link>https://medium.com/react-graphql-academy/5-reasons-why-advanced-dev-training-will-keep-your-company-tech-relevant-37b9bbc7b062?source=rss-d71a82789a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/37b9bbc7b062</guid>
            <category><![CDATA[developers-training]]></category>
            <category><![CDATA[team-training]]></category>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[corporate-training]]></category>
            <category><![CDATA[xing]]></category>
            <dc:creator><![CDATA[Alex Lobera]]></dc:creator>
            <pubDate>Mon, 21 Oct 2019 08:19:00 GMT</pubDate>
            <atom:updated>2019-10-21T08:19:00.788Z</atom:updated>
            <content:encoded><![CDATA[<p>On this page:</p><ul><li>1) You’ll motivate your team, <a href="https://reactgraphql.academy/blog/5-reasons-why-advanced-dev-training-will-keep-your-company-tech-relevant/#1_youll_motivate_your_team">go to section</a>.</li><li>2) You’ll standardise knowledge in your team, <a href="https://reactgraphql.academy/blog/5-reasons-why-advanced-dev-training-will-keep-your-company-tech-relevant/#2_youll_standardise_knowledge_in_your_team">go to section</a>.</li><li>3) You’ll empower your team, <a href="https://reactgraphql.academy/blog/5-reasons-why-advanced-dev-training-will-keep-your-company-tech-relevant/#3_youll_empower_your_team">go to section</a>.</li><li>4) You’ll promote greater teamwork, <a href="https://reactgraphql.academy/blog/5-reasons-why-advanced-dev-training-will-keep-your-company-tech-relevant/#4_youll_promote_greater_teamwork">go to section</a>.</li><li>5) You’ll optimise your team’s output, <a href="https://reactgraphql.academy/blog/5-reasons-why-advanced-dev-training-will-keep-your-company-tech-relevant/#5_youll_optimise_your_teams_output">go to section</a>.</li></ul><p>With advanced dev training, you can equip your team with the knowledge to satisfy their professional curiosity and take your company further. Why is that? We caught up with one of our clients, <a href="https://www.xing.com/profile/Eber_Herrera/cv">Eber Herrera</a>, Technical Director from Xing, to find out why he and his team found our in-house advanced dev training valuable.</p><p>So here’s our breakdown of the top reasons why advanced dev training will keep your team and company tech-relevant.</p><h3>1) You’ll motivate your team</h3><p>One of the best ways to keep your team tech-relevant is to get everyone motivated, and training is a great way of doing that.</p><p>It teaches everyone new, more effective ways to develop apps in React. It gets them excited to try out new things and to build even better products.</p><p>Passionate coaches play a key part in getting your team motivated, and the pay off is huge. For instance, during a week-long intensive course at Xing,we delivered React training that was tailored to the team’s needs. After, Eber said:</p><blockquote><em>The team is really motivated. We got what we wanted, which is that now our team discusses things in a different way. They’re more into the idea of doing things in the best way possible without compromising speed. […] They want to do their job well.</em></blockquote><h3>2) You’ll standardise knowledge in your team</h3><p>Miscommunication is a killer in any business, but it can be especially costly in tech.</p><p>For instance, you could have one team member who knows how to style in React, but doesn’t have the terminology to communicate his or her ideas to the rest of the team. This could become a bottleneck in the business, with products held up should another team member have to take over.</p><p>But advanced dev training helps you standardise knowledge across your team. Not only does that improve communication, it also improves your team’s performance.</p><blockquote><em>It shakes the tree,” said Eber. “For those who were falling behind a little bit, they now have a feeling like they understand why they have to do better and how there is so much more to their role.</em></blockquote><p>Your team can evolve and develop together, helping each other (as well as the company) to stay tech-relevant.</p><h3>3) You’ll empower your team</h3><p>A team that feels appreciated is one that you invest time and resources in. If you set aside time to train and upskill your team, you’re making sure they know you appreciate them and want to develop their skills.</p><p>But it isn’t just about keeping your team happy. If you empower your team through training, they’ll be more loyal and less likely to move companies to advance.</p><blockquote><em>At Xing, we have a collaborative environment,” said Eber. “We invest in training because, in the end, it pays off.</em></blockquote><p>It motivates everyone and makes them feel good about their work.</p><h3>4) You’ll promote greater teamwork</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*iLDHgNg86TotcdSsY6fVQg.jpeg" /></figure><p>Conferences are great, but you can only ever send a handful of staff at any one time.</p><p>However, in-house dev training will see your entire team benefit. We’ve established that courses like this will standardise knowledge, but what we haven’t said is that it will promote greater teamwork, too.</p><p>Eber said advanced dev training is a no-brainer.</p><blockquote><em>If you asked me if I would put my team in for this sort of training instead of a conference, I would say yes. I think it’s way deeper, you learn a lot more and, in the end, your team gets back way more rewarded.</em></blockquote><p>That’s because it actually bridged the knowledge gaps his team had and equipped everyone with the language they needed to discuss projects with each other. Soon, Eber’s team discussed things differently, trying to find better ways to build and maintain apps.</p><h3>5) You’ll optimise your team’s output</h3><p>For a company like Xing, data is the be-all and end-all.</p><blockquote><em>The only thing we work with is data and a nice UI, that’s what we deliver, so we need to stay relevant there,” said Eber. “The only way to do that is to use the right tools in the right way.</em></blockquote><p>Advanced dev training is how you make that happen. When your dev team knows how to use tools like React properly, your team doesn’t only deliver work on time and to spec: your company benefits by getting products to market faster, too.</p><p>Most importantly, when your processes are faster, you can set aside more time to develop your team, making them more efficient and more tech-relevant.</p><p>It’s clear that advanced dev training has a lot of benefits, and that’s why we do what we do. At React GraphQL Academy, we work alongside your team to deliver effective, tailored ReactJS training courses. Our <a href="https://reactgraphql.academy/react/training/corporate/">Corporate Team Training</a> course was a hit with Eber and his team at <a href="https://www.xing.com/">Xing</a>, so what are you waiting for? Contact us today to keep your team and company tech-relevant with our ReactJS training courses.</p><p>You can reach Eber Herrera on <a href="https://twitter.com/eberhm">Twitter</a>, <a href="https://www.linkedin.com/in/eberhm/">LinkedIn</a> and <a href="https://www.xing.com/profile/Eber_Herrera/cv">Xing</a></p><p>Find below the video of the interview if you want to watch the full interview</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FL-QTtmoLWd8%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DL-QTtmoLWd8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FL-QTtmoLWd8%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/01aed5fa1f9c2ee026162a039fa8f33a/href">https://medium.com/media/01aed5fa1f9c2ee026162a039fa8f33a/href</a></iframe><p><em>Originally published at </em><a href="https://reactgraphql.academy/blog/5-reasons-why-advanced-dev-training-will-keep-your-company-tech-relevant/"><em>https://reactgraphql.academy</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37b9bbc7b062" width="1" height="1" alt=""><hr><p><a href="https://medium.com/react-graphql-academy/5-reasons-why-advanced-dev-training-will-keep-your-company-tech-relevant-37b9bbc7b062">5 reasons why advanced dev training will keep your company tech-relevant</a> was originally published in <a href="https://medium.com/react-graphql-academy">React GraphQL Academy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The number one reason that will make you want to test your code]]></title>
            <link>https://medium.com/react-graphql-academy/the-number-one-reason-that-will-make-you-want-to-test-your-code-f63214c46bf0?source=rss-d71a82789a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/f63214c46bf0</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[writing-software]]></category>
            <dc:creator><![CDATA[Alex Lobera]]></dc:creator>
            <pubDate>Tue, 01 Oct 2019 15:21:36 GMT</pubDate>
            <atom:updated>2019-10-01T15:21:36.960Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XuSvGYakGM-VqsDVFphbfg.jpeg" /></figure><p>On this page:</p><ul><li>Writing software is complex, <a href="https://reactgraphql.academy/blog/the-number-one-reason-that-will-make-you-want-to-test-your-code/#writing_software_is_complex">go to section</a>.</li><li>Writing tests makes everyone happier, <a href="https://reactgraphql.academy/blog/the-number-one-reason-that-will-make-you-want-to-test-your-code/#writing_tests_makes_everyone_happier">go to section</a>.</li></ul><h3>Writing software is complex</h3><p>I teach advanced coding to professional developers from all over the world, and it’s surprising to me the number of developers that write very few tests for the software they build. There are many reasons for this, and I’m not here to point anyone out, instead, I’d like to share with you what I’ve found to be the number one reason that makes me, in practice, want to test the software I build.</p><p>First, let me tell you something about who I am, I’m a software engineer with 15 years of experience and I am extremely good, I’m very very very good… at writing bad code… on the first try. But I think I’m not alone.</p><h3>Addy Osmani on Twitter</h3><p>First do it, then do it right, then do it better - this is my mantra for successfully getting things done. It&#39;s all about the iteration.</p><p>Why is it so hard to build it right on the first try and so we need to iterate? The good news is it’s not because of us developers :), it’s because of the nature of building software. Building software is a complex problem.</p><p>I’m going to define complexity in the context of this article as the “unknown unknowns”, meaning cause and effect can only be deduced in retrospect. In other words, when we build software, a human believes that there is a problem to be solved. The problem needs to be defined and explained to other humans (unless it’s both built and used by only one person). Then, other humans design and implement the right solution to the problem. Finally, even if all the previous steps were executed perfectly, it could be that the problem was not actually a problem or that before the right solution is implemented the problem changed. Building software is an exploratory process because of its complex nature. That’s why we build it iteratively.</p><h3>Writing tests makes everyone happier</h3><p>It seems that the more tests we write, the more we can iterate. Let’s list the main reasons for which writing tests will help us iterate more, but also the people who will directly benefit from that:</p><p>- Test automation. This means faster deployment and fewer bugs. Reliable products, happier users.</p><p>- Adapt to change. We can add new features or change existing ones faster. That makes all the product owners and stakeholders that I know happier.</p><p>- Understanding and documenting code. This is good for onboarding new developers. Now we’ve got happier colleagues because it’s easier to understand the new code base they’ll work on.</p><p>- Last but not least, there is a reason that will likely make you, the developer who implements the feature, happier. Code refactoring.</p><h4>Code refactoring</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y95faHyiobHuLEXXpWeeZQ.png" /></figure><p>Code refactoring is in very simple words, making something that already works, better, without changing what it does. I don’t know about you but I feel an extreme pleasure every time I can improve something I built before.</p><p>The more we iterate, the closer we are to the optimal solution. The goal is not to get to the optimal solution, but to be good enough at different points in time.</p><p>In my view, a senior developer is such that understands the complexity of our job and so plans for successful future change to minimize the cost of that unknown change, now. Experience can be defined as the knowledge you learn after you need it. Writing tests is a key tool to help you with that process.</p><p>If you would like to brush up your unit testing skills using JavaScript, check out this <a href="https://reactgraphql.academy/react/unit-testing-fundamentals-explained-using-javascript/">article about unit testing explained with JavaScript</a>. You can also read this other <a href="https://reactgraphql.academy/react/testing-react-applications/">article about testing React apps</a> if you would like to focus on unit testing and integration testing in React.</p><p><em>Originally published at </em><a href="https://reactgraphql.academy/blog/the-number-one-reason-that-will-make-you-want-to-test-your-code/"><em>https://reactgraphql.academy</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f63214c46bf0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/react-graphql-academy/the-number-one-reason-that-will-make-you-want-to-test-your-code-f63214c46bf0">The number one reason that will make you want to test your code</a> was originally published in <a href="https://medium.com/react-graphql-academy">React GraphQL Academy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Testing React applications]]></title>
            <link>https://medium.com/react-graphql-academy/testing-react-applications-6e209f5797d7?source=rss-d71a82789a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e209f5797d7</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[codingbootcamp]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[react-js-development]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Alex Lobera]]></dc:creator>
            <pubDate>Tue, 01 Oct 2019 14:28:09 GMT</pubDate>
            <atom:updated>2019-10-01T15:08:04.817Z</atom:updated>
            <content:encoded><![CDATA[<h4>In this article you are going to learn what is the best approach to test your React components. The bad news is that I’m not going to directly tell you what the best approach is. The good news is that by the end of the article you should be able to make your own informed decisions about what’s the most “elegant” approach for your code.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YUBp5y80hcrrH_bq" /></figure><p>On this page:</p><ul><li>Testing approaches, <a href="https://reactgraphql.academy/#testing_approaches">go to section</a>.</li><li>Focusing the discussion, unit test vs integration test, <a href="https://reactgraphql.academy/#focusing_the_discussion_unit_test_vs_integration_test">go to section</a>.</li><li>Principles, <a href="https://reactgraphql.academy/#principles">go to section</a>.</li><li>Compare and contrast, <a href="https://reactgraphql.academy/#compare_and_contrast">go to section</a>.</li></ul><h3>Testing approaches</h3><p>The most common types of tests we write are end-to-end (AKA e2e), integration tests, and unit tests. e2e executes a user interaction from one end to the other end. For instance, a user logging in interaction requires from a real browser (one end) to the database (the other end). The e2e will test any code in between both ends.</p><p>A unit test tests a unit of code. For the purpose of this article, which is focused on testing in React, I’ll refer to a unit as a React component. So in this context, unit means a glob of UI that’s intended to be used. Discussing what a “unit” of code is can be an article in itself. No worries, we’ve got that <a href="https://reactgraphql.academy/react/unit-testing-fundamentals-explained-using-javascript/">article</a>. An integration test is a test that tests anything in between the other two.</p><p>There are different approaches to test a React app based on some variation of those 3 types of tests. Let’s see some of these variations:</p><h4>Test Pyramid</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Pf8An3DvaOOJLRAa5eGJg.png" /></figure><p>This approach tells us that we should write mostly unit tests, followed by fewer integration tests, and even fewer e2e tests.</p><p>There are two main reasons we should not write too many e2e tests according to this approach. First, e2e is slow because it tests a lot of things, and it requires other software to run, such as a browser, database, etc to complete the test. Second, e2e tests are fragile in the sense that if any of the many pieces it tests in one go fails, then the entire e2e test will fail.</p><p>On the opposite of the e2e side of the pyramid there is unit testing. Unit tests run fast because they don’t require many resources to run. Unit tests are less fragile because they test small parts of code independently. If a unit test fails, it should fail in isolation and not affect the other unit tests.</p><p>Mike Cohn coined the term Test Pyramid in his book “Succeeding with Agile”, first published in 2009. Many companies follow this approach nowadays. However, many things can happen in 10 years in the software industry, for instance, e2e tools have improved significantly since then. Therefore, being used by many for many years doesn’t mean we should not question it.</p><h4>Aaron Square</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2XpDD7FgklovMxpjkuCHSQ.jpeg" /></figure><p>Another approach is the Aaron Square, introduced in early 2018 by Aaron Abramov. If we follow this approach we should then write the same amount of e2e tests, integration tests, and unit tests.</p><h4>Kent C. Dodds Trophy</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mQW0dDai_U9pRLlgFCLTLw.png" /></figure><p>Another approach is the Kent C. Dodds Trophy, introduced in early 2018. In this approach, we should write more integration tests than unit tests and e2e tests, followed by a static type checking (TypeScript, Flow, eslint, etc).</p><h3>Focusing the discussion, unit test vs integration test</h3><p>In this article, we are focusing on the discussion of integration tests versus unit tests in React. E2E tests and static types are agnostic of the library or framework that we chose to build the UI. We can use Cypress and TypeScript with Angular or Vue for instance.</p><p>If you wonder why then I explained e2e in this long intro, it’s because I want to stimulate your critical thinking and question some of the beliefs you might have around testing. Presenting you 3 different established approaches from 3 different experts sets a nice ground for questioning.</p><p>Therefore our final questions could be, <strong>should we write more unit tests than integration tests? or the other way around? Maybe fifty-fifty?</strong></p><p>Once I had the good fortune to get trained by Kyle Simpson, and did pair programming with him. I asked him: “Kyle, do you write more unit tests or integration tests?”. He replied something along the lines: “obviously, I write more integration tests”. 🤔… When I asked him why, he replied “…users never use units. Those units are always composed with other units to achieve some greater functionality that users will use. Therefore it is more valuable to test how those pieces work together rather than testing them in isolation.”</p><p>There are different opinions when it comes to testing, even among respected developers. So, what should we do?</p><h3>Principles</h3><p>It seems we can’t all agree on the right testing approach. Different experts have different opinions. I also have my own opinion, which I won’t tell you. Instead, I’ll tell you what’s the criteria and principles I use to compare them.</p><h4>Have a criteria</h4><p>First things first, let’s define a criteria. To me, a good test is such that:</p><ul><li>I can refactor my code without changing my tests. Which <a href="https://reactgraphql.academy/blog/the-number-one-reason-that-will-make-you-want-to-test-your-code/#writing_tests_makes_everyone_happier">makes me happier.</a></li><li>It gives me a high degree of confidence that the code I write works as intended.</li></ul><p>This is my criteria. I encourage you to have your own. Most likely, you don’t spend 100% of your time as a developer writing tests (I hope, neither, the opposite), but writing good tests is highly influenced by the quality of the code being tested. Therefore, having criteria about what makes a good test will guide us in everyday code-related decision making.</p><h4>Testing the “what” as opposed to the “how”</h4><p>Testing <strong>what</strong> the code does means that the code we write to test some other code knows no implementation details of the code being tested. If we test the “what”, then we can refactor the test subject without changing the tests associated with it.</p><p>Testing <strong>how </strong>the code being tested works means I’ll likely need to change the test when I refactor the code being tested. In other words, the test knows implementation details of the test subject.</p><p>Based on my criteria, testing the “what” is better. The “what” and the “how” is also known as <a href="https://reactgraphql.academy/react/unit-testing-fundamentals-explained-using-javascript/#white_box_testing_vs_black_box_testing">black-box testing and white-box testing</a>, being the “what” the black box, and the “how” the white box.</p><h4>Adapting to change</h4><p>We know <a href="https://reactgraphql.academy/blog/the-number-one-reason-that-will-make-you-want-to-test-your-code/#writing_software_is_complex">writing software is complex</a>, and so it’s likely that tomorrow we’ll need to change the code we write today. Let’s embrace the change.</p><p>One principle many of us follow when building software is to build small independent units that can be reused, like Lego pieces (oops I used a cliché 🤭). The problem is, depending on how we wire those units together, it’ll be difficult to unwire them in our tests at our convenience.</p><p>“Unwire them in our tests at our convenience” — yes I’m suggesting we should consider adapting the code to the tests, 😱. You might think that’s fundamentally wrong. Theoretically, I could agree. In practice, if that adjustment significantly improves my refactoring, and increases my confidence at almost no time-cost, then I tend to disagree we should never do it. But! I understand you might have a different criteria, which is perfectly fine if it works for you.</p><h4>Dependency Injection</h4><p>Dependency Injection (also referred as the broader technique of inversion of control) is a technique whereby a glob of code (functionality) is supplied to a unit that depends on it in a way that the supplied functionality can be replaced by any other before or at runtime.</p><p>An example of this can be a React component that fetches some data from an API when the component mounts. When the app runs on the user’s browser, we want the component to connect to the API. If, for instance, in our test environment the test didn’t have access to the API or it did but it was very slow, then when running the test we would want to replace the code that connects to the API with some other code that returns a response directly, without involving any network request.</p><p>To be clear, I’m not advocating Dependency Injection (DI). Based on the first principle I’m following, testing the “what” and not the “how”, DI persé is not a good thing. The reason is, every time I inject a dependency it means I know something about how the functionality is implemented. From a pure black-box perspective, I shouldn’t even know that the code I’m testing has a dependency.</p><p>DI can minimize a problem, but the problem will still be there. As long as our apps have side-effects (the problem) — and <a href="https://reactgraphql.academy/react/unit-testing-fundamentals-explained-using-javascript/#what_we_will_never_see_in_theory">I haven’t seen one app without any side effect</a> — we’ll have to somehow deal with that.</p><p>Designing our entire application around DI, like some frameworks as Angular do, could encourage implementations that make refactoring and testing tedious in my experience, which defeats its purpose. However, I think DI is a good tool used wisely.</p><h3>Compare and contrast</h3><p>Enough talking, let’s compare some code in this video:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FxjP3Ll1UhEw%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DxjP3Ll1UhEw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FxjP3Ll1UhEw%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/eb20661370089b43d759378ee1a400e3/href">https://medium.com/media/eb20661370089b43d759378ee1a400e3/href</a></iframe><p><em>Originally published at </em><a href="https://reactgraphql.academy/react/testing-react-applications"><em>https://reactgraphql.academy</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e209f5797d7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/react-graphql-academy/testing-react-applications-6e209f5797d7">Testing React applications</a> was originally published in <a href="https://medium.com/react-graphql-academy">React GraphQL Academy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React forms controlled & uncontrolled components]]></title>
            <link>https://medium.com/@alexlobera/react-forms-controlled-uncontrolled-components-7842a7284dfa?source=rss-d71a82789a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/7842a7284dfa</guid>
            <category><![CDATA[final-form]]></category>
            <category><![CDATA[uncontrolled]]></category>
            <category><![CDATA[forms]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[components]]></category>
            <dc:creator><![CDATA[Alex Lobera]]></dc:creator>
            <pubDate>Sun, 10 Feb 2019 12:37:55 GMT</pubDate>
            <atom:updated>2019-02-10T14:07:13.238Z</atom:updated>
            <content:encoded><![CDATA[<h3>Controlled &amp; uncontrolled components, React forms and beyond</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/780/1*SLJI1ivoKwC6ji-PXIwEcg.jpeg" /></figure><p>React is a tool, not a Framework. React’s job is to render user interfaces. This means that React does not ship any code to make the creation of React forms easy. Other frameworks like Angular provide a form implementation that makes handling forms easier. You might like this or not, but that’s the way it is :) I personally think it’s good. React’s philosophy is to do one thing and do it well, but also and very important, to set the foundation and principles to lay down many other tools around that.</p><p>What is a web form? It’s a sort of container that holds some data (state) that can be sent to a server for processing. There are three main concerns forms will have to deal with:</p><ul><li>Handleing <strong>form validation</strong> of the data the user enters. React doesn’t provide any implementation for this.</li><li>Handling <strong>form submission</strong>. React doesn’t provide any implementation for this.</li><li>Getting values in and out of <strong>form state</strong>. There are two approaches that React provides to handle the state of the form called controlled and uncontrolled components</li></ul><h3>Form state</h3><p>The state of a form encompasses not only the value of each field (input, select, etc) but also the interaction between the user and the form itself. Here some examples:</p><ul><li>Which field currently has focus?</li><li>Which fields are dirty? Meaning the field has been changed since it was initialized</li><li>Which fields have errors?</li><li>Are we currently submitting?</li></ul><h3>Controlled and Uncontrolled components</h3><p>Heads up! Controlled/uncontrolled is a characteristic that doesn’t only have to do with forms. It has to do with how a component relates to some state. Therefore <strong>controlled and uncontrolled components have to do with components, not only with forms in React</strong>.</p><p>The reason I want to emphasize this is because most examples you find on the net use &lt;input/&gt; or &lt;select/&gt; to illustrate the concept, for instance, the <a href="https://reactjs.org/docs/forms.html">React official documentation</a>. I’ve observed that some React devs think that controlled and uncontrolled components only have to do with forms and inputs or selects. I want to make this clear. First, let’s discuss the “classic” controlled and uncontrolled example, and then let’s see other broader examples.</p><p><strong>Uncontrolled component</strong> , the component owns the state.</p><p><strong>Controlled component</strong> , the component does not own the state.</p><p>Is the following component controlled or uncontrolled? Can you type “hello” in it?</p><pre>&lt;input<br>    style={{ padding: 8, margin: 8 }}<br>    placeholder=&quot;type here!&quot;<br>/&gt;</pre><p><a href="https://reactjs.academy/blog/react-forms-controlled-and-uncontrolled-components/#live-example-1"><em>See the previous code example in a React live editor</em></a></p><p>The previous input is uncontrolled because we are not setting any state to it. In other words, we are not setting the “value” prop. The value (state) is managed internally by the input.</p><p>Is the following component controlled or uncontrolled? Can you type “hello” in it?</p><pre>&lt;input<br>    style={{ padding: 8, margin: 8 }}<br>    value=&quot;type here!&quot;<br>/&gt;</pre><p><a href="https://reactjs.academy/blog/react-forms-controlled-and-uncontrolled-components/#live-example-2"><em>See the previous code example in a React live editor</em></a></p><p>The previous input is controlled because we (some parent component) are setting its state. In other words, we are setting the “value” prop. The value (state) is hardcoded to “type here!” therefore it never changes even when you type on it because we are saying all the time to the input your value is “type here!” regardless of what you type.</p><p>Is the following component controlled or uncontrolled? Can you type “hello” in it?</p><pre>&lt;input<br>    style={{ padding: 8, margin: 8 }}<br>    placeholder=&quot;type here!&quot;<br>    value=&quot;&quot;<br>/&gt;</pre><p><a href="https://reactjs.academy/blog/react-forms-controlled-and-uncontrolled-components/#live-example-3"><em>See the previous code example in a React live editor</em></a></p><p>The previous input is controlled because we are setting the “value” prop to an empty string. The value (state) is hardcoded to “” therefore it never changes even when you type on it.</p><p>Is the following component controlled or uncontrolled? Can you type “hello” in it?</p><pre>&lt;input<br>    style={{ padding: 8, margin: 8 }}<br>    defaultValue=&quot;type here!&quot;<br>/&gt;</pre><p><a href="https://reactjs.academy/blog/react-forms-controlled-and-uncontrolled-components/#live-example-4"><em>See the previous code example in a React live editor</em></a></p><p>The previous input is uncontrolled because we are not setting the “value” prop. We are setting the defaultValue which is the initial value set internally in the input state. Since we are not controlling the value of the input it changes even when you type on it.</p><h3>Example of a Login form with controlled components</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodesandbox.io%2Fembed%2F712kk1y7o1&amp;url=https%3A%2F%2Fcodesandbox.io%2Fs%2F712kk1y7o1&amp;image=https%3A%2F%2Fcodesandbox.io%2Fapi%2Fv1%2Fsandboxes%2F712kk1y7o1%2Fscreenshot.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=codesandbox" width="1000" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/1ba661693aa215fdff704ab7a336f731/href">https://medium.com/media/1ba661693aa215fdff704ab7a336f731/href</a></iframe><p>React recommends in most cases to use controlled components to handle a form. It might look like React makes forms harder because all the work we need to do to handle the state. React makes it easier to change the UI — like hiding and displaying divs — and forms seem harder by comparison.</p><blockquote><em>“React exposed the inherent complexity of forms interactions that was always there” — </em><a href="https://twitter.com/jordwalke"><em>Jordan Walke</em></a><em>, creator of ReactJS.</em></blockquote><h3>Form library</h3><p>We recommend you to use an external <strong>library to implement forms in React</strong>. The library we recommend at ReactJS Academy and we use at <a href="https://leanjs.com/">LeanJS</a> with our client work is <a href="https://github.com/final-form/react-final-form">Final Form</a>. The reasons we recommend Final Form over other libraries are:</p><ul><li>Very small. Almost half of the size of Formik or 5 times smaller than Redux Form at the time of this article.</li><li>Pure JavaScript, no dependencies with other libraries</li><li>Very decoupled behavior and UI with simple components and clean APIs.</li><li>Very modular with its built in plugin system</li><li>Subscriptions based. Though this feature is only relevant in cases of extreme performance.</li></ul><p>Quoting the React documentation about these form libraries, they are <a href="https://reactjs.org/docs/forms.html#fully-fledged-solutions">“built on the same principles of controlled components and managing state — so don’t neglect to learn them (the principles)”</a></p><h3>Controlled and uncontrolled beyond forms</h3><p>Controlled components require more code, while uncontrolled components are the opposite. Let’s have a look at some code and analyze why that’s the case.</p><p>The following code is what the documentation of <a href="https://react-bootstrap.github.io/components/modal/#modals-live">React Bootstrap</a> says we need to do in order to use its modal. Do you think this modal is a controlled or uncontrolled component?</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodesandbox.io%2Fembed%2F9zkqkjn2zy&amp;url=https%3A%2F%2Fcodesandbox.io%2Fs%2F9zkqkjn2zy&amp;image=https%3A%2F%2Fcodesandbox.io%2Fapi%2Fv1%2Fsandboxes%2F9zkqkjn2zy%2Fscreenshot.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=codesandbox" width="1000" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/2a62dfd88d3bd944c1b0b7b6ddf12bba/href">https://medium.com/media/2a62dfd88d3bd944c1b0b7b6ddf12bba/href</a></iframe><p>The previous Modal is a controlled component.</p><p>Now let’s have a look at the following implementation of another modal extending the previous modal thanks to the React composition model. Is the following modal controlled or uncontrolled?</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodesandbox.io%2Fembed%2F30v2n85q55&amp;url=https%3A%2F%2Fcodesandbox.io%2Fs%2F30v2n85q55&amp;image=https%3A%2F%2Fcodesandbox.io%2Fapi%2Fv1%2Fsandboxes%2F30v2n85q55%2Fscreenshot.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=codesandbox" width="1000" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/e256b6dac0ed8479bee4b6c2b768597c/href">https://medium.com/media/e256b6dac0ed8479bee4b6c2b768597c/href</a></iframe><p>The previous Modal is an uncontrolled component.</p><p>Which modal is easier to reuse in different projects? The second one (the uncontrolled one). Why? Because the state is handled by the modal itself so we don’t need to do any extra work to reuse the modal.</p><h3>Controlled vs uncontrolled components</h3><p>So which is better, controlled or uncontrolled components? It depends on the use case. Controlled components obviously give you more, well, control. Controlled components give you direct access to the state, so if you need to perform tasks like validating that state, it’s really easy since you own the state. Uncontrolled components are easier to reuse with minimal setup. If your app doesn’t need to know about the state of the component, like in the case of the modal, uncontrolled components will be simpler to use.</p><p>A good component is one that can be either controlled or uncontrolled. Think of an &lt;input/&gt; itself. If you provide a value, the input becomes controlled. If you don’t provide a value, the input becomes uncontrolled.</p><p>This <a href="https://github.com/negomi/react-burger-menu">burger menu</a> is a good example. It’s implemented in a way that can be either controlled or uncontrolled.</p><p>&lt;Menu/&gt; // <a href="https://github.com/negomi/react-burger-menu#usage">this is uncontrolled</a></p><p>&lt;Menu isOpen={this.state.isOpen}/&gt; // <a href="https://github.com/negomi/react-burger-menu#open-state">this is controlled</a></p><h3>Conclusion</h3><ul><li><a href="https://reactjs.academy/blog/react-forms-controlled-and-uncontrolled-components/#uncontrolled-component">Uncontrolled component</a>, the component owns the state.</li><li><a href="https://reactjs.academy/blog/react-forms-controlled-and-uncontrolled-components/#controlled-component">Controlled component</a>, the component does not own the state.</li><li>A <a href="https://reactjs.academy/blog/react-forms-controlled-and-uncontrolled-components/#form-library">third-party form library</a> will help you submit, validate, and manage the state of the form (including user interactions)</li><li>The concept of controlled and uncontrolled component goes <a href="https://reactjs.academy/blog/react-forms-controlled-and-uncontrolled-components/#controlled-uncontrolled-beyond-forms">beyond forms, it applies to any component not only form fields like inputs, select, etc</a></li><li>A <a href="https://reactjs.academy/blog/react-forms-controlled-and-uncontrolled-components/#controlled-vs-uncontrolled">well designed component has the flexibility to be used either controlled or uncontrolled</a> depending on the use case.</li></ul><p><em>Originally published at </em><a href="https://reactjs.academy/blog/react-forms-controlled-and-uncontrolled-components"><em>reactjs.academy</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7842a7284dfa" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>