{"id":334281,"date":"2021-09-03T12:21:49","date_gmt":"2021-09-03T09:21:49","guid":{"rendered":"https:\/\/en.buradabiliyorum.com\/struggling-to-elevate-your-programming-try-mastering-these-two-mindsets\/"},"modified":"2021-09-03T12:21:49","modified_gmt":"2021-09-03T09:21:49","slug":"struggling-to-elevate-your-programming-try-mastering-these-two-mindsets","status":"publish","type":"post","link":"https:\/\/buradabiliyorum.com\/en\/struggling-to-elevate-your-programming-try-mastering-these-two-mindsets\/","title":{"rendered":"#Struggling to elevate your programming? Try mastering these two mindsets"},"content":{"rendered":"<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_84 counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<label for=\"ez-toc-cssicon-toggle-item-6a2f740fc84b2\" class=\"ez-toc-cssicon-toggle-label\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #dd3333;color:#dd3333\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #dd3333;color:#dd3333\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/label><input type=\"checkbox\"  id=\"ez-toc-cssicon-toggle-item-6a2f740fc84b2\" checked aria-label=\"Toggle\" \/><nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/buradabiliyorum.com\/en\/struggling-to-elevate-your-programming-try-mastering-these-two-mindsets\/#My_recent_journey\" >My recent journey<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/buradabiliyorum.com\/en\/struggling-to-elevate-your-programming-try-mastering-these-two-mindsets\/#Two_Mindsets\" >Two Mindsets<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/buradabiliyorum.com\/en\/struggling-to-elevate-your-programming-try-mastering-these-two-mindsets\/#Way_of_the_Architect\" >Way of the Architect<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/buradabiliyorum.com\/en\/struggling-to-elevate-your-programming-try-mastering-these-two-mindsets\/#Way_of_the_Adapter\" >Way of the Adapter<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/buradabiliyorum.com\/en\/struggling-to-elevate-your-programming-try-mastering-these-two-mindsets\/#Is_one_mindset_better_than_the_other\" >Is one mindset better than the other?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/buradabiliyorum.com\/en\/struggling-to-elevate-your-programming-try-mastering-these-two-mindsets\/#Switching_between_the_two_mindsets\" >Switching between the two mindsets<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/buradabiliyorum.com\/en\/struggling-to-elevate-your-programming-try-mastering-these-two-mindsets\/#Some_tips\" >Some tips<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/buradabiliyorum.com\/en\/struggling-to-elevate-your-programming-try-mastering-these-two-mindsets\/#Be_mindful_of_the_way_youre_thinking_when_working_on_a_task\" >Be mindful of the way you\u2019re thinking when working on a task<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/buradabiliyorum.com\/en\/struggling-to-elevate-your-programming-try-mastering-these-two-mindsets\/#If_you_find_you_made_a_mistake_because_you_werent_in_the_right_mindset_dont_sweat_it\" >If you find you made a mistake because you weren\u2019t in the right mindset, don\u2019t sweat it<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/buradabiliyorum.com\/en\/struggling-to-elevate-your-programming-try-mastering-these-two-mindsets\/#Reflect_on_your_process\" >Reflect on your process<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/buradabiliyorum.com\/en\/struggling-to-elevate-your-programming-try-mastering-these-two-mindsets\/#Conclusion\" >Conclusion<\/a><\/li><\/ul><\/nav><\/div>\n<p>&#8220;<strong>#Struggling to elevate your programming? Try mastering these two mindsets<\/strong>&#8221;<br \/>\n<img decoding=\"async\" src=\"https:\/\/img-cdn.tnwcdn.com\/image?fit=796%2C417&amp;url=https%3A%2F%2Fcdn0.tnwcdn.com%2Fwp-content%2Fblogs.dir%2F1%2Ffiles%2F2021%2F08%2Fcharlein-gracia-mqKKCsZgzXQ-unsplash.jpg&amp;signature=7948f6a089f82b4a4d7ad1224b84a2fd\" \/><\/p>\n<div><span style=\"font-weight: 400;\">When a developer <a href=\"https:\/\/buradabiliyorum.com\/en\/category\/download-scripts-themes-apps\/\" data-internallinksmanager029f6b8e52c=\"9\" title=\"Download Scripts &amp; Themes &amp; Apps\" target=\"_blank\" rel=\"noopener\">app<\/a>roaches a problem, they usually have a clear objective. Fix this bug, create that component, refactor this implementation. We\u2019re very goal oriented by nature. We have an objective that we need to get to, and we have to try all the techniques we\u2019ve learned in order to hit that mark. But something that I feel is less discussed is the mindset of a developer: the <\/span><i><span style=\"font-weight: 400;\">way<\/span><\/i><span style=\"font-weight: 400;\"> we think, rather than <\/span><i><span style=\"font-weight: 400;\">what<\/span><\/i><span style=\"font-weight: 400;\"> we think, in order to solve a coding problem.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">I want to share some thoughts on two specific mindsets that I realized I\u2019ve been oscillating between for most of my career. But here\u2019s the funny part\u2026I rarely noticed when I was switching between them. Looking back on it, had I realized this paradigm, I might have been able to save myself hours of thinking about the perfect solutions to problems.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">To give you an idea of the different stages of software development, I\u2019ll give a bit of backstory to the project I\u2019ve been working on. Afterwards, we\u2019ll examine the two programmer mindsets more closely. Finally, I\u2019ll present some tips on how to utilize the two approaches and how to be more mindful in the process.<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"My_recent_journey\"><\/span><strong>My recent journey<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Right now, my team is at an interesting point in our long journey. Since June 2019, we\u2019ve been migrating the Just Eat Takeaway.com food ordering web application to a modern stack of Next.js, React, and Redux Saga. Over the past year, our team has grown to the point where it\u2019s become beneficial to split into smaller teams with a more specialized set of responsibilities.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">We first started by building the menu &amp; checkout pages of the website. These included the header elements, including location search and account login, and also the menu, cart, and the order submission mechanism.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Over the next 1.5 years, I moved from the team responsible for the menu &amp; checkout experience to the restaurant list page where the user picks which establishment they want to order from. Our main challenge for this page was implementing the various filters and sorting mechanisms. After finishing the restaurant list page, I pivoted to the team that handles the development of the common components of the entire website (header, footer, account login, etc).<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Each team was responsible for building pages from the ground up. During this period I was mostly in what I started calling the <\/span><i><span style=\"font-weight: 400;\">architect<\/span><\/i><span style=\"font-weight: 400;\"> mindset.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Once the app started reaching completion, we weren\u2019t building as many new features and mechanisms, and the conventions were mostly stabilized. Instead, we were following what was already in place. We deliberated and agreed to follow the coding conventions that we\u2019d established together. You can think of it as building <\/span><i><span style=\"font-weight: 400;\">on top of<\/span><\/i><span style=\"font-weight: 400;\"> what was already there. This is the other mindset, what I call the <\/span><i><span style=\"font-weight: 400;\">adapter<\/span><\/i><span style=\"font-weight: 400;\"> mindset.<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Two_Mindsets\"><\/span><strong>Two Mindsets<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">After a long time deliberating, I feel the best labels for these two mindsets is the architect and the adapter. Neither mindset is better than the other. The two work together as yin and yang. Both mindsets are utilized by developers of all experience levels. The trick is to be mindful of when it\u2019s best to be in one mindset over the other.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Let\u2019s get into it.<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Way_of_the_Architect\"><\/span><strong>Way of the Architect<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">When building an application from scratch, we can assume the following:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">If a new feature needs to be implemented, there\u2019s no existing code that you can reuse. You\u2019ll have to write it yourself.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Architectural decisions will carry a lot of weight. You\u2019ll introduce new conventions.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">You have some flexibility to introduce packages, plugins, or software that the infrastructure of your app will depend on.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">In the architect mindset, you\u2019re not going to be looking into your app for a previous implementation because there won\u2019t be one. Being in the architect mindset means knowing that the path in front of you will be about exploring new ideas and designing a solution that currently doesn\u2019t exist.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This is when we start whipping out the dry erase markers and get to the whiteboard. You\u2019ll be weighing the decisions of one possible implementation with another. This means thinking about the future of the software \u2014 taking one approach now can be referenced until one day it\u2019s prevalent everywhere in your application and increasingly difficult to replace.<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Way_of_the_Adapter\"><\/span><strong>Way of the Adapter<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">The adapter mindset comes into play when you\u2019re working on a more mature application. Code conventions are in place, documentation has been written and rewritten, and you share a certain quality standard among the team members.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">When we shift from needing to build something new to extending what\u2019s already there, we enter the adapter mindset. This allows us to keep conventions for certain patterns in mind. They can be as small as preferring <\/span><span style=\"font-weight: 400;\">Boolean(foo)<\/span><span style=\"font-weight: 400;\"> over <\/span><span style=\"font-weight: 400;\">!!foo<\/span><span style=\"font-weight: 400;\"> or naming your redux action creators in the past tense like <\/span><span style=\"font-weight: 400;\">orderSubmitted<\/span><span style=\"font-weight: 400;\">, <\/span><span style=\"font-weight: 400;\">preferenceSaved<\/span><span style=\"font-weight: 400;\">, etc.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In this mindset, we\u2019re more focused on using what\u2019s already there, rather than building out something completely new or taking a new approach. We\u2019re following patterns that have been laid out by previous developers.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This is all with the healthy assumption that you and your team thought strategically about how to build your app. Good architectural decisions have been made to allow your software to extend and scale. Part of following the adapter pattern includes determining whether an existing implementation should be reused or if a better and more reusable solution is needed.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Imagine joining a big project that\u2019s been active for 2+ years. As the app is being built, the team is adding models, schemas, contracts, constants, utilities, selectors, etc. to implement functionalities. These various functions will be depended upon and utilized throughout the application. As an incoming developer, you may assume that you should follow the conventions that have been laid out for you. This places you in the adapter mindset.<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Is_one_mindset_better_than_the_other\"><\/span><strong>Is one mindset better than the other?<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">You might be quick to think we want to take the architect mindset most of the time, but this isn\u2019t the case. In order to efficiently build a piece of software, a developer must drift back and forth between the two mindsets depending on the task at hand.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Placing a new developer in the architect mindset can be an effective method to find better ways of doing something, whether in the development process or in the code itself. On the flip side, a senior developer tasked with working on the existing codebase can also help recognize trends in the way the app is being built.<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Switching_between_the_two_mindsets\"><\/span><strong>Switching between the two mindsets<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">One approach is not better than the other. In fact, as software developers we need a proper handle on both approaches. Sure, a new developer will probably be in the adapter mindset most of the time while learning a codebase and how to extend what\u2019s already there. But senior developers can greatly benefit from mastering this mindset. A developer that fails to recognize they can reuse a previous implementation is going to end up doing double the work \u2014 first by needlessly writing their own implementation and again when a colleague points out that this logic already exists in the app and they have to remove what they wrote.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Let\u2019s say that you\u2019ve taken up the task of restoring user preferences from cookies or local storage after refreshing the page. Assume that you have little knowledge about this topic and that the application is decently matured. A smart developer will first research which mechanisms already exist and can be reused. You ask a few colleagues who might know and then look into the code and test the chain of events for the particular flow. These are steps that we take while we\u2019re in the adapter mindset.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Then, let\u2019s assume another scenario where you you need to request certain user data from a separate API. You notice there is no GET request made to this API which also requires authentication, neither of which have been implemented yet. Now you have to consider how to extend the existing logic or whether you need to implement these mechanisms from scratch. This is the moment when we switch to the architect mindset. We then have to start thinking about the architectural steps of creating something new, rather than simply using and enhancing what\u2019s already there.<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Some_tips\"><\/span><strong>Some tips<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Now that we understand the two mindsets and relationship between them, I have some tips on how to best put our knowledge to use.<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Be_mindful_of_the_way_youre_thinking_when_working_on_a_task\"><\/span><strong>Be mindful of the way you\u2019re thinking when working on a task<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Quite often we find ourselves so focused on finding a solution that we don\u2019t stop to consider <\/span><i><span style=\"font-weight: 400;\">how<\/span><\/i><span style=\"font-weight: 400;\"> we\u2019re approaching the problem. It takes practice to zoom out for a moment and think: \u201c<\/span><i><span style=\"font-weight: 400;\">Am I going about this the right way? Have I checked in the codebase for a similar implementation that can be reused? Or am I just coding away on autopilot?<\/span><\/i><span style=\"font-weight: 400;\">\u201d Asking yourself these types of questions will help you reflect on your own approach \u2013 something I encourage everyone to do, not just developers.<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"If_you_find_you_made_a_mistake_because_you_werent_in_the_right_mindset_dont_sweat_it\"><\/span><strong>If you find you made a mistake because you weren\u2019t in the right mindset, don\u2019t sweat it<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">My inspiration for this article came from having been stuck in the adapter mindset for a day or two myself. I kept looking for an existing way to solve my problem. I kept trying to look at previous implementations from different perspectives, but I couldn\u2019t get to a comfortable solution. I was starting to agonize over how much time I was taking, how I couldn\u2019t get the app to behave the way I wanted; I started judging the amount of progress I had made.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Then a lightbulb \ud83d\udca1 went on in my head. I was trying to extend what currently existed in the codebase. Only after many instances of trial and error did I realize that I was approaching the problem from the wrong mindset. I needed to approach the problem from the architect mindset. I had done my research and testing, and determined that the solution did not exist in the codebase. I would have to build it myself.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This late realization happens more often than you would think. Don\u2019t beat yourself up if it took you a bit of time to make the connection like I did. This is all part of growing as a developer. The important thing is that you note these moments in your career and learn from them.<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Reflect_on_your_process\"><\/span><strong>Reflect on your process<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">When I first started working at JET, a colleague shared his daily and weekly approach for getting things done. He said he has a \u201cpersonal stand up\u201d every morning when he examines his list of ToDos, and decides on priorities. At the end of the week, he sets aside a few hours to reflect on the previous week, answering questions like:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">What went well? What didn\u2019t go so well?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Which activities are giving you energy and which are taking energy away from you?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Are you maintaining good habits? Have you developed any bad ones? How can you fix them?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Did you have any realizations during the week that you want to focus on for the approaching week?<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Asking these types of questions and actively reflecting on your own processes is a <a href=\"https:\/\/buradabiliyorum.com\/en\/category\/game\/\" data-internallinksmanager029f6b8e52c=\"7\" title=\"Game\" target=\"_blank\" rel=\"noopener\">game<\/a> changer. This will help you be more mindful about how you work and go about your day instead of being on autopilot and checking off ToDos without much thought into why you\u2019re doing it or if there\u2019s a better way.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">I appreciate how these concepts are reflected in scrum. As a practitioner of scrum and agile, you\u2019ll participate in ceremonies like Retrospectives, where the team will reflect on the previous sprint and ask similar questions to the ones stated above. Dedicating time to reflect on how you felt about your previous day\/week\/sprint is an ingenious tactic to take an honest look at how you or your team work.<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Conclusion\"><\/span><strong>Conclusion<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Sometimes it feels as if you\u2019re expected to know all the answers about your codebase. We fall into this thinking pattern where we need to work as fast as possible, comparing ourselves to our colleagues, and forgetting to take time to reflect on what we\u2019re actually doing. Working this way will build stress and can lead to burnout.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">That\u2019s why it\u2019s important to <\/span><i><span style=\"font-weight: 400;\">think about how you think<\/span><\/i><span style=\"font-weight: 400;\">. When you\u2019re planning how to tackle a coding task, ask yourself \u201c<\/span><i><span style=\"font-weight: 400;\">Which mindset do I need to be in right now? Which approach will most likely lead me to a high quality solution?<\/span><\/i><span style=\"font-weight: 400;\">\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Software development is all about trial and error. It\u2019s always cognitively demanding. We need take care of our mind and body if we want to be effective at work and in our daily lives. Taking time to step back and reflect on how \u2014 rather than what \u2014 you think will lead you to some enlightening realizations about your own process.<\/span><\/p>\n<p><em>This article was originally published on the <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/medium.com\/takeaway-tech\">Just Eat Takeaway-Tech medium blog<\/a>. You can read it<span>\u00a0<\/span><a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/medium.com\/takeaway-tech\/the-two-programmer-mindsets-adapter-architect-eb866593f3ba\">here<\/a>. <\/em><\/p>\n<p><em>With over 580,000 connected restaurants, Just Eat Takeaway.com is a leading online food delivery marketplace that offers consumers a wide variety of choices. Join founder and CEO, Jitse Groen, at TNW2021 for a fireside chat about how the Dutch and tech ecosystem has evolved, lessons learned along the way, and what\u2019s next for the food delivery giant.<\/em><\/p>\n<\/div>\n<blockquote><p><strong><span style=\"color: #ff6600;\">If you liked the article, do not forget to share it with your friends. Follow us on\u00a0<span style=\"color: #ff0000;\"><a style=\"color: #ff0000;\" href=\"https:\/\/news.google.com\/publications\/CAAqBwgKMLG0nwswvr63Aw\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Google News<\/a><\/span>\u00a0too, click on the star and choose us from your favorites.<\/span><\/strong><\/p><\/blockquote>\n<blockquote>\n<p style=\"text-align: center;\">For forums sites go to <span style=\"color: #ff9900;\"><a style=\"color: #ff9900;\" href=\"https:\/\/forum.buradabiliyorum.com\/\" target=\"_blank\" rel=\"noopener\">Forum.BuradaBiliyorum.Com<\/a><\/span><\/strong>\n<\/p><\/blockquote>\n<blockquote>\n<p style=\"text-align: center;\"><strong>If you want to read more like this article, you can visit our <span style=\"color: #ff9900;\"><a style=\"color: #ff9900;\" href=\"https:\/\/en.buradabiliyorum.com\/technology\/\" target=\"_blank\" rel=\"noopener\">Technology category.<\/a><\/span><\/strong><\/p>\n<\/blockquote>\n<p><span style=\"color: black;\"><a style=\"color: #ff9900;\" href=\"https:\/\/thenextweb.com\/news\/elevate-your-programming-try-mastering-two-mindsets\" target=\"_blank\" rel=\"noopener\">Source<\/a><\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>&#8220;#Struggling to elevate your programming? Try mastering these two mindsets&#8221; When a developer approaches a problem, they usually have a clear objective. Fix this bug, create that component, refactor this implementation. We\u2019re very goal oriented by nature. We have an objective that we need to get to, and we have to try all the techniques&#8230;<\/p>\n","protected":false},"author":1,"featured_media":334282,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"fifu_image_url":"https:\/\/img-cdn.tnwcdn.com\/image\/tnw?filter_last=1&fit=1280,640&url=https:\/\/cdn0.tnwcdn.com\/wp-content\/blogs.dir\/1\/files\/2021\/08\/charlein-gracia-mqKKCsZgzXQ-unsplash.jpg&signature=8e7d30bfe0938d47a10bdd1b78718eec","fifu_image_alt":"","footnotes":""},"categories":[18],"tags":[],"class_list":["post-334281","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-technology"],"_links":{"self":[{"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/posts\/334281","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/comments?post=334281"}],"version-history":[{"count":0,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/posts\/334281\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/media\/334282"}],"wp:attachment":[{"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/media?parent=334281"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/categories?post=334281"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/tags?post=334281"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}