<div style="border-bottom:1.5pt solid windowtext;border-left-style:none;border-right-style:none;border-top-style:none;padding:0cm 0cm 1.0pt;">Recently we got to be asked by a practitioner what is the difference between a software developer and a software engineer. This was the spark that made us write this blog on our website by answering this question.&nbsp;&nbsp;The terms 'software developer' and 'software engineer' have usually been interchangeably used in technology circles. However, they are quite distinguishable, with clear differences that do matter to people who are considering a career path in technology.&nbsp;&nbsp;If you are from Europe, then for sure you know that by law, in order to have the title of Engineer, you need to pass a certain certification, and that is where the titles differences between Engineer and Developer started. A developer usually writes and maintains code; an engineer designs solutions. If you are wondering, can an engineer also write code? It might but that is not its main purpose.&nbsp;After defining common points and key differentiates Between Software Developers and Software Engineers, we will expand the insight to a full stack developer, system developer, app developer as well.&nbsp;&nbsp;<h2>Points Common to Software Developers and Software Engineers</h2><ol><li>Programming Skills: Both of them possess very substantial programming skills and are familiar with a wide variety of programming languages, frameworks, and tools.</li><li>Problem-solving Ability: Both need to have immense problem-solving abilities for finding the problems, designing solutions, and implementing the same.</li><li>They work collectively in teams and therefore need to possess good communication and teamwork skills.</li></ol><h2>Key Differences Between Software Developers and Software Engineers</h2>&nbsp;<img src="https://admin.globalsoft.co/uploads/Key_Differences_61fa052f2b.png" alt="Key Differences.png" srcset="https://admin.globalsoft.co/uploads/thumbnail_Key_Differences_61fa052f2b.png 156w,https://admin.globalsoft.co/uploads/small_Key_Differences_61fa052f2b.png 500w,https://admin.globalsoft.co/uploads/medium_Key_Differences_61fa052f2b.png 750w,https://admin.globalsoft.co/uploads/large_Key_Differences_61fa052f2b.png 1000w," sizes="100vw" width="1200" height="1200">&nbsp;<ol><li>Educational Background: Most of the software engineers have educational backgrounds in computer science or related disciplines. The developers come from different backgrounds, from self-taught to attending boot camps.</li><li>Approach to Development: Software engineers follow best practices and strict rules. Developers might be more flexible and focus on getting the code to work.</li><li>Responsibilities: Engineers take up complete responsibility concerning the development lifecycle. In other words, developers usually focus on specific coding and not on the whole projects.</li><li>Theoretical Knowledge: This is what an engineer knows a lot about in the sphere of computer science, which is applied for making complicated systems. A developer stands for getting the job done.</li></ol><h2>Which one gets paid more: Software Engineer or Software Developer?</h2>&nbsp;Software engineers tend to get higher remuneration as compared to the software developers. In most cases, the difference based on location, experience, and industry varies. Due to a more in-depth comprehension of computer science and engineering principles, engineers have the ability to create extremely intricate software systems.&nbsp;&nbsp;<h2>Software Engineer vs. Full Stack Developer</h2>&nbsp;Comparing a software engineer to a full-stack developer, the main difference would fall in the focus and breadth of expertise. The software engineer will focus on the design, construction, and optimization of robust, scalable, and efficient software systems. His work’s main focus will involve the creation of a solid base in architecture for software, algorithm awareness, and quality cohesiveness of the system.&nbsp;On the other hand, full-stack developers are specialized software engineers who specialize in front-end and back-end development. The term “full stack” comes to mean they can handle the complete development process of a web application, from UI to server management and database management. However, since they are generalists, full-stack developers do not go as deep into technical complexities of each separate layer compared to a specialized software engineer.&nbsp;<h2>Software Engineer vs. System Developer</h2>&nbsp;Systems developers work closer to the hardware and deal with low-level operating system internals and device drivers. The focus is mainly on memory management, hardware constraints, and real-time performance; hence, more inclined towards optimization of code according to the particular architecture of hardware.&nbsp;By contrast, software engineers are high-level professionals who work with application software running on top of operating systems. They have special interests in the design of algorithms, user experiences, application architecture, and business logic. In essence, while system developers ensure that the foundational layer of software is running effectively, software engineers develop sophisticated applications based on these foundation systems.&nbsp;<h2>Software Engineer vs. App Developer</h2>&nbsp;Both of them create software, but the role and responsibilities differ quite a lot. The app developer specializes in mobile or platform-specific development, focusing on UI/UX design, platform guidelines, and performance optimization. They are capable of working with platform-specific technologies like Swift for iOS or Kotlin for Android.&nbsp;Software engineers work on higher levels of software, including desktop, enterprise, and web applications. They do higher-level system design, architecture, and engineering that involves putting several components together to create comprehensive software solutions.&nbsp;<h2>Conclusion</h2>&nbsp;Although there is some overlap in skills between software developers and engineers, they vary in significant respects. Engineers are more process-oriented and possess profound knowledge of computer science. In other words, the sole responsibility of engineers centers on the delivery of successful software solutions. On the other side, developers take everything in a pragmatic manner and focus on specific coding to implement features. It essentially focuses on practical aspects, hence can be flexible also.&nbsp;&nbsp;To put it simply, these differences will help an individual to choose between these two professions and on the other hand, helps an employer find exactly what they are looking for.</div>

Engineers are more process-oriented and possess profound knowledge of computer science. Developers take everything in a pragmatic manner and focus on specific coding to implement features.  

jozo 2.jpg

Software Developer vs. Software Engineer

What is the difference between Software Developer and Software Engineer

