I’ve found yEd to be a great fit for network diagrams. The combination of features really works well, with a visual tool and a the automatic layout options.

Surprised they didnt cover observer, the trace tool and the crashdump viewer.

As a Elixir developer who has dabbled with Go in the past, I found this post hits really close to home. One topic I do think needs further writing on is ‘why’ & ‘when’ to choose between something like Go and Elixir. Personally, I don’t see a large overlap of where I would use these too languages, but that is likely because for most service/web/network development I would reach for Elixir; and that covers the vast majority of what I write today.

• Working on a top to bottom monitoring plan for upcoming projects and how that will work with our hybrid cloud and DevOps tool sets.
• Create hiring plan for upcoming projects

• Delving deeper into Elixir and Phoenix on my usual CMS setup to learn a language and platform
• Testing out dynamic Routers for Phoenix to support my “plugin” system for the CMS

The correlation of EAV schema’s and JSON columns is a great point, and I think the post does a great job of simplifing the problem to show exactly how similar the two approaches can be.

But I can’t help but think EAV presents many different values then JSON as your code base changes. For example if you look at the Zotonic it’s data model is an EAV schema, based on something like RDF triples. It stores the binary of the code terms in a column… which I’m not a fan of at all. But it does have a very nice system of pivot tables which point back to the “Entity” resource table. This seem much more natural to me than either he JSON or embeded binary.

This is a classic article from Fred, if your looking for more info about handling issues like this in the erlang world see his ebook http://www.erlang-in-anger.com/

I love the presentation & content. Any chance you can share some the the source or do a write up on how you built it?