I’ve build entire databases/management tools out of Excel with following of administrative file completion, warning of due payment and KPIs. It was a pain to build but it kinda worked. Then I learn to build actual relational database and I went on rebuilding them on PostgreSQL… as a back, using Acess as front that would allow Excel-like usage and Excel export of the request response.
We can say what we want about Excel but it is working really well and people are already formed to use it or at least they are enough familiar with it so they are not nearly as frighten by the idea of learning Excel as they are to learn to read a single-table SELECT SQL statement.
It does sometimes happen that something in there just breaks and isn’t easy to recover. But it can also be a matter of (inexperienced) devs just deciding, fuck it, I won’t try to merge it, I’ll just copy my changes elsewhere and throw away the repo.
I have never had git get into a state I cannot get out of. Even if that is a reset, checkout or clean. And those are very rare. How are people breaking things so often.
Learn the tools you use daily, it saves you a lot of headache in thelong term.
Oh yeah, but I’m talking about the internal Git state just genuinely being broken, for example: stackoverflow.com/…/git-commit-stopped-working-er…
Ultimately, if you spend half an hour debugging that, it just starts being a waste of time compared to cloning anew.
As for how to merge, yes, one should learn that. The problem is that the complexity of the code changes adds on top of whatever insecurities you might still have with Git.
I did put “inexperienced” in braces there, because even as an experienced dev, merges are sometimes just not worth doing. In that case, you could just checkout the branch a second time, but well, still not that different.
That should not break things though. Maybe get a merge conflict that you need to sortout at worst. This is essentially the constant state of working with other people on a project.
But it can also be a matter of (inexperienced) devs just deciding, fuck it, I won’t try to merge it, I’ll just copy my changes elsewhere and throw away the repo.
Pretty sure that’s actually it. Git has a learning curve and, for example, some naive rebase not working out as intended can be scary if you don’t know what you’re doing.
I’ve been doing this yesterday. Not because Git broke, but since Intellij kept pulling invalid configs from the cache, and that was based on some kind of path identifier it seemed.
People inexperienced with git can get stuck after doing some funky checkout / rebase stuff. If you don’t know your way around git so well, I guess this is the obvious solution.
My dad does this, and I made a few bucks thanks to WordPress. Really, more thanks to Elementor because you can make a pretty snazzy website for cheap and the layman has no it took 2 hours to put together with templates. Lol
programmer_humor
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.