In one period of life, time becomes the most valuable resource. Some say that when it's used up, it's gone. When we put artificial intelligence in the context of time, we get a tool with which we can free up additional time. The question is what will we use that extra time for?&nbsp;How about using those few extra hours a week for things that are very important to us and that will help advance our career. This is exactly what artificial intelligence provides us. It allows us to leave the repetitive and time-consuming things to artificial intelligence and we use that time for strategic thinking, problem solving and creative activities.&nbsp;<img src="https://admin.globalsoft.co/uploads/1_cc847c970a.png" alt="1.png" srcset="https://admin.globalsoft.co/uploads/thumbnail_1_cc847c970a.png 156w,https://admin.globalsoft.co/uploads/small_1_cc847c970a.png 500w,https://admin.globalsoft.co/uploads/medium_1_cc847c970a.png 750w,https://admin.globalsoft.co/uploads/large_1_cc847c970a.png 1000w," sizes="100vw" width="1080" height="1080">&nbsp;In order to learn exactly which tasks in our daily work we can use AI for, we will first explore history together, progress in generative AI and machine learning. Are you ready to unlock your productivity? Let's learn how to do it together!&nbsp;<h2>History of AI</h2>&nbsp;The idea of Artificial Intelligence is not new; it goes back to the 1940s. In 1950, one of those mythological figures, Alan Turing, published his seminal work named "Computing Machinery and Intelligence," where he proposed this well-known Turing Test as a method for machine intelligence assessment.&nbsp;Fast forward to 1956-the term "Artificial Intelligence" was officially coined at the Dartmouth Conference, and AI as an independent field of study was thus born. Throughout the following decades, AI would experience cycles of hype and growth, followed by setbacks and cuts in funding that resulted in the first "AI winter" of the 1970s.&nbsp;Until the 1980s, a revival of interest in AI had been achieved through the success of expert systems in various industries. In the 1990s, the focus shifted to machine learning; thus, a direction toward data-driven approaches saw the development of algorithms for pattern recognition and neural networks.&nbsp;With the turn of the 2000s, there was great development in terms of processing power and data availability. This supported AI in a big way and led to breakthroughs in natural language processing and computer vision. The path now became clear for the common adoption of AI, which duly happened in the 2010s. During this period, the extensions in AI capabilities and implementations have proliferated remarkably across many sectors.&nbsp;Nowadays, we are into the age of AI innovation where continuous methodology and application breakthroughs are pushing the technology forward with an unprecedented advancing stride. Be it generative AI, deep learning, or multimodal interfaces, the possibilities for improving our work and daily life are limitless.&nbsp;&nbsp;<h2>Unleashing the Power of Generative AI and Effective Prompting</h2>&nbsp;The most interesting limits in AI turn out to be generative AI. This up-and-coming technology is a subcategory of deep learning that is focused on creating storytelling, human-similar content by learning from large datasets. The adaptability of generative AI keeps expanding really fast and offers creative solutions, from generating realistic images and videos to even text.&nbsp;The real power of generative AI, however, is in how this intelligence works in cooperation with human creativity. Through the intentional crafting of a clear, context-rich prompt, you will unlock the power of AI to improve your content creation process by melding its analytical power with your unique insights and ideas.&nbsp;Form your prompt with the CARE framework:&nbsp;<ul style="list-style-type:disc;"><li>Collaborative Goal,&nbsp;</li><li>Adding Context,&nbsp;</li><li>Real-World Application,&nbsp;</li><li>Expected Outcome.&nbsp;</li></ul>&nbsp;This guiding principle ensures that your prompts are aligned with your agile team's objectives, enabling AI to support your decision-making and problem-solving without overshadowing your human expertise.&nbsp;With embracing the generative AI possibilities, it also means that you will be rightly trespassing on ethical consideration. With this, you take up a responsible approach: reaffirm values of transparency and accountability. In so doing, this unlocks your creativity while ensuring that this transformational technology is appropriately applied to serve your needs.&nbsp;<h2>Agile with AI: Opening New Frontiers</h2>&nbsp;The use of AI together with agile practices stands at the forefront of constant change and evolution. Innovations like Artificial General Intelligence and Artificial Capable Intelligence are about to capture the way agile teams work by giving a deeper view, accomplishing complex tasks, and making teamwork easier.&nbsp;<img src="https://admin.globalsoft.co/uploads/2_11e0c60875.png" alt="2.png" srcset="https://admin.globalsoft.co/uploads/thumbnail_2_11e0c60875.png 156w,https://admin.globalsoft.co/uploads/small_2_11e0c60875.png 500w,https://admin.globalsoft.co/uploads/medium_2_11e0c60875.png 750w,https://admin.globalsoft.co/uploads/large_2_11e0c60875.png 1000w," sizes="100vw" width="1080" height="1080">&nbsp;&nbsp;Imagine having an AI-powered assistant to participate in all of your team meetings, to get comprehensive notes, capture action items, and free up that time needed to get to those strategic discussions or creative problem-solving that really drives agile projects. Alternatively, envision a diverse AI system that will go on to analyze not only verbal cues but also non-verbal ones, proffering custom solutions for improving communication and team dynamics.&nbsp;The more this becomes integrated capability within the workflow, the more significant the role agile practitioners play in bridging or connecting between technology and human-centric values. As AI competence is adopted and AI insights are integrated into agile processes, you can ensure such enhancements augment rather than replace your team's creativity and problem-solving ability.&nbsp;<h2>The Future of Work: AI Copilots and Autonomous Agents</h2>&nbsp;AI copilots are digital companions baked into the fabric of everyday tools, augmenting human capabilities by offering real-time support in everything from summaries of meetings to translations. This cadre of AI agents could free humans to become much more strategic, creative workers by improving efficiency, collaboration, and innovation.&nbsp;With AI-powered technologies going mainstream, practitioners will have to change with it-opening the mindsets to adaptability and continuous learning. You will gain an advantage in this regard through the development of competencies in the fields of data analysis, machine learning, and other uses regarding AI ethics, thereby positioning yourself as a vital bridge between technology and agile principles.&nbsp;<h2>Agility and Continuous Learning in Navigating the AI-Powered Future</h2>&nbsp;Agile and AI integration is a continuous evolution process that requires adaptation, vision, and perennial learning. The adoption of these kinds of transformational technologies means that one has to be open to continuous experimentation in the evolution toward new tools and processes that can benefit your team's efficiency and effectiveness.&nbsp;<img src="https://admin.globalsoft.co/uploads/3_ff6c825ec3.png" alt="3.png" srcset="https://admin.globalsoft.co/uploads/thumbnail_3_ff6c825ec3.png 156w,https://admin.globalsoft.co/uploads/small_3_ff6c825ec3.png 500w,https://admin.globalsoft.co/uploads/medium_3_ff6c825ec3.png 750w,https://admin.globalsoft.co/uploads/large_3_ff6c825ec3.png 1000w," sizes="100vw" width="1080" height="1080">&nbsp;It can only be kept by fostering a continuous-learning culture-both through formal education and informal sharing among peers. How would you assure that your agile skills, along with your AI competencies, stay pointed and current by incorporating a mixed range of learning strategies online? From courses to community discussions.&nbsp;&nbsp;In the end, the future of work rests in the balance between human and artificial inteligence capabilities. The search for adaptability, lifelong learning, and consideration of ethics unlocks productivity, innovation, and levels of collaboration one couldn't even dream of, whereby one can shape the future with intention and purpose.&nbsp;So, are you ready to use IA in your daily work for growing agility, creativity, and effectiveness?&nbsp;&nbsp;<h2>AI Tools That You Can Use Today&nbsp;</h2>&nbsp;<img src="https://admin.globalsoft.co/uploads/4_53044734a7.png" alt="4.png" srcset="https://admin.globalsoft.co/uploads/thumbnail_4_53044734a7.png 156w,https://admin.globalsoft.co/uploads/small_4_53044734a7.png 500w,https://admin.globalsoft.co/uploads/medium_4_53044734a7.png 750w,https://admin.globalsoft.co/uploads/large_4_53044734a7.png 1000w," sizes="100vw" width="1080" height="1080"><ul><li><a target="_blank" rel="noopener noreferrer" href="https://www.rewind.ai/">Rewind</a> is an AI that records your screen and audio so that you can review any meeting or task done, storing the data locally for greater privacy.</li><li><a target="_blank" rel="noopener noreferrer" href="https://chatgpt.com/">ChatGPT </a>by OpenAI is a powerful AI tool that generate human-like text, that finds its applications in drafting emails and even assisting coders-a major help in natural language processing.&nbsp;</li><li><a target="_blank" rel="noopener noreferrer" href="https://drawify.com/">Drawify </a>is an online visual content creation platform used in presentations, educational materials, and digital storytelling by adding personalized illustrations.&nbsp;</li><li><a target="_blank" rel="noopener noreferrer" href="https://lucidspark.com/product/collaborative-ai">LucidSpark </a>uses Collaborative AI to brainstorm, reveal central themes, and summarize your brainstorms to drive creativity and productivity for team projects.</li><li><a target="_blank" rel="noopener noreferrer" href="https://character.ai/">Character AI</a> offer tools to build, interact, and converse with AI characters.</li><li><a target="_blank" rel="noopener noreferrer" href="https://notebooklm.google/">NotebookLM</a> is a virtual research assistant, helping with organization and analysis of project-related documents.</li><li><a target="_blank" rel="noopener noreferrer" href="https://www.capcut.com/">CapCut</a> is a free video editor app with plenty of AI editing functions, including background removal, colour correction, and captioning, among others, which make video creation more accessible.</li><li><a target="_blank" rel="noopener noreferrer" href="https://huggingface.co/">Hugging Face</a> offers access to machine learning models and datasets, together with tools supporting the responsible integration of AI into products and workflows.</li><li><a target="_blank" rel="noopener noreferrer" href="https://www.spinach.io/home">Spinach</a> is an AI project manager doing the note-taking on behalf of the participants in meetings, capturing action items, and integrating with other existing tools to streamline project management.</li></ul>So, are you ready to use IA in your daily work for growing agility, creativity, and effectiveness?&nbsp;

Understand the how and the way to integrate AI that would set human skills working with machine intelligence to create unparalleled efficiency and innovation in today's workplace.

Unlock Your Productivity.png

Unlock Your Productivity: How AI Can Charge Your Workday

How AI Can Charge Your Workday

