The amount of damage GitHub has done to development literacy in the general population is fucking awful

Tip: you should never file a bug on if you have a question or comment. Start at the -users or -discuss mailing list first.

@deavmi @sir You're probably an outlier. Folks in my uni literally cannot differentiate between git and GitHub—and can't think beyond the fork/PR workflow.

But ditch that, there's an even worse crowd who think GitHub is like… DeviantArt but for their code. They "upload" code to GitHub (they don't care for proper commit messages, they just use the web UI), in hopes that a recruiter thinks their resume-padding React todo app is worthwhile.

@sir @x @deavmi this is not a fault of github. just increasing illiteracy.

@iron_bug @sir @x I mean you can still write fine commit messages with the web UI.

I am actually guilty of the above because @sir wasn't specific about it till @x made some remarks on what constituted bad dev habbits

@deavmi @iron_bug @sir I'd say it's less of a "bad dev habit" and more of how software development is perceived by the average guy. And these early impressions are hard to shake off.

Source: I work with people who think the way I described in my earlier toot. And it's not fun.

@x @iron_bug @sir I guess it depends on the person.

Most of my friends - whenever they make such mistakes - if they are attentive and you correct them then they learn.

It depends person to person I guess. So yeah.

@x @sir I can understand how that rubs off a bad development habit - yes.

@sir I feel like IDE's and text editor plugins did their fair share with their commit-everything-without-looking GUI.

Any time anyone asks for tips on how to get better at git all i ask is that they use the CLI and add changes one by one, e.g. with git add -p, because that's like 80% of the way to decent git usage.

@rune While I mostly agree, git add -p is a double-edged sword. You're essentially committing a state that never existed, and was never tested. As with many such tools, with great power comes great responsibility.

@vifon you don't have to push your changes as soon as you commit them, though.

You can commit it, then stash anything else, and run your tests.

Managing code in git requires care. Either by you or by whoever is cleaning up the code later.

@rune By all means. And too many people treat Git—or rather version control in general—as an afterthought.

@rune @vifon Is "you have to mind the details yourself" a bug or a feature?

I think the root issue is most people aren't interested in learning the theory behind a tool before trying to make use of it, and I'd posit it's a natural extension of the instant gratification culture that's so prevalent today. The software choices that exhibit that sort of thinking are more a symptom than the cause.

@sir Merge commits. By default, used to not even have an option. I hate merge commits.

@sir There's an interesting relationship that's been exposed in secondary education statistics inthe US since roughly 1950, when high-school attainment neared 90%.

Graduation percentages, or academic levels, could be increased. Very rarely both, and if so, almost always for reasons exogenous to the educational system: greater socioeconomic equality, reduced pollution (especially lead and particulates), general health.

Skills are unevenly distributed. Greater access will lower the mean.

See also Robert Wood Krutch: a bad road is a good filter.

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!