Professionally, I've used git, perforce and PlasticSCM. Personally, I've also used SVN and Mercurial. (I also toyed with pijul's claims of being fast). I think Perforce sucks in many ways, but I think it's objectively a better tool than git. Centralized, immutable history, atomic incrementing change numbers are superior (IMO) to a decentralised, signed, hash based model. I think git's branches are a superpower, and the PR-style workflow in github is objectively superior to whatever trash P4 has put out there.
CI Tools - I've used Jenkins, TeamCity, GH Actions, Buildkite and Electric Commander. I strongly prefer Buildkite over all of the others. It strikes the right balance between Jenkins and GH Actions, mostly by avoiding a bunch of the "legacy" that comes with Jenkins.
"Programming Languages" - This is a spicy one. I flip-flop between C++, Kotlin and Go these days depending on the task. Despite the warts, I really really like go. It's a statically typed language, built in (and opinionated) package manager, wicked fast compile times, an order of magnitude faster runtimes than python, OOTB cross compilation support for full statically linked binaries, (and it has a jetbrains IDE). I wish it had _some_ extra features (sum types, real enums, and a slightly wider range of the basics in the standard library), but overall I'm very happy with it!
When I was a college student just starting my CS journey, I happened to bump into one of the founders of Perforce at an unrelated event I was attending. After chatting a bit, I asked him what he did, and he replied "These days, not much". "Oh, retired early? What did you do before?" "Well, you know version control software?" "Like Git?" And I'll never forget the the defeated sigh the guy responded with.
Indeed, and it's useful. But, (and this is the most important part), it's a role based feature, not "standard day to day workflow", and it doesn't require everyone to handle as part of their mental model
A force push on a git repo is pain for everyone involved
Professionally, I've used git, perforce and PlasticSCM. Personally, I've also used SVN and Mercurial. (I also toyed with pijul's claims of being fast). I think Perforce sucks in many ways, but I think it's objectively a better tool than git. Centralized, immutable history, atomic incrementing change numbers are superior (IMO) to a decentralised, signed, hash based model. I think git's branches are a superpower, and the PR-style workflow in github is objectively superior to whatever trash P4 has put out there.
CI Tools - I've used Jenkins, TeamCity, GH Actions, Buildkite and Electric Commander. I strongly prefer Buildkite over all of the others. It strikes the right balance between Jenkins and GH Actions, mostly by avoiding a bunch of the "legacy" that comes with Jenkins.
"Programming Languages" - This is a spicy one. I flip-flop between C++, Kotlin and Go these days depending on the task. Despite the warts, I really really like go. It's a statically typed language, built in (and opinionated) package manager, wicked fast compile times, an order of magnitude faster runtimes than python, OOTB cross compilation support for full statically linked binaries, (and it has a jetbrains IDE). I wish it had _some_ extra features (sum types, real enums, and a slightly wider range of the basics in the standard library), but overall I'm very happy with it!