MÁLAGA, SPAIN — 2026 · PERSONAL REFLECTIONS · anudoranador87.github.io

Dev Log 365 Why I'm here — In my own words

"Logic is my superpower · Syntax is just the tool"  |  No filters · No self-pity · Real data

My biggest differentiator

The context behind the code

These reflections are not technical entries. They are the why behind the 365 days, behind EquiShift and behind this transition. I write them when I have something real to say — not to fill a calendar.

Reflection 01 Why coding · Why now

At 39 I decided that whatever happens,
I'm going to fight for this.

This is not an epiphany story. It's a story of wrong decisions, years in the right place for the wrong reasons, and a mental click that came when I understood that the path I thought I couldn't take had always been there.

The origin

When I was 8 or 9, my father bought our first home PC. The only way to play games was through the DOS console. Commands. Directories. File paths. Without knowing it, I was learning to think in a specific way — if you enter the right command, the system responds. If not, nothing.

Then Windows arrived and that faded into the background. But I was always the person who fixed computers. At home, among friends, at work. Not because I had any training — but because something in me enjoyed the process of finding what was broken and fixing it.

When I finished high school, the grade requirement for Computer Science was high. I chose Physical Education because sport also drove me and I thought I could teach it. I was wrong. I like doing sport, not teaching it. I worked in that field for a few years, but it never fully fulfilled me.

"I was always the person who fixed computers. Not because of training — but because I enjoyed the process."

The real path

I moved to the UK at 30. Six years in hotels. I learned real English, learned to work under pressure, learned to manage crises with people from ten different nationalities. Hospitality wasn't my first choice — but I was good at it and it opened doors.

When I came back to Spain at 35, 36, I already knew I wanted something different. But I thought that to change careers I needed years of university, formal training, a path I couldn't afford while working and supporting my family.

The click came when I understood that wasn't true. I don't need a degree to do this. I need real projects, demonstrable consistency and applying everything I already know. Because at 39 I have something a first-jobber doesn't: judgement, real experience under pressure and the maturity to know why I do things.

"I decided to change careers at 39. And whatever happens, I'm going to keep going."
Reflection 02 Why EquiShift was born

One person had 70% of weekends off.
The other four shared whatever was left.

EquiShift was not born as a portfolio project. It was born from an injustice that repeated itself year after year in my workplace and that nobody questioned because it was hard to prove. Until I decided to prove it with code.

The real problem

There are five people in my reception team. The shift distribution has always been manual, and the result year after year is the same: one person gets 70% of the year's weekends off, and the others share what's left.

Without anyone consciously deciding it. Without anyone calculating it. It just happens, repeats, and nobody questions it because it's hard to prove.

Public holidays, annual leave, weekends — everything interacts in a way that's nearly impossible to manage fairly by hand. When someone ends up working more than their fair share, they get financial compensation. But that's not what I'm after. What I want is to be able to enjoy a free weekend with my family like any other person. For the system to be fair from the start, not for the damage to be repaired afterwards.

"I'm not looking for financial compensation. I want the system to be fair from the beginning."

The solution

That's where EquiShift was born.

If logic, maths and programming can model this real problem, then it makes sense to build it. It's not a tutorial project. It's an algorithm that solves something that has been unfair in my workplace for years, and that is probably unfair in many other teams that don't have the tools to calculate it.

As I progress in JavaScript, every new concept gets applied here. The 365-day loop, modular arithmetic to detect weekends, the data model for each worker. Everything has a real reason behind it.

That's what makes this project worth finishing.

"It's not a tutorial project. It solves something that has been unfair for years."