<h2>We develop your business ideas</h2>At globalsoft, our famous slogan is "We develop your business ideas" - just like we proudly state on our <a target="_blank" rel="noopener noreferrer" href="https://globalsoft.co">homepage</a>. But can every business idea really be turned into a successful product or software? Imagine yourself, dreaming of a perfect house on the coast to spend your retirement days in. But there are prerequisites for such ideas: is the beach sandy, will thunderstorms occur every other night, are good materials available and, of course, is the financial support there. Most of these criteria, if not all, need to be met in order for you to enjoy a visit by your grandchildren in that perfect beachfront house. The same rules can be applied to ideas that our clients, potential and current, bring to us.&nbsp;<h2>What is Proof of Concept (PoC) in software development?</h2>globalsoft, among its other services, offers <a target="_blank" rel="noopener noreferrer" href="https://www.globalsoft.co/services/product-development">Product development</a>. The first step in Product development, as you can see on that page, is Detailed analysis - we sit down with our clients and brainstorm the happy path as well as any "what if" scenarios, for those not-so-happy paths. The client will bring out multiple ideas, our team always adds some of our own views, and we sketch out a rough overview of what we want to accomplish. However, some ideas can't directly be visualized and have too many variables, both from a technical and from a business perspective. In such cases, especially when we have clients with their own pre-existing legacy code, we move towards creating a so-called Proof of Concept.&nbsp;Proof of Concept, or PoC for short, is the practice of setting time on the side before actual development, typically with the Product Owner and one or more members of the dev team in tandem, to devise and propose a possible solution and present it to the client. Development of the proof of concept is generally an intellectual task, spending time mostly in front of a whiteboard with multiple coloured markers, but can also be a technical task, at least in part, as feasibility from a technical perspective has to be checked - no point in a great idea if you can't transform it into code.&nbsp;<h2>How to write Proof of Concept</h2>To start creating a Proof of Concept you need the third word - a concept. It can be a vague thought or a clear and concise requirement, but in any case it requires careful definition. The know-how of our Business Analysts and/or Product Owners, as well as experienced engineers, is important here, as now is the time to write down certain questions:<ol style="list-style-type:decimal;"><li>What is the Concept?</li><li>What is the targeted audience?</li><li>What is the happy path?</li><li>How to handle not-so-happy paths?</li><li>What would be a measurable outcome to determine success or failure, or in other words, to Prove the Concept?</li></ol>When these questions are answered, then the more concrete items come into the calculation:<ol style="list-style-type:decimal;"><li>What resources are needed, both financial and technical?</li><li>Can any potential dangers already be assessed?</li></ol>These questions can, and usually should, be asked in iterations, as during such brainstorming sessions, some new information will be revealed or unexpected problems might occur - budgets always change, the client comes up with a new idea, frameworks prove to be inadequate etc.&nbsp;After completing one or more rounds of these questions, and all the polishing in the end, the results are presented to the client, and the client usually to their own shareholder, for final approval. All information needs to be presented, both good and bad, as hiding potential risks can work in the short-term, but long-term and successful relationships require open communication and stating the facts - as the saying goes, "warts and all". If the Concept is Proven, then our work is done for that part of the Product Development.&nbsp;<h2>Proof of Concept vs. MVP</h2>Since <a target="_blank" rel="noopener noreferrer" href="https://www.globalsoft.co/services/mvp-launcher">MVP</a>, or "Minimal viable product" is a term often used in software development, we have sometimes been asked "What is the difference?". MVP is a set of tasks and features that have been determined by the client as a minimum set necessary for testing and possibly even using in real life, which are then layered upon with additional features and fixes. They are usually preceded by one or more Proof of Concepts, as any features needed in an MVP should be well thought about before dedicating precious time and resources into their development. Proof of Concept generally demonstrate feasibility - can it be done, while the V in MVP means viability - can the product of software earn money, market share or some other concrete goal.&nbsp;<h2>globalsoft PoC case study</h2>Although we have more detailed case studies which you can view <a target="_blank" rel="noopener noreferrer" href="https://www.globalsoft.co/case-studies">here</a>, we can offer you a quick example of Proof of Concept in our own development. For one of our clients, who brought to us their inherited legacy frontend code, we were tasked with introducing a new feature. Since the backend, which was not under our domain, did not directly support this new wanted feature, we offered the client to investigate the matter directly for a number of days to see if we can improvize using other existing features. The PO and dedicated developer took 3 days and found a possible solution which they then presented to the client - along with the benefits, e.g. having the wanted feature, and the short-comings, e.g. response time and complexity of setup and maintenance. After analysis, the client decided the "pros" outweighed the "cons" and decided to go forward with the feature. Starting with the results of the PoC and the feedback by the client who have now seen their feature "in action", the Product development team did an ever better job than expected, bringing an ever bigger smile, as well as some additional revenue, to our client. &nbsp;

hand writing.jpg

What is Proof of Concept in software development?

<h2>What is Strapi?</h2>Strapi is an open-source headless CMS (Content Management System) that enables developers to create and manage content-rich applications effortlessly. It provides a powerful and flexible back-end infrastructure while allowing you to use any front-end technology you prefer, such as React, Vue.js, or Angular.&nbsp;<h2>Benefits of Using Strapi</h2><ul><li>Flexibility: build APIs tailored to your needs and integrate them with any front-end framework or platform.&nbsp;</li><li>Efficiency: Save development time with automatic API generation and a user-friendly content management interface.</li><li>Community and Support: As an open-source project, Strapi has a growing community of developers contributing to its ecosystem, offering plugins, tutorials, and support.</li></ul>Strapi is an excellent choice for developers seeking a customizable, efficient, and powerful CMS to manage and deliver content seamlessly across multiple platforms.&nbsp;<h2>Automate Strapi deployment</h2>Before you start automating the deployment of Strapi to an instance, you need a few things: &nbsp;<ul><li>dockerize Strapi</li><li>Google instance</li><li>Google storage bucket for database backup and</li><li>GitLab cI script.</li></ul>&nbsp;<h2>Running Strapi in a Docker Container</h2>Using Docker Compose simplifies managing complex application environments by offering:<ul><li>Consistency: ensures consistent setups across environments.&nbsp;</li><li>Simplified Configuration: manages all configurations in one YAML file.&nbsp;</li><li>Scalability: easily scale applications up or down.&nbsp;</li><li>Dependency Management: handles multiple dependencies effortlessly. &nbsp;</li><li>Backup and Restore: encapsulates the entire stack for easy backup.</li></ul>For easy backup:<ul><li>Backup Docker Compose file: contains application definitions.</li><li>Backup Data Volumes: export persistent data volumes.</li><li>Version Control: store files in Git for tracking changes.</li><li>Automate Backup Tasks: set up automated backups for efficiency.</li></ul> Using Docker to run Strapi can streamline the setup process and ensure a consistent environment across different development stages. Here's a step-by-step guide to get Strapi up and running in a Docker container:<pre><code class="language-plaintext">FROM node:18-alpine3.18 
# Installing libvips-dev for sharp Compatibility 
RUN apk update &amp;&amp; apk add --no-cache build-base gcc autoconf automake zlib-dev libpng-dev nasm bash vips-dev git 
ARG NODE_ENV=development 
ENV NODE_ENV=${NODE_ENV} 

WORKDIR /opt/ 
COPY package.json yarn.lock ./ 
RUN yarn global add node-gyp 
RUN yarn config set network-timeout 600000 -g &amp;&amp; yarn install 
ENV PATH /opt/node_modules/.bin:$PATH 

WORKDIR /opt/app 
COPY . . 
RUN chown -R node:node /opt/app 
USER node 
RUN ["yarn", "build"] 
EXPOSE 1337 
CMD ["yarn", "develop"] </code></pre> Now it's time to write Docker Compose: &nbsp;<pre><code class="language-plaintext">version: "3"
services:
 strapi:
 container_name: strapi
 build: .
 image: strapi:latest
 restart: unless-stopped
 env_file: .env
 environment:
 DATABASE_CLIENT: ${DATABASE_CLIENT}
 DATABASE_HOST: strapiDB
 DATABASE_PORT: ${DATABASE_PORT}
 DATABASE_NAME: ${DATABASE_NAME}
 DATABASE_USERNAME: ${DATABASE_USERNAME}
 DATABASE_PASSWORD: ${DATABASE_PASSWORD}
 JWT_SECRET: ${JWT_SECRET}
 ADMIN_JWT_SECRET: ${ADMIN_JWT_SECRET}
 APP_KEYS: ${APP_KEYS}
 NODE_ENV: ${NODE_ENV}
 volumes:
 - ./config:/opt/app/config
 - ./src:/opt/app/src
 - ./package.json:/opt/package.json
 - ./yarn.lock:/opt/yarn.lock
 - ./.env:/opt/app/.env
 - ./public/uploads:/opt/app/public/uploads
 ports:
 - "1337:1337"
 networks:
 - strapi
 depends_on:
 - strapiDB
 strapiDB:
 container_name: strapiDB
 platform: linux/amd64 #for platform error on Apple M1 chips
 restart: unless-stopped
 env_file: .env
 image: postgres:12.0-alpine
 environment:
 POSTGRES_USER: ${DATABASE_USERNAME}
 POSTGRES_PASSWORD: ${DATABASE_PASSWORD}
 POSTGRES_DB: ${DATABASE_NAME}
 volumes:
 - strapi-data:/var/lib/postgresql/data/ #using a volume
 #- ./data:/var/lib/postgresql/data/ # if you want to use a bind folder
 ports:
 - "5432:5432"
 networks:
 - strapi
volumes:
 strapi-data:
networks:
 strapi:
 name: Strapi
 driver: bridge </code></pre>&nbsp;<h3>Database Backup</h3>Now it is very important to write a shell script and set up a cron job to run every day for a base backup on Google Cloud Bucket.<pre><code class="language-plaintext">echo "0 4 * * * /usr/share/strapi/base_backup.sh" | crontab - </code></pre>Here is an example of the script:<pre><code class="language-plaintext">#!/bin/bash 
