Dec 15, 2021
some of y'all are not ready for my breakcore speedcore arc
seen from China
seen from China
seen from Italy
seen from China
seen from Ireland
seen from Italy
seen from Ireland
seen from Italy
seen from Italy
seen from United States
seen from New Zealand
seen from China
seen from United States
seen from Australia
seen from Uzbekistan
seen from Türkiye
seen from Finland
seen from South Korea
seen from Australia
seen from United States
some of y'all are not ready for my breakcore speedcore arc
¡De Principiante a Coder Pro!
Desentrañando los Secretos del Lenguaje de Programación C# y .NET 💻🚀 ¡Hola, n’tiquers de Alicante! ¿Alguna vez te has preguntado qué hace que un programa de ordenador funcione? No hablamos de magia, sino de la estructura fundamental del lenguaje C# y la poderosa plataforma .NET. Si estás dando tus primeros pasos en la programación o simplemente quieres afianzar tus conocimientos, ¡este artículo…
Corregir y documentar código en Visual Studio
🛠️ De código caótico a código limpio: Guía definitiva para principiantes en Visual Studio ¿Alguna vez has abierto un archivo de código y has pensado “¿quién escribió esto, un mono con cafeinosis?”? Giro dramático de los acontecimientos: probablemente fuiste tú hace 6 meses. No te preocupes, todos hemos estado ahí. Incluso los programadores más experimentados han creado monstruosidades que…
Dominando la Nomenclatura en C# (.NET): PascalCase, camelCase y la Notación Húngara
En el mundo de la programación, la legibilidad y la consistencia del código son tan importantes como su funcionalidad. Especialmente en entornos colaborativos y proyectos grandes, una buena convención de nomenclatura es crucial. En C# y el ecosistema .NET, Visual Studio nos guía, pero comprender las notaciones PascalCase, camelCase y, en menor medida, la Notación Húngara es fundamental para…
Learned SomethingNew today. ForYears, I as all of you are, was aware of the tendency for companies especially TechCompanies to slam two words together and to capitalize the SeparateWord. I now know that this is called CamelCase.
Že CamelCase je špatně vím už dlouho, ale nikdy jsem pro to neměla důkaz. Tak už ho mám. isPlatformX11() vs IsPlatformX11(). Že pozdravuju vývojáře QT is celým Trotltechem, kde si v této sračce doslova libují.
Holy shit ChatGPT understands what LostSideDead means!
"
The pattern "1 2 2 3 3 3" can indeed be found in the camel case function name "LostSideDead" by analyzing the capital letters and their sequence within the string. Here's how it works:
Pattern: 1 2 2 3 3 3
Function Name: LostSideDead
To break it down:
The first capital letter "L" represents the first "1" in the pattern, indicating the start of a new sequence.
The next capital letter "S" marks the beginning of the "2" sequence. Since it's the second unique capital letter, it fits the "2" in the pattern.
Following "S", the next capital letter "D" represents the start of the "3" sequence. It's the third unique capital letter, aligning with the "3" in the pattern.
The pattern "1 2 2 3 3 3" doesn't directly map to repetitions or sequences of letters in "LostSideDead" in a straightforward manner, such as one might expect to see "A BB CCC" format directly reflected in the string's structure. Instead, if we interpret the pattern as indicating the positions of distinct capital letters as markers within the sequence, we can see how each capital letter represents a step in the pattern:
"L" is the first position (1),
"S" is the second unique capital letter, marking the second position (2),
"D" is the third unique capital letter, marking the third position (3).
However, this interpretation somewhat stretches the original intent of the pattern "1 2 2 3 3 3," which suggests a sequence of increasing repetitions. In "LostSideDead," we have three distinct sections marked by capital letters without repeating them according to the numeric pattern of repetitions.
The pattern "1 2 2 3 3 3" typically would suggest a single instance, followed by a double instance, and then a triple instance of elements. In the case of "LostSideDead," the direct correlation to this pattern is not precise if we're looking for repetitive sequences that match the numerical pattern in terms of repetition count or sequence length directly reflected by the characters in the function name.
User
look closer L s S d D d
ChatGPT
Ah, I see what you're pointing out now. When we take a closer look at "LostSideDead" and pay attention to the uppercase and lowercase letters as you highlighted, the pattern "1 2 2 3 3 3" becomes clear based on the positions and repetition of uppercase (capital) letters versus lowercase letters. Here's how the pattern fits:
Function Name: LostSideDead
Pattern Analysis:
L (1 occurrence) - Marks the start of the sequence, fitting the "1" in the pattern.
s S (2 occurrences, considering the uppercase 'S' as a continuation of 's') - This fits the "2 2" in the pattern, with the lowercase leading into the uppercase marking a distinct step.
d D d (3 occurrences, with the sequence starting with lowercase, peaking with uppercase, and then returning to lowercase) - Perfectly fits the "3 3 3" part of the pattern, illustrating the progression and repetition within the sequence.
In this interpretation, the function name "LostSideDead" cleverly encodes the pattern through the transition between lowercase and uppercase letters:
The first capital "L" stands alone, representing the "1".
The sequence of "s" followed by "S" represents the "2 2", with the transition from lowercase to uppercase indicating the repetition and progression.
Finally, "d D d" (starting with lowercase, moving to uppercase, and returning to lowercase) captures the "3 3 3" part of the pattern, with the presence of the uppercase letter flanked by lowercase versions of the same letter marking the triple step in the sequence.
This nuanced approach cleverly utilizes the camel case naming convention to map the numerical pattern into the structure of the function name, highlighting a creative encoding of patterns within text."
hey fucks
what's the objectively correct variable casing in your subjective opinion?
camelCase
PascalCase
snake_case
kebab-case
Other (tags, please!)