<?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 Nouran Bakry on Medium]]></title>
        <description><![CDATA[Stories by Nouran Bakry on Medium]]></description>
        <link>https://medium.com/@nouranbakry?source=rss-2de673e8226c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*MZZ39l3FtNA5YJ6bdR0jNw.jpeg</url>
            <title>Stories by Nouran Bakry on Medium</title>
            <link>https://medium.com/@nouranbakry?source=rss-2de673e8226c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 19:17:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nouranbakry/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[Why Most Productivity Systems Don’t Work And How To Build Your Own]]></title>
            <link>https://nouranbakry.medium.com/how-to-build-your-very-own-system-for-productivity-and-health-5b77f33dfe6d?source=rss-2de673e8226c------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b77f33dfe6d</guid>
            <category><![CDATA[journaling]]></category>
            <category><![CDATA[life]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[self-awareness]]></category>
            <dc:creator><![CDATA[Nouran Bakry]]></dc:creator>
            <pubDate>Mon, 28 Sep 2026 05:25:40 GMT</pubDate>
            <atom:updated>2026-09-30T09:05:42.497Z</atom:updated>
            <content:encoded><![CDATA[<p>For years, I have tried to find a productivity system that works for me, I tried many popular Systems, but I was finally able to build something that works for me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1EbUPXvFQ4mjNnRM" /><figcaption>Photo by <a href="https://unsplash.com/@markuswinkler">Markus Winkler</a> on <a href="https://unsplash.com/photos/a-close-up-of-a-typewriter-with-a-sheet-of-paper-on-it-sLabRVYuY2w">Unsplash</a></figcaption></figure><h3>The Problem I Used To Face</h3><p>The issue with all the productivity and planning advice and content out there even though I love it and I am a big fan and a consumer of this kind of content. We get an idea for a system that works for somebody and we try to replicate this system and fit into our own life and then we end up abandoning it two days later, so we think the problem is the method or on other occasions we start thinking that the problem is with us, we are lazy or unorganized and we will never be able to have a planning system and have aesthetic notes or calendars like the ones we see online.</p><p>The problem is not in the method or the System you have tried and No, We are not lazy.</p><p>A system is supposed to be tailored to your own life (your goals, your routine, personality and preferences) So, if you pick a System, no matter how awesome and well thought out it is, It is simply not yours. That is why it usually feels like trying to fit a square peg into a round hole.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*A-h8BQRBVq8oLlW0" /><figcaption>Photo By <a href="https://unsplash.com/@soymeraki">Javier Allegue Barros</a> on <a href="https://unsplash.com/photos/silhouette-of-road-signage-during-golden-hour-C7B-ExXpOIE">Unsplash</a></figcaption></figure><p>So after years of trying out different routines and systems. I finally built my own.</p><h3>How to start building your own System</h3><h4><strong>1. Observation and Building Awareness</strong></h4><p>At first, have a picture in you head of a day where you got so many things done, felt good, slept well and things were relatively easy for you.</p><p>We start with a mental model or a picture of an ideal kind of day, one that you had once or would like to have more often. Keep that in mind or journal about it somewhere, then now, forget about it.</p><p>What you need to do now is observe your current day.</p><p>A lot of people who go through their day without a routine or a plan, don’t realize that they already have a routine and a plan. They just don’t really decide it for themselves. It is more like life decides it for them, and they are mostly living reactively, responding to all urgent things that jump at them and demand to be done.</p><p>So, in this phase, we will observe the current routine, How is your day already going? There is no need for any judgment or assessment yet. To get into the habit, we simply start noticing how our current day is going.</p><h4><strong>2. Living One Day at a Time</strong></h4><p>We will not plan for the week yet, or even the month. Just one day. Just today.</p><p>We will not add specific timings or anything like that, unless they are absolutely necessary for appointments or certain tasks. What we will do, is write today’s date (in a notebook or in a digital note if that is what you prefer) and write down what you want to do today.</p><h4><strong>3. Handle Your Perfectionist</strong></h4><p>A tip for perfectionists and people who struggle with overambition, just have two lists.</p><p>Title the first one <strong>Perfectionist/Idealistic</strong>, and label the second one <strong>Realistic</strong>.</p><p>In the first list, write all your hopes and dreams of tasks you want to finish today — conquering the world probably. But make sure that when you move to the realistic list, you include only the absolute must-dos, basically the bare minimum you can get away with for the day.</p><p>At the end of the day, go back to that page. Don’t be harsh or judgmental if you got nothing done. Just put an arrow next to it to move it to tomorrow, cross it out if it is no longer needed, or add a tick mark for accomplished tasks — yaay! And that is all.</p><p>The next day, repeat the same exercise.</p><p>It doesn’t really matter if you keep writing down tasks without getting anything done. It is completely fine. We are still warming up and training your brain.</p><h4><strong>4. Differentiate Between Habits and Tasks</strong></h4><p>Sometimes, you might write things on your list that are actually habits, something repetitive. They are not work tasks, project-related tasks, or appointments, but things like “exercising more”, walking, journaling, etc.</p><p>For these, I suggest keeping a separate list because, a lot of the time, you are not necessarily going to do these things every day. Or you might do them every day if they are habits you are already maintaining.</p><p>For these, you can maybe try a habit tracker, which I will write about, along with my method, in the next publishing.</p><h4><strong>5. Stacking Similar Tasks Together</strong></h4><p>After you have had a streak of a few good days of writing things down and have started to cross at least one task or habit off the list, let’s reflect on your schedule.</p><p>You can sit down and recall the times during the day when you usually like to work, sleep, exercise, and so on. Then, you can start planning or grouping similar tasks together.</p><p>Maybe there is a focus hour when you do deep work early in the morning, and maybe you want to get into the habit of journaling. You could try planning your journaling right before or after that deep-work hour.</p><h4><strong>6. Journaling is Usually Where It Begins</strong></h4><p>This is my usual starting point for any good productivity or Self-Improvement story. It almost always starts with journaling.</p><p>Coincidence? I think not.</p><p>Every time I get back into the habit of daily journaling, I gain so many insights into my current life, what I want to improve, and what I want to do more or less of. It is also usually a very peaceful time.</p><p>You can check out another post I published a few years ago:</p><p><a href="https://medium.com/@nouranbakry/how-journaling-everyday-can-change-your-life-d657e7dc8a9f?sharedUserId=nouranbakry">https://medium.com/@nouranbakry/how-journaling-everyday-can-change-your-life-d657e7dc8a9f?sharedUserId=nouranbakry</a></p><p>It is basically the same way I journal now, except that I am more into writing in an actual notebook these days than keeping a digital journal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*djPpl9cDNyUnzvTd" /><figcaption>Photo By <a href="https://unsplash.com/@emirkutluay">Emir Kutluay</a> on <a href="https://unsplash.com/photos/close-up-of-an-ornate-astronomical-clock-on-a-building-NYIFxuhevas">Unsplash</a></figcaption></figure><h4><strong>So, What happened with me?</strong></h4><p>I started when I was in a very chaotic place in my life, where I began to notice that, on most days, I was just running around trying to get things done.</p><p>I started following the steps I outlined above.</p><p>At first, I only wrote down tasks for that day. Right after writing in my journal, I would simply jot down what I wished to do that day.</p><p>After a few days, I started to notice specific times during the day when I got more done, as well as other times when I preferred to rest or disconnect, and so on.</p><p>Slowly, I built a time-blocking schedule based on my five daily prayers. This was already how my day was naturally divided into blocks, without me realizing that it was my existing schedule.</p><p>I just had to become more intentional about it: deciding ahead of time which task goes where and prioritizing rest and self-care as well.</p><p>Let me know if these steps help you start building a System that works for you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b77f33dfe6d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Not Your Usual Study Guide to Cracking Coding Interviews]]></title>
            <link>https://nouranbakry.medium.com/not-your-usual-study-guide-to-cracking-technical-interviews-f31151fc3726?source=rss-2de673e8226c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f31151fc3726</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[whiteboards]]></category>
            <category><![CDATA[coding-interviews]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Nouran Bakry]]></dc:creator>
            <pubDate>Mon, 16 May 2022 14:25:38 GMT</pubDate>
            <atom:updated>2022-05-19T13:46:57.009Z</atom:updated>
            <content:encoded><![CDATA[<p>Preparing for coding interviews can be a pain. I found a way to make the process easier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_TF41GE3B9jE_O9qKeqzdw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@cgower?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Christopher Gower</a> on <a href="http://localhost:3000/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I have been preparing for technical interviews and I have practiced problem-solving for a while and I have developed my study guide. I am hoping that this article will help you develop an effective study plan to ace technical interviews.</p><p>Before you begin your interview preparation, you need to have a clear goal in mind, what kind of company do you want to work at? Some strategies will be effective only for some companies and not effective for others. For instance, some companies are looking for software engineers that are experienced in a particular field or stack like a Java Developer, An Android Developer, or an ios developer, while for some of these job opportunities you may be asked to solve problems but that will mostly be a small scope of the interview. The interview will mainly focus on that particular stack or technology. In this article, I am focusing on preparing for general Software Engineering roles at companies whose interviews focus on algorithms, data structures, and system design.</p><p>First pick a programming language that is easy for you and one that you are familiar with, it doesn’t matter which one from my experience most large companies let you pick whatever language you want.</p><p>Next, you will need to review important data structures and algorithms and for that, you will need a reference, Everyone will probably recommend CTCI (Cracking the Coding Interview By Gayle Mcdowell), From my experience, it is a great reference but I see it more of a study guide and I needed a more detailed reference. I will share what references I used at each step of my preparation.</p><h3>Studying and Reviewing Important Topics</h3><p>At this stage, I watched <a href="https://youtube.com/playlist?list=PLUl4u3cNGP63EdVPNLG3ToM6LaEUuStEY">MIT Data Structures and Algorithms lectures</a> and I also looked through their notes. While reviewing the lectures, I went through <a href="https://www.amazon.co.uk/Introduction-Algorithms-MIT-Press-Cormen/dp/0262533057">Cormen’s Introduction to Algorithms</a>. This was a great way to review data structures and algorithms. MIT’s course is amazing, they go through all the concepts and explain each one thoroughly, I would highly recommend that you check it out.</p><p>You don’t have to watch all the lectures or read all the references. Make a list of all the important topics and for each topic make sure you completely understand the concept. How do you know you understand it? Well, can you explain it to somebody else? If you can explain it to any of your friends then do so and get feedback from them or if you are by yourself record yourself explaining the topic, try to draw any diagrams, and write on a board or paper. This way you can make sure you fully grasp the concept.</p><p>As for topics like System Design or OOP, this will depend on your level and experience. For instance, if you are a junior, check with your recruiter if you will be asked system design questions, and try to get familiar with Object-Oriented Programming, Design Patterns, and Databases. If you are more experienced, you will need to look for more references, I used this <a href="https://github.com/donnemartin/system-design-primer">GitHub repository</a> along with some youtube videos you can also Check out <a href="https://youtu.be/9N2S3JZffeg">Ustav’s video on System Design</a>.</p><h3>Solving Problems</h3><p>I solved questions per topic. During this stage I used <a href="https://www.amazon.com/Elements-Programming-Interviews-Java-Insiders/dp/1517671272#:~:text=The%20book%20begins%20with%20a%20summary%20of%20patterns%20for%20data,design%2C%20probability%20and%20discrete%20mathematics.">Elements of Programming Interviews in Java</a>, there are other editions in other languages I solved problems in java which is why I used this edition. This is an excellent guide, it has detailed explanations and problems of different difficulties and it covers all the major topics. At the beginning of the book, there are also very helpful tips and tables that can help you create a timeline.</p><p>I also started solving on coding platforms, I have used leetcode and hackerrank. While solving I used to time myself and I wrote code on paper or a notepad, this is preferable so that you mimic whiteboard interviews. If you use a code editor don’t use an editor that will correct your syntax and Don’t run your code before to check if it is working. Wait till you finish and after your time is over then you can run your code. If I found myself struggling with a particular topic I went back to the previous step.</p><p>After solving problems on each topic, I started solving problems randomly, this step is also important so that you don’t expect what data structure or algorithmic approach you will need in your solution. Try to solve easy problems first once you get comfortable with them then you can go ahead and solve medium and hard problems. If you have time in your schedule, Hard problems are important to focus on because they combine several algorithms and data structures, and practicing hard problems will significantly improve your problem-solving game. There is an excellent guide to grinding leetcode problems that you can find <a href="https://www.reddit.com/r/cscareerquestions/comments/6luszf/a_leetcode_grinding_guide/">here</a>.</p><h3>Evaluation</h3><p>Now for the most important part that stepped up my problem-solving game. I started evaluating myself, for each problem that I solved, once the time was up, I used to look at my solution and ask myself some questions, what went wrong? what could have made my solution more optimal? was my code clean? was my syntax correct? and then I scored my solution. I used to score my solution based on correctness, optimality, the time taken, O(n), etc.. and then I averaged my scores. I learned this approach from <a href="https://youtu.be/7UlslIXHNsw">Engineering with Ustav’s guide to coding interviews</a>.</p><p>This was a game-changer for me. I made a Trello board dedicated to problem-solving and I created three lists (to-do, repeat, done). In the to-do list, I added all the problems I wanted to solve from leetcode, hackerrank, or any books or references, and every time I solved a problem I scored it, if I didn’t get 5/5 I would add it to the repeat list depending on my score, if my score was high I would add it to the bottom of the list, if it was low I added it to the top of the list. You can also use Notion, a pen, paper, or any simple to-do list to applying this method. In my Trello board, all the to-do problems were problems I never solved before, problems in the repeat list are problems I want to solve again and the problems in the done list are the problems I can solve confidently and this is the list I am most proud of. Every time I want to solve problems I would pick problems from the top of my to-do list and the top of my repeat list.</p><h3>Mock Interviews</h3><p>This is also an important part of your preparation. Mock interviews are where you apply everything you practiced. You need to reach a state where you are confident and calm during mock interviews. One video that gave me great tips on mock interviews was <a href="https://youtu.be/lDTKnzrX6qU">Chris Jereza’s video on coding interviews</a>. If you have a friend that is with you on your journey then do schedule time for mock interviewing one another, if not then you can schedule a mock interview on <a href="http://www.pramp.com/">pramp.com</a>, it is a platform that allows you to match with another candidate and you can interview each other. Another method is you can try to replicate your interview experience on your own and record yourself solving problems with a timer. This is also a very useful way to become more confident with interviews. You can then watch the recording and evaluate yourself. Real interviews with companies are also another way, try to schedule actual interviews and treat them as mock interviews, if you pass and get an offer yaaay! if not then this was a mock interview.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3zYAILMN_OwNsG2JoO006A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@hellokellybrito?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">J. Kelly Brito</a> on <a href="http://localhost:3000/s/photos/learning?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Things to keep in mind while solving problems</h3><h4><strong>1. Quality over quantity.</strong></h4><p>It doesn’t matter how many problems you have solved. The quality of your problems, the time taken on each problem, and the way you approach the problem are more important.</p><h4><strong>2. Explain your solution and your approach clearly before you think of how to write code.</strong></h4><p>This is the most important part of solving problems, if you have a clear approach your interviewer will know that you are capable of solving the problem and you will be able to easily translate it into code.</p><h4><strong>3. You don’t have to get the most optimal solution right away.</strong></h4><p>If you are stuck, think of the most simple solution or a brute force solution, once you have that then you can look for bottlenecks or spots where you can use a data structure may be a hash map or maybe you need to use a particular algorithm. Once you have a correct brute force solution you can always optimize it.</p><h4><strong>4. There is no such thing as failure.</strong></h4><p>Don’t get discouraged if you don’t know how to solve a problem or if you get rejected. Think of it as trial and error, try to enjoy the process as you are learning how to get it right next time. Don’t think of the future or the past and try to mindfully practice and learn for your interviews one step at a time.</p><h4><strong>5. Problem-solving is a skill you will need throughout your career.</strong></h4><p>Try to find what you like about it and look at it as a skill that you will constantly need to improve. You will always have interviews if you want to work full-time so you need to always improve your problem-solving skill.</p><h3>Lessons I learned along the way</h3><h4><strong>Stress and overthinking will only get in your way.</strong></h4><p>Try to be as calm as you can be, if you are not in a position to put yourself under the stress of an interview then maybe take some time off if you can afford it and think of how to improve this process for you. Think about what you want to be doing and how you want to go about it. Find out what works for you and go from there. There is no particular timeline or process, you can solve one problem every day or 5 problems or 10, this depends on how you can manage your time and what your goals are.</p><h4><strong>Mass applying is not effective.</strong></h4><p>Be mindful with applying for jobs, I understand how looking for a job can be a painful experience but make sure you are applying for the right companies. Before applying to a role, look at the company and the role and try to understand more about it, is it what you want to do? what kind of interview preparation is required for this role? Do you know somebody who works at the company or someone who interviewed with them? Try to gather some information that can make the process easier.</p><h4><strong>Putting a deadline for landing an offer is toxic.</strong></h4><p>Imagine putting a deadline on something you can never predict, luck and fate has a major role in you getting an offer or not. If you keep expecting to land a job by a particular date you will only get discouraged. Try to learn from the process as you go calmly, employ the same evaluation strategy that you used with problem-solving in your interviews, and try to evaluate each interview experience and think of what could have gone better.</p><h3>Conclusion</h3><p>At the end of the day, a career is only one aspect of your life. A job is just a way of getting an income and maintaining a well-balanced life. This is all meant to improve your life, be mindful while learning, and also be easy on yourself, and don’t let it become a stressful or overwhelming experience that may decline your life quality or affect your mental health.</p><p>I have gone through many interviews and I have explored my way through different routes and methods so feel free to leave any questions. I wish everyone who is interviewing the best of luck.</p><p>I have published this article on dev.to and Hashnode as well check it out:</p><ul><li><a href="https://dev.to/nouranbakry/not-your-usual-study-guide-to-cracking-technical-interviews-3f2l">Not Your Usual Study Guide To Cracking Coding Interviews</a></li><li><a href="https://nouranbakry.hashnode.dev/not-your-usual-study-guide-to-cracking-coding-interviews">Cracking Coding Interviews</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f31151fc3726" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Journaling Every Day Can Change Your Life]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://nouranbakry.medium.com/how-journaling-everyday-can-change-your-life-d657e7dc8a9f?source=rss-2de673e8226c------2"><img src="https://cdn-images-1.medium.com/max/2600/1*Rd9IZ3SLf5vJJ_qCd6dz9w.jpeg" width="6000"></a></p><p class="medium-feed-snippet">I have been journaling daily for a year and it has changed my life.</p><p class="medium-feed-link"><a href="https://nouranbakry.medium.com/how-journaling-everyday-can-change-your-life-d657e7dc8a9f?source=rss-2de673e8226c------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://nouranbakry.medium.com/how-journaling-everyday-can-change-your-life-d657e7dc8a9f?source=rss-2de673e8226c------2</link>
            <guid isPermaLink="false">https://medium.com/p/d657e7dc8a9f</guid>
            <category><![CDATA[journaling]]></category>
            <category><![CDATA[life]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Nouran Bakry]]></dc:creator>
            <pubDate>Mon, 16 May 2022 10:59:28 GMT</pubDate>
            <atom:updated>2026-10-01T03:34:11.347Z</atom:updated>
        </item>
    </channel>
</rss>