one of the most powerful use-cases for polyphonic is multi-perspective discussions. you can either use custom personas, or simply ask each model to embody a different perspective temporarily for the debate. Ive also included a feature that allows you to address individual models in-line, so you dont have to get overloaded with 3 responses to a question that only needs a single response. or lets say you have a questions about one models response, you can simply click on their pill (at the bottom within the chat input panel), and address them directly. i toyed around with setting this up where all you need to do is verbally say the name of whichever model you want ot talk to, and i also played with @-ing them. these options are doable, but it just makes the process cleaner and less at-risk for confusion used the button system. ill be looking for feedback on this once we go live to see if y'all have any requests or would like this feature to work differently in this example, i actually just noticed that gpt-5's response got truncated, so instead of rerunning the whole prompt, i just clicked on their pill, and asked them if they wanted to try to respond again since theirs got cut off. they saw and acknowledged the issue and regenerated their response. in their response, they proposed 3 roles that the group could take for the debate we were about to have (debating AI ethics). so, i addressed the other two models (last image) and asked them which of the two remaining roles/perspectives they would each like to take. once both of them repsonded, we began opening statements for the debate. this could also work for things like code review, writing, etc. get 3 reviews from three models on a somecode youre working on, or get 3 variations of a rewrite from three different models, etc etc. pretty cool!

“SomeCode”

Because someCode can get complicated and may leave program in logically incoherent state. It happens all the time, because software developers are humans and fallible. consts reduce surface for mistakes.

I think the value is not in that knowledge per se but in the active prevention of this pattern: let foo if (someCode) { foo = value } This is surprisingly common and is generally a bad pattern to use. There are cases to justify it but most people should either use a const or move this computation to a standalone function (also gaining better testability, hey!) At least, that's where I see the value of const. For some, it can also teach them not to rely on value reassignment and slowly shift their mental models to thinking in immutable structures and pure operations.

Print(1) #somecode Print(2) #someothercode Print(3) Output: 1 2 <Exception in code>

sprou.tt/1Nkx0XOkM6I #lowcode #nocode #somecode #letscode #low-code #nowhiring #chennaijobs

just code from a parallel universe 🙂 because in our, I often see this try { somecode; somecode; } catch { }

Wise words. It’s funny how SOMEcode no code art are all things I enjoy doing…

// disable-lint foobar SomeCode; // enable-lint foobar ↑これを こう書きたい↓ // push-lint // disable-lint foobar SomeCode; // pop-lint

Damn It! Symbol tables are meant to be used! func someCode(value : String?) { guard let hasValue = value else { return } doSomethingWith(hasValue) thenMaybeSomethingElseWith(hasValue) andFinallyForGoodLuck(hasValue) }

I haven’t actually. I trust Swift Evolution to bike-shed that ad infinitum 😂 Could it be like? #silenceWarnings(“someRegex that matches the warning”) someCode() #end

Sometimes #NoCode is actually #SomeCode

NoCode --> LowCode --> SomeCode?

Groovy is a fun language: Method signature: void blah(Closure<?> cl) Method call: blah { someCode() } Want to add something like this to Cyen (my own language)

this is somecode name kids next door kind of shit

#NoCode #SomeCode #LowCode #Code It's all the same Solve problems Build a business

Two friends - normies who can't code building cool things (their own description 😂) - just jamming on nocode or "somecode" over at @automationtown This was sooo entertaining yet great to hear practical perspectives from people in the thick of it 👏 open.spotify.com/episode/3Yu…

#nocode products can be much more with #somecode that integrate with cross-nocode tools Anyone with the hacks?

Update on @discord pack for @coda_hq : I got TWO migraines this week. You kidding me?? Two? Laid me out. But I am returning to discords api documentation with renewed vigor! I’m new to coding but I WILL figure it out. #nocode #somecode #codapack #buildinpublic