
- I'm trying this again :D. I've upgraded everything to latest Nextjs 13. It
  took less than one hour and most of it was because of the effort needed to
  rebuild the stack of transformations to pass from markdown to HTML with
  remark and unified.

- I'm using Twitter a bit less and Mastodon a bit more. Migrated to
  [https://hachyderm.io][2] from [https://mastodon.social][3] and the vibes
  there are just **AWESOME**.

- For now looks like the oEmbed lib I use with the blog doesn't support
  mastodon, but It looks relatively easy to implement it. The library uses the
  list of providers from [oEmbed][4], but just doesn't support any type of
  discovery or adding custom providers.

  Support for custom providers might be easy to add, but automatic discovery
  might be a bit more complex.

- I've been working with [sorbet][1] a bit lately and my love-hate relationship
  with it continues. It is delightful to have types in Ruby (sometimes) but I
  still find that some of the trade-offs implied by using sorbet are just too
  expensive.

- For the last year or so I've been working mostly with Go instead of Ruby. It
  has somehow become one of my favorite languages. I'm drafting a post playing
  a bit with its `error` interface as it is one of the funnier parts of the
  language IMHO.

[1]: https://sorbet.org "Sorbet"
[2]: https://hachyderm.io "Hachyderm"
[3]: https://mastodon.social "Mastodon.social"
[4]: https://oembed.com "oEmbed"


Weeknotes 2022 - Week 44


- I've played with rust's [rustlings][] lately. They are an awesome creation of
  their community. It includes short exercises that are designed to help you
  understand Rust's syntax and some of its basics (like borrowing).

  Learning materials from Rust and [go][gotour] are both awesome and super
  useful for newcomers.

[rustlings]: https://github.com/rust-lang/rustlings
[gotour]: https://tour.golang.org/


Weeknotes 2021 - Week 7


- Spent some more time working on the [Zettelkasten][zettelkasten] with
  [obsidian][] and it is
  really a nice tool.

  I've started to routinely take notes during my day. As a way to organize my
  thoughts but also as a way to keep ideas alive. I have a ton of ideas
  regularly that I end up forgetting.

  I can now keep track, so I guess I'll start doing something about them at
  some point xD.

- I've done some research on Neovim's 0.5 native LSP. Works pretty well mostly
  out of the box and configuration from the examples was enough to make
  [solargraph][] work.

  Config is done with [lua][] which seems to be taking a more and more
  important role on neovim's community. You can even [configure][config-lua]
  neovim with Lua instead of VimL now.

  The good part is that I now have a very good excuse to learn Lua 😀

[solargraph]: https://github.com/castwide/solargraph
[lua]: http://www.lua.org/
[config-lua]: https://github.com/nanotee/nvim-lua-guide#initlua
[zettelkasten]: https://zettelkasten.de/posts/overview/
[obsidian]: https://obsidian.md


Weeknotes 2021 - Week 6


- This has been a very little "noteable" week, but I promised myself to keep
  the habit of writing notes, so here it goes.

- Started working with [obsidian][] a bit to start building a personal-linked
  knowledge base kind of like [zettelkasten][].

  It is working quite well so far. It helps me focus a bit and I'm starting to
  develop some topics in which I want to spend more time writing articles :)

[obsidian]: https://obsidian.md "Obsidian"
[zettelkasten]: https://zettelkasten.de/


Weeknotes 2021 - Week 5


- Excellent talk to understand what utility-first CSS means and many of its
  props/cons.

  https://www.youtube.com/watch?v=R50q4NES6Iw&feature=youtu.be

- I've been doing a lot of research in the last days on what an effective
  testing strategy for a Rails application looks like.

  Most rails apps I've seen do really ineffective testing. Too expensive, too
  hard to change and coupled to the implementation. It is a problem that starts
  obsessing me.


Weeknotes 2021 - Week 4


- Back from holidays on Monday. It would be great if we abolished work once and
  for all, just saying...

- Elixir has reached 10 years!

  ![10 years](/weeknotes-2021-week-03/10-years.png)

  I worked with it for around 1 year and the experience was really good. I'd
  love to use it more on production.

  I have a side project running on Elixir but it hasn't reached any stable
  milestone yet although I'd like to put it on prod during 2021.

- I removed the justification of text on the blog. Thanks Pau for the
  recommendation!

  https://twitter.com/masylum/status/1349051521254780933

  I have an awful eye for things related to design. I'm trying to learn more
  about it and any feedback like that is more than welcome :grimacing:

- I've started experimenting with [obsidian][] as a tool to keep a personal
  wiki and to try to keep a [zettelkasten][].

  Obsidian is a tool to build a "second brain". This is a repository of ideas,
  notes and whatever that is organized and connected. It keeps the data local
  and has a very nice interface.

  Regarding zettelkasten, maybe the definition from the previous link explains
  it better:

  > A Zettelkasten is a personal tool for thinking and writing. It has
  > hypertextual features to make a web of thought possible. The difference to
  > other systems is that you create a web of thoughts instead of notes of
  > arbitrary size and form, and emphasize connection, not a collection.

