5 Matching Annotations
- Jan 2023
-
wiki.rel8.dev wiki.rel8.dev
-
https://wiki.rel8.dev/turbocharge_pattern_languages
-
- Oct 2020
-
github.com github.com
-
The problem is that not all tooling supports adding new dependencies from a transform. The first step is figuring out how this can be done idiomatically in the current ecosystem.
-
-
github.com github.com
-
create patterns & metaphor
-
-
-
it also allows for more divergence in how people write there code and where they put their logic, making different svelte codebases potentially even more different due to fewer constraints. This last point is actually something I really value, I read a lot of Svelte code by a lot of different people and broadly speaking things look the same and are in the same places.
Tags
- uniformity
- consistency
- software development: code organization: where does this code belong?
- programming: multiple ways to do the same thing
- strong conventions resulting in code from different code bases/developers looking very similar
- idiomatic code style (programming languages)
- idiomatic pattern (in library/framework)
- convention
Annotators
URL
-
- Sep 2020
-
Local file Local file
-
in constructing representations of how to supportlearning in particular cases
It reminds me of conjecture mapping. Are we going to make the similar thing?
-