On topic: maybe I live in a bubble but I'm surprised how many people on LinkedIn expose far behind the curve they are by talking about MCP or RAG or even prompt engineering as if it's a suddenly-new discovery.
533 karma · joined June 29, 2014
On topic: maybe I live in a bubble but I'm surprised how many people on LinkedIn expose far behind the curve they are by talking about MCP or RAG or even prompt engineering as if it's a suddenly-new discovery.
There’s something kind of amazing here in that having read about property based testing I’m pretty confident I could apply it if I had a good use case.
There’s no loss if all of this changes dramatically, there’s plenty of real work to do.
But honest question: where is this normal?
I got a few weeks in to each and then stalled on all of them because the effort and motivation required to extend beyond the crazed early days _is_ still more than the utility I get.
In a professional context, paying someone for software to do something outside my core domain is still the practical option compared to the motivation and effort needed to maintain another dependency.
The neurologist I could believe exists somewhere in the world with the same last name.
1. Can someone remind me why it was so important/intentional at the start of the language that every object has identity? 2. Why is it important that we not synchronize on these value objects?
So I guess you and others here have had the experience of building something that was your own that felt better than the distro?
That we can describe something like “validation” in the abstract and automate some part of it says nothing about whether it’s worthwhile. I’m hard pressed to think of anything that anyone pays for that doesn’t meet this description. Why should being a founder be special or different?
It matters a lot what size the PRs are, and this varies wildly from place to place. I spoke to someone who instituted a “no PRs over 500 lines” rule. I would refuse to even read something that big unless it was just a find and replace or boilerplate.
It’s interesting how people talk about vi vs emacs, can’t remember ever meeting anyone who chose vi over vim, let alone enough people to make th at the debate.
> why wouldn’t you use it to deliver more value to your customers, faster? That should show up as MAU, conversion, revenue
Most roadmaps are full of garbage and would be better off being deleted. You get very few truly useful new features in a year.
To paraphrase ESR: the value to your customers is in them being able to know that can rely on your product still operating next year, not in those 20 new features.
Or to think about it another way, maybe block will be better off with fewer developers, but only if they produce sufficiently FEWER features so that they’re forced to prioritize.
The effort to start is way down and drives new demand for software (at least in my own portfolio of side projects) but the effort to keep going is still above this threshold.
Or what else am I missing about why MCP is more secure than a CLI?
Easier to read for humans is easy to read for LLMs. A more expressive language will bring about fewer misunderstandings when you apply stochastic tools like LLMs.
Just be sure you don’t choose something heavier/slower that is not more expressive.