I found this week during my podcast listening sessions the concept of slow TV thanks to this episode of Invisibilia, to give you a resume of it, the whole concept is to produce a show with no plot, no characters, and surely no tension… Have you seen those live streams on YouTube of trains on Norway? Well, that’s basically it.

This concept on paper sounds so simple and yet, it isn’t. It made me feel uncomfortable for a reason, it made me listen to my inner thoughts and start thinking about the story of my life, it made me daydream of things and I should be doing or that I wanted to do and I haven’t done because I haven’t put the time to do them.

It all started with untaken trips that I should 100% do, but it grew further than that. Why haven’t I taken these trips? Why haven’t I put the time into researching what would make them possible? etc. And after a while contemplating the railroad and these beautiful nordic scenarios, it hit me.

I was giving some thought about my #programming approach using Test Driven Development lately and how much am I imparting the knowledge with my teammates of my experiences with it.

I must admit that I love the process and I’m not going to explain here what TDD is, there are many articles about it. I’m focusing this journal entry on one thing, the fact that it can be detrimental if you overuse it or use the process on the wrong things.

reported and allowing myself to understand the problem better by behaving in an automated way like the end-user.

It took me a bit to start writing about investing, at least publicly, because it has such a stigma with it, I’m not a financial advisor nor claim that what I’m saying works for me will work for you, but I do want to share these experiences hoping the best.

There are multiple vehicles to start investing, I have chosen more traditional means, but I got interested in peer-to-peer lending or better known as the P2P investing area, this is basically all about lending your money to people that want to take out loans from companies that aren’t traditional banks.

Before I start talking more about the topic, I want to clear something out, I started believing that lending was a shady business of corporations and pawnbrokers, but this isn’t the case, there are multiple types of companies and types of loans that you can opt into, more than you’ll be able to see in a lifetime.

Digging through my notes I found an article that spoke about the cult of done manifesto that I have saved a while ago and thought at that time it was an interesting way of looking at how you make and do things.

I connected with all these ideas and felt like it really represented my way of viewing how I wanted to approach growth in general. I’m someone that really dislikes procrastinating, but that also have a hard time at relaxing and just slowing down the pace, so banishing procrastination, in general, was a very interesting moto for me, I started with following the simple rule of “If you haven’t done anything about it, abandon it and move on to the next thing”.

That mentality has worked great to deliver different side projects lately, to grow my knowledge by reading, doing, and exploring different areas inside my job and outside of my job knowledge.

In January 2021, I launched the logbook, an app for people like me that want to do journaling with a more calmed down approach. At first, I envisioned this product mostly for me, I have tried multiple apps like mine in the past but haven’t enjoyed the process as much because all of them have something that I dislike, constant notifications, reminders, game theories, and other clickbait ways to draw your attention and make you use them,

So I said no to all those apps, and I built mine focusing on the core value of I want to journal when I want to journal and not when an app tells me I should, That’s how I like to journal and describe my journey towards completing multiple goals to myself.

It has been an interesting journey, and I must admit that I was quite scared when I launched this app and posted about it on producthunt. It received some really nice comments from the community, and it has been downloaded by people in 40 different countries.

Mostly known as “core team” or “architecture team”, are teams whose sole responsibility in the company is to improve the quality and performance of the experience that the end-user receives.

You probably heard them before and thought “… Isn’t quality and performance something that all teams should have metrics on?” Well… yes, but, and there’s always a but. Product teams run a backlog with new or tweaks of features that affect the business and most of the time these experiences are 90% there when speaking about performance and quality.

It’s that 10% that’s hard to achieve and requires more time or knowledge that most product teams can’t afford to have because the business has to keep finding new and better ways of engaging with the user.

I have been toying since the announcement of Apple One with the idea of moving into an all Apple ecosystem since I would be saving money by doing this.

Thing is… Spotify has been with me for so long that honestly, moving into an unknown UI/UX is so difficult, so that makes me think that even though I will be saving money by doing this, the annoyances and differences between the services might be enough for me to be loosing on features.

These are going to be my deep dives into the UX and UI of both apps and what makes them great or less usable in my personal opinions.

A list of the “rules” that I have been applying as my way to live for the past ~3 years and will continue doing.

I revisit these “rules” every year, and have found that in the past 2 revisions I haven’t added or removed anything from this list.

