<?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 Garrett Love on Medium]]></title>
        <description><![CDATA[Stories by Garrett Love on Medium]]></description>
        <link>https://medium.com/@garrettlove?source=rss-577289907045------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*UXiRl1Xc8xmU4rJUU_f6Sg.jpeg</url>
            <title>Stories by Garrett Love on Medium</title>
            <link>https://medium.com/@garrettlove?source=rss-577289907045------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 11:33:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@garrettlove/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[Beyond Chatting: The 3 Ways AI Agents Truly “Think” Before They Speak]]></title>
            <link>https://garrettlove.medium.com/beyond-chatting-the-3-ways-ai-agents-truly-think-before-they-speak-6fbd8bb46858?source=rss-577289907045------2</link>
            <guid isPermaLink="false">https://medium.com/p/6fbd8bb46858</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[agentic-ai]]></category>
            <dc:creator><![CDATA[Garrett Love]]></dc:creator>
            <pubDate>Fri, 23 May 2025 00:13:51 GMT</pubDate>
            <atom:updated>2025-05-24T10:29:48.987Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gT-bDvSrxLiKlW18ECpo1w.png" /></figure><p>You’ve seen AI models doing incredible things — writing code, drafting emails, generating images. They sound smart, they <em>feel</em> capable.</p><p>But have you ever stopped to think about <em>how</em> they actually process information, especially when the task gets complex or requires using external tools?</p><p>It’s easy to think of them as just predicting the next word, but for AI to move beyond simply <em>sounding</em> knowledgeable to actually <em>acting</em> intelligently and reliably, they need the ability to <em>reason</em>. They need to “think” about the problem, evaluate steps, and check results <em>before</em> giving you a final answer.</p><p>As builders in the AI space, understanding the mechanics behind this reasoning is crucial for building truly robust and effective AI applications.</p><p>That’s why I want to share the three approaches frameworks are using to bring real reasoning capabilities to AI agents.</p><p>Let’s dive in!</p><h3>Approach 1: Reasoning Models — AI Trained to Show Their Work</h3><p>Imagine you ask a brilliant friend a really hard question — maybe a complex math problem or how to fix a tricky piece of code. Instead of just giving you the answer, they might talk through it step-by-step, explaining their logic as they go.</p><p>That’s essentially what a <strong>Reasoning Models</strong> does.</p><p>These aren’t just standard Large Language Models (LLMs). They are often trained using specialized techniques, like reinforcement learning, specifically to encourage them to “think” before providing their final output. You literally get a stream of “thoughts” or intermediate steps before they land on their answer.</p><ul><li><strong>Think:</strong> These models are built to perform complex, multi-step reasoning.</li><li><strong>Excel At:</strong> Challenging problems, like sophisticated coding tasks, advanced mathematical proofs, or difficult reasoning puzzles.</li><li><strong>Examples:</strong> Models like OpenAI’s o-series (like gpt-4o), Claude Sonnet in its extended-thinking mode, Gemini 2.0 Flash’s thinking capabilities, and DeepSeek’s R-1 are pioneering this native reasoning ability.</li></ul><p>The key piece here is that the “thinking” happens <em>before</em> generating the final response.</p><h3>Approach 2: Reasoning Tools — Giving Non-Thinkers a Scratchpad</h3><p>Okay, so some models are built to think natively. But what if your preferred model is fantastic at generating creative text or summarizing information, but doesn’t have that built-in thinking capability?</p><p>This is where <strong>Reasoning Tools</strong> come into play.</p><p>First <a href="https://www.anthropic.com/engineering/claude-think-tool">published by Anthropic</a>, the idea is to give a model that <em>doesn’t</em> natively “think” a sort of “scratchpad” in the form of a tool to work through its logic.</p><p>Frameworks often handle much of the complexity here, but understanding the evolution of these tools shows us how this capability has grown:</p><h4>v0: The Think Tool</h4><p>The initial concept was simple: provide a tool or function that allows the agent to enter a “thinking mode.” It gives the model a space to generate internal thoughts or plans throughout the response generation process.</p><h4><strong>v1: The Reasoning Tools</strong></h4><p>This level adds a crucial component for agents that interact with the world via <em>other</em> tools (like searching a database or using an API). It introduces the ability for the agent to <strong>analyze</strong> the results of tool calls.</p><p><strong>Reasoning = Think + Analyze</strong>.</p><p>This is a game changer! The agent isn’t just using a tool; it’s thinking about <em>what</em> the result means and how it impacts the overall task <em>before</em> moving on. This significantly reduces errors, and improves reliability and quality.</p><h4><strong>v2: The Knowledge Tools</strong></h4><p>Building further, this version integrates access to external knowledge, often via a vector database. The agent can now search through domain-specific information or provided documents.</p><p><strong>Knowledge = Think + Search + Analyze</strong>.</p><p>Now, the agent can think about a problem, search its knowledge base for relevant information, analyze what it finds, and then use that understanding to formulate a better response.</p><p>For builders, the great news is that sophisticated frameworks abstract much of this. You often just configure the agent, and it intelligently uses these tools behind the scenes to enhance its capabilities.</p><h3>Approach 3: Reasoning Agents — Orchestrating Thought and Action</h3><p>So we have models that can think natively, and tools that can give thinking and reasoning abilities to models. How do you combine reasoning with sequential action, tool use, and iteration to solve complex, multi-step problems reliably?</p><p>Enter <strong>Reasoning Agents</strong>. (Note: reasoning models are a feature specific to the <a href="https://docs.agno.com/reasoning/reasoning-agents#example">Agno framework</a>)</p><p>Reasoning agents spin up a separate agent to run in parallel to the primary agent and “reasoning” as the task is completed.</p><h3>Why Does This Matter For You?</h3><p>Understanding these different layers of “thinking” is key if you’re building AI applications that need to be reliable, accurate, and capable of handling complex instructions.</p><p>It could be the difference between an AI system that sometimes guesses or hallucinates when faced with something difficult, and one that can systematically break down a problem, gather necessary information, evaluate it critically, and arrive at a trustworthy conclusion before actually responding to the user.</p><p>As AI technology evolves, its ability to reason effectively will become the most significant differentiator. By leveraging models, tools, and agents designed for reasoning, we move closer to building AI that doesn’t just talk the talk, but truly thinks the think.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fbd8bb46858" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Startup Founders MUST Read These 5 Books in 2025!]]></title>
            <link>https://garrettlove.medium.com/startup-founders-must-read-these-5-books-in-2025-520742f45d88?source=rss-577289907045------2</link>
            <guid isPermaLink="false">https://medium.com/p/520742f45d88</guid>
            <category><![CDATA[book-recommendations]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[founder-advice]]></category>
            <category><![CDATA[professional-growth]]></category>
            <category><![CDATA[how-to-make-money-online]]></category>
            <dc:creator><![CDATA[Garrett Love]]></dc:creator>
            <pubDate>Fri, 22 Nov 2024 18:30:55 GMT</pubDate>
            <atom:updated>2024-11-22T18:30:55.075Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r1u4zS8GcmhooPEfp-Rrfw.jpeg" /></figure><p>Did you know that in a 2016 Pew Research <a href="https://www.pewresearch.org/fact-tank/2021/09/21/who-doesnt-read-books-in-america/">report</a> it was discovered that people in higher socioeconomic groups are twice as likely to read books compared to people who are in lower socioeconomic groups?</p><p>As a founder, it’s no secret that continuous learning is crucial to stay ahead in the game. And what better way to learn than from the experiences and insights of others? That’s why I want to share with you the essential books that I think every founder should read in 2025.</p><p>Make sure you watch until the end, because I’ll share some bonus recommendations you won’t want to miss!</p><h3>Book 1: Atomic Habits</h3><p>So you want to be a startup founder… cool! But the reality is that there is a huge difference between wanting to be a founder (i.e. thinking it sounds cool and being curious) and actually putting in the work to become one.</p><p>Realistically, you will need to set lofty goals, welcome drastic changes, and make incredibly hard choices. This is where Atomic Habits comes in. In this book you’ll learn how to hack the habit creation part of your brain and create the habits you need in order to help make you a successful startup founder. Even better, the skills you’ll learn in this book will applicable to many other parts of your life and help you become a better, more well-rounded, person!</p><p>Check out Atomic Habits on <a href="https://amzn.to/4giUx23">Amazon</a>!</p><h3>Book 2: The Mom Test</h3><p>Stop me if you’ve heard this one before — Person has what they think is an innovative, million-dollar, business idea that everyone will want. Person then spends six months to a year build this idea. Person launches it tells everyone they know, but no one care. Person then wonders why no one is using their app which is clearly so valuable that they should be able to sell it for AT LEAST $1 million.</p><p>In comes The Mom Test, a short and sweet book that helps aspiring founders with conducting user research through interviews to really understand what they are struggling with and what ultimately should be built. I can tell you from personal experience, this book completely changed the way I was doing user interviews for my startup and it was a game changer!</p><p>Check out The Mom Test on <a href="https://amzn.to/4i5b23p">Amazon</a>!</p><h3>Book 3: Day Trading Attention</h3><p>Well-known author Gary Vaynerchuk recently released this book. It talks about how to leverage social media platforms to build a brand and ultimately promote your business and/or product.</p><p>But, here’s the kicker — while this book gives examples from today’s most platforms, you can easily extract key concepts that will be applicable on any future platforms or mediums. For example, Gary goes into detail about how to leverage certain types of creative to test out ideas, and other types of creative once you’ve validated those ideas, ultimately saving you money.</p><p>Check out Day Trading Attention on <a href="https://amzn.to/4fvPbjP">Amazon</a>!</p><h3>Book 4: Play to Win</h3><p>The word “strategy” means many things to many people and can be applied differently depending on the context. In Play to Win, the author goes into to detail about how to think about strategy in a business context and helps you to understand and be able to apply it.</p><p>I found this book to be incredibly helpful when thinking about the strategy for my current startup, and can’t recommend enough.</p><p>Check out Play to Win on <a href="https://amzn.to/3OnT9Pq">Amazon</a>!</p><h3>Book 5: Play Bigger</h3><p>Play Bigger, along with Play to Win, are the one-two punch every founder needs, and really they should be read together (or one after the other).</p><p>This book talks about how to position you startup in the market, what your goals should be, how to reach those goals, as well as helps you to understand what’s at risk if you don’t.</p><p>To be honest, Play Bigger, along with Play to Win, deserve their own sets of videos, so I think I’ll do that in the near future.</p><p>Check out Play Bigger on <a href="https://amzn.to/3V4e4uW">Amazon</a>!</p><h3>Honorable Mentions</h3><h4>HBR — On High Performance</h4><p>As mentioned before, being a startup is no easy task. It will require you to be on your game at all times, and work long hours, too. On High Performance talks about what it means and takes to operate at peak performance and be an expert in something.</p><p>Check out HBR, On High Performance on <a href="https://amzn.to/410Oivo">Amazon</a>!</p><h4>HBR — On Mental Toughness</h4><p>Again, on the same train of thought as On High Performance, On Mental Toughness will help you to persevere through all the hard parts in an effort to reach your goals.</p><p>Check out HBR, On Mental Toughness on <a href="https://amzn.to/4fE8lEh">Amazon</a>!</p><h4>Zero to One</h4><p>A classic in the world of startup books, Zero to One talks about innovation and what’s necessary to go from the world we live in now, to the world we should live in in tomorrow (i.e. the world where your startup exists and is successful).</p><p>Check out Zero to One on <a href="https://amzn.to/4fEWaH4">Amazon</a>!</p><h4>The Lean Startup</h4><p>Another classic in the world of startups, The Lean Startup presents the now well-known “Build, Measure, Learn” feedback loop and how to build a startup in as efficient and quick way as possible.</p><p>Check out The Lean Startup on <a href="https://amzn.to/40ZyzfT">Amazon</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=520742f45d88" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4 Practical Methods for Creating Daily To-Do Lists that Actually Work!]]></title>
            <link>https://garrettlove.medium.com/4-practical-methods-for-creating-daily-to-do-lists-that-actually-work-1271508b1e6d?source=rss-577289907045------2</link>
            <guid isPermaLink="false">https://medium.com/p/1271508b1e6d</guid>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Garrett Love]]></dc:creator>
            <pubDate>Wed, 20 Nov 2024 16:07:04 GMT</pubDate>
            <atom:updated>2024-11-20T16:07:04.818Z</atom:updated>
            <content:encoded><![CDATA[<p>Get ready to transform your day with some incredible planning tips!</p><h3>One: Big and Small</h3><p>Before we get started with the “Big and Small” approach, it’s worth noting that this one works best if you have some big, longterm, goals.</p><p>On a piece of paper, or in your notes app, create two sections — one called “Big” and one called “Small”.</p><p>The “Big” section is reserved for tasks that get you closer towards those big, longterm, goals I mentioned right above. For example, let’s say you want to build an app, one of your “big” goals for today might be to design the home page.</p><p>The “Small” section is reserved for tasks that don’t necessarily get you closer toward your goals, but are simply things that need to get done. For example, you might need to do the laundry or go grocery shopping today. These would go into the “Small” section.</p><h3>Two: Must Do, Could Do</h3><p>Again, on a piece of paper, or in a notes app, create two sections — one called “Must do” and the other called “Could do”. These sections aren’t connect to any big, long-term, goals. Instead, they are just as they say — a group of items you <em>must</em> do today and a group of items you <em>could</em> do today.</p><p>It’s up to you to decide how to prioritize items into these two groups. If you feel that folding the laundry is something that must be done, while doing your homework or meal-prepping are things that could be done, but don’t necessarily have to today, then group them accordingly!</p><p>The key here is that you DON’T tackle the “Could Do” items until you finish everything in the “Must Do”, hence the labels.</p><h3>Three: Kanban</h3><p>This one will be familiar to software developers, product managers, and maybe some other people as well.</p><p>Kanban has a long history. It was inspired by the Toyota Production System and helps to provide a visual for the work that needs to be done across multiple domains.</p><p>This approach could be seen as adding a bit more “process” to your workflow, but for some people it may turn out to be very helpful.</p><p>Additionally, this approach also allows you to prioritize your tasks for the day and order them accordingly (I don’t think ordering them is technically “correct” according to the official Kanban rules, but why not).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9_YTUwwIzODyQqfp9MWSqA.png" /></figure><h3>Four: Weekly Day by Day</h3><p>As with the Big and Small approach, this is another one that works best if you have previously identified some big, longterm, goals.</p><p>This approach aims to give a greater understanding of what you’re intending to accomplish throughout the week. It works by first starting with your overarching goals for the week. These goals should align with those big goals I mentioned earlier.</p><p>In the Big and Small approach we did something similar, however this time we’re going to take a higher 1,000 foot (or meter) view. The way I think of this is that here goals should be big enough that they take a week to accomplish, while in the case of Big and Small they should only take one day. However, in both cases they should be working towards your long-term goals.</p><p>Next, for each day, create a to-do list. These daily to-do lists can be made up of both the items that advance you toward your big goals, as well as daily tasks like doing the laundry.</p><p>This is the approach I’m currently practicing because it helps give me a broader context into my entire week. When I was using only the Big and Small or Must Do/Could Do I felt as though each day was happening in a vacuum. Obviously this was never actually true, but sometimes I felt that way and wanted to have a broader context.</p><h3>Helpful Tips</h3><ul><li>Combine approaches, such as Big and Small and Weekly Day by Day!</li><li>Limit the number of tasks you give yourself each day. This might sound obvious, but I’ve fallen into the trap of having a lot on my mind and adding too many to the list. Try limiting yourself to 2 or 3, see how that goes and increase or decrease accordingly.</li><li>Add an additional section for “On My Mind” where you can add stuff through the day or week that you don’t want to lose but may not be able to fit in or may not yet be applicable.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1271508b1e6d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A framework for developing good habits]]></title>
            <link>https://garrettlove.medium.com/a-framework-for-developing-good-habits-13a8ba70dafe?source=rss-577289907045------2</link>
            <guid isPermaLink="false">https://medium.com/p/13a8ba70dafe</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[personal-development]]></category>
            <dc:creator><![CDATA[Garrett Love]]></dc:creator>
            <pubDate>Thu, 14 Nov 2024 21:50:31 GMT</pubDate>
            <atom:updated>2024-11-14T21:50:31.617Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a_Sy17UMqKlxGnt1NFa6IQ.png" /></figure><p>For the past six years I have worked professionally as a software engineer, and throughout that entire time I was also working on various side projects with the hope that one of them would turn into a successful business. Thus far, none of them have panned out. But I did develop an obsession in the process — trying to be more productive.</p><p>I’ve tried a number of things to advance this effort — I’ve changed my diet, sleep schedule, frequency of social interaction, work-life balance, etc. and each of these things has worked to a certain degree…</p><p>Recently, however, I came across a statistic that claimed the average employee is only productive for less than three hours each day! I think this is a pretty eye-opening stat, and I can’t help but wonder if this is me… Worse is the possibility that I could be below average, and even if I’m above average on this one, that’s still potentially very unproductive.</p><p>In order to help me stay productive, I’ve always set goals for myself, but recently I’ve been reading about habits and it got me thinking that I’d been looking at it all wrong. Specifically, I read Atomic Habits (<a href="https://amzn.to/3ALjiEL">Amazon Link</a>) and the Power of Habit (<a href="https://amzn.to/3CCIAFy">Amazon Link</a>), and realized that while there is a time and place for goals, habits, in conjunction with goals, are the one-two punch I’ve been looking for.</p><p>Many people will set at least one goal at some point in their life, but the problem with goals alone are that they only talk about a single point in time, and say nothing how you will actually get there. There are two problems with this. One, the “getting there” part is really important, and two, what happens after you’ve gotten there or what happens if you don’t get there?</p><p>Let’s come back to the getting there part, and for now, focus on the after successfully getting there or failing to get there part. In the event that you are successful, what comes next? Are you happy? Do you just set a new goal and try to get to that next one? How do you make sure you don’t slip away from that which you have just achieved (e.g. getting in shape)? What happens if you fail? Are you depressed? Do you assume that you can’t do it and give up? Do you set the bar lower and thus risk not reaching your potential?</p><p>The answers to those questions will probably vary for everyone, but in general they center around a specific moment in time — the moment where you realize whether or not you’ve accomplished your goal, but then… nothing.</p><p>Goals aren’t bad, but they are really only one piece of the puzzle. Let’s return to the “getting there” part. If we focus on getting there, we’ll ensure that one, we get there, obviously, but also that a system is in place to ensure that we do so. The way we should think about building such a system is through habit creation. Developing habits, and thus a routine, ensures that over time we’ll chip away at everything that needs to be done in order to reach our goals and allow us to set new ones. This is also the part we should enjoy the most — while it’s obviously fun to reach our goals, we should also enjoy the road to reach them (i.e. “enjoy the process”). If we don’t enjoy the process, there is a good chance we won’t reach our goals.</p><p>For me, the book Atomic Habits (<a href="https://amzn.to/3Oa1bvl">Amazon Link</a>) was instrumental in understanding all this. But, I’ve also done a lot of other reading on developing habits, and so with that, I’d like to share with you my framework for creating habits.</p><p>Developing habits comes down to two big things: First, decide what you want to do. Second, decide on the time and place you’ll do that behavior (habit). For example, you may want to getting better at programming, so you decide to spend an hour working on a fun coding project each day at 8pm, after dinner.</p><p>This framework is very simple and does work. Here are two tips to help you further:</p><ol><li>Stack habits back to back — this gets you on a roll which makes it easier. You can also start with a really easy habit and then follow it up with the harder habit that you actually want. For example, Every morning at 6am I will put on my running shoes -&gt; every morning after I put on my running shoes I will go for a run.</li><li>Your environment plays a huge role in your behavior. For example, If you want to break the habit if checking your phone while you’re working, get into the habit of leaving your phone across the room when you work, preferably in a place where it is out of sight</li></ol><p>I hope this was helpful. If you want to see more content like this in the future give me a follow!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13a8ba70dafe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Should you use Firebase for your app or website?]]></title>
            <link>https://garrettlove.medium.com/should-you-use-firebase-for-your-app-or-website-f490e05732c4?source=rss-577289907045------2</link>
            <guid isPermaLink="false">https://medium.com/p/f490e05732c4</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[firebase]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Garrett Love]]></dc:creator>
            <pubDate>Thu, 01 Aug 2024 18:26:46 GMT</pubDate>
            <atom:updated>2024-08-01T19:00:39.675Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hiwhe81BQYRTOz5SDPAXXg.jpeg" /></figure><p>There really is no clear-cut answer to this question, but here are a few things to think about and ask yourself, or your team, before coming to a conclusion either way.</p><h3>My own story</h3><p>First off, I love Firebase, but I’m not ignorant to what it is and is not. For my current project, which is a startup with a web platform, I started with Firebase for my database, authentication, hosting, backend, and object storage. I have recently made the decision to “graduate” from Firestore to Postgres, and from Firebase Hosting (I tried their new App Hosting service too) to Vercel for my Next JS app. It’s not that Firebase isn’t good, but rather that my needs have changed as I’ve learned more about my project’s requirements. I am still using Firebase for other things such as object storage and authentication. Additionally, if I ever decide to build a mobile app, then I’ll have a good foundation by having Firebase remain in place.</p><h3>What’s your end goal?</h3><p>Are you trying to build a billion dollar startup that will rival Facebook and Google or just playing around to build something cool?</p><p>If you just want to play around with cool technology, have fun, and build something interesting, than it really doesn’t matter because you’ll have fun no matter which tech stack you use. In this case, I would say identify the parts of the puzzle you want to build yourself and use services to handle the rest for you.</p><p>If you’re goal is to build the next unicorn startup I would highly advise using Firebase (or an alternative like Supabase). Why, you might ask — great question! Startups are about moving as quickly as possible in order to reach product market fit (PMF), and once you do so they’re about capitalizing on that fit. This means you should be spending as much of your resources (time &amp; money) on building technology that delivers the value you intend to create, not reinvent the wheel. In other words, let’s say you’re building a revolutionary to-do list app which requires a database of some sort. In this case, you’re in the business of helping people manage they’re daily task list, not managing database infrastructure — there are companies that do that already. What this means for you is that Firebase provides out-of-the-box solutions to common app/web app development problems and since solving those problems (i.e. reinventing the wheel) isn’t what you’re actually in the business of doing you should outsource them to a platform like Firebase since they are actually in the business of solving them.</p><p>Also, in the case that you’re building the next big startup unicorn, chances are you’re going to be rewriting a lot of code and moving away from some services as you get bigger, regardless of if you choose to use Firebase or not.</p><p>It should also be mentioned that if you’re planning to immediately build enterprise software and have requirements such as handling multi-tenancy, or single-tenancy, then you probably aren’t going to be looking at Firebase… at least not as a blanket solution.</p><h3>Will Google kill Firebase?</h3><p>Anytime Firebase comes up, there’s always someone (usually an engineer or a business person who has heard it from an engineer), who says “never use Firebase because Google will kill it soon”. Then they point to some <a href="https://killedbygoogle.com/">Killed by Google</a>. The short answer to this question is probably not. Here’s my logic for this:</p><p>One, Firebase makes Google money. There are a lot of apps using Firebase, some of them quite popular. Firebase is also one of, if not, the biggest players in its space. If you look at the products that Google has killed over the years, they were mostly products that never became dominant players in their respective categories. For example, at the time of writing this, Google has most recently decided to kill off Jamboard, its collaborative digital whiteboard product. Instead of going along with the “Google kills everything” narrative, let’s ask ourselves why — why would Google kill of such a product? Well, according to <a href="https://6sense.com/tech/collaborative-whiteboards/miro-market-share">6sense</a>, another app called Miro is the biggest player in this product category with an estimated 88.99% market share. This is in contrast to Jamboard, which they estimate to have only 3.30% market share. The question now becomes why shouldn’t Google kill of this product? After-all, for a company like Google to pour millions into something there needs to be a sizable ROI — they likely gave it a shot, realized they couldn’t accomplish what they originally set out to, and decided to move on.</p><figure><img alt="6sense Miro marketshare estimate" src="https://cdn-images-1.medium.com/max/1024/1*ZrYJ3QLlMXFJgdCcUHwH2A.png" /></figure><p>Two, Firebase is likely a part of Google’s GCP strategy. I don’t think I’ve heard anyone talk about this, but Firebase is most ideal for side projects, startups, and maybe medium-sized businesses. On the other hand, raw GCP is more of an AWS competitor. With this context, I think Google is using Firebase as part of its sales funnel to get more customers for GCP. Let’s say you use Firebase for your app. You have a lot of data, but Firestore is able to handle everything in the beginning while you’re figuring things out. Up until now, you’re just a Firebase customer (yes, I realize Firebase is an abstraction over GCP). As your app continues to grow, you come to the conclusion that you’d greatly benefit from both a SQL database and a data warehouse. You could use AWS since they’re a leader in that space, but then you find that GCP offers Cloud SQL and BigQuery, and while they may not be a leader, you can accomplish what you need to and not have to leave the GCP universe that you’re already in because of Firebase. This is a HUGE win for GCP, don’t under-estimate it.</p><p>Back to Firebase. Using the logic from above, it wouldn’t really make sense for them to kill off Firebase because 1) it makes money, 2) they’re the biggest player in the category, and 3) It’s part of their cloud strategy. So no, I don’t think Google will be killing off Firebase anytime soon.</p><h3>How much control do you want?</h3><p>Here is an area where Firebase may not shine, but to that point alternatives may not shine either. Firebase is designed to enable app developers to reduce the amount of backend infrastructure management and thus primarily focus on their app.</p><p>This comes with the benefit of not needing to worry about the cloud infrastructure, but at the cost of losing control over that infrastructure.</p><p>If you want a high level of control, more than what Firebase offers, or see your app quickly outgrowing Firebase than it might make sense to use some features and not others. For example, you could use Firebase Auth, Cloud Messaging, and Crashlytics, but then use Cloud SQL and Cloud Run (equivalent to RDS and Fargate on AWS) instead of Firestore and Firebase Functions.</p><h3>What type of auth and security do you need?</h3><p>While Firebase has security rules, they are a bit limited. One option would be to use alternatives to those features where needed, but then you’re not realizing the full benefits of Firebase. For example, if you needed more fine-grained control over access to your database you could use Postgres in Cloud SQL instead of Firestore.</p><p>Another example is if you intend to build role-based authorization, you can build that with Firebase, but it is quite limited once you get past the basics. On the other hand, if that’s all you need then it will be a piece of cake. In my case, I have more than just user roles, as my app also meeds to enforce object level roles within certain parts of the app.</p><h3>Pricing</h3><p>Firebase will be cheaper in the short-term, as it’s free-tier will be able to accommodate your usage while in development and likely even when you have a small number of monthly active users. However, at some point it will start to become quite expensive, more so than if you were to buy the resources your self. There are two things to understand here, 1) the pricing model and how it differs from other cloud infrastructure, and 2) what you’re actually paying for with Firebase.</p><p>On the first point, Firebase (and most, if not all, serverless solutions) charge based on you’re usage, rather than availability. There are pros and cons to this, which are out of the scope of this post, and you should look them up and take them into consideration.</p><p>On the second point, paying for Firebase, and any other serverless product, is really about convenience. You’re paying for the fact that you don’t need to manage server infrastructure yourself. Again, there are pros and cons to this, which are out of the scope of this post, and you should look them up and take them into consideration.</p><p>A final note on price — be sure you’re calculating the “total cost of ownership”, meaning you also factor in your time and any other costs that will come up as a result of using a solution. Serverless, or Firebase in this case, might get expensive, but that cost may still be less than if you have to do things yourself.</p><h3>Database considerations</h3><p>Firebase provides a database called Firestore, which is a serverless, noSQL, option. I have found that those who will tell you not to use Firestore are usually relational database purists or don’t understand/appreciate the benefits of noSQL. To be clear, there is nothing wrong with those two things, but you shouldn’t just accept their advise and run with it.</p><p>Here are some things to consider:</p><ol><li>Firestore, and noSQL document databases in general, can be great when you’re first starting out on a new project. The reason for this is that you may not know what the data model should look like when you’re first getting started, and having the flexibility to make changes without having to worry about migrations is a plus.</li><li>Firestore does offer realtime streaming out of the box, so if that’s something you could benefit from then it’s a good option. Though, you might consider not using it as you primary database.</li><li>Firestore’s query capabilities are quite limited compared to something like SQL, so if you need more powerful querying, Firestore probably isn’t the best option for you.</li><li>Firestore doesn’t offer a way to migrate your data. You’ll unfortunately need to query every document and save it so some file, then import it to your new database manually. This is unfortunate, as it’s not only frustrating, but also potentially very expensive.</li></ol><h3>Here’s the tech-stack I am now moving to</h3><ul><li>Firebase for object storage, authentication, some microservices, and analytics</li><li>Vercel for Next JS hosting, Postgres database, and Redis database</li></ul><h3>Conclusion</h3><ul><li>You most likely don’t need to worry about Google killing off Firebase</li><li>You <strong>should</strong> consider using Firebase if you don’t yet know all the requirements of your app and need to iterate quickly</li><li>You <strong>should</strong> consider using Firebase when you want to focus on building your app and not worry about managing backend infrastructure</li><li>You <strong>should</strong> consider using Firebase when you have limited resources and can’t afford to manage backend infrastructure in addition to building your app</li><li>You <strong>should not</strong> consider using firebase if you’re worried about vendor lock-in</li><li>As your project grows, you can “graduate” from using certain Firebase features, though the migration process might be frustrating with certain products (e.g. Firestore)</li><li>You can choose to use certain Firebase features and not others depending on your needs</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f490e05732c4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using BottomNavigationBar in Flutter]]></title>
            <link>https://garrettlove.medium.com/using-bottomnavigationbar-in-flutter-1e4623073eea?source=rss-577289907045------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e4623073eea</guid>
            <category><![CDATA[dart]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[android-app-development]]></category>
            <dc:creator><![CDATA[Garrett Love]]></dc:creator>
            <pubDate>Sun, 11 Nov 2018 14:45:34 GMT</pubDate>
            <atom:updated>2018-11-11T14:45:34.810Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello everyone, I wanted to write a quick post going over how to use the BottomNavigationBar in Flutter. I wasn’t able to find a good example of this in the official Flutter docs or elsewhere, which is why I’m going to start a new series here showing how I solved common problems while learning Flutter. This will be similar to the “Cookbook” on the official Flutter docs, with the main differences being that these posts will mostly be on topics I couldn’t find in the Cookbook, and I will show how to write the code as well as how it all fits together within a project.</p><p>Anyway, on with the show…</p><p>Today we’re going to be adding Flutter’s BottomNavigationBar to an app. Flutter has some weird names for things so if you don’t know what I’m referring to just look at the picture below, although this is a pretty obvious one as nearly every app uses it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pzfLG6bpSs8KGe48AXZR_g.png" /></figure><p>When I first started tackling this I was using three widgets as pages, with named routes to make the app jump from page to page. However, this doesn’t really work because although want to change pages you technically aren’t doing so. Instead, you’re switching out a group of content within a single page to give the appearance that the page is changing. This is similar to using the TabBar widget for navigation at the top of the page (I’ll most likely have another post for the TabBar widget sometime depending on when I need to use it). Here is a illustration to visually describe what we’re doing. Not that the overall “scaffolding”, as Flutter calls it, stays the same and the contents within the page change.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*i4rlgsJM0rT-rfCFnyx24Q.png" /></figure><p>So essentially what’s happening here is we’re just switching out the color boxes. This could be a home, search, and profile widgets that would be switched out depending on which button at the bottom was tapped. Although all we’re doing is changing the widget that gets displayed, to the user it would appear as though the the app is changing pages.</p><p>Ok so we’ve gone through the theory, but lets actually look at some code.</p><p>We’ll be working in the main.dart file, which is where Flutter holds the main widget for building the app and displaying stuff on the screen. If you’ve worked with React or Angular this is similar to what they do with in their App.js files. Before hammering away at your keyboard, it may be easier to just read through the code that I have. At the bottom of this post I put my full main.dart file so you can see how everything fits together which may be easier to look at while actually typing your code.</p><p>First start by changing the MyApp widget in main.dart to be a Stateful widget. We need to do this because we will be storing which tab the user is on within our state.</p><pre>class MyApp extends StatefulWidget {</pre><pre>    @override</pre><pre>    State&lt;StatefulWidget&gt; createState() {</pre><pre>        return MyAppState();</pre><pre>    }</pre><pre>}</pre><pre>class MyAppState extends State&lt;MyApp&gt; {<br>    @override</pre><pre>    Widget build(BuildContext context) {</pre><pre>        return yourAppData<br>    }</pre><pre>}</pre><p>After you’ve done that, create the BottomNavigationBar inside the Scaffold widget.</p><pre>bottomNavigationBar: BottomNavigationBar(</pre><pre>    items: [</pre><pre>        BottomNavigationBarItem(</pre><pre>            icon: Icon(Icons.home),</pre><pre>            title: Text(&#39;Home&#39;),</pre><pre>        ),</pre><pre>        BottomNavigationBarItem(</pre><pre>            icon: Icon(Icons.category),</pre><pre>            title: Text(&#39;Categories&#39;),</pre><pre>        ),</pre><pre>        BottomNavigationBarItem(</pre><pre>            icon: Icon(Icons.search),</pre><pre>            title: Text(&#39;Search&#39;),</pre><pre>        ),</pre><pre>    ],</pre><pre>),</pre><p>Next, add the onTap property to the BottomNavigationBar widget</p><pre>onTap: (int index) {</pre><pre>    setState(() {</pre><pre>        _selectedTab = index;</pre><pre>    });</pre><pre>},</pre><p>Then, set the currentIndex property of the BottomNavigationBar widget to a variable. You can name it what ever you want, as long as it matches the name of the state variable we’re about to create</p><pre>currentIndex: _selectedTab,</pre><p>Now create an integer variable with the same name you set in currentIndex . Set this at the top of the state.</p><pre>int _selectedTab = 0;</pre><p>Last, create an array variable which holds all the widgets that will be loaded depending upon which button the user taps (note the order here matters and should be the same as the buttons). In my case, these are three widgets that I created to act as other pages, but you can put anything you want such as Text or Image widgets.</p><pre>final _pageOptions = [</pre><pre>    HomePage(),</pre><pre>    CatPage(),</pre><pre>    SearchPage(),</pre><pre>];</pre><p>All together, my main.dart file looks like this:</p><pre>import &#39;package:flutter/material.dart&#39;;</pre><pre>import &#39;./pages/home.dart&#39;;</pre><pre>import &#39;./pages/categories.dart&#39;;</pre><pre>import &#39;./pages/search.dart&#39;;</pre><pre>void main() =&gt; runApp(new MyApp());</pre><pre>class MyApp extends StatefulWidget {</pre><pre>    @override</pre><pre>    State&lt;StatefulWidget&gt; createState() {</pre><pre>        return MyAppState();</pre><pre>    }</pre><pre>}</pre><pre>class MyAppState extends State&lt;MyApp&gt; {</pre><pre>    int _selectedTab = 0;</pre><pre>    final _pageOptions = [</pre><pre>        HomePage(),</pre><pre>        CatPage(),</pre><pre>        SearchPage(),</pre><pre>    ];</pre><pre>    @override</pre><pre>    Widget build(BuildContext context) {</pre><pre>        return MaterialApp(</pre><pre>            theme: ThemeData(</pre><pre>            primarySwatch: Colors.grey,</pre><pre>            primaryTextTheme: TextTheme(</pre><pre>                title: TextStyle(color: Colors.white),</pre><pre>            )),</pre><pre>        home: Scaffold(</pre><pre>        appBar: AppBar(</pre><pre>            title: Text(&#39;Loopt In&#39;),</pre><pre>        ),</pre><pre>        body: _pageOptions[_selectedTab],</pre><pre>        bottomNavigationBar: BottomNavigationBar(</pre><pre>            currentIndex: _selectedTab,</pre><pre>            onTap: (int index) {</pre><pre>                setState(() {</pre><pre>                    _selectedTab = index;</pre><pre>                });</pre><pre>            },</pre><pre>            items: [</pre><pre>                BottomNavigationBarItem(</pre><pre>                    icon: Icon(Icons.home),</pre><pre>                    title: Text(&#39;Home&#39;),</pre><pre>                ),</pre><pre>                BottomNavigationBarItem(</pre><pre>                    icon: Icon(Icons.category),</pre><pre>                    title: Text(&#39;Categories&#39;),</pre><pre>                ),</pre><pre>                BottomNavigationBarItem(</pre><pre>                    icon: Icon(Icons.search),</pre><pre>                    title: Text(&#39;Search&#39;),</pre><pre>                ),</pre><pre>            ],</pre><pre>        ),</pre><pre>    ),</pre><pre>    );</pre><pre>}}</pre><p><strong>Conclusion</strong></p><p>Hopefully this helps. If you’re coming form the web development world this can be a little confusing, but it’s very similar to working with components in Angular or React. I will post more stuff like this as I continue to lear Flutter and do more things with it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e4623073eea" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>