4 ms·
“minimal viable knowledge" describes my git knowledge. I simple don't have time to become a git expert. After all git is only a source control tool, there are w
by spaetzleesser 5y ago
“minimal viable knowledge" describes my git knowledge. I simple don't have time to become a git expert. After all git is only a source control tool, there are way more important things to deal with that impact our customers.
- CRConrad 5y ago> “minimal viable knowledge" describes my git knowledge. I simple don't have time to become a git expert. Isn't there some middle ground between "minimal viable" and "expert" that you could (should) aspire to, like "reasonably competent"?
- spaetzleesser 5y agoI think I am reasonably competent to do my job. I just don’t think there is much value in learning more. It’s just a version control system.
- CRConrad 5y ago> I just don’t think there is much value in learning more. It’s just a version control system. I think it's not a matter of "just" a version control system; it's vital enough to (most of) our jobs that being more than just "minimally viable" good at it is an integral part of being reasonably competent. But who am I to talk; at work, I almost exclusively use Informatica's built-in "version control system", which IMO... isn't much of one; actually, hardly is one in the first place. Getting to use git (or similar) again is what Idream of. Then again, maybe that just means I'm only "minimally viable" with Informatica's system. :-) (All out of Spätzle, have to wait for next "Alpenfest" week at Lidl. :-( )