Linux Bible, 10th Edition is the ultimate hands-on Linux user guide, whether you're a true beginner or a more advanced user navigating recent changes. this updated tenth edition covers the latest versions of Red Hat Enterprise Linux (RHEL 8), Fedora 30, and Ubuntu 18.04 LTS. It includes information on cloud computing, with new guidance on containerization, Ansible automation, and Kubernetes and OpenShift. SEE ALSO: Get 'Teach Yourself VISUALLY Windows 11' (worth $19.00) for FREE With a focus on RHEL 8, this new edition teaches techniques for managing storage, users, and security, while emphasizing simplified administrative techniques with Cockpit. Written by a… [Continue Reading]

Discover how to use YouTube as a free and unlimited file storage platform with one easy script that will allow you to use your YouTube account as a cloud storage service, allowing you to upload and access files of any type and size without any limitations.

Cities: Skylines 2 is on the way but Paradox and Colossal Order aren't done just yet with Cities: Skylines. Multiple new content additions were just announced.

nvitop is an interactive NVIDIA GPU process viewer and more besides. It's free and open source software written in Python. The post Excellent Utilities: nvitop – GPU process management appeared first on LinuxLinks.

It can be a bit different when installing and removing packages in NixOS. Here, we explain it to make things easy. The post NixOS Series 3: Install and Remove Packages in NixOS appeared first on Linux Today.

Half-Life: MMod just released on Steam, a mod for the original Half-Life that overhauls many parts of it to create something that feels fresh.

PostgreSQL is an open-source database management system focusing on extensibility and SQL compliance. This tutorial will install the PostgreSQL database server on Ubuntu 22.04 servers and set up Multi-Master replication with multiple servers via Bucardo, an asynchronous PostgreSQL replication system.

