296 karma · joined June 8, 2018
Foundry's upside is that it's extensible (modules), which increases traction and nurtures a community.
Most of the FOSS attempts will probably die if they won't take that approach (extensibility that is).
But, I can't understand if this is a subscription service or I can simply self-host. I don't want to sign up without having that information first.
I think it's silly to compare the two.
It's nice and all that you can clarify to your team what you want to gain (the big picture), and it's also nice if you want to explain how (details), but in my opinion it's not worth much if your sequence diagram doesn't explain test cases clearly and expect for them to be written.
(And honestly this is probably a mistake as it actually draws more attention to the original article).
Perfect landing. :)
I pretty much am having the same positive experience.
Additionally, I play around with it to generate statblocks.
The "you" (or: self) is a concept, a perception.
I am just me, and couldn't have been something else, or born in another timeline, or to different parents.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
(In python there is the "*" operator which should be equivalent: [1, 2, *arr].
Array(clicks) instantiate an array of length 'clicks', with its elements undefined.
Then "[...Array(clicks)]" takes the above array instance and spreads it as content in another array.
Seems redundant and they could've just used Array(clicks).
Zero-trust means that Access Control is more finely-grained, down to the machine/user level. In this approach we don't trust any machine/user inside the organization as well.
Bad design is a universal orthogonal problem.
Most of the times folders feel artificial. I prefer tags nowadays as the single source.
The times I separate to a folder is for very-specific Dataview data-only pages, and for storing assets such as images.
Whatsapp/Meta claim so, but have no proof. As with your comment, without proof we can't be convinced.
What are the recommended data storage file systems nowadays?
Otherwise, if you only rebase once the PR is complete, then you are likely to stumble upon conflicts due to the order of affected files.
It's a waste of the developer's time either way, not to mention that rebasing i.e. changing history on an (upstream) PR hurts the review experience e.g. comments on lost commits.
What I like about text-based tools like plantuml/mermaid is the ability to see diffs in PR.
Other industry modeling tool use binary databases to represent the UML model and make it harder (i.e. need to use their specific diff visualizers, if available) to review changes of the design.
Maybe plantuml should be adopted and maintained. Unfortunately it is still stuck in a Java implementation...
While comments in code/tests, README.md etc. are a good way to explain the bits and pieces of our software, companies have various stakeholders (software engineers included) that can't affored the time to translate these primitive documentation formats so that they make sense.
Visual representation works the best, and I wish that UML would be elaborated as a sketching mean to communicate better with stakeholders, rather than being a part of an ambitious software-generation ecosystem.
A role of one unit inside this component is to use the provided coordinates and only perform the calculation.
I think what I don't understand is the concept: "and so just a few letters are enough to recognize whole word".
This isn't expressed in the example. The rest of the word isn't hidden, it's still there in my peripheral vision (?). It is basically the same as I normally read.
If the unboldened parts of the words were actually discarded, I am not sure if I would be able to recognize all the original words, at least not efficiently and faster than the original.