jackofalltrades

I am currently trying to keep track of my config files in a repo to be able to get the configa back together easily if/when I change distro, but I am not sure if that's the best way or if I should be using some tool to help me since I some programs keep preferences in other directories other then $HOME (at least I think so). Can you guys share with me your must used/trusted simple process for this?

Thank you and specially thanks to everyone who is being helpful in this community for the past few weeks, I've learned much and got some very useful tips from the comments in my posts and in other people posts too.

I am fairly familiar with Linux, I've been using different distros for some years now and have done some config editing here and there. I am also a web developer and use the terminal quite a lot and so I always stumble on people's recommendation to use tmux and how good it is, but I never really understood what it does and, in layman's terms, how can it be useful and for what use cases.

Can you guys please enlight me a bit on this?

Thank you.

Edit: if my phrasing is a bit awkward or confusing I apologize since I am not an English native speaker. (Maybe that's why I never fully grasped what tmux is from other explanations xD)

Edite: Ok, just to clarify, my original struggle was to understand what made tmux different from using some terminal app and just split the screen xD

Pretty much the title. Where's the hate towards Manjaro coming from? I was pretty much a Ubuntu/Fedora user for years but never got too technical. Used almost always gnome, but recently got interested in tiling wm and have done some searches and stumbled upon the Manjaro Sway edition and everything works quite well, but I keep seeing people bashing on Manjaro and I don't know exactly why. So if I were to use sway in Arch or Arco (way friendlier to install) if there any simple way to replicate the makeup sway default configuration?

Thank you all for your time.

So, I've been promoted to Senior Engineer in the last couple of months and that felt really good because I felt that people recognized my efforts to progress and that my dedication paid off. The problem is that, as a senior, I am supposed to become more part of the recruitment processes, through code review candidates applications, interviewing, etc. All fine by me, but sometimes I get haunted by the too familiar Imposter Syndrome when looking at the code submissions of some candidates for some of the challenges we ask them, I am supposed to be evaluating people that in some cases have (at my eyes) solutions that I would not be able to implement in such detail or finesse and some times I end up spending some hours going through some solutions just to grasp everything that a candidate has done. Am I an imposter or is this just another phase of the process?