By
El Copeland
October 28, 2024
•
20 min read
Fundamental Skills

The article you've stumbled across is the first in a collection of five blog posts meant to be an extension of The Care and Feeding of Meat Computers series which I’m releasing on the Rising Tide YouTube channel, born from a talk I shared at MSPGeekCon 2023. These companion guides are intended to help provide links to resources, research, and books that informed parts of this collection. The goal is to give you enough information and connections so you can dig into these concepts, including things that I cut from the talks for time or other organizational, boring reasons. I am also going to include some questions at the end of each guide to help you facilitate conversation with your team or to further deepen it!
Before we go much further, it's important to me to also extend my gratitude to the people who helped me make sure this talk happened in the first place. Heather and Brian at Gozynta encouraged me as I wrote and honed this concept the first time and generously sponsored me to attend MSPGeekCon and give this talk. Matt Fox, for the reliable perspective, fresh jokes, and tots. Alicia Gregory for academic and psychological insight, a cache of useful journal articles, and listening to me cry basically bi-weekly for nearly a decade.
Of course, last but not least, my business partner, Mendy Green, for believing in me and that this concept needed to see the light of day at all instead of just our five-minute-long WhatsApp voice notes.
If you’re here, there’s a good chance you’re involved in technology, whether you follow Rising Tide, are a part of the MSPGeek community, or otherwise found this series while searching the depths of the internet. Regardless of who you are or where you’re from, come on in, make a cup of something warm, and have a seat. I hope that you will find each word expressing my sincere love to the tech community, specifically to those often-unsung heroes, the nerds whose daily, Sisyphean job is to balance the science behind tech with the increasingly important art of human understanding.
This series is for those of you who may feel (or those of you who manage and collaborate with those who feel) more at home with your hard skills compared to soft skills. It’s completely understandable: in our society, and especially in tech, we tend to believe hard skills are the “real” skills, while soft skills are secondary or nice-to-have. But don’t let your imposter syndrome about the places you feel weak dictate what is real or true! Just because something can easily be expressed through certifications doesn’t mean they are more valuable or will help you live a more fulfilling life. In fact, you may have even been called “gifted” when it comes to technology, and as such, choose to feed that part of you, first. If we consider some of the theories about giftedness, specifically Renzulli’s three-ring conception of it, giftedness for any skill comes from ability, creativity, and commitment.

My goal with this series is to challenge the view that hard skills are respected and most prized; and to encourage us to reframe “soft skills” not as something separate or less-than, but as essential, accessible, and attainable, intertwined with our technical expertise. We may not come by it naturally, as in an above-average-ability, but with creativity and commitment, we can develop these skills as well!
I specifically want us to look at soft skills in a way that outright refuses the notion that as you are, you are bad, undesirable, or unacceptable. While there are certain social standards that you may have been trained to adhere to, I want you to put those rules aside for these conversations. If you’ve ever felt like you’re expected to fit a mold to be successful—whether to be more charismatic, more structured, or even more proper—this series is for you.
I’ve held a ton of jobs in a wide variety of industries and tiers of responsibilities. Despite my breadth and depth of experience and knowledge, I’m not interested in being revered as an expert. Experts tell you what you’re supposed to do and exactly how you’re supposed to do it to guarantee success. I’m sure my disdain for this snake-oily social power dynamic shows consistently in things I say and my approach in this series. Why the sass regarding experts? I want you to know and truly embrace the fact that your value as a tech professional goes beyond fitting into the boxes people want to put you in. Your value as a tech professional goes beyond fitting into the boxes you want to put yourself in! I’m not an expert, experts want you to be like them. I want you to be like you.
You have these skills: you have social skills, you have people skills, you have soft skills. Regardless of if they fit into what some expert tells you is “correct,” if you’re a little bit weird, I want you to embrace it.
You’re here because you’re passionate about technical solutions, and you’re here because you’re looking for ways to develop further yourself and your community. I propose to you that your passion for technology is actually a powerful tool, if not the most powerful tool, in developing your soft skills. You can use your technical intelligence to boost your Emotional Intelligence.
It’s time to stop kidding ourselves that hard skills are technical and measurable while that soft skills are just a “personality trait” exemplified by gentle people like women and mothers. This belief implies two terrible, not-true things:
This is a disservice to you and those who you work with. You have soft skills, and developing and enhancing them is vital to your personal and professional growth. Here’s the thing: soft skills are hard. But that doesn’t mean they aren’t worth shaping or that they’re out of your reach as a technical, linear-minded person. Soft skills are hard-won through life experiences, loss, pain, and PRACTICE.
These concepts fold neatly into coding ideologies like Human-Centered Design and Human-Computer Interaction. You are technical, you are practical. Humans are hard. Let’s reframe this to help ourselves be more successful. I propose that soft skills aren’t the opposite of hard skills, but an evolution of them, and if you find them hard, perhaps you just need to look at humans as what they are: complex meat computers that really just want to do what they can to survive and thrive in the world they’ve inherited, just like you.
So together, let’s flip the script and let’s start with reframing a questions we often ask, to see how we can better harness our natural penchant for hard skills and alchemize them into above average soft skills.
Join me as we elevate the question, “Why aren’t people more like computers?” to “Why might people be too much like computers?” Instead of following a set of rules, I want you to ask yourself, “what if I treat people with just as much care and curiosity as I treat computers? What would my life, my job, and my relationships look like, instead?”
To deepen the concepts discussed in this series, here are several resources for further exploration:
Questions for Team Reflection
If you’re watching this series with a team, here are some questions to guide your discussion and help you make the most of these ideas:
That’s it for Episode 1! Tune in for our next Episode: The most expensive piece of technology you’ll ever see.

