It has been a hard couple days to write. I’ve been quite busy and did not find a lot of time to do so. This is why those are very short posts. I am seeing this pattern of doing something just because I want to do it daily, but where it does not have a lot of benefit because it does not make my brain turn really on. Noticing this is quite an improvement though, and I want to expand on that. Read more

I’ve been working with Golang at my day job lately because it really makes it easier to deploy since it compiles to a single binary. However, I really am starting to not like the language that much, especially when I compare to Rust. I find a lot of documentation not very clear, having to deal with pointers is often confusing (especially when compared to the Option enum), and I find things unusually complicated. Read more

No time to work on my project today. But it does not mean I will stop. I will keep writing my daily post. I will get back to improving my landing page for the 365 days of side project. I will get back to outreach. I will get back to design. As long as I get back to it, progress will be made.

Yesterday, I finished a first version of the landing page for the 365 days of side-project challenge. The idea is to have a method that will help you develop the habit of working on your side project every single day. When you are coming back from work exhausted, have to take care of the kids, prepare dinner and all the other household tasks, you feel completely drained and you just don’t want to do even more work. Read more

I just want to list a few ideas of challenges that I could get running: 365 days writing challenge 365 days anti-procrastination challenge 365 days twitter challenge 365 days design challenge 365 days coding challenge Those obviously need some marketing rework (this could also be a challenge, the 365 days marketing challenge), but there are quite a lot to do with that. Also, 365 days may not make sense in some cases. Read more