This one will be on various personal thoughts on Medium, the JAM stack, the OpenAPI specification, and coding katas.
If you’re a regular reader or writer on Medium, you already know about the latest changes. Together with the new features, a partner program came into play, where companies and vendors will be more motivated to publish content about their products and services.
Being a small fish without financial interests in blogging (at least here and now), I decided to research new channels of communicating my ideas out of Medium. As a casual happy writer, I really wish Medium best of luck in their search of even more and better ways of monetizing their great platform and continue connecting deep thinkers.
Medium is aiming to solve problems at large scale for businesses and important individuals in the mission of un-breaking the internet and the publishing again. As a technical blogger, I’m interested in achieving smaller goals:
- I want to share about my wider “deep” thinking working with various technologies and tools. I am not vendor-interested in this communication channel. I’m more into experimenting with many tools and using only a few, later sharing my findings from hands-on work. For this, I can place my thoughts anywhere I decide to — I lately admire dev.to which feels like “the right place to be” — but the editor is not as easy as in Medium. So yeah, I can just do the markdowns in a static site generator and re-post wherever …
- I want to be part of a community somehow. Here at Medium, things tend to happen naturally. For example, I post a story about GraphQL which reaches 1.5k visitors, 7 of which come dev-blog.apollodata.com. I mean, that’s amazing — If I hadn’t shared my short notes on Medium, no-one using or reading about Apollo would have ever have visited my blog post. For this, I plan on disqus integration which seems straight-forward and covering this “business requirement”.
- I want my code to look really good, and I want it to be more interactive. This comes simply from the fact that I write mostly about code, so I want it to look nice. Medium allows effective snippets placement and github gists, yet there are many nice-looking styling options for code parsed out of markdown. Having control over the parsed version of your writing is an advantage in some aspects.
- I want to have statistics. Medium provides stats on each story and it’s really useful to have a global idea what’s going on. For the same GraphQL article I mentioned above, over 1k of the visits come from flipboard.com. That’s all I know as my application request to have a publication with Google Analytics required a payment I got informed a month after making the application. No Google Analytics on Medium unless you are having business goals. I think I’ll manage to integrate Google Analytics in my new stack without 70 dollars for the infrastructure.
At the moment, I’ve jotted just a few high-level milestones in the upcoming digital transformation …
- The J will maybe be in React. At this stage, I’ve found a decent book to follow on the way. At any case, investing into learning React will pay much better for me rather than writing new articles on a platform which can change its business goals tomorrow and just go offline.
- The A will be the github API. With inspirations from netlifycms, a well-known git flow translates to my upcoming publishing workflow.
- The M part of the stack — I didn’t manage to decide upon this yet as the trends are moving too fast.
So cool this is, google will show you a kickstarter campaign for the jam stack and there is a song to play while working:
Open API specification
In this month, I wrote a story about prototyping with the OpenAPI specifcation. It’s describing some techniques using the generator-openapi — made by the team of APIs.guru — really nice product to use!
I’m personally impressed by the community progress made around v3 of the latest spec. A release candidate was published in the beginning of the month, and various software packages literally sprouted in weeks.
I think there are mainly few links to follow the fast progress:
In the awesome list, there are few tools I hadn’t seen before. They seem to be made in quite a different way than the swagger-ui and swagger-editor, etc. that still keep popular positions in the toolbox.
Another good news this month for fans of the OpenAPI initiative was the v3 release of the swagger-editor which brought a warmly-welcomed auto-suggest feature:
The first competitive learning event (coding battle) from the Hack League team took place.
It was my first event since a very long time, so I could see some new people and technologies during the event :)
As organizers mentioned, the problems of the competition are open after the event and you are encouraged to see them and get encouraged to join the next event :)
I think (and I feel) that the problems are not the most complex thing you can see as a developer, but they definitely get closer to testing developers’ shape in solving problems fast and with confidence in the small steps.
As I really suck at making small steps really fast, I’m trying to get into the habit making regular exercise at codewars.com with the idea of improving shape through katas. This is not a radically new idea for me, as there are the ES6katas teaching TDD as codewards and nodeschool which provides various exercises for developers. (If you really enjoy them, you can give me a hand at the stream-adventure workshopper and I promise quick reviews and quick contribution gratification)
I believe in the important of taking care of my coding shape. I think it’s similar to doing sports and exercising or playing musical instruments. The tricky part being that programmers tend to overthink it sometimes …