how to convert an integer to string in Zig

I have been spending a while on learning Zig, by the way is pretty amazing.

fn convert_to_string(value: u32) []const u8 {
    var buffer: [4096]u8 = undefined;
    const result = std.fmt.bufPrintZ(buffer[0..], "{d}", .{value}) catch unreachable;
    return @as([]const u8, result);
}

How to Become Fluent on Your Own at Home

Some time ago I watched  this video I wrote down some ideas.

 Fluency equation

My motivation and my whys.

My real motivation, why I want to learn English.

Setting up a real goal. Setting up a deadline for reaching this goal. In other words, which level I want to have and in which amount of time.

It is basic to get my goals, create a routine, what I have to do on my daily basis.

Other interesting question is, which kind of English do I want to know?, because there are several types of English. English for Business is not the same as English for tourists.

I learned that C1 English level, is when I feel comfortable speaking the language, I can understand almost everything, but not at a native speaker level.

Other important question is how much time do I invest in learning English?

I have to become an independent learner. I have to take the responsibility or the control of your learnings. I am not used to doing that, because in a typical situation, there is a huge number of academies out there which teach English “without effort”. It seems that the responsibility of teaching/learning is the academy, not mine. The truth is that the responsibility for learning English or whatever, is only mine.

One of the strategies about learning English is to create my own bubble of English with lots of inputs. The author of the video calls It immersion. The cons of this method is that it takes a huge number of hours and the learner has to consume a lot of English content to reach their goal.

Other strategy is learning English through sentences, because context matters. It is like learning vocabulary, grammar and pronunciation all together at once. If I repeat them, I will learn how to put different parts of my mouth (tongue, lips and teeth) in the right way. Very interesting approach of that is, by imitation. Recording a sentence and comparing the difference. I think that it is a very good way of improving and learning as well.

An important aspect which we have to consider is to make this process of learning English really fun, because it is a journey which lasts too much time. In this particular case, consistency is very important.

Most of the learning is subconscious, it is the way that the brain works. For me this tip blows my mind up, because most of my learnings have been doing through effort and in a conscious way.

The other side of the very successful English learning method is time. If I have the best method, but I don't have time, I won't learn anything. By the way it is important to include a part of my routine at least 10 minutes every single day, on my daily basis.

A video about pair programming by Birgitta Bockeler

I found a very interesting video about pair programming, this is the link video

I find it very interesting because she tells some hidden things that happen, when someone practices this technique.

I wrote down about that, here it is my notes

Mutate Testing en javascript

 En la comunidad de aprendices de LeanMind se comentó la posibilidad de introducirse en el mutating testing en javascript.

Hace unos meses terminé de leerme el libro de Carlos Blé sobre TDD y me apunté para estudiar mutating testing. 

Lo primero que vi fue este video de Carlos Buenosvinos porque no sabía absolutamente nada.

Encontré varias librerías para hacer mutate testing con javascriot, pero la que más me convenció fue Stryker, porque tiene un activa comunidad que sigue desarrollando. Tiene tests y el código que estuve mirando muy por encima, no me pareció malo.

Me encontré con un video de codemanship que me ayudó muchísimo a entender con más profundidad el mutate testing y la librería Stryker.

Yo creo que esta práctica te ayuda a encontrar casos no contemplados, para generar una red de pruebas en las que tengamos más confianza. Creo que se puede hacer uso de esta práctica una vez que tengamos ya terminada el funcionalidad. No creo que una buena idea lanzarlos cada vez que hagamos un cambio en el código. Creo que es algo a tener en cuenta para nuestros desarrollos, igual que tenemos un analizador de código estático u otros elementos que nos ayudan con nuestros código.

learning resources

freeCodeCamp videos
learncodeacademy videos

Patterns And Principles:
- http://principles-wiki.net/
- David Gómez - Midiendo la calidad de código
- No Tiene Nombre 31 - Algunas experiencias y opiniones sobre Domain Driven Design
- Alfredo Casado - OOP & Connascence

eXtreme Programming:
 - https://github.com/xpeppers/starway-to-orione
- Eduardo Ferro - Agilidad Hacia la entrega continua ¿Qué te lo impide?
- Luis Rovirosa - Desarrollando a velocidad de crucero

Reactjs:
- https://developer.microsoft.com/en-us/fabric#/components
- https://www.edx.org/course/react-router-and-redux

Achitecture
 - .NET Application Architecture - Reference Apps
 - Serverless apps Architecture with Azure Functions
 - Starting poing for Clean Architecture
 - Robert C. Martin - Clean Architecture

Craftmanship:
- Eduardo Ferro - Simplicidad para desarrolladores
- Modesto San Juan - TDD mi cuaderno de recetas
- Be SOLID my Tests - Mavi Jiménez
- S.O.L.I.D Python - Eduardo Ferro
- Carlos Bastos - Empezando por el principio (de diseño)
- Xavi Gost - Refactoring a Patrones, kata Mars Rovers
- Xavi Gost - Refactoring a Patrones, kata Gilded Rose
- Xavi Gost - Refactoring a Patrones, Kata Bowling
- Xavi Gost - Kata Potter
- Xavi Gost - Test Doubles
- Xavi Gost - SOLID

Non Tech:
- Katia Aresti - Entrevistas al borde de un ataque de nervios

Health
- Ergonomics Expert Explains How to Set Up Your Desk
- Prácticas saludables en la vida del programador
- Máximo Rendimiento Personal para Ingenieros