HackerTrans
TopNewTrendsCommentsPastAskShowJobs

wstuartcl

no profile record

comments

wstuartcl
·قبل 3 سنوات·discuss
While I agree that getting locked out is a clear risk of any business built against another company's platform I do think it is perfectly reasonable for someone whom has done so for 15+ years (and is part of an ecosystem that helped establish that third party) to be publicly upset for the mode and method for how this change happened at twitter. Its not just his frustrations being vented in this post but the impact to his users (which is well out of his control).

Twitter's actions of breaking the API for the largest 25 integrators with millions of users (by all indications) on purpose with 0 deprecation warning, 0 communication, 0 response the the break is garbage. Knowing that Musk is the agent of change and the one setting these actions in place he can take the heat.

at the end of the day I am done with twitter as it is, so its no skuff on my skin either way -- as far as I am concerned there is a clear path forward for the types of actions Musk has taken at twitter. It is just a matter of time.
wstuartcl
·قبل 3 سنوات·discuss
I think it will be interesting to see the next few years. There were quite a few orgs that jumped as the pricing was introduced, detachment from k8s etc that was a side effect, a bunch of new options in (free) market. Just from my perspective out of the orgs I know of that bought into the pricing, every one of them has active projects to get off in the next year.
wstuartcl
·قبل 4 سنوات·discuss
I mean if you ask the same question to a human your question is ambiguous enough that you will get the same type of issues.

How is any being or AI meant to read your mind to know you don't want instructions for system X but assume the instructions would be good on system Y etc. I feel sorry for the humans you expect to query you to get what you really want out of you.
wstuartcl
·قبل 7 سنوات·discuss
I agree 100%. In my view every change you make to your software (that is not a bug fix) is just as likley to reduce the perceived value for your current customers as to increase it. Spread these changes over time and you segment the customer base across different states of pleased and unhappy. Naturally as the customer base denormalizes against any given state affinity you reduce the overall population's feelings about your app.

IMHO this is one of the hardest problems to solve with long lived applications. What changes can be made, what features can be added or changed and what "look and feel" changes can be made without tilting the affinity of the current users vs expanding the value proposition for new ones.