Live data from Hacker News

How to end up with 500k commits in your log

arp242.net

51–59 of 59 posts

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

#51

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…

Just use (feature-)branches.

You can commit every single character if you in the mood. At the end, when your new feature is complete, you just squash all commits in this branch to one single commit ("add feature xyz") and merge/rebase it to your main dev branch.

Now it is really easy to identify the actual code behind a new feature.

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

#54
This is a truly bizarre article. The practice he is outlining here is wild, no reasonable company would do this. Lots of companies however end up with bizarre and dumb build systems for reasons of history, but this one is the strangest I have ever heard of. Even just reading the article I cannot really come away with a sense of how or why they did this and it is so strange that my brain doesn't wanna accept that it existed.

However, it's also bizarre because it seems to not just contain an explanation of this weird tech but a lot of vitriol. This guy seems to have outlined what was a dysfunctional place where a lot of junior people got a nice start to their career. This doesn't seem to me to be a good reason to badmouth the place. You as a senior engineer should be helping people to be better coders, not shitting on them for being junior developers. (And yes the owner was bad but that's no reason to shit on the juniors!)

I think if I were interviewing this guy and saw this piece I would immediately slam then Strong No Hire button.

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

#55

Earlier quoted context omitted.

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

Musing about how you used to call your employer like the failed painter from Austria is a bridge further than ‘ruffling a few feathers’.

Unless it's true.

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

#56
post #50

Earlier quoted context omitted.

> > The value for the customers was that was in Dutch, with Dutch support (it didn’t even support English > Or people just want to do the work in their mother tongue instead of a foreign language These two sentences mean the same thing. While sometimes people say “or X” to reword X I don’t see why you’d do that. It’s clear as it is.

Yes, I am aware of that. Just wanted to express my opinion. For example, Netflix is doing a bad job at providing Dutch subtitles. Barely any tv show has Dutch subtitles. Disney+ does a much better job.

I always though it was strange than Dutch completely embrace English in Netherlands but Flemish make everything they can to not speak French in Belgium. We can wonder if dutch will be spoken only in Belgium at some point in the future.

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

#57
post #25

Earlier quoted context omitted.

--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”

The default message is empty though, so not editing it will abort the commit.

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

#58
post #56
post #50

Earlier quoted context omitted.

Yes, I am aware of that. Just wanted to express my opinion. For example, Netflix is doing a bad job at providing Dutch subtitles. Barely any tv show has Dutch subtitles. Disney+ does a much better job.

I always though it was strange than Dutch completely embrace English in Netherlands but Flemish make everything they can to not speak French in Belgium. We can wonder if dutch will be spoken only in Belgium at some point in the future.

Eh, it's just a few loanwords. The language isn't going extinct any time soon. There are many loanwords from French and German already.

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

#59
post #32

> One of their websites was a “website builder”, like Geocities, except worse. The value for the customers was that was in Dutch, with Dutch support (it didn’t even support English.[2] Shortly before I joined they decided to rewrite it from scratch (which in this case was probably the right decision by the way). Or people just want to do the work in their mother tongue instead of a foreign language. Personally, it's…

I don't think the article is dismissing the value of internationalization. As the endnote says: > People often seem dismissive of that value i18n, “everyone speaks English” Well, depends on who your customer base is. Even in the Netherlands where almost everyone speaks some English there are still loads of people who are not especially good at it and much more comfortable with Dutch. This is probably over half the po…

Here in Amsterdam there's probably more people who don't speak Dutch than there are people who don't speak English.

Heck, I've worked at companies where over 50% of the employees did not speak Dutch at all.

So English will reach a wider audience in Amsterdam, ironically. Not sure how well this applies to the rest of the Netherlands (especially outside Randstad).

Post reply on HN