<?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 The [e-spres-oh] Team on Medium]]></title>
        <description><![CDATA[Stories by The [e-spres-oh] Team on Medium]]></description>
        <link>https://medium.com/@espresoh?source=rss-d61e3d499379------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Fzj0wmZ0_v2pFF-fjh8wDg.jpeg</url>
            <title>Stories by The [e-spres-oh] Team on Medium</title>
            <link>https://medium.com/@espresoh?source=rss-d61e3d499379------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 14:34:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@espresoh/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[What Is Tech Debt and Why Should You Care About It?]]></title>
            <link>https://medium.com/tea-break-by-e-spres-oh/what-is-tech-debt-and-why-should-you-care-about-it-abd57348ea0?source=rss-d61e3d499379------2</link>
            <guid isPermaLink="false">https://medium.com/p/abd57348ea0</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[insights]]></category>
            <dc:creator><![CDATA[The [e-spres-oh] Team]]></dc:creator>
            <pubDate>Tue, 27 Oct 2020 10:22:31 GMT</pubDate>
            <atom:updated>2020-10-30T16:21:32.552Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NmQVzZOyEv-FLwq2Wf8LpQ.png" /></figure><p>Tech debt: can’t live with it, can’t live without it.</p><p>If you’re a non-tech person who’s involved in building a <a href="https://teabreak.e-spres-oh.com/product-or-project-approach-which-one-when-and-why-b3a5b4a3ae2a">software product</a>, you’ll soon reach this verdict. As you try to push a successful product to market, you’ll discover that aligning stakeholders’ expectations, customer needs, financial constraints, deadlines, and tech requirements will often require trade-offs. Most of the time, these “bargains” will mean cutting corners in the development process.</p><p>In the short term, your tech trade-offs can deliver the expected outcome: you’ll put a product to market sooner rather than later. But in the long-run, accumulating “tech debt” can slow-down your work and cause more harm than good. So, in a world where you want everything (tech-perfect, fast-to-market products), how can you deal with real-scenarios and make things work?</p><p>To solve this puzzle, we’ll explain what tech debt is, when it’s a necessary evil and the consequences of not paying it (spoiler alert: you always should pay it).</p><h3>What’s debt got to do with tech?</h3><p>Tech debt happens due to prioritizing a speedy and imperfect outcome over a longer, more refined, and substantial development process. At first glance, this might sound like a perfectly reasonable thing to do. After all, your interest is to reduce costs and timings to start gaining revenue from your product. Alternatively, project constraints pressure you only to achieve milestones, and 100% product perfection is not your goal.</p><p>Fair enough. However, while prioritizing is okay, the story behind tech debt is not that simple.</p><p>In essence, tech debt appears after a “quick fix” meant to shorten delivery time. The reverse of the coin is that these shortcuts accumulate “interest” and, in time, weigh heavily on the software’s quality and efficiency.</p><p>Think about tech debt as cutting tech corners with the goal of borrowing time. However, sooner rather than later, you’ll be asked to repay that time. Maybe you’ll want to develop a new feature. Maybe you’ll want to address user complaints. Or perhaps you’ll simply want a product upgrade.</p><p>These are just a few cases in which tech debt will come out to ask for its share. In these moments, the fast-tech-solution you opted for will get developers back to square one, as they’ll need to write not only new code but rewrite the “quick fix” as well.</p><h3>Why are software developers so dreary of tech debt?</h3><p>Oh, where to begin? The reasons are bountiful, and they hold water.</p><p>To start, think about the expectations <strong><em>you</em></strong> have from your software team. No doubt, you want your UX designers, <a href="https://teabreak.e-spres-oh.com/product-engineering-bridging-the-gap-between-engineering-and-products-3a5087923e1a">product engineers</a>, and developers to be amazing. However, being excellent stems from having strong skills and even stronger software values.</p><p>Great software teams are great because they care about best practices. They’re eager to work with new technologies and want to bring industry progress to customer products. The best software teams want to dig deep into software architectures and build flawless products with clean code. Aaaand they’re not big fans of shortcuts because these imply delivering less quality than they could.</p><p>Now, an important distinction that our software teams always want to make is that tech debt doesn’t equal a “mess.” <a href="https://sites.google.com/site/unclebobconsultingllc/a-mess-is-not-a-technical-debt">A mess is just a mess</a>. Still, tech debt does mean unpolished code that is not 100% aligned with best practices. It also implies dealing with code that accumulates weaknesses that will need to be addressed at some point.</p><h3>Why should you care about tech debt?</h3><p>Project constraints are real. Sometimes, no matter how much you’d love to have all the time in the world to build your software products by the book, you’ll have no choice but to be sensitive to market realities, investors’ requirements, and business deadlines.</p><p>That means that tech debt can be a reasonable solution — in exceptional cases — as long as there’s a thorough repayment plan to back it up. Otherwise, borrowing from your future tech solution will only seem like progress at first.</p><p>Accumulating too much tech debt will harm your business in several ways:</p><ul><li>It can provide a false sense of achievement. Sure, you’ll manage to achieve your milestones, but the result will fall flat after some time. This will be visible in your ROI and overall user satisfaction.</li><li>Tech debt makes it harder to implement changes later on. For example, in case of an upgrade, before you’ll be able to write a new code, you’ll have to mend the previously “patched” one. That means your costs will go up, and deadlines will be pushed.</li><li>Maintenance itself will become a daunting task. Tech debt can lead to bugs that are hard to track and a nuisance to solve. By cutting down on delivery time, peer reviews and testing become a luxury, so faulty pieces of code can easily make their way into the final product. With more maintenance work to do, your bills will pile up.</li></ul><h3>How can you avoid tech debt?</h3><p>Having the right software team by your side is essential. You want a team that doesn’t just say “yes” whenever you want to lean into tech debt. Instead, you want a team that understands both business needs and technology requirements and can balance the two to deliver a quality product. Ideally, such a software team should include business analysts, product engineers, UX designers, and software developers.</p><p>To avoid tech debt, you first need to <a href="https://teabreak.e-spres-oh.com/the-hard-thing-about-hard-things-the-difficult-conversation-every-software-project-should-start-66f87576f147">admit some hard truths</a> about what it takes to build a successful product. You need to keep a flexible mindset and be open to explore new ways of approaching your development process. For example, a <a href="https://teabreak.e-spres-oh.com/what-to-expect-from-the-discovery-phase-setting-the-course-for-a-successful-product-1b8e30483902">discovery phase</a> can be a great way to address issues. Compared to tech debt, even if a discovery phase requires more time at first, it delivers more quality later on. Continuous development is another approach that can help you deploy products faster and without hindering their quality. By entering a reiterative development process, you can automate and streamline your software efforts.</p><p>The most important thing to remember when dealing with tech debt is that it is what you make of it. It’s neither inherently good nor bad. If necessary, prioritize and borrow time, but always pay it back. If not, remember that there are other development approaches that could take you out of unwanted debt.</p><p>In the end, discussing things openly with a software team that’s keen on quality but also has your business interest at heart will always show you the right way. It’s up to you to take it.</p><p><em>If you want to keep up with our mischievous ways of coding and doing fun things with great energy, subscribe to </em><a href="https://teabreak.e-spres-oh.com/"><em>Tea Break</em></a><em> (our blog right here on Medium), stay up-to-date with our </em><a href="https://www.linkedin.com/company/2820676"><em>LinkedIn</em></a><em>, like our </em><a href="https://www.facebook.com/esoh.tech/"><em>Facebook page</em></a><em>, talk to us on </em><a href="https://twitter.com/e_spres_oh"><em>Twitter</em></a><em> or follow us on </em><a href="https://www.instagram.com/e_spres_oh/"><em>Instagram</em></a><em> (but not in a creepy manner).</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abd57348ea0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tea-break-by-e-spres-oh/what-is-tech-debt-and-why-should-you-care-about-it-abd57348ea0">What Is Tech Debt and Why Should You Care About It?</a> was originally published in <a href="https://medium.com/tea-break-by-e-spres-oh">Tea Break by [e-spres-oh]</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Hard Thing About Hard Things: The Difficult Conversation Every Software Project Should Start…]]></title>
            <link>https://medium.com/tea-break-by-e-spres-oh/the-hard-thing-about-hard-things-the-difficult-conversation-every-software-project-should-start-66f87576f147?source=rss-d61e3d499379------2</link>
            <guid isPermaLink="false">https://medium.com/p/66f87576f147</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[continuous-development]]></category>
            <category><![CDATA[insights]]></category>
            <dc:creator><![CDATA[The [e-spres-oh] Team]]></dc:creator>
            <pubDate>Wed, 30 Sep 2020 08:46:36 GMT</pubDate>
            <atom:updated>2020-10-01T04:22:39.690Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>The Hard Thing About Hard Things: The Difficult Conversation Every Software Project Should Start With</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qm_cCneg9vNemfa_99jt8A.png" /></figure><p>In 2016, Ben Horrowitz dedicated a disruptive book to the lack of easy answers in tech entrepreneurship. While other business and management books lured audiences with the illusion of ‘the promised formulas,’ Horowitz dispelled the haze by putting it bluntly: being a tech entrepreneur is hard. Tremendously rewarding, but incredibly difficult. It has no formulas for success, it has no guarantees, and it’s not a straight paved road. Every tech entrepreneur should get over it and get on with it, learning how to thrive while doing the hard thing.</p><p>Inspired by his honesty and having more than a decade of expertise in the tech-world ourselves, we’re living by the simple hard truths of how successful software products are built. We’re not preaching formulas, just encouraging the formation of adaptable mindsets and courageous skills. Our goal is to help our clients’ tech businesses grow by tackling software products creatively, smart, and efficiently. To achieve that, we’re prioritizing “the difficult talk” — the talk about scopes, budgets, expectations, and goals. We insist on having it early on. In fact, let’s have it right now.</p><h3><strong>You can’t predict all the tech roadblocks. <em>But you can adapt and overcome.</em></strong></h3><p>Passion is everything, and you should be in love with your software product idea. However, love is sometimes blind, and <a href="https://teabreak.e-spres-oh.com/surpassing-cognitive-biases-in-business-how-to-recognize-the-most-common-pitfalls-and-build-a57cfaa3ab1c">cognitive biases</a> are always lurking around the corner. Thus, chances are that you won’t predict all the limitations, flaws, and challenges down the road. No amount of complex prediction models, stats, or metrics will be able to foresee the future with 100% certainty.</p><p>In this context, when starting a new software project, you might have the impression that you know exactly <strong><em>how</em></strong> you want your <strong><em>software</em></strong> <strong><em>product to look and behave</em></strong>. You might already envision not only your end goal but your success as well. Of course, you expect the same amount of certainty from your development team. Some software companies will be ‘yes’ sayers, giving you the confidence to do it fast and under budget. They will make every possible effort to ensure that they will pull it through no matter what. In fact, they will be drawing you back.</p><p>The reality is that building software products in our current ever-evolving context leaves little room for certainties. What’s in today might be out tomorrow, and what’s important for people now might be considered superfluous in no time. Smart software products are not built on rigid, set-in-stone blueprints. They are symbiotic tech organisms that evolve with the market and its needs.</p><p><em>So, instead of falling into the trap of a waterfall development paradigm, in which you nail down a list of features and then ask your development team to implement it fast, fine-tune your mindset to the market.</em></p><p>Ideally, you should start with a <a href="https://teabreak.e-spres-oh.com/what-to-expect-from-the-discovery-phase-setting-the-course-for-a-successful-product-1b8e30483902">discovery phase</a> to dive into the deep end of what you know and, more importantly, what you don’t know about your future product. Once you do that, you’ll have a clearer idea of where to head next.</p><p><em>For all the products we build, our recommendation is to start with the hard things: build the features you’re not sure about upfront and test them. Adapt as you go. Go back on what you thought was right. Improve. Be smart about it. Grow as your product grows.</em></p><h3><strong>You can’t have all the answers. But you can ask better questions.</strong></h3><p>As an entrepreneur, it’s only natural to keep a close eye on your budget. There are so many areas that need capital infusion, and you can’t afford not knowing where each cent goes. It’s no wonder the first question you’ll ask your software development team is, “How much will it cost?”. Unfortunately, the answer isn’t that simple.</p><p><em>The most efficient way to develop software is by having clear and detailed up-front requirements. But this may not be the best business decision given the market’s insane pace and the unknowns that come with every new beginning. The smart approach is to be flexible, prepare to learn along the way and admit that there’s room for slightly different outcomes that initially anticipated. In a nutshell, move fast, test the biggest assumptions first, and pivot when necessary. Lather, rinse, repeat.</em></p><p>By switching from “how much it costs?” to “what budget should I allocate?,” you commit yourself to a better outcome. You switch from the <a href="https://teabreak.e-spres-oh.com/product-or-project-approach-which-one-when-and-why-b3a5b4a3ae2a">“project mindset” to the “product mindset” </a>and recognize the value of <strong>continuous development</strong>. You enable your software teams to tackle the product smartly, identify potential roadblocks, explore new paths, and ultimately build it to answer real, current needs.</p><h3><strong>You can’t keep everything under control. But you can embrace new opportunities.</strong></h3><p>Your software product doesn’t live in a vacuum — not when the idea for it first pops up, not when you discuss it with your development partners, and not when it finally reaches the end-users. If you accept this, you’ll also have to admit that you won’t be able to control everything that influences your product. However, you can be smart about it and take whatever comes its way as a new opportunity.</p><p>The hard truth is that as your software product progresses, you will encounter challenges. It’s a given. It’s normal, and you should be prepared for it. Your software development partners should be there to help you plan for success from the very beginning, but also help you plan for crisis-time before the tech boat will start to rock. And.it.will.rock.</p><p>That’s why it’s essential to<a href="https://teabreak.e-spres-oh.com/how-we-start-successful-software-engagements-with-great-energy-3284cb8f962e"> start your software development project</a> by having an honest conversation, by discussing a plan, by crafting escape scenarios that can reroute your product, and by leaving room for adaptability. Recognizing that there’s no certainty will save yourself a lot of time, money, and sleepless nights in the long-run. And it will also equip you with the mindset and skills needed to adapt and continue to march forward. No matter how hard it will get. Because, as Ben Horowitz put it:</p><blockquote><em>“Sometimes, an organization doesn’t need a solution; it just needs clarity.”</em></blockquote><p><em>If you want to keep up with our mischievous ways of coding and doing fun things with great energy, subscribe to </em><a href="https://teabreak.e-spres-oh.com/"><em>Tea Break</em></a><em> (our blog right here on Medium), stay up-to-date with our </em><a href="https://www.linkedin.com/company/2820676"><em>LinkedIn</em></a><em>, like our </em><a href="https://www.facebook.com/esoh.tech/"><em>Facebook page</em></a><em>, talk to us on </em><a href="https://twitter.com/e_spres_oh"><em>Twitter</em></a><em> or follow us on </em><a href="https://www.instagram.com/e_spres_oh/"><em>Instagram</em></a><em> (but not in a creepy manner).</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66f87576f147" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tea-break-by-e-spres-oh/the-hard-thing-about-hard-things-the-difficult-conversation-every-software-project-should-start-66f87576f147">The Hard Thing About Hard Things: The Difficult Conversation Every Software Project Should Start…</a> was originally published in <a href="https://medium.com/tea-break-by-e-spres-oh">Tea Break by [e-spres-oh]</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Decoding the language of great software products: A tech dictionary for businesses]]></title>
            <link>https://medium.com/tea-break-by-e-spres-oh/decoding-the-language-of-great-software-products-a-tech-dictionary-for-businesses-64583c042aaf?source=rss-d61e3d499379------2</link>
            <guid isPermaLink="false">https://medium.com/p/64583c042aaf</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[The [e-spres-oh] Team]]></dc:creator>
            <pubDate>Wed, 29 Jul 2020 12:50:10 GMT</pubDate>
            <atom:updated>2020-07-29T12:50:10.438Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kk50E7HwEy-IGSP07WvYKA.jpeg" /></figure><p>Development teams use programming languages to code, but they also have a language of their own for day-to-day communication. Tech jargon saves developers a lot of time, but can often feel overwhelming for clients who want to build software products.</p><p>When embarking on a new tech project, it’s the duty of the software team to onboard clients not only on the work process but also on their jargon rollercoaster. However, it’s always good for stakeholders to be in-the-know even before approaching a development company for a new product. By understanding what the most common tech jargon means, you’ll be better rooted in your product’s development from the get-go. Whether you’re leading an enterprise, a medium business, or driving the efforts of a start-up, pour yourself an [e-spres-oh] and learn with us the tech words of the day.</p><h3><strong>Tech jargon worth knowing before starting a software project</strong></h3><h4><strong>Agile Development</strong></h4><p>A set of 12 principles that lay out an ideal <a href="https://agilemanifesto.org/">software development approach</a><strong>. </strong>Agile Development recommends <strong>slicing functionalities into work phases </strong>(aka sprints) and focuses on <strong>iterations</strong> and <strong>adaptability</strong>, enabling teams to tackle long-term projects sustainably. It’s like running a mountain marathon: in the distance, you see the finish, but you break-down the course into manageable sprints and focus on one race at a time. After each sprint, you tweak your approach for the next portion and so on, until you reach the finish line.</p><h4><strong>Backend</strong></h4><p>The infrastructure of a software application that’s not visible to visitors, but is vital to the well-functioning of the software. Think about it as the kitchen of a restaurant: as a client, you can’t see it, but it’s where all the delicious magic happens. Without it, you’d be served…nothing. Examples of programming languages used for backend development: Ruby, Node.js, Python, Java, Perl, GoLang, PHP.</p><h4><strong>Continuous development (CD)</strong></h4><p>A collection of practices aimed at continuously improving a product through planning, delivering, gathering feedback, and acting on that feedback. Similar to the <strong>Agile </strong>principles, CD focuses on <strong>iterations</strong> and <strong>incremental</strong> <strong>delivery</strong>, while also leveraging the power of <strong>automation</strong>.</p><h4><strong>Design sprint</strong></h4><p>A UX/UI driven five-day process that helps solve big challenges sort out goals, validate ideas, and build a product prototype. Design Sprints are useful when looking to add new features or when trying to select the best course of action out of a large pool of possibilities. By bringing everybody in the same room (designers, developers, business owners, and stakeholders), a design sprint bypasses never-ending cycles of presuppositions and hints to a solution that can then be tested by real users for valuable feedback. It’s a hands-on approach that requires all people on deck for a smooth sailing experience.</p><h4><strong>Frontend</strong></h4><p>The part of a software product that is visible to users. If we previously compared the ‘backend’ to the kitchen of a restaurant, the ‘frontend’ is the dining area itself, alongside the food, of course. The frontend usually includes all the specific features a user interacts with, which is why it is defined as “client-facing.” Examples of programming languages used for frontend development are JavaScript, HTML, CSS.</p><h4><strong>Framework</strong></h4><p>A set of components/tools meant to ease development and increase product complexity by speeding up the work of developers through compressing detailed info into generic packages. A framework can be seen as the equivalent of a bread or coffee machine, meant to ease up an otherwise laborious baking/brewing process. Or think about frameworks as being a toolbox with commonly needed tools that can help one work faster (a nail gun can secure a nail more quickly than a hammer). Frameworks are created for each programming language. For example, the most popular frameworks are Angular, React, Vue.js and Express.js for JavaScript, Ruby on Rails for Ruby, Django for Python, Laravel for PHP and Spring for Java.</p><h4><strong>Middleware</strong></h4><p>The hidden software layer that acts like the glue between the frontend and the backend of an app, making new features possible. Used for various purposes (develop new apps, optimize older ones, integrate, help apps communicate with each other, automate), it increases efficiency and reduces costs, but adds complexity since it brings an extra layer. The middleware makes it possible for old systems to support new applications without rebuilding the system from scratch or modifying an extremely complicated one.</p><h4><strong>Scrum</strong></h4><p>An Agile software development methodology based on sprints, transparency, communication, iteration, and accountability; Scrum encourages teams to adapt based on client feedback rather than predict and helps members focus on specific tasks before reassessing the next steps.</p><h4><strong>Tech stack</strong></h4><p>A collection of all programming languages, technology services, frameworks and tools meant to create and run a single software application. The tech stack of a software product is highly important, because it directly impacts its performance and influences its cost and scalability. You can compare the <strong>tech stack </strong>of a software product with the modular blocks from an IKEA storage furniture piece — even if they are from different materials, they work exceptionally well together, while also allowing other pieces to be added in the future.</p><h3><strong>Tech jargon good-to-know during product development</strong></h3><h4><strong>Application Programming Interface (API)</strong></h4><p>An API is a set of actions and commands that enable users (i.e., developers) to send requests to suppliers (i.e.apps, servers, etc.) without hassle. Let’s say you’re at a bank with several counters. You need to perform a simple task, such as transferring money from one account to another. To do this, you simply go to the transfer counter and, without having to know all the intricacies of what it actually means to transfer money, you ask the teller to do it for you. Similarly, APIs help clients perform complex actions through simple commands. APIs are usually very specialized for particular tasks, in the same way, the counters in a bank can be reserved for specific operations (open a new account, exchange money, transfer money, etc.)</p><h4><strong>Branch</strong></h4><p>A copy of the existing codelines that enables developers to work in parallel on different tasks/features. Whenever developers need to work on a new feature, but don’t want to mix their existing code with the one they’re currently building, they create a new <strong><em>branch</em></strong> on which they <strong><em>branch out</em></strong><em> </em>new code. Once the code is feature-perfect, they <strong><em>merge</em></strong> it with the main one.<strong> </strong>If an existing software product has several new features in plan, developers will need to lay out a coherent <strong><em>branching strategy.</em></strong></p><h4><strong>Cache</strong></h4><p>A component within a software product that stores data to present it immediately the next time when it is needed. Let’s say you’re a realtor agent who’s always asked by clients what’s the surface area of certain houses. Now, you could go ahead and take measures every time the question comes up, or you could simply note the info down and check your agenda to answer.</p><h4><strong>Code review</strong></h4><p>The act of reviewing another’s code to spot errors, come up with fresh approaches and keep everybody on the team up to speed with the latest work. For a <strong>code review</strong> to be by the book, there must be at least one reviewer who hasn’t worked on writing the code. The work of a code reviewer can be compared to that of an editor, who reads a finished article to polish and refine it.</p><h4><strong>Commit</strong></h4><p>The <strong>commit</strong> action resembles saving changes in a document on Google Drive or Dropbox, making these available to everybody. Practically, to <strong>commit</strong> is to add a new piece of code to the central storage location (the repository that can be accessed by the entire team of developers who work on a product). To <strong>commit code</strong>, developers use version control software like Git, Mercurial, or Subversion, which enables them to keep all versions of code in case they want to revert to a previous state.</p><h4><strong>Deploy</strong></h4><p>The action of making a piece of code or a software available for use, whether it’s for testing purposes or for the end-user specifically. Think about the software product as being a cake. Once the bakers have the perfect recipe and mix all the ingredients, they assemble aka ‘deploy’ the final product. Now, the cake can simply be part of a tasting session for a couple looking for the perfect wedding cake, or it can fulfill its final goal of being served as the sweet ending of a great party.</p><h4><strong>End-to-end testing (E2E)</strong></h4><p>The process of testing the flow of an application from start to end, by simulating real user scenarios. You can think of E2E testing as a theatre play rehearsal that aims to get feedback from a few hand-picked, experienced spectators. In opposition, unit testing takes small units of code and verifies these step by step. Similar to an actor rehearsing their lines at home.</p><h4><strong>Environment</strong></h4><p>The collection of software and hardware tools needed to run an application. Environments can be of different types, according to their scope:</p><ul><li><strong>local environment </strong>is the environment in which an individual developer works on and implements new code;</li><li><strong>development environment </strong>is the eco-system that can be accessed by all the developers working on a project;</li><li><strong>staging environment </strong>is the environment in which the code is tested and replicates the final user-experience;</li><li><strong>production environment </strong>is the final setting that delivers the software product to the end-user.</li></ul><h4><strong>GitHub</strong></h4><p>Cloud-based service that helps developers store and manage code and keeps track of various code versions that are work-in-progress. You can compare it with an offline dossier where you save all drafts related to a single project.</p><h4><strong>Refactoring</strong></h4><p>The process of rewriting existing code with the purpose of improving its clarity, flexibility or scalability. It’s similar to reorganizing your books to find the titles you’re looking for faster. For example, maybe you had your books sorted by their publishing house, and now you decide that you’d benefit more from having them alphabetically ordered according to their author.</p><h4><strong>Release</strong></h4><p>The end goal all development teams work towards. A release is the distribution of the software product. A release is usually a public distribution, but it can also be private. Each time a product gets an update that needs to reach a larger audience, a release is required. The release is comparable to the shipping of a physical product to an end-consumer.</p><h4><strong>Test-driven development (TDD)</strong></h4><p>An Agile software development technique that focuses on writing automated tests first and implementing code after. In TDD, developers first write the automated test and only after move on to writing enough code to pass that test. They can continue to perfect the code that passed the test until they are completely satisfied with its form. Since the tests are already written, there’s no risk of writing faulty code lines. TDD works as a cyclical process and focuses on iterations.</p><h3><strong>Curious about other tech jargon?</strong></h3><h4><strong>Ask away. We sure have an analogy!</strong></h4><p>The above terms and expressions only scratch the surface of tech jargon, but consider them the essential tool kit to dive into your software project. If you’re curious about other terms, let us know in the comments below, and we’ll devise some fun way of explaining them. It’s what we do best, especially after a shot of [e-spres-oh].</p><p><em>If you want to keep up with our mischievous ways of coding and doing fun things with great energy, subscribe to </em><a href="https://teabreak.e-spres-oh.com/"><em>Tea Break</em></a><em> (our blog right here on Medium), stay up-to-date with our </em><a href="https://www.linkedin.com/company/2820676"><em>LinkedIn</em></a><em>, like our </em><a href="https://www.facebook.com/esoh.tech/"><em>Facebook page</em></a><em>, talk to us on </em><a href="https://twitter.com/e_spres_oh"><em>Twitter</em></a><em> or follow us on </em><a href="https://www.instagram.com/e_spres_oh/"><em>Instagram</em></a><em> (but not in a creepy manner).</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=64583c042aaf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tea-break-by-e-spres-oh/decoding-the-language-of-great-software-products-a-tech-dictionary-for-businesses-64583c042aaf">Decoding the language of great software products: A tech dictionary for businesses</a> was originally published in <a href="https://medium.com/tea-break-by-e-spres-oh">Tea Break by [e-spres-oh]</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Surpassing cognitive biases in business: How to recognize the most common pitfalls and build…]]></title>
            <link>https://medium.com/tea-break-by-e-spres-oh/surpassing-cognitive-biases-in-business-how-to-recognize-the-most-common-pitfalls-and-build-a57cfaa3ab1c?source=rss-d61e3d499379------2</link>
            <guid isPermaLink="false">https://medium.com/p/a57cfaa3ab1c</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[business-mindset]]></category>
            <category><![CDATA[insights]]></category>
            <dc:creator><![CDATA[The [e-spres-oh] Team]]></dc:creator>
            <pubDate>Wed, 29 Jul 2020 09:53:20 GMT</pubDate>
            <atom:updated>2020-07-29T12:03:17.040Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Surpassing cognitive biases in business: How to recognize the most common pitfalls and build stronger products</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tlHQiaPLkvkEORM-hpAGHA.jpeg" /></figure><p>When embarking on the development of a software product for your business, on-point decision-making is critical. Setting the right course for your product, pinpointing the needs it answers on the market, thinking about the target it will serve, and setting clear objectives are all crucial to its success. Of course, it takes two to software-tango, and your development team should support you in defining all business and software aspects. However, you’re the one setting the tone, and for that, you need a clear, unbiased vision.</p><p>The most successful leaders base their decisions on a mix of research, experience, deliberate reasoning, and instincts. Still, countless studies have shown that cognitive biases are <a href="https://www.theatlantic.com/magazine/archive/2018/09/cognitive-bias/565775/">hardwired into the human brain</a>. Thus, even <a href="https://hbr.org/2015/05/outsmart-your-own-biases">the most seasoned business individuals</a> sometimes get their decisions derailed by these cognitive biases, especially in high-stress, high-fatigue situations. The risk is even higher for those who think they are immune. The antidote? Recognize that you are a business-human too and learn to bypass those faulty judgments and predictions.</p><h3><strong>What are cognitive biases?</strong></h3><p>The public unmasking of cognitive biases started in the 70s, when psychologists Amos Tversky and Daniel Kahneman tackled prejudices from an economic perspective, <a href="https://www.ft.com/content/9d7d31a4-aea8-11e3-aaa6-00144feab7de">paving the way to behavioral economics</a>. Through several experiments, the two social scientists surfaced more than 20 breakdowns in rationality. Their findings were so compelling that the two were awarded the Nobel Prize in Economics in 2002, although Tversky didn’t live to enjoy the recognition. Daniel Kahneman went on to write the global bestseller <a href="https://www.theguardian.com/science/2014/feb/16/daniel-kahneman-thinking-fast-and-slow-tributes"><em>Thinking, Fast and slow</em></a><em> </em>in which he summarized their findings and dwelt further with the most common pitfalls of human thinking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lOB4Xw3UJhf6A7ZHIFaOXg.jpeg" /></figure><p>Since the 70s, the field has advanced tremendously. Today, it’s a scientifically respected fact that cognitive biases are fallacies and systematic errors that override decision making. What is even more unfortunate is that these biases are inherently human and happen at an unconscious level. In business and software developments, these biases can completely shift the course of products; that’s why we need to stop, pause, and think outside the bias-box.</p><p>While Daniel Kahneman remains slightly skeptical about our abilities to bypass this hindsight in reason, other respected scientists, such as psychology professor Richard E. Nisbett, are outlining fresh approaches that spark a light at the end of the business tunnel. Even Daniel Kahneman says that:</p><blockquote>“Others can perceive our errors more readily than we can.”</blockquote><p>And we believe this is precisely the point in having a software development team that is ready to communicate with you transparently.</p><h3><strong>Common biases in business and how to avoid them</strong></h3><h4><strong>Confirmation Bias</strong></h4><p>Considered to be one of the most pervasive and dangerous cognitive biases, the confirmation bias has business leaders looking for evidence or research that backs-up what they already believe or think to be true. In this context, more weight is given to ideas that support their initial hypothesis, and counter-thought is discounted or even ignored.</p><p>While the bias can appear in all life’s spheres (from daily choices to political decisions), in business it can hinder the success of a future product. For example, in case you want to build a software product and you approach a development team with a set of pre-established ideas, you might dismiss any opinion that diverts from your initial concept.</p><p>One of the easiest (but not simplest!) ways to bypass this bias is by partnering up with a software development team you trust and weigh their opinions equally to yours. Conducting a <a href="https://teabreak.e-spres-oh.com/what-to-expect-from-the-discovery-phase-setting-the-course-for-a-successful-product-1b8e30483902">Discovery Phase</a> can help clarify the picture. And, remember, if research results bet against your initial vision, maybe there’s something to reconsider.</p><h4><strong>Optimism Bias</strong></h4><p>Broadly speaking, the <strong><em>optimism bias</em></strong> is the tendency to overestimate the probability of positive outcomes and underestimate the likelihood of adverse events. While “optimism” is viewed as a highly desirable lens in our society, relying too heavily on “the bright side” can harm future projections. In business, one of the manifestations of the <strong><em>optimism bias</em></strong> is the <strong><em>planning fallacy</em></strong>, in which business individuals focus more on the benefits of a product, and underestimate costs and deadlines.</p><p>It’s easy to get enthused by challenging projects, and software products make no exception. But if you want your business to leverage real benefits from developing such a product, you must plan accordingly and realistically. A “yes, we can!” attitude defines successful business people, but only if a strong root balances it in reality. Daniel Kahneman proposes teams to imagine a project that has gone awry and write a couple of paragraphs as to why and how it happened, to help members think ahead.</p><p>From a software product stand-point, A <a href="https://teabreak.e-spres-oh.com/product-engineering-bridging-the-gap-between-engineering-and-products-3a5087923e1a">Product Engineer</a> can help to balance the business perspective with the development goals and fine-tune estimates always to hit the mark. After all, a positive outlook on a project should mean the willingness to find better solutions to problems instead of ignoring potential mismatches.</p><h4><strong>Narrow framing</strong></h4><p>Narrow framing is a typical case of “didn’t see the forest for the trees.” In essence, tight framing blinds business people into making decisions based solely on a given context and overlook the bigger picture. However, no matter how attractive a particular state of affairs might seem, there are always benefits in taking a step back.</p><p>In the case of product development, if you focus your attention only on specific details, there’s a big risk of ending up with a quality-skewed product. To build reliable products, businesses and development teams must zoom out and create expectations, goals, and requirements with a full-picture. Business goals, development goals, and UX/UI design goals are not separate endeavors. In fact, these all converge to the best outcome of a software product. A <a href="https://teabreak.e-spres-oh.com/a-remote-design-sprint-story-efd7d700eb">Design Sprint</a> can help everybody gain a better understanding of the path ahead and lead to a functional prototype.</p><h4><strong>Loss Aversion</strong></h4><p>According to Daniel Kahneman, “Losses loom larger than gains. And we have a pretty good idea of how much they loom larger than gains, and it’s by about 2-to-1”. That means that people prefer to avoid losing a specific thing/amount to winning that same thing/amount. While this approach might seem the right one, it can lead to business stagnation. Because without taking some calculated risks, there can be no innovation.</p><p>This particular bias is closely connected to reputational costs. Usually, individuals build their reputation on their successes and consider that any loss can be detrimental to their right image. However, it’s no secret that some of the most successful businesses in the world today were built on failures. In fact, failures can be good for business, as long as the losses get transformed into lessons learned. We’re not advocating, in any way, for taking uncalculated risks. Instead, we’re encouraging clients to courageously discover new grounds when the winnings are indeed worth the risks. In this case, multi-functional teams can help you tackle risks from both a business and a development perspective, bypassing loss aversion, and courageously aiming for innovative software products.</p><h3><strong>Bye, bye, business bias!</strong></h3><p>The way we process and analyze business information is fundamental in decision making and product development. Although cognitive biases are deeply wired in the way our brains evolved, there are specific ways in which we can bypass them and steer to more rational judgments in business. To say that any individual is free from bias is to say they have eluded human evolution and, well, that’s not possible.</p><p>It takes a conscious effort to recognize your own biases and reach out to your extended product development team to surpass them. We’ve only scratched the surface of cognitive biases, as the list <a href="https://en.wikipedia.org/wiki/List_of_cognitive_biases">extends to almost 200</a>. Recognize any? Let us know in the comments below.</p><p><em>If you want to keep up with our mischievous ways of coding and doing fun things with great energy, subscribe to </em><a href="https://teabreak.e-spres-oh.com/"><em>Tea Break</em></a><em> (our blog right here on Medium), stay up-to-date with our </em><a href="https://www.linkedin.com/company/2820676"><em>LinkedIn</em></a><em>, like our </em><a href="https://www.facebook.com/esoh.tech/"><em>Facebook page</em></a><em>, talk to us on </em><a href="https://twitter.com/e_spres_oh"><em>Twitter</em></a><em> or follow us on </em><a href="https://www.instagram.com/e_spres_oh/"><em>Instagram</em></a><em> (but not in a creepy manner).</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a57cfaa3ab1c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tea-break-by-e-spres-oh/surpassing-cognitive-biases-in-business-how-to-recognize-the-most-common-pitfalls-and-build-a57cfaa3ab1c">Surpassing cognitive biases in business: How to recognize the most common pitfalls and build…</a> was originally published in <a href="https://medium.com/tea-break-by-e-spres-oh">Tea Break by [e-spres-oh]</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What to Expect from the Discovery Phase: Setting the Course for a Successful Product]]></title>
            <link>https://medium.com/tea-break-by-e-spres-oh/what-to-expect-from-the-discovery-phase-setting-the-course-for-a-successful-product-1b8e30483902?source=rss-d61e3d499379------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b8e30483902</guid>
            <category><![CDATA[insights]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[discovery-phase]]></category>
            <category><![CDATA[product-mindset]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[The [e-spres-oh] Team]]></dc:creator>
            <pubDate>Thu, 25 Jun 2020 08:06:59 GMT</pubDate>
            <atom:updated>2020-06-25T08:13:32.945Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Business vector created by pikisuperstar — www.freepik.com" src="https://cdn-images-1.medium.com/max/1024/1*nhalBOq_XjSL_HTgm0dKXA.jpeg" /></figure><p>Many businesses believe they can gracefully leap from an initial idea to a grand software product, often to find themselves falling into an endless maze of changing scopes. Skipping steps — even if might be the faster alternative — ends up being a time consuming, costly affair that can leave stakeholders, development teams, and everyone involved on the verge of frustration.</p><p>According to <a href="https://www.mckinsey.com/~/media/McKinsey/dotcom/client_service/BTO/PDF/MOBT_27_Delivering_large-scale_IT_projects_on_time_budget_and_value.ashx">a study conducted by famous analytics firm McKinsey</a>, the four leading issues that lead to project failure are <em>unclear objectives, shifting requirements, unaligned teams, </em>and<em> unrealistic timings combined with reactive planning</em>, all of which can be elegantly avoided by performing a <strong>Discovery Phase</strong>.</p><p>Even if it might seem counterintuitive, slowing down at the beginning will result in getting things done faster in the long run — especially if the initial product idea is vaguely defined. A Discovery Phase helps businesses <strong>validate and clearly outline their idea</strong>, giving them <strong>all the missing pieces </strong>needed to<strong> kick-off development</strong> for a <strong>Minimum Viable Product (MVP)</strong>. As a result, the development will march on faster, expectations will be met (because they were set) and money will be saved. So let’s discover together what a Discovery Phase is and how it can save your software product from failing before it even had a chance to succeed.</p><h3><strong>What Is the Discovery Phase</strong></h3><p>As its name fairly suggests, the <strong>Discovery Phase</strong> is all about <em>uncovering</em>:</p><ul><li>the <strong>problem</strong> you are trying to solve;</li><li>he <strong>scope</strong> of the project;</li><li>the end <strong>goals</strong>;</li><li>the <strong>user journey</strong>;</li><li>the current state of the niche <strong>market</strong>.</li></ul><p>It’s an <strong>exploratory phase </strong>in which <strong>research</strong> will give businesses, UI/UX designers, and development teams the leverage needed to step into the development phase knowing exactly what they are doing and what their limitations are.</p><p>Depending on the complexity of the product idea, a Discovery Phase can take anywhere from <strong>two weeks to two months</strong>, time in which business analysts, product engineers, UX/UI designers, and, in particular cases, solution architects dig into every imaginable piece of info available.</p><p>This very fruitious step wraps up with a <strong>set of deliverables</strong> that <strong>open the road towards the development of a first release of the software product</strong>. These deliverables are:</p><ul><li>a comprehensive document called Software Requirements Specifications (SRS);</li><li>an interactive prototype;</li><li>a roadmap aka a kick-off plan;</li><li>a budget (time &amp; cost) estimation;</li><li>team staffing requirements.</li></ul><h3><strong>How a Discovery Phase Unfolds</strong></h3><p>Since the Discovery Phase marks the first step in the software product development journey, it <strong>starts</strong> <strong>big</strong>, with <strong>high-level specifications</strong> regarding the <strong>end-goals</strong> and the <strong>core functionalities</strong>. To define these points, the Discovery Team and the stakeholders get together<strong> </strong>to <strong>draft the initial direction</strong>.</p><p>As soon as everybody has the big picture, it’s time to break things down through <strong>research</strong>. The Discovery Team, composed of business analysts, product engineers and UI/UX designers, get down to work and expand their findings through a <strong>Business Model Canvas</strong>, <strong>user flow diagrams, </strong>and <strong>a market and competitive landscape analysis</strong>. The team will<strong> leave no digital or business stone unturned.</strong> In fact, they will go as deep into the research as necessary <strong>until they gather the level of specifications needed for a successful MVP development.</strong></p><p>At the conclusion, the stakeholders will receive a<strong> document </strong>that clearly<strong> outlines the core functionalities </strong>of the product, the<strong> business goals, </strong>the<strong> user journeys, </strong>and the <strong>competition, </strong>with a full understanding of<strong> what a successful outcome means</strong>. Plus, they’ll go through an <strong>interactive design prototype</strong> rooted in research, not gut feeling, ready to be tested with real users for feedback that will be ultra-valuable in the development phase. What’s more, the <strong>SRS document </strong>will offer a tangible idea of <strong>how the development team should look</strong> and what <strong>technologies</strong> would work best <strong>for developing the product.</strong></p><blockquote><em>“The Discovery Phase is a good place to build trust and establish common ground. Sometimes a business can use these Software Requirements Specifications and move into the Development Phase with a different software company than the one that conducted the Discovery Phase. As a best practice, who discovers together, develops together.”</em></blockquote><blockquote><em>Daniel Markovits, Director of Engineering at [e-spres-oh]</em></blockquote><h3><strong>Why Do It?</strong></h3><p>The Discovery Phase <strong>helps businesses fully clarify their goals</strong> and <strong>objectives</strong> based on market research. As a result, it <strong>minimizes risks, saves time, </strong>and<strong> reduces costs.</strong> The documents delivered at the end of the Discovery Phase have straightforward directions that will help<strong> align all stakeholders involved</strong>.</p><p>With clear directions and <strong>quantifiable goals </strong>that are<strong> guaranteed not to change due to novel information</strong>, the path is set towards <strong>frustration-free development.</strong> Stakeholders, designers and developers will get along easier, better and have <strong>more efficient collaboration</strong>. Everyone involved will<strong> know what to do </strong>and<strong> in just how much time</strong>.</p><p>The Discovery Phase is generally an <strong>opportunity opener</strong>, enabling teams to <strong>find better solutions </strong>that might have not been so obvious from the get-go. By getting to understand the product better, its opportunities and its limitations, new horizonts are visible, ones that might have not even seemed initially possible.</p><p>This step, considered superfluous by many, provides the valuable context that will help a product thrive in the real-world. Through user-research, functionalities can be better defined as a key to a successful outcome. And, speaking about the outcome, a Discovery Phase encourages stakeholders to focus on objectives and goals and what specific deliverables can get them to these. Which is, in the end, the purpose of it all.</p><h3><strong>First an MVP, Then the Entire World</strong></h3><p>It’s easy to get carried away by the desire to get things done right away. But research isn’t a nice-to-have item. <strong>Research is a stepping stone for strong products</strong>. Thus, the Discovery Phase should be the basis of all first-releases of any software product.</p><p>It’s been long proven that the <em>waterfall</em> model has major flaws and a high potential to flood teams with frustrations. By developing a <strong>Minimum Viable Product (MVP)</strong>, a business can make sure their product has value and then continue to add new extra functionalities gradually. An <strong>MVP</strong> is also a great way to help stakeholders attract investors and <strong>gather funds</strong> for further development.</p><p>All things considered, digital capabilities are always changing. This <strong>step-by-step approach</strong> ensures a business will always be in-tune with the times and with its stakeholders. As they say: sometimes you need to slow down to speed up.</p><p>From us, to you, all the <strong>great energy</strong> needed for your <strong>Discovery Phase</strong>.</p><p><em>If you want to keep up with our mischievous ways of coding and doing fun things with great energy, subscribe to </em><a href="https://teabreak.e-spres-oh.com/"><em>Tea Break</em></a><em> (our blog right here on Medium), stay up-to-date with our </em><a href="https://www.linkedin.com/company/2820676"><em>LinkedIn</em></a><em>, like our </em><a href="https://www.facebook.com/esoh.tech/"><em>Facebook page</em></a><em>, talk to us on </em><a href="https://twitter.com/e_spres_oh"><em>Twitter</em></a><em> or follow us on </em><a href="https://www.instagram.com/e_spres_oh/"><em>Instagram</em></a><em> (but not in a creepy manner).</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b8e30483902" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tea-break-by-e-spres-oh/what-to-expect-from-the-discovery-phase-setting-the-course-for-a-successful-product-1b8e30483902">What to Expect from the Discovery Phase: Setting the Course for a Successful Product</a> was originally published in <a href="https://medium.com/tea-break-by-e-spres-oh">Tea Break by [e-spres-oh]</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Engineering: Bridging the Gap Between Engineering and Products]]></title>
            <link>https://medium.com/tea-break-by-e-spres-oh/product-engineering-bridging-the-gap-between-engineering-and-products-3a5087923e1a?source=rss-d61e3d499379------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a5087923e1a</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[insights]]></category>
            <category><![CDATA[product-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[The [e-spres-oh] Team]]></dc:creator>
            <pubDate>Thu, 21 May 2020 10:27:26 GMT</pubDate>
            <atom:updated>2020-05-21T10:27:26.624Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vw-zYqvKJuglk8hPUjYg1A.jpeg" /></figure><p>What’s the recipe for a <strong>successful software development project</strong>? This is the million-dollar riddle every entrepreneur, CEO, manager or anybody who has an interest in software tries to solve — especially when an endeavour in this direction starts to crumble.</p><p>The solution is simple yet complex. Generally, to build a robust and viable software product, you need to make sure you are building the “right product”, that it’s “managed right” and, of course, it’s “done right”. For every aspect to fall into place, the team accountable for the product needs to bring together diverse roles and cover a wide range of activities — from planning to outlining specifications, monitoring the progress, coding, technical architecture, UX design and many more.</p><p>Defining such a multi-functional team and determining the degree of involvement of each member proportionally to the objectives of the project is highly challenging. This is when the mindset gap between <strong><em>product</em></strong> and <strong><em>engineering</em></strong> becomes apparent. And the divide will only grow as the project moves into later stages, risking little to no progress.</p><p>Here’s where the <strong>Product Engineer </strong>steps in, <strong>resolving the gap</strong> <strong>efficiently and effectively</strong> and putting a<strong> twist on the classical approach</strong> of cross-functional teams.</p><h3>Product vs. Engineering Mindset</h3><p>The literature* on teamwork and efficiency clearly shows that mindsets and attitudes play a significant role in accomplishing tasks. When it comes to software development projects, understanding and solving <strong><em>the gap between the product and engineering mindset</em></strong> is the first step towards success. So, how do the product/engineering perspectives differ?</p><p><strong>The product mindset </strong>is all about understanding the product from a <strong>business perspective</strong> and aims to:</p><ul><li>Fully grasp the socio-economic context and the problem the product tries to solve;</li><li>Gather as much knowledge as possible about the industry in which the product will be introduced;</li><li>Think about the solution in terms of relevancy to the customers and viability on the market.</li></ul><p><strong>The engineering mindset </strong>concentrates on building the product from a <strong>technical perspective </strong>to:</p><ul><li>Make accurate technical forecasts based on precise technology audits;</li><li>Build a strong, viable technology architecture for the product;</li><li>Ensure the necessary coding skills to implement the needed specifications are in place;</li><li>Deliver high technical performance.</li></ul><p>Solving the gap between the two starts with <strong>understanding both perspective</strong>s. After all, only by making sure that both aspects are met will a software project be successful. So, <strong>negotiating solutions</strong> and <strong>finding common ground</strong> between the two is not only advisable, but mandatory. Of course, every project is different and assessing the importance of each perspective in the context of the product’s objectives will give a clearer view on how the team working on it should look, what set of skills the members will need and in what degree.</p><h3>The Skills That Bridge the Gap</h3><p>To bridge the perspective gap, a Product Engineer brings to the table a <strong>wide range of skills</strong> that <strong>account for a variety of classical roles</strong> such as Product Manager, Team Lead, Scrum Master, Product Owner and Product Owner Proxy, Software Engineer and Product Architect, to name the most common. Think of the Product Engineer as a <strong>“Jack of all trades”</strong> that has <strong>basic knowledge skills</strong> in all these domains and <strong>in-depth expertise</strong> in one or two, according to his/her background.</p><p>The Product Engineer, no matter his/her previous specialization, brings to the table the following skills in order to merge the product and engineering mindsets:</p><ul><li>Knows how to <strong>easily communicate and wor</strong>k with Designers, Product Managers, Data Scientists, Marketing Managers or Business Developers and <strong>disseminate information across-departments </strong>to deliver a good product from all perspectives;</li><li>Has <strong>strong engineering know-how</strong> and can merge it with a <strong>pragmatic focus on ROI</strong> to deliver short and long-term planning strategies;</li><li>Is aware of and<strong> fully understands technical constraints</strong>, resources availability, opportunities and limitations and can leverage them all to the project’s advantage;</li><li>Can <strong>manage all parties’ expectations </strong>and is able to <strong>prioritize</strong>;</li><li><strong>Internalizes the business’ mission and needs</strong> and<strong> </strong>translates them into clear, well-rounded <strong>technical specifications;</strong></li><li>Plays a leading role in the Product Definition and Discovery Phase;</li><li>Is capable of <strong>streamlining communication</strong> in order to improve <strong>team performance </strong>overall.</li></ul><h3>Engineering the Product One Step Further</h3><p>In addition to being the natural binder that bridges the gap between product and engineering through a set of skills from both worlds, the <strong>Product Engineer</strong> also acts as<strong> a motivational and inspirational agent.</strong></p><p>It’s been proven that solving dry tasks, void from their end goal, is detrimental to innovation. People are not inspired or motivated by solving issues in a vacuum. In order for team members <strong>to be enthused by a project and innovate</strong>, they need to <strong>empathise with the problem</strong> and <strong>internalize the mission</strong>. It’s the same for Software Engineers and UX/UI Designers. To spark the innovation magic, they need to understand the role of the product in the real environment.</p><p>A Product Engineer, through his/her role of disseminating info cross-departments, can help <strong>paint the bigger picture</strong>, provide <strong>transparency</strong> and point out<strong> purpose and meaning</strong>. By passing on knowledge on the broad view, a Product Engineer acts as an <strong>informal leader</strong> and conducts self-organizing teams to tackle technical challenges from a<strong> fresh perspective</strong> with <strong>new-found understanding</strong>. A Product Engineer can boost morale through providing a birds-eye view perspective of the entire software development project, in context.</p><h3>Benefits of Having a Product Engineer</h3><p>As software products become more and more complex, setting yourself up for success from the very beginning is more important than ever. It’s also more difficult. Having a Product Engineer on your software development team can bridge the gap between product and engineering by delivering a perspective that advocates for both business and technology. All in all, a Product Engineer will help to:</p><ul><li><strong>Tackle the project in the most efficient way. </strong>Since the Product Engineer can account for multiple classical roles, it becomes easier to balance responsibilities at lower costs and in a timely manner.</li><li><strong>Reduce overhead with management and specification definition. </strong>A Product Engineer will know how to translate business needs into technical product specification and thus reduce the back and forth between the business and tech departments.</li><li><strong>Minimize risk.</strong> A Product Engineer makes sure the implementation team understands the business contexts and thus builds the right features and product.</li><li><strong>Rapidly and efficiently adapt to change</strong>. During software development projects, change often involves the need to redistribute the workload between various skill sets. A Product Engineer can quickly address this need by tweaking the degree of involvement for each member or by adding or removing roles as necessary.</li></ul><h3>Bridge the Gap to a Successful Software Product</h3><p>As we’ve pointed out at the beginning, the recipe for a <strong>successful software development project </strong>is simple, yet sophisticated. In this case, a Product Engineer can be the binding agent that stirs it in the right direction and keeps it on track. All, of course, with the help of a strong development team that has a ton of great energy.</p><p>*<strong>The Product Mindset:</strong> <strong><em>Succeed in the Digital Economy by Changing the Way Your Organization Thinks</em></strong> by David H. DeWolf and Jessica S. Hall</p><p><em>If you want to keep up with our mischievous ways of coding and doing fun things with great energy, subscribe to </em><a href="https://teabreak.e-spres-oh.com/"><em>Tea Break</em></a><em> (our blog right here on Medium), stay up-to-date with our </em><a href="https://www.linkedin.com/company/2820676"><em>LinkedIn</em></a><em>, like our </em><a href="https://www.facebook.com/esoh.tech/"><em>Facebook page</em></a><em>, talk to us on </em><a href="https://twitter.com/e_spres_oh"><em>Twitter</em></a><em> or follow us on </em><a href="https://www.instagram.com/e_spres_oh/"><em>Instagram</em></a><em> (but not in a creepy manner).</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a5087923e1a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tea-break-by-e-spres-oh/product-engineering-bridging-the-gap-between-engineering-and-products-3a5087923e1a">Product Engineering: Bridging the Gap Between Engineering and Products</a> was originally published in <a href="https://medium.com/tea-break-by-e-spres-oh">Tea Break by [e-spres-oh]</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creative Tips for WFH (Working From Home) — With Extra Gimmicks for Great Energy]]></title>
            <link>https://medium.com/tea-break-by-e-spres-oh/creative-tips-for-wfh-working-from-home-with-extra-gimmicks-for-great-energy-995122b6e2a0?source=rss-d61e3d499379------2</link>
            <guid isPermaLink="false">https://medium.com/p/995122b6e2a0</guid>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[insights]]></category>
            <category><![CDATA[wfh]]></category>
            <dc:creator><![CDATA[The [e-spres-oh] Team]]></dc:creator>
            <pubDate>Wed, 22 Apr 2020 07:35:05 GMT</pubDate>
            <atom:updated>2020-04-22T07:40:44.504Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Creative Tips for WFH (Working From Home) — </strong>With Extra Gimmicks for Great Energy</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T7LGmwN8tsPhOTPjzVluVQ.jpeg" /></figure><p>Working from home can be a treat, but it can also be bittersweet, especially now, when <strong><em>everything</em></strong> has to happen <strong><em>from home</em></strong>. With outdoors out of the question, indoor space needs to accommodate the answer to all our needs: business and pleasure alike. No pressure, though, right?</p><p>Staying productive in WFH-mode means achieving a fragile balance between work, rest, play and a dozen responsibilities. While we’ve been practicing remote work ever since we can remember, working from home in quarantine-times poses a completely different challenge.</p><p>Luckily, we bravely faced it and came out victorious. Now, four of our developers and designers are ready to share their behind-the-home-scene tips and tricks for a more efficient, productive and, dare we say, even fun WFH scenario.</p><h3><a href="https://medium.com/u/a7f61cb18b5"><strong>Robert Todea</strong></a><strong>, Software Developer, Father of Two</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uowKVTNuKakXQf2qeKxVJQ.jpeg" /><figcaption>Juggling work and play</figcaption></figure><p><strong>Video-call colleagues: </strong>I schedule daily short calls to see what my teammates have been doing on and off projects. I prefer video-calls on Hangouts to audio-calls because we are social creatures and like to have a face to speak to. I keep my camera on even if I sometimes have to re-purpose the bedroom or the bathroom as my meeting-room. My teammates understand this is not my usual time of the year.</p><p><strong>Schedule time for ‘deep work’: </strong>Take advantage of the time when your kids are asleep (early in the morning or late at night) to tackle the hardest and most thought-provoking tasks. Disconnecting from all communication forms during this time helps. Get in your work-bubble and get to it.</p><p><strong>Expect the unexpected:</strong> Things will get out of control or kids will drop by to show you their latest feats (it’s their work and they are proud to share it with you). So accept that you will have to stop what you’re doing and attend to whatever might pop up.</p><p><strong><em>Extra inside-info: </em></strong><em>When you finish work it is better to have some buffer time before playing with the kids. This will help you put a smile on, which is mandatory because kids always pick up when you are sad and amplify it. I use the 7minute iOS app to boost my mind. Then I’m ready to play and prepare the activities for the kids for the following day.</em></p><h3><a href="https://medium.com/u/149da147261d">Alexandra Braslasu</a><strong>, UX/UI Designer, Creative-Routine Lover</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cOAD25F3dsQWyD-LhhnTEw.jpeg" /><figcaption>Keeping it neat</figcaption></figure><p><strong>Routine is your best friend: </strong>Having a schedule and not compromising on it helps me stay hyper-productive and tick off my to-do list. My morning ritual helps get in focus: I wake up, wash my face, brush my teeth, drink my smoothie, sip my coffee and listen to music while watching the Ginkgo Biloba in front of my kitchen window bloom.</p><p><strong>Keep your workspace neaaaaaat: </strong>I designated the desk in my living room as my ‘workspace’. On this desk, I hate keeping things that I don’t need for work. Having a work-only area that’s neatly organized helps me stay in the ‘tunnel’ mindset when I am in the mindset to work, work, work, but also reminds me that I need time for myself.</p><p><strong>Stay motivated by getting inspired: </strong>I pay a lot of attention to what draws my interest and try things that bring me pleasure. Playtime feels like a good time to learn all the little things I have always wanted to learn but never had the time. I started painting and drawing again, reading books about my favorite artists, learning calligraphy and trying to find resources to learn how to braid baskets.</p><p><strong><em>Extra tip: </em></strong><em>When I first started working from home, I used to dress up to motivate myself to get in the work-mindset. Now, after almost 5 years of alternating working from home with working from the office, I don’t need that trick anymore — sitting at my homework desk helps me stay focused.</em></p><h3><a href="https://medium.com/u/fa723eefd634">Ovidiu Bite</a><strong>, Software Developer, Active Video-Conference Participant</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R26bRH2ujFrwrX4_04nIHQ.jpeg" /><figcaption>Give me a cat-break</figcaption></figure><p><strong>Keep work and play separate: </strong>I’ve chosen a particular room as “my office” and I keep it for work only. During breaks, I go to a different room and I avoid using my computer. I either (try to) play with my cat or I…simply stare out the window.</p><p><strong>Follow the 30/70 rule: </strong>I alternate sitting down with standing up. I have an adjustable desk, and I try to mix it up: 30% of the time I sit down and 70% of the time I stand (okay, that’s the maximum percentage for standing, still a novice).</p><p><strong>Step it up: </strong>I bought a stepper (best decision ever!), and I use it even when I’m on video calls. The good part is that I keep active, the bad part is that I lose my breath and talk funny when it’s my turn to speak.</p><p><strong><em>Extra #stayhome tips: </em></strong><em>I heard that having a quarantine hobby helps, so I started to learn to play the guitar. Two weeks ago, I didn’t know how to hold a chord. Now I know…that holding a chord hurts my fingers. A hobby that </em><strong><em>does</em></strong><em> help is keeping in touch with my friends. Every evening, after work, we video call to enjoy some time out, inside. Pro tip: Chat over cold craft beers; paying the extra buck will make you feel like you’re actually out and about.</em></p><h3><a href="https://medium.com/u/5730bfdf50bd"><strong>David Porosnicu</strong></a><strong>, Experienced Remote Developer, Novice Quarantine Dweller</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*injVr2k08_F8ysgDQFnECg.jpeg" /><figcaption>-oh] that first sip of coffee</figcaption></figure><p><strong>But first, coffee: </strong>Before going into work-mode, I enjoy my cup of coffee while doing my morning read. Currently, I’m reading Atomic Habits by James Clear, a pretty cool book I definitely recommend. Then, I pour myself a second cup and off to work…meaning off to the other room.</p><p><strong>Break your tasks in mini-tasks to afford…breaks: </strong>I’ve devised this gimmick to reward myself at the end of each task with a short, pampering break. During my breaks, I usually take lessons on Duolingo or watch a short TV-Series episode. Oh, and I never take my breaks in the same room in which I work.</p><p><strong>Sync with your teammates’ schedules: </strong>I try to respect the “official” working hours to make sure I’m overlapping with my other colleagues’ calendars. This helps me keep the communication stream smooth. Plus, it also gives me a better separation between my work and personal life.</p><p><strong><em>Extra inside-info: </em></strong><em>WFH and Remote Work are two different breeds</em><strong><em>. </em></strong><em>During my remote work adventures around Asia, the biggest downside was finding a stable internet connection. The awesome part was that I had a cool new office daily, with a sea-view. Working from home during this pandemic is entirely different, as I rely mostly on routine and my mom’s excellent cooking.</em></p><p>Have any creative strategies and gimmicks of your own? We’d like to hear them! Share the WFH joy and pass it on.</p><p><em>If you want to keep up with our mischievous ways of coding and doing fun things with great energy, subscribe to </em><a href="https://teabreak.e-spres-oh.com/"><em>Tea Break</em></a><em> (our blog right here on Medium), stay up-to-date with our </em><a href="https://www.linkedin.com/company/2820676"><em>LinkedIn</em></a><em>, like our </em><a href="https://www.facebook.com/esoh.tech/"><em>Facebook page</em></a><em>, talk to us on </em><a href="https://twitter.com/e_spres_oh"><em>Twitter</em></a><em> or follow us on </em><a href="https://www.instagram.com/e_spres_oh/"><em>Instagram</em></a><em> (but not in a creepy manner).</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=995122b6e2a0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tea-break-by-e-spres-oh/creative-tips-for-wfh-working-from-home-with-extra-gimmicks-for-great-energy-995122b6e2a0">Creative Tips for WFH (Working From Home) — With Extra Gimmicks for Great Energy</a> was originally published in <a href="https://medium.com/tea-break-by-e-spres-oh">Tea Break by [e-spres-oh]</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tech Trends That Will Shift your Business to Version 2.0.2.0]]></title>
            <link>https://medium.com/tea-break-by-e-spres-oh/tech-trends-that-will-shift-your-business-to-version-2-0-2-0-17b4be9ab0d4?source=rss-d61e3d499379------2</link>
            <guid isPermaLink="false">https://medium.com/p/17b4be9ab0d4</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[trends]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[The [e-spres-oh] Team]]></dc:creator>
            <pubDate>Wed, 26 Feb 2020 14:04:03 GMT</pubDate>
            <atom:updated>2020-02-26T14:18:15.926Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3u7i3OmPsFamBKhvnPP_sA.png" /></figure><p>On the horizon for this decade, tech trends are emerging to challenge and push businesses forward. Whether you’re running a corporate empire, a medium-sized enterprise, a small business or a one-man show, 2020 is bringing winds of tech change.</p><p>Where some see worry we see opportunities. With that in mind, we’ve selected those digital trends that will affect your business. So wake up Alexa, Siri or Cortana and note these trends down. You’ll need them sooner rather than later.</p><ol><li><strong>Progressive Web Apps (PWAs)</strong></li><li><strong>WebAssembly</strong></li><li><strong>Distributed Cloud Services and Cloud Neutrality</strong></li><li><strong>Low-Code to No-Code Development</strong></li><li><strong>AI and Machine Learning</strong></li></ol><h3><strong>1. PWAs: Become Mobile-Smart</strong></h3><p>PWAs have been called the “the future of the mobile web” and are, in fact, mobile websites that offer a similar experience to that provided by native apps (those apps you can download from app stores). PWAs’ biggest strength is its ability to work simultaneously as a mobile website AND a native app, enabling you to get the best of both worlds. That means you’ll be able to enjoy the reach of a website and the engagement of a native app. Sure, PWAs still have to cover more ground to reach native apps’ capabilities, but with more APIs on the way, their future looks mighty bright.</p><p>In 2020, PWAs will make a difference for businesses that want to smartly value their assets and efficiently manage their resources.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P63vGzsRVXqlZkzj3KbwdQ.png" /></figure><p><strong>Benefits and Key Take-aways:</strong></p><ul><li>Eliminate the extra step of finding and installing an app</li><li>Immersive user experience</li><li>Faster load times (even work offline) and higher user retention</li><li>Increased session lengths and decreased bounce rates</li><li>Less data usage to deliver complex results</li><li>Can work in tandem with native web apps</li><li>Quickly becoming the new standard for mobile web interactions</li></ul><p><strong>Companies That Use PWAs:</strong> Twitter, Financial Times, New York Times, AOL, The Washington Post, The Home Depot, Starbucks, Lancôme</p><h3><strong>2. WebAssembly (WASM): Build More Complex Products For The Web</strong></h3><p><strong>WASM </strong>is<strong> </strong>one of the newest web standards that opens up new possibilities for the web. By using WASM, you’ll be able to compile complex programming languages that, up until now, couldn’t be used for browsers. Thanks to this new technology, you now have the flexibility to use code in any programming language and run it within Firefox, Chrome, Edge, and Safari which all support WebAssembly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OUjtNn5egreEGK6eO9NCUw.png" /></figure><p>For your business, that means your web dev team will be able to deliver higher-performing products, with improved load-time no matter how heavy-coded. We won’t get into the techy details of how (although we’re hardly abstaining from diving deep), but we’ll tell you this: the web just got more competitive!</p><p><strong>Benefits and Key Take-aways:</strong></p><ul><li>Offers more flexibility when choosing a technology for building a product</li><li>Runs code written in multiple languages at native-level speeds across different platforms</li><li>Improves load-time for heavy-code products, such as video games</li><li>Reduces file sizes by using Binary (aka as low-level programming; in contrast, JavaScript is a high-level programming language)</li><li>Has solid safety and security guarantees</li><li>Develops more performant products</li><li>It has applications across the web tech world, including in AI, AR, and VR</li></ul><p><strong>Companies That Use WASM: </strong>Cubbit, Frontend, IHMC, Synfig, OPA, Unity</p><h3><strong>3. Distributed Cloud Services and Cloud Neutrality: Sky-High Impact</strong></h3><p><strong>Cloud neutrality</strong> is a public-interest tech issue we all should be paying close attention to, as it impacts not only the way we do business but the way we interact online. Currently, most of the data center infrastructure in the cloud belongs to a handful (actually less than a handful) of tech giants. These companies have complete power on lease terms and can basically make their own rules. What <a href="https://www.wired.com/story/we-need-to-talk-about-cloud-neutrality/">future cloud neutrality legislation</a> will look like is hard to say, but one thing is for certain: we should start pushing for one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pa3-KfOFlOx1j4Yvzn__IQ.png" /></figure><p>On the other hand, “distributed cloud services” or “hybrid clouds” present a solution to the neutrality conundrum, separating infrastructure power among several providers.</p><p><strong>Benefits and Key Take-aways:</strong></p><ul><li>Eliminates challenges related to data sovereignty</li><li>Offers back-up solutions that are fail-proof by having multiple remote replicas</li><li>Reduces latency</li><li>Greater flexibility and more deployment options</li><li>Lower costs</li><li>More options for optimization when it comes to infrastructure</li><li>Better security</li><li>Higher compliance</li><li>Will highly benefit Internet of Things data processing, VR/AR and gaming</li></ul><p><strong>Companies that Use Cloud Services: </strong>General Electric, eBay, Meals on Wheels, Fitbit</p><h3><strong>4. Low-Code to No-Code Development: Automate The Coding Process</strong></h3><p>The new decade is ushering in new development tools that will deliver complex results with<strong> less code </strong>and less effort. The trends are shifting from meticulous programming languages that require endless lines of code, to high-level ones (Python, anyone?!) or even visually optimized environments that automate the coding process. The ultimate goal is to enable developers to focus on performance and complexity.</p><p>For your business, this means more time spent by developers on improving product performance and capabilities, rather than building basic layers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yVXDmshUBpiu15IP0FmaQQ.png" /></figure><p><strong>Benefits and Key Take-aways:</strong></p><ul><li>Improves efficiency and productivity</li><li>Interactive interfaces with code-autocomplete and other tools that improve development speed</li><li>Opens new possibilities for complexity</li><li>Enables developers to focus on the bigger picture</li><li>Easier to scale and maintain</li></ul><p><strong>Companies that Use Low-Code Development: </strong>Pinterest, Moz Pro, Lonely Planet, Financial Times, Toyota Connected</p><h3><strong>5. AI and Machine Learning: Breaking New Grounds</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gQfeE9tT16A37KK6FUpdcA.png" /></figure><p>AI and Machine Learning (ML) have been the main technological drivers of change for the past few years, but their true impact is yet to be seen in this decade. The applicability of AI and ML spans from business to cybersecurity, finance, employment, and even medicine. In fact, scientists have just recently managed to discover a new <a href="https://www.theguardian.com/society/2020/feb/20/antibiotic-that-kills-drug-resistant-bacteria-discovered-through-ai">extremely powerful antibiotic by using machine learning</a>. Of course, with such great tech power comes great responsibility and the ethical implications of using AI and ML should not be taken lightly.</p><p>For businesses, the ability to run systems that learn and discover on their own (ML) is not only deemed to be more efficient, but highly innovative and revolutionary.</p><p><strong>Benefits and Key Take-aways:</strong></p><ul><li>Real-time business decision-making</li><li>Reduces menial tasks and improves efficiency</li><li>Provides insightful business intelligence</li><li>Helps build smarter workplaces by automating tasks</li><li>Improve customer satisfaction</li><li>Optimizes leads recommendations and increases sales opportunities</li><li>Enhance security and network performance</li><li>Curate content based on a personalized customer approach</li></ul><p><strong>Companies that Use AI and ML: </strong>General Electric, eBay, Meals on Wheels, Fitbit</p><h3><strong>Upgrade to the new decade</strong></h3><p>Truth be told, there’s no shortcut to success, although leveraging emerging technologies could get you where you want to be faster and smarter. Only not by themselves.</p><p>The new decade requires you to be on top of trends, but also to know the depths of your business. Remember our advice to carefully inspect the winds of tech change? Having the right tech partner by your side will help you figure out where to start your upgrade and how exactly to load a new year of successful software products. At [e-spres-oh], we keep our eyes on the future so you can focus on your business.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L8AkA3ioaL-5HGeFCxKkUA.png" /></figure><p><em>If you want to keep up with our mischievous ways of coding and doing fun things with great energy, subscribe to </em><a href="https://teabreak.e-spres-oh.com/"><em>Tea Break</em></a><em> (our blog right here on Medium), stay up-to-date with our </em><a href="https://www.linkedin.com/company/2820676"><em>LinkedIn</em></a><em>, like our </em><a href="https://www.facebook.com/esoh.tech/"><em>Facebook page</em></a><em>, talk to us on </em><a href="https://twitter.com/e_spres_oh"><em>Twitter</em></a><em> or follow us on </em><a href="https://www.instagram.com/e_spres_oh/"><em>Instagram</em></a><em> (but not in a creepy manner).</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17b4be9ab0d4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tea-break-by-e-spres-oh/tech-trends-that-will-shift-your-business-to-version-2-0-2-0-17b4be9ab0d4">Tech Trends That Will Shift your Business to Version 2.0.2.0</a> was originally published in <a href="https://medium.com/tea-break-by-e-spres-oh">Tea Break by [e-spres-oh]</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Looking back, coding forward: A decade minus two years of digital lessons learned]]></title>
            <link>https://medium.com/tea-break-by-e-spres-oh/looking-back-coding-forward-a-decade-minus-two-years-of-digital-lessons-learned-6cacf091a5c6?source=rss-d61e3d499379------2</link>
            <guid isPermaLink="false">https://medium.com/p/6cacf091a5c6</guid>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[The [e-spres-oh] Team]]></dc:creator>
            <pubDate>Mon, 20 Jan 2020 11:44:32 GMT</pubDate>
            <atom:updated>2020-01-21T11:00:35.379Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0J3eaz2Zn9ZERpUdq4ACuQ.jpeg" /></figure><p>With the end of the decade, we felt the need to look back and reflect on our journey thus far. It’s been quite a ride! Hope you’ve had your morning brew, because we’re about to share eight lessons from our eight years of coding, designing and drinking coffee.</p><h3><strong><em>Lesson 1: Start small, think big</em></strong></h3><p>In 2012, we were a small team with big dreams, embarking on a single digital project. We didn’t have an “office”, but we were happy to code out of whichever place gave us the greatest fuel: coffee. This was actually what inspired our name: <a href="https://www.e-spres-oh.com/">[e-spres-oh]</a>.</p><p>Eight years later we know that success is not dictated by the initial resources. <strong><em>Success is driven by the ambitions you fuel your journey with. </em></strong><em>It’s about code, coffee and reinventing the cup.</em></p><h3><strong><em>Lesson 2: You always need a bigger cup</em></strong></h3><p>By 2013, we had already grown so much that we couldn’t fit in coffee shops anymore. So we decided to get a proper office. Okay, an <a href="https://www.facebook.com/pg/espresoh.tech/photos/?tab=album&amp;album_id=616254625051373">oh]-mazing office</a>. We restored a three story historical building and transformed it into a hip working space that incorporated the coffee shop vibe that got us going.</p><p><strong><em>Growth has to be celebrated but also encouraged</em></strong><em>. And the new office spoke a mixture of both.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/661/1*daP-xNh7PtVyzOwMBYdgSA.png" /><figcaption>Article in <a href="https://freshome.com/">freshome</a> about [e-spres-oh]’s new office</figcaption></figure><h3><strong><em>Lesson 3: Put people first</em></strong></h3><p>The opening of our coding-playground in 2013 gave us the opportunity to host several community events such as the first tim.js JavaScript meet-up. More growth led to the opening of extra work-space in 2014. AltClub was an alternative office that also had a bar, a fully-equipped professional kitchen, and a game zone. With two working spaces, we could choose from, well… in 2016 and 2017 we gathered the entire team and went on remote working getaways around Europe (who could forget <a href="https://teabreak.e-spres-oh.com/the-ohlisbon-experience-a13b00737301#.48zvubbe1">#ohlisbon</a>?).</p><p><strong><em>Great software products happen only if you have the best developers.</em></strong> And, in order to attract unique talent, we need to nurture the software community while helping our own coders discover new grounds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rBOYF958DgCF4Tyl" /><figcaption>Concert at one of [e-spres-oh]’s trimestrial parties</figcaption></figure><h3><strong><em>Lesson 4: Share the knowledge</em></strong></h3><p>Sharing the knowledge started with the idea to create an internal <a href="https://www.youtube.com/watch?time_continue=10&amp;v=-3c35nML_6g&amp;feature=emb_title">weekly Demo</a> with the intention to help our teams get in-sync. In 2016 we opened the <strong>[e-spres-oh] Academy </strong>(later on rebranded <a href="https://www.decodeacademy.ro/en/">Decode Academy</a>) and began a series of tech, design and marketing courses for everybody. In 2019 we were proud to team-up with <a href="https://www.meetup.com/tim-js/">tim.js</a> and create <a href="https://teabreak.e-spres-oh.com/fueling-the-first-edition-of-revo-js-3b05bdb7f95c">revo.js</a>, the first JavaScript conference in Timisoara, Eastern-Europe’s Tech Hub. We also started a <a href="https://podcast.e-spres-oh.com/">series of tech podcasts</a> featuring leaders and C-level executives that disrupt the industry. With the new year, we’re working on a new laboratory class for University students.</p><p>Bottom line is that we’re certain that <strong>learning wouldn’t happen without sharing. </strong>In fact, that’s why we are writing this article.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AMuqcwgqC96U735Y" /><figcaption>Introduction in UX Design Course @ Decode Academy by [e-spres-oh]</figcaption></figure><h3><strong><em>Lesson 5: Multi-functional teams are key</em></strong></h3><p>In 2017 we diversified our digital products’ portfolio and decided to grow <a href="https://teabreak.e-spres-oh.com/pushing-for-data-driven-design-c009fde8c98a">our own UX/UI department</a>. In the past years, we have introduced more team roles and completed the circle with the addition of <a href="https://teabreak.e-spres-oh.com/business-analyst-for-auto-europe-an-analytical-story-of-why-and-how-c749a8ff3a4e">business analysts</a>. Now, we’re stepping up again by empowering our teams with product engineers (and even more coffee, of course).</p><p><strong><em>We’ve learned that approaching complex products successfully can only be done by tackling them from all perspectives.</em></strong></p><h3><strong><em>Lesson 6: Great can always become greater</em></strong></h3><p>From sticking to our<a href="https://teabreak.e-spres-oh.com/how-we-start-successful-software-engagements-with-great-energy-3284cb8f962e"> strong collaborations’ ethic</a> to working on bigger projects and developing internal projects, we have always strived for “better”. The greatest success came in 2019 when <a href="https://teabreak.e-spres-oh.com/e-spres-oh-gets-acquired-by-us-investment-group-and-moves-towards-bigger-things-with-the-same-2ebe6f7093a7">[e-spres-oh] got acquired by Alpine Consolidated</a> and we moved our headquarters to Washington, D.C. while continuing to grow our engineering offices in Timisoara, Romania.</p><p><strong><em>We now know that in order for companies to be great, they have to continuously explore new grounds.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qZZPibGLhxIRrXOp" /><figcaption>Enhanced team after <a href="https://www.alpineconsolidated.com/">Alpine Consolidated</a> acquisition</figcaption></figure><h3><strong><em>Lesson 7: Have fun</em></strong></h3><p>Throughout the last decade, our offices were home to coding, but also to enjoying concerts, theatre plays and countless parties in the attic. We worked-out our coding and design skills, but also our muscles during marathons and <a href="https://www.facebook.com/pg/espresoh.tech/photos/?tab=album&amp;album_id=1730521983624626">hiking trips</a>. We even took it upon ourselves to organize a <a href="https://www.facebook.com/pg/espresoh.tech/photos/?tab=album&amp;album_id=2420893407920810">climbing challenge</a> for the entire tech community. And, in between, we also took the time to say “cheers!” with our very own beer, <a href="https://www.facebook.com/espresoh.tech/videos/498557967564342/">crafted in collaboration with the coolest craft beer brewer in town</a>.</p><p><strong><em>All in all, we’ve had 8 years of great times, which is what it’s all about.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Hnqq5festzPSvz9M" /><figcaption>Cold Bru, [e-spres-oh]’s own beer, collab with <a href="https://www.facebook.com/BeretaTM/">BeretaTM</a></figcaption></figure><h3><strong><em>Lesson 8: Drink coffee.</em></strong></h3><p>Now, let’s all get back to coding a new decade and learning its lessons. Yes, some will be bitter, some will be sweet and others will taste just like the perfect cup of coffee. To more of those!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Cv6Gnsh5WhRgqYxQH1bNg.jpeg" /><figcaption>Coffee-cake, the best of both worlds</figcaption></figure><p><em>If you want to keep up with our mischievous ways of coding and doing fun things with great energy, subscribe to </em><a href="https://teabreak.e-spres-oh.com/"><em>Tea Break</em></a><em> (our blog right here on Medium), stay up-to-date with our </em><a href="https://www.linkedin.com/company/2820676"><em>LinkedIn</em></a><em>, like our </em><a href="https://www.facebook.com/esoh.tech/"><em>Facebook page</em></a><em>, talk to us on </em><a href="https://twitter.com/e_spres_oh"><em>Twitter</em></a><em> or follow us on </em><a href="https://www.instagram.com/e_spres_oh/"><em>Instagram</em></a><em> (but not in a creepy manner).</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6cacf091a5c6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tea-break-by-e-spres-oh/looking-back-coding-forward-a-decade-minus-two-years-of-digital-lessons-learned-6cacf091a5c6">Looking back, coding forward: A decade minus two years of digital lessons learned</a> was originally published in <a href="https://medium.com/tea-break-by-e-spres-oh">Tea Break by [e-spres-oh]</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product or Project Approach: Which One, When and Why]]></title>
            <link>https://medium.com/tea-break-by-e-spres-oh/product-or-project-approach-which-one-when-and-why-b3a5b4a3ae2a?source=rss-d61e3d499379------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3a5b4a3ae2a</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[insights]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[product-mindset]]></category>
            <dc:creator><![CDATA[The [e-spres-oh] Team]]></dc:creator>
            <pubDate>Mon, 16 Dec 2019 09:34:38 GMT</pubDate>
            <atom:updated>2019-12-16T09:34:38.194Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jeYZXY-q_jGsCoQusMvhqQ.jpeg" /></figure><p>The showdown between the “project” and “product” mindset has been sweeping the software industry, even the most reserved developers are getting heated and opinionated. While some voice a definite winner, as far as we’re concerned, it all depends on what each of our clients aims to achieve.</p><p>But we get it. From a software company’s perspective, the product mindset has an undeniable appeal, returning the highest professional satisfaction. On the other hand, projects can present thrilling digital challenges too, so we’re not quick to dismiss the approach. Thus, the question “Which one to follow?” remains. What now?</p><p>It’s not about what we prefer. We believe all clients should know what each model entails in order to pick a side(and win!). Without further ado, here’s the difference between both the product and project approach.</p><h3><strong>Product-approach: Business at the Core</strong></h3><p>When engagements between a software company and a particular client follow a product approach, it means that either the digital product that’s being developed is the core of the client’s business or that they have a persistent business issue that can only be solved with tech.</p><p>In this case, a custom multi-functional team is whipped together to ideate, build and run the product on an on-going basis. The team will act as an embedded part of the client’s business. Usually it will include developers and <a href="https://teabreak.e-spres-oh.com/pushing-for-data-driven-design-c009fde8c98a">UX designers</a>, but it will also leverage soft or analytical skills from <a href="https://teabreak.e-spres-oh.com/business-analyst-for-auto-europe-an-analytical-story-of-why-and-how-c749a8ff3a4e">business analysts</a>, product owners, product engineers and other specialists.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YrfMdZEUcmDBE4I97Y9pAQ.jpeg" /></figure><p>Regularly tuning in with the client, the team establishes the scopes and specs, but has the flexibility to reorient quickly without losing the architectural integrity of the software. With a vision on long-term effectiveness, the product team also performs short-cycle iterations to perfect and grow the product indefinitely.</p><p>The budget in a product approach is not fixed. While specific guidelines or even monthly budgets are agreed upon, adjustments in accordance with any new requirements are to be expected. Time-wise, the product approach is open-ended, with software teams working as long as the product is successful and profitable.</p><h3><strong>Project-approach: Specific Problem Targeting</strong></h3><p>The project model can be applied to solve specific problems that are adjacent to the core of a client’s business. Thus, whenever a target is clear and quantifiable in terms of time, budget and scope, running a development engagement by following a project approach makes a lot of sense.</p><p>To tackle a project engagement, smaller teams are formed. Often times, these are build-only teams that have a single focus. With a well-defined task and scope, the teams develop the digital project in an established time-frame, without having too much calibration freedom.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2yKpI-DmLmNlSi2SdAZGww.jpeg" /></figure><p>The risk in this particular case is coming up with an end-result that is well within the initial estimations but that’s not 100% adjusted to the perfect real-life environment. We all know that tech changes at unbelievable speeds, so the biggest danger of project-based engagements is sticking with only one method just because it was planned. We’re huge advocated for flexibility, no matter if it’s “product” or “project”.</p><p>The project approach type of engagement has fixed budgets and fixed timelines. Again, while constraints can be real focus-generators when it comes to getting teams to pull-through, these should be reassessed if the better of the project requires it.</p><h3><strong>Talk it over.</strong></h3><p>The verdict is in and there’s no fit-all right or wrong answer. Choosing between one collaboration model or another should be tailored to fit a client’s final objective.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w7XlcnNwnG6wlmPZ7W7kGg.jpeg" /></figure><p>So, when deciding if it’s a “product” or “project” mindset we should follow, it’s about you and us together. Only as a team we can discover which model is best. And the answer is, each time and engagement, it is different.</p><p><em>If you want to keep up with our mischievous ways of coding and doing fun things with great energy, subscribe to </em><a href="https://teabreak.e-spres-oh.com/"><em>Tea Break</em></a><em> (our blog right here on Medium), stay up-to-date with our </em><a href="https://www.linkedin.com/company/2820676"><em>LinkedIn</em></a><em>, like our </em><a href="https://www.facebook.com/esoh.tech/"><em>Facebook page</em></a><em>, talk to us on </em><a href="https://twitter.com/e_spres_oh"><em>Twitter</em></a><em> or follow us on </em><a href="https://www.instagram.com/e_spres_oh/"><em>Instagram</em></a><em> (but not in a creepy manner).</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3a5b4a3ae2a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tea-break-by-e-spres-oh/product-or-project-approach-which-one-when-and-why-b3a5b4a3ae2a">Product or Project Approach: Which One, When and Why</a> was originally published in <a href="https://medium.com/tea-break-by-e-spres-oh">Tea Break by [e-spres-oh]</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>