<?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[CML Team - Medium]]></title>
        <description><![CDATA[CML Team blog - Medium]]></description>
        <link>https://medium.com/cmlteam?source=rss----a97506673e5f---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>CML Team - Medium</title>
            <link>https://medium.com/cmlteam?source=rss----a97506673e5f---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 03:41:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/cmlteam" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How we almost get scammed by AI generated fake candidates]]></title>
            <link>https://medium.com/cmlteam/how-we-almost-get-scammed-by-ai-generated-fake-candidates-7f153134d350?source=rss----a97506673e5f---4</link>
            <guid isPermaLink="false">https://medium.com/p/7f153134d350</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[recruiting]]></category>
            <dc:creator><![CDATA[Oleksandr Shchetynin]]></dc:creator>
            <pubDate>Tue, 01 Jul 2025 17:57:03 GMT</pubDate>
            <atom:updated>2025-07-01T17:57:03.873Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*f1bMogBp2VDK6LCj_O8VnQ@2x.jpeg" /></figure><p>Recently, our team narrowly avoided a sophisticated recruitment scam involving advanced deepfake technology combined with strategic social engineering tactics.</p><p>During the interview process for a remote Full-stack React and Node.js developer role, we encountered a candidate named “Bob” (name changed for privacy), who claimed to be based in Ireland. Bob’s English proficiency was convincing, and both HR and our software engineering team initially found nothing suspicious during the video interview. We were preparing to extend an employment offer.</p><p>However, our suspicion was triggered when another candidate with a similar profile applied for a different position. Upon deeper investigation, we discovered alarming inconsistencies:</p><ul><li>Multiple technology stacks (C#, Java, Python, Node, Solidity) appeared inconsistently across their GitHub profiles and did not fully align with their CVs.</li><li>Several profiles had starred the GitHub repository<a href="https://www.google.com/url?q=https://www.google.com/url?q%3Dhttps://github.com/iperov/DeepFaceLive%26amp;sa%3DD%26amp;source%3Deditors%26amp;ust%3D1751371938710186%26amp;usg%3DAOvVaw1tNVZE8KIm7HxF6NAU94b8&amp;sa=D&amp;source=docs&amp;ust=1751371938722690&amp;usg=AOvVaw0zI3rsj2AlJ1kktoA_6bts"> </a><a href="https://github.com/iperov/DeepFaceLive">DeepFaceLive</a>, a known deepfake software capable of real-time face swapping in live video calls.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*NhdQDJgoETpTZODH" /><figcaption>DeepFaceLive has been detected on few profiles in starred repos</figcaption></figure><ul><li>All of them refuse to have in-person meetings in Dublin (where Bob is supposed to be located) and London (where the other guy is supposed to be located). We came to a conclusion that this might be a scam.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*M1sKZZJ2N-7egFz9" /><figcaption>an example of a typical excuse to avoid meeting</figcaption></figure><p>Upon reviewing Bob’s recorded interview, we confirmed that it featured highly sophisticated real-time facial movement, hand gestures, and emotional expressions, without obvious artifacts typically associated with deepfake technology. Only subtle clues like consistent headwear (potentially hiding artifacts) and artificial backgrounds hinted at deception.</p><p>We determined the likely modus operandi:</p><ul><li>An organized group, presumably operating from Asia, creates fake profiles with credible EU/UK identities.</li><li>Skilled, English-fluent individuals conduct interviews using advanced deepfake technology to impersonate these fabricated identities convincingly.</li></ul><p>In response, we’ve implemented crucial updates to our recruitment process:</p><ol><li>Mandatory in-person or verified physical meetings prior to any job offer.</li><li>Comprehensive social media and professional network audits for candidate authenticity.</li><li>Explicit guidelines forbidding artificial backgrounds and headwear during video screenings.</li></ol><p>Sharing this experience highlights the evolving threat landscape in remote hiring, underscoring the need for vigilance, robust candidate vetting, and awareness of increasingly sophisticated fraud techniques.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f153134d350" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cmlteam/how-we-almost-get-scammed-by-ai-generated-fake-candidates-7f153134d350">How we almost get scammed by AI generated fake candidates</a> was originally published in <a href="https://medium.com/cmlteam">CML Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top Project Risks for Developers (Part 2)]]></title>
            <link>https://medium.com/cmlteam/top-project-risks-for-developers-part-2-9c2e726a3352?source=rss----a97506673e5f---4</link>
            <guid isPermaLink="false">https://medium.com/p/9c2e726a3352</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[risk-management]]></category>
            <category><![CDATA[delivery-management]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Oleksii Skurikhin]]></dc:creator>
            <pubDate>Fri, 22 Sep 2023 09:46:09 GMT</pubDate>
            <atom:updated>2023-09-22T09:47:27.716Z</atom:updated>
            <content:encoded><![CDATA[<p>This article discusses common project risks that software developers may encounter, whether working under direct client management in a small startup or in large projects where their project manager is overwhelmed with other tasks.</p><p>If you haven’t had the chance to read the <a href="https://medium.com/cmlteam/top-project-management-risks-for-developers-part-1-97361eba5713">first article</a>, you can catch up by checking out now.</p><p>Let’s dive into the remaining risks from our plan.</p><h3>7. Communication Overhead</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rHqP7LnNH0Myc0DvLkmuSQ.png" /><figcaption><a href="https://www.monkeyuser.com/">https://www.monkeyuser.com/</a></figcaption></figure><h4>Why it happens</h4><ul><li>Absence of a ticket management system.</li><li>Underestimation of the discovery phase and backlog refinement</li><li>Overly active and creative clients.</li></ul><blockquote>Implication: Burnout from meetings and frequent ticket reworks can lead to missed deadlines and strained stakeholder relationships.</blockquote><h4>Prevention:</h4><ul><li>Adopt a ticket management system if you don’t have any.</li><li>Include communication in estimations to encourage efficient discussions.</li><li>Prepare meeting agendas and convert questions into actionable items or clear choices.</li></ul><h3>8. Colleague Turnover</h3><h4>Why it happens</h4><ul><li>Aspirations for personal growth beyond the project.</li><li>Burnout from an unmanageable workload.</li><li>Lack of teamwork.</li></ul><blockquote>Implications: increased workload, navigating unfamiliar product areas, added stress due to insufficient documentation, and potential project delays.</blockquote><h4>Prevention:</h4><ul><li>Cultivate a supportive and team-oriented environment.</li><li>Strengthen bonds with colleagues, promoting open dialogue and engagement.</li><li>Prioritize updated documentation to simplify transitions.</li><li>Maintain a pulse on your colleagues’ tasks through regular code reviews or check-ins.</li></ul><h3>9. Architectural Constraints</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m2whxStXlizwEfFkmPh77g.png" /><figcaption><a href="https://www.monkeyuser.com/">https://www.monkeyuser.com/</a></figcaption></figure><h4>Why it happens</h4><ul><li>Project evolving</li><li>Initial budgetary and time constraints.</li><li>The prior team lacked experience.</li></ul><blockquote>Implications: stability and scaling issues lead to persistent bugs and crashes and ultimately extend timelines, inflate budgets, and result in missed deadlines</blockquote><h4>Prevention:</h4><ul><li>Before estimating, thoroughly review the codebase, especially for significant features.</li><li>Discuss reworks with the client, highlighting impacts on user experience and performance.</li><li>In startups, start with a lean architecture and pre-plan upgrades, like after hitting 100,000 users.</li><li>Don’t hesitate to consult colleagues for insights to make informed technical decisions in new domains.</li></ul><h3>10. Challenges with 3rd Party Components</h3><h4>Why it happens</h4><ul><li>Documentation may be vague or incomplete.</li><li>Potential component instability or bugs.</li><li>Security vulnerabilities.</li><li>The component’s end of life or support.</li></ul><blockquote>Implications: extensive debugging and bug fixes or even require starting from scratch, ultimately leading to project delays.</blockquote><h4>Prevention:</h4><ul><li>Thoroughly vet any component, especially lesser-known ones, before integration.</li><li>Investigate the component vendor’s credibility and reliability.</li><li>Dive deep into component documentation and related community discussions.</li><li>Incorporate research when estimating, considering potential setbacks.</li><li>For essential yet risky components, create a PoC in the early stages.</li></ul><h3>11. Integration Failures</h3><h4>Why it happens</h4><ul><li>Unavailability of tech support.</li><li>Limited budget constraints</li><li>Legal and compliance challenges.</li></ul><blockquote>Implication: can render a project infeasible or significantly delay its launch, making time and money spent on development wasteful.</blockquote><h4>Prevention:</h4><ul><li>Address infrastructure early; secure all environments for a solid CI/CD setup.</li><li>Review the chosen API and its support before developing the integration.</li><li>Alert the client to potential legal hurdles; obtaining documentation, credentials, or passing compliance can prolong the timeline and should be addressed before or concurrently with early development stages.</li></ul><h3>Final Thoughts</h3><p>For developers, particularly those in out-staff positions, recognizing and adeptly managing risks is pivotal. While the landscape of challenges might shift, proactive risk management remains a potent tool in ensuring the success of any project.</p><h3>How We Can Help You</h3><p>Our dedicated team of professionals has hands-on experience navigating the challenges we’ve discussed. We don’t just highlight problems; we present actionable solutions tailored to your specific needs. Our extensive experience and passion for successful project delivery make us a trusted partner in your development journey.</p><p><a href="https://www.cmlteam.com/schedule-a-call">Contact us</a> if you’re searching for dedicated engineers, expert consultancy, or an entire outstaff team. We’re here to ensure your vision materializes without unnecessary obstacles or stress.</p><p>Stay updated with insights, trends, and more valuable content by following <a href="https://medium.com/@oleksiiskurikhin">me</a> and our <a href="https://medium.com/cmlteam">blog</a>. Your engagement fuels our motivation. Please share your thoughts, ideas, or suggestions below. We cherish your feedback and look forward to continuous learning and improvement.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c2e726a3352" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cmlteam/top-project-risks-for-developers-part-2-9c2e726a3352">Top Project Risks for Developers (Part 2)</a> was originally published in <a href="https://medium.com/cmlteam">CML Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top Project Management Risks for Developers (Part 1)]]></title>
            <link>https://medium.com/cmlteam/top-project-management-risks-for-developers-part-1-97361eba5713?source=rss----a97506673e5f---4</link>
            <guid isPermaLink="false">https://medium.com/p/97361eba5713</guid>
            <category><![CDATA[risk-management]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[estimation-techniques]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Oleksii Skurikhin]]></dc:creator>
            <pubDate>Mon, 18 Sep 2023 12:10:08 GMT</pubDate>
            <atom:updated>2023-09-22T09:46:44.373Z</atom:updated>
            <content:encoded><![CDATA[<p>There’s a common misconception that only project managers must identify and handle risks.</p><p>Yet, developers, especially those in outstaff roles within startups, consistently navigate these challenges. A basic understanding of risks can unlock key outcomes, especially without a Project Manager on board or amid disagreements with one.</p><p>Let’s dive into these risks, viewing them as opportunities to deliver intended outcomes quickly.</p><h3>1. The Disengaged Client/Manager</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B6JbLbzhXjJpMxtIE_Mz9g.png" /><figcaption><a href="https://www.monkeyuser.com/">https://www.monkeyuser.com/</a></figcaption></figure><h4>Why it happens</h4><ul><li>Busy schedules</li><li>Budgeting issues</li><li>Loss of faith in the project, especially after missed deadlines</li></ul><blockquote><strong>Implications</strong>: A disengaged client or manager is a red flag. Prolonged disengagement can directly lead to losing the project.</blockquote><h4><strong>Prevention</strong></h4><ul><li>Maintain consistent and clear communication.</li><li>Manage the backlog effectively to ensure continuous work.</li></ul><h4><strong>If problems arise</strong></h4><blockquote>In any ambiguous situation — Think</blockquote><ul><li>Don’t hesitate to point out pending tickets politely; consider diverse communication channels such as email, chat, jira, arranging a meeting, etc.</li><li>Be creative and try to propose beneficial features or enhancements.</li><li>Report the situation transparently in internal daily updates and seek guidance from your organization if your actions don’t help.</li></ul><h3>2. Ambiguous Task Descriptions</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*t5flmXCo2TXLEClk.png" /><figcaption><a href="https://www.monkeyuser.com/">https://www.monkeyuser.com/</a></figcaption></figure><h4>Why it happens</h4><ul><li>The assumption is that tasks are self-explanatory.</li><li>Overwhelmed with other responsibilities.</li><li>Uncertainty about task specifics.</li></ul><blockquote>Implications: Wasted efforts, conflicts in the team, and potential project delays.</blockquote><h4>Prevention</h4><ul><li>Avoid accepting vaguely described tasks.</li><li>Propose and stand out for standardized task formatting.</li><li>Discuss uncertainties with the client, manager, and QA engineers, especially don’t miss the last ones since their opinion matters a lot.</li><li>Update the ticket summary after any discussion; don’t keep comments elsewhere.</li></ul><h4>If problems arise</h4><ul><li>Stay focused on the end goal and look for a way to handle the situation</li><li>Make informed assumptions and validate them with the client, managers, and QA to ensure alignment.</li></ul><h3>3. Persistent Requirement Changes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MJoCKFXTQ_R9BB47.png" /><figcaption><a href="https://www.monkeyuser.com/">https://www.monkeyuser.com/</a></figcaption></figure><h4>Why it happens</h4><ul><li>Ongoing product market fit experimentation.</li><li>The client’s high creativity generates infinite ideas.</li><li>Stakeholder misalignment affecting requirement consensus.</li></ul><blockquote>Implications: Persistent changes can cause workflow disruptions, timeline extensions, strained relations, and team burnout.</blockquote><h4>Prevention</h4><ul><li>Fully acknowledge that once you accept a task, the onus to meet the deadline is on you, not the client or your manager.</li><li>Consolidate minor updates, recognizing that many “one-minute” tasks can significantly exceed the estimated time.</li><li>Develop and agree on a change plan to protect the project scope.</li><li>Maintain open communication channels, actively discussing task priorities and potential delays.</li></ul><h4>If problems arise</h4><ul><li>Alert the client promptly if there’s a potential risk of missing a deadline.</li><li>Always propose solutions when presenting a problem, whether suggesting feature removals from the release, halting the current task, or exploring alternative approaches.</li></ul><h3>4. Gold Plating: Overdoing Enhancements</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fW_GbVPDh1n6NzxRbjqVhg.png" /><figcaption><a href="https://www.monkeyuser.com/">https://www.monkeyuser.com/</a></figcaption></figure><h4>Why it happens</h4><ul><li>Desire to surpass expectations.</li><li>Creative nature</li><li>A wish to optimize even if there is no technical debt.</li></ul><blockquote>Implications: Over-optimization can consume unnecessary time and resources, potentially diverting focus from the project’s ultimate goal.</blockquote><h4>Prevention</h4><ul><li>Prioritize business value over deliverables, and remember that a client pays for it.</li><li>Bring up potential improvements during the estimation phase.</li><li>Stay flexible, and be prepared to delay or set aside your ideas, but don’t hesitate to bring ones.</li></ul><h4>If problems arise</h4><ul><li>Handle the consequences if it affects the schedule badly.</li><li>Discuss the situation with the client or managers and explore potential solutions together.</li></ul><h3>5. Estimation Pitfalls</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z0Tli_N7VxJMCieUf08VzQ.png" /><figcaption><a href="https://www.monkeyuser.com/">https://www.monkeyuser.com/</a></figcaption></figure><h4>Why it happens</h4><ul><li>Neglecting to break down and thoroughly analyze high-level described features during estimation.</li><li>Forgetting specific activities like meetings, research, or regression tests.</li><li>Ignoring dependencies and potential risks.</li><li>Pressure from a client or manager to commit to challenging targets.</li><li>Overestimating for a safety buffer.</li></ul><blockquote>Implications: Incorrect estimates inflate budgets and timelines, affect team morale, and strain client relationships.</blockquote><h4>Prevention</h4><ul><li>Don’t hesitate to ask questions and address any uncertainties.</li><li>Break down a big future into smaller ones.</li><li>Include all the necessary activities like code review, bug fixing, etc</li><li>Remember, you’re not alone. If you’re facing a new technology or business domain, don’t hesitate to seek colleague assistance, even outside the current project.</li><li>Provide clients with estimation ranges, highlight risks, and help them make educated decisions.</li><li>Be ready to stand for your estimation</li></ul><h4>If problems arise</h4><p>Suggest aligned alternatives that you can deliver on time to reach their project goals.</p><h3>6. Miscommunication Challenges</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wF3rcfz1w2jxHlxn.png" /><figcaption><a href="https://www.monkeyuser.com/">https://www.monkeyuser.com/</a></figcaption></figure><h4>Why it happens</h4><ul><li>Geographic and cultural differences.</li><li>Missing meetings, emails, and messages.</li><li>Clients changed past decisions.</li><li>Making assumptions without confirmation</li></ul><blockquote>Implications: Miscommunications can lead to misaligned expectations, strained relationships, and project delays.</blockquote><h4>Prevention</h4><ul><li>Maintain regular communication with the client to ensure alignment.</li><li>After meetings, send follow-up emails summarizing the discussion.</li><li>Record discussions and decisions as action items in tickets.</li><li>Since tracking changes in external links on tools like Figma can be challenging, save all evidence within the ticket. This includes taking screenshots and uploading documents to capture the real-time progress.</li><li>Always clarify assumptions before taking any actions.</li><li>If a report format isn’t specified, inquire about the client’s preference.</li></ul><h3>Stay tuned</h3><p>Our <a href="https://medium.com/cmlteam/top-project-risks-for-developers-part-2-9c2e726a3352">upcoming article</a> will explore risks like <strong>Communication Overhead</strong>, <strong>Colleague Turnover</strong>, <strong>Integration Failures</strong>, and more. Stay tuned by following <a href="https://medium.com/@oleksiiskurikhin">me</a> and <a href="https://medium.com/cmlteam">our blog</a>. Your feedback is invaluable — if you have insights, ideas, or suggestions for this or future articles, please comment below.</p><h3>Contact us</h3><p><a href="https://www.cmlteam.com/schedule-a-call">Contact us</a> seamlessly if you’re searching for outstaff engineers or a dedicated team to bring your ideas to life. We’re here to ensure your vision is realized without any headaches or workload.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97361eba5713" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cmlteam/top-project-management-risks-for-developers-part-1-97361eba5713">Top Project Management Risks for Developers (Part 1)</a> was originally published in <a href="https://medium.com/cmlteam">CML Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Monolithic vs. Microservices architecture: How to not fail your startup]]></title>
            <link>https://medium.com/cmlteam/monolithic-vs-microservices-architecture-how-do-not-fail-your-startup-c99fbd3c533d?source=rss----a97506673e5f---4</link>
            <guid isPermaLink="false">https://medium.com/p/c99fbd3c533d</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[monolithic-architecture]]></category>
            <dc:creator><![CDATA[Oleksii Skurikhin]]></dc:creator>
            <pubDate>Mon, 28 Aug 2023 13:56:31 GMT</pubDate>
            <atom:updated>2023-08-28T15:22:13.771Z</atom:updated>
            <content:encoded><![CDATA[<p>Startups often operate within a shifting product-market fit, under ambiguous requirements, and on a limited budget. These constraints make every architectural decision invaluable, entirely worth its weight in gold.</p><h3>A Lesson from Experience</h3><p>Years ago, our team lead proposed a complex architecture at a startup. This led us to miss deadlines and lose a significant contract, as we focused too much on refactoring rather than delivering value and fixing bugs.</p><blockquote>It taught me a crucial lesson: always prioritize business value over architecture and question developers’ opinions to ensure realistic outcomes.</blockquote><p>Though four architecture approaches are illustrated in the following diagram, we consider the pros and cons of the serverless approach in the next article. Let’s focus on Monolith and Microservices.</p><figure><img alt="Monolith vs microservices" src="https://cdn-images-1.medium.com/max/795/0*1M08peTC8flGmAw5" /></figure><h3>Critical considerations in choosing an architectural approach</h3><p>If you’re a business person, consider factors like product size, scalability requirements, budget, and team size.</p><h4>Product size and scalability requirements in the current stage</h4><ul><li>The monolithic system suits small to medium-sized products well, especially during the early stages or when you must launch a quick PoC, MVP, or first few versions.</li><li>Microservices are ideal for products that have grown successfully and have clear and comprehensive architecture requirements, with plans for flexible scaling. Note that vertical scaling is still possible with a monolithic server.</li></ul><h4>Budget</h4><ul><li>If you have a limited budget, I strongly recommend monolithic.</li><li>If the budget supports bigger ambitions, Microservices might be your choice.</li></ul><h4>Team Size</h4><ul><li>A monolithic approach may be ideal for small teams, as you can easily discuss linkages and resolve conflicts.</li><li>Larger Teams Working Concurrently: Microservices allow developers to work more effectively if you have a large team.</li></ul><h4>Tech Stack</h4><ul><li>The microservice approach is your best bet to bring together various teams with different technology stacks under a single product.</li><li>On the other hand, if you’re working with a unified technology stack, a monolithic architecture works just fine.</li></ul><blockquote>In short, while many sturtups thrive using a monolithic architecture, some falter, starting with microservices. That’s why it’s often recommended to begin with a monolithic approach.</blockquote><h3>Monolithic Architecture</h3><p>A monolithic architecture consists of a single unit where all components are interdependent.</p><figure><img alt="Monolythic architecture" src="https://cdn-images-1.medium.com/max/534/1*XwMv_trkJf6G_U6_U27xng.png" /></figure><p>Startups must endure until the challenges of monolithic architecture become clear. If you miss the opportunity window, the quality of the architecture won’t matter. So, if you are working on a disruptive idea, focus on rapid prototyping and bringing customer value.</p><blockquote>While growing, the Monolithic architecture can still be neat and user-friendly by modularization that helps developers contribute quickly and ease the eventual transition to microservices.</blockquote><h3>Microservices Architecture</h3><p>In a Microservices architecture, an application is a collection of loosely coupled, independently deployable, scalable services. They offer efficiency for big distributed teams and easy scaling of separate services like transaction processing. Complexity does arise in monitoring, testing, inter-process communication, and failure management.</p><figure><img alt="Microservices architecture" src="https://cdn-images-1.medium.com/max/562/1*cZ2vSGYPLdtCcx-O3en1Rw.png" /></figure><p>Microservice architecture makes the system flexibly scalable and resilient, where problems in a specific microservice won’t require rebooting the entire system, unlike a monolithic system.</p><h3>Transition and Rework</h3><p>Ideal architecture is unattainable. The most suitable architecture — does. The ultimate goal of any project is to bring intended outcomes to life effectively and efficiently, so good enough is usually sufficient, except rocket since or similar domains, as you know.</p><blockquote>For instance, Netflix transitioned to microservices only after making $1.670 million annually. Does your product? Remember, your product will evolve, and there’s always will be a suitable time to take the next step toward enhancing your architecture.</blockquote><h3>How to choose that time?</h3><p>Look at the diagram below that illustrates the productivity curve and the point where a transition to a microservice architecture makes sense.</p><figure><img alt="Monolith vs Microservices: How productivity depends on complexity" src="https://cdn-images-1.medium.com/max/504/1*eJaFfpobH98h2ytQ-bG-Ww.png" /></figure><p>Until you reach that point, fully embrace the monolithic approach benefits. Then, you can begin the decomposition process, focusing on the separate modules that your monolith consists of.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z7gWxNzQkuwMPis2J7U4kA.png" /><figcaption>A thriving startup flies towards its next investment round with a simple architecture.</figcaption></figure><p>It helps you to avoid such a sad situation where your product has the best architecture in the world but still isn’t ready and is stuck on the ground while your competitors are soaring above you, securing their second round of investment on their plane, which was built from a fridge and a set of mops using as wings.</p><blockquote>Please note: Great developers matter much more than architectural decisions because they deliver the intended outcomes with quality code. Consequently, they can evolve the product and its architecture over time.</blockquote><h3>How we can help</h3><p>At the <a href="https://www.cmlteam.com/">CML Team</a>, we specialize in monolithic and microservices architectures, offering personalized guidance for your startup.</p><p><a href="https://www.cmlteam.com/schedule-a-call">Reach out to us</a> today to discover how we can assist in refining your concept, defining a technology approach, and bringing your dreams and ideas to life.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c99fbd3c533d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cmlteam/monolithic-vs-microservices-architecture-how-do-not-fail-your-startup-c99fbd3c533d">Monolithic vs. Microservices architecture: How to not fail your startup</a> was originally published in <a href="https://medium.com/cmlteam">CML Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CML Team Receives Clutch Leader Award for Top Development Firms in Ukraine]]></title>
            <link>https://medium.com/cmlteam/cml-team-receives-clutch-leader-award-for-top-development-firms-in-ukraine-c605433ca475?source=rss----a97506673e5f---4</link>
            <guid isPermaLink="false">https://medium.com/p/c605433ca475</guid>
            <category><![CDATA[full-stack-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Oleksandr Shchetynin]]></dc:creator>
            <pubDate>Mon, 25 Nov 2019 15:20:10 GMT</pubDate>
            <atom:updated>2019-11-25T15:20:10.529Z</atom:updated>
            <content:encoded><![CDATA[<p><em>“We are honored to receive this award. It was a pleasure and a great honor for us to work with such great organizations and promising startups all over the world. This has helped our company grow in terms of the expertise that we provide, and the human capital that we have. All of these factors led us to earn a position as one of the top custom software agencies in Ukraine.”</em> — Oleksandr Shchetynin, Founder</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Og8B6-eShwXfhJTz6TFfCg.jpeg" /></figure><p>Clutch, a globally-recognized market research firm, recently announced its annual list of top-performing companies across various business segments in Europe. Here at CML Team, we’re thrilled to share that we were <a href="https://clutch.co/ua/web-developers">listed as a Clutch Leader</a> among development firms in Ukraine!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PbQtSg6RxrX4NSYTXSNslw.png" /></figure><p>Carving out a space in the technology consulting industry is no easy task, and we recognize that the hard work of our developers plays a huge role in our sustained growth. We often take a comprehensive approach when delivering products to our clients, with the goal of ensuring that their vision matches our recipe for success. Whether it be <a href="https://interestingengineering.com/6-technology-trends-to-watch-in-2020">blockchain</a>, e-commerce, or even mobile app development, our team is committed to providing excellent services at every stage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kx3z24lOWvlZEighcT4Vtw.png" /></figure><p>Clutch research analysts collect reviews like this one as part of a sophisticated B2B ranking methodology. The team weighs client feedback heavily in its process for determining which firms are leaders in their respective industries. For this reason, we see this award as coming from our clients as much as it is coming from Clutch!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/231/1*tTJZv80dyGrSBwzUXITKBg.png" /></figure><p>To build upon these company rankings, Clutch offers other websites that contain unique, supplementary content. According to The Manifest, a site that publishes market insights to help buyers navigate the outsourcing process, we are one of <a href="https://themanifest.com/ua/software-development/companies/kiev#cmlteam">Kyiv’s best tech resources</a> for small and medium-sized businesses!</p><p>Thank you, clients, for supporting us since the beginning. Your dedication is a major factor in our ability to keep delivering superior projects. That being said, we love to add more products to our to-do list and would love to discuss your development goals! <a href="https://www.cmlteam.com/callus/">Schedule a call</a> if you’re interested in a partnership.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c605433ca475" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cmlteam/cml-team-receives-clutch-leader-award-for-top-development-firms-in-ukraine-c605433ca475">CML Team Receives Clutch Leader Award for Top Development Firms in Ukraine</a> was originally published in <a href="https://medium.com/cmlteam">CML Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we hire a Rockstar developer — Part 1]]></title>
            <link>https://medium.com/cmlteam/how-we-hire-a-rockstar-developer-part-1-15a7296ba0e6?source=rss----a97506673e5f---4</link>
            <guid isPermaLink="false">https://medium.com/p/15a7296ba0e6</guid>
            <category><![CDATA[cmlteam]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[full-stack-developer]]></category>
            <category><![CDATA[talent]]></category>
            <dc:creator><![CDATA[Oleksandr Shchetynin]]></dc:creator>
            <pubDate>Fri, 14 Jun 2019 11:29:48 GMT</pubDate>
            <atom:updated>2019-06-14T11:29:48.524Z</atom:updated>
            <content:encoded><![CDATA[<h3>How we hire a Rockstar developer — Part 1</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GXswSvGHW4SPYjL2fVRgww.png" /></figure><p>When we’ve started a CML Team Ltd, we didn’t have an established hiring process. We had a little experience interviewing people from the past jobs we were working at, but unfortunately this experience was quite fragmented.</p><p>In order to succeed we need to come up with a holistic approach that allows us to find the best software engineers out there who share our values.</p><p>In order to understand how to find the right people, we have to understand how those people look like, think, and what skills they should possess.</p><p>As a seasoned hackathoners we were looking for people who share this passion.</p><p>Not every developer is eager to cross the comfort zone and become a white hacker. Not every developer is open minded enough to continuously learn new technologies that sometimes do not nicely feet into their existing background. There is nothing bad with those kind of developers in particular. This is just a matter of tactical and strategic choices everyone makes. We seek people with a broader view on different technologies and ecosystems.</p><p>We appreciate much more not a specific technology knowledge and years of experience in it. We appreciate the ability to effectively use this experience and learn fast and adapt to the new dynamic realities that continuously change.</p><p>We are looking for people who are eager to change and is capable to do it fast!</p><p>This person not just should have a great math and computer science background, but this background should be in her mindset, way of thinking and DNA. Given that, the lack of some technical skill at the moment won’t be an issue, since she will be capable of mastering it in a short amount of time.</p><p>Our Rockstar developer is a white hacker willing and capable of using full stack expertise in his pocket!</p><p>Those thoughts lead us to understand that our first round of interview will consist of logical, math and simple algorithmic problems. During that round the candidate will have an opportunity to show us if she is passionate about math, computer science and solving problems.</p><p>Let me provide a few examples of tasks we were asking at that round of interview that we’ve called “initial interview”.</p><blockquote>Brick weight = 1 kilo + half of the brick. What is the weight of a brick?</blockquote><p>This task is quite easy to solve, in fact I believe that pupils of primary school are capable of solving those kinds of problems. Surprisingly to us on our initial interview a lot of people failed to solve this problem, even when we are giving tips and advice on how to make a simple equation. And all of those people are not random people from the street, they do have a nice CV, years of experience in well known companies and different Spring Boot, React mumbo jumbo buzzwords in it.</p><p>Can you believe that 22% of developers we interview cannot solve this task?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4dTpWgJg4saVRGM0NWbcBg.png" /><figcaption>-1 if the candidate has led by interviewer to the equation and still can’t solve it</figcaption></figure><p>In fact, the percentage is even higher, and we decided to move this task from our “initial interview” to a phone screening in order to not waste neither candidate nor our time on interview process. Since after failing this task there’s not much we can discuss.</p><p>Another task we were asking and where a lot of people failed is about basic knowledge of sorting algorithms.</p><blockquote>What sorting algorithms do you know</blockquote><blockquote>a) What is the complexity of Bubble Sorting?</blockquote><blockquote>b) What is the complexity of Quick Sort?</blockquote><blockquote>c) What is the worst complexity of Quick Sort and for what input it happens?</blockquote><p>Even though most of the people were able to name some of the sorting algorithms, most of them failed on understanding of basics, like algorithmic complexity and principle. And please note we don’t even ask people to pseudo-code those algorithms, we just want to hear a basic understanding at that moment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AKbgPuphCdWDfSnPveiIkw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5Nz8yVD_ToN6TFZRHBoz7Q.png" /><figcaption>-1 if candidate says some obvious bs, example: log(n) &gt; n, etc; 1 if he thinks some time, or need advice</figcaption></figure><p>28% of the candidates saying some absurd things on the question about bubble sort algorithmic complexity. Like that complexity is exponential function, or that it’s log(n), and on the next question what function grows faster log(n) or n, they told us without any doubts that log(n) grows faster.</p><p>This is another task we moved from “initial interview” at some point to phone screening.</p><p>Below I will mention a few more tasks we were given to the candidates.</p><blockquote>Solve an equation: x² + x + 1 = 0</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KyxebcxSArESuvBow8gRNA.png" /><figcaption>-1 if the candidate provides wrong answer without trying them out against the equation; 1 if the candidate found at least one solution; 2 found both solutions but with mistakes or advice; 3 found everything correctly</figcaption></figure><blockquote><a href="https://en.wikipedia.org/wiki/Fizz_buzz">FizzBuzz</a> problem</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w54wwgrTFlSaNPa7y-XvJw.png" /><figcaption>-1 if the candidate doesn’t understand the task or how to solve it; 2 solves with a lot of mistakes and advice; 3 solves with minor mistake or small advice; 4 solves w/o mistakes and advice</figcaption></figure><p>If the candidate successfully passes those “childish” tasks at the interview, we’ll give him an opportunity to try himself against the tasks like following:</p><blockquote>Prove that n² — 1 divides by * for any prime number n &gt; 3</blockquote><blockquote>a) * is 12</blockquote><blockquote>b) * is 24</blockquote><p>We have a number of similar easy and complex tasks we choose from and shuffle during the “initial interview”.</p><p>Usually “initial interview” helps the candidates that are passionate about math and computer science to show this passion and stand out of the crowd. It helps us to narrow down the candidates to the ones that share our values. In fact, a small percentage pass this interview.</p><p>But those who do, not only have more chances to join our team, but they are also very excited to do so.</p><p>Most of them really enjoy the interview process. They are asked not just about “chrestomathic knowledge” of simple Java questions that any person can learn without really understanding what they’ve learnt. On the contrary they are given an opportunity to stand out from the grey developers crowd and to show what is their way of thinking and what is their passion, and they see that we appreciate this much more than mythical years of experience and standard Java “nerdy” questionnaire anyone can memorise.</p><p>In the next article I will cover how we allow successful candidates from first stage to share their passion about Java, and why do we ask for Java knowledge in full stack position.</p><p><strong>Stay tuned …</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15a7296ba0e6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cmlteam/how-we-hire-a-rockstar-developer-part-1-15a7296ba0e6">How we hire a Rockstar developer — Part 1</a> was originally published in <a href="https://medium.com/cmlteam">CML Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Develop a utility on GraalVM]]></title>
            <link>https://medium.com/cmlteam/develop-a-utility-on-graalvm-cc160feafc19?source=rss----a97506673e5f---4</link>
            <guid isPermaLink="false">https://medium.com/p/cc160feafc19</guid>
            <category><![CDATA[graal]]></category>
            <category><![CDATA[curl]]></category>
            <category><![CDATA[graalvm]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Volodymyr Gubarkov]]></dc:creator>
            <pubDate>Tue, 14 May 2019 17:35:44 GMT</pubDate>
            <atom:updated>2019-05-14T17:37:47.890Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Image result for GraalVM" src="https://cdn-images-1.medium.com/proxy/1*eIW3gooOD5kApk7qw_82lg.png" /></figure><h3>Problem definition</h3><p>From time to time I need to share files over a local network for instance with a project colleague.</p><p>There are a lot of solutions for this — Samba / FTP / scp. You can simply upload the file to a publicly accessible place like Google Drive, attach it to a task in Jira or even send as email.</p><p>But all this is to some extent inflexible, sometimes it requires preliminary setup and has its limitations (for example the maximum size of the attachment).</p><p>And you want something more lightweight and flexible.</p><p>I always admired Linux for letting me quickly build a practical solution using only built-in tools.</p><p>Say, I often solved the problem mentioned above using the system python with the following one-liner:</p><pre>$ python3 -mhttp.server<br>Serving HTTP on 0.0.0.0 port 8000 ...</pre><p>This command starts the web server in the current folder and allows you to get a list of files through the web interface and download them. You can find more similar tricks here: <a href="https://gist.github.com/willurd/5720255">https://gist.github.com/willurd/5720255</a>.</p><p>There are several inconveniences though. Now to transfer the download link to your colleague you need to know your network IP address.</p><p>For this you can just do:</p><pre>$ ifconfig -a</pre><p>And then from the received list of network interfaces select the appropriate one and manually compile a link like <a href="http://ip:8000/">http://IP:8000</a>. Now it’s ready to be shared.</p><p>The second inconvenience — this server is single threaded. Thus while one of your colleagues is downloading the file the other one will not even be able to see the list of files.</p><p>Thirdly — it is inflexible. If you need to transfer only one file it will be unnecessary to open the entire folder i.e. you will have to perform such gestures (and don’t forget to clean up the garbage afterwards):</p><pre>$ mkdir tmp1<br>$ cp file.zip tmp1<br>$ cd tmp1<br>$ python3 -mhttp.server</pre><p>The fourth inconvenience — there is no <em>simple</em> way to download the entire contents of the folder.</p><p>To transfer the contents of the folder a technique called <a href="https://docstore.mik.ua/orelly/unix3/upt/ch10_13.htm">tar pipe</a> is usually used.</p><p>Example:</p><pre>$ ssh user@host &#39;cd /path/to/source &amp;&amp; tar cf - .&#39; | cd /path/to/destination &amp;&amp; tar xvf -</pre><p>No worry if it’s not clear, I will explain how it works. The first part of the tar cf - . command compiles an archive of the contents of the current folder and writes to standard output. Then the output is transmitted through the pipe via a secure ssh channel to the input of a similar command tar xvf - which does the reverse procedure i.e. reads standard input and unzips to current folder. In fact this is a transfer of archived data but without creating an intermediate file!</p><p>Obviously this approach is “slightly” inconvenience. You need to have ssh access from one machine to another which generally is almost never set up.</p><p>Is it possible to achieve the same functionality but without the problems described?</p><p>Finally let’s formalize what we are going to build:</p><ol><li>A program that is easy to install (static binary)</li><li>Which is able to transfer both the file and the folder with all contents</li><li>With optional compression</li><li>Which allows the receiving party to download the file(s) using only standard *nix tools (wget/curl/tar)</li><li>After launch the program immediately reveals the exact commands for downloading</li></ol><h3>Solution</h3><p>At the <a href="https://jeeconf.com/">JEEConf</a> conference that I attended not long ago the topic of <a href="https://www.graalvm.org/">Graal</a> was raised pretty often. The topic is far from new but finally I had a chance to play with it on my own.</p><p>For those who are not yet in context (do these people exist? oO) let me remind you that GraalVM is a JVM on steroids from Oracle with additional features. The most notable are:</p><ol><li>Polyglot JVM — the ability to seamlessly launch Java, Javascript, Python, Ruby, R, etc. code</li><li>Support AOT compilation — compiling Java directly into a native binary</li><li>A less noticeable but very cool feature: the C2 compiler has been rewritten from C++ to Java for the purpose of more convenient further development. This has already produced noticeable results. The new compiler makes much more optimizations at the stage of converting Java bytecode to the native code. It is able to remove allocations more efficiently. Twitter has reduced CPU consumption by 11% simply by turning on this setting. At their scale it gave a noticeable saving of resources (and money).</li></ol><p>You can refresh your knowledge of ​​Graal <a href="https://chrisseaton.com/truffleruby/tenthings/">in this article</a>.</p><p>For implementation we will use Java so for us the most relevant feature will be an AOT compilation.</p><p>Actually the result of the development is presented <a href="https://github.com/xonixx/serv">in this Github repository</a>.</p><p>An example of usage for transferring a single file:</p><pre>$ serv &#39;/path/to/report.pdf&#39; <br>To download the file please use one of the commands below: </pre><pre>curl <a href="http://192.168.0.179:17777/dl">http://192.168.0.179:17777/dl</a> &gt; &#39;report.pdf&#39;<br>wget -O- <a href="http://192.168.0.179:17777/dl">http://192.168.0.179:17777/dl</a> &gt; &#39;report.pdf&#39;<br>curl <a href="http://192.168.0.179:17777/dl?z">http://192.168.0.179:17777/dl?z</a> --compressed &gt; &#39;report.pdf&#39;<br>wget -O- <a href="http://192.168.0.179:17777/dl?z">http://192.168.0.179:17777/dl?z</a> | gunzip &gt; &#39;report.pdf&#39;</pre><p>An example of usage for transferring the contents of a folder (all files including nested!):</p><pre>$ serv &#39;/path/to/folder&#39; <br>To download the files please use one of the commands below. <br>NB! All files will be placed into current folder!</pre><pre>curl <a href="http://192.168.0.179:17777/dl">http://192.168.0.179:17777/dl</a> | tar -xvf -<br>wget -O- <a href="http://192.168.0.179:17777/dl">http://192.168.0.179:17777/dl</a> | tar -xvf -<br>curl <a href="http://192.168.0.179:17777/dl?z">http://192.168.0.179:17777/dl?z</a> | tar -xzvf -<br>wget -O- <a href="http://192.168.0.179:17777/dl?z">http://192.168.0.179:17777/dl?z</a> | tar -xzvf -</pre><p>Yes, that simple!</p><p>Please note that the program itself determines the correct IP address that serves the files.</p><h3>Observations / Reflections</h3><p>It is clear that one of the goals in creating the program was its compactness. And here is the result achieved:</p><pre>$ du -hs `which serv`<br>2.4M	/usr/local/bin/serv</pre><p>Incredibly, the entire JVM along with the application code fits in just a few megabytes! Of course, everything is somewhat more complex, but more on that later.</p><p>In fact the Graal compiler produces a binary of slightly more than 7 megs. Additionally I decided to <a href="https://github.com/upx/upx">compress it with UPX</a>.</p><p>This turned out to be a good idea since the launch time increase was rather small.</p><p>Uncompressed version:</p><pre>$ time ./build/com.cmlteam.serv.serv -v<br>0.1</pre><pre>real    0m0.001s<br>user    0m0.001s<br>sys     0m0.000s</pre><p>Compressed:</p><pre>$ time ./build/serv -v<br>0.1</pre><pre>real    0m0.021s<br>user    0m0.021s<br>sys     0m0.000s</pre><p>For you to compare here is the launch time “in the traditional way”:</p><pre>$ time java -cp &quot;/home/xonix/proj/serv/target/classes:/home/xonix/.m2/repository/commons-cli/commons-cli/1.4/commons-cli-1.4.jar:/home/xonix/.m2/repository/org/apache/commons/commons-compress/1.18/commons-compress-1.18.jar&quot; com.cmlteam.serv.Serv -v<br>0.1</pre><pre>real    0m0.040s<br>user    0m0.030s<br>sys     0m0.019s</pre><p>As you can see it is two times slower than the UPX-version.</p><p>In general a short starting time is one of the strengths of GraalVM. This as well as the low memory consumption caused a significant enthusiasm around using this technology for microservices and serverless.</p><p>I tried to make the logic of the program as minimal as possible and use a minimum amount of libraries. Such an approach is always recommended but additionally in this case I had concerns that adding third-party maven dependencies would significantly increase the size of the resulting program file.</p><p>Therefore I didn’t use third-party dependencies for Java web server. Instead I used the JDK implementation from the com.sun.net.httpserver.* package. In general using the com.sun.* package is considered as a bad practice. I found it acceptable in this case since I compile it into native code and this means the compatibility among the JVMs is not so important.</p><p>However my fears were completely in vain. For convenience I used two dependencies in the program.</p><ol><li>commons-cli - to parse command line arguments</li><li>commons-compress - to generate a folder tarball and optional gzip compression</li></ol><p>The file size increase was barely noticeable. I would assume that the Graal compiler is smart enough so as not to put all the used jar-files into the executable but only the code that is actually used by the application.</p><p>Compiling into native code on Graal is performed by the <a href="https://www.graalvm.org/docs/reference-manual/aot-compilation/">native-image</a> utility. It is worth mentioning that this process is resource intensive. Say, in my not very slow configuration with an Intel 7700K CPU on board this process takes 19 seconds. Therefore I recommend to run the program during development as usual (via java) and assemble the binary at the final stage.</p><h3>Findings</h3><p>I think the experiment turned out to be very successful. During the development using the Graal toolkit I didn’t encounter any significant problems. Everything worked predictably and consistently. Although it can be not so smooth if you try to do something more complex, for example <a href="https://royvanrijn.com/blog/2018/09/part-2-native-microservice-in-graalvm/">a Spring Boot app</a>. Nevertheless, a number of platforms has already been presented that claim to support Graal natively. Among them are <a href="https://micronaut.io/">Micronaut</a>, <a href="https://microprofile.io/">Microprofile</a>, <a href="https://quarkus.io/">Quarkus</a>.</p><p>As for the further development of the project the <a href="https://github.com/xonixx/serv/issues">list of improvements</a> is already planned for version 0.2. Also, at the moment only building of the binary for Linux x64 is implemented. I hope that this will improve especially since the Graal compiler supports MacOS and Windows. Unfortunately it doesn’t yet support cross-compilation that could really help here.</p><p>I hope that the presented utility will be useful at least to someone from the respected community. I would be glad twice if there are those who want to contribute <a href="https://github.com/xonixx/serv">into the project</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc160feafc19" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cmlteam/develop-a-utility-on-graalvm-cc160feafc19">Develop a utility on GraalVM</a> was originally published in <a href="https://medium.com/cmlteam">CML Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Hackathons Shifted My Mindset Towards Entrepreneurship]]></title>
            <link>https://medium.com/cmlteam/how-hackathons-shifted-my-mindset-towards-entrepreneurship-8b217421e1d2?source=rss----a97506673e5f---4</link>
            <guid isPermaLink="false">https://medium.com/p/8b217421e1d2</guid>
            <category><![CDATA[java]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[travel]]></category>
            <dc:creator><![CDATA[Oleksandr Shchetynin]]></dc:creator>
            <pubDate>Fri, 23 Mar 2018 19:05:52 GMT</pubDate>
            <atom:updated>2018-03-23T20:12:46.522Z</atom:updated>
            <content:encoded><![CDATA[<p>When I’ve participated in my first hackathon I would never imagine it will be a new milestone in my life, and that just one year later I will become an entrepreneur and participating in hackathons throughout the world will be a part of my lifestyle.</p><p>But let’s start the story from the very beginning. It was a summer 2016. I was a software developer at average software company one of those so called “galleys”. My lifestyle was pretty much the same over the past few years. I had a plenty of work during the week, and then every Friday and Saturday nights I was spending in bars, nightclubs drinking and partying with friends to get away from the stress that I’ve got from communication with stupid managers, hours in pointless meetings and bunch of one story point jira issues.</p><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=instagram&amp;url=https%3A//www.instagram.com/p/9wtDrNE2zy/&amp;image=https%3A//i.embed.ly/1/image%3Furl%3Dhttps%253A%252F%252Fscontent-iad3-1.cdninstagram.com%252Fvp%252F7c2140c39c08a601321d4cd6e3386a1c%252F5B3B178E%252Ft51.2885-15%252Fs640x640%252Fsh0.08%252Fe35%252F11939591_1681076642107329_558006376_n.jpg%26key%3Da19fcc184b9711e1b4764040d3dc5c07" width="640" height="630" frameborder="0" scrolling="no"><a href="https://medium.com/media/92306ff49c3286ac4308d6d488a16931/href">https://medium.com/media/92306ff49c3286ac4308d6d488a16931/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=instagram&amp;url=https%3A//www.instagram.com/p/6dc6R3k29S/&amp;image=https%3A//i.embed.ly/1/image%3Furl%3Dhttps%253A%252F%252Fscontent-iad3-1.cdninstagram.com%252Fvp%252F282bf3dc153f4f21f905c823ab926a0e%252F5B429B4B%252Ft51.2885-15%252Fs640x640%252Fsh0.08%252Fe35%252F11374038_104097553278108_1437619045_n.jpg%26key%3Da19fcc184b9711e1b4764040d3dc5c07" width="640" height="640" frameborder="0" scrolling="no"><a href="https://medium.com/media/14edc177457197a927f89b1b9bf06a35/href">https://medium.com/media/14edc177457197a927f89b1b9bf06a35/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=instagram&amp;url=https%3A//www.instagram.com/p/6mY0_Nk2y7/&amp;image=https%3A//i.embed.ly/1/image%3Furl%3Dhttps%253A%252F%252Fscontent-iad3-1.cdninstagram.com%252Fvp%252Fc30140c778d11b485f345fe11031fa50%252F5B398859%252Ft51.2885-15%252Fs640x640%252Fsh0.08%252Fe35%252F11410347_1664898470422132_589052460_n.jpg%26key%3Da19fcc184b9711e1b4764040d3dc5c07" width="640" height="640" frameborder="0" scrolling="no"><a href="https://medium.com/media/dab10009119487c40e2a3964d01e046d/href">https://medium.com/media/dab10009119487c40e2a3964d01e046d/href</a></iframe><p>Sometimes I had vacations and usually I used them to travel or to participate in music festivals.</p><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=instagram&amp;url=https%3A//www.instagram.com/p/BEw47XpE26b/&amp;image=https%3A//i.embed.ly/1/image%3Furl%3Dhttps%253A%252F%252Fscontent-iad3-1.cdninstagram.com%252Fvp%252F2e3741ed0a72bc48d356d11ae64580ce%252F5B75FC7C%252Ft51.2885-15%252Fs640x640%252Fsh0.08%252Fe35%252F12724691_1580317582297481_113198674_n.jpg%26key%3Da19fcc184b9711e1b4764040d3dc5c07" width="640" height="564" frameborder="0" scrolling="no"><a href="https://medium.com/media/e6c4fe471796250928e8bc84a9df2303/href">https://medium.com/media/e6c4fe471796250928e8bc84a9df2303/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=instagram&amp;url=https%3A//www.instagram.com/p/BEmkr15E222/&amp;image=https%3A//i.embed.ly/1/image%3Furl%3Dhttps%253A%252F%252Fscontent-iad3-1.cdninstagram.com%252Fvp%252F6748be23e48611ec0140e4575d29e676%252F5B33903D%252Ft51.2885-15%252Fs640x640%252Fsh0.08%252Fe35%252F12479066_235534380141377_907246314_n.jpg%26key%3Da19fcc184b9711e1b4764040d3dc5c07" width="640" height="491" frameborder="0" scrolling="no"><a href="https://medium.com/media/fc911bc23481278334ddd47ccb01431c/href">https://medium.com/media/fc911bc23481278334ddd47ccb01431c/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=instagram&amp;url=https%3A//www.instagram.com/p/6_C-XeE2xe/&amp;image=https%3A//i.embed.ly/1/image%3Furl%3Dhttps%253A%252F%252Fscontent-iad3-1.cdninstagram.com%252Fvp%252Fde1e06b759784e5661493fd6c512a410%252F5B2C8C54%252Ft51.2885-15%252Fs640x640%252Fsh0.08%252Fe35%252F11875589_1623887621193574_200826004_n.jpg%26key%3Da19fcc184b9711e1b4764040d3dc5c07" width="640" height="640" frameborder="0" scrolling="no"><a href="https://medium.com/media/71d21f5f87cfd42bee88f5be4e915ee8/href">https://medium.com/media/71d21f5f87cfd42bee88f5be4e915ee8/href</a></iframe><p>But that wasn’t what I wanted my life to look like. I realized I became just another office machine that turns coffee into the code and spends spare time not on developing myself as a better person, but just to run away from a day-to-day routine I had.</p><p>I was open to new opportunities and new thoughts at that moment. And here when my friend Johnny appears with that hackathon idea!</p><p>We were sitting Friday summer night with him and his wife in the pub called “Head Trick” eating some crawfish and drinking a bear. Then he told me about that hackathon the company he was working on at the moment holding — it supposed to be a one day <a href="https://leanpoker.org/">“Lean Poker” hackathon</a>, lean word was in hype back at those days. The objective was to build a bot (bot word was also popular back then :) ) that will beat all the other bots in the poker. My friend Johny used to be a semi-professional online player few years before, when online poker still not prohibited in the US. Yeah it was gold times for Johny!</p><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=instagram&amp;url=https%3A//www.instagram.com/p/2EQmWRE28b/&amp;image=https%3A//i.embed.ly/1/image%3Furl%3Dhttps%253A%252F%252Fscontent-iad3-1.cdninstagram.com%252Fvp%252F095bc7f2c182217872e42dec1a4cb655%252F5B744A3F%252Ft51.2885-15%252Fe15%252F11192984_510822779066317_644226696_n.jpg%26key%3Da19fcc184b9711e1b4764040d3dc5c07" width="640" height="640" frameborder="0" scrolling="no"><a href="https://medium.com/media/05417b91c7aadab35eb4bf8972f635d2/href">https://medium.com/media/05417b91c7aadab35eb4bf8972f635d2/href</a></iframe><p>His responsibility during the hackathon was in writing “smart” poker strategies, and my responsibility was to find at least one more developer and together build a bot infrastructure to wire-up Johny’s strategies inside.</p><p>So first thing I did — I called my friend, his name was Vlad, he was working with me for a <a href="http://www.aliceapp.com/">young successful startup</a>. That startup was an awesome place to be, it was like a Pulp Fiction, and Vlad was like Mr. Wolf there. Together with Vlad and Johny we formed the team — “Flash Boys”.</p><p>The hackathon started, our bot didn’t work. Everything was against “Flash Boys”. All those fancy node.js, python, jango-shmango hipster mess were easy to bootstrap and start going, and we were struggled with some servlet peace of shit stub organizers provided.</p><p>We were at the last position, but then once mr. Wolf fixed some NPEs and Johny finally was ready to put his “smart” strategies. Our bot quickly went all the way up to the second position in the rank. I was quite sure we will win, but unfortunately the “Lean Poker” hack ended before our bot could make it through to the winner.</p><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=instagram&amp;url=https%3A//www.instagram.com/p/BHuLhcGjUsL/&amp;image=https%3A//i.embed.ly/1/image%3Furl%3Dhttps%253A%252F%252Fscontent-iad3-1.cdninstagram.com%252Fvp%252F9071801565c30234f40640e4acb10c93%252F5B47A176%252Ft51.2885-15%252Fs640x640%252Fsh0.08%252Fe35%252F13628235_1225731770770527_1062457398_n.jpg%26key%3Da19fcc184b9711e1b4764040d3dc5c07" width="640" height="334" frameborder="0" scrolling="no"><a href="https://medium.com/media/ca5a377a27d9a240be8eb99db606639f/href">https://medium.com/media/ca5a377a27d9a240be8eb99db606639f/href</a></iframe><p>That experience was something totally new to me. Everything — from team formation, working together with strangers you’ve never met before, to presenting your solution on public judgement at the end. The ways you get used to write a code during your usual scrum or whatever process doesn’t work here at hackathon! You need to move forward really fast. You need to focus on really important things and leave all the noisy things behind. That’s part of success here. You need to fail fast, listen to the people around and absorb as much details as possible that can help you to move forward. And there is this energy! Competing energy, but still it’s a good energy. Your competitors are not your enemies, they are your partners and teachers, but still you have to beat their asses!</p><p>After this hackathon there were a lot more, some of them were epic wins, and some were epic fails, but still epic. But this is another story, and this story is about me losing virginity with my first hackathon. To be continued …</p><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=instagram&amp;url=https%3A//www.instagram.com/p/BcN45Y2lbdd/&amp;image=https%3A//i.embed.ly/1/image%3Furl%3Dhttps%253A%252F%252Fscontent-iad3-1.cdninstagram.com%252Fvp%252F6ee5efa0aa3a3c613e0f62bfdf2a6221%252F5B3824DA%252Ft51.2885-15%252Fs640x640%252Fsh0.08%252Fe35%252F24254409_2046240338928869_74287283359973376_n.jpg%26key%3Da19fcc184b9711e1b4764040d3dc5c07" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/de79ab73207c7c17e47025c40ed4a0cb/href">https://medium.com/media/de79ab73207c7c17e47025c40ed4a0cb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b217421e1d2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cmlteam/how-hackathons-shifted-my-mindset-towards-entrepreneurship-8b217421e1d2">How Hackathons Shifted My Mindset Towards Entrepreneurship</a> was originally published in <a href="https://medium.com/cmlteam">CML Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>