How being open at work results in happy customers katgaines Fri, 03/17/2023 - 03:03 Every interaction we have with another person is influenced by our emotions. Those emotions have ripple effects, especially when it comes to how you do business. A happy customer patronizes your business more, recommends it to family and friends, writes a positive review, and ultimately leads to more money being spent at your business than if they'd been disappointed. The most basic known variable of providing good customer service influences this: If something isn't going as expected, work to make it right (within reason), and you'll save the relationship. In tech, you can respect this in a few ways. If you listen to customer feedback, create products they'll find useful and intuitive, and nurture those positive associations with your project, then you'll do well. But there's an oft overlooked component to your customer's emotional perception of your business, and that's the customer support team. Customer support team The interactions handled by a support team carry a high emotional charge for the customer. Software needs to work, and it needs to work now. Software faces a unique challenge when it comes to how a customer-facing team builds a relationship: it's primarily a virtual interaction. For in-person customer care, an employee wields the superpower of eye contact, a strong emotional influence. Facial expressions force us to interact with more empathy than say, a voice over the phone, or an email response. When that's not possible, though, the ability to shift the emotional tone to a calm one can be challenging. It's easy for a customer to have a natural bias toward online support. Maybe they've had a bad experience with heavily automated support in the past. There are plenty of badly configured chatbots, unnavigable phone menus, and dispassionate robotic voices to add fuel to the fire when emotions are already high. A customer may have talked to a support agent who's miserable at work and therefore apathetic to the outcome. The customer carries these experiences into their emotional approach when asking for help. This can create stress for the agent who picks up their ticket, and a vicious cycle repeats. Because of high stakes, emotional nature of Customer Support (CS), your business has an opportunity. Corral these big emotions through the people who have the most access to them. The key to doing this successfully is to remember the ripple effect. A customer service agent with the necessary tools and knowledge at their fingertips is happy. A happy customer service agent has better conversations with customers. You can set yourself apart from competitors by creating happy customer support agents in an empowered and knowledgeable customer service team. How is this done? Preparing for success If you’re a leader in customer support, or a stakeholder elsewhere in the organization (engineering, product, and so on) who works with support a lot, you can work in key areas to make the lives of your support agents a little easier: Create visibility As a customer support agent, you need data about the customer you're helping. You need to know the systems your customer is using, and the products you're meant to support. It's crucial to have visibility into other teams in the organization, because they have that kind of data. You need to know who to ask for help when a problem arises, what the known issues are, what's being worked on already, and so on. Siloed departments are a common major barrier to achieving visibility across teams. This can be made worse by tools and systems that don't connect departments, such as a spreadsheet directory or filing issues in an internal tracking tool. When this is the case, the customer service department can't get timely information on the status of an issue, and the engineering department can't get a good feel for how customers are experiencing the issue. If your customer service team is given visibility into the complexity faced by your engineering teams, it's easier to clearly articulate the state of issues to customers and stakeholders. Customer service teams can create visibility for engineering, too. Crucial information about problems can come from your customers. When engineering has visibility into customer issues, they're better equipped to prioritize for customer needs. Everyone works hard to prevent customers from being affected by issues, but that's not always realistic. Use the data your customers give your customer service team about what's wrong, and empower your customer service agents to become part of an incident response process rather than just reacting to it. Make difficult moments easy Customer support is a difficult job. If you have never worked in customer service, I'm giving you some homework: shadow your customer support team so you can understand where friction happens. It's a great way to get to know who your customers really are, by seeing them in their highest emotional moments, and seeing how your team navigates that. Customer service means all the questions coming your way, few of the answers at your fingertips, manual tasks to complete, and not enough people to share the load. Make the job easy for customer service where you can. It will pay off. Maybe you can help the team automate mundane tasks to better focus on more interesting problems. Often this manifests in chatbots, but it's worth being creative here. For example, can automation be applied when escalating tickets to engineering? That could free an agent to work on their troubleshooting process, rather than the manual steps of making that escalation happen. You can use tooling your engineering team might already have in place to find these opportunities. Operations platforms can be shared to put both team's metrics out in the open, helping everyone stay aligned on common goals. The feedback loop required for a mature software development life cycle needs the customer service team to operate effectively. You can only do that with shared visibility across your organization. Making it easy also means proactive design, especially when it comes to processes for critical moments. You probably have a process to manage major incidents. When you share these tools and processes with customer service, you enable greater visibility and gain valuable insight and teammates along the way. During an incident, customer service can play a few key roles: Aggregating customer reported issues When an incident triggers, engineering needs to quickly find out how much of the service is impacted, including how many features, the depth to which they are affected, and whether they are slow or completely offline. Customer impact is part of that, which customer service can help uncover by associating inbound customer complaints to technical incidents to help drive priorities. As customer service receives reports of issues during an incident, that data becomes part of the impact of the incident, and is incorporated into the resolution process. Prioritization of SLA Your customer service team is in a unique position to help confirm the impact of an incident on the end user. They have insight into when services are reaching their Service Level Agreement (SLA) for certain customers, and can alert the responding team. This is an important piece of information to manage, and engineering teams might not have visibility into those contractual agreements. This aids in the prioritization of issues during incidents. CS can advise on whether or not an incident should be escalated or have its severity increased based on the customer intelligence they are receiving. More customer impact could mean a higher severity level for the incident, more responders included in the triage, and more stakeholders informed. Liaisons and stakeholder communication Speaking of stakeholders, customer service can take the lead when it comes to codifying communication practices for incidents. Customer service can take ownership of policies around messaging for customers, template responses, and communication processes. Templates with clear information and status pages to keep up to date are just some of the assets they can manage. Post-incident follow-up You'll always encounter customers who watch your status page like a hawk for updates. These customers and others ask customer service for updates if they don't see progress. You can ease the cognitive load of responding to these customers with the newfound connection with the incident process. If you hold incident reviews, then customer service must be part of that conversation. The tone of a conversation changes when a customer service agent has extra data to present to users about the impact of the incident, the resolution, and long-term plans for prevention. Your customer feels consistency, and your agent feels real ownership of the conversation. At the end of the day, involving your customer service team through the entire process, from start to finish, allows them to gain control of their own destiny. It lets them provide valuable input back into the resolution process, and leverage their improved experience to improve the customer experience. Automation with open source Download now: The automated enterprise eBook Free online course: Ansible essentials Ansible cheat sheet eBook: A practical guide to home automation using open source tools A quickstart guide to Ansible eBook: 7 examples of automation on the edge More articles about open source automation Invest in people You can't create a happy employee out of thin air. Customer service leaders need help doing this. People need investment in career growth, the ability to collaborate with their peers, and a voice in the organization to know that their feedback is heard. Your customer support team is not here to report on metrics to the business or to slog through the queue. Investing means giving them time and space to expand their skills and grow in their careers. For customer service leaders, this comes with knowing you may not keep them in support forever. You can build a strong team that offers phenomenal support, and also creates a hiring funnel into the rest of the business. The first level of this is up-leveling agents within support. It's common to have a "premium" support team, or similar, for customers who need a high touch level of support, and the ability to get help at any hour. Hiring 24x7 staff won't help a customer service leader redesign their team's status as a cost center, but developing a staffing model to use the existing team's time efficiently can. Sharing tooling with engineering can be one way to get there. For example, if engineering is on call for responding to issues, customer service can use the same tooling to provide a creative solution, rotating a specialized team for those odd hours or high priority issues. This can open up a new career path for those who want to be on a team with specialized knowledge. Having a team that can be notified as-needed, rather than fully staffed at all times, staring at a queue, and waiting for incoming requests, allows leaders to scale their customer experience efficiently. Empowering customer service teams to reach out to other teams and advocate for customers also creates new communications channels and opportunities. Your customer service team can serve as a gateway into your organization for technical personnel who are still building skills. A close relationship with engineering supports career growth. Shared processes promote this. So does a shadowing program, having a subject matter expert in support departments for different product areas, and intentionally building career paths to assist transitions when it's time to do so. Customer service agents who transition to other departments bring with them their customer focus and dedication to the customer experience. This is a valuable addition to teams in your organization which increases empathy across the board. The modern software development life cycle doesn't end when code is checked into a repository and all the tests turn green. A constant feedback loop from users back into development planning links user requirements directly to the product management phase of the cycle. Organizations across various industries have seen the benefits of adopting shared goals and purposes across different teams. Include your customer service team in larger organization-wide initiatives, like DevOps transformations and automation projects. Doing this increases the effectiveness of customer-focused teams, and improving their day-to-day work in turn improves the experience they can provide for customers. In a nutshell: Happy agents translate to happy customers. The way the teams within your organization interact affects customer experience. Open communication and shared knowledge can transform your business. Image by: Opensource.com SCaLE Careers Business What to read next This work is licensed under a Creative Commons Attribution-Share Alike 4.0 International License. Register or Login to post a comment.

