The conversation

Lessons learnedExperience excerpt · English

I used to think this way until I started a company with employees

… I used to think this way until I started a company with employees. My opinion on the matter changed almost instantaneously. 1. One does not simply set up their own "X". Setting up X takes time and you will also have to manage it, which also takes time (and is harder to anticipate when you are fully responsible for managing it). 2. As someone making decisions on this type of stuff (eg a founder, executive, head of IT, etc), maintaining something like X is a poor use of your time and not something you want to have to even think about. So you'll be paying for it anyway even when it's "free" by having an employee maintain it or sacrificing your own time on it. 3. You may trust yourself to be able to maintain it properly, but if you delegate it to an employee, the math changes. Now you have to hire someone you can trust to do a good job maintaining it and who is willing to do that kind of work. And you need to consider things like "what if that person quits/retires/gets sick" and "what if they get hacked or go rogue" and "what do I do when they go on vacation"? 4. …

Original discussionAsk HN: What's Wrong with IRC?91 source comments · at import
2

What was this responding to?

Parent context · original excerpt

IM

With the proliferation of chat apps like Slack, Discord, Teams, etc. why don't more companies just set up their own IRC server? The pricing for Slack seems insane for something that was essentially a solved problem 30 years ago. Admittedly, I haven't used IRC much and I know the UI/UX isn't the best, but that could probably be fixed pretty easily and tacked on to the existing messaging infrastructure?

Full original

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 2

Direct replies available in this import. Original-language excerpts.

WA

> Why don't you grow your own food? Why don't you just write your own payment processor? I find that usually if someone says "why don't X _just_ do Y", they haven't really considered what it takes to _just do Y_. Similarly, > I know the UI/UX isn't the best, but that could probably be fixed pretty easily could be expanded into 50 points of why exactly it wouldn't be _pretty easy_ to to "fix IRC UI/UX". Honestly I don't know what answer OP expected here. If it's easy to set up/maintain Slack alternative based on IRC, with fixed UI/UX and appropriate for _most companies_, they should simply start a Slack competition for half the price and rake the profits, I guess

Full original
WJ

I wish I could upvote this twice. Many people only consider monetary cost as "cost" because their own time is basically free. But when you have to pay for any extra time spent on "fixing" IRC to become business capable, the proposition by Slack and their competitors starts to make a lot more sense. Even if you already have people capable of doing the work, do you want to task expensive employees on replicating something you could easily buy at a lower price or do you want to have them work on something that will actually increase revenue?

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.