<?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 Viktoria | Coding Viking on Medium]]></title>
        <description><![CDATA[Stories by Viktoria | Coding Viking on Medium]]></description>
        <link>https://medium.com/@coding-viking?source=rss-6e3a9bcfbbb1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_kfDLcTsAoyhfAHq9qdu_A.jpeg</url>
            <title>Stories by Viktoria | Coding Viking on Medium</title>
            <link>https://medium.com/@coding-viking?source=rss-6e3a9bcfbbb1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 03:20:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@coding-viking/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[AI Transformation Playbook for engineering organizations]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">The uncomfortable truth about &#x201C;AI transformation&#x201D;</p><p class="medium-feed-link"><a href="https://coding-viking.medium.com/ai-transformation-playbook-for-engineering-organizations-00806c92ba6c?source=rss-6e3a9bcfbbb1------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://coding-viking.medium.com/ai-transformation-playbook-for-engineering-organizations-00806c92ba6c?source=rss-6e3a9bcfbbb1------2</link>
            <guid isPermaLink="false">https://medium.com/p/00806c92ba6c</guid>
            <category><![CDATA[ai-transformation]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Viktoria | Coding Viking]]></dc:creator>
            <pubDate>Tue, 14 Apr 2026 18:52:50 GMT</pubDate>
            <atom:updated>2026-04-14T18:52:50.969Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Backend Service Best Practices (with Examples)]]></title>
            <link>https://coding-viking.medium.com/backend-service-best-practices-with-examples-f1bdcbf47531?source=rss-6e3a9bcfbbb1------2</link>
            <guid isPermaLink="false">https://medium.com/p/f1bdcbf47531</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[backend]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[backend-development]]></category>
            <dc:creator><![CDATA[Viktoria | Coding Viking]]></dc:creator>
            <pubDate>Sat, 03 Feb 2024 11:06:07 GMT</pubDate>
            <atom:updated>2024-02-03T11:06:07.548Z</atom:updated>
            <content:encoded><![CDATA[<p>Backend applications are essential for powering the services and platforms. These applications work behind the scenes to handle data, manage transactions, and ensure a smooth user experience. Developing a strong and efficient backend application requires attention to several key elements. Each plays a vital role in the application’s performance and reliability. We’ll explore these elements, using examples from analytics software to highlight their importance and how they’re implemented.</p><h3>1. Single Responsibility</h3><p><em>Principle</em>: A backend application should focus on a single business area or component. This means that each part of the application should do one thing only, making the system easier to understand and maintain.</p><p><em>Example</em>: In analytics software like Google Analytics, different services handle specific tasks such as tracking user actions, processing data, or creating reports, ensuring the system is straightforward and effective.</p><h3>2. Integration Ready</h3><p><em>Principle</em>: Backend applications must be ready to connect with other systems, offering ways to communicate such as APIs or webhooks. They should be able to add new features without changing existing code.</p><p><em>Example</em>: Analytics tools provide APIs for data access and tool configuration, allowing them to work with other systems like CRM without needing to change the core application.</p><h3>3. Versioning</h3><p><em>Principle</em>: It’s important to keep old versions of your interfaces available so that changes don’t break systems that rely on them.</p><p><em>Example</em>: Analytics tools keep old API versions available when they release new updates, ensuring that existing setups continue to work properly.</p><h3>4. Clean Architecture</h3><p><em>Principle</em>: Having a well-organized system makes it easier to manage and update, ensuring that different parts can work independently.</p><p><em>Example</em>: Analytics software separates tasks like collecting data, processing it, and showing it into different layers, which helps with maintenance and growth.</p><h3>5. Testing</h3><p><em>Principle</em>: Testing thoroughly, including checking small parts, how parts work together, and how the system handles lots of users, helps find and fix problems early.</p><p><em>Example</em>: Before releasing updates for an analytics platform, extensive testing ensures new features work well and don’t break existing ones.</p><h3>6. Caching</h3><p><em>Principle</em>: Storing data temporarily can reduce load on databases and make the application respond faster.</p><p><em>Example</em>: Analytics software stores frequently accessed data and reports temporarily, making the system faster for users.</p><h3>7. Scalability</h3><p><em>Principle</em>: Backend services need to be able to grow to handle more users or data without losing speed.</p><p><em>Example</em>: Analytics platforms can expand across more servers to manage more data or users efficiently.</p><h3>8. Logging</h3><p><em>Principle</em>: Keeping detailed records of what the application does helps identify and fix issues faster.</p><p><em>Example</em>: Analytics software logs errors and unusual activity, helping developers quickly pinpoint and solve problems.</p><h3>9. Performance Monitoring</h3><p><em>Principle</em>: Watching how the system performs helps find areas that need improvement, ensuring it runs smoothly.</p><p><em>Example</em>: Analytics platforms use monitoring tools to keep an eye on data processing and report generation, making sure they’re fast and efficient.</p><h3>10. Security</h3><p><em>Principle</em>: Protecting data and preventing unauthorized access are critical, using measures like encryption and secure logins.</p><p><em>Example</em>: Analytics tools encrypt data and use secure methods for user login to keep information safe.</p><h3>11. Health Check</h3><p><em>Principle</em>: These provide updates on how the system is doing, helping catch and fix issues early.</p><p><em>Example</em>: Analytics services offer health checks to monitor different parts of the system, ensuring they work well.</p><h3>12. Continuous Integration/Continuous Deployment (CI/CD)</h3><p><em>Principle</em>: Automating development steps helps get updates out faster and more reliably.</p><p><em>Example</em>: Analytics software teams use automation to quickly integrate, test, and release updates, reducing errors and speeding up improvements.</p><h3>13. Documentation</h3><p><em>Principle</em>: Good documentation makes it easier for new team members to get started and helps with ongoing development and troubleshooting. <em>Example</em>: Clear documentation for analytics software includes guides for APIs, user manuals, and troubleshooting advice.</p><h3>14. Resilience and Fault Tolerance</h3><p><em>Principle</em>: The system should keep running smoothly even when parts fail, using strategies like retrying failed operations or temporarily reducing functionality.</p><p><em>Example</em>: Analytics platforms use methods to ensure data collection and processing continues even if some parts of the system go down.</p><p>These principles, when applied well, can greatly improve the strength, efficiency, and ability to grow backend applications. Analytics software is a great example of these practices in action, showing the benefits of following these standards in real-world applications.</p><p><em>Viki<br></em><a href="https://www.instagram.com/coding_viking"><em>https://www.instagram.com/coding_viking</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f1bdcbf47531" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ChatGPT Prompts Template]]></title>
            <link>https://coding-viking.medium.com/chatgpt-developer-prompts-80bc9860d6a6?source=rss-6e3a9bcfbbb1------2</link>
            <guid isPermaLink="false">https://medium.com/p/80bc9860d6a6</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[openai]]></category>
            <category><![CDATA[prompt]]></category>
            <category><![CDATA[chatgpt]]></category>
            <dc:creator><![CDATA[Viktoria | Coding Viking]]></dc:creator>
            <pubDate>Tue, 03 Jan 2023 22:17:53 GMT</pubDate>
            <atom:updated>2023-01-04T12:42:18.617Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vmg3Fz-su8arFpcBzWhnzQ.png" /></figure><p>Here is the General Template on how to talk to ChatGPT:</p><p>Act as &lt;role_name&gt;.<br>I will provide you with &lt;detailed_info_on_inputs&gt;.<br>And you will &lt;detailed_task_description&gt;.<br>This might include &lt;concrete_deliverables&gt;.</p><p>Of course, there are more creative ways, but here is where to start when in doubt.</p><p>Examples:</p><ol><li><strong>Code Review</strong></li></ol><blockquote>Act as a developer code reviewer. I will provide you with a piece of {language/logic} code. You will help me identify potential bugs in this code, give important suggestions on improving the code quality and maintainability, and check if it adheres to coding standards and best practices.</blockquote><p><strong>2. Product Manager — Requirements Engineering</strong></p><blockquote>Create a detailed technical task. Technical requirements: the creation of a 3D constructor of frameworks in the form of a cube, provide the ability to edit the squares that make up the cube. User should be able to add custom parameters to the cube via the admin panel.</blockquote><p>3. Developer with no clue</p><blockquote>modify this function to be {what_should_be_done}. {conditions}.</blockquote><p><em>Btw my Insta: </em><a href="https://www.instagram.com/coding_viking/"><em>https://www.instagram.com/coding_viking</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80bc9860d6a6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Has Clean Code just become obsolete?]]></title>
            <link>https://coding-viking.medium.com/clean-code-is-obsolete-2f357c88b1e5?source=rss-6e3a9bcfbbb1------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f357c88b1e5</guid>
            <category><![CDATA[software]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[clean-code]]></category>
            <dc:creator><![CDATA[Viktoria | Coding Viking]]></dc:creator>
            <pubDate>Fri, 23 Dec 2022 20:13:35 GMT</pubDate>
            <atom:updated>2022-12-23T20:13:57.066Z</atom:updated>
            <content:encoded><![CDATA[<p>The principles of clean code, as outlined in Robert C. Martin’s book “Clean Code: A Handbook of Agile Software Craftsmanship,” have long been considered essential for writing efficient and maintainable software. However, with the advent of advanced artificial intelligence technologies such as ChatGPT, it is possible to refactor and optimize code in a previously unimaginable way automatically.</p><p>One of the key benefits of using AI to write clean code is the ability to refactor and reorganize methods and classes automatically. This can help to make code more readable and easier to understand, as well as reduce the amount of duplicate or unnecessary code. By using ChatGPT to analyze code and identify areas that could be improved, developers can quickly and easily improve the quality of their code without having to spend time manually refactoring.</p><p>In addition to the ability to automatically refactor code, ChatGPT also brings several other benefits to writing clean code. For example, ChatGPT can generate code snippets or entire functions based on natural language input, allowing developers to quickly and easily write code without manually typing out every line. This can save significant time and effort and help developers be more productive.</p><p>Overall, while the principles of clean code are still important for writing high-quality software, the use of ChatGPT can significantly improve the efficiency and effectiveness of the development process. By automating many of the tasks involved in writing clean code, developers can focus on more important aspects of their work, such as solving complex problems and creating innovative solutions.</p><p>a few examples of how ChatGPT could be used to improve the process of writing clean code:</p><ul><li>Automatic refactoring: ChatGPT could analyze existing code and identify areas that could be refactored to make it more readable or efficient. For example, ChatGPT might suggest renaming variables to use more descriptive names or reorganizing methods and classes to make the code more modular.</li><li>Code generation: Developers could use ChatGPT to generate code snippets or functions based on natural language input. For example, a developer could describe the functionality they want to implement, and ChatGPT could generate the corresponding code. This could save significant time and effort and help developers be more productive.</li><li>Code optimization: ChatGPT could analyze existing code and suggest optimizations that could make it run more efficiently. For example, ChatGPT might suggest replacing a series of nested loops with a more efficient algorithm or identifying areas where memory usage could be reduced.</li><li>Debugging assistance: ChatGPT could be used to help identify and fix bugs in code. By analyzing the code and the error messages, ChatGPT could suggest potential fixes or workarounds that could help developers resolve issues more quickly.</li></ul><p>Overall, these are just a few examples of how ChatGPT could improve the writing process of clean code. By automating many of the tasks involved in maintaining and optimizing code, ChatGPT could significantly improve the efficiency and effectiveness of the development process.</p><p>Well, hello, new world!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f357c88b1e5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Politics for technical people]]></title>
            <link>https://coding-viking.medium.com/politics-for-technical-people-98ab4fbe1e75?source=rss-6e3a9bcfbbb1------2</link>
            <guid isPermaLink="false">https://medium.com/p/98ab4fbe1e75</guid>
            <category><![CDATA[technical-management]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Viktoria | Coding Viking]]></dc:creator>
            <pubDate>Wed, 26 Oct 2022 13:35:02 GMT</pubDate>
            <atom:updated>2024-02-03T10:56:47.366Z</atom:updated>
            <content:encoded><![CDATA[<p>Very often, technical people are too concentrated on technical things, which, well, is the basics, but only partially. Some points were especially painful to me when transitioning away from developer role. Throughout my 10+ years-long career, it feels like I have made all the possible mistakes. Thanks to them, I was able to learn and now hope you will not make the same ones. Here are the compilations of the knowledge gathered over the years in more than 15 projects, which I wish someone told me at the beginning. Most of these apply to non-tech careers as well. These tips will leverage your ability to interact with others and might shape your view.</p><ol><li><strong>Nobody owes you anything.</strong> Period. Sometimes as a junior or someone who has just joined a new company or project, you are full of expectations to get something for yourself. This was either promised in the job posting or during the interview, or just the job title implies it. Well, needless to say, that job posting is rather marketing. An interview is sometimes showing up the best sides of the environment… In the end, it’s just a skills market, and something is or will be (in the case you’re in an apprenticeship position) needed from you in the first place. So you were expecting some sort of tasks and are not getting them? You have imagined your job in another way? Welcome to real life! Getting interesting, challenging, or *put your own adjective* should be considered a privilege, not a must. If you look deeper into the company and the people you’re surrounded with, you will understand why things are the way they are. Now your task is not to demand and make a conflict (my mistake!) but to access the possibilities and effort of changing this situation. If it’s going to take too long or is impossible, you might still want to give it a try to change the situation. Talk nicely, express what you’re looking for, and look into the direction of other departments and teams. Ultimately, you choose either to change the situation, deal with it or quit. Sometimes lowering expectations is the way to go.</li><li><strong>Do not make conflicts</strong>. Think seven times before introducing the conflict. There is most certainly no way back. There are very, very few situations when you need to make a conflict. Before doing it, think about what might be the future setup with the person and all the implications of you starting it, and try to heat things off.</li><li><strong>Do not introduce your rules without understanding why things are how they are. </strong>It was a painful one. And there is no easy revert back. As a rule of thumb, make sure that at least 2 months have passed since you are on the project and that you really understand why things are the way they are. Before introducing changes, validate your assumptions with someone.</li><li>Be transparent, especially in a remote setup. I usually see people chatting to someone, doing smth, but that’s not visible to the manager in case the team is big and especially to the upper management. On each level, you should communicate rather more than less.</li><li>Bonus: do more than you should, and go beyond your role. Try to figure out where you are good and take these things to the next level, even if they are not “directly” your responsibility.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98ab4fbe1e75" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nuxt.js: Use Cases and Templates/Themes]]></title>
            <link>https://coding-viking.medium.com/nuxt-js-use-cases-and-templates-themes-f4da765775bc?source=rss-6e3a9bcfbbb1------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4da765775bc</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[nuxtjs]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[server-side-rendering]]></category>
            <dc:creator><![CDATA[Viktoria | Coding Viking]]></dc:creator>
            <pubDate>Tue, 25 Oct 2022 19:08:40 GMT</pubDate>
            <atom:updated>2022-10-25T19:08:40.463Z</atom:updated>
            <content:encoded><![CDATA[<p>Nuxt.js is a free open source JavaScript library based on Vue.js, Node.js, Webpack, and Babel.js. Nuxt is inspired by Next.js, a framework of similar purpose based on React.js. The framework is advertised as a “Meta-framework for universal applications”.</p><p>Even though it appeared quite some time ago, in 2016, it became more popular after the breakthrough of Next.js.</p><h3>When to use Nuxt.js?</h3><p>As with every framework/technology, it is best to use it for a certain type of problems. In the case of Nuxt.js, these are:</p><ol><li>SEO. Nuxt.js allows server-side rendering and therefore is SEO-friendly. SSR is fetching AJAX data and rendering Vue.js components into HTML strings on the server (Node.js)</li><li>Non-SPA app. Nuxt is better suited for applications that include multiple pages, social sharing features, and management.</li><li>If you want less hassle with configs but are up to using cookies over the local storage.</li></ol><h3>Free ready-to-use templates/themes/starters</h3><ol><li><a href="https://jamstackthemes.dev/theme/#ssg=nuxt">https://jamstackthemes.dev/theme/#ssg=nuxt</a></li><li>Creative Tim website</li></ol><p>Thanks for reading, will be happy to see you around on Insta: <a href="https://www.instagram.com/coding_viking">coding_viking</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4da765775bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 things I wish I knew before transitioning to Product Management from Development]]></title>
            <link>https://coding-viking.medium.com/6-things-i-wish-i-knew-before-transitioning-to-product-management-from-development-7f635f157a9b?source=rss-6e3a9bcfbbb1------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f635f157a9b</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Viktoria | Coding Viking]]></dc:creator>
            <pubDate>Mon, 15 Mar 2021 21:26:17 GMT</pubDate>
            <atom:updated>2021-03-19T09:08:47.266Z</atom:updated>
            <content:encoded><![CDATA[<h3>Background</h3><p>It’s been exactly one year since I moved into product. Under “product”, I will mean both the Product Manager and Product Owner roles. I can’t say it was a smooth transition, but it took less than a year overall.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RLoojUk4m97tUMOXra074w.jpeg" /><figcaption><a href="https://instagram.com/coding_viking">instagram.com/coding_viking</a></figcaption></figure><h3>The 5 pitfalls</h3><p>The Product Manager role is pretty unstructured. There is no clear path to becoming a Product Manager, and a Software Developer role is just one way to achieve it. The transition path implies some knowledge and experience gaps, which the development role typically does not fill.</p><p>Here I will briefly discuss the pitfalls I faced at the beginning of my career as a Product Manager.</p><ol><li><strong>Stereotypes</strong>. It doesn’t matter if you changed companies or switched within the same company, people who know your background will have stereotypes. People always have them. So what are the typical ones for a developer background? Average communicator, not good empathy, and weak understanding of business. Depending on your current situation and your new product role, you might want to enhance some of the abovementioned skills. If I were starting in the product today, I would better mind my audience while speaking, (always!) think twice of a customer before making even the most minor decisions, observe more of business culture within the company at the beginning. Taking this further, a bunch of books in psychology and online courses would have helped enormously.</li><li><strong>Align your expectations</strong>. As a Developer, it’s pretty clear what you should do in your role. You see where you’re going, and you know what to tackle and learn next to be there. Overall, the world is relatively stable and predictable. For Product Managers, it’s quite the opposite. Everything is business/team specific and subjective depending on who you work with, structures etc. It would help if you did not stick to the product role idea you have in your mind — something you experienced in the previous company or the other Product roles you’ve seen throughout your career. You want to be aligned with your boss/team about what they expect from you initially. Likewise, the position of another side should be clear and consistent. So this should work in both directions. Bringing up expectations topic during the interview and the first days, setting personal goals all are excellent strategies to overcome misunderstandings at the beginning.</li><li><strong>Success tracking</strong>. For developers, the work is more objective and there are clear success metrics like story points closed. It is not the case for products. At a B2C company, you can start seeing some metrics enhancement. At B2B, it’s about people&#39;s satisfaction. You can see if developers have enough on their plate, if your team/managers are happy, if you have a bigger picture in mind, as well as smaller steps to achieving high-level goals. Asking for feedback or talking to your supervisors is a great way to approach uncertainty in this case.</li><li><strong>Thinking that Product Management is easier than Development</strong>. You should never compare these two. This will lead to underestimating efforts. But TLDR: it’s not. It’s about people, there is no “right” answer, unlike in tech, and you have a much higher level of responsibility.</li><li><strong>Acting like a team-lead/being too technical</strong>. Being technical is undoubtedly a huge plus. Also, it’s a common trap. Now, it’s not about HOW, but about WHAT and WHY. Yes, you will miss programming, everybody around (non-COVID!) is talking about it, but you have to stay away. You’ve made your choice for reasons, so stick to it. The good news is, you’re free to code in the free time. It’s always good to understand how things work and to be technically up-to-date. Just for now, you have more important things to tackle. Namely, it’s high time to start getting to know, understand and further learn the customer. For this, you need lots of energy, empathy and data. Your primary focus needs to be <strong>on what features you’re going to deliver</strong>, how those features will help your company make money, and how to ensure that those features get shipped. Everything else is the primary responsibility of someone else — and to be an effective PM, you can’t afford to spend time thinking or caring about most of the things you did as an engineer.</li></ol><h3>Summary</h3><p>Transition into Product Management from a technical position is challenging, and knowing the pitfalls will help you adapt more effectively: As a great product you:</p><ul><li>are a great communicator — mind your audience, listen with empathy; know your customer and your business;</li><li>define goals and expectations;</li><li>ask for feedback and validate your performance;</li><li>do not underestimate the role;</li><li>are not solving technical problems, care for WHAT and WHY.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f635f157a9b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Command Line Notes, part 1]]></title>
            <link>https://coding-viking.medium.com/linux-command-line-notes-part-1-2f5b3c9148e4?source=rss-6e3a9bcfbbb1------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f5b3c9148e4</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[command-line]]></category>
            <category><![CDATA[operations]]></category>
            <category><![CDATA[terminal]]></category>
            <category><![CDATA[linux-tutorial]]></category>
            <dc:creator><![CDATA[Viktoria | Coding Viking]]></dc:creator>
            <pubDate>Sat, 09 Mar 2019 15:34:37 GMT</pubDate>
            <atom:updated>2021-03-10T20:34:23.784Z</atom:updated>
            <content:encoded><![CDATA[<h3>Very Basic Linux Command Line Notes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/962/1*NOR7ESq3z6hs2rA-Lsrlbw.png" /></figure><p>It is a cheat sheet for a Linux terminal beginner. You will not find many explanations here. It’s rather a quick answer to your search. Also, you will get an idea of how mighty your small terminal actually is. Maybe the article will inspire you to dig deeper. The information is based on the book: “The Linux Command Line: A Complete Introduction” by William Shotts.</p><p>Today we will talk about most frequently used commands as well as I/O redirection.</p><pre><strong>pwd </strong>— display the current working directory, (print working directory) command</pre><pre><strong>ls -l</strong> — see a list of files and subdirectories contained in the current working directory. By adding -l to the command, we changed the output to the long format.</pre><h3>Most frequently used commands:</h3><p><strong>cp </strong>— Copy files and directories:</p><p>copy the single file or directory <em>item1 </em>to file or directory <em>item2:</em></p><pre><strong>cp</strong> item1 item2</pre><p>copy multiple items (either files or directories) into a directory:</p><pre><strong>cp</strong> <em>item</em>... <em>directory</em></pre><pre><strong>mv </strong>— Move/rename files and directories.<br></pre><pre><strong>mkdir </strong>— Create directories.</pre><pre><strong>rm </strong>— Remove files and directories.</pre><pre><strong>ln </strong>— Create hard and symbolic links.</pre><p>Wildcards (too long to be listed here).</p><p>Info commands:</p><pre>type; which; help</pre><h3>Redirection</h3><p>I/O redirection allows us to redefine where standard output goes. To redirect standard output to another file instead of the screen, we use the <strong>&gt;</strong> redirection operator followed by the name of the file. Why would we want to do this? It’s often useful to store the output of a command in a file. For example, we could tell the shell to send the output of the ls command to the file ls-output.txt instead of the screen:</p><p>Examples:</p><p>Truncate/create a new file:</p><pre><strong>&gt;</strong> file.txt</pre><p>Append to the file:</p><pre><strong>&gt;&gt;</strong> file.txt</pre><p>Commands that make use of standard input:</p><p><em>cat</em> — Concatenate files. The cat command reads one or more files and copies them to standard output like so:</p><pre><strong>cat</strong> [filename...]</pre><p>join files file1.pdf and file2.pdf together:</p><pre><strong>cat</strong> file1.pdf <strong>&gt;</strong> file2.pdf</pre><p><em>sort</em> — Sort lines of text.</p><p>uniq — Report or omit repeated lines. The uniq command is often used in conjunction with sort. uniq accepts a sorted list of data from either standard input or a single filename argument (see the uniq man page for details) and, by default, removes any duplicates from the list. So, to make sure our list has no duplicates (that is, any programs of the same name that appear in both the /bin and /usr/bin directories) we will add uniq to our pipeline:</p><pre>ls /bin /usr/bin | sort | <strong>uniq</strong> | less</pre><p><em>wc</em> — Print newline, word, and byte counts for each file.</p><pre><strong>wc</strong> ls-output.txt  7902 64566 503634 ls-output.txt</pre><p><em>grep</em> — Print lines matching a pattern. grep is a powerful program used to find text patterns within files, like this:</p><pre>grep pattern [file…]</pre><p>When grep encounters a “pattern” in the file, it prints out the lines containing it. The patterns that grep can match can be very complex, but for now we will concentrate on simple text matches. Let’s say we want to find all the files in our list of programs that have the word zip in the name. Such a search might give us an idea of which programs on our system have something to do with file compression. We would do this:</p><pre>ls /bin /usr/bin | sort | uniq | <strong>grep</strong> zip </pre><p>There are a couple of handy options for <strong>grep: -i</strong>, which causes grep to ignore case when performing the search (normally searches are case sensitive) and -v, which tells grep to print only lines that do not match the pattern.</p><p><em>head</em> — Output the first part of a file. Sometimes you don’t want all the output from a command. You may want only the first few lines or the last few lines. The head command prints the first 10 lines of a file, and the tail command prints the last 10 lines. By default, both commands print 10 lines of text, but this can be adjusted with the -n option:</p><pre><strong>head</strong> <strong>-n</strong> 5 output.txt </pre><p>Using the -f option, tail continues to monitor the file and when new lines are appended, they immediately appear on the display.</p><p><em>tail</em> — Output the last part of a file.</p><p><em>tee</em> — Read from standard input and write to standard output and files. The tee program reads standard input and copies it to both standard output (allowing the data to continue down the pipeline) and to one or more files. This is useful for capturing a pipeline’s contents at an intermediate stage of processing.</p><pre>ls /usr/bin | <strong>tee</strong> ls.txt | grep zip</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f5b3c9148e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Spring Boot + DataVirtuality JDBC Guide]]></title>
            <link>https://coding-viking.medium.com/spring-boot-datavirtuality-jdbc-guide-b85fb6942b81?source=rss-6e3a9bcfbbb1------2</link>
            <guid isPermaLink="false">https://medium.com/p/b85fb6942b81</guid>
            <category><![CDATA[java]]></category>
            <category><![CDATA[spring-boot]]></category>
            <category><![CDATA[database]]></category>
            <category><![CDATA[spring]]></category>
            <category><![CDATA[datavirtuality]]></category>
            <dc:creator><![CDATA[Viktoria | Coding Viking]]></dc:creator>
            <pubDate>Sun, 01 Apr 2018 08:54:59 GMT</pubDate>
            <atom:updated>2018-04-17T14:17:20.982Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/392/1*hdkOu6-YzWCD5ueNG44ILQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/310/1*L566wJNgAwp9sUFrRYLt1w.png" /><figcaption>Spring Boot + DataVirtuality</figcaption></figure><p><a href="https://datavirtuality.com/">DataVirtuality</a> is a Business Intelligence tool that enables you to manipulate all your APIs, databases and flat files from within one place. Sounds good, doesn&#39;t it? But there is one problem — accessing DataVirtuality databases as a datasource programatically. Since all the information available on the Internet is a support <a href="https://support.datavirtuality.com/hc/en-us/articles/115002011163-Connecting-SQuirreL-via-JDBC">ticket</a>, it is time to shed light on the topic.</p><p>Imagine that we are connecting to a MySQL database called &quot;Animals&quot;. It is located on a remote server. The connection is possible only through the VPN. But here we are — a DataVirtuality has an already established connection to the &quot;Animals&quot; database! The only task now is a correct datasource configuration in the Spring Boot application. Follow the two steps below.</p><p>1. Add a driver dependency to the maven or gradle configuration file. The latest version of DV driver should be inquired.</p><p><em>pom.xml:</em></p><pre>&lt;<strong>dependency</strong>&gt;<br>    &lt;<strong>groupId</strong>&gt;com.datavirtuality&lt;/<strong>groupId</strong>&gt;<br>    &lt;<strong>artifactId</strong>&gt;jdbc-driver&lt;/<strong>artifactId</strong>&gt;<br>    &lt;<strong>version</strong>&gt;2.0.28&lt;/<strong>version</strong>&gt;<br>&lt;/<strong>dependency</strong>&gt;</pre><p>2. Configure the datasource. The key moment is to put the database name (in this case &quot;Animals&quot;) not to the <strong>url </strong>string, but to the <strong>VirtualDatabaseName </strong>property under the hibernate settings.</p><p>In case of SSL, change the <strong>url </strong>property to :</p><pre>jdbc:datavirtuality:datavirtuality@mm://server-address.com:31000<br></pre><p>The datasource setup from within application.yml will look the following way:</p><p><em>application.yml:</em></p><pre><strong>// ...</strong></pre><pre><strong>datasource:<br>  driverClassName: </strong>com.datavirtuality.dv.jdbc.Driver<br>  <strong>url: </strong>jdbc:datavirtuality:datavirtuality@mms://server-address.com:31001<br>  <strong>username: </strong>usr_name<br>  <strong>password: </strong>password<br>  <strong>tomcat:<br>    test-on-borrow: </strong>true<br>    <strong>test-on-connect: </strong>true<br>    <strong>validation-query: </strong>SELECT 1<br>    <strong>max-wait: </strong>30000<br><strong>jpa:<br>  database: </strong>mysql<br>  <strong>hibernate:<br>    ddl-auto: </strong>none<br>    <strong>naming:<br>      physical-strategy: </strong>org.hibernate.boot.model.naming.PhysicalNamingStrategyStandardImpl<br>  <strong>properties:<br>    hibernate:<br>      VirtualDatabaseName: </strong>Animals<br>      <strong>dialect: </strong>org.hibernate.dialect.MySQL5Dialect</pre><pre><strong>// ...</strong></pre><p>Pay attention to the JDBC driver <strong>driverClassName</strong> and database <strong>url</strong> properties. The JPA database setting as well as hibernate dialect are based on the database type you need. In our case it is MySQL.</p><p>The further usage of the datasource is like a general JPA entity. In case you want to create more connections to other databases from the same DataVirtuality instance, more datasource configurations will be needed.</p><p>That is it. Hope it helps.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b85fb6942b81" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>