It’s not just about knowing the code or the properties in this case that you can apply to any element in your DOM. It’s also about knowing how each browser rendering engine will display your attributes.

Lately, the trend of front-end developers is to focus on JavaScript and learn all about the frameworks, V8 performance, and other elements that make these web apps interactive and fulfill their business intentions.

This is good, but it’s also clear that we have been neglecting a bit the CSS side of it, there are things like styled-components which try to break the barrier between doing CSS as we have been doing for decades now into the JS world and other similar tools, but that’s not the main issue. The main issue is:

I love journaling, mainly because it makes me rethink what I have done during my day and understand all the important things I have accomplished or couldn’t finish, and most importantly how that made me feel.

Now, to be effective with your Journal, you need to do various processes that you might not want to or have the time to do so and that’s when it all starts crumbling into less effective journal entries.

There has to be a better way of keeping the benefits of the journal but not having to do all the ceremonies? (Kinda a throwback to those discussions between doing SCRUM or Kanban hah), well, for me there is a way.

After a few months of doing indie apps on the side of my normal job, I have thought about key elements to make your apps successful based on it, there might be some obvious ones but I will still make the effort to point them out.

The goods and the bad ones, they are there, they are still hanging in the AppStore, do they have reviews? how many? How recent? What do people say in them?

This is one of the things I constantly check, at least once a week, because it gives me insights into what I could add to my app that people are clamoring on others and make them convert from their current one to mine.

It’s 2020, and we still have background: white websites when you enable your OS built-in dark mode, why? Why?! I get this feeling every time it’s 9pm, and I switch my computer to be in dark mode with the magic automatic setting from macOS and my browser stills shows me a white background at 300 nits of brightness.

I remember reading an article a while ago touting the browsers that support media queries for the dark mode, which had the following browsers:

Phew, that’s a long list… So… To detect whether a browser is running on a dark mode device or not, you’ll need support for prefers-color-scheme: dark media query, and as 2019 that was fairly new, but on 2020, boy oh boy, we basically have support for it on all browsers.

I used to be able to get by every day without knowing exactly how things made me feel. When people asked me how I felt, the answer was quite easy “I dunno. Everything seems ok so I’m fine”, and I was always answering “Fine and you?”.

So I started journaling because I wanted to know what I accomplished every day. This was a pain in the ***, not because it was hard to do, but because I had to invest time into writing things I accomplished every, single, day. So I asked myself, there has to be a better way of doing this?

Meet my approach to journaling — I got some goals I want to accomplish this year, and I only want to journal the things I do for those goals and on some occasions other things that just made me feel either good or bad but are worth remembering.

I have had the opportunity of grabbing a coffee with many colleagues, my latest one was with @sospedra_r, we used to work together, then we both quit from our previous company, and we didn’t… And now we are working together again. And that’s not my point.

My point is that taking a coffee talk with a friend, a colleague or someone that inspires you can take a profound influence on your work and daily life. You probably have been saying to someone “hey, let’s grab a cup of coffee when we have time”, but you are not making the time to make it happen.

You should. You should give yourself a moment to get inspired, have a nice conversation and discuss whatever is happening over your life, that persons life and live the moment.

I discussed this topic at my podcast a couple episodes ago, but if you don’t speak Spanish, let me give you my condensed thoughts here.

Designers have 1 clear advantage over developers, most of them understand how the customer acts and behaves. Why is this a big advantage you might ask? In a world where the tools start to become easier and easier to use, it doesn’t matter how you write your code that much, (yes, performance still matters and there are nuances to writing code, but I’m not going over complex code bases, that’s another topic.)

For most new endeavors or MVPs, a designer is now able to create a basic functional prototype and even connect it to a database like service like Firebase and start showing to the end customer how the app will behave and the customer can interact over a real application.

As a senior developer, learning a new language isn’t as hard as it was when I was starting my career, the way you express yourself is similar to other languages, so you think more about “what’s the syntax for doing X in this language?” vs “how would I do this?”.

So why learn Swift? Is it to just do apps for the Apple ecosystem? — I mean, I have been doing apps for the same ecosystem using React-Native. I don’t need to learn a new language to make good apps for the users inside their ecosystem.

I’m learning Swift because I want to make experiences that I believe right now I cannot make with tools like React-Native. Experiences that make my users feel engaged but that also, makes them feel appreciated in different ways.