@matematicascontoxqui: 💻📄 ¿El examen de control UNAM en CDMX será en computadora o en papel? En León y Oaxaca, los aspirantes realizaron su examen en computadora y bajo supervisión presencial, pero todavía existe incertidumbre sobre cómo será la aplicación en el Palacio de los Deportes. Por las condiciones del recinto y buscando que todos los aspirantes presenten en circunstancias similares, surge la gran pregunta: ¿mantendrán el formato en computadora o cambiarán a papel? 👀 Por ahora esto es un análisis, no una confirmación oficial. ¿Tú cuál prefieres para presentar: papel o computadora?

matematicascontoxqui
matematicascontoxqui
Open In TikTok:
Region: MX
Saturday 15 August 2026 21:10:00 GMT
13526
1071
9
15

Music

Download

Comments

criandocreando
Criandocreando :
mi hija ensayó en papel, porque yo pense que siendo presencial iba a ser como antes, pero si iniciaron con computadora obviamente no son las mismas condiciones si en el palacio de los deportes lo hacen en papel. yo creo que organizaran de algun modo que sea en computadora, pero si es estress extra para los chavos que si han estado estudiando y que no hicieron trampa, pero es lo que hay, a cer si no salen con otra payasada
2026-08-15 21:20:05
35
su_can6
Su :
ya salieron las fotos en el Palacio de los Deportes y están acomodando las mesas con dispositivos electrónicos
2026-08-16 23:22:10
31
marelyrosas1
Marely :
yo creo que también podría ser en tablet
2026-08-15 21:15:53
23
aletriunfador
Alexito :
yo siento que va a ser lo mismo en hojas de papel y en computadora , aunque en computadora es más facial porque si colocan mesas , es muy probable que a más de 1 se le caiga la mesa por el espacio y rompa si hoja de respuestas , mientras que en una pc solo clikea y ya la hoja pues ta alado o encima de la compu y no tienen problema de que escogieron mal
2026-08-16 06:32:10
1
stephanie_spell
Stefani :
Ojalá y si sea favorable, yo tengo fibromialgia ya de por sí 3 hrs sentada es una pesadilla como para estar encorbados. Espero sea bien en palacio de los deportes.
2026-08-16 13:12:33
3
bereniceortegah13
Berenice OH :
han dicho que no tenían conexión a internet
2026-08-15 22:04:21
0
naomirs2
Naomi RS :
🥰🥰🥰
2026-08-16 20:05:40
0
To see more videos from user @matematicascontoxqui, please go to the Tikwm homepage.

Other Videos

Why “asking ten people” can kill an idea •	Dilution of vision: When you solicit broad opinions before you’ve clarified your core hypothesis, you get ten different directions and end up with a compromised, generic version. •	Premature optimization: Early feedback often focuses on surface details (wording, colors, edge cases) instead of whether the underlying problem and solution are worth pursuing. •	Social risk aversion: People tend to point out risks more than possibilities, especially if they’re not invested in your success. That skews the signal toward “why this won’t work.” •	Decision paralysis: Conflicting advice creates uncertainty, which leads to endless tweaking instead of shipping a testable version. When asking people helps instead of hurts The problem isn’t feedback; it’s unstructured, premature, and unfocused feedback. •	Ask the right people: Talk to people who actually experience the problem you’re solving, not just colleagues or friends who want to be helpful. •	Ask at the right time: •	Very early: test the problem and value proposition (“Does this matter to you?”). •	Mid-stage: test usability and clarity (“Can you do X without help?”). •	Later: test pricing, positioning, and scale. •	Ask the right questions: •	“What’s the last time you faced this problem?” •	“How do you solve it now?” •	“What would make this 10x better?”   Avoid “Do you like this idea?” which invites polite, low-signal answers. A better pattern than “ask ten people” Instead of “ask ten people what they think,” try: 1.	Write a one-paragraph hypothesis: •	Who has the problem? •	What is the problem? •	What is your proposed solution? •	What would count as success? 2.	Talk to 3–5 target users with that hypothesis in mind, focusing on their behavior and pain, not your solution’s features. 3.	Look for patterns, not opinions: If multiple people independently describe the same pain and current workaround, that’s a strong signal. 4.	Decide, then test: Make a clear decision based on patterns, then run a small experiment (landing page, prototype, pilot) instead of re-opening the debate.
Why “asking ten people” can kill an idea • Dilution of vision: When you solicit broad opinions before you’ve clarified your core hypothesis, you get ten different directions and end up with a compromised, generic version. • Premature optimization: Early feedback often focuses on surface details (wording, colors, edge cases) instead of whether the underlying problem and solution are worth pursuing. • Social risk aversion: People tend to point out risks more than possibilities, especially if they’re not invested in your success. That skews the signal toward “why this won’t work.” • Decision paralysis: Conflicting advice creates uncertainty, which leads to endless tweaking instead of shipping a testable version. When asking people helps instead of hurts The problem isn’t feedback; it’s unstructured, premature, and unfocused feedback. • Ask the right people: Talk to people who actually experience the problem you’re solving, not just colleagues or friends who want to be helpful. • Ask at the right time: • Very early: test the problem and value proposition (“Does this matter to you?”). • Mid-stage: test usability and clarity (“Can you do X without help?”). • Later: test pricing, positioning, and scale. • Ask the right questions: • “What’s the last time you faced this problem?” • “How do you solve it now?” • “What would make this 10x better?” Avoid “Do you like this idea?” which invites polite, low-signal answers. A better pattern than “ask ten people” Instead of “ask ten people what they think,” try: 1. Write a one-paragraph hypothesis: • Who has the problem? • What is the problem? • What is your proposed solution? • What would count as success? 2. Talk to 3–5 target users with that hypothesis in mind, focusing on their behavior and pain, not your solution’s features. 3. Look for patterns, not opinions: If multiple people independently describe the same pain and current workaround, that’s a strong signal. 4. Decide, then test: Make a clear decision based on patterns, then run a small experiment (landing page, prototype, pilot) instead of re-opening the debate.

About