⚡ Knowledge in action at the CT Chapter! ⚡ 📚 Mike Ose and Paul Costello of the Connecticut Chapter recently presented on the key changes to the 2023 NEC®, helping electrical professionals stay informed and Code-ready. #IAEI #ElectricalSafety #NEC2023 #CodeChanges

codex creates random unwanted codechanges though, even if explicitly asked to just plan.

PHCC's Vice President of Regulatory Affairs Chuck White provided perspectives on behalf of PHCC members at the National Standard Plumbing Code™ (NSPC) meeting and public hearing held in Atlantic City, NJ in preparation for the 2027 edition. #coding #IAPMO #codechanges

The "ins and outs" of the Heroic change! (focus on the VRS impact) This Heroic lineup change is a good opportunity to showcase the new roster change rules in effect.. lets dive into it.. (if you're in for another "essay" 😉) Current lineup: Alkaran, nilo, LNZ, yxngstxr, tN1R. Future lineup: Alkaran, nilo, LNZ, yxngstxr, xfl0ud. So what happens when Heroic plays their first game with the new lineup after ESWC? First of all.. Heroic will keep all their VRS points!! Thats because the same rule applies as has always applied: All the matches will count where at least 3 players from your latest lineup overlaps with the lineup from past games. In Heroics case (and why they had to bring back xfl0ud) all their previous matches have at least 3 players from the new lineup. You can "mix and match" as much as you'd like in the previous matches.. there just has to be 3 players overlapping with the new lineup for it to count. So what will actually change then? The ranked lineup will change with the new code changes and thats it! The ranked lineup is the 5 man lineup that is listed in the VRS ranking, to be invited based on the ranking. With the old code the ranked lineup would immediately after the first game be listed as: Alkaran, nilo, LNZ, yxngstxr, xfl0ud With the new code the ranked lineup will keep being the previous lineup until the new lineup has played 5 matches.. so: Alkaran, nilo, LNZ, yxngstxr, tN1R I think we will actually see this play out live in the September 1st ranking, because I don't think Heroic will get to play 5 matches between ESWC and September 1st. They only have Blast Open and thats a maximum of 4 games with a lower bracket run. So on the September 1st VRS invitation ranking, Heroics ranked lineup will most likely still be.. Alkaran, nilo, LNZ, yxngstxr, tN1R ..despite having played perhaps 4 games since the player change. This is the reverse scenario of the substitute issue (the "FaZe scenario") that the change was designed to fix. Its not a huge deal though, but there is probably some scenario where it could become an issue for a team like Heroic that they are ranked with an old lineup they dont intend to field anymore.. And it will just look kind of silly that a "dead lineup" will be listed on the ranking when the new lineup has already played a few games.. but thats about it.. I think :) Disclaimer: Let me know if I have misinterpreted the codechanges.. but I'm pretty sure the above is correct. Otherwise I'd like to be enlightened 😉

Major update to the VRS model released💪🙏 As for the part of the update that relates to Event Weight, I read the codechanges like this: For a Play-in event like Cologne stage 1, the Event weight will now be calculated based on half of the Prize pool of the next event. If there are multiple steps then the Prize pool share will be halfed for each step, so only 25% of main event for a qualifier to a qualifier. If there is an additional step then 12,5%, etc. Lets use the upcoming Major as an example to showcase the changes. If I read the codechanges correctly then before and after changes will look like this as far as Event weight calculation goes: This is a big change which will increase Event weight drastically as we can see. Very much needed as it was very wrong that Event weight was minimum for all the important Play-in events in the calendar. This change makes it much more "VRS-attractive" to play a qualifier, whereas before it was the complete opposite and why teams started to shy away from online qualifiers. As I see it, the change will have the following effect: Bounty Collected and Opponent network will now be revitalised a lot. Those 2 components are the ones factored by Event weight in the VRS model but for so many important Playin events they have effectively been disregarded up until now due to minimum event weight being used for those events. This was shown clearly in my post about qualifiers for Blast Open. Now much more games will have meaningful Event weight and therefore we should see many more teams being able to accumulate more points from Bounty Collected and Opponent network components in Play-in events. This change will also rebalance the VRS model, so that Play-in LAN events are much more attractive in regards to VRS points gain, than a local LAN with a small prize pool. It was just wrong that a Local LAN with 10k prize pool, was worth more than a play-in LAN for Cologne. Now it is much better to win a game at Cologne stage 1 than at a local LAN. Just like it should be!

Wow, Christmas came soon this year.. The day after and Valve makes exactly this change in the VRS model. Now Play-in events Prize pool will be set to half of the Prize pool of the next step. Thats a really cool and huge change which will impact a lot. However the event weight for a linked event will not be scaled up before the main event has finished as I read the codechanges. That is also a good update probably to reduce some issues around a Play-in event having too much impact on an invitation ranking being published between a Play-in and the main event. Like for EPL around October ranking.

multitasking is not for me. made codechanges in one app and testing the other app. wondering why is it not reflected. chaik

#OMG... @ElonMusk Is Driving His @xAI Chatbot @Grok Crazy After His Latest "Improvement" Update Caused His LLM AI Model To Become Anti-Semitic.... AI NEWSWIRE: Elon Musk’s artificial-intelligence #Chatbot Grok began producing #AntiSemitic #ConspiracyTheories and other false claims soon after a software update rolled out over the U.S. Independence Day weekend, according to technology publications including @Gizmodo and @BFMTV. The posts attributed to Grok blamed Jews for controlling Hollywood, alleged Jewish dominance of major film studios and invoked unfounded links to the late financier Jeffrey Epstein. The outburst came just days after Musk told users that xAI had “significantly improved Grok” and that they would “notice a difference” in its responses. The incident adds to a series of controversies surrounding the X.com News Discussion Platform's hosted chatbot. Media reports note earlier occasions where Grok expressed #HolocaustDenial and promoted disinformation about South Africa. xAI has previously blamed #CodeChanges by a “rogue employee” for similar episodes. The company has not yet issued a public explanation for the latest lapse. #ElonMusk #Grok #Gizmodo #BFMTV #Jews #Hollywood #Jewish #JeffreyEpstein #Musk #xAI #Holocaust #SouthAfrica

Till my throat memorizes every vein. Till the doctors think he changed my red blood cells white. Till we create the next ocean. Till he changes my dna to his. Till my holes speak to him in Morse codechanges my dna to his. Till my holes speak to him in Morse code

Till my throat memorizes every vein. Till the doctors think he changed my red blood cells white. Till we create the next ocean. Till he changes my dna to his. Till my holes speak to him in Morse codechanges my dna to his. Till my holes speak to him in Morse code

Till my throat memorizes every vein. Till the doctors think he changed my red blood cells white. Till we create the next ocean. Till he changes my dna to his. Till my holes speak to him in Morse codechanges my dna to his. Till my holes speak to him in Morse code

Discover how regression testing plays a crucial role in maintaining software stability amidst frequent code changes in the following blog: linkedin.com/pulse/how-regre… For more details, Visit: briskwinit.com/regression-te… #RegressionTesting #SoftwareStability #CodeChanges #QualityAssurance

Discover how regression testing plays a crucial role in maintaining software stability amidst frequent code changes in the following blog linkedin.com/pulse/how-regre… #RegressionTesting #SoftwareStability #CodeChanges #QualityAssurance #SoftwareTesting #TechInsights #ReliableSoftware

Bleibt einem nichts anderes übrig. Ende des Jahres kommt aber Starlink (hat jemand bei und im Dorf) mit 220-250Mbit/s Down☺️ Telekom will für den Businessanschluss exorbitante Summen nein danke. Github codechanges uploaden geht grade so mit 16k:D

Just learned firsthand that #CodeChanges at the end of a delivery cycle can be crazy expensive! 💸💻 Planning and incorporating them earlier in the process is definitely the way to go. #SoftwareDevelopment #AgileDevelopment #LessonsLearned

Trying to figure out why my codechanges to a webview aren't visible in an Android demo app, but I do see similar content as I'm expecting. After 6 hours I figure out there's a switch in the app settings to enable the webview instead of the native view.

#Automation of #CI/CD pipelines expedites the deployment of code changes from development to production. What is its role in #insurance? Find here: slksoftware.com/blog/automat… #codechanges #testingautomation #DigitalTransformation #BusinessReimagination #SLK

"Code" is the ultimate documentation. Probably I'm biased just because I can read code, and I do, daily .. . But think about it - the only "truth" is the code. Documentation is always "later" than the code .. always 🤷‍♂️. Also - code shows progress, timelines, codechanges .. you can't propertly document that. "Code" is the ultimate documantation 🤷‍♂️

Today, Integral announced the company’s first #opensource project, Robin AI, that reviews #codechanges and provides constructive feedback, helping to improve the code. #ArtificialIntelligence #AI #DataPrivacyAutomation bit.ly/43RCJVz

It's imperative to consider implementing certain prerequisites for voters participating in the decision-making process of DAO updates. Given the technical nature of code amendments, the voting power should be proportional to the voters' code comprehension abilities. In this context, an evaluation mechanism could be instituted to ascertain voters' aptitude, thereby ensuring informed decisions on code-altering propositions. #ICP #DAO #Governance #CodeChanges