Tailwind is a huge pain.

by

A few months ago, I discovered the Bootstrap framework. It's a straightforward way to create websites quickly. I wasn't necessarily fond of it since I haven't had the project that will make it useful yet. So I went on with my personal things using old school CSS. And I loved making responsive websites using just CSS.

Recently, as I was watching a couple of tutorials on Node.JS, Express.JS, etc, I stumbled upon a new hyped framework which was Tailwind CSS. I jumped on ahead because like Bootstrap I wanted to get on the wagon and at least learn it so I can add it to my slowly growing resume. Usually, I would be struggling to find a proper tutorial on the web but searching on YouTube, I found the most comprehensive tutorial I could find in the shortest amount of time. I literally studied and tested the components of Tailwind for around 2 days.

As you may already know, I still consider myself a huge newbie as a developer. Though the idea of tech, hardware and software, had not been a stranger to me, I still consider myself lacking in the area of theories and computer science concepts. Since I mostly grew up focusing a lot of my years in art and filmmaking, unlike others, I have not been exposed to a lot of technology-related topics in classes so I had to seek my own. I built computers, upgraded parts, I helped my friends to build their own, I hackintoshed my PC, I built my own server. I dabbled in and out of technology, coding, etc. Mostly for the sake of reaching a goal - of which are related to my creative and filmmaking endeavors.

Now, back to Tailwind. The title pertains to my initial thought about it. Since the current level of complexities of my websites are very low, my initial thought about it is that it needlessly clutters my html. Though it does make for less going back and forth between html and css files, I found myself struggling to make things work instead of just jumping on ahead and doing things from scratch using CSS. A lot of experienced developers did mention that at first Tailwind can be an annoying piece of sh*t but in time they also realize the enjoyment and the fun of not having to think about creating new styles and classes that Tailwind offers without the extra fuss.

My philosophy in life is that I like things modular in a sense that my items as much as possible are separated in terms of their functionalities. I'm still hanging on to that idea in my head wherein HTML files are for structure and CSS files are for styling. I do realize that there is space for meshing these files together when I found myself watching a tutorial on React.JS the other day. I know I will always find a coherence between technologies and hopefully one day I will find comfort in a bit of chaos if it means that I will find deployment of my projects faster. That way I can make changes and improvements faster. I think Tailwind can be a huge pain in the a** but another milestone for my resume isn't going to hurt (I also recently read that Tailwind works great with ReactJS, which I'm currently learning right now). I think I'm perfectly fine knowing it exists and that should the need arise I shall be ready to use it much like Bootstrap. 

 

Kai Javier

Sometimes I wonder what if we can all truly tap our potential? What if you're not hindered by societal limitations? What if you can do anything you always wanted to do?

Whenever I talk to people of different races and foreigners that know very little of my country, my horizons widen and my opportunities open up. They get to know more about what I have to offer beyond what is written and shown in popular media.

As a Filipino, I'm so used to the fact that Filipinos are consistently hindered by so many responsibilities and limitations, from poverty to cultural issues. I refuse to be limited due to my nationality and what other people write about Filipinos. Talent shouldn't be limited by region or race or stereotypes. The future is global.