Start Here! (Blog Introduction)

The first point of contact to have with the blog to understand the motivation behind it.

random intro

Welcome to My Personal Blog

Introduction

The idea of creating this blog didn’t come naturally , but as part of my interest in creating a portfolio-like page to showcase a little bit about me, to put in action my web development skills and share some of the things that I find interesting, or what I do in my free time, sometimes related to work, sometimes not.

I do not intend to be selfish and talk about me in here, but I’d like to share things that I personally do or think that might be useful for someone else. I will get into detail of my intentions in the following sections.

I don’t want to forget one of the reason why I started this project and the blog itself: to have fun, to learn new technologies (Astro + DaisyUI + TailwindCSS in this case) and to have a good excuse to write some content from time to time.

What to Expect

I am clearly not experienced in content creation , so do not expect to have regular posts or high-quality articles (at least for now, and not my plan for the short term).

However, as I mentioned before, I found this blog to be a good excuse to sporadically share what I’m doing, using it as a database of things I faced, and also to show people -that might be interested in my profile- what I have done in the past.

Relationship in between this blog and my personal career

When I started working in 2017 I was still studying at the University and I was watching the entire industry go crazy because there was not enough talent to cover the demand of developers. The job opportunities were (and of course they still are) enormous; but also the amount of people competing for the same positions also increased . That means that you need a way to differentiate yourself and to demonstrate who you are.

Which are the things that companies are looking for in a candidate?

We all know that getting a job in tech (or at least in the software engineering sector) is normally a long process where you go through various steps including a technical test. Not all people are comfortable with this kind of evaluation : live coding, whiteboard algorithms, offline exercises, etc.

I mean, of course you need to prove somehow what you know and what you are capable of doing, but at this moment software engineering is not only about algorithms, data structures, and all the technical stuff . There are many other aspects that should -and normally are- be considered when interviewing a candidate.

The problem with that is that a lot of those things are not easily demonstrable in a normal interview process . That means that people like me that have a lot of other skills apart from coding, have a hard time showing them.

My goal with this blog

Having into consideration the last section, I found that it could be useful for me to have a place where I can share how I think, what I do, and to describe my profile better.

In that same process I might share something interesting or useful to you; maybe make you reason about it , something that I consider a bonus and I appreciate when I read/hear other people’s thoughts.

But then, what’s my profile?

I like to think about myself as a context focused engineer, meaning that I try to get as much context as I can to work on a certain feature so I get a clear idea of the intent and the public that it’s meant to satisfy.

Lately I like to add that I enhance my workflow using AI as a core part of my development process as it speeds up a lot of things that normally mean time spent typing: creating tests, adding mocked data, re creating really similar UI where just a type changes, etc, etc.. if you are an engineer and you use at least a bit of AI you’ve been there.

And the other really important aspect about me that I like to highlight is my conviction that communication is the most important part of our work as engineer to make sure that we are all aligned in the objectives, that we share all the information that is useful for us and the rest, that we help each other to move faster and that we effectively communicate with the rest of the company for the same reason I mentioned earlier.

Also I was told by my previous managers that I’m pretty good as a “leader” as I have the product always on top of my mind , I care about context (we know that already) and people listen to me at some point somehow (who knows why haha).

Additionally I consider that I have a really good eye for the UI/UX and I really care to have those things delivered correctly.

Closing thoughts

If you reach this section I would be really surprised and happy, so thank you for reading this far!

I hope that you find this blog useful and interesting , and that you can learn something from it .

See you in the next one !