My thoughts about software engineering evangelism best practices
It is mostly about stuff like SOLID having 10s of interpretations and confusing principles that require years of xp to make sense (you realize that they're just poorly written)
This is funny because in PR oriented development I started treating commits in the same way as "save" in IDE,
it's just backup of current state with irrelevant commit message. Everything is described at the end of the work in PR's description and squash merged.
>The latter is ahead in network effects in a massive way - but I always preferred Mercurial. I'd have used it more but - network effects! - used git because of the projects I was working on.
I've recently wrote a post about it - how we're kinda locked with git and how other solutions have it hard to get adoption.
git was good, but github cemented git's position. So unless GitHub allows other solutions, then we're kinda locked.
>So what's the issue here? I'm worried that just because GitHub is so good, then unless they decouple from git as letters management engine and allow any/other, then we will be locked with git.
>It's been about a decade since git "won" the version control war due to the (yet another) unjustified tech hype wave
Hah, I've recently wrote a post about similar issue - why we may be locked with git.
>So what's the issue here? I'm worried that just because GitHub is so good, then unless they decouple from git as letters management engine and allow any/other, then we will be locked with git.
It is mostly about stuff like SOLID having 10s of interpretations and confusing principles that require years of xp to make sense (you realize that they're just poorly written)