Selesnya counters? Was that the deck with Venerated Loxodon?
I hope so. Selesnya has a ton of support right now, especially with the Gearhulk. That plus Sheltered by Ghosts can be the core of a counters deck.
The other deck that came to mind was Simic adapt, but I think that was in the beta.
Missed opportunity to make this a kindred spell, sadly. Also, at 6 mana, I'd rather just play a double strike sliver most times, and it doesn't create slivers until the next upkeep.
Might be fun in limited and commander, but I don't see it anywhere else. A standard slivers deck would be neat though.
Had this happen before with pattern matching.
Because you created a first draft. Your first draft should include all that info. It isn't writing the whole doc for you lol, just making minor edits to turn it from notes into prose.
Without that? No clue, good luck. They can usually read source files to put something together, but that's unreliable.
This would infuriate me to no end. It's literally the definition of a data race. All data between threads needs to either be accessed through synchronization primitives (mutexes, atomic access, etc) or needs to be immutable. For the most part, this should include fds, though concurrent writes to stderr might be less of an issue (still a good idea to lock/buffer it and stdout though to avoid garbled output).
The main value I found from Copilot in vscode back when it first released was its ability to recognize and continue patterns in code (like in assets, or where you might have a bunch of similar but slightly different fields in a type that are all initialized mostly the same).
I don't use it anymore though because I found the suggestions to be annoying and distracting most of the time and got tired of hitting escape. It also got in the way of standard intellisense when all I needed was to fill in a method name. It took my focus away from thinking about the code because it would generate plausible looking lines of code and my thinking would get pulled in that direction as a result.
With "agents" (whatever that term means these days), the article describes my feelings exactly. I spend the same amount of time verifying a solution as I would just creating the solution myself. The difference is I fully understand my own code, but I can't reach that same understanding of generated code as fast because I didn't think about writing it or how that code will solve my problem.
Also, asking an LLM about the generated code is about as reliable as you'd expect on average, and I need it to be 100% reliable (or extremely close) if I'm going to use it to explain anything to me at all.
Where I found these "agents" to be the most useful is expanding on documentation (markdown files and such). Create a first draft and ask it to clean it up. It still takes effort to review that it didn't start BSing something, but as long as what it generates is small and it's just editing an existing file, it's usually not too bad.
This depends. Many languages support 1 liner aliases, whether that's using/typedef in C++, type in Rust, Python, and TS, etc.
In other languages, it may be more difficult and not worth it, though this particular example should just use a duration type instead.
Ah yes, one of the major questions of software development: to comment, or not to comment? This is almost as big of a question as tabs vs spaces at this point.
Personally? I don't really care. Make the code readable to whoever needs to be able to read it. If you're working on a team, set the standard with your team. No answer is the universally correct one, nor is any answer going to be eternally the correct one.
Regardless of whether code comments should or shouldn't exist, I'm of the opinion that doc comments should exist for functions at the very minimum. Describe preconditions, postconditions, the expected parameters (and types if needed), etc. I hate seeing undocumented **kwargs in a function, and I'll almost always block a PR on my team if I see one where the valid arguments there are not blatantly obvious from context.
Similar to Gateway Plaza. I like the design, though tapping a permanent might end up being a lot easier to do than paying 1 mana.
Still, Gateway Plaza had the benefit of being a gate and working with Plaza of Harmony, so it's a lot different.
Counterspell feels like one of those cards that you'd think is legal but for some reason it's not. With Historic's current power level, it makes way more sense for it to be there now than when it was added to Arena with Strixhaven.
I'd love to see WOTC take the hammer to standard. It'd make it more fun for me at least.
I think my list is at minimum Monstrous Rage, Cori Steel-Cutter, Manifold Mouse, Stormchaser's Talent. Following that:
Decks I think will rise are the bounce deck, hopefully a goblin deck for red (instead of the BS we have now), maybe jeskai prowess(?), jeskai control, dimir control, and some reanimator strategies that weren't as viable before. Boros tokens coming back could be interesting too.
Unstoppable Slasher at home.
Seriously. Slasher is so pushed. It's insane that card is 3 mana. Even wilder that it's not even close to broken in current standard, but maybe that just means that power level is where we're at now.
The ward on this is nice, but at 5 mana, the opponent will have many ways to answer it. Or they can just take the hit and block it since it's only a 3/3 I guess.