3 ms·

(Appreciating this entire thread) - side question: you used the word ‘shape’ in the abstract sense, something I never came across until Claude vibecoding came a

(Appreciating this entire thread) - side question: you used the word ‘shape’ in the abstract sense, something I never came across until Claude vibecoding came along. Was it common / did you use ‘shape’ in the abstract sense before say 2025? Also, my coming from being a non-coder, I have a lot of appreciation for the possibilities for project failure one way or another due to a data model or project schema being wrong, even though I still only have a superficial understanding of what either of those concepts even are. . My question is, does your conception of data models in the abstract come from a formal academic course, like an algo’s & data structures course, or from trade-knowledge acquired through the practitioner grapevine?

supern0va 16d ago
>you used the word ‘shape’ in the abstract sense, something I never came across until Claude vibecoding came along. Was it common / did you use ‘shape’ in the abstract sense before say 2025? As far as I can remember, this has been fairly common in tech (or at least where I've worked) for some time, though it's possible that my memory here is a bit fuzzy. I will say that my spouse has often commented that "Claude talks like you", which I suspect is because it is trained on a lot of language specific to the tech world. >My question is, does your conception of data models in the abstract come from a formal academic course, like an algo’s & data structures course, or from trade-knowledge acquired through the practitioner grapevine? I have worked for over a decade on the telemetry for a specific major product that most people have probably used, and shepherded it through a major re-architecture, so most of this is from my career. I came in right after it was built and witnessed the pain as things had been layered on over a long period of time as the product evolved, so I've just witnessed all the pointy bits where naive early decisions can come back to bite you later.

supern0va 16d ago

>you used the word ‘shape’ in the abstract sense, something I never came across until Claude vibecoding came along. Was it common / did you use ‘shape’ in the abstract sense before say 2025? As far as I can remember, this has been fairly common in tech (or at least where I've worked) for some time, though it's possible that my memory here is a bit fuzzy. I will say that my spouse has often commented that "Claude talks like you", which I suspect is because it is trained on a lot of language specific to the tech world. >My question is, does your conception of data models in the abstract come from a formal academic course, like an algo’s & data structures course, or from trade-knowledge acquired through the practitioner grapevine? I have worked for over a decade on the telemetry for a specific major product that most people have probably used, and shepherded it through a major re-architecture, so most of this is from my career. I came in right after it was built and witnessed the pain as things had been layered on over a long period of time as the product evolved, so I've just witnessed all the pointy bits where naive early decisions can come back to bite you later.