<?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 Ivailo Ivanov on Medium]]></title>
        <description><![CDATA[Stories by Ivailo Ivanov on Medium]]></description>
        <link>https://medium.com/@dajungle?source=rss-6a19d7fdf660------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*07Ux-A6nFwOzzs-UMCQj5g.jpeg</url>
            <title>Stories by Ivailo Ivanov on Medium</title>
            <link>https://medium.com/@dajungle?source=rss-6a19d7fdf660------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 16:31:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dajungle/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[A (semi) scientific ChatGPT Test]]></title>
            <link>https://medium.com/@dajungle/a-semi-scientific-chatgpt-test-b7aeac8ae290?source=rss-6a19d7fdf660------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7aeac8ae290</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Ivailo Ivanov]]></dc:creator>
            <pubDate>Sun, 19 Feb 2023 10:20:31 GMT</pubDate>
            <atom:updated>2023-02-19T10:53:37.718Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/305/1*wfPUar59VsDcOGHxpi1_Zw.png" /><figcaption>La Jangada by Jules Verne. Source: <a href="https://www.svvruellan.com/">https://www.svvruellan.com/</a></figcaption></figure><p>Yeah, I know! Everyone writes and talks about ChatGPT, prompts, how to ‘hack’ it and how to use it in the mundane daily tasks. Some people are going a bit far by checking whether it is conscious, asking for example “Do you have a soul?”.</p><p>It’s content (and variations) generation capabilities are astonishing. Throw a few keywords or bullets and it can generate a whole story, even sometimes meaningful. I attend to ChatGPT discussions several times per day. Somehow just find myself in the middle of such discussions between different people an colleagues who share excitement or concerns about the future of their jobs. It is THAT kind of buzz in the IT crowd.</p><p>What you would do if you have 30 minutes couch time on a Saturday afternoon with a cup of coffee?</p><p>Correct Play with ChatGPT. (And that’s what I did.)</p><p>Just a little background first: My experiments with the GPT-3 API started a couple of years ago during COVID lockdowns and I was really impressed by the results. Even made a couple of small apps analyzing e-mail content and generating innovation ideas with predefined dictionary. All of this was a fun game and and the hype wasn’t at current scale where literally everyone talks about this technology. The second important thing to know before explaining the experiment is that I love reading fiction books. I love them since a little kid and read a lot of stuff especially between the age of 10 and 18. One of the books which was a huge effect on me as a kid was “Eight Hundred Leagues on the Amazon” which was translated in Bulgarian using its second title “La Jangada”. The main story line in the book is about decrypting an encrypted letter which made me playing with ciphers for weeks after reading it scratching letters with a pencil making piles of paper with encrypted messages.</p><p><strong>The Experiment</strong></p><p>First of all most of the prompts were (a bit) sloppy so some people might criticize their quality and the level of detail passed to define the context. And they will be correct. It is a ‘couch test’ after all! The main idea was to check three things:</p><ol><li>Simple “creative” task following instructions.</li><li>Fact check + extraction of a concept from a book.</li><li>Apply the extracted concept to another creative task.</li></ol><p>Let’s play with an extremely simple cipher:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/911/1*FF5xUuvIbjjjhF10pInsMw.png" /><figcaption>Caesar Cipher</figcaption></figure><p>Okay. That’s correct. Even the description looks nice. But! Let’s be realistic, the string “hello world” is widely used and the probability someone gave it as an example somewhere in The Internet is quite high (Even if I didn’t check personally, too lazy during the couch test :)). Let’s try something obvious:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/893/1*stW_vxKxgMDqmW5oyw4Cng.png" /><figcaption>Caesar cipher again.</figcaption></figure><p>The description makes sense but the result is obviously wrong. ABCD should become BCDE. Our ‘smart’ friend explains it correctly but makes a mistake in the result. In fact the first group of letters completely wrong. I deliberately used the letters in reverse order. It got the second part right, maybe also found it as an example somewhere.</p><p>Let’s see how it works with the fact check + extraction. Now that is a really hard one:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/906/1*MNCP3Qi7-XeP08-Ss-yCLw.png" /><figcaption>Search for book content.</figcaption></figure><p>Wrong. Wrong and wrong. First of all there is no such book written by Jules Verne “The Amazon Queen”, second “The Child of the Cavern” is a completely different book taking place in Scotland and has nothing to do the Amazon jungle. ChatGPT is trying to be smart and makes up stuff, but it can’t fool me! Another sip of coffee later:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/908/1*jfHqT2ZSkEGqp-bPtOBmUw.png" /><figcaption>Made up stuff.</figcaption></figure><p>Oh my. Wrong again. The Verne cipher and “the sequence” has nothing to do with the book. The result code encoding ‘Hello World’ is correct but it comes from a completely different book, while in La Jangada the encryption follows a different algorithm. The sequence above is completely made up I-L-P-W-B-K-V-X-A-D-T-M-R-G-N-O-H-F-J-U-Q-Z-Y-E-S and translates to nothing. I know that it’s a bit twisted experiment but I wanted deliberately to make it pull out a ‘fact’ or a context and apply it to something else. It got the facts wrong and additionally generated some things which should make sense to the human observer. And in reality they do if you don’t know the subject well. Scary, right?</p><p>After it failed with the extraction and facts and my coffee was almost finished, I did a couple of final attempts:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*o50dfUUqk5nHIdyKbjjGGw.png" /><figcaption>Made up again.</figcaption></figure><p>Well I must admit my prompt was a bit stupid. I had to explain that each digit should be applied to each letter. Although, ChatGPT … Is not a simple substitution cipher! I told you it is not! :) Now let’s try again:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*N98yIyn_-nvxzNe2-LYpbQ.png" /></figure><p>The encrypted message is obviously wrong. Although the explanation is really good! The main problem is that the explanation doesn’t follow the result. In the real world if we want to apply ChatGPT we should be extremely careful in the result, even if the explanation is a spot on. Anyway I’ve tried also other tabular prompts trying to make real sense of this simple algorithm:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*GeR_360xku8Ag5Kc1Hqg0Q.png" /><figcaption>Cipher table.</figcaption></figure><p>Looks kind of OK. The thing is that some of the sums are correct, others are not, also some of the result letters are correct, others are completely random. A small example is the third column where 12 + 2 = 14 (correct) but the 14th letter in the alphabet is N, not O. In column 9 , 18+1 is not 21 and the 21st letter is not V.</p><p>I’ve shortened the example, there were multiple prompts for the tabular format which had mistakes on random places. Each time I got an apology and another semi-correct variation. Even if you run it twice you will get <strong>different mistakes</strong>.</p><p><strong>Conclusion</strong></p><p>ChatGPT is an amazing technology. It is important to know though that it is a Large Language Model which calculates probability of a certain word (or a number?!) to appear after another. It is not an AGI (General Intelligence) even if it can be quite convincing in many cases. It invents stuff which makes sense for the untrained eye which is <strong>dangerous </strong>especially when the result is loaded with booby traps<strong>. </strong>Most of the time we would use it we wouldn’t be are not lying on the couch sipping coffee but trying to speed up our work and automate tasks. Keep that in mind and use it to <strong>generate</strong>! And read “La Jangada”, amazing book of it’s time!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7aeac8ae290" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why you must modernize your applications]]></title>
            <link>https://medium.com/@dajungle/why-you-must-modernize-your-applications-3f04a42b7863?source=rss-6a19d7fdf660------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f04a42b7863</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[future-of-work]]></category>
            <dc:creator><![CDATA[Ivailo Ivanov]]></dc:creator>
            <pubDate>Fri, 28 Oct 2022 08:38:02 GMT</pubDate>
            <atom:updated>2022-11-07T14:57:22.160Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why you must modernize your applications?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ORuKPPaJkS2YeBKX6BIMig.png" /><figcaption>Source: Adobe Stock Photos.</figcaption></figure><p>The corporate world is well into a 30+ years digitalization journey. Many would argue about the timing but somewhere in the mid-late 80s the computer became a ‘must have’ tool for most companies. Used for performing calculations, data storage, communications, process modelling … An endless list of things which could be done faster and better. The original concepts of many software tools such as word processors and spreadsheets originate from these times. Of course their current versions are enormously different, more powerful and user friendly from their ‘granddads’.</p><p>This is how Microsoft Word looked like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*Sct4u8TSfnvudNoc" /><figcaption>MS Word for OS/2 and DOS</figcaption></figure><p>We all know how it looks (and works) now after 30 years of modernization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6N_Cf1JOuSUCkpZn" /><figcaption>MS Office 365</figcaption></figure><p>There is a reason for this difference. The hardware, operation systems and companies have evolved. But most importantly: people evolved. They have higher expectations from a software tool. They want things to happen instantly and with a minimal effort. Can you blame someone who gets frustrated by slow loading times and hundreds of unnecessary clicks if she spends tens of hours weekly with an outdated legacy system designed in the 90s? The business loses twice: one time because of a slow execution and second — due to frustrated personnel.</p><p>Thinking about software adoption, an average business uses tens of software tools on a daily basis. Out of the box tools such as MS Word, MS Excel, customized solutions as CRMs and ERPs or completely custom systems modeling particular business cases for particular industries. In mature companies being around for a long time many of these systems might be way behind current standards. Some of you would ask: “Why would that be an issue? We have perfectly good systems and besides we have better ways to spend our budgets instead of throwing a pile of money to replace working software.”</p><p>And this is a completely valid point, although I would agree to disagree and give you at least 5 good reasons why a business would want to modernize its systems:</p><p><strong>Long term support</strong></p><p>The long term support is crucial for mission critical applications. Imagine systems running the processes in a machinery factory, a big warehouse, taxi company or a medicine manufacturer. If a software system fails, there could be hundreds or if not thousands of people who won’t be able to do their jobs or won’t get timely service. The financial and reputation losses can be significant. Yet, many companies rely on systems which are based on outdated operating systems, use outdated software components and depend on the ‘mercy’ of the software vendors who are usually not really keen to provide support for something they developed 15–20 years ago. Even if they would do it, they will charge a pile of money to keep these systems ticking. Time is not an ally in this case and planning for business continuity must not be swept away under the rug. One day the IT managers can wake up and find out that a critical system has stopped working and there is nobody there who is familiar with the tech or the software vendor doesn’t want to support it anymore.</p><p><strong>Adding new features or making software changes</strong></p><p>With an aging system it is harder and harder to tweak functionalities or add a small feature here and there. That might require old software tools, old software libraries and also specific knowledge about how the system works. A lack of flexibility when adding features or changing functionality might be really costly for the business. In some cases there are also legislative changes which lead to software changes which are mandatory. What would happen if the company fails to comply? An explanation like ‘We can’t change our legacy system’ wouldn’t do much in front of the authorities.</p><p><strong>Data Security</strong></p><p>There are people with a mission in life to “break things”. Some of them do it just to prove their skill, others to steal data or money, third — just for fun. I wouldn’t say it is particularly funny if somebody breaks into a corporate system, especially a vital one. Hackers regularly find holes in widely used libraries or services which lead to patches every now and then. Unfortunately at some point old libraries and frameworks are excluded from this security maintenance and the systems might be left vulnerable. In order to stay on the safe side, the IT managers must know the software dependencies and their planned retirement. An application modernization must be done to reduce the security risks.</p><p><strong>New Generation of Users</strong></p><p>We’ve mentioned above the frustrating loading times and the outdated and confusing user interface. A generation grown up with touch screens and shiny UX of the social networks is already in the labor force. It can be a cultural shock for a 20-something person to be asked to work with a desktop software running on Windows XP or a custom Microsoft Access based Warehouse application. It wouldn’t be an issue for the people who spent the last 20 years of their professional career at the PC but the businesses must do something to keep Gen Z productive and motivated. Providing them with the tools they are used to is one of the key things.</p><p><strong>New Generation of Programmers</strong></p><p>The final of the five reasons to modernize is the actual people who would support the systems. We have talked about the long term support and this support is done by actual people. People have their career plans: what technology to learn to stay competitive, what are current trends and what would be future proof. Learning old tech doesn’t make much sense for the young programmers and the older ones knowing the legacy frameworks and libraries either moved to managerial positions or even maybe already retired. That opens a massive gap in the systems support and maintenance which grows by the day.</p><p>Of course there is plenty to say and discuss about each of these topics and I am barely scratching the surface of each of them. The key thing is to ignite a small spark of thinking towards business continuity and how important it is to address the risks for the organizations and take preventive actions towards systems modernization.</p><p>Some of you might say: That really makes sense. Where to start from?</p><p>A <a href="https://www.bgosoftware.com/services/product-discovery">discovery session</a> about the modernization options is always a good idea. Also <a href="https://medium.com/@dajungle/5-key-ingredients-of-a-successful-software-delivery-343094c34ad6">here</a> you can find some ideas on how to guarantee the project success.</p><p>Keep modernizing! :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f04a42b7863" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 key ingredients of a successful software delivery]]></title>
            <link>https://medium.com/@dajungle/5-key-ingredients-of-a-successful-software-delivery-343094c34ad6?source=rss-6a19d7fdf660------2</link>
            <guid isPermaLink="false">https://medium.com/p/343094c34ad6</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Ivailo Ivanov]]></dc:creator>
            <pubDate>Fri, 05 Aug 2022 12:12:02 GMT</pubDate>
            <atom:updated>2022-08-05T12:12:02.612Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fa0MBQAilEh_i2XsfUfaqQ.jpeg" /><figcaption>The project will fly … Or not. Image by Author.</figcaption></figure><p>“Software is eating the world” as they say, and that’s not far from reality. It is difficult to imagine a business that doesn’t require software to run. Even traditionally “offline” businesses can’t exist without a number of systems or at least without the “ruler of them all” a.k.a. Microsoft Excel. These businesses already learn a lesson: “If you don’t go digital<em>,</em> your days are counted.” Aside from the established companies, software startups spawn literally every minute, each with another fancy idea for world domination with yet another software product. They are bold, motivated, and in many cases jump “all in” into their endeavors. Unfortunately, the <a href="https://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect">Dunning-Krueger effect</a> is often applied in full… What then?</p><p>Projects fail. Sometimes no matter how hard you try, the whole thing is doomed. What makes it even worse is that for all bystanders failure is quite obvious, yet the team is happily steering the ship to the abyss.</p><p>There can be hundreds of reasons that might lead to a failure, but I’ll try to share a few key things which can dramatically increase the chances of success (and change the ship’s course to a jolly Caribbean Island).</p><p>Make sure you don’t miss these 5 ingredients along with everything else in the project “pot”.</p><h3><strong>1.</strong> <strong>Engineers wearing developer hats</strong></h3><p>When you ask a software developer what they do, you often get: “What do you mean? I am an engineer!”, although people rarely understand what being an engineer truly means. When an engineer designs a machine (<em>or a software product</em>) the thinking should be far beyond using a fancy technology, coding a smart API endpoint, designing some complex class hierarchy, or following design patterns by the book. I’m not saying that it’s bad doing so; nevertheless, importance lies in the real engineering part.</p><p>Do the developers ask themselves:</p><p>● Do I understand the true purpose of the functionality I’m building?</p><p>● How does it connect with the other parts of the system?</p><p>● Where does it stay in the whole use case and business process?</p><p>● What if this functionality fails at runtime? <br> <em>(Trust me, at some point it will.)</em></p><p>● If it fails, how do I ensure that the user has an alternative way to get things done? Or if it is mission critical, do I show the right message which tells them what to do next?</p><p>● If I were to use the interface I am building, would it be easy or will it make me miserable?</p><p>● As an engineer, how can I make the user’s life easier and design a machine (software) that rarely fails, that saves time and effort, and that delivers value?</p><p>An “engineer, wearing a developer’s hat” means that they understand that <strong>technology is merely a tool</strong>. It is great to master your tool, but it is far greater to learn how to deliver a product that generates more value than it causes support burden and headaches. Practically no one cares about your fancy code and design patterns if the result sucks.</p><h3><strong>2.</strong> <strong>A technical leader who cares</strong></h3><p>I wrote about this topic in my <a href="https://medium.com/@dajungle/cto-as-a-service-driving-projects-forward-804fa4ce0f10">CTO as a service</a> article and having a leader who is tech savvy and truly cares is the most important factor. Software engineering is a complex task. Every day there are tens or hundreds of little issues to solve, obstacles to overcome, and decisions to be made. Who is the project’s technical leader? When you ask them about the project, do they think about it as ‘their baby’? Do they care if it suffers, if features are delayed, if the interface is ugly and even useless on some screens, or if developers write lousy code? If there is a production issue, do they wake up at 3 am and go debugging and patching stuff?</p><p>If the person leading the project is not like that, the risk of failure is high! Better go find someone else. Someone with passion, ownership, and care. Remember that such leaders are priceless. They are the true leaders; those who lead by example and without the need for fancy titles. Their success speaks for itself.</p><h3><strong>3.</strong> <strong>Transparency (not isolation)</strong></h3><p>In many cases (software) teams are quite detached from the end result of their work. Kept in a silo or completely removed from the actual users and their pain points in another way. Companies also tend to keep the commercial performance of products a secret from the tech team. It’s a common mistake that can have a devastating impact on the team morale and motivation. The progress can be great, but the team might be flooded with complaints, hard push from project managers, product owners or managers who just want to ‘squeeze more’.</p><p>An even worse scenario could be when the project gets stuck. Deadlines are not met, users are horrified or worse — indifferent to the monster you’ve created, budget is depleted, and there are tons of bugs in the backlog. Despite that you may tell the team that they’re doing a great job and repeat the ‘we are successful` mantra.</p><p>Just be honest. Show that negative feedback to the development team. Brainstorm together on possible improvements. Occasionally put a developer on a 1st line support position so they get true, unfiltered feedback from the users. Tell them that sales are not good (or that they are — depending on your situation). Praise the good results and distribute positive feedback. Appreciate proactivity and good ideas.</p><h3>4. <strong>A walking skeleton</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7tD4zpDC9t2P44xSiRKEiA.png" /><figcaption>Pay attention to the green circle. This is when the skeleton is born and learns to walk. Image by <a href="https://www.bgosoftware.com/">BGO Software</a>.</figcaption></figure><p>Most people in the software industry are familiar with the concepts of ‘Design Thinking’, ‘Lean’, ‘Agile’ etc. You must be agile! You can’t just use ‘waterfall’; that’s wrong and outdated. Scrum sprints, story points, implement it all… Following the rituals is somehow a guarantee that you will deliver. There is something about agile/lean that is far more important than strict iterations and ‘ticking’ scrum meetings. It is simple and it is about validating (as early as possible) that you are on the right track. Everything else is a detail. Every software project implements a real-life process or multiple processes. Start there. Go through these steps. Take these alternative roads. Achieve a result.</p><p>When starting the project make sure you <a href="https://www.bgosoftware.com/services/product-discovery">develop, or even better — prototype</a> a bit of every necessary step to cover the end-to-end process as early as possible. It might be ugly; it might lack hundreds of corner cases or details, but it is critical to allow someone to go through the entire process and confirm that it fits the business case.</p><p>This is the walking skeleton. You should use this ancient craft to animate it and get it to walk. No flesh, no clothes, no fancy accessories. You’ll add these later. Do not spend the first 5 sprints implementing 5 different login providers for your e-shop instead of developing one type of login, one product listing, basic order, basic payment, and shipping. Get the basics right so I user can have a complete process. Then add bells and whistles, such as clothing and jewelry to your creature.</p><h3><strong>5.</strong> <strong>No Overengineering</strong></h3><p>The last rule is (somehow) related to the walking skeleton but it’s also part of the developer’s psychology. There is even a term for it: <a href="https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it">YAGNI</a> (stands for You Aren’t Gonna Need It). Every feature must be developed no sooner than when it is needed. Period. For example, why would you spend weeks or months on complex scaling features when you still have zero users, and it is not clear that this product is commercially viable or that anyone would use it? Or why would you develop a micro-services architecture for an internal company tool with 20–30 users max, using a 10-tables database that would never grow bigger than a few hundred megabytes?</p><p><em>The true engineering skill is to do what is needed at the start for an easy separation of concerns at a later stage.</em> For instance, a smart modular monolith is usually a great start in most cases that might end up being split into microservices at a later stage (which also might never happen). <em>The second skill is to make it simple and easy to maintain.</em> Using fancy architecture without the actual need will lead to a steep learning curve for new people in the team. Overengineering in the direction of using complex patterns for a simple case is another thing to keep an eye on.</p><p>***</p><p>While these five key rules might not be enough to deliver successfully, ensuring they are followed would act as a high-return insurance covering project delivery risk. Maybe I am oversimplifying and missing a critical element? Feel free to comment and share more valuable insights!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=343094c34ad6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CTO as a Service: Driving projects forward]]></title>
            <link>https://medium.com/@dajungle/cto-as-a-service-driving-projects-forward-804fa4ce0f10?source=rss-6a19d7fdf660------2</link>
            <guid isPermaLink="false">https://medium.com/p/804fa4ce0f10</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[tech-startups]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[services]]></category>
            <dc:creator><![CDATA[Ivailo Ivanov]]></dc:creator>
            <pubDate>Fri, 22 Jul 2022 08:54:47 GMT</pubDate>
            <atom:updated>2022-07-22T10:35:53.182Z</atom:updated>
            <cc:license>http://creativecommons.org/publicdomain/zero/1.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gCWKVgrJWWO86agMIRs_ZQ.jpeg" /><figcaption>That’s me. Still a person, not a service.</figcaption></figure><p>It’s the age of everything-as-a-service. Businesses nowadays must constantly optimise to remain competitive: cut unnecessary expenses, reduce maintenance costs, deliver more with less, you name it. This is the perfect environment for no-commitment easy-to-get-out-of business relationships. Especially if you are running a startup, struggling with deliverables between investment rounds, and spending sleepless nights worrying, “Are we going to make it?”</p><p>As a CTO myself, my reaction to the concept of CTO as a service when I was first presented with the idea was kind of comical. Outraged, I jumped from my chair, objecting: “What’s this nonsense! I am the CTO, I have enough on my plate, and you want to do what? Sell ME as a service?”.</p><p>My rage was apparent. We, tech people, are funny like that, and you don’t need to try hard to offend us — we’ll react strongly even to the slightest hint of diminishment.</p><p>The conversation continued in a heated manner for a bit longer, but 10 minutes in, the cogs in my brain started moving. From there and on, I was easily persuaded. That person was onto something. Let me explain.</p><p>Imagine a startup founded by businesspeople and domain experts without a strong IT co-founder. They have a brilliant idea but can’t execute it without spending tons of cash on a senior IT person or, worse, without giving away some equity to get a techie to join them.</p><p>Imagine also a project manager in a corporation who is struggling with the coordination of the in-house staff, dealing with contractors, translating business requirements to technical deliverables, and the piles of other tasks that require technical expertise.</p><p>What if those two had a CTO? And I don’t mean a high C-level fellow with ceremonial duties. I mean a solid, hands-on IT professional — a Swiss army knife type of person with expertise in coding, development processes, and software architecture. Also, someone who has <em>actually delivered</em> IT projects before and knows what it takes. A person like that is a game-changer.</p><p>I have seen many failed IT projects over the last 20 years. They all had similar profiles and lacked the same ingredients, but it was never funding — it was something else. When I realised what it was, it became clear that we’ll be expanding our portfolio, and this concept was to be included.</p><p>There is, of course, a mountain (or a bumpy road if you prefer) between talk and do. How do we deliver the most value to customers? How do we create a premium service of this type and offer it on a large scale without hiring thousands? What activities do we need to include? The list of questions was endless.</p><h3>The Four Pillars</h3><p>After significant brainstorming, many cups of coffee, customer interviews, and several service trials, we decided to cover four aspects of the software project delivery process. These aspects are the foundation elements of the desired foal that sounded simple: “To drive the project forward.”</p><p><strong>1.</strong> <strong>Tech Consultancy</strong></p><p>· Advice on software development process</p><p>· Assistance with the evaluation and selection of software tools and platforms</p><p>· Help with good system security practices</p><p>· Attendance of meetings as a technical representative as part of team</p><p>· Implementation and process improvement: CI/CD, support levels, project management methodology.</p><p><strong>2.</strong> <strong>Product/Project</strong></p><p>· Technology stack(s) evaluation and choice</p><p>· Systems architecture advice/decisions (including proposals and documentation)</p><p>· Collaboration with the Product Owner on the product roadmap scope, schedule, and priorities</p><p>· Assistance with functionality — UX improvements, business features</p><p>· Help with estimates and work effort evaluation</p><p>· Point of contact for system support</p><p>· Code quality guardianship</p><p>· Establishment of product technical knowledge retention (training, knowledge base, others)</p><p><strong>3.</strong> <strong>Product Team</strong></p><p>· Assistance with the decisions on team size, structure, positions, and all other staffing requirements</p><p>· Assistance with interviewing new team members</p><p>· Team skills evaluation</p><p>· Team performance and corrective actions</p><p>· Team coaching and individual members’ personal development</p><p><strong>4.</strong> <strong>Relationships</strong></p><p>· Assistance with project/team budgeting and financial planning</p><p>· Act as a point of contact between the customer and third-party technical contractors (including mediation and issue resolution)</p><p>· Product success management</p><h3>It’s not a person; it’s a team!</h3><p>Once we broke the service down into deliverables, it became clear that “CTO as a Service” couldn’t possibly be done by a single person. Naturally, the customer would have a single point of contact (sanity must be retained), but that person must have a team behind them. The team includes a senior IT architect, a project manager, a business analyst, and a domain expert for all technical and business-specific needs. All in all, the customer “sees” one but gets the value of many. Sounds perfect, right?</p><p>We finally nailed it. It is an incredible relief for the project owner to know that they have a tech specialist on their side who truly cares. That’s why the core value of the “<a href="https://www.bgosoftware.com/services/cto-service">CTO-as-a-service</a>” concept is ownership and dedication. It’s like renting your very own IT superhero for as long as you need them. I suppose when it comes to IT services, it doesn’t get better than that.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=804fa4ce0f10" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>