HN user

itzami

3 karma

I'm a self-taught front-end developer with a knack for design and a Master's Degree in Psychology

Posts8
Comments9
View on HN

i apologize for my heresy on doing this!

i'm actually swinging into two different approaches for my tmux panes and none of them conform to what tmux expects (again, i'm sorry for that!)

i miss kitty's way of doing stuff so i had to make some sense out of tmux and ghostty to make the change less brutal! i also suck at remembering keybinds

my other approach is, on doing `cmd+enter` running the following script https://gist.github.com/ItzaMi/d8da1e779d05ce40a66ed75ddeae2...

this allows me to create panes just the way i want while only having to remember one keybind (which was already the one i used for kitty!)

i guess this means i find my layouts very precious!

Historically, we avoided this to maintain a separation of concerns, but it's puzzling why some prefer reintroducing similar methods. Is it just to save a few keystrokes?

In bigger projects, if we start looking at the amount of files one has to deal with, Tailwind becomes very appealing. We've went through the regular `.css` route but then you have weird names, and, potentially, duplications or even conflicts. `css modules` is an option but you've now essentially duplicating the number of files that you have for each component / page. `sass` or `less` essentially bring the problems from `css modules` and regular `.css` into one.

I don't inherently like or dislike Tailwind (although I very much started by absolutely disliking it) but you feel its value in a project with 200+ files composed of components and pages

I did but I've been feeling that the LLMs end up giving an average solution / something that I don't fully understand / the same solution that just looks slightly different and I think I'll end up getting influenced by its responses instead of thinking by myself or learning from others