rrrene

This is the final part in a series discussing the projects that shaped “my” 2015.

This is the second part in a series discussing the projects that shaped “my” 2015.

This is the first part in a series discussing the projects that shaped “my” 2015.

This past week a blog post by @mindreframer shared via elixirstatus.com sparked a lot of controversy and debate on Twitter.

I guess we are all finishing up work in our day jobs and preparing for the christmas holidays.

TL;DR Jesus, another style guide?

Last week I released Credo, a new static code analysis tool that acts as a code linter, but also focusses on teaching coding practices and code consistency.

I am overwhelmed by the response to Credo, the first teaching code linter for Elixir.

TL;DR Credo is finally out.

I have a soft spot for analysis tools, so it was no wonder that I jumped on the opportunity to contribute to Dogma, a code linter trying to bring Rubocop to Elixir (I just realized that I am one of the top contributors as of this writing, yay!).

Last week I had the opportunity to give a talk at EuRuKo about Inch & Inch CI.

Not too long ago I open sourced html_sanitize_ex and back then I took a day to think about the name.

Today the 100th post was submitted to elixirstatus.com – it is about testing compile-time exceptions in Elixir!

Exactly one month ago the “beta phase” of ElixirStatus started and it has been a real success in my mind.

There are more and more people pitching Elixir to their bosses and their bosses’ bosses.

TL;DR I am building a site akin to RubyFlow for Elixir.

TL;DR I think we need a site where people can post what they made in Elixir, simliar to RubyFlow for Ruby.

On June 22nd, the Inch CI site and services were not available for ~ 18 hours, as you may have witnessed.

It’s actually been a year since I posted the official annoucement post.

I was a fan of the mix hex.docs task since it was first introduced.

I recently announced the addition of Build History to Inch CI.

In my last blog post I wrote that the new design sets up Inch CI for extensions in the future.

I am happy to report that Inch CI got a fresh coat of paint.

Here we go: Five not-so-technical tips to improve your documentation quality: 1.

Before going into Holiday Hibernation Mode, I wanted to say Thank You!

Hex 0.6.0 (Elixir's package manager) is out and it includes "mix hex.docs" which pushes your beautiful docs to hexdocs.pm!

The short answer is: Yes.

Inch After 11 release candidates (yeah, I know) we finally got to Inch 0.5.

I get asked about the “value” which the docs badge provides to project maintainers, in the sense that I ask people maintaining popular projects to include my little badge and they ask back “What do I get out of it?”.

Besides analysing and grading your inline docs, one of the main features of Inch, the command line tool, is the suggest command, which gives you hints where to improve your docs - one inch at a time.

It has been a month since Inch CI started.

Inch is about five months old.

It has been three weeks since Inch Pages started.

Wait, docs?

Inch is a documentation measurement tool for Ruby that gives you grades instead of a “coverage score”.

Sparkr is a port of spark for Ruby.

As I pointed out in my previous post, documentation sometimes seems like the step-child in code metrics, static analysis and – last but not least – awareness.

Status quo Okay Ruby, so we have to talk.

Sparkr is a port of spark for Ruby.

Today I’m open-sourcing Homecoming, a little gem that let’s you easily traverse all parent directories of a given or the current directory.

tipsy.hovercard provides twitter-like hovercards for tipsy, the facebook-styled tooltip plugin for jQuery.