People being dicks in Coding Help suck
-
BTW, I thought of another reason that the boss is right. When you leave for the day, the code may not be in a state where the tests pass or that it even compiles. If you commit in that state and don't rebase your output later, now you have broken commits in your history which will make bisecting and such more difficult later.
-
Or you could learn to use them properly.
You must be a practitioner of black magic? If blakey can't get it, it must be magic.
-
The appropriate term is "vidoo".
-
That's why I'm so amazed there's no solution to the problem!
So your boss is regularly complaining about too many commits to his entire IT staff? Or is everyone else at your workplace unprofessionaly ignorant about data security?
Do you actually read what people write here?
-
Do you actually read what people write here?
I feel qualified to answer that.
No. No he doesnt.
-
I wonder if there really are some useful points in these two threads. There might be.
Unfortunately Blakey has completely buried them in irrelevant vitriol, so they will never be found or solved.
Such a shame.
-
You are trying to use a tool in a manner it was never initially intended to be used in. (Using a CLI tool with a shoehorned GUI)
But mostly using VCS as backup software. That's been pointed out multiple times, but probably not enough.
-
I knew it would have it's own potential problems, but it sounded like it could have gotten rid of some of the existing ones.
There are no tradeoffs in blakeyland. It's all or nothing.
-
I probably can't work off the network drive because I know from experience that both Visual Studio and SQL Server have issues when told to work off network drives.
But you refuse to "push" your stuff to the network drive on your way home and insist on pushing to the remote repository to litter it with your incomplete changes.
Filed Under: Catching up is a barrier to posting without toasters
-
I thought of that later that day. If he is keeping his VS projects in any sort of sane place, chances are the sysadmins are backing it up anyway. At least for the companies that we work with, we automatically mirror a lot of folders to the server. (Desktop, Documents, Pictures, etc.) For most companies it is SOP because lots of
idiotspeople keep tons of important stuff on their desktop and not on network shares as they should.If VS projects are in the Documents folder, then they will be safe even if he gets hit by a bus. Or, more likely, run over by someone who knows him...
-
I'd be pissed, too, if some asswipe started mucking up my repository with nonsense commits like he's doing.
-
...and...who the fuck waits until exactly 5PM and then just stops everything they are doing and leaves? I have always found a good stopping point, usually after finishing some specific task and then commit, push and call it a day.
Or, just don't freaking worry about it because a half finished task will be worth fuck-all to whomever has to pick up the pieces after blakey's pieces are scraped off that bus. They are going to start over anyway.
-
...and...who the fuck waits until exactly 5PM and then just stops everything they are doing and leaves?
I don't have a problem with this. Stopping time is stopping time, however you determine it.
Or, just don't freaking worry about it because a half finished task will be worth fuck-all to whomever has to pick up the pieces after blakey's pieces are scraped off that bus.
It may or may not. But either way, it's not in condition to live in the repository. If it's worth backing up then back it up, by all means. Zipping it and emailing it to yourself is a better solution than this, though the email admins might disagree. I suppose you could just email a diff.
Really, the possibilities for process improvement are wide open.
-
I don't have a problem with this. Stopping time is stopping time, however you determine it.
I don't either, but somewhere a few minutes either way there has to be a useful commit message.
-
found a good stopping point
I often have tasks that take multiple days. It just depends on the magnitude of the changes.
-
I often have tasks that take multiple days. It just depends on the magnitude of the changes.
But are those so monolithic that there are no sub-tasks?
-
Depends.
A document of test cases half-converted to the new format is of no use to anyone.
One fully-documented feature out of a set is a whole different story.
-
Fair enough, but each one of those test cases is a sub-task to me. I find it unlikely that a Flintstones type alarm goes off and you would just stop typing in mid-line and fuck off for the day. ;)
-
For a format conversion? Nobody cares. If I get hit by a bus, they'll have bigger issues than the tests being in an older, slightly less efficient format.
TBH it's half an hour to the end of the day here and I doubt I'll get anything else done.
-
Nobody cares. If I get hit by a bus
We would care.
Well, blakey wouldn't. But the rest of us would miss your particular brand of banter.
-
I often have tasks that take multiple days. It just depends on the magnitude of the changes.
I'm sure that's true for most people. We just don't all misuse our VCS as backup software. That's what RAID-3 is for. Duh.
-
If I get hit by a bus
Who would take over your duties? Someone must provide tasty cupcakes! ;)
-
...and...who the fuck waits until exactly 5PM and then just stops everything they are doing and leaves?
Depends on how you commute and work. If you're a public transit person for instance, it can be "do I stop now at a place that isn't the best, or wait 30 minutes for the next bus"? Or "do I stop now at a nice place and twiddle my thumbs for 20 minutes waiting, or do I keep working even though I won't be at a good place to stop?"The other thing is this; I'm not sure that "good stopping place" for leaving is necessarily the same as "nice commit point." I read a quote from an author a while back, who said that (s)he tries to stop writing mid-sentence, because later it's easy to see what you were working on and you have more of a prodding towards your next step. I think the best programming analogue to this might be working in a TDD style, writing a failing test, and then leaving; but you can imagine other places to stop that are deliberately not a commit point. (And in the failing test case, other people having that test case if you get hit by a bus would be helpful.) I've done this a few times, and I actually rather like that way of working. The nature of my stuff precludes anything approaching true TDD for 99% of what I work on sadly, but as unsettling as leaving off in the middle of something is, I like it.
We just don't all misuse our VCS as backup software. That's what RAID-3 is for. Duh.
"RAID as backup" is arguably a bigger
than "VCS as backup", though maybe not for short-term stuff of the sort we're discussing here.
-
the rest of us would miss your particular brand of banter.
Considering the source* that might be the sweetest thing anyone ever said to me XD
* WTDWTF in general, not you particularly
-
writing a failing test, and then leaving;
I would not sleep well. That would drive me bonkers all night.
-
I read a quote from an author a while back, who said that (s)he tries to stop writing mid-sentence, because later it's easy to see what you were working on and you have more of a prodding towards your next step. I think the best programming analogue to this might be working in a TDD style, writing a failing test, and then leaving
Hrmm, sounds like it could be a good idea, will have to give it a try.
-
I'm sure that's true for most people. We just don't all misuse our VCS as backup software. That's what RAID-3 is for. Duh.
I'm pretty sure I'm going to be asked to put several GB of training videos into my VCS shortly, so I will no longer get to claim that.
-
-
@Yamikuronue said:
Nobody cares. If I get hit by a bus
We would care.
That would be sad. Unless someone caught it on video. Then I would be just on the positive side of ambivalent.
-
I read a quote from an author a while back, who said that (s)he tries to stop writing mid-sentence, because later it's easy to see what you were working on and you have more of a prodding towards your next step. I think the best programming analogue to this might be working in a TDD style, writing a failing test, and then leaving;
Oh that's really clever. Really, really clever. A big problem I have is "starting up" for the day. I nearly always try and finish "neatly" at end of day, and next morning have to start afresh which can take me an hour or two of coffee and web, which is really bad. Having a busted thing to jump straight into sounds like a really good idea. I'm going to try that from now on!
-
Having a busted thing to jump straight into sounds like a really good idea.
The "downside" to this is that I tend to keep thinking about the problem. Not necessarily so much that it keeps me awake or anything, but still.
-
And this is the reason why your employer should get you an external hard drive and set up some proper backup solution with it. I thought we had already covered this. Using the git server for your personal backups is just unprofessional.
-
I'm happy with the solution I'm using.
-
I probably can't work off the network drive because I know from experience that both Visual Studio and SQL Server have issues when told to work off network drives.
That's windows hardware for you. It's broken by design.
-
-
No. You're obviously not.
Be fair, it's really his boss who has a problem here. @blakeyrat is plenty happy to misuse his tools.
-
@Polygeekery said:
if you shit all over those who try to help you, do not expect good help
Funny, that's what blakey said to @wood...
Which is why I rely on no one but myself. But even he can't be relied on sometimes.
-
Theoretically speaking, if your primary concern were the company not losing your work if you got hit by a bus, then a daily backup before going home, that other people knew about, would get rid of the need for a superfluous commit.
Using whatever corporate-approved tool does the same job as Dropbox, to sync the laptop's own working folder and git repo somewhere that gets centrally backed up, would work as well.
Separating the backup concern from the VCS concern lets you keep the authoritative central VCS as tidy as corporate policy dictates, while giving devs the freedom to run their local VCS however they damn well please.
