When I explore or consider alternatives, I don't think of or ask myself about design principles, but consider and weigh what could and would make sense where I am.
More than principles, the guiding goal is Maintainability - Readability, Graspability, Consistency, Correctness, Robustness. Weighted against constraints.
I guess separation of concerns is a big one I use implicitly. Like many others.
Only one of them barely reaching 200. For the size of the Linux kernel I find these numbers surprisingly low.
I've aired my frustration about the terminology previously; anyway, I'm trying to accept the terminology in the interpretation it could make some sense:
You tell the AI the "vibe" of what you want the result to have, and it does that - but of course it's not necessarily that simple. You may end up doing prompt engineering, multiple iterations, trial and error, etc
When we tried a product at my workplace generating a web app prototype in react seemed viable and reasonable, possibly good for prototyping and demonstrating. We also tried a Blazor app, and it utterly failed. I suspect because of less training on it and much more complex mixture of technologies.
This is a community for discussing things about programming.dev itself. Things like announcements, site help posts, site questions, etc. are all welcome here.
So instead of one replacement… we have seven:
haha
I did not go through those phases.
Sharing for anyone else not familiar with AT Protocol:
The AT Protocol is an open, decentralized network for building social applications.
Account portability and Scalability through activity aggregation
Bluesky uses AT Protocol. The connected network/platform is called the Atmosphere.
Bluesky Social has pledged to transfer the protocol's development to a standards body. - Wikipedia
I didn't see any mention of other software/platforms using AT protocol on the protocol website or Wikipedia.
I am very proficient in my primary language, C#.
Writing more context out feels like boasting, so I think I will skip that and go to a summation/conclusion directly.
Knowledge and expertise comes from more than the language. Which you hinted at. The language is only our interface. How is the language represented, how will it transform the code, how will it be run. There's a lot of depth in there - much more than there is in the language itself.
I learned a lot, through my own studies and reading, studying, projects, and experience. I'm a strong systematic thinker. It all helps me in interpreting and thinking about wide- and depth- context and concerns. I also think my strengths come at the cost of other things, at least in my particular case.
You're not alone. Most developers do not have the depth or wide knowledge. And most [consequently] struggle to or are oblivious to many concerns and opportunities, and to intuitively or quickly understand and follow such information.
Which does not necessarily mean they're not productive or useful.
Even C# has something that few people use, but it has something.
Huh? Are you claiming few people use NuGet?
In my Firefox I get a NS_BINDING_ABORTED error on the Google Fonts font request.
And they didn't specify a font fallback, only their external web font. It would have worked if they had added monospace as a fallback.
The "rectangle" probably isn't supposed to be this messy?
They mention examples of such frameworks and technologies; listing them and adding hyperlinks: HTMX, Qwik, Astro, Remix, SvelteKit
I've known HTMLX, which I wanted to make use of and try out for a while now. Remix looks interesting [to me] too.