Cloud repatriation is undoubtedly one of the hottest trends in the cloud infrastructure space as of 2023. It enables organisations to regain control of their cloud spend, workloads and data. According to a report on cloud repatriation by 451 Research group, 48% of IT decision makers confirmed that they had moved their applications away from […]

My first pull request at age 14 neilnaveen Fri, 03/17/2023 - 03:00 My name is Neil Naveen, and I'm a 14-year-old middle schooler who's been coding for seven years. I have also been coding in Golang for two years. Coding isn't my only passion, though. I've been practicing Jiu-Jitsu for four years and have competed in multiple competitions. I'm passionate about coding and Jiu-Jitsu, as they teach me important life lessons. Codecombat I started coding on Codecombat, which taught me many fundamental coding skills. One of the most exciting moments in my coding journey was when I ranked 16th out of around 50,000 players in a multiplayer arena hosted by Code Combat. I was just 11 years old then, and it was an incredible achievement for me. It gave me the confidence to continue exploring and learning new things. Leetcode After Codecombat, I moved on to leetcode.com. This site helped me hone my algorithm coding skills with tailored problems to learn specific algorithms. Coding Game When I turned 13, I moved on to bot programming on Coding Game. The competition was much more intense, so I had to use better algorithms. For example, when creating ultimate tic-tac-toe AI, I used algorithms like Minimax and Monte Carlo Tree Search to make my code fast and efficient. Our favorite resources about open source Git cheat sheet Advanced Linux commands cheat sheet Open source alternatives Free online course: RHEL technical overview Check out more cheat sheets GitHub CLI One day, I saw my dad using an open source tool called GitHub CLI, and I was fascinated by it. GitHub CLI is a tool that allows users to interact with the GitHub API directly from the command line without ever having to go to GitHub itself. Another day, my dad was reviewing PRs from a bot designed to detect vulnerabilities in dependencies. Later, I thought about GitHub CLI and this bot, and wondered whether GitHub CLI itself was being monitored by a security bot. It turned out that it was not. So I created a fix and included a security audit for GitHub CLI. To my delight, my contribution was accepted. It was merged into the project, which was a thrilling moment for me. It was an excellent opportunity to contribute to a significant project like a popular tool like GitHub CLI, and to help secure it. Here's the link to my PR: https://github.com/cli/cli/pull/4473 Commit your code I hope my story will inspire other young people to explore and contribute to the open source world. Age isn't a barrier to entry. Everyone should explore and contribute. If you want to check out my website, head over to neilnaveen.dev. You can also check out my Leetcode profile. And if you're interested, check out my talk at CloudNativeSecurityCon recording. I'm grateful for the opportunities I've had so far, and I'm excited to see what the future holds for me. Thank you for reading my story! Age is not a barrier for contributing to open source. Image by: Opensource.com Careers Programming What to read next 7 steps to securing your Linux server This work is licensed under a Creative Commons Attribution-Share Alike 4.0 International License. Register or Login to post a comment.

