How to end up with 500k commits in your log
1–10 of 59 posts
Re: How to end up with 500k commits in your log
#2"A lot of times the concerts weren’t sold out at all, but we pretended it was. It was just a lie. Pretty much 100% of our traffic came in through AdWords, people would search “Something-something concerts tickets”, got an ad from us, and be duped in to buying them at ridiculous prices."
Sounds very scummy.
Re: How to end up with 500k commits in your log
#3"A lot of times the concerts weren’t sold out at all, but we pretended it was. It was just a lie. Pretty much 100% of our traffic came in through AdWords, people would search “Something-something concerts tickets”, got an ad from us, and be duped in to buying them at ridiculous prices." Sounds very scummy.
Google censors YouTube in the name of protecting people from their own stupidity, meanwhile profiting from the same phenomena through AdWords.
Re: How to end up with 500k commits in your log
#4"A lot of times the concerts weren’t sold out at all, but we pretended it was. It was just a lie. Pretty much 100% of our traffic came in through AdWords, people would search “Something-something concerts tickets”, got an ad from us, and be duped in to buying them at ridiculous prices." Sounds very scummy.
It gets worse
> At one point I learned that one company we connected with would literally just invent concerts: they would guess “they’re probably doing a tour next year” and start “pre-selling” tickets for it at extraordinary prices.
Re: How to end up with 500k commits in your log
#5It's not hard. I use git add ., git commit -m "asdfghj", git push as my save. Exactly like I press Cmd+S in Photoshop all the time. So naturally I end up with a ridiculous amount of commits.
Re: How to end up with 500k commits in your log
#6"A lot of times the concerts weren’t sold out at all, but we pretended it was. It was just a lie. Pretty much 100% of our traffic came in through AdWords, people would search “Something-something concerts tickets”, got an ad from us, and be duped in to buying them at ridiculous prices." Sounds very scummy.
The author agrees
“I very much regret working on this First job, insecure about your career prospects and whether you’re able to get a new job, and it becomes easy to rationalize these things to yourself.”
Re: How to end up with 500k commits in your log
#7It's not hard. I use git add ., git commit -m "asdfghj", git push as my save. Exactly like I press Cmd+S in Photoshop all the time. So naturally I end up with a ridiculous amount of commits.
My principle has always been "commit early, commit often" and "push early, push often". This works well when you do your work in a branch and you only "squash and merge" into the main branch (even if you are the sole developer on the project).
Re: How to end up with 500k commits in your log
#8This reminds me of when I joined a company that used Dropbox for deployments. Install and configure Dropbox on each server, drop your updated files into Dropbox on your local computer, and boom — deployed. (Sometimes.)
Re: How to end up with 500k commits in your log
#9It's not hard. I use git add ., git commit -m "asdfghj", git push as my save. Exactly like I press Cmd+S in Photoshop all the time. So naturally I end up with a ridiculous amount of commits.
My principle has always been "commit early, commit often" and "push early, push often". This works well when you do your work in a branch and you only "squash and merge" into the main branch (even if you are the sole developer on the project).
Works extremely well indeed. Like git was basically made to be used like this. However, only because of that 'squash and merge' aka 'sculpt a nice history with the emphasis on story' bit. Not doing that is in my opinion and experience completely useless for code. As far as I'm concerned there's hardly any difference between one commit with message 'fixes' introducing a 1k loc diff code dump or 1000 commits introducing a one-line diff: a proper git history is a joy to work with when figuring out bugs and why/how things were done the way they are. Anything else is just mediocre at best, usually just worthless. Which I learned the hard way obviously.
Re: How to end up with 500k commits in your log
#10Quote: "Two people working on the same file at the same time was … unwise."
Yep, that one! That's the one that cracked me up, waking my wife from her afternoon nap :).