[elixir]: https://twitter.com/josevalim/status/1348661182853480448
[obsidian]: https://obsidian.md/
[zettelkasten]: https://zettelkasten.de/introduction/


Weeknotes 2021 - Week 3


- While finetuning this very same blog and adding some functionalities into it
  I reread [this amazing article][content-container] by my good friend
  [Ferran][fcsonline]

  It makes some very good points on how to apply the SRP on the frontend and
  specially on how to organize your components around it.

- Slack had an outage today (Mon, Jan 4th) and I honestly miss when our main
  communication tool was asynchronous (AKA email).

- I read [this article][micro-feedback] about micro feedback loops.

  > From what I have observed, you have to nail the basics, the things that
  > developers do 10, 100 or 200 times a day. I call them micro-feedback
  > loops. This could be running a unit test while fixing a bug. It could be
  > seeing a code change reflected in your local environment or development
  > environments.

  My personal experience is that the continuous feeling those loops are "not
  fast enough" becomes so frustrating that it slows me down in 2 ways:

  1. The way the article describes: by making it very hard to keep focus.
  2. I get obsessed with improving it and I need to restrain myself to avoid
     leaving everything until I fix it. You can go check my [dot-files][]
     :sweat_smile: if you want a to check them.

[content-container]: https://ferranbasora.com/posts/content-and-container
[fcsonline]: https://twitter.com/openfcsonline
[micro-feedback]: https://martinfowler.com/articles/developer-effectiveness.html#IntroducingMicroFeedbackLoops
[dot-files]: https://github.com/franciscoj/dot-files


Weeknotes 2021 - Week 2


- Started this new blog. Using [NextJS][nextjs], [TailwindCSS][tailwind] and
  [Vercel][vercel]

  I've been meaning to do it for a long time and I finally found time during
  the holidays. I've had this domain (fjcasas.es) since around 2016 and
  didn't find a use for it until now :grimacing:

- I discovered the amazing ecosystem around [unified][] (I used it for this
  blog too)

  Many of the functionalities on this blog are based on `remark` and on their
  plugins. There are plugins for many things, like code higlighting or oembed.
  Really interesting. I'll check it a bit more to finetune the blog.

- I started researching about [anki][anki] and how to use it to learn new
  stuff.

- I made some new year resolutions:
  - Less cell phone.
  - Build smaller side projects that I can actually ship (like this!)
  - Ship at least one of the side projects that I have started already
  - Write more. Keep a blog or some other other similar publication and
    periodically post into it.

[anki]: https://apps.ankiweb.net/
[nextjs]: https://nextjs.org/ "NextJS"
[tailwind]: https://tailwindcss.com/ "TailwindCSS"
[unified]: https://unifiedjs.com/
[vercel]: https://vercel.com


Weeknotes 2021 - Week 1


I was checking my `init.vim` today trying to find how to improve it a bit.

I found this case that could be interesting to share... so there it goes.

I write a lot of documentation. One thing I always try to do is to keep the comments I write well aligned and easy to read. That's why I keep them at a length of 80 characters, I find that to be easier to read than long lines.

You can use the `textwidth` configuration in vim to do that.

```vim
set textwidth=80
```

Once the text you write gets to a width of 80 characters vim will split it to
the next line.

![vim auto splitting text](/smart-textwidth-on-vim-when-writing-comments/textwidth.gif)

This is a very well known fact about vim, but you can read more about it if
you're interested with `:help textwidth`

```
						*'textwidth'* *'tw'*
'textwidth' 'tw'	number	(default 0)
			local to buffer
	Maximum width of text that is being inserted.  A longer line will be
	broken after white space to get this width.  A zero value disables
	this.
	'textwidth' is set to 0 when the 'paste' option is set and restored
	when 'paste' is reset.
	When 'textwidth' is zero, 'wrapmargin' may be used.  See also
	'formatoptions' and |ins-textwidth|.
	When 'formatexpr' is set it will be used to break the line.

```

The thing is that I don't want vim to do the same on the code I write. Mainly because it will end up splitting the code on a different place than the one I would want it to.

I needed a way to `set textwidth=80` when editing comments and then `set textwidth=0` when not editing comments anymore.