Secure Backend Server for Web, Mobile & Flutter Developers

A seemingly unintentional factual error in a get-out-the-vote email sent by Open Source Initiative to its members could result in some members waiting until after the polls close to vote in the organizations current board of directors election. The post OSI Email Mistake Could Affect Election Results appeared first on FOSS Force.

Learn how to redirect non-WWW or WWW in Nginx on Linux.

Cloudflare is a web performance and security company that provides a wide range of services, including content delivery network (CDN), DDoS mitigation, and DNS management. It has a global network of servers that help improve website performance by caching content closer to users and reducing latency. Cloudflare also offers security

Transmission 4.0.2 open-source and free BitTorrent client has been released today as the second maintenance update to the latest Transmission 4.0 release launched in early February 2023 to address more issues.

This tutorial explains the concept of variables in Python, their types, and how to use them with examples in real-world projects. In Python, a variable is a reserved memory location that stores a value. They are names that can be assigned a value and used to reference it throughout your code. Using a variable makes... The post Variables in Python: Concepts with Examples appeared first on DebugPoint.com. Do not reproduce this post without permission.

We haven’t always spoken in glowing terms about Bungie, the game studio behind the Destiny franchise. That being said, in more recent days, Bungie has also taken some very positive steps when it comes to protecting its fans from copyright takedown abuse, while also highlighting for the record that the DMCA takedown process employed by […]

Tremor is a free, open-source library that aids developers in building data-rich dashboards. With Tremor, you can create simple and modular components to build insightful dashboards with ease. The library is fully open-source and was made by data scientists and software engineers with a sweet spot for design. You can

The XIAO ESP3S3 is a thumb size module enabled with 2.4GHz Wi-Fi and BLE 5.0 connectivity. The new SeeedStudio board includes lithium battery charging support and it provides up to 11x GPIOs. Unlike the XIAO ESP32C3 (32-bit RISC-V based) launched last year, the XIAO ESP32S3 integrates a 32-bit Xtensa LX7 processor. ESP32-S3R8 — Dual-core Xtensa […]

Build your React-based CRUD applications, without constraints.