Live data from Hacker News

How to end up with 500k commits in your log

arp242.net

21–30 of 59 posts

Re: How to end up with 500k commits in your log

#21
post #11

I have this rails app that behaves really weird on Heroku, where every build fails the first time. So I have a comment "Commit comment" in my html that I adjust a capitalization on then push again. Works 100% of the time I expect to end up in the 500k commits club

Reminds me of another part of OP:

> No one liked how any of this worked, but just accepted it as a fact of life, like how you would accept that it really sucks that it rains today. That’s an attitude I’ve seen more often and never really understood: if I see something that’s really awkward, frustrating, and time-consuming then I want to fix it, but a lot of people seem happy to just and accept it.

Re: How to end up with 500k commits in your log

#22
I won’t lie, I keep using commits as the equivalent to saving, and hence have many commits on my GitHub Profile (2,000 in the last year - many for me, I guess some have much more).

At some point I got addicted to the number, so from time to time I try to manually increase my frequency of commits.

All that said, I end up doing more commits when working on front end stuff, when I doing back end programming, I am not at all interested in saving / committing frequently as I’m focused on the task at hand. With front end stuff, you necessarily need to save and refresh the webpage in your development browser, so it goes hand in hand with increasing my commits :-)

Re: How to end up with 500k commits in your log

#23
post #11

I have this rails app that behaves really weird on Heroku, where every build fails the first time. So I have a comment "Commit comment" in my html that I adjust a capitalization on then push again. Works 100% of the time I expect to end up in the 500k commits club

And yet our field is called Software « Engineering ».

Re: How to end up with 500k commits in your log

#24
post #12
post #5

It'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.

why bother with a message if it's just garbage?

I use 'wip' (work in progress) and it makes it easy to find those save my work commits.

Re: How to end up with 500k commits in your log

#25
post #19

Earlier quoted context omitted.

Someone above mentioned: git commit --amend --allow-empty

--allow-empty refers to the changeset [1]. You still need a message. [1] To be precise, it allows to create a commit that has the same tree as the parent commit.

That can be fixed by using “EDITOR=true git commit --amend --allow-empty”

Re: How to end up with 500k commits in your log

#26
post #11

I have this rails app that behaves really weird on Heroku, where every build fails the first time. So I have a comment "Commit comment" in my html that I adjust a capitalization on then push again. Works 100% of the time I expect to end up in the 500k commits club

Reminds me of another part of OP: > No one liked how any of this worked, but just accepted it as a fact of life, like how you would accept that it really sucks that it rains today. That’s an attitude I’ve seen more often and never really understood: if I see something that’s really awkward, frustrating, and time-consuming then I want to fix it, but a lot of people seem happy to just and accept it.

I think it’s more like « this place is full of smart people that knows this is shit so if nobody fixed it already, it must be hard to fix ».

And since this is a shared behavior, even your potential fix can be hard to get reviewed because everyone will be afraid of the potential side effects because nobody understands why it even worked like this.

Re: How to end up with 500k commits in your log

#27
post #14
post #4

Earlier quoted context omitted.

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.

Hey now, it's just branch prediction !

You should get into marketing!

Re: How to end up with 500k commits in your log

#28
This is a good opportunity for me to ask something I've been wondering for a while about what is appropriate to put on a blog tied to your real identity.

The majority of this article could be seen as negative toward the author's former employer. The website is also listed on the author's CV, and knowing the author's name it is easy to find the website. Is there the possibility that this is seen as unprofessional, or that someone who was involved might read it and be upset? Maybe it is okay because the company is defunct (I assume), or because it was so long ago?

I ask because I am early in my career and I just finished a job where the majority of the things I learned were non-technical in nature. I would like to write about the lessons learned but, like this article, it would have some component of criticism about the company. Like the author, my website is on my resume and the website can be found by searching online for my name. Someone reading my resume could figure out what company I'm talking about, and some people who work there might find it. I don't live in a large tech hub in the US so it's very likely a future potential employer knows some people personally that I might have criticized vaguely (but due to process of elimination from the jobs listed on my resume wouldn't be hard to identify).

The advice I've been given from people I know is to either not have a website tied to your identity at all, or be as professional as possible if it is tied to your identity.

What do you think? If you knew this author, or it you stumbled across this article because you are thinking of hiring the author, how would you feel?

Re: How to end up with 500k commits in your log

#29
post #28

This is a good opportunity for me to ask something I've been wondering for a while about what is appropriate to put on a blog tied to your real identity. The majority of this article could be seen as negative toward the author's former employer. The website is also listed on the author's CV, and knowing the author's name it is easy to find the website. Is there the possibility that this is seen as unprofessional, or…

You should speak truth regardless of what others think. You'll get more respect even if you ruffle a few feathers.

Re: How to end up with 500k commits in your log

#30
post #28

This is a good opportunity for me to ask something I've been wondering for a while about what is appropriate to put on a blog tied to your real identity. The majority of this article could be seen as negative toward the author's former employer. The website is also listed on the author's CV, and knowing the author's name it is easy to find the website. Is there the possibility that this is seen as unprofessional, or…

I personally wouldn't, but everybody has to decide for themselves.

I at least know a few companies that would avoid hiring people who criticize old employers, afraid they will be next. I mean, most companies have at least some "skeletons in the closet" of bad practices or what not.

Having said that I'm usually brutally honest in job interviews, I see it as my way of screening companies, if they don't want the honest me, then I would probably not fit the company culture anyway. So there might be nothing wrong with having an honest blog in the end, maybe you receive less offers, but the offers match you more.

Post reply on HN