Muestra las diferencias entre dos versiones de la página.
| Ambos lados, revisión anterior Revisión previa Próxima revisión | Revisión previa | ||
|
wiki2:global [2020/06/22 09:31] alfred [Questions to make] |
wiki2:global [2021/02/18 14:37] (actual) |
||
|---|---|---|---|
| Línea 82: | Línea 82: | ||
| </code> | </code> | ||
| ===== Python ===== | ===== Python ===== | ||
| + | |||
| + | ==== Examples ==== | ||
| + | |||
| + | * [[https://stackoverflow.com/a/24846766|Fibonacci]] | ||
| ==== Generators ==== | ==== Generators ==== | ||
| Línea 197: | Línea 201: | ||
| Partitioning of relational data usually refers to decomposing your tables either row-wise (horizontally) or column-wise (vertically). | Partitioning of relational data usually refers to decomposing your tables either row-wise (horizontally) or column-wise (vertically). | ||
| + | ==== Modified Preorder Tree Traversal (MPTT) ==== | ||
| + | |||
| + | MPTT is a technique for storing hierarchical data in a database. The aim is to make retrieval operations very efficient. | ||
| + | |||
| + | The trade-off for this efficiency is that performing inserts and moving items around the tree is more involved, as there's some extra work required to keep the tree structure in a good state at all times. | ||
| + | |||
| + | * https://www.sitepoint.com/hierarchical-data-database/ | ||
| + | * http://mikehillyer.com/articles/managing-hierarchical-data-in-mysql/ | ||
| + | * https://www.ibase.ru/files/articles/programming/dbmstrees/sqltrees.html | ||
| ===== Networking ===== | ===== Networking ===== | ||
| * IPC: Inter Process Communication. | * IPC: Inter Process Communication. | ||
| * TCP/IP | * TCP/IP | ||
| + | |||
| + | ===== Security ===== | ||
| + | |||
| * CORS | * CORS | ||
| - | ====== Questions to make ====== | + | ===== Questions to make ===== |
| + | |||
| + | * {{ :wiki2:notes:reverse-interview-master.zip |Reverse interview document}} | ||
| * Por qué el stack que usan? No como crítica pero -explicar los problemas de ese stack y ofrecer alternativas-. Entonces, qué les llevó a esa arquitectura? | * Por qué el stack que usan? No como crítica pero -explicar los problemas de ese stack y ofrecer alternativas-. Entonces, qué les llevó a esa arquitectura? | ||
| - | * Cuánto tiempo hace que trabajan ahí? Por qué? | + | * Cuánto tiempo hace que trabajan ahí? Por qué? Qué es lo que más te gusta de trabajar aquí? |
| + | * Tell me about the worst day (work-wise) you've had in the last six months. | ||
| * Cómo reaccionó la empresa durante el COVID? | * Cómo reaccionó la empresa durante el COVID? | ||
| + | * What brought you here? What keeps you here? What keeps you up at night? | ||
| + | |||
| + | In my experience it's important to not ask "easy" questions that can be answered by a simple yes/no. | ||
| + | * Instead of: Are you friendly to remote work? Ask: Will I be working with anyone who is remote, or who works from home on a regular basis? | ||
| + | * Instead of: Is the work life balance good? Ask: How responsive are people to emails/Slack over the weekends and after 6pm? | ||
| + | * Instead of: Can I have a good career path? Ask: Did any of your senior engineers start out as junior engineers here? | ||
| + | |||
| + | En la línea de lo anterior: si hay algún problema grave en un fin de semana, cual es la predisposición del equipo de quedarse. | ||