Veuxdo

16 ms·

151.
by Veuxdo 3y ago
> They are just expensive to build, expensive to maintain and go out of date fast enough that they're practically ephemeral. I agree with this if you're using drag-and-drop diagramming tools. Diagrams-as-code is a potential sol
152.
by Veuxdo 3y ago
> I've had the idea that graph diagrams (including architecture diagrams) can be paged - you show a different set of links/vertices on each page of the same graph (show the same node but different enumeration of edges) You&#x27
153.
by Veuxdo 3y ago
> Your main priority always should be to do meaningful things, to solve real-world problems, to be the man in the arena. It's always amazed me that people openly called themselves "thought leaders". You're practically
154.
by Veuxdo 3y ago
Agreed. Good architecture diagrams require genuine knowledge, insight, and, yes, effort. The creator needs to carefully decide what to show and what to omit from each perspective. It goes way beyond dependency diagrams, which is what automa
155.
by Veuxdo 3y ago
Italy has never been as libertine as France and Spain in this regard, no...
156.
by Veuxdo 3y ago
> and then head up to the public beach where 20% of women are topless and nobody gives a shit. A bit dissonant. Back in the 90s it was closer to 100%, so this is really a trend pointing in the same direction.
157.
by Veuxdo 3y ago
Not the OP, but sequence diagrams show individual scenarios, by definition. And there can be a lot of scenarios in a complex system. Thousands, perhaps. Relation (box-and-line) diagrams show the static relations between resources in a sys
158.
by Veuxdo 3y ago
You probably shouldn't convert diagrams from HTML to PNGs since you lose all accessibility. SVGs might be better; I'm actually not at sure.
159.
by Veuxdo 3y ago
If you're more technical, I wrote about an alternative mode of diagramming previously [0]. The summary is that whiteboarding has its place, but creating truly valuable diagrams has to be done deliberately. [0] https://www.il
160.
by Veuxdo 3y ago
There is no "two party system". There is a "first post the post" system. There are only two viable parties because of it.
161.
by Veuxdo 3y ago
You probably can get to 100% branch test coverage while being able to tie all tests to business requirements. It'll be expensive, though.
162.
by Veuxdo 3y ago
"If you were a goldfish, would you rather live in an ocean, or a garden pond? Probably the pond." Definitely the pond, they're freshwater fish.
163.
by Veuxdo 3y ago
> The point is: if your tests just assert which methods are called on dependencies with what arguments (or something close to that), they are extremely coupled and brittle. I'll go further. These tests are worse than useless; they&#
164.
by Veuxdo 3y ago
Sequence diagrams for showing specific interactions, box-and-line diagrams for showing static relations.
165.
by Veuxdo 3y ago
You could say that's the only thing they can do, by definition.
166.
by Veuxdo 3y ago
Makes sense. For Meta, though, by publishing papers like this are they hoping for something else other than PR? My only other guess would be attracting talent.
167.
by Veuxdo 3y ago
Does companies publishing papers about internal tools serve any purpose other than PR?
168.
by Veuxdo 3y ago
I'm wondering if it could be [the assumption that] those with natural talent have more untapped potential than those who have already "worked hard" for their achievements.
169.
by Veuxdo 3y ago
You can't use LS or anything like that to get around GDPR.
170.
by Veuxdo 3y ago
I like how the cons of SPA are "you have to manage state" and "clients have to execute code". I mean, aren't these baseline "get computers to do stuff" things?
171.
by Veuxdo 3y ago
I'm a bit biased, but I feel diagrams-as-code should use a stateless, declarative language (like json or yaml) and not a programming language. Programming languages have so much functionality that just doesn't apply to the output
172.
The System Architecture of Stack Overflow in 2016(app.ilograph.com)
3 points by Veuxdo 3y ago|0 comments
173.
by Veuxdo 4y ago
Security as well. Now step 0 is "Make it secure". When using microservices connected via the internet, you have no choice.
174.
by Veuxdo 4y ago
"Tasks" are the lowest-common-denominator directives that developers should refuse to estimate as a matter of self respect. If management wants an estimate, insist that they do their job and write a proper story instead.
175.
by Veuxdo 4y ago
Hi, author here. The article isn't about model-based vs. ad-hoc (at least, that wasn't my intent). Ad-hoc diagramming obviously has its (rightful) place. Whiteboards wouldn't be ubiquitous in offices otherwise :)
176.
by Veuxdo 4y ago
Hi, author here. An API can be a concrete thing (created, deleted, etc.) in cloud environments (e.g. AWS API Gateway APIs).
177.
by Veuxdo 4y ago
> But if Ilograph goes down, all I have is useless YAML. Depends. If you're using Ilograph Desktop [0], an outage won't affect you. And both with Ilograph Desktop and paid versions of the web app, you can export your diagrams t
178.
Concrete Diagramming, a Lightweight Alternative to C4(ilograph.com)
85 points by Veuxdo 4y ago|16 comments
179.
by Veuxdo 4y ago
Site is unreadable on mobile
180.
by Veuxdo 4y ago
Hint: if you're ever described what you're working on using the phrase "... in Python" or "... in Rust", this probably applies to you.

More ›