Are the scores here normalized such that each point difference is equidistant?
153 karma · joined September 27, 2009
chris@bootstrapital.com
Are the scores here normalized such that each point difference is equidistant?
I'm equally excited -- I've spent much of my career building janky internal versions of popular SaaS out of necessity since we didn't have the budget to buy. To be able to do a better job with less effort is enticing.
But this is: a) a step-change that hasn't had a full year to bake; we should all anticipate the pain associated in the medium term after a few iterations, inevitable feature add-ons, etc. b) beside the point.
Yes, many teams can also build internally, but it doesn't change the fact that others find value in outsourcing. Just because it's much easier, or rather __because__ it's easier to stand stuff up, it's imperative we prioritize what gets built.
If [Anthropic](https://fin.ai/customers/anthropic) themselves are willing to vouch for the value-add, I think it's silly to suggest that teams with budget and higher priorities should trade the time and focus to roll their own.
It's an incredibly common aspect of business. Enterprise level contracts often include the sort of white glove service to help fill in these sort of gaps. On simpler plans, having the tooling provided frees up just enough capacity to handle the exceptions to keep the process running smoothly (since one doesn't have to build and run simultaneously).
Sometimes people want to minimize the hassle with stuff. It's why car washes and oil change places and coffee shops exist.
That's why it's called learning.
Accountants and marketers didn't build the legacy tools teams are stuck with.
[0] https://www.amazon.com/Incorruptible-Good-Companies-Great-St...
People rag on StackOverflow for being mean, but it was a good training ground for developing habits that satisfy the social contract of professional spaces.
I ran it last night and it was just fine as a drop-in replacement for my usage. Disappointment averted with minimal effort on my part (it helps that my typical workflow is pretty mundane/close to the defaults).
Alas, I now feel the sting of disappointment.
It's a nice departure from the visual overstimulation I get while in VS Code (for which I have to take some blame as I need to remove some installed plugins).
There are a couple of features shown in the v1.0 video that I was unaware of and am keen to check out.