Episode 17 warps up the breakdown of version 2.21 and begins 2.212, highlighting impactful updates across billing, SLA visibility, and ticket management. The team dives into major improvements like dynamic ticket filters, default billing templates, and better billing tab access controls. This episode is especially useful for MSPs looking to tighten billing accuracy, improve reporting visibility, and streamline ticket workflows.
Watch Now: By the [run]Book: Episode 17
For easier tracking, check out haloreleases.remmy.dev to filter and search HaloPSA updates by ID, version, and keyword.
The Billing tab is now visible to agents without requiring full billing permissions, with actions locked based on access.
Tickets on hold can now be included in SLA breached filters.
You can now define a default billing template applied automatically when creating a new customer.
Dynamic filters can now be used on ticket lists for more flexible querying.
This helps keep recurring invoices aligned when item third-party IDs change.
Recurring invoices now get the same due date option already available at customer setup.
This adds more control to portal-based approval workflows.
This extends alternate invoicing behavior down to the site level.
This helps prevent tickets from disappearing into inactive-agent limbo.
More ticket list criteria means more practical operational views.
This update improves the ManageEngine Endpoint Central integration.
Halo now supports generic OpenID Connect SSO.
You can now duplicate item bundles instead of rebuilding them manually.
This adds more naming flexibility to the UI.
This makes SLA breach reporting more honest and more useful.
A major improvement for standard billing configuration.
This adds more flexibility to meter-driven recurring billing.
Dynamic ticket filters add a much stronger filtering experience.
Cloning custom fields speeds up admin work.
This update improves chart label readability.
This update refines the encryption update workflow.
This improves call handling context.
This gives more control over quantity precision.
This improves flexibility when linking work records from sales orders.
This adds better billing visibility without fully exposing billing controls.
Spreadsheet imports can now target existing tickets by ID.
A small UI cleanup on the ticket details pane.
This adds flexibility for co-managed support models.
This improves control over CSP user mapping behavior.
This adds clarification around tax rate usage in Xero-linked setups.
This makes Avalara tenant cleanup easier from the client billing tab.
This is a strong automation improvement.
Custom table row deletion gets more precise.
This cleans up recurring invoice visibility.
This is a documentation/config clarity improvement.
Ticket rule assignment now supports more role-based options.
Approval rule logic gets another useful condition.
Supplier-related configuration gets more flexible.
Project templates now get more dynamic input from sales-order-driven creation.
This expands visibility in quote and sales order line views.
This makes customer/site control more precise.
The API docs continue to improve.
This improves ticket logging layout flexibility in the agent app.
This is an important reliability improvement for payment processing.
This adds more flexibility when services are generated from assets.
This improves parent/child ticket data behavior.
Third-party ID linking is now available across more entities.
Query Builder gets another field for reporting logic.
This expands visibility of account/prospect records in top-level views.
Custom buttons now get access control.
This adds polish to the opportunity creation experience.
This is one of the biggest integration-facing updates in the episode.

