Desarrollando el formulario registro para ezvisa [SPA-ENG]
Ya llevo casi un mes en esta empresa de visas norteamericanas y junto a mi colega tuvimos que estar desarrollando muchas cosas en la plataforma web debido a problemas de seguridad mala implementación de código por la inteligencia artificial y necesidades de optimización en la velocidad de la página.
A lo largo de esta semana nos hemos encontrado con muchas cosas para solucionar pero también peticiones de cliente y una de esas es que el formulario registro era demasiado extenso y él lo quería visualmente más atractivo.
I've been with this US visa company for almost a month now, and my colleague and I have had to develop many things on the web platform due to security issues, poor code implementation due to artificial intelligence, and page speed optimization needs. Over the course of this week, we've encountered many issues to resolve, as well as client requests. One of them is that the registration form was too long, and he wanted it to be more visually appealing.

Luego de algunas reuniones y acuerdos llegamos a la conclusión de que implementaríamos algunas animaciones que avisen el rol de usuario que desea utilizar para registrarse y que el formulario registro sería mucho más corto.
Esto resultó en un trabajo un poco más tedioso porque fue borrar todo lo que habíamos hecho previamente y volver a empezar pero por otro lado nos facilita la tarea de la base de datos ya que el flujo de datos será mucho menor.
After several meetings and discussions, we came to the conclusion that we would implement some animations indicating the user role they wished to use to register, and that the registration form would be much shorter. This resulted in a slightly more tedious process because it meant erasing everything we had previously done and starting over, but on the other hand, it made the database easier for us since the data flow would be much smaller.

Aquí no entraré en detalle sobre cómo manejar el flujo de datos en la base de datos por cuestiones de seguridad pero cabe decir que me permite hacer menos peticiones a la base de datos para crear un usuario.
I won't go into detail here on how to handle the data flow in the database for security reasons, but it's worth mentioning that it allows me to make fewer requests to the database to create a user.

You can see in the images portions of the code showing how it's being implemented, and some images showing how there are only three screens that show the same user role, although they are different in the background, and a much simpler form to complete.
Thanks for your contribution to the STEMsocial community. Feel free to join us on discord to get to know the rest of us!
Please consider delegating to the @stemsocial account (85% of the curation rewards are returned).
Consider setting @stemsocial as a beneficiary of this post's rewards if you would like to support the community and contribute to its mission of promoting science and education on Hive.
Congratulations @dobro2020! You have completed the following achievement on the Hive blockchain And have been rewarded with New badge(s)
Your next target is to reach 3000 comments.
You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word
STOP
Check out our last posts: