Joseph Harisson and the Trouble With Choosing

Joseph Harisson has an opinion about buying laptops. Costco, he says, often has competitive prices. He also buys household supplies there in bulk to save money and time. For someone whose working life involves cloud computing, cybersecurity and the selection of technology partners, this is a pleasingly unceremonious approach to procurement. Sometimes the supplier assessment ends with a shopping trolley.

The detail belongs in his story because so much of his work concerns the same ordinary problem: how people decide what to buy, whom to trust and what to learn. Harisson is the founder of IT Companies Network, a directory connecting businesses with technology service providers. He is also a technical writer and a contributor to discussions about security, software and hiring. Across those activities, he keeps returning to decisions that sound simple until somebody has to make them.

A company needs outside IT help. A candidate needs to pass a coding assessment. A manager wants employees to use their own data. Each situation comes with tools. Each also comes with people, who have an inconvenient habit of requiring more attention than the product brochure suggests.

Before the directory, an explanation

In January 2019, Harisson published an introduction to Ruby on Rails. Its opening concern was a basic distinction: Ruby is a programming language; Rails is a framework. A reader could reasonably have encountered both names without understanding how they fit together. His article took the terms apart before discussing their uses.

That same year, he wrote about programmatic advertising. Here the subject was the automation of buying advertising space, with software taking on decisions once handled through human negotiation. The distance between web frameworks and media buying is considerable. Both pieces, however, required a writer to make an unfamiliar system legible to somebody trying to use it.

His author biography described experience in web development and cloud computing. It also gave the reader two less technical details: he enjoyed walks and video games. The programmer who writes explanations and then goes outside is a useful corrective to the industry’s more theatrical portraits of itself. A career in technology can accommodate both an interest in systems and a perfectly ordinary afternoon.

A competitor might have something useful

By November 2020, Harisson was writing about competitive collaboration. The premise was that another business pursuing the same customers might also be a useful partner. Rivalry could create opportunities for shared work, access to audiences and learning, provided both sides chose the arrangement carefully.

His argument included an essential qualification: cooperation still required limits. Partners needed to think about what information they shared and how they managed the relationship. The friendly handshake did not abolish the need for judgment. It merely gave judgment another appointment in the diary.

This is an interesting subject for a founder associated with a network of IT businesses. A directory puts competing providers into a common setting. Their differences matter to buyers, while their shared participation makes the directory useful. Collaboration and competition can occupy the same page without either disappearing.

Read alongside his later work, the essay offers a way to understand his interest in connections. He was writing about the value of relationships between businesses in the same year that IT Companies Network was founded. The dates establish the overlap; the argument makes the overlap worth noticing.

The purchase before the project

IT Companies Network gives that concern a concrete business setting. Its stated purpose is to help companies discover, compare and contact IT service providers. The service categories include managed IT, cybersecurity, software development and cloud infrastructure. Company profiles and reviews give prospective buyers material to examine before they start a conversation.

Harisson’s part in that business is publicly described through several titles: founder, co-founder and CEO. The common thread is his association with the platform’s creation and leadership. His professional profile places him in Dallas, and lists the University of Liverpool among his educational affiliations.

The directory addresses a stage of technology work that rarely enjoys the glamour of a launch: choosing the people who will do it. Buyers must connect their needs to a provider’s capabilities. Providers must explain their services in terms a prospective client can recognize. A directory earns its usefulness in that space between a business problem and a plausible next conversation.

The coding test has other people in it

Harisson’s comments on HackerRank bring the same question of fit to hiring. Coding assessments can help employers evaluate technical ability in a consistent way. They also give applicants a place to practise and discover the areas that need work. He discusses the platform from both sides of that exchange.

For candidates, his advice is refreshingly scheduled: practise regularly, reserve time for it and join programming communities. “Consistency is key to improving your coding skills,” he says. The prescription contains little that would look impressive on a motivational poster. It does, however, tell somebody what to do next Tuesday.

He also treats interview preparation as an exercise in communication. A candidate needs experience explaining a thought process under pressure, alongside solving the problem itself. Other programmers can offer feedback and alternative approaches. Even preparation for an individual assessment can benefit from company.

This connects with his writing about collaboration without turning the two subjects into identical exercises. A business partnership needs boundaries. A learner needs feedback. In each case, another person can contribute something that a solitary encounter with software cannot provide.

A dashboard cannot change the office by itself

Harisson applies a similar caution to self-service business intelligence. Giving employees the ability to run reports changes who can reach the data. Whether they actually change their working habits is a separate question. His observation is direct: “Whether your teams will adjust to evaluating their own data and running their own reports is heavily influenced by culture.”

The distinction matters because software purchases arrive with an unusually persuasive promise: install the capability, receive the benefit. Harisson points toward the intervening work. Employees have familiar practices. Organizations have established expectations. A different interface does not automatically settle either.

Placed beside his comments on hiring, this becomes a recurring concern in his public work. Technical access and human readiness have to meet. A coding platform needs a practising learner. A reporting tool needs people prepared to use it. The user remains stubbornly present.

“One example was conducting a thorough vulnerability assessment of a client’s network infrastructure.”

Joseph Harisson, describing a cybersecurity project milestone

Security, measured in work completed

When asked about project milestones, Harisson offered a cybersecurity example: assessing a client’s network for vulnerabilities, considering their consequences and recommending measures to address them. It is a compact account of work that can be checked. The milestone marks a completed assessment and a set of recommendations, rather than an encouraging feeling about progress.

His technical writing extends that practical attention to network infrastructure. He discusses access controls, segmentation, device security and the difficulty of maintaining visibility. Older systems and limited resources complicate the picture. Security decisions take place inside actual organizations, with constraints that a diagram can make look tidier than they are.

His commentary on cybersecurity budgets likewise connects spending to business pressures. He identifies increasingly sophisticated threats, growing attack surfaces, regulatory attention and recognition at board level as reasons organizations invest. The budget discussion belongs beside the assessment example: one concerns the decision to commit resources; the other concerns the work those resources are meant to support.

When ChatGPT entered the conversation

In February 2023, Harisson joined a Cloud Security Alliance discussion about the implications of ChatGPT. The exchange considered the ways language models might assist attackers and defenders, and how the industry should respond. He raised the risk of more cyberattacks and argued for attention to offensive cybersecurity.

He also wondered what Google’s then-named Bard would offer through access to fresher information. That detail places the conversation in a particular moment: generative AI had attracted broad attention, and practitioners were trying to understand what the tools would change. The questions were arriving faster than settled answers.

Jim Reavis, the alliance’s CEO, replied that the industry needed to understand the implications ahead of the curve. It was a public professional exchange, grounded in a shared security question. For Harisson, it adds another setting to a career that moves between explaining technology and discussing its consequences with other practitioners.

The trolley and the directory

Then there is Costco. In his 2025 shopping comments, Harisson discussed electronics, clothing and bulk household purchases. Price mattered, as did the convenience of finding different kinds of goods in one place. The interests of the technology buyer and the household shopper turn out to have some overlap.

That does not make shopping a theory of company building. It supplies something more modest and more enjoyable: a glimpse of a founder evaluating the ordinary things he uses. The author biographies add walks and games; his professional comments add practice, feedback and preparation.

Together, those details give Harisson’s story its scale. He works on the choices that sit around technology: selecting a provider, preparing for an assessment, changing a reporting habit, deciding which risks deserve attention. There is room here for cloud infrastructure and for cleaning supplies. Both eventually require somebody to make a decision.