<?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 Daniel Hauschildt on Medium]]></title>
        <description><![CDATA[Stories by Daniel Hauschildt on Medium]]></description>
        <link>https://medium.com/@drhouseshield?source=rss-488c00edc939------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4Xi-swKul_k74Uc7mCNJ9A.jpeg</url>
            <title>Stories by Daniel Hauschildt on Medium</title>
            <link>https://medium.com/@drhouseshield?source=rss-488c00edc939------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 17:26:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@drhouseshield/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[On the Democratization of Design]]></title>
            <link>https://medium.com/imgly/on-the-democratization-of-design-ce731e9374f0?source=rss-488c00edc939------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce731e9374f0</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[image-processing]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[photography]]></category>
            <dc:creator><![CDATA[Daniel Hauschildt]]></dc:creator>
            <pubDate>Mon, 24 Jun 2019 11:53:30 GMT</pubDate>
            <atom:updated>2019-06-24T11:53:30.658Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UUXCltgfNnl3pabjCsjjGg.jpeg" /></figure><p>Over the last century we have experienced the democratization of various domains of our lives:</p><p>Key drivers have been technological advancements and lower barriers to leveraging those technologies. In turn, technology became more accessible to more people resulting in products, services, and tools that improve our lives every day.</p><blockquote>“Computers are a bicycle for the mind” — Steve Jobs</blockquote><p>Tools, such as computers, allow us to finish more tasks in a shorter amount of time and with fewer resources. Even more importantly, said tools also rid us from boring and repetitive work, thus enabling us to shift our attention to exciting and more creative tasks, paving the way for us to experiment and create rather than repeat.</p><h3>Evolve Design with better Tools</h3><p>Proper visual design attracts, engages, and persuades; it helps convey stories and facilitates communication.</p><p>Nowadays, design in all its facets like advertising, social stories, product presentations, or merchandise is omnipresent in our daily lives. As there is no arguing that appealing and beautiful design has an impact on us and our surrounding, consequently there is also a growing demand for good design and easy-to-use tools.</p><blockquote>“Use a picture. It’s worth a thousand words!” — Arthur Brisbamne</blockquote><p>Although the importance of design is unquestioned, creating appealing designs remains hard for most of us, and there are many reasons for that.</p><p>First of all, design tools are still challenging to master, and while they empower professional designers to create stunning assets, they remain a closed book for most people.</p><p>Secondly, even if we leave most of the creational part to professionals, the average user is still unable to use existing designs as a basis to create new assets or refine and update small details. Even for the slightest changes, one has to get familiar with the inner workings of sophisticated design tools.</p><p>Also, when it comes to collaboration, the process with most tools is far from frictionless, to put it mildly. Still, most designs get shared as Photoshop, Sketch, or PowerPoint files, and there is no tool or platform that grants unhindered access for multiple stakeholders with varying degrees of experience with design solutions.</p><p>As today’s design processes regularly involve multiple stakeholders like designers, marketers, copywriters, or product engineers, one has to acknowledge that prevalent design solutions simply lack features and workflows that reflect daily routines.</p><h3>Make Design Accessible through Technology</h3><p>As we pointed out, the overall access to good visual design is still very limited, but with the growing need for compelling creatives in virtually every aspect of the digital and non-digital realm this shouldn’t be and it doesn’t have to. We believe in the democratization of design.</p><blockquote>Better tools enable the democratization of design!</blockquote><p>We believe that:</p><ul><li>We need to overhaul design processes and methods to cope with the ever growing design needs and the ever-rising number of stakeholders.</li><li>Achieving elegant design must be made simple.</li><li>Design can be made accessible through technology.</li></ul><p>The question remains: How do we achieve that?</p><p>We came to the conclusion that there are four key elements design tools should have that will make design more accessible:</p><ol><li>Collaboration,</li><li>building blocks of intelligent design components,</li><li>automation of tedious design tasks, and</li><li>bringing together Editing, Compositing, and Layouting.</li></ol><p><strong>Collaboration</strong></p><p>We hold as an opinion that design tools have to facilitate the collaboration between professionals and non-professionals, thus allowing an effective and frictionless design creation and adaption process. This includes direct collaboration on a design as well as the exchange of whole design templates, design components, and presets.</p><p>While some solutions already offer templates for content creation, we think that design components as a more modular approach are going to be a necessity to simplify the creation of new complex assets for everyone.</p><p><strong>Building Blocks of Intelligent Design Components</strong></p><p>If Lego™ taught us anything, then it is that creativity can flow when you base your work on a solid foundation.</p><p>That said, one has to admit that while the basic elements of design such as text, shapes, or images can be creatively combined in millions of ways to create stunning designs, they also can be used in a trillion ways to create underwhelming output.</p><p>Similar to modern UI design, complex building blocks will play a central role in the visual design process, allowing creators to be more efficient by removing repetitive tasks from the workflow and also allowing average users to create and adopt complex designs quickly. Intelligent design components will shift the focus to the composition by guiding the user in carefully chosen constraints.</p><p><strong>Automation of Tedious Design Tasks</strong></p><p>Speaking of intelligent building blocks, we believe that said blocks must not be static but adaptive to fit into an effective and frictionless design process. That may include the automation of certain design tasks like text layout or even abstracting away the complexity of image editing.</p><p>We envision that with the help of technology and specifically artificial intelligence, recurring and taunting tasks like for example, the separation of a picture into fore- and background can become totally interaction- and hassle-free. Even automatically choosing the right adjustments based on the image content will be possible.</p><p>Altogether, intelligent design components are a necessity and will be the next step in design automation, fostering a flexible and fail-safe adaption and creation process and thus ensuring that even without professional knowledge designs will be created faster and look better.</p><p><strong>Bringing together Editing, Composition, and Layouting</strong></p><p>Photo editing and layouting are both central to the design process. That is why, in a holistic approach, combining both will yield exciting new possibilities, improved visual consistency, and a reduced amount of friction while going back and forth between layout and photo editing.</p><h3>Closing words</h3><p>To sum it up: To democratize design, we need intelligent design tools and ecosystems that allow for the cooperation between all stakeholders, as well as a community that is open to share and learn from one another by building and sharing reusable and intelligent design components.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce731e9374f0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/imgly/on-the-democratization-of-design-ce731e9374f0">On the Democratization of Design</a> was originally published in <a href="https://medium.com/imgly">IMG.LY</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rebuild or Report?]]></title>
            <link>https://medium.com/imgly/rebuild-or-report-211d6ac6e787?source=rss-488c00edc939------2</link>
            <guid isPermaLink="false">https://medium.com/p/211d6ac6e787</guid>
            <category><![CDATA[code]]></category>
            <category><![CDATA[bug-report]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[support]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[Daniel Hauschildt]]></dc:creator>
            <pubDate>Thu, 26 Apr 2018 12:38:24 GMT</pubDate>
            <atom:updated>2019-07-16T15:49:01.691Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3nG4Ayoaym4TQ6jlBHcAxA.png" /></figure><h4>On helping yourself and others through precise Bug Reports</h4><p>Nowadays, every code project depends on various third party and additional libraries. Truth be told, we wouldn’t be able to create apps or webpages that fast if we would have to build everything from scratch. Typically, we add a library via our favored package manager and give it a go. We start using that specific library, read the docs, figure out how it works and use it for our purposes. Best case, that’s it. Unfortunately, in practice, it may turn out differently.</p><h3><strong>Make no Mistake, Mistakes happen</strong></h3><p>While we work with a specific library, we may encounter some roadblocks. Sometimes that’s due to missing or bad documentation. Or it might be due to our missing knowledge about some things. Anyway, sometimes, we eventually realize that it is not us, it was them all along. We found a mistake, a so-called bug.</p><blockquote>A (software) bug is an error, flaw, failure or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways.</blockquote><blockquote>— Wikipedia</blockquote><p>If we’re honest, our first reaction may be that we get angry at the library itself or the author, but, after acknowledging that we never wrote flawless or bug-free code, we look for a solution.</p><h3><strong>We found a Bug! Now what?</strong></h3><p>Logically, some of us start to follow the most obvious path. We throw that library away and write a replacement ourselves…<strong>not</strong>.</p><p>Ok, honestly, we may think about that, but it in most cases that is neither the right nor the best way to go. Many authors put a lot of effort into creating software libraries and shared it with us. So, most undoubtedly, a lot of knowledge, work, testing and time has already gone into it.</p><p>Therefore, there is a high chance that rewriting that library from scratch is the least favorable option.</p><blockquote>So, what should we do?</blockquote><p>Worst case scenario: We don’t do anything and leave it be. But this way it won’t get fixed, the authors won’t be aware of it, and others will encounter the same bug and spend unnecessary time on it.</p><p>Best case scenario: We track down the bug, propose a solution to the authors and hope they will acknowledge and accept it. But sometimes we don’t have the means, options or time to fix the bug. Consequently, the second best way is telling the authors about the bug you found. But wait, before we file a bug we should ask ourselves the following question</p><blockquote>Are we running the latest version of the library?</blockquote><h3><strong>Writing good Bug Reports helps Yourself and Others</strong></h3><p>We at <a href="https://img.ly/">img.ly</a> provide a software library for photo editing. Thus, we are both library authors as well as users.</p><blockquote>I would like to say that we don’t ever make mistakes, but truth be told, everyone does.</blockquote><p>As you can imagine, providing photo editing capabilities results in a lot of code for rendering, UI, or other business logic. Although all the usual quality checks are in place, mistakes or unthought-of use-cases manifest in bugs, no matter what.</p><p>Consequently, we get bug reports. Now, unfortunately, an awful lot of said bug reports only contain a single line that literally says:</p><blockquote>“XYZ does not work.”</blockquote><p>While, this is far better than not reporting it at all, it doesn’t help much in hunting down the bug.</p><p>With bug reports like this, we spend a lot of our time on trying to reproduce the bug or asking for details on how to reproduce it. That time would be better spent on improving the libraries or helping other users. However, with just a little help we’d be able to find bugs faster and be more effective. So, what should a proper bug report look like? From our point of view, bug reports should be comprised out of the following things:</p><ul><li>One bug at a time,</li><li>the context of the bug,</li><li>a minimal runnable example, and</li><li>the steps to reproduce the bug.</li></ul><h3><strong>One bug at a time</strong></h3><p>In reality, one may encounter multiple bugs at the same time, and might wish to drop them at the library authors all at once. However, it is far better not to combine multiple problems even if they seem to be alike. So, one should always report each bug individually.</p><h3><strong>Describing the context</strong></h3><p>Often forgotten when reporting bugs is to describe the context the bug occurs in. For us, a good bug report contains at least the following specifications:</p><ul><li>A description,</li><li>the environment</li><li>the actual and desired output, and</li><li>attachments (e.g. Screenshots).</li></ul><h4>Description</h4><p>First thing we need to know is what the bug is about. This includes:</p><ul><li>A short meaningful <em>title</em> of the bug (e.g. Exporting image after crop and rotate corrupts output), and</li><li>a <em>description</em> of the bug which explains the error in an understandable manner.</li></ul><h4>Environment</h4><p>Due to the nature of web and app development, software libraries can be used in many different environments. All of which have their own little differences and quirks. Thus, it is very helpful to include information about the environment, including:</p><ul><li>the used <em>operating system’s </em>version (e.g. iOS 10.1),</li><li>the <em>device</em> it is running on (e.g. iPhone 7 32GB),</li><li>the <em>used browser or runtime environment</em> and its version (e.g. Chrome 65.0.3325.181 (64-Bit) or Node.js 8.11.1 ), and not to forget</li><li>the <em>name of the library</em> and its version/variant (e.g. pesdk-html5 4.1.3).</li></ul><h4>Actual Output and Expected Output</h4><p>Often, an experienced developer can classify the bug on the basis of the resulting error or error output only. Therefore, a useful bug report should provide:</p><ul><li>the<em> actual output</em> that is is observed, and</li><li>the <em>desired output</em> that should be generated</li></ul><h4>Attachments</h4><p>Additionally, attachments are very helpful to pinpoint the bug. Helpful attachments can be but are not limited to:</p><ul><li><em>error output or logs</em><strong> </strong>generated by the compiler and build system, console output, and stack trace, and whenever the bug results in something that is visual recognizable, and</li><li><em>screenshots</em> showing the issue.</li></ul><h3><strong><em>Reproducibility</em> is key</strong></h3><p>While all aforementioned greatly assists to narrow down the context in which the bug appears there is one thing that helps even more:</p><p>Even if it seems trivial to reproduce, a good bug report should come with a <em>minimal runnable example</em> that produces the bug in question and a description of how to trigger it.</p><h4>Providing a minimal running Example</h4><p>So, one should strip away everything from the current code that isn’t necessary and keep it simple. The faster we and other library maintainers can track down an error, the sooner it’s going to be fixed.</p><p>Also, probably it was already necessary to narrow down the issue so stripping it out into a minimal example is not too much work. If possible, the Gist should be provided via a GitHub repository or any other similar sharing system.</p><h4><strong>Keep it simple to trigger the Bug and be specific about it</strong></h4><p>While having a minimal example is already lovely, sometimes it needs a bit more than just code to trigger the bug. Writing down precise instructions on how to trigger it is not always easy but being specific dramatically helps to get to it.</p><p>That is why one should summarize the problem in brevity and with utmost precision.</p><h3>Conclusions</h3><p>From our point of view these are the most important things one needs to consider when reporting a bug. Most certainly, the requirements change and need to be adapted for different types of software. We’d really like your feedback on this. So, if you have any comments and additions please let us know.</p><h4>Thanks a lot for reading. If you’ve enjoyed this piece, applaud hearty! Also, you might want to subscribe to our Newsletter, so we can keep you posted about our latest Articles and Case Studies.</h4><figure><a href="https://photoeditorsdk.us13.list-manage.com/subscribe?u=dc9f652839dbb620d14d6d28d&amp;id=04a306e4b2"><img alt="" src="https://cdn-images-1.medium.com/max/150/1*R1Fb2pIT6GEUszuj6Bo-uA.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=211d6ac6e787" width="1" height="1" alt=""><hr><p><a href="https://medium.com/imgly/rebuild-or-report-211d6ac6e787">Rebuild or Report?</a> was originally published in <a href="https://medium.com/imgly">IMG.LY</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build or Buy?]]></title>
            <link>https://medium.com/imgly/build-or-buy-f09785ce1138?source=rss-488c00edc939------2</link>
            <guid isPermaLink="false">https://medium.com/p/f09785ce1138</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[framework]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[developer-tools]]></category>
            <dc:creator><![CDATA[Daniel Hauschildt]]></dc:creator>
            <pubDate>Thu, 02 Nov 2017 15:14:14 GMT</pubDate>
            <atom:updated>2019-07-16T15:42:28.634Z</atom:updated>
            <content:encoded><![CDATA[<h3>Build or Buy? — A delicate decision between buying years of experience versus making your own secret sauce.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*leT6ftmXam6V1MPhpR1Qzw.jpeg" /></figure><p>We all know the deal; thoughts about new products bounce around in our heads and sometimes those thoughts yield ideas we want to pursue. Once that happens we start putting ourselves into action by building a prototype, ideally on the shortest path possible.</p><p>For many years, we at <a href="https://img.ly/">img.ly</a> and our partners at <a href="https://9elements.com/">9elements </a>have been developing various applications for customers and ourselves. Often, we had to decide whether to build everything from scratch or to consider third party components. Sounds familiar?</p><p><strong>As developers, makers and tinkerers we often tend to build everything ourselves.</strong> It seems to be in our nature and part of who we are. Truth be told, this is the point where we often got irrational.</p><p>Taking a good look at modern application development, we quickly realize that everything is getting more complex in a tremendous pace. While it was feasible to develop apps without any third party libraries back then, it has become more or less of a standard to employ third party libraries or tools that solve certain problems for us. Nowadays, there are a lot of features that are must haves and simply expected to be in your product.</p><p>Thus, we are more aware than ever when it comes to the decision whether to build or buy.</p><h4><strong>Decisions</strong></h4><p>Most often, our resources are not endless. With limited time, money, and labour power<strong> </strong>we always struggle to make the decision whether to build a certain component of our software ourselves or buy it from a third-party.</p><p>But why do we struggle? Are we sure we can do it better than everybody else? Are we not trusting the third-party? Do we just think it is cheaper to do it ourselves? Or, do we just underestimate the amount of work that is required to build that one component?</p><p>Most certainly we know that software, even a small app, can be a complex beast that is comprised out of a lot of components. Even more surely, our idea or product should stand out of the masses. So, should we really spend too much time building a component or rather focus on getting things done efficiently? How do we set the priorities?</p><h4><strong>Priorities</strong></h4><p>Probably, we want to focus on the things that set our product apart from all others, may it be a singular specific feature or a novel combination of already existing ones.</p><p>Surely, most of us will never consider writing their own relational database like PostgreSQL. But, what about features such as payment, authentication or a content management system?</p><p>Speaking from experience, most of us won’t even think about implementing payment themselves and eventually, we will use a popular SaaS such as <a href="https://stripe.com/">Stripe</a>. But, what about authentication? Would we build that ourselves?</p><p>Thinking about all the details that you need to account for when building an authentication system, it becomes obvious that more is needed than just providing a simple registration with username and password. Depending on the software we are developing, people might expect to be able to login with their social logins via e.g. <a href="https://facebook.com/">Facebook</a> or <a href="https://github.com/">GitHub</a>. Also, we would need to provide a way to reset passwords, send emails on registration and so on. Over time, the list of requirements will grow and we will be forced to spend our precious resources on it, whether we want it or not.</p><p><strong>So, why not just let someone else do the job for you and solve all these problems?</strong></p><p>Don’t we trust services like <a href="https://auth0.com/">Auth0</a> to solve all these problems for us, or what is the reason we build those things ourselves? Evidently, if our product <em>is</em> an authentication system we <em>should</em> build it ourselves. But, let’s be honest, most of the time it is just something we <em>need</em> for our product and nothing we care about deeply.</p><p>Unfortunately, we know that everything comes at a price. In case of <a href="https://auth0.com/">Auth0</a>, the login data may not be any more in our possession. However, are we sure that it is really bad? We tell ourselves that we can protect our data in a way that no one else would have access, no data would be leaked and so on. At least, that is what we would be thinking, right? But, are we sure that we can protect the data better than the service whose one and only task is to care about exactly that? And what about backups? Do we really want to put our resources into creating and checking that our data is properly backed up and restorable in case of a server failure? Probably we won’t and in many cases it would be a good idea to let someone do the job who does it on a day to day basis. Being completely honest with ourselves, we realized that:</p><p><strong>By zeroing in on one specific problem, we can build better and more advanced tools than we could by trying to solve multiple problems at once.</strong></p><p>We experienced first hand how much time and effort is required to tackle one specific problem when we needed a photo editing solution as part of one of our projects. In that particular case, we needed to go down the rabbit hole and <a href="https://www.photoeditorsdk.com/?utm_campaign=Blog%20&amp;utm_source=Medium&amp;utm_medium=PESDK&amp;utm_content=Build%20or%20Buy">build it ourselves</a>. Back then, we didn’t have any other option as there was no component available that we could have used.</p><p>Was it a good idea? Probably not for the project but while building the components we realized that others could benefit from our learnings. This is basically why we started building and advancing our <a href="https://www.photoeditorsdk.com/?utm_campaign=Blog%20&amp;utm_source=Medium&amp;utm_medium=PESDK&amp;utm_content=Build%20or%20Buy">PhotoEditor SDK</a>.</p><p>Apart from the previous mentioned pros and cons about building and buying, there is also another important factor: These services cost money and most of us will look at the pricing and believe it may be too expensive. Especially, if you have to take out your credit card and start a subscription that may feel like slowly draining your bank account. Even more so if you’re a small business or startup and every additional expense poses a threat to your project as a whole. However, this is the time to really weigh your options.</p><p><strong>Time is Money</strong></p><p>We always hear and rephrase the good old <em>time is money</em> slogan. And this is true in many ways. Even if we don’t care much about the cost of our own time, we would still have to invest it to build said feature and by that might delay the whole product. Do we really want to spend that time and delay our whole product?</p><p>Ok, assuming we don’t do it ourselves and we have a team of developers and parallelize our efforts, we still need to pay for it with, and let’s be honest … money.</p><p>According to <a href="http://www.payscale.com/research/DE/Job=Software_Developer/Salary">PayScale</a> the average salary of a software developer is around 45k€ in Germany. Considering that we work around 220 days per year, each day would at least cost us approximately 200€, but to be fair it will surely be more. Depending on the software component you are considering to build or the SaaS we consider to use, we most surely would get a lot more for our 200€ than what we could build in one day. And, if we are honest, 200€ are definitely not enough to develop any feature that requires more than just a few lines of code.</p><h3><strong>Final words</strong></h3><p>Summing it up, we should definitely not just buy every component from a third party or subscribe to every SaaS, but we should weigh carefully in which cases we really have to build it ourselves or when buying is the better option.</p><p>The whole point is that whether you buy some of your components or build everything yourself really doesn’t matter as long as it’s the smartest decision for your business. And if you automatically shy away from solutions that cost you something and decide to build it yourself no matter what, that decision might cost you a whole lot more.</p><p>The good thing is, that there is a trend that third parties tend to focus on more granular problems, which allows us to make the distinct decision whether to build or buy a specific component of our application.</p><h4>Thanks a lot for reading. If you’ve enjoyed this piece, applaud hearty! Also, you might want to subscribe to our Newsletter, so we can keep you posted about our latest Articles and Case Studies.</h4><figure><a href="https://photoeditorsdk.us13.list-manage.com/subscribe?u=dc9f652839dbb620d14d6d28d&amp;id=04a306e4b2"><img alt="" src="https://cdn-images-1.medium.com/max/150/1*R1Fb2pIT6GEUszuj6Bo-uA.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f09785ce1138" width="1" height="1" alt=""><hr><p><a href="https://medium.com/imgly/build-or-buy-f09785ce1138">Build or Buy?</a> was originally published in <a href="https://medium.com/imgly">IMG.LY</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>