You're viewing a single thread.
Removed double quotes, added single quotes
50 1 Replysomeone later on -m "removed single quotes, added double quotes"
35 0 ReplyMore commits == More money!!!
19 0 ReplyReal talk: I have worked at a company where an exec briefly had the bright idea to rank developers on number of commits made.
You can imagine how that turned out.
He wasn’t an exec for very long.
7 0 Replylmaoo, I can't believe someone actually did that and was serious about it.
I'm already imagining commits piling up with comments like:- "add a newline"
- "move function up"
- "rename variable
users
touser_list
" - "Revert previous commit"
- "no John, it's
user_list
and that's it, don't you dare change it again"
He wasn’t an exec for very long.
Good riddance I guess
3 0 ReplyOh, no, we can do better.
Every single line of every single PR is an individual commit. And never squash-commit.
5 0 ReplyTalk about atomic commits
2 0 ReplyIf you really want to nuke it from orbit: do it for every character.
It is absolutely technically feasible to go further than that, but I think that’s the point of diminishing returns in terms of effort.
2 0 ReplyHah, I knew it would come to that
but I think that’s the point of diminishing returns in terms of effort
Not if you make another application to automatically split commits in that way... application which will need its own commits, it's never-ending
1 0 Reply
Why do u prefer single quotes?
2 0 ReplyNot Shall330, but double quotes can imply variables in the string in some languages.
4 0 ReplyWhich languages are these?
2 0 ReplyPHP for one. "$x" will interpret the variable $x. '$x' does not.
5 0 ReplyWell there's ya problem ur using php.
2 1 ReplyAlso bash
4 0 ReplyAnd Perl.
2 0 Reply
I have no preference! It was to do with Spring/yaml config and some really strange conflict which required the use of single quotes. I'm still a total noob in the world of software dev, so I wouldn't be able to explain why it worked 🤣
3 0 Reply