I don't think it's exactly what you mean but I've used monodraw to diagram

that is the aesthetic I have in mind 🙂 . But I'm thinking of something more in the data repl space like portal. In my current case I look at this function. I call (map sigmoid (range 0 10)) and get a feel for its output, but imagine something auto generating an asci comment in monodraw style. That's my vision right now.

what would an ascii diagram look like for that?

+                  +-+ +-+      
 1 |             +-+  | | | |      
   |             | |  | | | |      
   |      +--+   | |  | | | |      
   |      |  |   | |  | | | |      
   |      |  |   | |  | | | |      
   |      |  |   | |  | | | |   ...
   |      |  |   | |  | | | |
   +--+   |  |   | |  | | | |
   |  |   |  |   | |  | | | |
   |  |   |  |   | |  | | | |
   |  |   |  |   | |  | | | |
   |  |   |  |   | |  | | | |
   |  |   |  |   | |  | | | |
   |  |   |  |   | |  | | | |
   |  |   |  |   | |  | | | |
   +--+---+--+---+-+--+-+-+-+--------------------
     0    1       2    3   4

I'm on mobile so that probably looks a lot more chaotic than on desktop 😅

yes

Its is a bar diagram with input on the x axis and output value on the y axis

that really is not at all what I expected when you said visualization

Have you tried https://github.com/aphyr/gnuplot ? I haven't, but looks worth a try

Oh yes that's it

I was working on something like this a while back for scatterplots. I never got it to the point where it was ready for release, but perhaps it's still interesting to you. https://github.com/zane/plot

I'd love to see more on http://dev.to

put them on a blog you own

then you don't have to worry about some place changing in ways you don't like or going under and losing that work

Yeah I'd always say your own blog and just share it around

Yeah I like http://dev.to as well but I'm not sure if it will reach the average executive or non FP devs out there? I think its same with dev.rant...

I did my own blog years ago but its hard to get some exposure... Maybe having your landing page and share links to your articles in there?

Oh well, the other way around might work too 😆

i have no insights if you're looking to get "exposure", but i've seen countless blogging platforms go under over the years, and there's no guarantee that the one you choose today will survive. better to own your own domain and either self-host or redirect from a blogging platform so you can switch if they shutter

I'd have a non-Medium blog (it has a bad rap by now - think the paywall and the lower average content quality), link to every post from Linkedin Sadly a lot of things that once worked (like RSS, or arguably Twitter) are dead now, so I'd have a main self-hosted blog, and regularly link to it from the few platforms that currently work (LI, Slack communities, HN if you have something remarkable to say) Having a newsletter is another successful formula. Probably it has a higher bar for acceptance though - people should have formed the idea that they'll enjoy your content > [...] but I'm not sure if it will reach the average executive or non FP devs out there? Probably LI is the best bet here. For ensuring success I'd try to make sure that following me is a pleasant experience - few updates per year (of any kind), only important stuff (e.g. don't hit Like for every nice post you see - you can get unfollowed)

anyway, that's how I'd do it. As a contractor I've always wanted to have a sweet content pipeline. But one doesn't feel the need... until the day it becomes necessary 😅

If you do not write often enough to warrant a long-term newsletter, then a two-pronged approach works best. First, write a dignified, cogent, positive essay and post it on a blog you own. Do not worry about exposure. Second, after some time, write a very brief, nasty, emotionally presumptuous put-down of your blog post, and put it on Reddit. Make sure to use trigger words like "honestly" and "truly curious". Your goal here is to excite and incense your blog's intended readership, and compel them to post replies in support of you, but make sure not to provide too much detail on reddit because the point of the whole exercise is that your intended audience must visit your blog post to get the full picture before replying on reddit. Ideally, the second post would not obviously be under your own name, but it probably doesn't matter very much. 🙂

> I'd love to see more on http://dev.to @U02N27RK69K What do you like about it? 🙂

Decent approach in my experience: 1. Write your post in Markdown and publish to your personal blog. 2. Post key takeaways with https://carbon.now.sh/ in a thread on Twitter or something similar. Link to your post at the end. 3. Share on a relevant Reddit, clearly indicating it's a blog post. 4. If it's a long post, rework a subsection that can stand on it's own and post that to http://Dev.to and link to your post if interested readers would like to learn more.