3 ms·
That's a lot of words, and then nothing concrete. I can counter that with concrete advice: make your own tooling because there isn't anything out there that is
by boxed 3y ago
That's a lot of words, and then nothing concrete.
I can counter that with concrete advice: make your own tooling because there isn't anything out there that is good. In iommi I wrote tooling to write tests with extra comments that are then projected into docs. The advantage is that the code examples are a part of the normal test suite. I also generate output .html files from examples that are then embedded as iframes into the documentation, which is a superior way of doing screenshots.
- NewsaHackO 3y agoThe article looks like it mostly for advertisment of their product. Quality for the article is definitely not the writer priority.
- MilStdJunkie 3y agoYup. I'm in the techpubs systems business, and I tell everyone this: no matter how much you're spending on the tool stack, you will be wrenching on it, and probably quite a lot. So if you need to pay someone else to wrench, you have to keep that cost in mind; if you anticipate a metric buttload of wrenching, make sure to use something you can wrench yourself. You're going to run out of money reaaaaaaaal quick if you're paying a dozen PTC/Adobe consultants to come visit you once or twice a year. Not to mention when you need an emergency change yesterday - good luck getting an actual real English-speaking PTC rep to return a call this financial quarter. Nothing irritates me quite as much as the usual "Open Source Isn't Cheap!" people. Mostly because of the cognitive dissonance: of course it's cheap, it's free. You're trying to gaslight the English dictionary. Cheap doesn't mean cost over time, it means cost right now. A 1998 Kia Sedona is cheap. Now, does it cost a whole bunch? Well, maybe it will, and maybe it won't[1], but that doesn't make it not cheap. Goddammit. [1] Although, with the Sedona, probably it will. I'm more of a "grab a farted up old Lexus or Infiniti" kind of guy.