<?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 Raphaël Titsworth-Morin on Medium]]></title>
        <description><![CDATA[Stories by Raphaël Titsworth-Morin on Medium]]></description>
        <link>https://medium.com/@RaphaelTM?source=rss-7c9e75e19092------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*-TMZzyqhJO66hu5t1JX92w.jpeg</url>
            <title>Stories by Raphaël Titsworth-Morin on Medium</title>
            <link>https://medium.com/@RaphaelTM?source=rss-7c9e75e19092------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:38:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@RaphaelTM/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[So I finally gave Tailwind a shot]]></title>
            <link>https://blog.ephemerecreative.ca/so-i-finally-gave-tailwind-a-shot-6fd49215635c?source=rss-7c9e75e19092------2</link>
            <guid isPermaLink="false">https://medium.com/p/6fd49215635c</guid>
            <category><![CDATA[css]]></category>
            <category><![CDATA[tailwind-css]]></category>
            <category><![CDATA[material-design]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[framework]]></category>
            <dc:creator><![CDATA[Raphaël Titsworth-Morin]]></dc:creator>
            <pubDate>Wed, 29 May 2024 15:02:35 GMT</pubDate>
            <atom:updated>2024-05-29T15:02:35.858Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Colorful swirls and clouds" src="https://cdn-images-1.medium.com/max/1024/1*d3hbQdI-FGpIPMusO544UQ.png" /></figure><p>I’ve been building with a variety of styling tools (frameworks, toolkits, whatever you want to call them) for a while now. I hopped on the Bootstrap bandwagon early on. I followed the Foundation crowd for a little while. I bought into Bulma for a few years. And then I met MUI (which I fell in love with). Finally, in the past 6 months, after <em>years</em> of hearing about it, I tested Tailwind.</p><h3>The Journey</h3><p>It was a bit of a rollercoaster. Here’s how it went, over the course of a few months:</p><ol><li>My first instinct, seeing Tailwind code was: “I can’t do this. I can’t write 100 classes all over the place. It’s so ugly and annoying even with IDE extensions.”</li><li>My reaction after trying it was “Oh. This is kinda neat. I can get things looking pretty decent pretty fast.”</li><li>My reaction after trying it for a full project (including trying out Tailwind UI) was, “Ok, I can get stuff done fast initially, but it quickly becomes hell to maintain.”</li><li>My next reaction was to search for something like “framework on top of Tailwind,” it which point I found both <a href="https://daisyui.com/">DaisyUI</a>, and salvation.</li></ol><h3>The Learning</h3><p>At <a href="https://ephemerecreative.ca/">Éphémère Creative</a> we build a lot of stuff in React. So it’s pretty straightforward to bundle your tailwind classes into a component. But the thing I found difficult/frustrating with Tailwind is that I kept approaching it as a “framework.” But I would argue it’s not really a framework: it’s a library. To be fair, they call themselves “a utility-first CSS framework.” Which feels like a bit of both. But to me, I was looking for the guardrails, structure, and functionality that come with what I traditionaly think of as “frameworks.” Tailwind doesn’t offer that out of the box: it’s really more like “css, but faster to work with, with a <em>soupçon</em> of structure, and with pretty defaults.” Once I started to think of it as a library (i.e. a collection of useful tools), I felt more at peace with it. I also realized that there were frameworks like Daisy UI which helped add structure and functionality on top of Tailwind, which made it pretty much what I was looking for.</p><h3>What next?</h3><p>I think we’ll build some of our future projects with it, but I still generally find myself leaning towards MUI for larger projects, and Tailwind for smaller ones. We’ve gotten pretty adept at making MUI look very little like MUI, while retaining all of it’s functionality. When I start a small Next.js project, though, I do feel myself thinking “eh, we can probably just use Tailwind on this and thing will go faster.”</p><p>🤝 If you think we could work together, we’d love to partner up and help you with your projects!</p><p>🧑‍💻 Get a FREE consultation here! <a href="https://goec.io/contact-us/">https://goec.io/contact-us/</a><br>✉️ Sign up for the newsletter: <a href="https://s.goec.io/newsletter">https://s.goec.io/newsletter</a><br>🎙 The Small Tech Podcast by EC: <a href="https://smalltechpodcast.com/">https://smalltechpodcast.com</a><br>🎥 Watch our videos: <a href="https://s.goec.io/videos">https://s.goec.io/videos</a><br>➡️ Shoot us a message: <a href="https://s.goec.io/contact">https://s.goec.io/contact</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fd49215635c" width="1" height="1" alt=""><hr><p><a href="https://blog.ephemerecreative.ca/so-i-finally-gave-tailwind-a-shot-6fd49215635c">So I finally gave Tailwind a shot</a> was originally published in <a href="https://blog.ephemerecreative.ca/">Éphémère Creative</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Exploring a modern solution to deploy and manage services]]></title>
            <link>https://blog.ephemerecreative.ca/exploring-a-modern-solution-to-deploy-and-manage-services-8cd33c0ef69e?source=rss-7c9e75e19092------2</link>
            <guid isPermaLink="false">https://medium.com/p/8cd33c0ef69e</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Raphaël Titsworth-Morin]]></dc:creator>
            <pubDate>Fri, 11 Aug 2023 18:20:10 GMT</pubDate>
            <atom:updated>2023-08-11T19:10:49.252Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*laz-Lv7m4bp_XALQoCB_mQ.png" /></figure><p>Over the years, I’ve been paying attention to the evolution of the landscape of container deployment and orchestration services. These transformations ushered in numerous tools and platforms, with big players like AWS and Google Cloud offering a wide array of solutions. I came across loads of offerings from different vendors as time passed on.</p><h4>Existing Options</h4><p>On AWS you’ve got EKS, ECS, Fargate, and the more recent ability to run containers using Lambda. And more… for example, it’s a bit awkward and the developer experience is terrible, but you can point Elastic Beanstalk to an image you’d like to run. Then you’ve got the GCP offerings like Google Cloud Run, GKE and a bunch of other tools and projects built around them (Anthos, KNative, etc.). I haven’t used Azure much, but my understanding is there are plenty of ways to run containers on their infrastructure as well.</p><p>Of course you can also run a Kubernetes cluster yourself or use any number of managed offerings, from DigitalOcean, Civo, Linode, etc. There’s even a wide variety of tools to help you build your own k8s clusters, from microk8s, to k3s, and more.</p><p>All these products, while impressive, lead to a tonne of complexity, both regarding the knowledge required to effectively deploy workloads, but also in the sheer number of configuration options. What I want to be a straightforward process always turns into a maze of choices. Sure, there’s power in the ability to run exactly the configuration you want, but my experience is that for the vast majority of systems, a lot of that configuration could be standardized, and there’s power in knowing that someone you trust has taken care of that configuration for you.</p><h4>Something new…</h4><p>Enter <a href="https://defang.io/">Defang.io</a>. I had a chance to do some work for them on a project recently, where I deployed 5 services to their platform. It really felt as if they were the answer to that complexity. They’re all about creating a really, <em>really</em> developer-centric experience. If you’ve ever used docker-compose, Defang’s approach will make you feel right at home. They allow you to deploy your services to the cloud by simply pointing their CLI to a compose file. Crucially for our workflows at <a href="https://ephemerecreative.ca/">Éphémère Creative</a>, they also provide a Pulumi provider. That makes it dead simple to provision service and data stores. And on top of it all, they’re aiming for cost-efficiency and scalability. My impression was that they want to make sure you don’t have to worry about your bill if you’re just running a few services, and you don’t have to worry about growth, at least as it relates to things like compute and networking (they don’t take care of storage, so of course you’ll still need to architect your systems appropriately around databases, etc.).</p><p>One of the things I’ve really appreciated when working with them and talking to them about their vision is that it’s not just about containers (even though that’s the starting point). They have a broader vision in mind about how to architect scalable systems and making it easy for developers to build around certain principles. They’re keen to build out systems to make it easy for developers to deploy containers or serverless functions through a system that makes it effortless to work with both. All with the understanding that in many systems, they each have their place. This aligns really well with what we’re building with the <a href="http://gochewy.io/">Chewy Stack</a>, so I’m really excited to see where it goes!</p><h4>Moving forward</h4><p>The work we did with Defang wasn’t just transactional. I felt a strong connection with their mission and how I hope to see software development evolve. Their beta phase, focused on container deployment, has shown a tonne of promise, and the way they’re structuring their thinking about deploying backend services more broadly feels really groundbreaking.</p><p>If you find yourself deploying containers, I’d recommend checking out <a href="https://defang.io/">defang.io</a>. You won’t be disappointed, and I’m personally really excited to see the future of the platform.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8cd33c0ef69e" width="1" height="1" alt=""><hr><p><a href="https://blog.ephemerecreative.ca/exploring-a-modern-solution-to-deploy-and-manage-services-8cd33c0ef69e">Exploring a modern solution to deploy and manage services</a> was originally published in <a href="https://blog.ephemerecreative.ca/">Éphémère Creative</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Exploring AI Tools: Discovering the Impact of GitHub Copilot, ChatGPT, and more]]></title>
            <link>https://blog.ephemerecreative.ca/exploring-ai-tools-discovering-the-impact-of-github-copilot-chatgpt-and-more-9c82ca22735?source=rss-7c9e75e19092------2</link>
            <guid isPermaLink="false">https://medium.com/p/9c82ca22735</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[small-business]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Raphaël Titsworth-Morin]]></dc:creator>
            <pubDate>Mon, 22 May 2023 10:34:50 GMT</pubDate>
            <atom:updated>2023-05-22T10:34:50.277Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*atoMrO_sdRnMT3x9Lduy2Q.jpeg" /></figure><p>The world of AI tools has seen an explosion in recent years, and it’s hard not to be curious about the impact they’re having on our daily lives. As someone who’s always on the lookout for new and interesting tools, I’ve been trying out various AI applications to see how they can benefit me and other small tech companies.</p><p>🎥 If you’d rather watch a video, <a href="https://youtu.be/wgXEDmjjioo">watch it here</a>.<br>🎙️ If you’d rather listen as a podcast, <a href="https://smalltechpodcast.com/episodes/ai-tools">listen here</a>.</p><p>Ok, let’s get into it…</p><h4>Code</h4><p>One such AI tool that has piqued my interest is GitHub Copilot, which many of you may be familiar with. If you aren’t… it’s an AI-powered code completion tool ‌designed to make coding more efficient by suggesting entire lines or blocks of code as you work. It’s not without its flaws, of course, but it’s neat to see how AI can help developers, especially those in the early stages of their careers, to streamline their workflow and learn from the suggestions provided. One problem I foresee with it, though, is that there will certainly be devs thoughtlessly including code from the AI without double-checking whether it does what they intended.</p><h4>Writing</h4><p>Another area where AI tools have made a significant impact is in content generation. Tools like ChatGPT are transforming the way we create and edit content. Although AI-generated content is not as original or creative as human-generated content, I have found it to be a valuable resource to help with restructuring and improving existing content. By providing the AI with a solid starting point (often just a transcript of my rants), it can generate novel text that fits a particular format, like a blog post, case study, grant application, etc.</p><h4>Images</h4><p>Canva, the well-known design tool, has recently incorporated AI-driven content generation, adding an extra layer of convenience for users working on their projects. It’s fascinating how you can now create custom images within the app by simply describing your vision, like a wavy green field with a hawk soaring through the sky. Although ‌AI-generated content might not match the quality of those created by a professional, it’s a neat way to add some custom imagery to a graphic if you don’t mind a bit of weirdness (or you get really good at prompting and refining the images).</p><h4>Search/Parsing Content</h4><p>Now, let’s talk about AI and search engines. Initially, I was skeptical about the value of using large language models for search, but tools like Perplexity have proven me wrong. Perplexity provides a more contextual and natural language-driven search experience, which links to sources when it provides a response. I’ve found the results to be quite good so far. Its Chrome extension, which allows you to summarize or ask questions about a specific webpage, has been particularly valuable for tasks like parsing grant applications or understanding lengthy documents. Of course, you need to double-check that the results are accurate, because they aren’t always. Most of the time though, it’s still a time-saver.</p><h4>Hype</h4><p>As the hype around AI tools continues, I think it’s important to remember that there’s a hype cycle with every new technology. However, the practical value that many people, including myself, are finding in these AI applications sets them apart from previous trends in recent years‌. I’m eager to see what’s left when the hype dies down and we’re left with the genuinely valuable aspects of this new technology. I might be overly excited, but I think the way these tools allow us to interact with machines is laying the groundwork for a new relationship between humans and computers, similarly to graphical user interfaces, or smartphones.</p><h4>In the end…</h4><p>I’d say that if you’re curious about AI tools and their potential, you shouldn’t hesitate to explore the options available and see how they can benefit you in your work or personal projects. There’s a lot of vaporware, but there’s also a lot of genuinely useful stuff out there!</p><p>🤝 If you think we could work together, we’d love to partner up and help you with your projects!<br>✉️ Sign up for the newsletter: <a href="https://s.goec.io/newsletter">https://s.goec.io/newsletter</a><br>🎙 The Small Tech Podcast by EC: <a href="https://smalltechpodcast.com/">https://smalltechpodcast.com</a><br>🎥 Watch our videos: <a href="https://s.goec.io/videos">https://s.goec.io/videos</a><br>➡️ Shoot us a message: <a href="https://s.goec.io/contact">https://s.goec.io/contact</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c82ca22735" width="1" height="1" alt=""><hr><p><a href="https://blog.ephemerecreative.ca/exploring-ai-tools-discovering-the-impact-of-github-copilot-chatgpt-and-more-9c82ca22735">Exploring AI Tools: Discovering the Impact of GitHub Copilot, ChatGPT, and more</a> was originally published in <a href="https://blog.ephemerecreative.ca/">Éphémère Creative</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Exploring Project Management Tools for Small Tech Teams]]></title>
            <link>https://blog.ephemerecreative.ca/exploring-project-management-tools-for-small-tech-teams-29ffb65aee07?source=rss-7c9e75e19092------2</link>
            <guid isPermaLink="false">https://medium.com/p/29ffb65aee07</guid>
            <category><![CDATA[asana]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[clickup]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[tools]]></category>
            <dc:creator><![CDATA[Raphaël Titsworth-Morin]]></dc:creator>
            <pubDate>Tue, 28 Mar 2023 23:47:21 GMT</pubDate>
            <atom:updated>2023-03-29T00:35:54.135Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xgncMDBdmH1XjOLuEOKIGQ.jpeg" /></figure><p>Navigating the world of project management tools can be daunting, especially for small teams. With so many options available, it’s essential to find the right fit for your team’s unique needs. In this blog post, I’ll share my personal experiences with some popular and lesser-known tools, including JIRA, Asana, ClickUp, Linear, Height, Notion, and Coda, to help you make an informed decision. This is all based on my experience over the past few years, and most recently when I decided to move <a href="https://ephemerecreative.ca/">Éphémère Creative</a> away from Asana last year (though it might work well for you!).</p><p>🎥 If you’d rather watch a video, <a href="https://www.youtube.com/watch?v=CT4tmI3jkt8">watch it here.</a><br>🎙️ If you’d rather listen as a podcast, <a href="https://smalltechpodcast.com/episodes/project-management-tools">listen here</a>.</p><p>Ok, let’s get into it…</p><h3>JIRA and Asana: The Classics</h3><p>Links: <a href="https://www.atlassian.com/software/jira">JIRA</a> and <a href="https://asana.com/">Asana</a></p><p>During my time using JIRA, I appreciated its robust features and flexibility, especially for software development projects. The integration with the Atlassian ecosystem is amazing if you use their other tools. However, I found its complexity to be overwhelming for my small team, and the learning curve was steeper than I would have liked. That complexity is also its superpower: JIRA feels like a beast that you can train to do pretty much anything you want, if you have the resources to put towards that.</p><p>In contrast, Asana provided a more user-friendly interface and a wider range of applications beyond software development. My team enjoyed the versatility that allowed us to integrate it with various workflows and structures. It’s also a very performant tool. Everything just works beautifully. However, the pricing structure could be limiting for some teams. If you want some of the more advanced features, they charge you in weird buckets of users. So you might be paying for 10 users, even if you only have a six person team.</p><h3>ClickUp and Linear: The Newcomers</h3><p>Links: <a href="https://clickup.com/">ClickUp</a> and <a href="https://linear.app/">Linear</a></p><p>My experience with ClickUp revealed a comprehensive feature set, aiming to be a one-stop-shop for all project management needs. It’s got whiteboarding, video recording, documents, and more. You can do a <strong><em>lot</em></strong> in ClickUp. I appreciated its customizable interface and integration with other tools. For some people, I can imagine the extent of the features and customizability might be a bit overwhelming, though. One other thing I quite like is the GitHub and GitLab integrations: I can create PRs (MRs in GitLab’s case) and branches directly from ClickUp, and see commits associated with the work. In the end I moved our work from Asana to ClickUp. One thing I found frustrating though: in Asana, everything is really fast and smooth… ClickUp has better pricing, and a broader feature set, but things are a little slower/clunkier, but they are visibly improving quite quickly.</p><p>When I tried Linear, I was drawn to its clean, streamlined interface, which seems designed with simplicity and speed in mind. The focus on performance and ease of use was a breath of fresh air. It seems ideal for a fast-paced environment. It really is perfectly tailored to iterative software development processes. Its minimalistic approach may not suit teams looking for extensive customization options or advanced features, though. For example, I tried to see what it would look like if I were to move our setup over from Asana to Linear. I could not, because we were using multiple GitHub Organizations and GitLab Groups, which they did not support yet. (I think they do now)</p><h3>Notion and Coda: The Adaptable Duo</h3><p>Links: <a href="https://www.notion.so/">Notion</a> and <a href="https://coda.io/">Coda</a></p><p>My exploration led me to Notion as well. It’s a versatile tool that combines note-taking, document management, and task tracking into a single platform. I found the flexibility it offers allowed me to create unique workflows that could be tailored to our specific needs if we switched. But in the end, I didn’t like the “document-first” approach. For me, project management is about process first, knowledge management second. The Notion experience is the reverse, which is fine, but didn’t “click” for me.</p><p>Coda is another, very similar tool I decided to check out. To be completely honest, it struck me as very, very similar to Notion from a user experience perspective: you can do process management, but it feels more focused on knowledge management. One thing I found neat about Coda is the incredible number of integrations and automations. It seems like you can plug Coda into basically anything, allowing you to build really complex systems that tie into your other tools. It just feels weird to me that the primary way of interacting with those systems is documents.</p><h3>Height: The Minimalist</h3><p>Links: <a href="https://height.app/">Height</a></p><p>Lastly, I tried Height, a minimalist project management tool that focuses on simplicity and ease of use that someone recommended to me. He he mentioned that their support team was absolutely fantastic, which I would agree with. I found its streamlined interface and straightforward features to be refreshing and probably great for tech teams that value a clutter-free workspace. I ran into the same limitation as Linear, though: I couldn’t connect it to multiple GitHub Organizations / GitLab Groups, so it was impossible to move our workflows over.</p><h3>Conclusion</h3><p>These are all really interesting tools, with different ways of doing similar things. I think the key thing is to try a few of them out and see what “clicks” for you. By exploring different options and considering your team’s unique requirements, you can find the perfect fit (well… maybe not <em>perfect</em>, but you’ll find something that works better for you than any of the other things). Whether you prioritize flexibility, simplicity, or a comprehensive feature set, there is a tool out there that will [mostly] do the job for you, and hopefully this helped you find one!</p><p>🤝 If you think we could work together, we’d love to partner up and help you with your projects!<br>✉️ Sign up for the newsletter: <a href="https://s.goec.io/newsletter">https://s.goec.io/newsletter</a><br>🎙 The Small Tech Podcast by EC: <a href="https://smalltechpodcast.com/">https://smalltechpodcast.com</a><br>🎥 Watch our videos: <a href="https://s.goec.io/videos">https://s.goec.io/videos</a><br>➡️ Shoot us a message: <a href="https://s.goec.io/contact">https://s.goec.io/contact</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29ffb65aee07" width="1" height="1" alt=""><hr><p><a href="https://blog.ephemerecreative.ca/exploring-project-management-tools-for-small-tech-teams-29ffb65aee07">Exploring Project Management Tools for Small Tech Teams</a> was originally published in <a href="https://blog.ephemerecreative.ca/">Éphémère Creative</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Chewy Stack]]></title>
            <link>https://blog.ephemerecreative.ca/the-chewy-stack-8973884047a6?source=rss-7c9e75e19092------2</link>
            <guid isPermaLink="false">https://medium.com/p/8973884047a6</guid>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[Raphaël Titsworth-Morin]]></dc:creator>
            <pubDate>Fri, 20 Jan 2023 00:02:32 GMT</pubDate>
            <atom:updated>2023-01-20T00:48:47.607Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*YSGTcak6Cqk5lHamp4FN1A.png" /></figure><p>Hi folks! I’m Raphaël, and I’m building a project called the Chewy Stack to help developers deploy complex applications faster.</p><p>I wanted to write a little something about the Chewy Stack, the motivations behind it, and the philosophy behind its architecture. Some of this stuff is also in our <a href="https://docs.gochewy.io/docs/introduction">docs</a>, but I want to give people a sense of why I, as an individual, wanted to build this thing.</p><h3>Some History</h3><p>The initial idea for the Chewy Stack came about four years ago in early 2019. I was working on a couple different projects at the time, and was thinking about the similarities I found across them. Some of it was agency work (I’m a co-founder of <a href="https://ephemerecreative.ca/">Éphémère Creative</a>) and some of it was part-time contract work. Essentially my thought was that a lot of different web and mobile products have very similar needs, or at least there is a lot of overlap between their needs. For example, most of the types of projects I work on need two or more of the following:</p><ul><li>some sort of API</li><li>a web and/or mobile client</li><li>auth</li><li>object storage</li><li>search</li><li>admin panel</li><li>BI dashboard</li><li>etc.</li></ul><p>I also generally found that it made sense, at their scale and budget, to use off-the-shelf open-source tools rather than building anything custom. Often, tools like Firebase were a no-go. Sometimes it was because of data residency requirements. Sometimes because the functionality they required would be easier to build on a SQL database. Or some other reason.</p><h3>Some Patterns</h3><p>In the end, I developed a stack that I liked and re-used across multiple projects, which consisted (mostly) of <a href="https://www.postgresql.org/">Postgres</a>, <a href="https://hasura.io/">Hasura</a>, <a href="https://nestjs.com/">Nest.js</a>, <a href="https://www.keycloak.org/">Keycloak</a>, and <a href="https://nextjs.org/">Next.js</a> or <a href="https://expo.dev/">Expo</a>. More recently I’ve started moving away from Keycloak towards <a href="https://www.ory.sh/">Ory Kratos/Oathkeeper</a>. In certain cases, I also deployed <a href="https://www.appsmith.com/">AppSmith</a> and <a href="https://www.metabase.com/">Metabase</a> and I considered tools like <a href="https://www.meilisearch.com/">Meilisearch</a> in a couple instances.</p><p>Now… getting all those different tools to play nicely together, instead of just building a simple Django or Rails app can be a little daunting, and there are potential operational and performance disadvantages at smaller scales. But once they are hooked up properly, and playing nicely together… it’s a really nice set of tools to work with: they offer a lot of functionality out of the box, which I’ve found a lot of clients end up asking for and I like that they can scale and be managed independently. Another advantage was I found that when working with less experienced developers, they found that, if the development environment was well setup for them, they could develop features much faster with this stack than with others. Which brings us to…</p><h3>Tooling</h3><p>So I had sort of templated a bunch of stuff that would make our work more efficient internally:</p><ul><li>Cloud-based development environments, to make sure every dev had everything they needed to work with the stack.</li><li>Scripts and configurations to make the stack run nicely and make it easy for devs not to have to think too much about the underlying complexity</li><li>A bunch of deployment stuff to make it easy to deploy to different environments</li></ul><p>Now, the <em>idea</em> for the Chewy Stack had started way back, and I had started to build an early version of it back then. But it’s only after 2–3 more years of building projects for various clients that I really wished I had it available to me in my tool box. I also learned a lot about what would make it more efficient to work on those projects in that time.</p><p>So a couple years ago I decided we (Éphémère Creative) should probably dedicate some time towards the Chewy Stack. We were two developers at the time, including myself, and we spent a few months building out an early version of it. It was a really great starting point and a nice exploration of what the Chewy Stack could be. But over the following year and a half, I realized something: it felt too much like a somewhat customizable template, rather than a framework.</p><h3>A Framework</h3><p>Since then, I’ve re-imagined what the Chewy Stack should be to address the pains I had felt:</p><p><em>The Chewy Stack is a framework, built on required and optional components, organized in a dependency graph in which each node is aware of information about related nodes.</em></p><p>(I’m sure that definition will keep evolving)</p><p>I say “components” rather than “services” because here’s one of the important things for me about this framework: it is aware of infrastructure, so the CLI will help you manage infrastructure as well as the services that run on top of it.</p><p>The goal is that if you want to run Next.js on Vercel, Hasura on Hasura Cloud, and Nest.js on a DigitalOcean kubernetes cluster, the Chewy Stack will help you do that, from development to deployment. Each service will know how to connect to the others in production, staging, etc., and your development environment will work with zero additional effort from you. You just write your code and run the deploy command when you’re ready.</p><p>And we’re developing interfaces to specify how all of this should work so that anyone can develop Chewy Stack-compatible services and deployment targets: this thing will be extensible. It might not be quite there yet when our first beta comes out… but it will get there eventually! That’s not to say this will be for everybody, but hopefully the extensibility will make it possible for a wider variety of use cases down the line.</p><p>Oh, a quick note about the code. We’re building everything in TypeScript, even though there are certain parts of the system that might have benefited from a different language. The reason is to make the entire codebase accessible to developers we’re hoping will benefit from this. So if you like building on Next.js and/or Nest.js in TypeScript, you should be able to hop into the Chewy Stack code and feel right at home 😊</p><p>If you want to learn more about the Chewy Stack, want to chat, contribute, help out, ask questions, etc. you can find me on our <a href="http://s.gochewy.io/discord">Discord</a>, or you can poke around the code on <a href="https://github.com/gochewy">GitHub</a> (and if you have any suggestions about the code/architecture/etc. please let me know! I would really appreciate the help!)</p><h3>About Money</h3><p>So… there are a few things we haven’t figured out yet, money-wise. It’s taking a lot of my time to build this! So I want to say a few things about money.</p><p>The first is that the core functionality of the Chewy Stack should always be freely available.</p><p>That being said, this thing needs to be financially sustainable. I recently enabled the sponsorship button on GitHub. But I know that it’s early for people who don’t know us to support. And unless a big infrastructure provider decides to sponsor, that’s not going to be the thing that keeps us going.</p><p>We will definitely paywall some extra functionality, eventually. Maybe that’s collaborative features. Maybe we’ll do something like a licence where for-profit companies with more than X developers need to pay a yearly fee on an honour system. Maybe it’s something tied to deployment, or monitoring. I’m not sure. But if you have any suggestions, I’d gladly take them 😂</p><p>Finally, since I mentioned licencing… after a chat with someone recently, I decided to throw the AGPL v3 on all of our code… but I’m not sure I like that. I’ll probably be switching it to something more permissive. But I’m really a novice regarding licencing, so if anyone has advice, I’d appreciate it!</p><p>Again, if anyone reads this and finds it neat, please come find me on our <a href="http://s.gochewy.io/discord">Discord</a> or shoot me a message at <a href="https://mailto:raphael@gochewy.io/">raphael@gochewy.io</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8973884047a6" width="1" height="1" alt=""><hr><p><a href="https://blog.ephemerecreative.ca/the-chewy-stack-8973884047a6">The Chewy Stack</a> was originally published in <a href="https://blog.ephemerecreative.ca/">Éphémère Creative</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We did it! (maybe)]]></title>
            <link>https://blog.ephemerecreative.ca/we-did-it-maybe-ed0f4c70d33f?source=rss-7c9e75e19092------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed0f4c70d33f</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[ec-methodology]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Raphaël Titsworth-Morin]]></dc:creator>
            <pubDate>Tue, 17 Jan 2023 18:02:29 GMT</pubDate>
            <atom:updated>2023-02-16T23:03:48.531Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome back to our series on EC’s methodology.</p><p>Last time we talked about <a href="https://blog.ephemerecreative.ca/watch-out-25b4aef3c128">prevention of major breakdowns and setting yourself up for quick recovery</a>. Today we’ll talk about gathering data to better understand your progress.📊</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*o6WB3aqOJLwwCC5p.jpg" /></figure><p>Each project will have a different definition of success. In almost every case, you’ll need both quantitative and qualitative feedback to assess whether you’ve reached your goals. That’s the final piece of the puzzle. <strong>We need to identify metrics that correlate with success and keep track of them.</strong></p><p>There are many types of data you could consider for your success metrics. Here are a few we like to consider when building an app:</p><ul><li><strong>App Data </strong>— This is the data in your database. If you’re building a “todo” app, it might be the number of todos created. We like to monitor this type of data with <a href="https://www.metabase.com/">Metabase</a>.</li><li><strong>Behavioural Data </strong>— This is data gathered from how users interact with your app. Typically this is collected and measured using analytics tools, like our favourites: <a href="https://segment.com/">Segment</a>, <a href="https://analytics.google.com/">Google Analytics</a>, and <a href="https://mixpanel.com/">Mixpanel</a>.</li><li><strong>Operational Data </strong>— This is data that answers questions like “how many features did we release this quarter”</li><li><strong>Performance Data </strong>— The type of metrics we might extract from our <a href="https://blog.ephemerecreative.ca/watch-out-25b4aef3c128">previous blog post about observability</a>: how fast everything is running, how often things go wrong, etc.</li><li><strong>Qualitative Feedback </strong>— Feedback from users is crucial to understanding where you are at, and where you should go. This is harder to measure, but absolutely essential. <strong><em>Connect with your users.</em></strong></li></ul><p>😊If you found this helpful and would like to learn more about what goes into building software, we’ve put together an extensive FREE PDF that covers all areas of custom software! Take a look <a href="http://landing.ephemerecreative.ca/how-to-build-an-app">here</a> ↗️</p><p>✍️ What tools do you use to analyze data?</p><p>🚀 Follow us if you want to keep up with this series! We have a lot more to share with you! We’re constantly updating this process as we learn from ourselves, our partners, and our community 🙂</p><p>🤝 If you think we could work together, we’d love to partner up and help you with your projects!</p><p>🎙 Subscribe to the podcast: <a href="https://podcast.ephemerecreative.ca/">https://podcast.ephemerecreative.ca/</a></p><p>🎥 Watch our videos: <a href="https://www.youtube.com/@ephemerecreative">https://www.youtube.com/@ephemerecreative</a></p><p>➡️ Shoot us a message over here <a href="https://ephemerecreative.ca/contact-us/">https://ephemerecreative.ca/contact-us/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed0f4c70d33f" width="1" height="1" alt=""><hr><p><a href="https://blog.ephemerecreative.ca/we-did-it-maybe-ed0f4c70d33f">We did it! (maybe)</a> was originally published in <a href="https://blog.ephemerecreative.ca/">Éphémère Creative</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Watch out!]]></title>
            <link>https://blog.ephemerecreative.ca/watch-out-25b4aef3c128?source=rss-7c9e75e19092------2</link>
            <guid isPermaLink="false">https://medium.com/p/25b4aef3c128</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[ec-methodology]]></category>
            <dc:creator><![CDATA[Raphaël Titsworth-Morin]]></dc:creator>
            <pubDate>Tue, 10 Jan 2023 18:02:31 GMT</pubDate>
            <atom:updated>2023-02-17T21:19:03.122Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome back to our series on EC’s methodology.</p><p>Last time we talked about <a href="http://www.medium.com/we-need-to-talk">communicating with your users</a>. Today we’ll talk about tools to help stabilize your systems and prevent major breakdowns. ⚖️</p><p><em>Want this content in video form? </em><a href="https://youtu.be/OLWP2guLWgE"><em>Watch it here.</em></a></p><p><em>Want a podcast version you can take on the go? </em><a href="https://podcast.ephemerecreative.ca/episodes/watch-out"><em>Listen to it here.</em></a></p><figure><img alt="Image of a bunny with the text “TypeError: ‘undefined’ is not an object” layered on top." src="https://cdn-images-1.medium.com/max/1024/0*Lly0_zK6PntAl5Si.jpg" /><figcaption>Photo by <a href="https://unsplash.com/@kris_ricepees?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Gary Bendig</a> on <a href="https://unsplash.com/s/photos/alert?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>You’ll do everything to make sure the system doesn’t go down, but it inevitably will. You can’t guarantee stability in complex systems, but you can take steps to quickly recover and learn from outages.</p><p>If you do go down the Kubernetes path, then you probably already have access to something similar to the <a href="https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/">Kubernetes Dashboard</a> from your cloud provider. This is a quick way to quickly understand if you have any services that are down, or have any issues. You’ve also have configured “liveness” probes to make sure services restart on failure. But despite those, <strong>you’ll want to make sure you can be alerted of any failures, and that you have an easy path to diagnosing issues.</strong></p><p>For this reason we strongly recommend using observability tools like <a href="https://newrelic.com/">NewRelic</a>, <a href="https://www.datadoghq.com/">DataDog</a>, or the <a href="https://betterstack.com/">BetterStack</a> tools. They will give you <strong>the ability to be notified when anything isn’t running correctly</strong>.</p><p>Lately we’ve been using BetterStack for our customers, because we like their billing model and the simplicity of their tooling. But we’ve also used the other two, which are more powerful, but are also more complicated to configure and manage from a billing perspective. DataDog, for example, charges based on hosts, or other metrics which don’t always correlate with the value we, or our clients, derive from them.</p><p>😊If you found this helpful and would like to learn more about what goes into building software, we’ve put together an extensive FREE PDF that covers all areas of custom software! Take a look <a href="http://landing.ephemerecreative.ca/how-to-build-an-app">here</a> ↗️</p><p>✍️ Drop a comment and tell us what you do to prevent major security issues! 🙏</p><p>🚀 Follow us if you want to keep up with this series! We have a lot more to share with you! We’re constantly updating this process as we learn from ourselves, our partners, and our community 🙂</p><p>🤝 If you think we could work together, we’d love to partner up and help you with your projects!</p><p>🎙 Subscribe to the podcast: <a href="https://podcast.ephemerecreative.ca/">https://podcast.ephemerecreative.ca/</a></p><p>🎥 Watch our videos: <a href="https://www.youtube.com/@ephemerecreative">https://www.youtube.com/@ephemerecreative</a></p><p>➡️ Shoot us a message over here <a href="https://ephemerecreative.ca/contact-us/">https://ephemerecreative.ca/contact-us/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25b4aef3c128" width="1" height="1" alt=""><hr><p><a href="https://blog.ephemerecreative.ca/watch-out-25b4aef3c128">Watch out!</a> was originally published in <a href="https://blog.ephemerecreative.ca/">Éphémère Creative</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We need to talk…]]></title>
            <link>https://blog.ephemerecreative.ca/we-need-to-talk-4456bcb05d2f?source=rss-7c9e75e19092------2</link>
            <guid isPermaLink="false">https://medium.com/p/4456bcb05d2f</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[ec-methodology]]></category>
            <dc:creator><![CDATA[Raphaël Titsworth-Morin]]></dc:creator>
            <pubDate>Tue, 03 Jan 2023 18:01:45 GMT</pubDate>
            <atom:updated>2023-02-15T17:57:52.990Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome back to our series on EC’s methodology.</p><p>Last time we talked about <a href="https://blog.ephemerecreative.ca/deliver-continuously-18aa8f228120">automation</a>. Today we’ll talk about communicating with your users 📞✉️</p><p><em>Want this content in video form? </em><a href="https://youtu.be/YpsVA3FtWkE"><em>Watch it here.</em></a></p><p><em>Want a podcast version you can take on the go? </em><a href="https://youtu.be/YpsVA3FtWkE"><em>Listen to it here.</em></a></p><figure><img alt="Image of a man, on the left, with his right hand upturned suggesting he’s explaining something to a woman and man to his right. The phrase “…so why have you stopped using our product?” is layered at the top." src="https://cdn-images-1.medium.com/max/1024/0*AoQrgAMHsWA-hRF_.jpg" /><figcaption>Photo by <a href="https://unsplash.com/@priscilladupreez?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Priscilla Du Preez</a> on <a href="https://unsplash.com/s/photos/talking?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Sometimes it’s about confirming an email address, and other times it’s about notifying users about something, or sending them on-boarding messages. Sometimes it’s about asking them why they aren’t using your product anymore so you can address any problems.</p><p>Communication takes many forms, but the most common on the web is email. So <strong>the first thing you’ll probably need to do is configure an SMTP (simple mail transfer protocol) provider, like </strong><a href="https://sendgrid.com/"><strong>SendGrid</strong></a><strong>. </strong>Remember how we talked about domains earlier? Your users will probably expect to see your domain when you send them a password reset email, or an onboarding email. SMTP services like SendGrid will allow you to configure your domain to do this securely.</p><p>You can use tools like SendGrid right out of the box, but we find it’s simpler and more powerful to work with analytics-driven tools. <strong>We recommend using a tool like </strong><a href="https://segment.com/"><strong>Segment</strong></a><strong> to unify your customer data across different parts of your infrastructure, and using it to leverage tools like </strong><a href="https://www.intercom.com/"><strong>Intercom</strong></a><strong> or </strong><a href="http://customer.io/"><strong>Customer.io</strong></a><strong>. to easily reach users at the right point in the user journey.</strong></p><p>😊If you found this helpful and would like to learn more about what goes into building software, we’ve put together an extensive FREE PDF that covers all areas of custom software! Take a look <a href="http://landing.ephemerecreative.ca/how-to-build-an-app">here</a> ↗️</p><p>✍️ How are you setup for communication with your customers?</p><p>🚀 Follow us if you want to keep up with this series! We have a lot more to share with you! We’re constantly updating this process as we learn from ourselves, our partners, and our community 🙂</p><p>🤝 If you think we could work together, we’d love to partner up and help you with your projects!</p><p>🎙 Subscribe to the podcast: <a href="https://podcast.ephemerecreative.ca/">https://podcast.ephemerecreative.ca/</a></p><p>🎥 Watch our videos: <a href="https://www.youtube.com/@ephemerecreative">https://www.youtube.com/@ephemerecreative</a></p><p>➡️ Shoot us a message over here <a href="https://ephemerecreative.ca/contact-us/">https://ephemerecreative.ca/contact-us/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4456bcb05d2f" width="1" height="1" alt=""><hr><p><a href="https://blog.ephemerecreative.ca/we-need-to-talk-4456bcb05d2f">We need to talk…</a> was originally published in <a href="https://blog.ephemerecreative.ca/">Éphémère Creative</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deliver. Continuously.]]></title>
            <link>https://blog.ephemerecreative.ca/deliver-continuously-18aa8f228120?source=rss-7c9e75e19092------2</link>
            <guid isPermaLink="false">https://medium.com/p/18aa8f228120</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[ec-methodology]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Raphaël Titsworth-Morin]]></dc:creator>
            <pubDate>Tue, 20 Dec 2022 18:01:53 GMT</pubDate>
            <atom:updated>2023-02-15T17:56:03.249Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome back to our series on EC’s methodology.</p><p>Last time we talked about <a href="https://blog.ephemerecreative.ca/wait-am-i-a-user-b1d12e343936">admin panels</a>. Today we’ll talk about automation ⚙️</p><p><em>Want this content in video form? </em><a href="https://youtu.be/zoUFa0s9hjQ"><em>Watch it here.</em></a></p><p><em>Want a podcast version you can take on the go? </em><a href="https://podcast.ephemerecreative.ca/episodes/deliver-continuously"><em>Listen to it here.</em></a></p><figure><img alt="Gears with the word “automation” layered on top." src="https://cdn-images-1.medium.com/max/1024/0*__utLloFhnB5jmHX.jpg" /><figcaption>Photo by <a href="https://unsplash.com/@joshredd?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Josh Redd</a> on <a href="https://unsplash.com/s/photos/gears?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>You don’t want to get stuck manually deploying the latest versions of your app. That path leads to bottlenecks and uncertainty. You need to make sure features get delivered into peoples hands through smooth, automated, consistent processes.</p><p>Modern tools make it a lot easier to automate huge swaths of the software development and deployment process. If you ever find you, or your team, manually tweaking things on a server during a deployment, ask yourself <strong>“What happens if that team member suddenly leaves? Do we know how to get the app in production?”</strong> What if you haven’t deployed for a couple months? Are you certain you’re going through the right steps?</p><p>For every app we build, we also build out a continuous integration, delivery, and deployment pipeline, making sure that <strong>code is automatically tested, compiled, packaged, and deployed through automated systems. </strong>We do this using tools like <a href="https://about.gitlab.com/stages-devops-lifecycle/continuous-integration/">GitLab CI/CD</a> and <a href="https://www.pulumi.com/">Pulumi</a> usuall, but we’ve also used other tools like <a href="https://www.terraform.io/">Terraform</a>, <a href="https://circleci.com/">CircleCI</a>, and <a href="https://github.com/features/actions">GitHub Actions</a>.</p><p>Not only does building a process like this reduce the amount of work required for a deployment, it also <strong>reduces fragility and forces you to properly consider and design the steps required to deploy, </strong>since you have to code them out.</p><p>😊If you found this helpful and would like to learn more about what goes into building software, we’ve put together an extensive FREE PDF that covers all areas of custom software! Take a look <a href="http://landing.ephemerecreative.ca/how-to-build-an-app">here</a> ↗️</p><p>✍️ Drop a comment if you do automation, we’d love to hear about your experiences 🙏</p><p>🚀 Follow us if you want to keep up with this series! We have a lot more to share with you! We’re constantly updating this process as we learn from ourselves, our partners, and our community 🙂</p><p>🤝 If you think we could work together, we’d love to partner up and help you with your projects!</p><p>🎙 Subscribe to the podcast: <a href="https://podcast.ephemerecreative.ca/">https://podcast.ephemerecreative.ca/</a></p><p>🎥 Watch our videos: <a href="https://www.youtube.com/@ephemerecreative">https://www.youtube.com/@ephemerecreative</a></p><p>➡️ Shoot us a message over here <a href="https://ephemerecreative.ca/contact-us/">https://ephemerecreative.ca/contact-us/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18aa8f228120" width="1" height="1" alt=""><hr><p><a href="https://blog.ephemerecreative.ca/deliver-continuously-18aa8f228120">Deliver. Continuously.</a> was originally published in <a href="https://blog.ephemerecreative.ca/">Éphémère Creative</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wait. Am I a user?]]></title>
            <link>https://blog.ephemerecreative.ca/wait-am-i-a-user-b1d12e343936?source=rss-7c9e75e19092------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1d12e343936</guid>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[ec-methodology]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Raphaël Titsworth-Morin]]></dc:creator>
            <pubDate>Tue, 13 Dec 2022 18:01:46 GMT</pubDate>
            <atom:updated>2023-02-14T18:55:39.406Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome back to our series on EC’s methodology.</p><p>Last time we talked about <a href="https://blog.ephemerecreative.ca/dont-forget-to-lock-up-287e7d470ce9">security</a>. Today we’ll talk about administration 🖥️</p><p><em>Want this content in video form? </em><a href="https://youtu.be/sItqnZvA1AU"><em>Watch it here.</em></a></p><p><em>Want a podcast version you can take on the go? </em><a href="https://podcast.ephemerecreative.ca/episodes/wait-am-i-a-user"><em>Listen to it here.</em></a></p><figure><img alt="Confused german shepherd puppy with the words “user?” and “admin?” layered on top." src="https://cdn-images-1.medium.com/max/1024/0*reC-D5g-MKCYzL5z.jpg" /></figure><p>You might be building this app for someone else to use, but most apps need to be managed, so you’ll probably need an admin account and interface too.</p><p>We find that it’s very common for people to initially focus on the problems they want to solve for their end users and lose track of their role within the system. <strong>You inevitably need ways to manage the apps you build.</strong></p><p>Sometimes this means building out a whole separate app for the internal team to use (or at the very least, a separate section in the main app). If you’re using a framework like Django, you might use the <a href="https://docs.djangoproject.com/en/4.0/ref/contrib/admin/">Django Admin</a> to whip up something quickly.</p><p>For simple data access/management, a tool like the Django Admin makes sense. If you’ve got complex requirements, a custom system makes sense. If you land somewhere in between, as most do, then using <strong>a system like </strong><a href="https://www.appsmith.com/"><strong>AppSmith </strong></a><strong>(open source, self-hosted or paid) or </strong><a href="https://retool.com/"><strong>Retool </strong></a><strong>(paid service) will give you a balance between simplicity and power, which can be a nice place to start.</strong></p><p>😊If you found this helpful and would like to learn more about what goes into building software, we’ve put together an extensive FREE PDF that covers all areas of custom software! Take a look <a href="http://landing.ephemerecreative.ca/how-to-build-an-app">here</a> ↗️</p><p>✍️ How do you do admin panels?</p><p>🚀 Follow us if you want to keep up with this series! We have a lot more to share with you! We’re constantly updating this process as we learn from ourselves, our partners, and our community 🙂</p><p>🤝 If you think we could work together, we’d love to partner up and help you with your projects!</p><p>🎙 Subscribe to the podcast: <a href="https://podcast.ephemerecreative.ca/">https://podcast.ephemerecreative.ca/</a></p><p>🎥 Watch our videos: <a href="https://www.youtube.com/@ephemerecreative">https://www.youtube.com/@ephemerecreative</a></p><p>➡️ Shoot us a message over here <a href="https://ephemerecreative.ca/contact-us/">https://ephemerecreative.ca/contact-us/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1d12e343936" width="1" height="1" alt=""><hr><p><a href="https://blog.ephemerecreative.ca/wait-am-i-a-user-b1d12e343936">Wait. Am I a user?</a> was originally published in <a href="https://blog.ephemerecreative.ca/">Éphémère Creative</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>