<?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 KOstas Hatzis on Medium]]></title>
        <description><![CDATA[Stories by KOstas Hatzis on Medium]]></description>
        <link>https://medium.com/@kostas_hat?source=rss-3a08b0569951------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*oE0dEY84lE2iJ3Z8D5LzuQ.jpeg</url>
            <title>Stories by KOstas Hatzis on Medium</title>
            <link>https://medium.com/@kostas_hat?source=rss-3a08b0569951------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 06:52:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kostas_hat/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[Quality product? Software testing.]]></title>
            <link>https://medium.com/monospace-pub/quality-product-software-testing-fdbbc9e6ffd4?source=rss-3a08b0569951------2</link>
            <guid isPermaLink="false">https://medium.com/p/fdbbc9e6ffd4</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[quality-software]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <dc:creator><![CDATA[KOstas Hatzis]]></dc:creator>
            <pubDate>Tue, 18 Jul 2017 10:25:33 GMT</pubDate>
            <atom:updated>2017-07-20T12:30:17.131Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*vFyiK-2mpFrBT3lYrFhT6A.jpeg" /></figure><h4>A high level talk for the QA of a product.</h4><p>Everyone knows that today’s software products become more complicated while we use new technologies. We use new languages or frameworks that are still in beta. <a href="https://facebook.github.io/react-native/versions.html">React Native</a> for example still, has not stable version 1.0. Developers are busy knowing the new techniques and implement on time the requirements. Software houses are running to catch the deadlines and pushing to deliver to their customers, so they get paid.</p><p>Then, how we guarantee the quality of the product when the developers don’t have the time to test thoroughly? Many products go for testing when go live! Or in better cases, the customer examines what he gets. How then we say to our clients that they’re getting a quality product? And let’s be serious, using an issue tracker software to add some bugs, it’s not a “characterized by careful consideration” business.</p><h4><strong>A testing strategy for everyone</strong></h4><p>The right time to organize your testing strategy for a product is …the day one (<a href="https://en.wikipedia.org/wiki/Test-driven_development">Test Driven Development</a>). As soon as you start implementing your new sweet code of yours, you initiate the testing procedure too. All the people in the team they have to get involved. And not only them. You have to engage the stakeholders and the some of the plain users if possible. All of them.</p><p>As I read in an article recently, the Quality Assurance team doesn’t assure the quality of the product. The code itself guarantees it and the people they write it. So, each line of code from the team either makes the user happy or sad and frustrated. The user experience depends on your developers’ code quality. Certainly, the Quality Assurance team is there to alert everyone in the team about the bugs, the risk and has the open channel with the customer to communicate the problem with the broader organization.</p><p>Software teams involve all different kinds of people in the product they make: ops guys, back-end developers, front-end developers, mobile designers and developers, designers and illustrators, testers, the stakeholders and the actual users. Do not leave anyone out without a role for testing the application quality.</p><p>The strategy is: from day one until the launch day all the people that are getting involved with the project they test it. It’s a collaborative process.</p><p>Make a careful plan and engage all these fellows in.</p><h4><strong>What role do I have?</strong></h4><p>Let’s start from the …start.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/64/1*lIXlze84McPL6uufYJ1MTA.png" /><figcaption>I’m a dev and I love to test it. Just kidding ;p</figcaption></figure><p>All <strong>developers</strong> have to create and use <a href="https://phpunit.de/">unit tests</a> before writing the lines. Unit test validates small parts of the code, small components in the system. They should exist everywhere in the application to ensure and verify that the individual classes handle the information correctly. They assure that these little components work properly under expected, boundary, and negative cases.</p><p>As a product manager or a leader of a small team, you should explain this and “enforce” them to get used to it. Well, maybe you get a: “Holy Jesus in a flaming canoe! What are you saying, dude? We’re not going to catch the fucking deadline.“ But don’t you worry about. It’s a habit. And when they start doing it, after a couple of projects they can’t live without their unit tests. Don’t forget: A developer has to prove the quality of code that she delivers and owns. Developers that write unit tests are better developers.</p><p><strong>Front-end</strong> guys and gals have to test all their integrations with APIs or/and external services. They have to cooperate with <strong>designers</strong> and verify that the visual, hover and animation effects are working properly in all required screens. Also, they could do some integration test and ensure that the tested set of components play as they intended to do and work nicely together.</p><p><strong>Test Engineers</strong> they should get in early in the project and guarantee that they provide early feedback to back-end and front-end people. These are the people that they are going to give a clear eye to the developers when they need a more accurate and critical feedback. These are the fellows that they deliver the issues across the team, on the right time, to the right person, with the right description and guidance.</p><p>Test Engineers are a must part of the team if you want to deliver a quality product. They have their methods, and they use all kind of different tools.</p><p>They make automation tests with — usually- <a href="http://www.seleniumhq.org/">Selenium</a>. There are some other tools for automation test out there, but 50% of test developers use Selenium. I’m not the expert to tell you if this is the best tool, but it’s free and open source, it has a huge community in 40 countries around the world, and it can be integrated into other developer tools. It’s quite old fashion, and it’s very time intensive to maintain, especially with the agile development methods. But we could leave this on the test engineer choice.</p><p>They also have to do a manual test as well. These could be functional or explanatory tests to verify end-to-end scenarios that the users of the product will go through. They have to write down individual flows and procedures and test them thoroughly during the lifetime of the product. They have to test on different operating systems, different screens, and various devices. A painful process but necessary.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/64/1*JN1g_DWAoX9J8x2iAJURuw.png" /><figcaption>I’m a stakeholder and my product has bugs. Shit!</figcaption></figure><p>Let’s not forget the <strong>real people</strong>, the manual tests by real humans. They are the real feedback about the User Experience of what you’ve made. Test Engineers, as you already probably understood, are the connection points throughout the product. So in this phase too, they should contact the black box test with users that they have no insight into the product under test. These are the users that they’ll ride the car, and they’ll say: “this feels soo cool!” — or not! Don’t forget that all users are coming in your product as black box testers. The only person to settle the upcoming issues from this exercise and deliver them to the right individuals of the team with the right descriptions and indications are the test engineers.</p><h4>Conclusion</h4><p>We all know that we always have to maintain a shippable product. We have to deliver a steady flow of code from the developers’ cave until the user’s home. Deliver often and keep the procedure in all phases. No matter how time-consuming it is. Use as many people of the team as you can in the whole process. Use tools that are around the market for bug tracking or for any other help you need for your procedure.</p><p>We as a team use <a href="https://www.atlassian.com/software/jira">Jira Capture</a> along with Jira bug-tracker software for the whole system. Capture is an excellent solution for the regular users too. You have instant print screens and all technical information you need to start the debugging. In the past, we’ve been through <a href="https://www.pivotaltracker.com/">Pivotal Tracker</a>, <a href="https://trello.com/">Trello</a>, <a href="https://www.producteev.com/">Producteev</a>, and some other I can’t recall. Recently I’ve been through <a href="https://issuetracker.google.com/">Google’s Issue Tracker</a>. Yes! It has one. Well, let’s not stick to the tool. Tools are many for any taste. But the important thing it’s not the tool. It’s the artisan.</p><p>Have fun testing your product :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/64/1*nizaRUrau7ZYNDyrK5hA1g.png" /><figcaption>I’m just a guy… I don’t know why I’m here :(</figcaption></figure><p><em>If you liked this, click the💚 below so others will see this here on Medium.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fdbbc9e6ffd4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/monospace-pub/quality-product-software-testing-fdbbc9e6ffd4">Quality product? Software testing.</a> was originally published in <a href="https://medium.com/monospace-pub">Monospace Pub</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What we do and how in Monospace Labs]]></title>
            <link>https://medium.com/monospace-pub/what-we-do-and-how-in-monospace-labs-dd263399b1ea?source=rss-3a08b0569951------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd263399b1ea</guid>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[introduction]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[KOstas Hatzis]]></dc:creator>
            <pubDate>Wed, 14 Jun 2017 08:52:49 GMT</pubDate>
            <atom:updated>2018-12-17T14:55:15.063Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*xvorClTfvsXILsF4_lKaPg.jpeg" /></figure><h4>A short informal introductory note</h4><p>We’re a small team in Athens, Greece that makes software. Good software. Others say, great software! We have realized that we are doing something very well because our customers are happy, and they refer other people to us. They tell them that we’re a pain in the ass but also that we know what we’re doing. We know our shit. Their customers are happy, and everyone is glad to use what we’ve made.</p><p>We create software for startups. We make big applications, like CRM combined with CMS and a whole administration system. We make software for hardware, and we also make simple, user-friendly and good looking websites. We continuously try different and innovative technologies, and we take risks to implement things in a new way.</p><p>We certainly don’t have the illusion of perfection. But every day, we try hard, and we give our best to deliver good stuff that everyone will be happy to use because it will make their life better. Yes! Really. It will make their life better.</p><h3>Team</h3><p>Recently I read an <a href="https://medium.com/@cwodtke/design-the-team-you-need-to-succeed-aeb98d396fcf">excellent post</a> from Christina Wodtke. She so eloquently describes the five different team groups, and this made me curious to see in which category our group belongs.</p><p>She starts with the <strong>Workgroups</strong>. Well, I’m the product manager, but we’re not a group of individuals that work separately. I feel myself equal when we’re developing and implementing things. And all others don’t feel separate people. This is for sure.</p><p>The next group category is the “<strong>Team,</strong>” as the evolution of a workgroup. In these groups, there is a hierarchy that wastes time, money and …brain. If a design asset is missing from a frontend developer, she goes to the supervisor and asking for it and not directly to the fellow designer and say: “Yo! Where is the .svg that you’ve drawn on the mock up? Give it to me”. Dysfunctional? Absolutely. Do we belong in such category? Nope!</p><p>But after “Teams” there is another gathering named: <strong>Collectives</strong>! Christina describes it like:</p><blockquote>“In what I’m calling a <strong>collective</strong>, you see shared decision making and shared responsibility for goals. All members have a clear vision for what they want their results to be, and they both help each other and hold each other responsible their peers.”</blockquote><p>Wow! We’re working like that. Probably this is our team. We’re not only a team performing as a collective, but we’re also working together to become better every day.</p><p>And this is the next step: the <strong>Learning Team</strong>. Yes, we certainly belong to this one. We have a new presentation in a roll every week with something we’ve discovered, continuously share posts, technologies, and knowledge and we don’t hide anything from each other. Yes, we are here.</p><p>The last group of people is the <strong>Mindful Team</strong>. This team group:</p><blockquote>not only takes care of the team’s growth and learning but in each individual’s. They care about each other as people as well as colleagues.</blockquote><p>Well… I believe we’re approaching this. But nobody knows if we ever make it. Not all the people working in Monospace Labs are into caring about each other’s growth, but because of an incident we experienced <em>-one of our developers got killed with his motorbike last year-</em> a unique form of interest conjured up between some of them. Particularly in those who have experienced the incident, working in that time.</p><p>I believe that we, in <a href="https://monospacelabs.com/">Monospace Labs</a>, have the most advanced ingredients to reach the top of teamwork in a more sophisticated way. Our company fully supports this way of working and the team admires this a lot. We keep walking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*SdoFHOM4gin0Nz7nmCjJMQ.jpeg" /></figure><p>Christina has drawn all these groups in a pyramid scheme. I think of it exactly the opposite! I think of it like a funnel that eventually gets you the best human resources and the best possible collaboration between them. Refining, inventing and building every day to reach your desired goal.</p><h3>Technology</h3><p>Recently <a href="https://medium.com/@dukevomv">Duke</a>, one of our backend developers, slacks me a <a href="https://youtu.be/sBzRwzY7G-k">video</a> to watch. It was awesome and quite descriptive about all the new tech stuff around. A must-know web development tech as its title states. In fact, this video was the trigger for writing this first introductory post about us. I’ve seen in this so many applications and technologies we use every day that it was inevitable not to write about the way we work.</p><blockquote>We don’t hesitate to try new things. On the contrary, we dive into the deep waters and swim. And we like it! It’s refreshing, and we become stronger.</blockquote><p>Let me now, describe all the tools we use and how.</p><p>Let me start with <strong>design</strong>. CC of Adobe is our basic tool for designing. We use Adobe XD for our interactive experiences. We try to have a coherence and complicity between design and front-end development with continues iterations and interventions. We believe that these two aren’t separate things in the web design visual process. We have a lot of UX corrections and a continuous rearrangement of the assets.</p><p>We can start from the <strong>front-end</strong>. We couldn’t miss saying that we use CSS and HTML, of course. We go more with Twitter Bootstrap than Foundation framework and always playing responsively. At all times we use <a href="http://sass-lang.com/">Sass</a> as CSS preprocessor.</p><p>But the big change these last two years came in Javascript world. We’ve introduced in our lives the front-end build tools like <a href="http://gulpjs.com/">GulpJS</a>. Gulp is a task manager for automating time-consuming tasks in our development workflow. It takes a lot of resources, but it became necessary, and now we all use it.</p><p>The big change though came in the Javascript frameworks. We ended up to write many thousands of lines of Javascript, and inevitably we needed a tool. When we decided to use a Javascript framework, React wasn’t then in the top of the heap. We chose <a href="https://angularjs.org/">AngularJS</a>. The Google devs that made up this MVW Javascript framework say:</p><blockquote>AngularJS lets you extend HTML vocabulary for your application. The resulting environment is extraordinarily expressive, readable, and quick to develop.</blockquote><p>We adopt Angular in several projects, and we still do. It helped us big time to make extraordinary front-end experiences and had our code in order.</p><p>After some time we start looking for other tools and start comparing them. We’ve tried <a href="https://vuejs.org/">VueJS</a> that it proved to be more simple and minimal than Angular, but at the end, we were not satisfied.</p><p>After massive Angular 1 shift to Angular 2, we were not that happy, and we get to search another similar tool. Until one day we’ve seen the light! Well, maybe I’m exaggerating a little, but the day we’ve tried <a href="https://facebook.github.io/react/">ReactJS</a> was a breakthrough. It was the painless way to make interactive UIs. It was what we were looking for. After some little time we played with React Native too for all our mobile apps, and now we have the same code base for the whole project! Of course, we use it with all other apps that come with like Flux to help us in architecture or <a href="http://redux.js.org/">Redux</a> for consistent writing. We believe that this is the future and we’re on it.</p><p>In the <strong>backend</strong> now, we primarily write in PHP with the Laravel framework. Now we started a project using the awesome <a href="https://nodejs.org/en/">NodeJS</a> with its <a href="https://expressjs.com/">Express</a> framework. Yes, of course, we’ve made a project with C# and other with some Java, but now we’re in the scripting languages, and we stay there.</p><p>Probably here I have to mention that we use a bunch of things in our backend. We use Unit testing, all applications we make, expose and consume RESTful APIs, have used OAUTH2 sometimes but we moved to JWT and we are going to stay there, we’ve used websockets, and various ORMs.</p><p>Regarding databases, we certainly go with a relational database like MySQL. We often use Redis for sessions and caching. We also know how to use server caching in Apache, and we use it a lot. We use MongoDB for more documented data, sometimes in the same application with MySQL. Now because of a project’s need we shoot for a database warehouse for more complex and demanding queries. When we need a search engine, we go with Elasticsearch. We’ve tried to use the whole Elastic Stack -ELK Stack for reports- but with no luck. Yet.</p><p>I couldn’t avoid to exposing how we work in the <strong>DevOps</strong> part.</p><p>We had most of our stuff in AWS for many years. But then I met in person couple of fellows from this cool company, Digital Ocean, a beautiful start up back then, we moved all our infrastructure there. Until a hacking incident happened, a couple of years ago, and they closed our dev server down. Locked. No questions asked! We couldn’t get in for a day. It was the reason to move back in AWS for good. And I don’t think that we’re going to move out soon. They are very reliable, and when you get used to it, it’s hard to switch.</p><p>We use Linux, but in these days we explore Docker. We are not sure yet if we finally use it. Also, we move to Jenkins for CI. We’ll try SemaphoreCI too, but from a prior experience, I’m pretty confident that we finally go with Jenkins.</p><h3>Conclusion</h3><p>As a software house, we’re on the edge of technology using the latest tools. As a team, we belong in the Learning Team group that we learn from each other constantly every day.</p><p>It’s about time to make our products, and test our strengths and weaknesses.</p><p>We will. Soon. Stay tuned in our Pub. Let’s have some …beer now.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd263399b1ea" width="1" height="1" alt=""><hr><p><a href="https://medium.com/monospace-pub/what-we-do-and-how-in-monospace-labs-dd263399b1ea">What we do and how in Monospace Labs</a> was originally published in <a href="https://medium.com/monospace-pub">Monospace Pub</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>