Enter [OnSyntaxChange](https://github.com/inkarkat/vim-OnSyntaxChange). This
plugin allows you to define vim autocommands that execute when the syntax of
the current file changes, in our case, when we're editing comments.

I use [vim-plug](https://github.com/junegunn/vim-plug) so I install it like
this:

```vim
Plug 'inkarkat/vim-OnSyntaxChange'
" This is a dependency library from the same author that includes
" some autoload functions that he uses on the plugins he writes.
Plug 'inkarkat/vim-ingo-library'
```

```vim
" Add a new autocommand that will activate when the cursor is on a Comment and
" it either enters or leaves insert mode.
" 1. The name: `Comment` means the autocmd will be called
" `SyntaxCommentEnter{MODE}`
" 2. A regex to max the syntax, on our case any syntax similar to `Comment`
" will match to us.
" 3. Whether we want to generate it to all buffers or only a particular one,
" we're ok with only the current buffer.
" 4. To which mode we want to link the autocommand. We're only interested in
" the insert mode
call OnSyntaxChange#Install('Comment', '^Comment$', 1, 'i')

augroup auto_wrap_comments
  " Set textwidth to 80 when editing
  autocmd User SyntaxCommentEnterI setlocal textwidth=80
  " Remove it again when leaving insert mode
  autocmd User SyntaxCommentLeaveI setlocal tw=0
augroup END
```

And with that code on our `init.vim` we now have that the split behaves like
this :)

![Smart text width](/smart-textwidth-on-vim-when-writing-comments/auto-textwidth.gif)


Smart textwidth on Vim when writing comments


2 or 3 years ago I bought an [Ergodox Ez](https://ergodox-ez.com/) I like
mechanical keyboards a lot but I fell in love with this on the moment I saw it.

I own one of the old versions. No key backlights or any other of those fancy
coloring stuff. It performs well, the cherry brown switches are great for my
use and being able to position the keyboard halves the way I want has improved
my posture when working a lot.

[![The ergodox](/my-ergodox-ez-coding-layout/the-ergodox.jpg)](/my-ergodox-ez-coding-layout/the-ergodox.jpg)

One of the things that made it a game-changer for me was the possibility to
experiment with custom layouts and, lately, the support for macros.

## The 4 layers

The layout is built around 4 different layers

- `0` or Home layer
- `1` or extended layer
- `2` or media layer
- `3` or numeric layer

Some of the ideas on it (like reducing the use of pinkies) comes from [here](https://implementsblog.com/2016/10/16/my-ergodox-ezs-custom-layout/)

## Layer 0 (Home)

[![Home layer](/my-ergodox-ez-coding-layout/layer-0.png)](/my-ergodox-ez-coding-layout/layer-0.png)

This is the default layer. It is built as a `QWERTY` keyboard but in order to
minimize the use of the pinky finger it has dual function keys on the home row
(those are the keys on light blue for `a`, `s`, `d`, `f`, `j`, `k`, `l` and `;`
that way `SHIFT`, `ALT`, `CTRL` and `SUPER`/`CMD` are mapped on parallel on
each hand and pinkies use is reduced.

This is weird at the beginning but once you get used to it it is so much better
than the regular keyboard distribution that I would never want to get back to
it.

The next thing that is worth mentioning here is the set of macros I have. Those
are the purple keys at the top and at the bottom of the layout.

The ones on the left hand are for Vim and going from top left to bottom right
they:

- Open git status
- Open horizontal split
- Open vertical split
- Fuzzy file finder
- Grep on project
- Close current buffer
- Repeat last test (with https://github.com/vim-test/vim-test)
- Run the tests on this file

For the right hand I had tmux macros and from top left to bottom right:

- Rename tab
- Open new tab
- Open vertical split
- Open horizontal split
- Change to previous tab
- Change to next tab
- Switch to next split
- Zoom split
- Enter search mode
- Close current split/window

I know, you're wondering "do you really use all that?" well, after some time
yes. I use it all. Besides, so far I've not lost my muscular memory so I can
still use a regular keyboard.

## Layer 1 (Extended)

The most important thing about this layer is that it has some programming
symbols like `[` or `]` and that it has the numbers (and all the symbols they
have on `SHIFT`) but in the home row instead of the top row.

[![Extended layer](/my-ergodox-ez-coding-layout/layer-1.png)](/my-ergodox-ez-coding-layout/layer-1.png)

I'm currently studying how can I change some of the other coding symbols to a
more comfortable position, like the row on top of the home one on the right
hand. But I have still not decided.

## Layer 2 (Media)

[![Media layer](/my-ergodox-ez-coding-layout/layer-2.png)](/my-ergodox-ez-coding-layout/layer-2.png)

This one is easy. It has the arrows on the home row and on the same position as
Vim `hjkl` + the media keys on the row on top of the home one + mouse movement
on the left hand.

I actually don't use that mouse a lot, but it helps having it around.

It has all the `F` keys on the position where the numbers would be on a regular
keyboard... I don't use them that much but I still want to have them around in
some cases.

## Layer 3 (Numeric)

This layer is pretty simple. It works as a numeric pad. I don't use it that
much but it gets useful when you need to do things with excels for example.

[![Numeric layer](/my-ergodox-ez-coding-layout/layer-3.png)](/my-ergodox-ez-coding-layout/layer-3.png)

## WIP

This is still unfinished. I change it from time to time and try to time and
regularly go through it to try to find ways to improve. Mainly to make things
more comfortable or to reduce typos.

## Can I use it?

I wouldn't recommend it if you're starting with an ergodox keyboard. That's
already a bit hard on its own. But if you want to give it a spin you can find
it [here][config]

[config]: https://configure.ergodox-ez.com/ergodox-ez/layouts/KrKNl/latest/0


Blog Posts