Starward Rogue Update 1.016: The Ricochet Sequel

[Misery]

At this point I dont know how in the world anyone is supposed to keep track of who did/made what in these.

The important thing is just to remember to say that it wasnt your content when something breaks.

[x4000]

Did you know, in svn there is actually a tool called the "blame" tool.  For any line of code, even, you can go and see who exactly touched it, and when, and what they did.  So you know where to point the finger.

I always thought that was a needlessly harsh way to name such a useful feature, haha.  In a big company I could see needing to go to Bob from 3 departments over and say "what does this MEAN???" about whatever feature, heh.

[ptarth]

The "personal responsible for this line of code, no matter how crappy or confusing it is" tool just didn't catch on for some reason.

Also, it is ALWAYS Misery's fault. Unless it was Craig's fault. Or Cinth's fault. They should really learn to check my code better before using it.

[Draco18s]

"Blame" is a harsh word, yeah. I saw a similar feature in Atlasian Source Tree during a contract I did over the new year.  Though it was commit based ("blame commit for..." kind of wording).

But at the same time I am unsure of a better word for it.

[Cinth]

Did you know, in svn there is actually a tool called the "blame" tool.  For any line of code, even, you can go and see who exactly touched it, and when, and what they did.  So you know where to point the finger.

I always thought that was a needlessly harsh way to name such a useful feature, haha.  In a big company I could see needing to go to Bob from 3 departments over and say "what does this MEAN???" about whatever feature, heh.

I actually used that to point out to Pepisolo that he uploaded something that was throwing XML errors all over the place.  I did kill the error first though. 

The "personal responsible for this line of code, no matter how crappy or confusing it is" tool just didn't catch on for some reason.

Also, it is ALWAYS Misery's fault. Unless it was Craig's fault. Or Cinth's fault. They should really learn to check my code better before using it.

Unless it's the reanimator boss that had naming conflicts written all over it, then it's your fault??   

If we ever [redacted] we'll have to [redacted] and deadly [redacted] real life zombies [redacted].

https://www.youtube.com/watch?v=HWfKdKWJEkM

Flashbacks!!!!

Flashbacks on the forum!  Flashbacks on the forum!!  That's it!!!  That's IT!!!!  I'm sick of these [redacted] flashbacks on this [redacted] forum!!
Of course I went there...how could I not?

The flashback I had wasn't a pleasant one.  It wasn't even forums related :/



I like how this thread went from me ribbing Chris to assigning blame through SVN in like 3 hours time.  So much derail

[crazyroosterman]

Did you know, in svn there is actually a tool called the "blame" tool.  For any line of code, even, you can go and see who exactly touched it, and when, and what they did.  So you know where to point the finger.

I always thought that was a needlessly harsh way to name such a useful feature, haha.  In a big company I could see needing to go to Bob from 3 departments over and say "what does this MEAN???" about whatever feature, heh.

I actually used that to point out to Pepisolo that he uploaded something that was throwing XML errors all over the place.  I did kill the error first though. 

The "personal responsible for this line of code, no matter how crappy or confusing it is" tool just didn't catch on for some reason.

Also, it is ALWAYS Misery's fault. Unless it was Craig's fault. Or Cinth's fault. They should really learn to check my code better before using it.

Unless it's the reanimator boss that had naming conflicts written all over it, then it's your fault??   

If we ever [redacted] we'll have to [redacted] and deadly [redacted] real life zombies [redacted].

https://www.youtube.com/watch?v=HWfKdKWJEkM

Flashbacks!!!!

Flashbacks on the forum!  Flashbacks on the forum!!  That's it!!!  That's IT!!!!  I'm sick of these [redacted] flashbacks on this [redacted] forum!!
Of course I went there...how could I not?

The flashback I had wasn't a pleasant one.  It wasn't even forums related :/



I like how this thread went from me ribbing Chris to assigning blame through SVN in like 3 hours time.  So much derail

well that's half the point of making threads in the first place it wouldn't be any fun otherwise ya?.

[x4000]

"Blame" is a harsh word, yeah. I saw a similar feature in Atlasian Source Tree during a contract I did over the new year.  Though it was commit based ("blame commit for..." kind of wording).

But at the same time I am unsure of a better word for it.

I know, right?  I've occasionally mused on that for like a decade, and... nothing better.  Ah well.

[Misery]

Also, it is ALWAYS Misery's fault.

This is what I usually assume.

*game crashes after changing nothing* "Oh crap what did I just do"

[keith.lamothe]

It's called "blame" because, if you have to ask, that's what you're looking for

[x4000]

It's called "blame" because, if you have to ask, that's what you're looking for

True in a small team -- I never use that thing.  But I can imagine seeing some strange code at a company like Microsoft and wanting to go ask the original author "okay this seems strange: if I change it, it's not going to start making ATMs eat cards or flush the toilet or something, right?"

[Draco18s]

No no, credit card processing is much much more terrifying:

Point of Sale: "¥2000 please"
Credit card transaction into the US: "Convert that"
Some (broken) system: "Okie, $2000."
Bank: "Transaction validated, confirmed for $2000."

A friend of mine worked at a company where that happened.  It somehow went into production after it had been checked over by the regulatory agencies and it was that bad.  It converted currency simply by changing what currency it wanted.  IIRC, they hadn't meant to push it live, but yeah.

[nas1m]

"Blame" is a harsh word, yeah. I saw a similar feature in Atlasian Source Tree during a contract I did over the new year.  Though it was commit based ("blame commit for..." kind of wording).

But at the same time I am unsure of a better word for it.

I know, right?  I've occasionally mused on that for like a decade, and... nothing better.  Ah well.

I once came across an svn client that allowed to use an alternate name for the blame feature: praise .

[x4000]

Yikes on the currency conversion!  That would be so incredibly much worse with certain other currencies, too.

And oh yeah, I have seen the praise thing!  Sometimes blame/praise.  I thought that was nice.

[keith.lamothe]

Such weak UI. Where's my "excoriate" button?

[x4000]

excoriate/laud