<?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 1Ci on Medium]]></title>
        <description><![CDATA[Stories by 1Ci on Medium]]></description>
        <link>https://medium.com/@1Cinternational?source=rss-e4ac2fb667ae------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*VaeoGFcY1dc1YN3EJ3uQQg.png</url>
            <title>Stories by 1Ci on Medium</title>
            <link>https://medium.com/@1Cinternational?source=rss-e4ac2fb667ae------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 21:09:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@1Cinternational/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[How to Choose Cost-Effective Software for Business Automation]]></title>
            <link>https://medium.com/yellow-universe/how-to-choose-cost-effective-software-for-business-automation-18c5a378f759?source=rss-e4ac2fb667ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/18c5a378f759</guid>
            <category><![CDATA[software]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[business-automation]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[1Ci]]></dc:creator>
            <pubDate>Thu, 06 Sep 2018 09:50:02 GMT</pubDate>
            <atom:updated>2018-09-06T09:50:02.948Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t7sM4fxibFbzO3eAkbx3Wg.jpeg" /><figcaption><em>Image credit: </em><a href="https://unsplash.com/photos/JW6r_0CPYec"><em>Unsplash</em></a></figcaption></figure><p>Before making a final decision about starting using a particular automation platform it is crucial to perform a cost-effectiveness analysis. New software should lower costs and maximize the revenue of the business.</p><p>It is tough to build such a system in-house, however choosing the right one from multiple options from third-party vendors is not a piece of cake as well. There are numerous potential costs involved including the price of the product, its implementation/integration in current infrastructure, employees training, etc.</p><p>Today we will talk about what factors to consider while choosing automation software in order to reduce the potential cost of ownership (TCO).</p><p><strong>Architecture and a tech stack</strong></p><p>Overall quality of work of software is measured by the system’s architecture. This is where most problems of in-house programming are laying, however, such issues can be met when dealing with a software from the third-party vendor. Before rushing into migration to the new system or implementing new cloud service into current infrastructure it is a good idea to assess its architecture and tech stack.</p><p>Nowadays, the main values of any technology platform are:</p><p>· The flexibility that allows aligning technology with the changing business requirements.</p><p>· An opportunity to integrate software with third-party systems.</p><p>An example of such a platform is <a href="http://bit.ly/2NSusK4">1C:Enterprise</a>. It is a framework incorporating multiple pre-set business objects and libraries, and a runtime environment with built-in integration features at the same time.</p><p>Data storage is also one of the most important aspects here. There should be documentation available on how data is stored in a new system, what kind of operations you can do with it, what databases does the system support. If there are few opportunities in working with data and the system does not support your preferred database type, it means that using this software may incur additional costs.</p><p>The technology stack is also very important. If the product is created using outdated technology (like, say, Perl), it is a bad sign. Ask yourself, how the team behind the product will find good developers for such outdated technologies in the future. It almost for sure will harm the development process and overall quality of the software. And bad software could be very costly to use.</p><p>Basically, tech stack should:</p><p>· Be flexible enough to easily modify the functionality of the product.</p><p>· Have a wide range of built-in integration tools.</p><p>· And an active and evolving community of supporters and developers as it is a perfect source of human resources.</p><p><strong>Support and community</strong></p><p>When dealing with systems that have big impact on business and its results, it is crucial to have an opportunity to solve problems quickly. This means good support is one of the main factors affecting the final choice of the software.</p><p>You can understand the quality level of the customer care by asking several questions. Whether there is a 24x7 support or not? Does the customer care team use a tracking system and are there any SLA and standards concerning reaction time in place? If there are little obligations taken by developers, they mostly for sure will fail to provide good support. This opens a room for potential losses: if your financial automation system is broken, it is a huge problem.</p><p>A vibrant community of users around a certain product is also nice to have. Tons of common questions are usually answered by members of such communities on dedicated forums or in social media. It is often faster to just google for the answer rather contacting support, as it saves time and resources. If there is no active community around software you are assessing, it is a huge drawback.</p><p><strong>Real price</strong></p><p>The last but not least thing to analyze is pricing itself! The total cost of ownership consists of multiple factors like licensing, implementation, support and upgrade. Also, there are tons of options for how software can be priced nowadays, and navigation through multiple billing plans might be confusing.</p><p>If you are about to use some free system, examine is it real or just a marketing: software might be free, however its updates or support very expensive. The same with paid tools: compare several products to find out the list of options you can get for a certain amount of money.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18c5a378f759" width="1" height="1" alt=""><hr><p><a href="https://medium.com/yellow-universe/how-to-choose-cost-effective-software-for-business-automation-18c5a378f759">How to Choose Cost-Effective Software for Business Automation</a> was originally published in <a href="https://medium.com/yellow-universe">Yellow Universe</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Change Software and Don’t Make Your Users Angry]]></title>
            <link>https://medium.com/@1Cinternational/how-to-change-software-and-dont-make-your-users-angry-8f2479d5adf9?source=rss-e4ac2fb667ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f2479d5adf9</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[development-tools]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[1Ci]]></dc:creator>
            <pubDate>Fri, 31 Aug 2018 11:17:38 GMT</pubDate>
            <atom:updated>2018-08-31T11:17:38.292Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UUhzlMHfMpjkJnv9Q-eKWw.jpeg" /></figure><p><em>Image credit: </em><a href="https://unsplash.com/photos/tEMU4lzAL0w"><em>Unsplash</em></a></p><p>Redesigns or major software fixes and updates are often accompanied with a flair of negative comments. Users, who should be thankful to software developers that created tools they use and are working hard to make them better turn angry. But why it is like this, and how to change your product without such problems?</p><p><strong>“People do not like change”</strong></p><p>It is a common belief that people mostly do not like changes and prefer things to remain the way they have used to. There are lots of psychology research made to bake this theory. Scientists explore people’s preferences and tell us that #1 predictor of happiness is <a href="http://www.psychologytoday.com/blog/bouncing-back/201106/the-no-1-contributor-happiness">a sense of control</a>.</p><p>In this thought framework, it seems obvious that it is almost impossible to introduce any changes in your product in a way that won’t get users angry. You know how to do the product better, but if you change it people will feel they are losing control and have to re-learn everything from the beginning.</p><p>No matter product is now really better, customers will go mad. It’s just psychology. So you may decide to better explain changes with beautiful overlays or tutorials so that they understand what elements were moved, and why some features were released while others killed. Seems logical, but the interesting thing here is that in real life it’s just all wrong.</p><p><strong>People do not hate change, they hate problems</strong></p><p>As Christina Wodtke, UX expert, <a href="https://medium.com/@cwodtke/users-dont-hate-change-they-hate-you-461772fbcac7">stated</a> in her brilliant article, “users don’t hate change, they hate you”. If people really hated changes there was no Silicon Valley with its multiple startups and unicorn companies. Google was not first search engine, there were some already, including Altavista. But it turned out to be the best one, so users switched to it. The same with Facebook (remember Friendster, Myspace?) and tons of other successful companies. Users like changes if they make their life better.</p><p>Users do not like to feel stupid struggling to find where the Settings menu went after the redesign, how to use this new feature or spend time watching tutorials and skipping overlays with tips that slow down access to the app itself. And when it comes to software, they hate surprises.</p><p>Usual scenario for software updates and redesign can be described as a “sudden attack”: the user wakes up, starts his app or program, and realizes that it is just not it was yesterday. Lots of things changed, he or she now needs to re-learn, and there is no information about what benefits it may bring instead.</p><p>As a result, users have to spend time on learning, or studying information about changes, and receive negative emotions of such surprises. However, this does not mean they do not like changes as we still have Google, Facebook, Skype, and other products that have proven that changes for the good might be highly appreciated.</p><p><strong>Final thoughts: how to implement changes right way</strong></p><p>Thankfully, there are a number of best practices to follow working on a major fix or a redesign that will reduce potential negative to a minimum.</p><ul><li><strong>Fight the uncertainty</strong> — people do not want unwelcomed surprises with changes that nobody understands why need to be made.</li><li><strong>Don’t take control</strong> — users should possess control of their software at all times. This means even if you want to introduce something super-duper cool, it is a good idea to give the user an opportunity to not opt-in to these changes.</li><li><strong>Explain benefits</strong> — even if changes are somewhat obligatory, and there is no way you can allow users to remain in their familiar space, spend the time to explain to them how their life will change to the better.</li><li><strong>Test the update very well</strong> — if the new version of a system works bad, this will generate negative even you were good at the announcement and explanation stage.</li></ul><p><strong>Our approach</strong></p><p>Here is how we organize <a href="https://www.1ci.com/developers">1C:Enterprise</a>-based <a href="https://www.1ci.com/applications">product</a> updates and some of the tools we use.</p><ul><li><strong>Documentation</strong> — we create a full list of needed and upcoming changes and write down what needs to be done for such an upgrade.</li><li><strong>Compatibility mode </strong>— all changes are run in compatibility mode which ensures that platform functionality is restricted to make old code/UX compatible with new features.</li><li><strong>Version control map and GIT</strong> — there should be an opportunity to roll back to the previous version if some problem occurs. This is why we store our code in GIT.</li><li><strong>Testing</strong> — we test everything, including configurations, builds (CI). Code review is performed by several independent developers, tests are both manual and automated.</li><li><strong>Step-by-step release</strong> — before going public and uploading our update we give new version out to a selected group of partners. Only after they’ve used new software and it went smoothly, we initiate the final release.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f2479d5adf9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Secure Cloud Infrastructure by Choosing the Right Providers]]></title>
            <link>https://medium.com/yellow-universe/how-to-secure-cloud-infrastructure-by-choosing-the-right-providers-7a9f26c54253?source=rss-e4ac2fb667ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a9f26c54253</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[platform]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[1Ci]]></dc:creator>
            <pubDate>Fri, 17 Aug 2018 11:19:51 GMT</pubDate>
            <atom:updated>2018-08-17T11:29:35.470Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yW2lRbp0YjLaRFWRKvHisw.jpeg" /><figcaption><em>Image credit: </em><a href="https://medium.com/%20https:/unsplash.com/photos/nvRJJsd54Cg%20"><em>Unsplash</em></a></figcaption></figure><p>Information security is one of the most important factors for any tech company. However, it is often overlooked when it comes to using cloud services. It is common belief that security is something that the cloud provider should have to worry about.</p><p>This is the wrong approach, and today we will talk about what the client company should do when preparing to use cloud services of different types and to avoid big problems resulting from possible security breaches.</p><p><strong>1. It is your job to find secure solutions</strong></p><p>Yes, cloud service providers (CSPs) must work hard to ensure the highest security level possible. But there are dozens of them in almost every industry and market segment nowadays. However, this abundance also means that you should not go with the first solution you come across.</p><p>Besides, business-related factors such as the pricing security level of every potential solution should be thoroughly examined. You should ask the team behind the product what security tools they use (antivirus, firewalls etc) and what encryption methods they implement (SSL, local encryption etc).</p><p><strong>2. A new tool should be included in a backup policy</strong></p><p>It is obvious that every cloud service of choice should provide functionality for backups. But it is also important that this functionality is flexible and may be incorporated into an already existing backup policy of the whole company.</p><p>Analyze what types of backups your CSP is offering and whether it is possible to schedule backups or automatically transfer them to external storage.</p><p><strong>3. Work on how the cloud solution will access data in your network</strong></p><p>Problems may arise not only in the cloud itself but on the way from your internal infrastructure. A client-server approach to building infrastructure helps to reduce such risks. For example, our customers often use dedicated servers for <a href="http://bit.ly/2MRbsLx">1C:Enterprise</a>-based solutions, while the database is running somewhere else (maybe, in another country). In this case, you can use the built-in security features of the database management system (DBMS) such as file encryption to protect data.</p><p>Another important tip is to implement security profiles in your network. These tools can be used to restrict potentially harmful actions including the opening files of a certain type on the server running important application (CRM, accounting etc) or ensuring that only connections from trusted sources (IP-addresses) are allowed.</p><p>Configuration management is also not to be overlooked. This technique allows the application of flexible restrictions on who can access what data: for example, in financial systems, international currency exchange rates may be available to everyone while detailed corporate information access is restricted to certain users only. The next step here is implementing the roles model, defining permissions for each role and assigning roles to different groups of users. Logging and data version control is also important here as these tools allow administrators to easily track changes made in important data and understand the source of these changes.</p><p><strong>4. Test everything</strong></p><p>Testing might sound like a somewhat minor step when it comes to starting to use a new cloud service, but actually, there are lots of things to test here. First of all, backups — it is important not only generate them but to be able to restore. If you do not test such things you risk falling into a situation similar to what <a href="https://about.gitlab.com/2017/02/01/gitlab-dot-com-database-incident/">happened</a> to GitLab last year when all 5 backup methods they used failed to restore.</p><p>The second important thing to test is how the new cloud service is connected to your infrastructure. There might be lots of weak points and to find them you may consider hiring an ethical hacker or a consultancy firm. Such an expert will perform actions similar to what potential attackers might do in order to hack into your infrastructure, attack it, or steal confidential information. As a result of this work, you will receive a report with all potential threats highlighted along with recommendations on how to fix these problems.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a9f26c54253" width="1" height="1" alt=""><hr><p><a href="https://medium.com/yellow-universe/how-to-secure-cloud-infrastructure-by-choosing-the-right-providers-7a9f26c54253">How to Secure Cloud Infrastructure by Choosing the Right Providers</a> was originally published in <a href="https://medium.com/yellow-universe">Yellow Universe</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Speed Up Software Development Without Sacrificing Quality]]></title>
            <link>https://medium.com/yellow-universe/how-to-speed-up-software-development-without-sacrificing-quality-fc35854b1316?source=rss-e4ac2fb667ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc35854b1316</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[platform]]></category>
            <dc:creator><![CDATA[1Ci]]></dc:creator>
            <pubDate>Thu, 28 Jun 2018 13:03:30 GMT</pubDate>
            <atom:updated>2018-06-28T13:03:30.925Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5I8Wu8EpyEKwZF8oYra3bQ.jpeg" /><figcaption><em>Image source: </em><a href="https://unsplash.com/photos/eJ9mX6yEbAw"><em>Unsplash</em></a></figcaption></figure><p>In today’s tech world it is crucial for every business to be fast. You need to reduce time-to-market or else your customers will switch to competitors that can provide them with new opportunities. This is why speeding up development is an important issue to solve.</p><p>Today we will talk about how to meet constantly shrinking timelines and still keep your code quality at a high level.</p><h3><strong>Design a clear plan and set dev standards</strong></h3><p>Planning is one of the most important factors in IT solutions development. You can’t achieve success if your goals are too opaque and lack specifics. So it is a good idea to first break up the whole project into small, manageable parts, then set a development timeline for main features with specific deadlines (but it is important to not fall into overplanning here).</p><p>Even if you want to speed up development, this does not mean that tasks should be solved just any way possible. It is better to have clear coding, testing, and documentation standards as this will save tons of time in the future and drastically improve the overall quality of the software.</p><h3><strong>Doing less is better</strong></h3><p>Having big batches of changes in every release makes it hard to avoid mistakes and meet deadlines. It is better to use short-term development sprints where only a handful of tasks are solved. It is easier for team members to move step by step, solving smaller tasks and releasing new features often rather than diving into the endless development of the stuff nobody knows when will be released.</p><h3><strong>Code cleanup is a must</strong></h3><p>Integration of new features with the old ones is a hard task which can’t be done fast. However, often old code might be not needed anymore. Doing a regular code cleanup helps to eliminate chunks of unused code, improve overall codebase quality, and simultaneously speed up the development process.</p><h3><strong>Test in a clever way</strong></h3><p>When it comes to speeding up the development process, often one of the first ideas is to reduce spending on testing. This is an obvious mistake that will only lead to poor code quality and even greater time spent on fixing them.</p><p>But this does not mean that anything can’t be done here. You can implement a clever approach to testing. For example, it might be worth trying to test things before the development even starts: write tests that need to be passed otherwise features are unable to be accepted. Writing tests and code that will pass them in parallel will result in more reliable code and will also stimulate faster releases.</p><h3><strong>Use better tools</strong></h3><p>Task lists, process automation apps, development environments — the better tools you have, the faster and the more productive you will be. This is why it is crucial to build a strong stack of tools used for development purposes.</p><p><em>At 1Ci we and our partners try to build such tools for our customers. Our solutions allow them to solve their tasks with a top-notch code and do it very fast.</em></p><p><em>For example, NFP consulting company uses the 1C:Enterprise platform to optimize processes, to increase the efficiency of its clients’ business and for fast implementation at customers’ sites. Last year, by using this tool the NFP experts prepared a methodology in order to automate a winery that produces and supplies wine to Michelin restaurants. 1Ci system is straightforward and fast to integrate into both existing and new infrastructures — often a key factor for success.</em></p><p><em>Another company, </em><a href="https://www.accountingsuite.com/?utm_source=medium&amp;utm_medium=social&amp;utm_campaign=how_to_speed_up_software_development"><em>AccountingSuite</em></a><em>, which is a cloud accounting and inventory software — claimed to save up to 50% of development time using 1C:Enterprise platform.</em></p><p><em>Axioma, in turn, is focused on corporate projects such as business automation, manufacturing process management, and ERP projects. One of the typical customer requests they receive is as follows: “Remove as many users as possible. Eliminate the human factor. And make sure it happens very quickly, in the most convenient way [..]” To address such requests, Axioma experts used the 1C:Enterprise development platform, automating the marine terminal and providing integration of all equipment into a single system at the port of a city in Poland.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc35854b1316" width="1" height="1" alt=""><hr><p><a href="https://medium.com/yellow-universe/how-to-speed-up-software-development-without-sacrificing-quality-fc35854b1316">How to Speed Up Software Development Without Sacrificing Quality</a> was originally published in <a href="https://medium.com/yellow-universe">Yellow Universe</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>