The API Stack Profiling Checklist
I just finished a narrative around my API Stack profiling, telling the entire story around the profiling of APIs for inclusion in the stack. To help encourage folks to get involved, I wanted to help distill down the process into a single checklist that could be implemented by anyone.
The GitHub Base
Everything begins as a GitHub repository, and it can exist in any user or organization. Once ready, I can fork and publish it as part of the API stack, or sync it with an existing repository project. https://goo.gl/WwVSBY #DataIntegration #ML
Customizing Visual Studio Code for Writing
ICYMI: Some time ago I wrote a post on how to configure the Atom text editor for (technical) writing that proved one of my most popular posts. At the time I was looking for a text editor that was extensible, open source, and that I could optimize for a writers setup, not just for coding. Atom has vastly improved since that post, but still suffers from a lot of reliability, memory, and CPU issues, thanks to the fact it’s built upon web technologies, not native code.
Also since that post, Microsoft released Visual Studio Code, that, despite having similar origins to Atom, somehow feels more polished and is more performant. On initial inspection, it’s still more optimized for coding than writing, but I thought it was time I dug into to how it compared to Atom from a writer’s perspective. To do this, I refer mostly to the original post and recreate the same sub-headings and needs. Since I first wrote that post some features in Atom changed, as did my needs, so this post won’t stick entirely to the original. https://goo.gl/XK2QVG #DataIntegration #ML
