The Stripe article starts with "I worked at Stripe for 3+ years" so Stripe is clearly a company, the article itself is focused on the operations & team cohesion side of stripe not on their line of business.
The article about Julia is hosted on `julialang` and within the first paragraph there is a sentence containing: "So I thought it might be helpful to the broader Julia community—and maybe even for other programming language communities—to actually write down Julia’s release process"
None of these articles give you a full and complete comprehension of their topics - walking away from Strip I don't know if they're a listed company or what their market cap is - but I was given enough information to make it through.
ACH is not a common jargon term, and even with common jargon there usually is some explanation, if someone writes a well-written article about some MySQL quirk, it'll probably have the term "SQL" somewhere in the first paragraph and it'll certainly have the term "database" and "query" - those hints are enough to grasp the general subject matter. The word "bank" doesn't show up in the article until paragraph three and the jokey description of doing it to "a dead person" immediately derails the users ability to grasp that it's a monetary transaction - it's perfectly logical that monetary transactions need to have error handling around dead, missing and not-yet-existing people, but leading with that point harms readability.
I think this article is a great example of a poorly written piece that with some very minor edits to clearly define the scope of the article would be a lot more legible.
