LogFAQs > #957496939

LurkerFAQs, Active DB, DB1, DB2, DB3, DB4, DB5, DB6, DB7, Database 8 ( 02.18.2021-09-28-2021 ), DB9, DB10, DB11, DB12, Clear

Topic List	Page List: 1
Topic	Activision Blizzard being sued California for a toxic work environment.
HashtagSEP 08/27/21 4:42:00 PM #330:	GTM posted... I disagree with it being hard to break code and that the changes are only strings, but agree that definitely youre right that the harder part is all the pre-made stuff If it's well written code, it should be extremely hard to break code by changing strings, since you should never be referencing those strings directly. It should be variables that are referenced. So, for a very basic example, if you've got a bunch of character objects that have different strings and the like, and you want to display a name, you should be using a variable to display that name that then gets said name from the object. So you'd be calling upon a variable like "charName" that changes depending on which object it's referencing. That way, even though the name string itself would be changing from "McCree" to "Winston" to "Tracer" to whatever else based on the need, the actual reference to that is always just "charName." There should rarely, if ever, be an actual reference to the actual string "McCree," which is what COULD break things, yes, if you're not careful. EDIT: Now, in the example of changing the repository name from "master" to "main," that would break things, certainly, because it's a direct reference that your local repo is matching to. If your local repo is expecting "master" but the repository itself was renamed "main," that's definitely going to cause headaches. One other such instance that could break things would be file names, but the file names themselves aren't gonna be seen by your average player, so they can definitely take their time doing that more carefully and just roll out the simple changes like strings and the like right away. And even then, you'd kinda need to be pretty negligent to miss a file name or reference. The repository thing is definitely a much bigger headache than anything else since you've gotta worry about local repos and pipelines. --- #SEP #Awesome #Excellent #Greatness #SteveNash #VitaminWater #SmellingLikeTheVault #Pigeon #Sexy #ActuallyAVeryIntelligentVelociraptor #Heel #CoolSpot #EndOfSig <cite>HashtagSEP posted [p:957496939] in Activision... [t:79576831]...</cite> <quote>GTM posted... </cite> <quote>I disagree with it being hard to break code and that the changes are only strings, but agree that definitely youre right that the harder part is all the pre-made stuff</quote> If it's well written code, it should be extremely hard to break code by changing strings, since you should never be referencing those strings directly. It should be variables that are referenced. So, for a very basic example, if you've got a bunch of character objects that have different strings and the like, and you want to display a name, you should be using a variable to display that name that then gets said name from the object. So you'd be calling upon a variable like "charName" that changes depending on which object it's referencing. That way, even though the name string itself would be changing from "McCree" to "Winston" to "Tracer" to whatever else based on the need, the actual reference to that is always just "charName." There should rarely, if ever, be an actual reference to the actual string "McCree," which is what COULD break things, yes, if you're not careful. EDIT: Now, in the example of changing the repository name from "master" to "main," that would break things, certainly, because it's a direct reference that your local repo is matching to. If your local repo is expecting "master" but the repository itself was renamed "main," that's definitely going to cause headaches. One other such instance that could break things would be file names, but the file names themselves aren't gonna be seen by your average player, so they can definitely take their time doing that more carefully and just roll out the simple changes like strings and the like right away. And even then, you'd kinda need to be pretty negligent to miss a file name or reference. The repository thing is definitely a much bigger headache than anything else since you've gotta worry about local repos and pipelines. --- #SEP #Awesome #Excellent #Greatness #SteveNash #VitaminWater #SmellingLikeTheVault #Pigeon #Sexy #ActuallyAVeryIntelligentVelociraptor #Heel #CoolSpot #EndOfSig</quote> ... Copied to Clipboard!
Topic List	Page List: 1