Git troubleshooting flowchart
-
What if I want a similarly-easy RCS? Where do I find that?
src.bak
src.bak.2
src.bak.9-5-14
-
-
Refuse Combustion Starter
-
This is a cool concept but probably needs additional rules (perhaps using a Markov chain) to be interesting.
-
It's always been Revision Control System. I missed the memo where it changed to a VCS. V = Versioning? I guess?
-
For what it's worth, I use VCS as the generic term, leaving RCS as the name of a specific piece of software that was the predecessor and base for CVS.
-
Things are as they are only because people like you want them to remain as they are. Personally, I don't think anybody-- anybody on Earth-- should be excluded from participation in software development.
Well, that makes one of us. I, for one, heartily dislike people who write viruses, malware and anything related to it. I wish they didn't and hope they find some other hobby they could do, that would bother fewer people.
@toon said:
So every book ever written should use one syllable words and pretty pictures of cheerful anthropomorphic animals, because some other books do and those are easier to read!
If I want to read a book like that, they exist. I can go to the bookstore and find thousands of them.
Yes, and precisely none of them will be about software development, because the authors of books about software development expect their audience to be able to read words of more than one syllable.
-
A disability like that would also make programming difficult. Seems like a pretty good reason to me?
/me Gets popcorn. This should be fun!
-
-
Disappointed. Expected major Blakeyrant™. Needs all-caps and swearing. 5/10.
Personally, I don't think anybody-- anybody on Earth-- should be excluded from participation in software development.
Really? How about stupid people? How about people as stupid as Nagesh (or as it pretends to be)? Or people that can't comprehend the difference between a computer and a monitor? Do you really want to enable them to write software?
-
But that's really the essence of a good BlakeyrantTM: a statement that's so far off base that it throws into doubt anything else the person has to say.
-
Really?
Yes.
How about stupid people?
From my experience, people software developers label as "stupid" are usually quite smart. So yes.
How about people as stupid as Nagesh (or as it pretends to be)?
I like Nagesh. So yes.
Or people that can't comprehend the difference between a computer and a monitor?
Sure why not.
Do you really want to enable them to write software?
Yes.
-
-
How about Jeff Atwood?
-
How about Jeff Atwood?
Yes, but I'm extremely disappointed that anybody would pay money for the resulting software. Or volunteer their time to help it along.
-
How about the people behind Tigermouse?
-
Yes, damnit, stop asking.
-
Really? How about stupid people? How about people as stupid as Nagesh (or as it pretends to be)? Or people that can't comprehend the difference between a computer and a monitor? Do you really want to enable them to write software?
The development of Lotus Notes must continue!
-
The best thing about software development is that anyone can attempt to learn it. They can grab a tutorial, install an interpreter or a compiler, and get going. A lot of people don't deserve to get paid to produce software, but that's exactly the sort of thing the market's supposed to weed out; the easier it is for the guy in charge of hiring to learn a little development in his spare time, the more likely it is he won't hire people who are full of shit and can't code. Since every generation is more computer-literate than the last, over time, we should see the industry's standards for what makes a good programmer rising on their own.
So for once I wholeheartedly agree with @blakeyrat: Everyone should be allowed to participate in software development.
-
So for once I wholeheartedly agree with @blakeyrat: Everyone should be allowed to participate in software development.
It's just like construction or cooking or whatever. Make it easier to do because it is something that any and everyone should be able to get in on.
-
It's just like construction or cooking or whatever. Make it easier to do because it is something that any and everyone should be able to get in on.
But that still doesn't make everyone an architect or a chef.
While VCS tools can definitely be improved, we're a lot better than we used to be. We don't do global locking any more (it was tried and found to be awful when someone goes away for a couple of weeks leaving everything locked “because that's how he worked”). We have actually fairly reasonable tools for examining the histories of committed artefacts. Many IDEs integrate with the underlying VCS tools; we can argue about the quality of the integration, but for many developers that makes getting going quite a lot easier.
Not everything is easy, and sometimes can't be easy. (Deciding how to resolve conflicts between how two developers altered a file can be really hard, even for smart and wise people, and we shouldn't kid ourselves into thinking that programs can get it right for us automatically all the time.) But the grind of actually identifying what particular configurations look like, conveying those to others, and enabling comparisons between them — the core of what all VCSes do — is now a pretty thoroughly understood problem. We get to concentrate on higher-order problems than that…
-
/There has to be some thing here to prevent those Boxes of touching each other in an unholy manner. An empty line is obviously not enough/
<!-- I find that an HTML comment works well -->
-
Yes, but I'm extremely disappointed that anybody would pay money for the resulting software. Or volunteer their time to help it along.
It's mostly because those of us who continue to 'help' (read: not me but others in this community) realise we are stuck with this POS but want to make it so that participating in this awesome community is at least less painful than it has been.
-
Part of the craft of software development is to make your programs accessible and usable. I would argue that's the most important part of the craft.
You also have to get the underlying systems right, especially for something like a VCS where the data (the managed source code) is the whole damn point.
It's like in a house: while yes, it is important to get the lighting and door hinges right, if the foundations are bad, the house isn't going to be valuable to anyone for very long. Claiming that the specialist foundation builders should stop that and focus on positioning of the lightbulbs will earn you a shit load of scorn.
Alas, git was mostly designed by a foundation builder. Who wasn't even that good at that either, not at the scale of a house. (Git sometimes loses your data, which is just about the worst of the worst for a VCS. All that pain you went through in the past? Be prepared to do it again…)
-
<!-- I find that an HTML comment works well -->
Yeah but that wouldn't have been visible now would it. And that would have robbed me of a jab at how Discourse mangles his own damn feature
-
It wouldn't have robbed you of that jab. It would have robbed you of some of the sympathy from it, though (except from those who quote your posts)
-
Just 5 years ago, in a company with a large dev team - yes, we were using Visual Studio with VSS.
TFS existed - and was even set up on our servers but the tech lead was NOT interested in TFS.
VSS is what he knew, so it was what we had. And god forbid that anyone might go on holiday with a file or two locked.
I think they have now mostly shifted to TFS. At least, I hope so. I also hope that they no longer have VB.NET projects running, but that is probably just dreaming.
-
Thank whatever gods you believe in that you have not been exposed to SharePoint. Thank them fervently.
It fucking sucks giant festering dog-cocks.
-
He's ranted at length on that specific subject.. have a look in the old forums.
-
Old forums are a barrier to abusing Discourse. And I was struggling to think of ways to spam mention him without just blatantly doing it. I already figured he'd hate JIRA like I do. Or worse.
-
-
-
-
[spoiler]Remedy ARS.[/spoiler]
I try not to think about it.(The new SourceForge bug trackers are pretty bad too.)
-
Does your company use JIRA for completely non-software related activities like setting up workflows for things to be approved by people?
For example one time I needed to get sign-off for something and the entire hierarchy of people for whom I had to get approval - for non software practices, but for lending lots of money - was all orchestrated via JIRA.
-
Does your company use JIRA for completely non-software related activities like setting up workflows for things to be approved by people?
That's not a good reason to hate JIRA, though. I use it day to day, and it's pretty decent at being a bug tracker.
[spoiler]Remedy ARS.[/spoiler]
I try not to think about it.(The new SourceForge bug trackers are pretty bad too.)
FAIL
<read the raw>
-
Oh, that in itself is not a good reason to hate JIRA. There is so much more but I've repressed the memories.
Thankfully my former employer is no longer in business. You might have heard of them, and even though I was only employed at a subsidiary, the bullshit corporate culture infected us too.
-
Does your company use JIRA for completely non-software related activities like setting up workflows for things to be approved by people?
I work at a university. We're only completely uptight about money; many other working practices are closer to “if stuff is sorted out on time, we're cool”.I work developing workflow systems. I know how bad these things can get.
#However…
Our IT department uses a bug tracker for booking leave. With the form for doing it created by a summer student rather more years ago than anyone remembers. It's not that nobody could improve it, it's that any time someone proposed doing so, IT management and the (clerical) admin office screamed that it shouldn't be touched, despite it being grossly broken in just about every way you can imagine. (The gossip is that we're going to get rid of it. At. Last. Well, maybe. If the secretaries don't go on strike over it or something…)
-
