<?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 SoftServe on Medium]]></title>
        <description><![CDATA[Stories by SoftServe on Medium]]></description>
        <link>https://medium.com/@softserve-tech?source=rss-3fa9e021b6ba------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*56m1ZB_sm0542dsdWv_LrQ.png</url>
            <title>Stories by SoftServe on Medium</title>
            <link>https://medium.com/@softserve-tech?source=rss-3fa9e021b6ba------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 00:57:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@softserve-tech/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[MLOps in Plain Words]]></title>
            <link>https://medium.com/inside-the-tech-by-softserve/mlops-in-plain-words-9b118bba3d13?source=rss-3fa9e021b6ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b118bba3d13</guid>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[mlops]]></category>
            <category><![CDATA[data-science]]></category>
            <dc:creator><![CDATA[SoftServe]]></dc:creator>
            <pubDate>Thu, 10 Jun 2021 12:25:20 GMT</pubDate>
            <atom:updated>2021-06-10T12:25:20.799Z</atom:updated>
            <content:encoded><![CDATA[<p>What is MLOps? Is it here to stay or just another trend to fade away? How has it changed the way ML projects are done?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*nCMtH_aVrGYiwCMNeinE2w.png" /></figure><p>SoftServe launched MLOps practice about two years ago as a reasonable response to the very same challenges, Data Scientists have been experiencing over and over while implementing different projects.</p><p>So far so good. So, in this article Volodymyr Solskyy, leader of MLOps practice, demonstrates why this new Ops is so to the point.</p><h3>To start with, let’s take a look at the recent role of Machine Learning</h3><p>Growing complexity of modern-day tasks has been exposing limitations of traditional Software Engineering for quite a while now, forcing us to search for new approaches. Machine Learning has already proven to be one of the best candidates for the job so far, with its ability to scale to the complexity without requiring extensive domain experience from ML engineers. This leads to some people naming ML as new Software Engineering or Software 2.0.</p><p>Sounds promising, yet it’s too early to state that we’ve got a silver bullet. <strong>Why?</strong></p><p>To answer this question, we need to look holistically at the whole process of applying ML to meet particular objective or to address a problem.</p><p>There is misperception that Machine Learning is all about model training and tuning. Well, not really, in fact it’s just a small piece of a larger puzzle. To deliver value from Machine Learning <strong>multiple steps must be taken</strong>, generally grouped in two phases:</p><ol><li>Model development — starts with data ingestion, then data analysis, feature crafting and model creation.</li><li>Model serving — is needed to make your model useful. It involves ingesting new, previously unseen data that needs to be validated against your existing model pipelines.</li></ol><p>While we managed to harness the first phase, the second one remains <strong>a major challenge</strong>.</p><p>According to Gartner survey, in 2018 <strong>only 47% of all AI/ML projects made it fully to production</strong>. In 2020, this figure grew by 8%. Pretty slow progress, right? The root of the problem lies in difficulties with integrating ML model into real environment.</p><blockquote>McKinsey: The inability to integrate analytic solutions into workflows and achieve frontline adoption is the number one inhibitor to why data and analytics initiatives fail.</blockquote><p>What makes bringing AI/ML solution to production such a tall order?</p><p>Out of numerous factors we can distinguish three central ones:</p><ul><li><strong>Insufficient data quality</strong></li></ul><p>ML is a completely data centric paradigm. Getting enough data seems to be a no-brainer as we have numerous sources of information and millions of data points generated daily. The key issue is quality of this data from both business and technical perspective.</p><ul><li><strong>Rapid growth of complexity</strong></li></ul><p>As the industry matures, complexity of tasks for us to solve grows exponentially. ML by nature will scale to everything we are going to throw at it, but we are still left to manage the complexity. Therefore, we generate more and more experiments involving more and more data, which requires more computational power, GPUs, FPGs, etc. Consequently, we bury ourselves in the sheer ramification of infrastructure, code and processes required to deliver value.</p><ul><li><strong>Unclear success criteria</strong></li></ul><p>Traditional Software Engineering heavily relies on functional specifications and requirements, making evaluation of progress and results relatively straightforward task.</p><p>In ML, we operate “proxy” functions and metrics. This also gets the job done. But the way how we get there is different, quite often making it quite hard to reconcile business objectives with obtained results. Also, reaching good numbers for objective functions does not necessarily transforms into success from business standpoint (look no further than Netflix challenge, for example).</p><p><strong>How can we do better?</strong> Before addressing this question, let`s clarify what this “better” stands for.</p><h3>Measuring progress in bringing ML solutions to production</h3><p>To be able to quantify progress of any effort, we need some set of objective metrics for it, and ML in production is not an exception.</p><p>Over the years of accumulating experience, our team has arrived at 4 major categories that cover most of the process, specifically KPIs related to:</p><p><strong>ML:</strong></p><ul><li>Implementation time</li><li>Time to deploy</li><li>Model performance</li><li>Business impact</li><li>Number of model calls (i.e. relevancy or popularity)</li><li>Average call duration</li></ul><p><strong>Data dependencies:</strong></p><ul><li>Time to access</li><li>Data ingestion time</li><li>Number of data issues</li></ul><p><strong>Infrastructure:</strong></p><ul><li>Resource provision time</li><li>Auditability</li><li>Chargeback and showback reports</li></ul><p><strong>Operations:</strong></p><ul><li>Number of models in production</li><li>Number of new models deployed</li><li>Model versioning</li><li>Number of calls and errors</li><li>Hardware utilization</li></ul><p>Over the years of experiments, industry worked out what can be considered <strong>an ideal ML project lifecycle</strong>.</p><p>It starts with framing your business idea or need — doing sanity check whether that idea is feasible at all — going over the rapid cycle of modelling iterations until good model is created — proceeding to production phase (to have everything deployed) — measuring the impact to understand if the initial objectives are met. The result of such analysis is an input to any next large iteration of the project.</p><p>Here is an extensive scheme of this process:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*-S-rK5_qeBlFK8cVAT9lpg.png" /></figure><p>Can we expect a typical Data Science team to deliver this cycle end-to-end? Well, experience so far has shown us that no. And here’s why.</p><h3>The brutal reality of developing ML project without MLOps</h3><p>At average, ML teams are built around the idea that desirable outcome of their work is either a model, or a nice, ad-hoc research report.</p><p>Hence, the primary focus is on stuffing those teams mostly with Data Scientists that are extremely well versed in research, mathematics, and data analysis, but usually less knowledgeable/experienced in engineering topics like scaling, automation, code optimizations, etc. In theory those parts can always be covered by Software Engineers, but <strong>this is precisely where things start to break</strong>, since both sides usually work at different velocities using different (often conflicting) approaches, different set of tools, and, in general, speak different languages. This leads to missed deadlines, poor overall quality, and teams being completely frustrated with each other. All together it causes huge losses for business.</p><p>Now, deploying ML to production is challenging stage, yet it is <strong>not the end of the journey</strong>. Congrats for making it this far and welcome to a new exciting world of operating ML-based systems in production. Your data sets will drift, and models will degrade; you will encounter biases, privacy and compliance issues, deal with latencies, throughputs, and general infrastructure instabilities, debug complex problems, and scratch your head over reproducibility issues.</p><p>This brutal reality can quickly and easily overwhelm unprepared teams, leading to countless overtimes, wasted budgets, and frustrated stakeholders effectively spelling doom for another ML initiative.</p><p>However, the journey does not necessarily need to end like this…</p><h3>Ingredients of successful ML project</h3><p>As we briefly touched upon already, successful ML project requires at least the following set of skills:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*BF87AmpIJxOtyg0A8CWLZA.png" /></figure><p>In a nutshell:</p><ul><li>Data Scientists doing all that stuff around model training.</li><li>Data engineers doing lots of heavy lifting with the data.</li><li>DevOps engineers supporting the environment.</li><li>Software Engineers implementing integration with the upstream and downstream systems.</li></ul><p>But as we have also shown in previous section, having experts to cover each of those skills wouldn’t do any good.</p><p><strong>This is where MLOps comes into play.</strong></p><h3>The essence of MLOps</h3><p>Just like others in Ops family, MLOps is not a particular profession or role. Instead, it’s a form of a contract, a set of practices aimed at enabling Data Scientists and Subject Matter Experts to deliver their work faster and in more robust and scalable way.</p><p><strong>The pillars of MLOps contract, among others, include:</strong></p><ul><li>Shared responsibilities and trust.</li><li>Self-service APIs and services.</li><li>Reusable code templates and playbooks.</li><li>Coding conventions and style guides.</li><li>Support for ML toolkit and frameworks.</li><li>Unified environments and images.</li><li>Unified data access and operations.</li><li>CI/CD and SDLC guidelines.</li></ul><p><strong>Applied properly, this contract will:</strong></p><ul><li>Establish tight collaboration between researchers and engineers.</li><li>Minimize code refactoring and rewrite between research and production.</li><li>Establish iterative, rapid, and high-quality ML model delivery lifecycle.</li><li>Ensure MLOPs practices are shared among the stakeholders.</li></ul><p><strong>What does this seamless collaboration bring? Ability to deliver ML models to clients or business users faster and more efficiently.</strong></p><h3>What changes does it introduce to our work routine?</h3><p><strong>Centralized ML data management</strong></p><p>If there’s one single improvement that should be considered for every AI project, it’s this one — data unification for model development and serving.</p><p><strong>Key idea:</strong> ML requires data that is properly consolidated (preferably into a single source), QCed, and automated.</p><p>Quite often, the project involves multiple data sources such as streams, data lakes and databases, object stores, and manual annotations. This complex landscape is the exact reason why a Data Scientist spends 80% of their time searching for relevant data and doing data munging. This is also source of too many surprises in production while the model is live and serving users.</p><p>The solution to this problem is <strong>Feature Store</strong> — a central vault for storing curated, well documented, tightly controlled features that can be used for training and serving across multiple models. Essentially, feature store is data warehouse for ML. Having one helps Data Scientists to quickly search and reuse available features, avoid duplication, ensure that features are always up to date and there’s no discrepancy between data used for training and serving.</p><p><strong>Versioning</strong></p><p>While in traditional Software Engineering the end result primarily depends on the code written by developers, the situation is much more complex for ML-based systems. Since ML is purely data-centric approach, even slightest change in incoming data or data pipeline can and will lead to a different result. Also, as many algorithms are non-deterministic by nature, the results might heavily depend on initial values, hyperparameters used, etc.</p><p>As such, to ensure reproducibility, provenance, and ease hand-offs of models, it makes sense to version control:</p><ul><li>Training data: raw data snapshots.</li><li>Environments: images, libraries, dependencies.</li><li>Data Transformations: data pipelines and processing code.</li><li>Features: feature metadata and extraction code.</li><li>Models: model code, weights, hyperparameters, binaries.</li><li>Experiments: configuring, metrics, artifacts.</li></ul><p><strong>Modularity</strong></p><p>While it’s quite tempting (and actually practiced) to put everything into a single script or a notebook, such monoliths are hard to optimize, scale, and reuse. Instead, it’s way better to structure the code as a set of abstracted out, loosely coupled components with well-defined interfaces and join them in a form of a DAG or pipeline.</p><p>Applying this approach enables us to:</p><ul><li>Reuse single components in other pipelines.</li><li>Scale each component individually if needed.</li><li>Test, debug, and troubleshoot the code faster and easier.</li></ul><p>It also allows us to utilize full power of platforms such as Kubernetes/Kubeflow and Airflow.</p><p><strong>Building CI/CD pipelines for ML</strong></p><p>No matter how many improvements introduced, we won’t be able reap the benefits if we do things manually. In fact, the level of automation for the data, models, and code pipelines determines level of maturity for ML process. Let’s take a look at how the fully automated process might look like:</p><p>The process starts from data that is stored in central location — feature store.</p><p>From here Data Scientists begin model development on the data sample. They go through the regular cycle of experimentation, data validation, feature crafting, building models, etc. Here we encountered first major change — the output of Data Scientists work is not a model anymore, but the reproducible code that is committed to a source code repository.</p><p>Once the code is there, the operations team can orchestrate the deployment into staging/production environment, where fully automated pipelines will run all the steps on entire dataset, produce a model, and store it in model registry. All parameters and details of this process are to be recorded in metadata storage for later audit (if required). From model registry the model is deployed in semi- of fully-automated fashion via A/B testing or Challenger process. Once the model is in production, it will be closely monitored by the ops team along with its data pipelines to ensure system stability and all of the important findings will be fed back to development/training/deployment loop.</p><p>As you might have noticed already, this new process is faster, less prone to human error, and ensures proper separation of responsibilities between various roles.</p><h3>What does it bring us? The most essential benefits of MLOps</h3><p>Reproducibility &amp; Auditability:</p><ul><li>All artifacts can be tagged and audited.</li><li>Pipelines are reproducible and their results are verifiable.</li><li>Code drives deployments.</li></ul><p>Validation:</p><ul><li>Minimize bias and enable provenance.</li><li>Online/offline comparisons of model quality.</li><li>SWE best practices for quality control.</li></ul><p>Automation &amp; observability:</p><ul><li>Controlled rollout capabilities.</li><li>Live comparison for model performance: real vs. expected.</li><li>Feedback loop for model improvements and drift.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b118bba3d13" width="1" height="1" alt=""><hr><p><a href="https://medium.com/inside-the-tech-by-softserve/mlops-in-plain-words-9b118bba3d13">MLOps in Plain Words</a> was originally published in <a href="https://medium.com/inside-the-tech-by-softserve">Inside the Tech by SoftServe</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Guide to Successful Preparation for a Client Interview]]></title>
            <link>https://medium.com/inside-the-tech-by-softserve/guide-to-successful-preparation-for-a-client-interview-e068a4b7a94?source=rss-3fa9e021b6ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/e068a4b7a94</guid>
            <category><![CDATA[client-relationship]]></category>
            <category><![CDATA[customer-interview]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[clients]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[SoftServe]]></dc:creator>
            <pubDate>Fri, 12 Feb 2021 09:49:30 GMT</pubDate>
            <atom:updated>2021-03-26T09:45:49.233Z</atom:updated>
            <content:encoded><![CDATA[<p>Is a client interview your nightmare? Read this article to know how to prepare effectively and get a client to hire you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/934/1*95qszy0gcLYZ5E5aARTo0A.png" /></figure><p>Yevhen Behen, a competence expert at the Software Development Office of SoftServe, has passed dozens of client interviews and now helps engineers to succeed in this tricky yet important step. On top of that such preparation benefits clients as well, as they can get all the needed information about a specialist and decide if it`s a perfect fit for the position.</p><p>Below he outlines the most crucial aspects.</p><h3>How a client interview is different from a job interview?</h3><p>A job interview consists of two parts:</p><ul><li>formalized technical interview — checks your professional level and has pretty much the same structure for all engineers within one profile.</li><li>Project interview — checks if you meet the requirements of the project and the particular vacancy.</li></ul><p>A client interview is similar to the second one. Though it is different because the mentality of the foreign interviewer is different and the focus will be shifted towards the needs of the client, and not an employer. I`ll dwell upon why it`s important below.</p><h3>Two steps that are often missed while preparing for a client interview</h3><ol><li><strong>Prepare CV</strong></li></ol><p>Don`t underestimate the role of CV. Refusals often happen at this stage. Reasons are trivial:</p><ul><li>Grammar mistakes — it looks as if the person is irresponsible.</li><li>Poor stylistic design — it looks as if the person did not prepare for the interview properly and does not meet the level claimed.</li></ul><p>There are two versions of this document:</p><ul><li>The advanced version containing the entire professional history (CV) — start with your latest projects and describe them in detail. Place projects that started your career, or irrelevant to the client’s technology stack projects only with a general description at the end.</li><li>Shortened version (resume, or excerpt from CV) — the last few projects, or the most relevant to the client&#39;s needs.</li></ul><p>In the general summary and skills description, focus on matters that will present you as a specialist best suited for a particular project. The rest is not of interest to this particular client.</p><p>When describing projects, check the NDA compliance with previous clients and do not disclose their confidential information.</p><p><strong>2. Rehearse self-presentation</strong></p><p>Self-presentation is an opportunity to promote yourself. Please use it. But impromptu speech (especially in English) is a tricky thing. Believe me, investing time into preparation is beyond important.</p><p>Simply writing a text is not enough. I strongly recommend having several rehearsals and deliver your speech. If you don’t have a listener to give you feedback, try to practice in front of a mirror.</p><p>3 key points to check here:</p><ul><li>Duration of the speech</li><li>Sequence of facts</li><li>Logic of presentation</li></ul><p>While saying out loud the words you will understand what parts can be confusing or not present you in the best light.</p><p>Here is an example of a proper structure:</p><ul><li>Education (if you have a relevant one) because for Americans and Europeans it is important</li><li>A general summary of your experience (how many years in the profession, what technologies you work with, what projects you have performed on, what methodologies you have worked with)</li><li>Details on the last two or three projects (project ecosystem, team structure, responsibilities within the team, requirements) to make it clear that you have a helicopter view, and not just know your technical part</li><li>The logical ending (to make it clear that you have completed your story).</li></ul><h3>How interview goes?</h3><p>I distinguish three types of interviews:</p><ul><li><strong>An interviewer is a non-technical person</strong> — they will check your soft skills. Usually, a conversation is built around common topics, whereas technology is brought up on a very high level.</li><li><strong>Classic technical interview</strong> — the interviewers often want to know about your latest projects and ask a lot of questions from the profile (what frameworks you have worked with, what approaches you have used, your code quality, etc.).</li><li><strong>In-depth technical interview</strong> — in addition to (or instead of) technical questions, you will be asked to solve tasks. This is the most stressful option since you will code in front of the interviewers. Even experienced professionals can get confused because it is hard to work when you are watched by strangers and expected to get the result as soon as possible. When we prepare a colleague for this kind of interview, we model similar sessions and go through them several times (starting with clarifying questions for the task in English, and then perform the actual coding and presentation of the result).</li></ul><p>The best preparation here is to train and perform certain technical tasks while someone is watching you.</p><p>There are also <strong>homework interviews</strong>. In this case, the client sends a link to an assignment and an interviewee has from 24 to 48 hours to do it. In this case, you need to carefully analyze and code the solution that meets the basic attributes of code quality and is optimal for performance.</p><h3>What non-technical questions you can be asked?</h3><p>There is a pretty standard set of questions that interviewers ask most frequently. Something like:</p><ul><li><strong>What are your weaknesses?</strong></li></ul><p>Of course, there is no need to list them all.</p><p>I advise you to answer in such a way that presents your negative traits as a side effect of the positive ones.</p><p>Example: “I am meticulous and very attentive to details, so my weakness is that I sometimes need more time to perform tasks”. In the end, it may be advantageous, for example for a QC engineer in the medical field.</p><ul><li><strong>Share some examples of your failures (clients from America love this question)</strong></li></ul><p>It is perfectly normal to talk about it because failures happen to everyone. But you need to make it clear that you have drawn conclusions and know how to prevent a similar situation in the future.</p><h3>What to do if you don`t know the answer?</h3><p>If you cannot answer the question, <strong>do not say it directly</strong>. Instead, show your ability to find a way out of any situation, e.g. “I haven’t used this technology yet, but I know a similar one that performs this task. I assume that it has identical functionality, so I will be able to figure it out very quickly.”</p><p>Foreign clients expect a person to praise themselves and to show themselves in the best light. They will smile and not show that they are dissatisfied with the answer, little can be read on their faces. They ask more conceptual things — how do you see business, how do you develop (because they want to see a person within a broader competence).</p><p>Mentality difference:</p><ul><li><strong>Americans</strong> tend to ask how you feel about working on the weekends. Since it is their pace of life, they often demand it from the people they work with.</li><li><strong>Europeans</strong> may have a different understanding of life-work balance, and they usually do not ask about overtime.</li><li><strong>The British</strong> clients are always very polite, but even their conventional complex language structures can confuse a person.</li></ul><p>I strongly advise you to thoroughly study the information about the client, considering that questions like “What do you know about our company and why do you want to work with us?” occur quite often. It is essential for some clients that a person chose to work with them consciously.</p><h3>Is it ok to ask an interviewer questions?</h3><p>Not only it is ok, but it’s also can be extremely productive for both sides.</p><p>It shows your interest and gives you a bonus in the eyes of the interviewer.</p><p>In most cases, it`s better to do it at the end, after all topics of interest to the interviewer were covered. But it depends on the style of the interviewer though — there are people who are looking for a dialogue during the interview. Therefore, if you feel that the person is eager to talk, you can already start asking questions.</p><p>I`d recommend avoiding the following topics:</p><ul><li>religion</li><li>politics</li><li>sport (you cannot be certain what sport a person likes and which team he supports)</li><li>operational matters that will be decided with the project manager (for example, whether you will have an on-site trip to the client country or salary issues)</li><li>about the history of your company’s cooperation with the client. It is something the interviewer may not even know or be interested in.</li><li>some basics about the client, that are easy to google. E.g. client’s history, how many years the company has been working, etc. Stay focused on the project: what are the plans for further development of the project? What is the structure of the project team? How are the processes built?</li></ul><h3>Last but not least ….. proficiency in English</h3><p>It`s a must.</p><p>If you do not have regular speaking practice, it will be difficult for you to talk for an hour. Or if you use English most often at work, it can be difficult to talk about some general topics unrelated to technology.</p><p>Therefore, it is better to start <strong>preparing in advance</strong> and at least visit the language courses or conversation clubs a few times. When I prepare a colleague for a client interview, I also check how long a person can speak English fluently.</p><p>In conclusion, I strongly recommend that <strong>you prepare for the interview and start not a day or two earlier, but even more in advance</strong> to understand your gaps, so you have time to tackle them. The preparation benefits clients as well because they can get all the needed information about a specialist and make a better hiring decision.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e068a4b7a94" width="1" height="1" alt=""><hr><p><a href="https://medium.com/inside-the-tech-by-softserve/guide-to-successful-preparation-for-a-client-interview-e068a4b7a94">Guide to Successful Preparation for a Client Interview</a> was originally published in <a href="https://medium.com/inside-the-tech-by-softserve">Inside the Tech by SoftServe</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Tech Lead to Architect — Part 2: a key to successful Quality Attribute Workshop]]></title>
            <link>https://medium.com/inside-the-tech-by-softserve/from-tech-lead-to-architect-part-2-a-key-to-successful-quality-attribute-workshop-8c19f168118f?source=rss-3fa9e021b6ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c19f168118f</guid>
            <category><![CDATA[it-career]]></category>
            <category><![CDATA[technical-leadership]]></category>
            <category><![CDATA[tech-lead]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[it-consulting]]></category>
            <dc:creator><![CDATA[SoftServe]]></dc:creator>
            <pubDate>Tue, 08 Dec 2020 14:11:00 GMT</pubDate>
            <atom:updated>2020-12-08T14:11:00.624Z</atom:updated>
            <content:encoded><![CDATA[<h3>From Tech Lead to Architect — Part 2: a key to successful Quality Attribute Workshop</h3><p>Tips &amp; tricks on Quality Attribute Workshop: how to conduct, what to ask your clients, and how to handle unclear answers in order to get all the needed inputs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*uYfxN6e0z7o33zGQphBxyw.png" /></figure><p>Dmytro Ovcharenko, Senior Solutions Architect at SoftServe DevCenter in Dnipro, continues series of blog posts about basics of IT Consulting.</p><p><a href="https://medium.com/inside-the-tech-by-softserve/from-tech-lead-to-architect-part-1-it-consulting-process-38f131661af8">In my previous article</a> I walked you through IT consulting process. Now I`ll dwell upon one specific part of it — the Quality Attribute Workshop (QAW). I`ll shed light on what pitfalls you might come across here and my experience how to handle it.</p><h3>Why you need the Quality Attribute Workshop (QAW) and what stages it consists of?</h3><p><strong>What is QAW?</strong></p><p>In plain words it`s a meeting with stakeholders on the client side, that is conducted within Discovery or Pre-Sale session to agree on expectations from a future decision.</p><p><strong>Why is it needed?</strong></p><p>To determine non-functional requirements for a system.</p><p><strong>What if you skip or fail it?</strong></p><p>Expectations will remain at the “highly-available / highly-secure / highly-performed” level, where everyone understands this “highly” in their own way. As a result, your client may still have questions for a ready-made solution, but you will have nothing to appeal to.</p><p><strong>Why is QAW so tricky?</strong></p><p>Things are not always so straightforward and there can be difficulties — from the clients’ incomprehension of what they want to get, to political disputes between stakeholders, when everyone takes their stand and cannot reach a common solution. You have to work through this to get what you want from them anyway.</p><p><strong>QAW step-by-step</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kgaSyZmm4CKMLgwktsOArw.png" /><figcaption>The scheme of how QAW is organized</figcaption></figure><p><strong>Part 1</strong> — preparation within the team</p><p>We collect material for the future brainstorm:</p><ul><li>case studies to work out non-functional requirements</li><li>templates for scripts and architecture (if it is an assessment)</li><li>concerns, constraints, etc.</li></ul><p>Now, it takes me a few hours: an hour to prepare general scenarios without measurements and about an hour to detail and refine those scenarios with the team.</p><p><strong>Part 2</strong> — work with clients</p><p>We usually go to face-to-face meetings. Now, under quarantine and closed borders, we work online, but the principle remains the same.</p><p>I strongly recommend gathering all stakeholders on the client side before the main sessions for a short session (not more than half an hour for them not to get too bored) to explain what we will do and why.</p><p>Then you can proceed to the main part of the QAW, which consists of two stages:</p><ul><li>Brainstorming to generate scenarios</li><li>Scenario prioritization session</li></ul><p>That was a bit of theory, now let`s get down to real life.</p><h3>Hands-on advise to make the most out of QAW</h3><p><strong>Build the discussion around clients’ use cases</strong></p><p>The more specific you are while explaining your ideas the better.</p><p>Too generic explanation — “We plan to make system A that will respond to system B in a certain way; the data loss will not exceed 0.001%”</p><p>Much more clear and closer to the client`s reality explanation — “The user needs to log in to the system to be able to generate a report. This critical feature is always available (in 99.95% of cases), while the system chat can be turned off for a while, which is not critical.”</p><p>This is how we move script by script: we discuss, listen to what stakeholders think, and let everyone speak without criticizing.</p><p><strong>Agree on measurements</strong></p><p>Ask about clear indicators or ranges for each scenario. Be ready, that clients may not know what they want. Yet it`s crucial to get a precise answer to secure yourself.</p><p>I suggest taking a proactive position and advise something, referring to your experience or the world’s best practices. If that doesn’t work, you can go for small provocations. For example, you discuss the latency of a SaaS healthcare solution. The client does not know what it should be. Try to offer 10 seconds — it will make them think faster and offer better options. And eventually you`ll agree on some compromise number.</p><p>Use this approach to go through all your scenarios.</p><p><strong>Remember prioritization</strong></p><p>If prioritization is not worked through, all previous steps will lose their meaning because architecture is built on the understanding of priorities. For example, if the most important quality of the system is security, then we are likely to lose performance. Such things need to be considered and clarified right away.</p><p>Stakeholders on the client side can start disputes, as everyone loves to fiercely defend their interests.</p><p>What helps me in such situations is giving each participant a certain number of points to distribute between the scenarios. This method clearly shows what prevails.</p><p><strong>Track time</strong></p><p>Determine in advance the needed time to discuss each topic, state it in the meeting agenda, and adhere to this timing to go through all the mentioned steps and find out what is truly essential.</p><p>If stakeholders have an hour for everything, we can briefly run through the main points that will help understand the complexity of future infrastructure, deployment, and the general course of the client’s thoughts. It’s important to clarify the security and performance requirements of a system. Depending on the context, there may also be other requirements, such as sustainability or usability (for web application).</p><p>Here, we clearly will have no time to go script after script, so I prepare a quality attribute script in advance, leave the question on the measurements so that we brainstorm specifically them, and not the scripts. Of course, even in this case, there may not be enough time to discuss everything. So, define the most important points for yourself, clarify them at first, and agree to finish the rest in correspondence.</p><p><strong>As a result of all the steps described above, we form a Utility Tree</strong></p><p>The name is not obvious, but it is a table where we describe all our scenarios and define for each of them the level of Importance and Complexity. Risks, assumptions, etc. can also be described there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eoIEBSSfZPBgf5gt1BubcQ.png" /></figure><p>Medium and High priorities are key for us. We will build a design and achieve measurements primarily for these scenarios. The combination of L-H indicates a problem, that we always try to investigate and take into account at the design stage.</p><p><strong>QA Scenario refinement</strong></p><p>The last step, when we refine the requirements, their content, and bring clarity. If you have more questions, it is better to ask for another session to find out everything before the work starts.</p><p>Here is an example of a detailed scenario description. I usually do a shorter version.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/858/1*_DMRUZ53_yWg_fDN1Qx2EQ.png" /></figure><p>In most cases, we send this document to all stakeholders and ask for confirmation. I remember only one case when we had to continue the discussion for about two more hours struggling with prioritization.</p><h3>How to distribute team roles for QAW?</h3><p>As you can see, QAW is a rather complex process that requires a lot of consideration: from the proper organization of work with stakeholders to finding out all necessary technical details.</p><p>To make your work more convenient, I advise to clearly outline the roles.</p><p><strong>Facilitator</strong> moderates discussions:</p><ul><li>communicates with the client</li><li>holds attention of an audience</li><li>clearly follows an agenda</li><li>resolves controversies during any conversation</li><li>conducts small talks and maintain a friendly atmosphere (it`s important!)</li></ul><p>Business Analyst is an excellent fit for this task.</p><p><strong>Question-keeper:</strong></p><ul><li>asks questions on the technical part, risks, and other relevant topics</li><li>helps the facilitator to direct the conversation in the right direction.</li></ul><p>It is an expert in a particular technology.</p><p><strong>Scrubber</strong> writes down everything that is voiced during the discussions: requirements, risks, assumptions.</p><p>Based on these records, non-functional requirements will be further elaborated, so this role is very important.</p><p>Project Manager can handle this role perfectly, if a team has one. I am often a scrubber myself. In this role, I ask additional questions and watch the reaction of stakeholders, which is very useful.</p><p><strong>What recording tools to use?</strong></p><p>MS Teams + SharePoint is a nice option.</p><p>Files and tasks are stored in one place, and it is convenient to share materials and build team interaction.</p><p>Business Analysts often use XMind.</p><p>I also have a Word template that I can easily fill out.</p><p>But be careful with using a board: it ends quickly, you need to write legibly, take pictures of all records, and then transfer them to electronic form.</p><p><strong>Some useful sources:</strong><br><a href="http://resources.sei.cmu.edu/%E2%80%A6%E2%80%8Bt-view.cfm?assetid=474329">Quality Attribute Workshop Collection</a><br><a href="http://resources.sei.cmu.edu/%E2%80%A6%E2%80%8Bt/2018_010_001_513488.pdf">How to Clarify Architectural Requirements to Ensure Successful Development</a> <br><a href="http://kilthub.cmu.edu/%E2%80%A6%E2%80%8B582656/files/12069557.pdf">Guide on QAW by Carnegie Mellon Software Engineering Institute</a></p><p>Feel like this is something you`d like to try? <a href="https://hubs.ly/H0CbXcK0">Don`t hesitate</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c19f168118f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/inside-the-tech-by-softserve/from-tech-lead-to-architect-part-2-a-key-to-successful-quality-attribute-workshop-8c19f168118f">From Tech Lead to Architect — Part 2: a key to successful Quality Attribute Workshop</a> was originally published in <a href="https://medium.com/inside-the-tech-by-softserve">Inside the Tech by SoftServe</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How i migrated a legacy banking application to Amazon EKS step-by-step]]></title>
            <link>https://medium.com/inside-the-tech-by-softserve/how-i-migrated-a-legacy-banking-application-to-amazon-eks-step-by-step-d9ce568d781?source=rss-3fa9e021b6ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9ce568d781</guid>
            <category><![CDATA[amazon-eks]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-migration]]></category>
            <dc:creator><![CDATA[SoftServe]]></dc:creator>
            <pubDate>Wed, 25 Nov 2020 12:01:58 GMT</pubDate>
            <atom:updated>2020-11-27T08:26:21.853Z</atom:updated>
            <content:encoded><![CDATA[<h3>How we migrated a legacy banking application to Amazon EKS step-by-step</h3><p>Banking legacy app, hosted in on-prem datacenter, with high maintenance cost, long Time To Market, poor 20-year-old UX and no Agility. Client wants an upgraded Amazon EKS-based solution. Here`s a step-by-step guideline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*lyHvZOyyEvdIv9fQs7u42A.png" /></figure><p>I am Oleksandr Vorobiov, DevOps Engineer at SoftServe Development Center in Kharkiv. For the last three years I have mostly been working with Amazon Cloud (apps migration, optimization, and re-architecture). The project, I`m writing about, is one of the most challenging and interesting so far.</p><h3>Resolution plan</h3><p>Along with re-platforming, we took four additional approaches:</p><ul><li><strong>Infrastructure as a Code (IaaC)</strong> to easily process all the needed resources.</li><li><strong>Helmfile deployment</strong> to orchestrate deployment of the components in Kubernetes.</li><li><strong>CI/CD</strong> to automate the whole process of the migration.</li><li><strong>GitFlow</strong> to develop microservices.</li></ul><h3>Preparation</h3><p>Prior to the migration development team:</p><ol><li>Broke down legacy code to small chunks by converting the source code to Java and C++ and added additional features.</li><li>Wrapped the app into Docker containers.</li><li>Designed a brand new architecture for our app as shown in the diagram.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6DCoKmIloiZ7NBcEEQZFEQ.jpeg" /><figcaption><em>In-cloud app architecture</em></figcaption></figure><p>To AWS Cloud we deployed VPC with three subnets in it. Each subnet contains pre-deployed services:</p><ul><li>Amazon EKS.</li><li>Aurora databases, those numbers vary depending on the environment.</li><li>Kafka services, provided by Amazon.</li><li>Elasticsearch with basic components set.</li></ul><p>4. Used <em>nested stacks</em> to easily update and make changes to the product. Each nested stack is represented by a .yaml file that leverages a separate set of AWS services. This approach lets us make changes to different parts of infrastructure without any disruptions to the whole product.</p><p>5. Used <em>Cloud Formation Custom Resources</em> which essentially are Python scripts, wrapped into AWS Lambda. Custom Resources are used to make custom configuration to some services in case it is not supported by CloudFormation, such as Kafka.</p><h3>Migration overview</h3><p>The most obvious solution, when it comes to leveraging microservices in Kubernetes, would be using Helm charts. Indeed, we can use Jenkins to compile Helm charts and pack Docker images with executable code into them. Additionally, Helm charts allow customizing parameters for different environments, such as Production, Staging, or Test.</p><p><em>But…the issue is Helm charts don’t allow you to define deployment dependencies between the microservices.</em></p><p>We can use umbrella helm chart but still it doesn’t provide required level of configuration and dependency management.</p><p>And the solution was…</p><p><strong>Helmfile</strong></p><p>Think of it as of the Helm for your Helm. You practically wrap your Helm charts into Helmfile. With this, you can easily manage environments using parameters in values files and, most importantly, seamlessly define dependencies between your Helm charts.</p><p>The structure of Helmfile is as easy as pie.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*I2b4Vs6bhnXeu6QNYtZZ7Q.png" /><figcaption><em>Snapshot of Helmfile</em></figcaption></figure><p>From top to bottom you:</p><ol><li>Specify your environments’ info.</li><li>Register internal Helm chart’s repository, hosted in Artifactory.</li><li>Describe releases.</li></ol><p>Overall, Helmfile is the best idea when it comes to deployment of the (micro)services on different environments using different parameters set.</p><p><strong>Helmfile features</strong></p><p>Separately, I would like to highlight the major features of Helmfile:</p><ul><li>12-factor style configurations.</li><li>Inline values.yaml.</li><li>CI/CD integration.</li><li>Environments synchronization.</li><li>Go templating.</li></ul><p><strong>CI/CD pipeline</strong></p><p>For the microservices development, we followed <strong>GitFlow</strong> approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*VjhYzy_toiPSYss5bIkigA.png" /><figcaption><em>GitFlow approach</em></figcaption></figure><p>In this case, we have at least four branches:</p><ul><li><strong>Master</strong> with release tags of the app.</li><li><strong>Release </strong>(not in the picture) for preparing releases</li><li><strong>Develop</strong> where changes to the code were being made.</li><li><strong>Feature</strong> — derivative to Develop. For each new product feature development, we were creating a separate branch.</li></ul><p>For Helmfile — so it automatically establishes deployment dependencies — we followed <strong>GitOps</strong> approach. It states that the infrastructure state represented in Infrastructure Git repo should represent actual state of running environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*Ky-mPawwLgn9i0pCJoKtvw.png" /><figcaption><em>Sync workflow between cloud and Git</em></figcaption></figure><p>Briefly, the synchronization works as follows:</p><ol><li>Developer makes a change to a microservice and tests it.</li><li>A microservice undergoes testing on CI stage.</li><li>Jenkins compiles Helm chart and Docker image for this microservice, and tags a new version.</li><li>Jenkins updates the version of the corresponding microservice in a infrastructure Git repo, for a specified environment.</li><li>Automatically-triggered CD job applies the initial change in a corresponding environment.</li></ol><p>As you can see, no manual efforts are needed to make changes to environment. Also, to find out which versions of services are running in specific environment, you can simply check your Git repo.</p><p><strong>Local pipeline</strong></p><p>For microservices packaging, we used Minikube to simulate whole or at least part of real environment in Kubernetes. To orchestrate process locally we use Gradle, created a Gradle file and described necessary logic.</p><p>Gradle file runs automatically upon testing of some change. The script compiles Docker image from a Git repo, installs minikube, and starts Kubernetes cluster if missing. When a Kubernetes cluster is up and running, simply a new version of updated microservice is installed. Minikube here validates if local changes were executed successfully.</p><p>Additionally, in a repo we have Helmfile that describes only that part of the infrastructure that is needed to run tests for that specific microservice.</p><h3>Secrets management</h3><p>To build communication between the app and secrets, we used <strong>Kubernetes External Secret Controller</strong>. This solution is also installed from Helmfile.</p><p>Inside a Kubernetes cluster, Kubernetes External Secret Controller creates Custom Resource. This Custom Resource has API to fetch secrets from Secrets management (SSM component in Amazon) to the needed namespaces.</p><p>To summarize, Kubernetes External Secret Controller enables automatic movement of the secrets to the new namespaces upon their creation. As easy as that…</p><h3>Service mesh for secure communication</h3><p>Luckily, the days when <strong>Istio</strong> was a novelty have passed. This allows me to focus on the peculiarities of this solution’s adaptation to our needs. The major areas that service mesh solved in our case were:</p><ul><li>Secure communication between microservices.</li><li>gRPC-based communication between microservices.</li><li>gRPC load balancing.</li><li>Istio serves our case best due to its following features:</li><li>Provision of endpoints for user’s communication with the services via the product’s UI. Istio routs requests, made on the UI, to the app’s components.</li><li>Possibility to set up mutual TLS between the services. Traffic between the services is encrypted.</li><li>Balancing of the gRPC protocol between the services.</li></ul><h3>Logging and monitoring</h3><p>Of course, we set up logging and monitoring.</p><p><strong>Infrastructure logging</strong></p><p>To collect logs from the services (Amazon Aurora, Kafka, and others), which already are leveraged in the cloud, we employed <strong>Kibana</strong>. For convenient collection of the logs, we used <strong>AWS Lambda</strong>. Obviously, we configured it slightly to make each component get into Kibana’s needed index.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nyw5Wz2-yJzwrYmt5GpAxg.png" /><figcaption><em>Infrastructure logging workflow</em></figcaption></figure><p><strong>Infrastructure monitoring</strong></p><p>All the metrics are reported to<strong> Amazon CloudWatch</strong>. Then <strong>Grafana</strong> fetches data from it and stores metrics in an appropriate format for the user’s convenient access.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XXyCnzT7Ce_b_bBtymcaLQ.png" /><figcaption><em>Infrastructure monitoring workflow</em></figcaption></figure><p><strong>Microservices logging</strong></p><p>To collect logs from the microservices, we deployed <strong>Fluentd</strong> to every Amazon EKS worker node. Inside every node, microservices write logs to a Fluentd daemon. To properly retranslate logs from the microservices, which are written in Java and C++, every daemon has a pre-configured parser. Eventually, Fluentd writes logs to appropriate Elasticsearch indexes that visualize data in Kibana.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tSphRXrYJcxeS5RgVv8J8g.png" /><figcaption><em>Microservices logging workflow</em></figcaption></figure><p><strong>Microservices monitoring</strong></p><p>We implemented microservices monitoring using Prometheus. It collects all metrics from the microservices and puts data into Grafana dashboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*pN8w3OFErgnrr0MQEOTTNw.png" /><figcaption><em>Microservices monitoring workflow</em></figcaption></figure><h3>Improvement areas</h3><p>Our current top-priority is setting up autoscaling, which is planned to be implemented using the two solutions:</p><ul><li><strong>Horizontal Pod Autoscaler</strong> for pods scaling in a Kubernetes cluster. Based on custom metrics of our services, it scales pods based on their load.</li><li><strong>Cluster Autoscaler</strong>, provided by Amazon, for worker nodes’ scaling.</li></ul><p>To sum up, migration to cloud is an extremely beneficial idea when it comes to effortless app updating and maintenance. Even for big enterprise, market offers abundance of solutions to make this process easy and risk-free. In our case, Helmfile was what provides flexibility to the team and automation for the product.</p><p>Feel free <a href="https://hubs.ly/H0BxlZx0">to check out open positions in our team</a> if such complex projects for leading enterprises is something you`re interested in.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9ce568d781" width="1" height="1" alt=""><hr><p><a href="https://medium.com/inside-the-tech-by-softserve/how-i-migrated-a-legacy-banking-application-to-amazon-eks-step-by-step-d9ce568d781">How i migrated a legacy banking application to Amazon EKS step-by-step</a> was originally published in <a href="https://medium.com/inside-the-tech-by-softserve">Inside the Tech by SoftServe</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Anthos: how it has changed DevOps]]></title>
            <link>https://medium.com/inside-the-tech-by-softserve/google-anthos-how-it-has-changed-devops-60d10968a645?source=rss-3fa9e021b6ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/60d10968a645</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[google-anthos]]></category>
            <category><![CDATA[cloud-architecture]]></category>
            <category><![CDATA[devops-tool]]></category>
            <dc:creator><![CDATA[SoftServe]]></dc:creator>
            <pubDate>Wed, 18 Nov 2020 13:41:29 GMT</pubDate>
            <atom:updated>2020-11-18T14:40:26.184Z</atom:updated>
            <content:encoded><![CDATA[<p>Google Anthos is a game-changing platform for DevOps. Here`s why.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*uje9nadTo5xHitisaFkH7g.png" /></figure><p>Max Kozinenko, Solutions Architect at SoftServe, embraced Google Anthos as an experiment right after it was released in spring 2019. Now, 1,5 years later, he`s Google Anthos Cluster Lead. Having implemented 5 projects together with the team of engineers from SoftServe Development Centers from Kharkiv, Kyiv and Lviv, he`s sure that this technology is a breakthrough.</p><p>Here are Max`s thoughts on that.</p><h3>Few words on what Anthos is and what pet peeves it eliminates for enterprises?</h3><p>Managing all existing infrastructure environments may be quite a nightmare for a company, especially enterprise, with no easy solution how to get from point A to point B. Often this path is long, expensive and impeding overall business growth.</p><p>Anthos is an ecosystem, that provides the solution.</p><p>It gives a full control over a company`s infrastructure. Its every object is treated as a Kubernetes object and managed using the GitOps workflow.</p><p>These are the crucial advantages, why companies will eventually go for Anthos:</p><ul><li>Allows managing different environments: AWS, GCP, on-premises,</li><li>Gives a full control over the whole infrastructure,</li><li>Enables changing environment configuration quicker and easier.</li></ul><p>But it`s not only a client who wins.</p><h3>Wins for engineers. How Anthos makes DevOps` lives easier?</h3><p>It`s a DevOps nightmare to containerize some complex setup, as it`s too time- and efforts-consuming</p><p>Here is how Migration for Anthos (M4A) can be integrated into current CI/CD pipeline:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*9eezfffPVM-0Blo-87ARng.png" /></figure><p>Much simpler, right?</p><p>The result won`t be the ideally looking containerized application like after replatforming, yet workflow will be containerized.</p><p>It comes in handy when you are expected to do a quick lift&amp;shift. This time saving allows to have ROI increased. Then you`ll able to invest time and money into optimization.</p><p>That`s the main use case where M4A is applicable.</p><p><strong>Workloads, currently supported by M4A</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*XMY-91Hg5HWTJTBnPfto-g.png" /></figure><p>As for Windows apps, keep in mind, that it produces Windows containers, that can`t be added to a Service Mesh. So, it`s very tricky to set up a Service Mesh between a standard Linux and Windows containers as you`ll spend a lot of time on designing how they should communicate via the Istio Ingress. On top of that, you won`t be able to utilize all the Service Mesh features in Windows Containers.</p><p>But for LAMP, WordPress, Java-based apps this approach gives a huge advantage.</p><p><strong>Opportunity to control all the workloads from a single place</strong></p><p>Here is how it looks:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*S3_sZenuF4rqngvUF_nBXA.png" /></figure><p>This is a GKE cluster hub, that unites all your workloads and gives a single point of view on all the clusters, registered here. It`s not only about Google Cloud projects, but on-premise and AWS as well (Azure will be added in the immediate future).</p><p>Here you can:</p><ul><li>track everything (issues, warnings, alertings etc.) easily in a centralized way,</li><li>manage all the Anthos features like configuration management, Service Mesh,</li><li>use Ingress for Anthos or Multicluster services.</li></ul><p><strong>Load balancing</strong></p><p>Ingress for Anthos utilizes the Google Network backbone to do the intelligent drawing of the inbound traffic.</p><p>As you can see on the scheme below, Ingress utilizes Google Front-end. It gets a Google request from a specific area to a single virtual IP and then this request is routed to the closest Google Front-end and gets routed to the closest cluster in terms of latency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zVweFnhidmyRhj5LoA2H4Q.png" /></figure><p><strong>The most convenient integration with other cloud environments</strong></p><p>As I`ve mentioned above, Anthos is integrated with AWS. It means that we get here the GKE experience with the operability, manageability etc.</p><p>There are other similar tools like Kops, AKS or simply Kubernetes on AWS to eliminate the complexity aspects.</p><p>Here are 6 key factors why Anthos gives a better experience:</p><ul><li>Turn-key, production-grade, conformant Kubernetes with best-practice configuration,</li><li>Easy upgrade path to the latest Kubernetes releases that have been validated and supported by Google,</li><li>Get started quickly: use the GCP Cloud Console as the single pane of glass to create and view your workloads,</li><li>GitOps-style day 2 management for all your Anthos clusters with familiar tooling,</li><li>Integrated with ACM, ASM, Cloud Run, Cloud Logging &amp; Monitoring and marketplace solutions,</li><li>Available and reliable: highly available control plane and node pools with support for auto-scaling.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60d10968a645" width="1" height="1" alt=""><hr><p><a href="https://medium.com/inside-the-tech-by-softserve/google-anthos-how-it-has-changed-devops-60d10968a645">Google Anthos: how it has changed DevOps</a> was originally published in <a href="https://medium.com/inside-the-tech-by-softserve">Inside the Tech by SoftServe</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Overview of eHealth Courses for ML engineers]]></title>
            <link>https://medium.com/inside-the-tech-by-softserve/overview-of-ehealth-courses-for-ml-engineers-6163144c2a15?source=rss-3fa9e021b6ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/6163144c2a15</guid>
            <category><![CDATA[ehealth]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[course]]></category>
            <category><![CDATA[coursera]]></category>
            <dc:creator><![CDATA[SoftServe]]></dc:creator>
            <pubDate>Fri, 13 Nov 2020 12:29:47 GMT</pubDate>
            <atom:updated>2020-11-13T12:29:47.565Z</atom:updated>
            <content:encoded><![CDATA[<p>ML engineer passed majority of Coursera eHealth courses. Here`s his review and recommendations</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*OwN7S35DRgej6G-lxHHVnQ.png" /></figure><p>Electronic healthcare is a growing domain in data science and machine learning. Many courses are being created for engineers to enter this field. But which are the ones worth investing our time and money?</p><p>Figuring this out was Borys Kabakov`s (Senior ML Engineer) first assignment during approbation period at SoftServe. He had to pass a bunch of eHealthcare courses to check which one could be useful for our team.</p><p>In this article, Borys shares his experience.</p><p>Since I hold the MD, Ph.D. degrees and work as ML Engineer in the Healthcare team, my expertise was helpful on this matter.</p><p>I passed all of the provided courses and wrote an inner report. It was almost a year ago. After that, new courses kept coming and I continued taking them as a part of my individual development plan.</p><p>Time has passed, the original report became outdated, and the company decided to create a blog on the Medium platform. At this point, I was asked to update the old review and write a blog article to share our vision of the best learning path for DS/ML in Healthcare. And this is what you are reading now. :)</p><p>All the reviewed courses are in English and stored on the Coursera platform due to the features of our learning programs.<br> It is assumed that a hypothetical student already has some basic knowledge in ML/DS, and their aim is to get specifically into eHealth domain nuances. Or, at least, I propose to obtain this prerequisite knowledge by taking additional courses that would be more efficient.</p><p>In this article, I’m not covering bioinformatics since it requires a separate discussion.</p><p>And of course, I would appreciate your thoughts and feedback, so do not hesitate to share your favorite eHealthcare courses in the comments.</p><h3>Short review of all the courses, I`ve passed</h3><p><strong>Disclaimer</strong></p><p>A lot of the discussed courses include peer-review tasks, which is inconvenient because one can spend a lot of time simply waiting for another student to provide a review. And as long as it is not clear what score threshold is and in which mood a reviewer happens to be, there are good chances to go for a second or third round of peer-reviewing.</p><p>All discussed courses (except “AI in medicine”) are basically for everyone. No programming skills or any other background are needed. For “AI for Medicine”, you’ll need some basic ML knowledge and Python skills.</p><p><a href="https://www.coursera.org/learn/clinical-data-models-and-data-quality-assessments?"><strong>Clinical Data Science Specialization by the University of Colorado</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*kC2SoPFubp2v00Laz0edlg.png" /></figure><ol><li><a href="https://www.coursera.org/learn/introduction-clinical-data-science">Introduction to Clinical Data Science</a></li><li><a href="https://www.coursera.org/learn/clinical-data-models-and-data-quality-assessments">Clinical Data Models and Data Quality Assessments</a></li><li><a href="https://www.coursera.org/learn/computational-phenotyping">Identifying Patient Populations</a></li><li><a href="https://www.coursera.org/learn/clinical-natural-language-processing">Clinical Natural Language Processing</a></li><li>Predictive Modeling and Transforming Clinical Practice — cancelled</li><li>Advanced Clinical Data Science — cancelled</li></ol><p>It started as a specialization but later, they cancelled two last courses.</p><p>There are some bloopers in the course videos that no one bothered to reshoot and some bugs as well (like the absence of the final quiz dataset).</p><p>Students must complete tasks that should be done in SQL, R, and use custom Java-based software (which produces XLSX file as output). Answers must be submitted as PPTX file (sic!) to be peer-reviewed.</p><p>Due to the peer-review and the lack of students in the course it could be hard for one to meet deadlines.</p><p><strong>Pros:</strong></p><ul><li>Clinical Data Models</li><li>MIMIC-III dataset introduction</li><li>SQL introduction</li><li>ICD-9/10</li></ul><p><strong>Cons:</strong></p><ul><li>Java software from OHDSI</li><li>Submissions in .pptx and .xlsx file formats</li><li>Peer-reviewed tasks</li></ul><p><a href="https://www.coursera.org/specializations/healthcare-information-literacy-data-analytics"><strong>Health Information Literacy for Data Analytics Specialization by the University of California, Davis</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*Wz9LHpg3j70lDI2f1KxTMQ.png" /></figure><p>The videos are spartan and can be compared to PowerPoint presentations with voiceovers.</p><ol><li><a href="https://www.coursera.org/learn/healthcare-data-literacy">Healthcare Data Literacy</a> — rather decent, with a presentation of many good subjects like an excellent introduction to the state of business of the medical care in the USA, ICD codes, and other standard terminologies.</li><li><a href="https://www.coursera.org/learn/healthcare-data-models">Healthcare Data Models</a> — too general and superficial.</li><li><a href="https://www.coursera.org/learn/healthcare-data-quality-governance">Healthcare Data Quality and Governance</a> — too general and superficial.</li><li><a href="https://www.coursera.org/learn/analytical-solutions-common-healthcare-problems">Analytical Solutions to Common Healthcare Problems</a> — contains interesting and useful concepts like Super Utilizers or Fraud detection in week 1. However, later, it tries to cover SAS software and topics that are much better explained in the “Understanding Medical Research: Your Facebook Friend is Wrong”.</li></ol><p><strong>Pros:</strong></p><ul><li>An excellent introduction to the state of business of the medical care in USA</li><li>Super Utilizers</li><li>Ontologies (SNOMED, CPT, LOINC, etc)</li><li>ICD-9/10</li></ul><p><strong>Cons:</strong></p><ul><li>Too superficial and impractical</li><li>Peer-reviewed tasks</li></ul><p><a href="https://www.coursera.org/specializations/ai-for-medicine"><strong>AI for Medicine Specialization by deeplearning.ai</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*Z0AIE7VkB_LQLuwMBNlwzw.png" /></figure><ol><li><a href="https://www.coursera.org/learn/ai-for-medical-diagnosis">AI for Medical Diagnosis</a></li><li><a href="https://www.coursera.org/learn/ai-for-medical-prognosis">AI for Medical Prognosis</a></li><li><a href="https://www.coursera.org/learn/ai-for-medical-treatment">AI For Medical Treatment</a></li></ol><p>The theoretical part is great. It covers CV, NLP, and working with the table data. You’ll learn about CNN, Sequence models, Tree models, important performance metrics, nuances of data preparation, and the DL model’s results interpretation. For example, it was the only course which covered <a href="https://github.com/slundberg/shap">SHAP values</a>.</p><p>But there are many boring “translate well-known formulas to python code” practical tasks. The original code is full of things like from utils import *, global variables, low code reuse, a lot of enclosed IF’s, rewritings of 100K times implemented standard features (like grid search), etc.</p><p>Still, it is the only known DL eHealthecare course. Since authors were more focused on healthcare, I would also recommend taking a course “<a href="https://www.coursera.org/specializations/deep-learning">Deep Learning Specialization by Andrew Ng</a>” for a deeper understanding of underlying algorithms.</p><p><strong>Pros:</strong></p><ul><li>Great theory</li><li>DL in medicine</li></ul><p><strong>Cons:</strong></p><ul><li>Boring and impractical programming tasks</li></ul><p><a href="https://www.coursera.org/specializations/ai-healthcare"><strong>AI in Healthcare Specialization by Stanford</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*aAUtBnhOSCiGedip6teAxQ.png" /></figure><p>This specialization costs more than others: 79$ vs 49$, and during the free trial period, you won’t be able to take quizzes — they will unlock after you press “new session start”, which occurs after the first free week.</p><ol><li><a href="https://www.coursera.org/learn/intro-to-healthcare?specialization=ai-healthcare">Introduction to Healthcare</a> — provides a lot of information about money flow inside the USA healthcare system, though, it will be described in a more optimistic way than in the <a href="https://www.coursera.org/learn/healthcare-data-literacy">Healthcare Data Literacy</a>.</li><li><a href="https://www.coursera.org/learn/introduction-clinical-data?specialization=ai-healthcare">Introduction to Clinical Data</a> — is about the specifics, types, and nuances of the medical data.</li><li><a href="https://www.coursera.org/learn/fundamental-machine-learning-healthcare?specialization=ai-healthcare">Fundamentals of Machine Learning for Healthcare</a> — this course is ML/DL 101. I prefer <a href="https://www.deeplearning.ai/machine-learning-yearning/">Ng’s book Machine Learning Yearning</a> for this purpose.</li><li><a href="https://www.coursera.org/learn/evaluations-ai-applications-healthcare?specialization=ai-healthcare">Evaluations of AI Applications in Healthcare</a> — quite significant. It covers business values, stakeholders, general deployment problems of eHealthcare solutions, FDA approval process of Software as Medical Device solutions. For example, it states that the most accurate model is not the most useful one.</li><li><a href="https://www.coursera.org/learn/ai-in-healthcare-capstone">AI in Healthcare Capstone</a> — looks like a job interview. You will get the role of a eHealthcare expert on some hypothetical task. There are no programming tasks, only quizzes. They include 9 peer-review tasks (I personally hate this type of task), but those are not mandatory.</li></ol><p><strong>Pros:</strong></p><ul><li>Strong theory</li><li>Topics that are not covered in other courses</li><li>A lot of useful readings</li><li>You will get a slide deck in PDF with materials from video lectures after each course completion</li></ul><p><strong>Cons:</strong></p><ul><li>No practical tasks</li></ul><p><a href="https://www.coursera.org/learn/healthcare-data"><strong>Using clinical health data for better healthcare by The University of Sydney</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*AYvwRydOAnN34Fua2gAewQ.png" /></figure><p>It is a general course about the medical data workflow. However, what makes it interesting is that it describes the Australian healthcare system which is very different from the USA’s model. However, the most of the medical DS/ML projects are currently coming from the USA. That is why I did not add this course to the recommended list.</p><p><strong>Pros:</strong></p><ul><li>Australian healthcare system</li></ul><p><strong>Cons:</strong></p><ul><li>Peer-reviewed tasks</li></ul><p><a href="https://www.coursera.org/learn/clinical-research"><strong>Understanding Clinical Research: Behind the Statistics by University of Cape Town</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*71aBR0uBGZuwqavX4UXCig.png" /></figure><p>General and Medical Statistics 101. In the introduction, I stated that it is better to take a separate course on statistics. This course could be the one.<br> However, most of its material are covered in the “Understanding Medical Research: Your Facebook Friend is Wrong” and “Healthcare Data Literacy” better.</p><p><strong>Pros:</strong></p><ul><li>101 statistics</li></ul><p><strong>Cons:</strong></p><ul><li>Peer-reviewed tasks</li></ul><p><a href="https://www.coursera.org/learn/datascimed?"><strong>Data Science in Stratified Healthcare and Precision Medicine by The University of Edinburgh</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*u9IQQlCQ02HCwZUTC9e-CA.png" /></figure><p>The course covers basics and brings some biological context in Python, DNA sequencing, medical imaging, ML, graph data models. It looks like the authors tried to cover every topic.<br> In some way, they succeeded. But the result is very superficial.</p><p><strong>Pros:</strong></p><ul><li>Python</li><li>ML general concepts</li></ul><p><strong>Cons:</strong></p><ul><li>Peer-reviewed tasks</li><li>A lot of long and boring case studies</li><li>A course listener will need to write a short essay</li></ul><p><a href="https://www.coursera.org/learn/medical-research/"><strong>Understanding Medical Research: Your Facebook Friend is Wrong by Yale University</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*zYei7CyI8bIrRW4Bxc8o1A.png" /></figure><p>This is the best 101 to clinical trials I’ve ever encountered, the real “must have”, especially in our COVID-19 times.</p><p>The course “About” page provides a nice and fair description:</p><p><em>[This course]</em> will provide you with the tools and skills you need to critically interpret medical studies, and determine for yourself the difference between good and bad science.</p><p>The course covers study-design, research methods, and statistical interpretation. It also delves into the dark side of medical research by covering fraud, biases, and common misinterpretations of data. Each lesson will highlight case-studies from real-world journal articles.</p><p><strong>Pros:</strong></p><ul><li>The best 101 to clinical trials I’ve met</li></ul><p><strong>Cons:</strong></p><ul><li>The course name typed in certificate may not look worthy in the employer’s eyes.</li></ul><h3>My recommendations</h3><p>There is a bunch of eHealth courses, but only few of them are useful in the applied sense.</p><p>In my opinion, the best options are:</p><ul><li><a href="https://www.coursera.org/specializations/ai-healthcare">AI in Healthcare Specialization by Stanford</a> — has the most comprehensive eHealth coverage among all of the courses I’ve reviewed.</li><li><a href="https://www.coursera.org/learn/medical-research/">Understanding Medical Research: Your Facebook Friend is Wrong</a> — sheds some light on details of clinical trials and their common pitfalls, including peculiar medstatistic errors.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6163144c2a15" width="1" height="1" alt=""><hr><p><a href="https://medium.com/inside-the-tech-by-softserve/overview-of-ehealth-courses-for-ml-engineers-6163144c2a15">Overview of eHealth Courses for ML engineers</a> was originally published in <a href="https://medium.com/inside-the-tech-by-softserve">Inside the Tech by SoftServe</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Tech Lead to Architect — Part 1: IT consulting process]]></title>
            <link>https://medium.com/inside-the-tech-by-softserve/from-tech-lead-to-architect-part-1-it-consulting-process-38f131661af8?source=rss-3fa9e021b6ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/38f131661af8</guid>
            <category><![CDATA[it-consulting]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[tech-lead]]></category>
            <category><![CDATA[it-career]]></category>
            <dc:creator><![CDATA[SoftServe]]></dc:creator>
            <pubDate>Mon, 09 Nov 2020 09:28:49 GMT</pubDate>
            <atom:updated>2020-11-09T09:28:49.432Z</atom:updated>
            <content:encoded><![CDATA[<h3>From Tech Lead to Architect — Part 1: IT consulting process</h3><p>What happens after Sales Manager finds a potential client and what is a Software Architect`s role here?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*zRxjIKTe1choK4zpGUTX0w.png" /></figure><p>Understanding of how consulting works is a must to become a Software Architect.</p><p>Dmytro Ovcharenko is a Senior Solutions Architect from SoftServe Development Center in Dnipro. He`s involved both in the direct implementation of projects and in consulting activities for client acquisition. In this article he will go through IT consulting process and figure the place of an Architect in it.</p><h3><strong>Types of Software Architects in consulting</strong></h3><p><strong>Farmers</strong> — work independently or as part of an architectural team on one project when a client has already signed a contract and agreed on a scope of work. More frequently are involved in implementation only.</p><p><strong>Hunters</strong> — participate in consulting processes together with sales and delivery teams to attract new business (new customers or new contracts with existing ones). The hunter participates in presale, discovery and assessment activities.</p><p>Here is the scheme of what a hunter`s place in IT consulting process is.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IYUW4FQyZynFzSsi-jXr1w.jpeg" /></figure><h3><strong>IT consulting process in a nutshell</strong></h3><p><strong>Step 1.</strong> To find a potential client (prospect) with a clear need to solve a business problem or achieve a business goal.</p><p>Responsible — Sales Executives or Client Partners</p><p><strong>Step 2. </strong>Pre-sale stage — to turn a prospect into a client (to sign a contact)</p><p>Responsible — <strong>Tech team, that includes</strong>:</p><ul><li>Sales Executive or Client Partner, who attracted this client,</li><li>Engagement manager that drives the organizational part: makes appointments, provides materials, tracks the process, reminds key points when needed, and also helps the clients who have not worked with consulting companies before to understand the process and tasks,</li><li>Architect,</li><li>Business Analyst,</li><li>Technical expert, for example, Data Science or ML, depending on the client specifics,</li><li>Managers of different levels, depending on the size of the client’s company.</li></ul><h3>How pre-sale goes?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*d7HnLj2b4rZj5VmFZQQ03Q.jpeg" /></figure><p><strong>Step 1. A call with the client</strong></p><p>All<strong> </strong>team members attend this call to discuss the client`s need and get as much information as possible.</p><p>An Architect needs to be thoroughly prepared and have all questions in advance, otherwise, the conversation will be too general, without specifics.</p><p>Some key points to ask:</p><ul><li>Business goals: what does your client want to achieve?</li><li>Architectural drivers: what are functional and non-functional requirements (at least in general terms)?</li><li>Assumptions</li><li>Risks</li></ul><p>Usually, we do not have enough time to talk over all questions, so we discuss the most critical ones and email the rest after the call.</p><p><strong>Step 2. Proposal development</strong></p><p>We analyze all the information, we got from the client, and prepare one of the following documents:</p><ul><li>Presentation — a sketch of our vision and an estimate of project costs. It can be high-level or detailed, depending on the situation.</li><li>State of work — a legal document and the base for contract conclusion. This draft is reviewed by internal stakeholders, finalized, and sent to the client for signature.</li></ul><h3>What follows pre-sale? There are few options</h3><p><strong>Implementation</strong></p><p>A fairly common practice in many companies, but the risky one. We at SoftServe do not use. As pre-sale is a short activity, up to 2 weeks, it is difficult to understand all requirements, so there is a high risk of faulty estimates. That`s why a client may not get the expected result from the chosen solution.</p><p><strong>Assessment of the client’s current projects</strong></p><p>This is particularly necessary when:</p><ul><li>Client buys another company, and their software needs to be checked. The client usually needs only a report, and this is where the project ends.</li><li>Client has a real problem that needs to be assessed. In such cases we prepare a report and recommendations to eliminate this problem. This is often followed by the implementation of the developed plan.</li></ul><p><strong>Discovery</strong></p><p>It`s on-site sessions with the client to work out the requirements in more details and develop documentation — Implementation Proposal, Architecture Vision, Roadmap, and Estimates. Now, during the lockdown, we are conducting these sessions online.</p><p>This format is needed when we know only general descriptions and do not understand what our client specifically needs.</p><p>Depending on the scale of the client’s request, the terms vary from 3 weeks to 1.5 months.</p><p>For the trip/online session you need to prepare:</p><ul><li>Agenda</li><li>Stakeholder RACI matrix (the list of people to talk to). If you do not know the names, you can indicate the positions, for example, Chief DevOps Engineer, Lead Security Engineer, or Tech Leads.</li><li>Vision template</li><li>Basic information on the client, such as, with whom they have previously worked and what software they use. You can find it on the internet.</li></ul><p>Before starting work, I advise to have a kick-off meeting with a client, announce the agenda and your expectations. It is also important to discuss the list of stakeholders with whom the sessions are critical, and to get a confirmation that those people will be available to you.</p><h3>A closer look at Discovery agenda</h3><p><strong>Part 1 (first few days)</strong></p><p>Goal: collect functional and non-functional requirements, business goals.</p><p>To do this, we hold meetings with stakeholders, organize Quality Attribute Workshop (will write about it in my next article) and <a href="https://www.softserveinc.com/en-us/blog/design-thinking-methodology">Design Thinking Workshop</a>.</p><p>As a result, we get a set of architectural drivers that become a base to proceed to the second part.</p><p><strong>Part 2</strong></p><p>Goal: prepare solution sketches.</p><p>I strongly recommend not to work on your own at this stage. Conduct knowledge sharing with technical experts from the client’s side, share your assumptions and sketches to immediately validate and discuss them.</p><p>At SoftServe, we use several methodologies for system design and analysis such as ADD, <a href="https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=8147">Attribute Driven Design</a>, and ATAM, <a href="https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=5177">Method for Architecture Evaluation</a>. The documenting process is entirely built around <a href="https://resources.sei.cmu.edu/library/asset-view.cfm?assetID=30386">Documenting Software Architectures: Views and Beyond</a>. Each of the methodologies deserves a separate article. For novice architects, I suggest reading on documentation, as it is an integral part of the architect’s work, be it a farmer or a hunter.</p><p>The result of the discovery is a presentation with outcomes of the discovery session, architecture vision document, detailed team composition, detailed roadmap and budget, and software requirements specification.</p><p>The discovery is successful when the client has signed the contract for the implementation of the proposed solution and a new delivery team is formed for it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38f131661af8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/inside-the-tech-by-softserve/from-tech-lead-to-architect-part-1-it-consulting-process-38f131661af8">From Tech Lead to Architect — Part 1: IT consulting process</a> was originally published in <a href="https://medium.com/inside-the-tech-by-softserve">Inside the Tech by SoftServe</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>