# Source the .env file 
source /usr/share/strapi/.env 
# Step 2: Connect to the PostgreSQL container and perform backup 
docker compose exec -T strapiDB sh &lt;&lt; 'EOF' 
# Step 3: Execute the backup command (inside the container) 
pg_dump -U postgres -d postgres &gt; /var/lib/postgresql/data/backup_$(date +%Y%m%d).sql 
EOF 
 
# Step 5: Copy the backup file from the container to host 
docker cp $(docker compose ps -q strapiDB):/var/lib/postgresql/data/backup_$(date +%Y%m%d).sql /usr/share/strapi/backup_base/ 
 
# Step 6: Upload the backup file to Google Cloud Storage 
gsutil cp /usr/share/strapi/backup_base/*.sql gs://$STORAGE_CLOUD_DB/ </code></pre> Now you have a ready Docker Compose file and a database backup shell script. You can now write a GitLab CI script to automatically connect to the instance and run Docker Compose for Strapi.&nbsp;You can connect to the instance using SSH with GitLab CI, copy the Docker Compose file, and then run it.&nbsp;In GitLab CI, you can define two types of deployment stages: "stage" and "prod". These stages help organize the deployment process, allowing for distinct actions at different points in the pipeline. For example, you can designate the "stage" stage to run when you merge changes into the main branch, ensuring that your developments are thoroughly tested before moving further. Conversely, you assign the "prod" stage to execute when you tag a release, indicating that the code is ready for production deployment. This separation of stages streamlines the deployment workflow, enhancing efficiency and reliability in software delivery.&nbsp;<h2>Cost-saving advice</h2>In addition to optimizing your deployment pipeline, there are further strategies you can employ to reduce expenses in cloud infrastructure. For instance, if you maintain a staging instance for testing and development purposes, it may not be necessary to keep it running continuously. Leveraging features provided by platforms like Google Cloud, you can schedule the instance to automatically turn on and off based on your usage patterns.&nbsp;By implementing this proactive approach, you can significantly lower your operational costs while still maintaining the flexibility and accessibility of your staging environment.&nbsp;This simple yet effective cost-saving measure demonstrates your commitment to efficient resource management and financial sustainability in your cloud operations.&nbsp; &nbsp;

Discover the optimized efficiency of automated Strapi deployment, ensuring continuous integration and improved productivity for your projects.

what is strapi.jpg

Automated Strapi Deployment

Automated Strapi Deployment: Simplifying Your Workflow

You are building a new product, creating product development plan, investigating development process, looking for a new company to build your idea. If yes, then let’s see how Design Thinking with Scrum can help you with this process.&nbsp;<h2>More Innovative Solutions with 5 Stages in the Design Thinking Process</h2>If you are, while designing your product, thinking about end user, your customer, you could say that you started with Design Thinking. What is common for Scrum and Design Thinking? They both deal with complex problems. How user will behave, think or how your product could change his life, Hasso Plattner, Institute of Design at Stanford proposed five stage Design Thinking model: Empathize, Define, Ideate, Prototype, Test.&nbsp;<figure class="image"><img style="aspect-ratio:1920/1080;" src="https://admin.globalsoft.co/uploads/5_stages_in_the_Design_Thinking_process_f267de9714.jpg" alt="5_stages_in_the_Design_Thinking_process.jpg" srcset="https://admin.globalsoft.co/uploads/thumbnail_5_stages_in_the_Design_Thinking_process_f267de9714.jpg 245w,https://admin.globalsoft.co/uploads/small_5_stages_in_the_Design_Thinking_process_f267de9714.jpg 500w,https://admin.globalsoft.co/uploads/medium_5_stages_in_the_Design_Thinking_process_f267de9714.jpg 750w,https://admin.globalsoft.co/uploads/large_5_stages_in_the_Design_Thinking_process_f267de9714.jpg 1000w," sizes="100vw" width="1920" height="1080"></figure>&nbsp;<h3>Empathize</h3> In this phase you need to understand your users, their needs and the problems, problems that will be solved by using your product. Good thing is if company that will build your product is using Scrum. One artefact in Scrum is Product Goal. When Scrum Team is building product, they always have Product Goal in mind. It didn’t all started with Product Goal, it started from Vision, Product Vision, Product Roadmap to Product Goal. Both in common to Design Thinking and Scrum is to have end user on mind. When you search for a company that will create a product, company that you are entering product development process with, expect to talk about and users as well, there is nothing worse than build a product that nobody use. If you fail, fail early. You have opportunity to inspect and adapt.&nbsp;<h3>Define</h3>&nbsp; Think of your product as a solution for customer problems, needs. Think about features that are solving problems. Communicate your product as solution to client’s problems to company that is building your product as well. Be on the same page. Scrum will help you with increment development, every iteration called Sprint is adding value to your product, you are able to collect feedback as product is developing to gain feedback early. When you are invited to Sprint Review event, by the team that is building your product, please don’t skip it. This is your opportunity to redefine, to give feedback, to coordinate with your product development plan.&nbsp;&nbsp;<h3>Ideate&nbsp;</h3> All team members are suggesting ideas, here is when psychological safety comes in place. In psychological safe environment team members feel safe to talk. Whether you are empowering existing product, developing your product idea from the beginning as MVP, celebrate every suggested idea. In some companies, people are rewarded for rejected ideas. If you are in situation where ideas are coming one after one you are lucky. So, when you chose company for product development, “listen” carefully.&nbsp;<h3>Prototype</h3> It is time to create your solutions for previously defined problems. This is when Product Backlog is created. It is a prioritized list of work for the developers that is derived from the roadmap and its requirements. Product Backlog items on top goes to iteration, at the end of iteration called Sprint you will see first prototype. Inputs for Product Backlog are very important. They are coming from product vision, product roadmap, customers, marketing, sales… When communicating your requirements with company for product development let them be SMART (Specific, Measurable, Achievable, Relevant and Time-based).&nbsp;<h3>Test&nbsp;</h3> Now your users are testing your solution, giving you feedback so you can go into next production iteration. Try your solution and gain feedback from customers. Both with Design Thinking and Scrum you have 3 pillars of Empiricism in place: Transparency, Inspection and Adaption. Use them all.&nbsp;<h2>Core Principles of Design Thinking</h2><figure class="image"><img style="aspect-ratio:1920/1080;" src="https://admin.globalsoft.co/uploads/Core_principles_0b416f98c1.jpg" alt="Core_principles.jpg" srcset="https://admin.globalsoft.co/uploads/thumbnail_Core_principles_0b416f98c1.jpg 245w,https://admin.globalsoft.co/uploads/small_Core_principles_0b416f98c1.jpg 500w,https://admin.globalsoft.co/uploads/medium_Core_principles_0b416f98c1.jpg 750w,https://admin.globalsoft.co/uploads/large_Core_principles_0b416f98c1.jpg 1000w," sizes="100vw" width="1920" height="1080"></figure> There are several key principles that guide the process in Design Thinking that you could use:<ul><li>Human Centred – focus on creating solutions that meet customers requirements. Customer is in the centre of your mind. You are solving his problems.&nbsp;</li><li>Empathy – Design Thinking is calling for active listening, understanding clients’ emotions and motivators. This is why we are born with two ears and one mouth. Iterative Process – transparent process that enables to inspect and adapt, delivering value with each iteration.&nbsp;</li><li>Collaboration – all Scrum events are calling team members to collaborate because it leads to more creative solutions, effective ones.&nbsp;</li><li>Mindset – all that you were able to read previously is a matter of a mindset. If you get value from this blog post that means you have a mindset for it.</li></ul>This principle enables you to build product that are meaningful and have impact for end users.&nbsp;<h2>Impact of Design Thinking on Product Development</h2>Design Thinking is not just impacting product development it starts from Vision. First vision was created in mind, so we can say that Design Thinking is a mindset, as well as Agile, mindset that can be applied across all aspects of a business enabling solutions to complex problems.Right mindset is in place when principles come to live. Both Agile and Design Thinking principles foster collaboration, encouraging employees to think outside the box and experiment for solutions. Make decisions based on experiences. Look for a feedback loop. Gain your deserved market share.&nbsp;<h2>Embrace a Mindset to Design Thinking</h2>When you are practicing empathy just put yourself into customers shoes. Think from different position. If you need, put yourself in third position as well and think like observer. Remember how acters are preparing for their roles, in real time situations most of the time. You are preparing yourself to solve real problems and empathy can help.If you are a real talent but you can’t collaborate with others, you miss lots of chances for success. Collaboration fosters creativity, generates innovative solutions. Freedom to experiment and psychological safety, encourages a culture of experimentation and iteration. It values the process of trial and error, allowing designers to explore multiple solutions, refine ideas based on feedback, and iterate until they arrive at the most viable and effective solution (MVP). This freedom to experiment encourages risk-taking, fosters creativity, and ultimately leads to great innovations.Having a mindset to design thinking with empathy, collaboration, and creating an environment where experimentation is encouraged, complex challenges can be led to meaningful innovation.&nbsp;<figure class="image"><img style="aspect-ratio:1200/1200;" src="https://admin.globalsoft.co/uploads/Mindset_5429e3e925.jpg" alt="Mindset.jpg" srcset="https://admin.globalsoft.co/uploads/thumbnail_Mindset_5429e3e925.jpg 156w,https://admin.globalsoft.co/uploads/small_Mindset_5429e3e925.jpg 500w,https://admin.globalsoft.co/uploads/medium_Mindset_5429e3e925.jpg 750w,https://admin.globalsoft.co/uploads/large_Mindset_5429e3e925.jpg 1000w," sizes="100vw" width="1200" height="1200"></figure>&nbsp;<h2>What if You Ignore Design Thinking?</h2>Nothing will happen, or you could build something that nobody uses. &nbsp;It is up to you.&nbsp; &nbsp;

You don't have to choose between Scrum and Design Thinking, combine them for successful product development, read how.

Sie entwickeln ein neues Produkt, erstellen einen Entwicklungsplan, untersuchen den Entwicklungsprozess, suchen ein neues Unternehmen, das Ihre Idee umsetzen soll? Wenn ja, dann lassen Sie uns sehen, wie Design Thinking mit Scrum Ihnen bei diesem Prozess helfen kann.&nbsp;<heading>Mehr innovative Lösungen mit den 5 Stufen des Design Thinking Prozesses</heading>&nbsp;<h2>Mehr innovative Lösungen mit 5 Phasen im Design Thinking-Prozess</h2>Wenn Sie bei der Entwicklung Ihres Produkts an den Endverbraucher, Ihren Kunden, denken, könnten Sie sagen, dass Sie mit Design Thinking begonnen haben. Was haben Scrum und Design Thinking gemeinsam? Sie beschäftigen sich beide mit komplexen Problemen. Hasso Plattner vom Institute of Design in Stanford schlug ein fünfstufiges Design Thinking Modell vor, bei dem es darum geht, wie sich der Benutzer verhält, wie er denkt oder wie das Produkt sein Leben verändern könnte: Einfühlung, Definierung, Ideenfindung, Prototyp, Test.&nbsp;<figure class="image"><img style="aspect-ratio:1920/1080;" src="https://admin.globalsoft.co/uploads/5_Stufen_d651855be3.jpg" alt="5_Stufen.jpg" srcset="https://admin.globalsoft.co/uploads/thumbnail_5_Stufen_d651855be3.jpg 245w,https://admin.globalsoft.co/uploads/small_5_Stufen_d651855be3.jpg 500w,https://admin.globalsoft.co/uploads/medium_5_Stufen_d651855be3.jpg 750w,https://admin.globalsoft.co/uploads/large_5_Stufen_d651855be3.jpg 1000w," sizes="100vw" width="1920" height="1080"></figure><heading>Einfühlung</heading>&nbsp;<h2>Einfühlung</h2>In dieser Phase müssen Sie Ihre Benutzer, ihre Bedürfnisse und die Probleme verstehen, die durch die Verwendung Ihres Produkts gelöst werden sollen. Es ist gut, wenn das Unternehmen, das Ihr Produkt herstellen wird, Scrum verwendet. Eines der Artefakte in Scrum ist das Produktziel. Wenn das Scrum-Team ein Produkt entwickelt, hat es immer das Produktziel im Blick. Es hat nicht alles mit dem Product Goal angefangen, sondern mit der Idee, der Product Vision, der Product Roadmap und dem Product Goal. Design Thinking und Scrum haben beide gemeinsam, dass sie den Endverbraucher im Blick haben. Wenn Sie ein Unternehmen suchen, das ein Produkt entwickeln soll, ein Unternehmen, mit dem Sie in den Produktentwicklungsprozess einsteigen, erwarten Sie, dass Sie darüber sprechen und auch die Benutzer im Blick haben, denn es gibt nichts Schlimmeres, als ein Produkt zu bauen, das niemand benutzt. Wenn Sie scheitern, scheitern Sie früh. Sie haben die Möglichkeit, das Produkt zu überprüfen und anzupassen.&nbsp;&nbsp;<h2>Definierung</h2><heading>Definierung</heading>&nbsp;Betrachten Sie Ihr Produkt als eine Lösung für die Probleme und Bedürfnisse Ihrer Kunden. Denken Sie an Funktionen, die Probleme lösen. Vermitteln Sie Ihr Produkt als Lösung für die Probleme des Kunden auch dem Unternehmen, das Ihr Produkt herstellt. Seien Sie auf der gleichen Seite. Scrum hilft Ihnen bei der schrittweisen Entwicklung. Jede Iteration, die Sprint genannt wird, steigert den Wert Ihres Produkts, und Sie können während der Produktentwicklung Feedback einholen, um frühzeitig Rückmeldungen zu erhalten. Wenn Sie von dem Team, das Ihr Produkt entwickelt, zu einem Sprint Review eingeladen werden, sollten Sie dies nicht auslassen. Dies ist Ihre Gelegenheit, Ihr Produkt neu zu definieren, Feedback zu geben und es mit Ihrem Produktentwicklungsplan abzustimmen.&nbsp;<h2>Ideenfindung</h2><heading>Ideenfindung</heading>Alle Teammitglieder schlagen Ideen vor. Hier kommt die psychologische Sicherheit ins Spiel. In einer psychologisch sicheren Umgebung können alle Teammitglieder frei reden. Egal, ob Sie ein bestehendes Produkt verbessern oder Ihre Produktidee von Anfang an als MVP entwickeln, Sie sollten jede vorgeschlagene Idee begrüßen. In einigen Unternehmen werden die Mitarbeiter für abgelehnte Ideen belohnt. Wenn Sie in einer Situation sind, in der eine Idee nach der anderen kommt, haben Sie Glück. Wenn Sie also ein Unternehmen für die Produktentwicklung auswählen, sollten Sie genau zuhören.&nbsp;<h2>Prototyp</h2>Es ist Zeit, Ihre Lösungen für die zuvor definierten Probleme zu erstellen. Dies ist der Zeitpunkt, zu dem das Product Backlog erstellt wird. Dabei handelt es sich um eine nach Prioritäten geordnete Liste von Aufgaben für die Entwickler, die aus der Roadmap und den Anforderungen abgeleitet wird. Die obersten Elemente des Product Backlogs gehen in die Iteration. Am Ende der Iteration, die Sprint genannt wird, sehen Sie den ersten Prototyp. Die Inputs für das Product Backlog sind sehr wichtig. Sie stammen von der Produktvision, der Produkt-Roadmap, den Kunden, dem Marketing, dem Vertrieb... Wenn Sie Ihre Anforderungen für die Produktentwicklung mit dem Unternehmen kommunizieren, sollten sie SMART sein (Spezifisch, Messbar, Erreichbar, Realistisch und Zeitbezogen).&nbsp;<heading>Test</heading>&nbsp;&nbsp;<h2>Test</h2>Jetzt testen Ihre Nutzer Ihre Lösung und geben Ihnen Feedback, damit Sie in die nächste Produktionsiteration gehen können. Testen Sie Ihre Lösung und holen Sie das Feedback Ihrer Kunden ein. Sowohl mit Design Thinking als auch mit Scrum verfügen Sie über 3 Grundpfeiler der Empirie: Transparenz, Prüfung und Anpassung. Nutzen Sie sie alle.&nbsp;<heading>Grundprinzipien des Design Thinking</heading> <img>&nbsp;<h2>Grundprinzipien</h2><img src="https://admin.globalsoft.co/uploads/Grundprinzipien_a7284092b7.jpg" alt="Grundprinzipien.jpg" srcset="https://admin.globalsoft.co/uploads/thumbnail_Grundprinzipien_a7284092b7.jpg 245w,https://admin.globalsoft.co/uploads/small_Grundprinzipien_a7284092b7.jpg 500w,https://admin.globalsoft.co/uploads/medium_Grundprinzipien_a7284092b7.jpg 750w,https://admin.globalsoft.co/uploads/large_Grundprinzipien_a7284092b7.jpg 1000w," sizes="100vw" width="1920" height="1080">&nbsp;Es gibt mehrere Grundprinzipien, die den Prozess des Design Thinking leiten und die Sie nutzen können:&nbsp;<ul><li>Menschenorientiert - konzentrieren Sie sich auf die Entwicklung von Lösungen, die den Anforderungen der Kunden entsprechen. Der Kunde steht im Mittelpunkt Ihres Denkens. Sie sind dabei, seine Probleme zu lösen.&nbsp;</li><li>Empathize - Design Thinking erfordert aktives Zuhören, das Verstehen der Emotionen und Motivatoren des Kunden. Aus diesem Grund hat jeder von uns zwei Ohren und einen Mund. • Iterativer Prozess - ein transparenter Prozess, der es ermöglicht, zu prüfen und anzupassen und mit jeder Iteration einen Mehrwert zu liefern.&nbsp;</li><li>Zusammenarbeit - alle Scrum Events fordern die Teammitglieder zur Zusammenarbeit auf, weil dies zu kreativeren und effektiveren Lösungen führt.&nbsp;</li><li>Mindset - alles, was Sie bisher lesen konnten, ist eine Frage des Mindsets. Wenn dieser Blogbeitrag für Sie von Nutzen ist, bedeutet das, dass Sie eine entsprechende Einstellung haben.&nbsp;</li></ul>&nbsp;Dieses Prinzip ermöglicht es Ihnen, Produkte zu entwickeln, die für den Endverbraucher sinnvoll sind und Wirkung zeigen.&nbsp;<heading>Auswirkungen von Design Thinking auf die Produktentwicklung</heading>&nbsp;&nbsp;<div class="flex-shrink-0 flex flex-col relative items-end"><div><div class="pt-0.5 juice:pt-0"><div class="gizmo-bot-avatar flex h-6 w-6 items-center justify-center overflow-hidden rounded-full juice:h-8 juice:w-8"><div class="relative p-1 rounded-sm flex items-center justify-center bg-token-main-surface-primary text-token-text-primary h-8 w-8"><svg class="icon-md" width="41" height="41" viewBox="0 0 41 41" fill="none" xmlns="http://www.w3.org/2000/svg" role="img"><text x="-9999" y="-9999"></text><path d="M37.5324 16.8707C37.9808 15.5241 38.1363 14.0974 37.9886 12.6859C37.8409 11.2744 37.3934 9.91076 36.676 8.68622C35.6126 6.83404 33.9882 5.3676 32.0373 4.4985C30.0864 3.62941 27.9098 3.40259 25.8215 3.85078C24.8796 2.7893 23.7219 1.94125 22.4257 1.36341C21.1295 0.785575 19.7249 0.491269 18.3058 0.500197C16.1708 0.495044 14.0893 1.16803 12.3614 2.42214C10.6335 3.67624 9.34853 5.44666 8.6917 7.47815C7.30085 7.76286 5.98686 8.3414 4.8377 9.17505C3.68854 10.0087 2.73073 11.0782 2.02839 12.312C0.956464 14.1591 0.498905 16.2988 0.721698 18.4228C0.944492 20.5467 1.83612 22.5449 3.268 24.1293C2.81966 25.4759 2.66413 26.9026 2.81182 28.3141C2.95951 29.7256 3.40701 31.0892 4.12437 32.3138C5.18791 34.1659 6.8123 35.6322 8.76321 36.5013C10.7141 37.3704 12.8907 37.5973 14.9789 37.1492C15.9208 38.2107 17.0786 39.0587 18.3747 39.6366C19.6709 40.2144 21.0755 40.5087 22.4946 40.4998C24.6307 40.5054 26.7133 39.8321 28.4418 38.5772C30.1704 37.3223 31.4556 35.5506 32.1119 33.5179C33.5027 33.2332 34.8167 32.6547 35.9659 31.821C37.115 30.9874 38.0728 29.9178 38.7752 28.684C39.8458 26.8371 40.3023 24.6979 40.0789 22.5748C39.8556 20.4517 38.9639 18.4544 37.5324 16.8707ZM22.4978 37.8849C20.7443 37.8874 19.0459 37.2733 17.6994 36.1501C17.7601 36.117 17.8666 36.0586 17.936 36.0161L25.9004 31.4156C26.1003 31.3019 26.2663 31.137 26.3813 30.9378C26.4964 30.7386 26.5563 30.5124 26.5549 30.2825V19.0542L29.9213 20.998C29.9389 21.0068 29.9541 21.0198 29.9656 21.0359C29.977 21.052 29.9842 21.0707 29.9867 21.0902V30.3889C29.9842 32.375 29.1946 34.2791 27.7909 35.6841C26.3872 37.0892 24.4838 37.8806 22.4978 37.8849ZM6.39227 31.0064C5.51397 29.4888 5.19742 27.7107 5.49804 25.9832C5.55718 26.0187 5.66048 26.0818 5.73461 26.1244L13.699 30.7248C13.8975 30.8408 14.1233 30.902 14.3532 30.902C14.583 30.902 14.8088 30.8408 15.0073 30.7248L24.731 25.1103V28.9979C24.7321 29.0177 24.7283 29.0376 24.7199 29.0556C24.7115 29.0736 24.6988 29.0893 24.6829 29.1012L16.6317 33.7497C14.9096 34.7416 12.8643 35.0097 10.9447 34.4954C9.02506 33.9811 7.38785 32.7263 6.39227 31.0064ZM4.29707 13.6194C5.17156 12.0998 6.55279 10.9364 8.19885 10.3327C8.19885 10.4013 8.19491 10.5228 8.19491 10.6071V19.808C8.19351 20.0378 8.25334 20.2638 8.36823 20.4629C8.48312 20.6619 8.64893 20.8267 8.84863 20.9404L18.5723 26.5542L15.206 28.4979C15.1894 28.5089 15.1703 28.5155 15.1505 28.5173C15.1307 28.5191 15.1107 28.516 15.0924 28.5082L7.04046 23.8557C5.32135 22.8601 4.06716 21.2235 3.55289 19.3046C3.03862 17.3858 3.30624 15.3413 4.29707 13.6194ZM31.955 20.0556L22.2312 14.4411L25.5976 12.4981C25.6142 12.4872 25.6333 12.4805 25.6531 12.4787C25.6729 12.4769 25.6928 12.4801 25.7111 12.4879L33.7631 17.1364C34.9967 17.849 36.0017 18.8982 36.6606 20.1613C37.3194 21.4244 37.6047 22.849 37.4832 24.2684C37.3617 25.6878 36.8382 27.0432 35.9743 28.1759C35.1103 29.3086 33.9415 30.1717 32.6047 30.6641C32.6047 30.5947 32.6047 30.4733 32.6047 30.3889V21.188C32.6066 20.9586 32.5474 20.7328 32.4332 20.5338C32.319 20.3348 32.154 20.1698 31.955 20.0556ZM35.3055 15.0128C35.2464 14.9765 35.1431 14.9142 35.069 14.8717L27.1045 10.2712C26.906 10.1554 26.6803 10.0943 26.4504 10.0943C26.2206 10.0943 25.9948 10.1554 25.7963 10.2712L16.0726 15.8858V11.9982C16.0715 11.9783 16.0753 11.9585 16.0837 11.9405C16.0921 11.9225 16.1048 11.9068 16.1207 11.8949L24.1719 7.25025C25.4053 6.53903 26.8158 6.19376 28.2383 6.25482C29.6608 6.31589 31.0364 6.78077 32.2044 7.59508C33.3723 8.40939 34.2842 9.53945 34.8334 10.8531C35.3826 12.1667 35.5464 13.6095 35.3055 15.0128ZM14.2424 21.9419L10.8752 19.9981C10.8576 19.9893 10.8423 19.9763 10.8309 19.9602C10.8195 19.9441 10.8122 19.9254 10.8098 19.9058V10.6071C10.8107 9.18295 11.2173 7.78848 11.9819 6.58696C12.7466 5.38544 13.8377 4.42659 15.1275 3.82264C16.4173 3.21869 17.8524 2.99464 19.2649 3.1767C20.6775 3.35876 22.0089 3.93941 23.1034 4.85067C23.0427 4.88379 22.937 4.94215 22.8668 4.98473L14.9024 9.58517C14.7025 9.69878 14.5366 9.86356 14.4215 10.0626C14.3065 10.2616 14.2466 10.4877 14.2479 10.7175L14.2424 21.9419ZM16.071 17.9991L20.4018 15.4978L24.7325 17.9975V22.9985L20.4018 25.4983L16.071 22.9985V17.9991Z" fill="currentColor"></path></svg></div></div></div></div></div><div class="group/conversation-turn relative flex w-full min-w-0 flex-col agent-turn"><div class="flex-col gap-1 md:gap-3"><div class="flex flex-grow flex-col max-w-full"><div class="min-h-[20px] text-message flex flex-col items-start whitespace-pre-wrap break-words [.text-message+&amp;]:mt-5 juice:w-full juice:items-end overflow-x-auto gap-2" data-message-author-role="assistant" data-message-id="584b38aa-05d8-4321-959b-91a2e4ff57ce" dir="auto"><div class="flex w-full flex-col gap-1 juice:empty:hidden juice:first:pt-[3px]"><div class="markdown prose w-full break-words dark:prose-invert dark"><h2>Auswirkungen von Design Thinking auf die Produktentwicklung</h2></div></div></div></div></div></div>Design Thinking wirkt sich nicht nur auf die Produktentwicklung aus, sondern beginnt mit der Vision. Wir können also sagen, dass Design Thinking sowohl eine Denkweise als auch etwas Agiles ist, die auf alle Aspekte eines Unternehmens angewendet werden kann und Lösungen für komplexe Probleme ermöglicht. Die richtige Denkweise ist vorhanden, wenn die Prinzipien zum Leben erweckt werden. Sowohl Agile- als auch Design Thinking Prinzipien fördern die Zusammenarbeit und ermutigen die Mitarbeiter, über den Tellerrand hinauszuschauen und nach Lösungen zu suchen. Treffen Sie Entscheidungen auf der Grundlage von Erfahrungen. Suchen Sie nach einer Feedbackschleife. Gewinnen Sie Ihren verdienten Marktanteil.&nbsp;&nbsp;<h2>Eine Denkweise des Design Thinking annehmen</h2><heading>Machen Sie sich eine Denkweise zu eigen, die auf Design ausgerichtet ist </heading>Wenn Sie Empathie üben, versetzen Sie sich einfach in die Lage des Kunden. Denken Sie aus einer anderen Position. Wenn nötig, versetzen Sie sich auch in eine dritte Position und denken Sie wie ein Beobachter. Erinnern Sie sich daran, wie sich Schauspieler auf ihre Rollen vorbereiten, und zwar meistens in Echtzeitsituationen. Sie bereiten sich darauf vor, echte Probleme zu lösen und Einfühlungsvermögen kann dabei helfen.&nbsp;Wenn Sie ein echtes Talent sind, aber nicht mit anderen zusammenarbeiten können, verpassen Sie viele Chancen auf Erfolg. Zusammenarbeit fördert die Kreativität und bringt innovative Lösungen hervor. Die Freiheit zu experimentieren und die psychologische Sicherheit fördern eine Kultur des Experimentierens und der Iteration. Sie schätzen den Prozess des Ausprobierens, der es den Designern ermöglicht, mehrere Lösungen zu erforschen, Ideen auf der Grundlage von Feedback zu verfeinern und so lange zu iterieren, bis sie die praktikabelste und effektivste Lösung (MVP) gefunden haben. Diese Freiheit zum Experimentieren ermutigt zur Risikobereitschaft, fördert die Kreativität und führt letztendlich zu großartigen Innovationen.&nbsp;&nbsp;Mit einer Denkweise, die auf Einfühlungsvermögen, Zusammenarbeit und die Schaffung eines Umfelds ausgerichtet ist, in dem das Experimentieren gefördert wird, können komplexe Herausforderungen zu sinnvollen Innovationen geführt werden.&nbsp;<img src="https://admin.globalsoft.co/uploads/Mindset_5429e3e925.jpg" alt="Mindset.jpg" srcset="https://admin.globalsoft.co/uploads/thumbnail_Mindset_5429e3e925.jpg 156w,https://admin.globalsoft.co/uploads/small_Mindset_5429e3e925.jpg 500w,https://admin.globalsoft.co/uploads/medium_Mindset_5429e3e925.jpg 750w,https://admin.globalsoft.co/uploads/large_Mindset_5429e3e925.jpg 1000w," sizes="100vw" width="1200" height="1200">&nbsp;<h2>Was passiert, wenn man Design Thinking ignoriert?<img></h2>Es wird nichts passieren, oder Sie entwickeln etwas, das niemand benutzt. Es liegt ganz bei Ihnen.

Sie müssen sich nicht zwischen Scrum und Design Thinking entscheiden, kombinieren Sie sie für eine erfolgreiche Produktentwicklung, lesen Sie, wie.

Kann Design Thinking mit Scrum wirklich bei der Produktentwicklung helfen?    

Imate ideju za razvoj proizvoda, pravite plan razvoja, istražujete proces, razmišljate kojoj kompaniji ukazati povjerenje da vašu ideju pretvori u proizvod kojeg klijenti obožavaju. Ako je odgovor da, idemo skupa istražiti kako Design Thinking i Scrum mogu pomoći u ovom procesu. 

<heading>Kroz 5 faza do inovativnijih rješenja </heading>

Ako ste, dok ste dizajnirali svoj proizvod, razmišljali o krajnjem korisniku, svom kupcu, mogli bi reći kako ste u osnovi aktivirali Design Thinking. Što je zajedničko za Scrum i Design Thinking? Bave se kompleksnim problemima. Kako će se korisnik ponašati, razmišljati ili kako bi mu vaš proizvod mogao promijeniti život, Hasso Plattner, Institut za dizajn na Stanfordu predložio je pet faza Design Thinking modela: empatija, definiranje, ideacija, prototip i test. 

<img>![Designt_thinking_5_faza.jpg](https://admin-v2.globalsoft.ba/uploads/Designt_thinking_5_faza_63f51989dd.jpg)</img>

<heading>Empatija</heading>
U ovoj fazi morate razumjeti svoje korisnike, njihove potrebe i probleme, probleme koji će se riješiti korištenjem vašeg proizvoda. Dobra stvar je ako tvrtka koja će razvijati vaš proizvod koristi Scrum. Jedan artefakt u Scrumu je Product Goal. Kad Scrum tim razvija proizvod, uvijek ima na umu cilj proizvoda. To je i zajedničko za Design Thinking i Scrum, imati na umu krajnjeg korisnika. Kada birate kompaniju koja će razvijati proizvod, a ujedno primjenjuje Scrum, korisno je očekivati i razgovor o krajnjem korisniku, nema ništa gore nego napraviti proizvod koji nitko ne koristi. Greške su u uredu i prihvatljive su u ranoj fazi razvoja gdje imate priliku uraditi inspekciju i prilagodbu. 

<heading>Definiranje</heading>
Uvijek zamišljajte o svom proizvodu kao rješenju za probleme i potrebe krajnjeg korisnika, kupca. Komunicirajte svoj proizvod kao rješenje za klijentove probleme timu koji razvija vaš proizvod. Budite na istoj strani. Scrum će vam pomoći s inkrementalnim i iterativnim razvojem, svaka iteracija pod nazivom Sprint dodaje vrijednost vašem proizvodu, u mogućnosti ste prikupljati povratne informacije kako se proizvod razvija kako biste rano uradili prilagodbu. Kada vas tim koji izrađuje vaš proizvod pozove na događaj Sprint Review, nemojte ga preskočiti. Ovo je vaša prilika da redefinirate, date povratne informacije, da se uskladite sa svojim planom razvoja proizvoda. 

<heading>Ideacija, razmišljanje</heading>
Kada članovi razvojnog tima predlažu ideje, ovdje znajte kako je prisutna psihološka sigurnost. U psihološki sigurnom okruženju članovi tima se osjećaju sigurno razgovarati. Bilo da unaprjeđujete postojeći proizvod, razvijate svoju ideju od početka kao MVP, slavite svaku predloženu ideju. U nekim kompanijama ljudi su nagrađeni za odbačene ideje. Ako ste u situaciji da ideje dolaze jedna za jednom, imate sreće. Dakle, kada birate kompaniju za razvoj proizvoda, pažljivo “slušajte”.

<heading>Prototip</heading>
Vrijeme je da kreirate rješenja za prethodno definirane probleme. Scrum tim stvara Product Backlog. To je prioritetni popis poslova izveden iz plana. Product Backlog stavke s vrha popisa idu u iteraciju, na kraju iteracije pod nazivom Sprint vidjet ćete prvi prototip. Inputi za Product Backlog vrlo su važni. Oni dolaze iz vizije proizvoda, plana proizvoda, kupaca, marketinga, prodaje... Kada komunicirate svoje zahtjeve s timom za razvoj proizvoda, neka budu specifični, mjerljivi, dostižni, relevantni i zasnovani na vremenu.

<heading>Test</heading>
Sada vaši korisnici testiraju vaše rješenje, daju vam povratne informacije kako biste mogli prijeći na sljedeću iteraciju razvoja. Isprobajte svoje rješenje i prikupite povratne informacije od kupaca. Design Thinking i Scrum postavljaju 3 stupa empirizma: Transparentnost, Inspekcija i Prilagodba. Koristite ih sve.

<heading>Design Thinking i temeljna načela, principi</heading>

<img>![Ključni_principi.jpg](https://admin-v2.globalsoft.ba/uploads/Kljucni_principi_e7a29eebde.jpg)</img>

Postoji nekoliko temeljnih principa koja vode proces i koja biste mogli koristiti:
•	Usmjerenost na korisnika – fokus na stvaranje rješenja koja ispunjavaju zahtjeve korisnika koji je u središtu vašeg uma. Vi rješavate njegove probleme.
•	Empatija – Design Thinking poziva na aktivno slušanje, razumijevanje emocija i motivatora klijenata. 
•	Iterativni proces – transparentan proces koji omogućuje inspekciju i prilagodbu, isporučujući vrijednost sa svakom iteracijom.
•	Suradnja - Scrum i Design Thinking od članova tima očekuju suradnju koja dovodi do kreativnijih, učinkovitijih rješenja.
•	Način razmišljanja, mindset – sve što ste mogli pročitati do sada je stvar načina razmišljanja. Ako imate vrijednost od ovog posta, to znači da imate mindset za to.

Ova načela vam omogućavaju da izgradite proizvod koji ima značaj i ima utjecaj na krajnje korisnike.

<heading>Kako Design Thinking utječe na razvoj proizvoda</heading>

Design Thinking ne utječe samo na razvoj proizvoda, kreće već od vizije. Prva vizija je stvorena na umu, tako da možemo reći da je Design Thinking način razmišljanja, kao i Agile, način razmišljanja koji se može primijeniti u svim aspektima poslovanja omogućujući rješenja za složene probleme.

Ispravno razmišljanje, mindset postoji kada principi zažive. Načela Agile i Design Thinking potiču suradnju, potičući članove tima da razmišljaju izvan okvira i eksperimentiraju u potrazi za rješenjima. Odluke je korisno donositi na temelju iskustava. Tražiti i uvažavati povratnu informaciju i na takav način imati zasluženi tržišni udio.

<img>![Mindset.jpg](https://admin-v2.globalsoft.ba/uploads/Mindset_5429e3e925.jpg)</img>

<heading>Kako koristiti Design Thinking</heading>

Kada vježbate empatiju, razmišljate iz cipela korisnika. Razmišljajte iz druge pozicije. Ako treba, stavite se i u treću poziciju i razmišljajte kao promatrač. Prisjetite se kako se glumci pripremaju za svoje uloge, većinu vremena u situacijama iz stvarnog okruženja. Pripremate se za rješavanje stvarnih problema i empatija može pomoći.

Ako ste pravi talent, ali ne možete surađivati s drugima, propuštate puno prilika za uspjeh. Suradnja potiče kreativnost, stvara inovativna rješenja. Sloboda eksperimentiranja i psihološka sigurnost potiču kulturu eksperimentiranja i iterativnog razvoja. Cijenite proces pokušaja i pogrešaka, potičite tim da istražuje višestruka rješenja, poboljšaju ideje na temelju povratnih informacija i ponavljaju sve dok ne dođu do najefikasnijeg i najučinkovitijeg rješenja (MVP). Ova sloboda eksperimentiranja potiče preuzimanje rizika, potiče kreativnost i u konačnici dovodi do velikih inovacija.

Kada imate način razmišljanja s empatijom, suradnjom i stvaranjem okruženja u kojem se potiče eksperimentiranje, kompleksni izazovi mogu dovesti do značajnih inovacija.

<heading>Što ako zanemarite Design Thinking?</heading>

Ništa se neće dogoditi ili biste mogli izgraditi proizvod kojeg klijenti ne koriste. Na vama je.

Kako izraditi proizvod kojeg klijenti koriste? Design Thinking i Scrum mogu pomoći u ovom procesu, u kombinaciji dovode do značajnih inovacija.

Mogu li Design Thinking i Scrum stvarno pomoći za razvoj proizvoda?

Design thinking.jpg

Can Design Thinking with Scrum Really Help with Product Development?  

Combine Design Thinking and Scrum for Product Development

<h2>What is Hexagonal Architecture?</h2>Hexagonal architecture, also known as Ports and Adapters or the Onion architecture, is a software design pattern that has gained popularity due to its ability to improve the maintainability, testability, and adaptability of an application. The layers of the application are represented as a hexagon, with the innermost layer being the core of the application and the outer layers representing various external interfaces.&nbsp;<h2>Components of the Hexagonal Architecture</h2><h3>Domain Model</h3>At the centre of the architecture is the Domain Model, which represents the application’s core business logic and entities. It is responsible for implementing the main functionality and rules that the application is built around. One of the critical principles of hexagonal architecture is that the core of the application should not depend on any specific external interface.&nbsp;<h3>Ports</h3>Ports are the interfaces that define the communication points between the application’s core logic and the external world. They can be categorized as:<ul><li>Primary or Driving Ports - define the operations that the application exposes to external actors. They represent the use cases or application services that external systems or users initiate.</li><li>Secondary or Driven Ports - define the operations that the application needs from external services or components. They represent the dependencies or resources required for the application to function.</li></ul>&nbsp;<h2>Adapters</h2>Adapters are the components that translate the interactions between the external world and the core business logic by implementing the ports. There are two types:<ul><li>Primary or Driving Adapters - convert external inputs into a format that the core logic can understand.</li><li>Secondary or Driven Adapters - implement secondary ports by providing the required functionality to interact with external services or resources. &nbsp;</li></ul>

Hexagonal architecture, also known as Ports and Adapters or the Onion architecture, is a software design pattern that has gained popularity due to its ability to improve the maintainability, testability, and adaptability of an application.

hex.jpg

Understanding Hexagonal Architecture: Ports, Adapters, and Domain Model

<h2>Web Development</h2>GoLang has gained significant popularity in web development due to its ability to handle high levels of concurrency and its quick startup times. Frameworks like Gin and Echo provide tools for building efficient web APIs and services.&nbsp;<h2>Distributed Systems</h2>GoLang's built-in support for concurrency and networking makes it a solid choice &nbsp; for &nbsp; building &nbsp; scalable &nbsp; and &nbsp; efficient &nbsp; distributed &nbsp; systems, microservices, and cloud-native applications.&nbsp;<h2>Networking and Backend&nbsp;</h2>GoLang's &nbsp; native &nbsp; networking &nbsp; libraries &nbsp; and &nbsp; performance &nbsp; characteristics make it ideal for crafting network-heavy applications such as proxies, servers, and networking tools.&nbsp;<h2>System Programming</h2>Go's low-level features, coupled with its garbage collection and memory safety, &nbsp;make &nbsp; it &nbsp; suitable &nbsp; for &nbsp; system-level &nbsp; programming, &nbsp; providing &nbsp; an alternative to languages like C or C++.

blog golang.jpg

Where GoLang fits the best?

Global Soft developers seek to broaden their knowledge and soak it up from other developers which, on the other hand, are eager to share things they know more about. That is the concept our internal workshops are based on. 

In Decemeber, a Docker workshop was held by one of our DevOps Engineers. All developers, backend and frontend, from the company, took part in one-day workshop. 

The aim of the workshop was to up the level of knowledge and usage of Docker, being a tool present in everyday life of a developer. Extending their knowledge from users perspective, developers can use it to some extent in their daily tasks.



In Decemeber, a Docker workshop was held by one of our DevOps Engineers.

Die Entwickler von Global Soft streben immer danach, ihr Wissen zu erweitern und von anderen Entwicklern zu lernen, die wiederum bereit sind, ihr Wissen weiterzugeben. Das ist das Konzept, auf dem unsere internen Workshops basieren.

 

Im Dezember wurde ein Docker-Workshop von einem unserer DevOps-Ingenieure abgehalten. Alle Backend- und Frontend-Entwickler des Unternehmens nahmen an dem eintägigen Workshop teil.

 

Ziel des Workshops war es, die Kenntnisse und die Nutzung von Docker zu verbessern, da es sich um ein Tool handelt, das im Alltag eines Entwicklers präsent ist. Indem sie ihr Wissen aus der Sicht der Benutzer vertiefen, können die Entwickler es bis zu einem gewissen Grad bei ihren täglichen Aufgaben einsetzen.

Im Dezember wurde ein Docker-Workshop von einem unserer DevOps-Ingenieure abgehalten.

Interner Docker-Workshop

Developeri Global Soft-a traže načine da prošire svoje znanje i upiju ga od drugih developera, koji, su, s druge strane, voljni podijeliti stvari o kojima znaju više. To je koncept na kojem su bazirane naše interne radionice.

U prosincu je održana jednodnevna Docker radionica, koju je održao jedan od naših DevOps inženjera. Svi developeri iz Global Soft-a, backend i frontend, sudjelovali su u ovoj jednodnevnoj radionici.

Cilj radionice bio je povećati razinu znanja i korištenja Docker-a, budući da je to alat prisutan u svakodnevnom životu jednog developera. Proširenjem znanja o njemu iz perspektive korisnika, developeri ga mogu do određene razine koristiti u dnevnim zadacima.

U prosincu je održana jednodnevna Docker radionica, koju je održao jedan od naših DevOps inženjera. 

Category: Engineering