In Episode 16 of By the [run]Book, Mendy and Robbie continue reviewing HaloPSA v2.210, covering a wide range of updates across billing, workflows, integrations, AI, and asset management. The episode highlights several settings MSPs should review immediately—especially a billing change that can lock recalculation—as well as improvements to ticket automation, AI categorization, and service desk efficiency.
Watch Now: By the [run]Book: Episode 16
For easier tracking, check out haloreleases.remmy.dev to filter and search HaloPSA updates by ID, version, and keyword.
Editing billing time allocation will lock billing recalculation | v2.21 #1044274
A setting has been added to Billing configuration so that editing the billing time allocation on an action will lock the ticket from billing recalculation.
Credit notes can default to today’s date | v2.21 #1042924
A setting has been added to Credit Note configuration so that the Credit Date is set to today's date instead of the Invoice Date.
Auto-assign the next unassigned ticket when closing a ticket | v2.21 #1003964
Added a new setting that automatically assigns an Agent the next available Unassigned Ticket when they close a Ticket.
Parent tickets can inherit dates from child tickets | v2.21 #975755
Added a new Ticket Type setting: "Automatically set Start Date and Target Date based on Child Tickets".
This setting adds a new option for grouping ticket entities during invoice creation in the Ready for Invoicing area.
This setting locks a ticket from billing recalculation when billing time allocation is edited on an action.
A new variable has been added for adjusted opportunity value.
Workflow steps now require an outcome to be selected.
Invoices can now default to the customer’s main site address.
Credit notes can now default to today’s date instead of the original invoice date.
Halo can now remove FW: and RE: prefixes when creating tickets from email subjects.
AI generated summaries can now be displayed in ticket column profiles.
A new advanced setting enables configuration change tracking for Services.
A global setting can now display the asset DID as a read-only field.
Custom integrations can now use separate credentials per instance.
The Main Site Address field can now be used in client and site column profiles.
The instances area has been updated with a new loading method to improve performance.
Tickets generated from Contract Schedules can now be created a specified number of days before the appointment date.
Additional ownership-related fields are now available in asset column profiles.
Asset dependency diagrams can now display customizable fields.
The client API endpoint can now return website data when requested.
The Twilio WhatsApp integration has received multiple improvements.
Assignment rules can now be disabled during Salesforce sync.
Runbooks triggered via webhook can now use a secret URI parameter for authentication.
HubSpot quote imports now include a default user field.
Agents can automatically receive the next unassigned ticket when they close one.
Chat Bot input steps can now access browser local storage.
Additional configuration options are now available for asset system fields.
Asset custom buttons now support dynamic visibility.
Asset fields can now perform SQL lookups.
Stock bins can now be selected for non-serialized assets.
Date custom fields now support validation rules relative to the current date.
Workflow Stage can now be used in the report query builder.
The New Relic integration has received improvements.
The phone number requirement for anonymous portal tickets can now be configured per ticket type.
Parent tickets can automatically derive start and target dates from their child tickets.
AI can now suggest ticket categories from a configurable list.
A new setting expands how Agent Site Restrictions apply to users and organizations.
Halo now allows configuration of how appointment unique IDs are generated.

Episode 15 of By the [run]Book covers Halo v2.208 and starts into v2.210, with Mendy and Robbie walking through SLA refinements, shifts/time tracking updates, billing cadence improvements, and tighter access controls across portals and reporting. Key moments include new SLA response targeting options, a clock-in/clock-out widget for shifts, a bi-monthly schedule period, and expanded team leader controls. This is a useful episode for MSPs looking to tighten operational workflow, reporting governance, and self-service experience improvements.
Watch Now: By the [run]Book: Episode 15
For easier tracking, check out haloreleases.remmy.dev to filter and search HaloPSA updates by ID, version, and keyword.
Adds an SLA option so your first response target can differ from subsequent response targets.
Adds the FAQ List Ticket field as a workflow criteria option.
Allows ticket end-user updates when an anonymous chat is successfully upgraded.
Adds a clock in/clock out widget for Shifts.
Adds a 2-month schedule period option.
Improves Knowledge Base latest article links.
Adds “Visible - Read Only” for Agent Asset details visibility.
Adds load-balance on reopen if assigned agent doesn’t meet qualification rules.
Introduces a module for an Opinyin integration.
Adds test email sending for individual mail campaign messages.
Adds new Halo API actions in runbooks.
Splits KB view counts so end users see only user views (when enabled).
Adds item group restrictions + running cost total on portal ticket item selection.
Adds a Ticket Reference field that’s searchable and usable in column profiles.
Groups service subscribers.
Adds $ variables for CONTRACTSLA, CONTRACTSUBTYPE, CONTRACTSTATUS.
Adds improvements to Agent Resource Booking.
Adds encryption options for variables/responses in integrations/runbooks.
Adds software expiry date tracking on assets.
Adds ticket-type control for end-user approval action visibility.
Allows team leaders to modify agents’ preferences.
Adds bulk add assets via the asset search modal.
Adds chat profile overrides at the user role level.
Allows KB links to include FAQ lists and auto-expand on open.
Allows HTML formatting in popup notes triggered by ticket rules.
Shows credit notes alongside invoices in the portal.
Adds a setting to limit users/agents to one active session.
Adds TD Synnex Quote Line Imports.
Adds dark mode counter widget color options.
Adds downpayment invoice creation from sales orders (fixed price + T&M).
Adds settings to limit portal options to Web Access Level list values.
Adds access control for reports.
Adds a deep link button on imported Addigy devices.
Multiple changes made to the Expenses list.
Allows embedding Halo portal/agent UI (including dashboards) in SharePoint via iframe.
Changes how recurring invoices appear/create based on month selection.
Ensures billing template application creates a billing plan record per matching contract/agreement.
Adds Last Contacted + Created Date fields to NinjaOne device import.
Removes quote “Send” button so sending happens only via ticket/opportunity.
Disables change history tracking for selected asset fields.
Adds invoice access restriction levels (No Access/Site/Client).
Shows the overriding contract field even if it isn’t on the field list (admin-editable only).
Enables database lookup while entering an action in the self-service portal.
Updates the Account Integrator for Sage UK v32 (2026).
Adds a setting to group ticket entities separately during invoice creation.