Due to the software culture I've been exposed to, especially in web-dev, I am cautious about any level of indirection added by third parties. They may seem like a value-add to first-order, but when managed in the context of a larger system, tend to make performance worse, debugging more difficult, and modifications high-inertia. Not as a principle, but based on observations.
For example, When I see text like this: > With pre-built components for chat, presence, and notifications, as well as fully customizable UI primitives, Cord enables rapid implementation of sophisticated, in-app collaboration tools.
my pattern-matching brain thinks This is probably going to be slow, require the user to download a large amount of data, and may or may not reduce code required to implement, and will make customization and modification tedius. Maybe this isn't true for this particular library, but it seems to be a good rule, currently.
Devs: It sucks ass.
We would have a senior dev on the dealing-making-or-breaking call and he would say something like, "Wait -- sorry, do you support <specific thing that our system doesn't have>?" We would say honestly that we don't have that yet. Then the senior dev would say, "Ooohh.... sorry... yeah... we need (per-message arbitrary data storage | support for on-prem | real-time analytics | per-messsage privacy controls | etc.)." We eventually had to face the reality that one of two things must be true:
1) The market is just too fragmented such that there cannot exist one product that serves it
2) The devs involved really, really don't want to give a product like this a chance because they actually want to build fun features like this themselves and they're (rightfully) skeptical that some random startup can do it better
As I sit here now, I have some confidence that it's 75% #2 and 25% #1. Anyway, the basic shape of the sales calls went a lot like what you're saying.
It’s more likely literally what the author says - getting engineers onboard for something they themselves didn’t choose is difficult. I’ve been in the same position - lots of buy in from leadership / solving a real problem and providing real value. Then it takes months to implement due to having to corral a dev team who simply doesn’t care about your integration.
If you think most engineers are evaluating things based on the value it’ll drive for their product, you’ve lived a lucky career (and long may it continue).
Management wants to add Google ads to their premium offline app? Sure, they'll work to add that, who cares. Whether they spend two months building this feature or another, they're getting paid the same amount.
Some features are annoying to work on, some have long term implications for how much and what type of work will need to be done. Some just don’t fit with what the engineers want to work on. I know which features are going to take endless stakeholder meetings and which aren’t. I know which are going to require overtime and being on-call. I know which are going to kill off my pet project.
The most self-serving action a software engineer who doesn’t want to work more than the bare minimum can take is to reject as much as possible as being too difficult or bad or some other excuse.
What usually happens in my experience is that management comes up with some new requirements that they may or may not have already sold to a customer on a more or less specific timeline. They then ask for an estimate on when that will be implemented in the product.
If the estimate doesn't conform to their expected timeline, they typically challenge it vehemently. If you can convince them that it's a realistic estimate for what they're asking, they then start discussing ways to reduce the scope while still delivering more or less the same feature. If you can't, then it will end up at "you're being pessimistic, let's start and we'll pull through", which will later turn into "we'll have to work this Saturday because we're way behind on what we committed on that feature".
Sometimes, a very well respected engineer will occasionally be able to convince someone in management that a feature is just not worth it. But that is the rarest case I've seen, and it will definitely not happen if some junior or middle engineer tries to invent some generic excuse.
I get the context here (you are talking about software engineers, fine, and adding silly chat features, which is pretty low stakes). But, still, want to mention the general case:
The engineer’s professional obligation is to push back against the company if they are asked to design something impossible (and try to find some alternative that fits the customer’s business need if that’s possible), and to refuse or possible whistle-blow if asked to do something unethical/harmful to society.
We live in a very corporatized society where professions are being turned into jobs left and right. But, the engineer’s job is to just implement management’s requests in the same way that the doctor just exists as a conduit to your insurance company: that’s the way the company would like it.
From the other side, this looks like "management signed up for some flashy product based on marketing, but it turned out to be useless". Not recognising that seems like a substantial blind spot.
It would be interesting to hear from anyone who evaluated Cord and decided not to use it. I wonder if the risk that the company might fold entered into the decision.
Still, excellent of them to have open-sourced it; it superficially looks like they've put a lot of effort into making it usable.