Estos últimos días estuve trabajando en unos cambios del diseño de formulario de registro ya que el jefe solicitó que tuviera un sistema registro visualmente diferente.
En un principio contábamos con un solo formulario de registro opciones para elegir el tipo de rol pero actualmente decidimos que se muestran los roles disponibles para registrarse con sus características que tendrán dentro de la web.
<blockquote>
These past few days, I've been working on some changes to the registration form design because the boss requested a visually different registration system.
Initially, we had a single registration form with options to choose the role type, but we've now decided to display the roles available for registration, along with their respective features, on the website.
</blockquote>

https://images.hive.blog/DQmb3Y547fqDAs9RCodxtEjDCoEbdiqJsTEqv4pBxNALDXq/formu.jpg

Una vez que el usuario elige error al cual se va a registrar el formulario se ejecutará una vez por cada campo que debo rellenar.
<blockquote>
Once the user selects the error to be registered, the form will be executed once for each field that must be filled out.
</blockquote>
https://images.hive.blog/DQmSEbbYFv88tZhLa3WxGq954hMnmNQSW6v5F9hvwhBG8wm/formu1.jpg
Con esto quiero decir que para cada campo requerido el usuario existe un formulario no exactamente en código sino visualmente porque no es óptimo aplicar un formulario de registro por cada campo que tenga que rellenar el usuario.
Realizar este trabajo me tomó un poco más de tiempo y esperaba porque necesito validar cada paso de formulario y mostrar todas las alertas que sean necesarias en cada paso más algunos métodos de seguridad para evitar que se pueda saltear los pasos requeridos.
<blockquote>
By this, I mean that for each required field, there is a form, not exactly in code, but visually, because it's not optimal to apply a registration form for each field the user has to fill out.
This work took me a little longer than I expected because I need to validate each form step and display all the necessary alerts for each step, plus some security measures to prevent skipping required steps.
</blockquote>
https://images.hive.blog/DQmUK3tJYsWemDgRYZpNo3eVp1WffGMgEnuM7QLKtzQYkfE/formu2.jpg
Adjunto unas imágenes de cómo se ve el formulario tanto en código como del lado del cliente.
Con respecto al código para evitar tener que importar una gran cantidad de formularios decidí utilizar un renderizado dinámico con una variable dentro del formulario para que parezca que a medida que uno va completando cada campo se puede continuar con el siguiente.
<blockquote>
I've attached some images of what the form looks like, both in code and on the client side.
Regarding the code, to avoid having to import a large number of forms, I decided to use dynamic rendering with a variable within the form so that it appears as if each field can be completed, allowing you to move on to the next.
</blockquote>
https://images.hive.blog/DQmehePGEHfPzKjfH2f5VVL1BfqwfUYZ8QmgSQxyyoDzmod/formu3.jpg

StemSocial

Cambios en el diseño del formulario de registro de EzVisa [SPA-ENG]

I finally decided to sit down and learn how to code in Python. I just finished up a learning module. I took other programming courses in college. I learned some Pascal, FORTRAN, C, Javascript, and Visual Basic. I also tinkered with Java and shell scripts on my own. But, if I sat down to write a program in any of those programming languages, I wouldn't know where to start. I've forgotten all of them. What has endured in my memory are concepts of variable types, conditionals, loops, classes, functions, and arrays. The concepts are there, but the particular details have evaporated after almost 30 years.

What Triggered The Decision
---------------------------

The first trigger for deciding to learn Python is a bit of a tangent. I spent some time working on a spreadsheet today. It required me to set up a dropdown menu that would trigger a vlookup function in other cells to populate them with data from another sheet that acts as a data source. This, in turn, could be used to calculate things simply from choosing several dropdown menu items. Similarly, I had done this before. But I forgot the details. If you don't use a skill often enough, you lose it.

I'm not crazy about spreadsheets, in general. My problem with them is that you are so dependent on apps that run on your machine or in the cloud. Lately, I have been using markdown files for my text documents. This plays particularly well with [Obsidian](https://obsidian.md). I can use nano in the command line to create or edit documents, knowing that they'll be properly formatted on Obsidian. I've known for some time that I can work with data using Python in the command line as well. The advantage of using markdown for text files is that they are universal across platforms. I don't have to worry about compatibility. And the files are tiny.

It occurred to me that busting my brain to manipulate data on a spreadsheet is not too different from busting my brain to write some code. It's all about syntax in both cases.

The second trigger is that I have been using LLMs more lately. The thing is that I have not been able to use Machine Learning without knowing how to use Python. I get the sense that I'm missing out on opportunities by not knowing how to take full advantage of AI.

Why Hesitate?
-------------

The main reason why I put off learning were memories of my previous, unhealthy experience with programming. I had an unhealthy tendency to work for hours and hours to avoid losing my train of thought. It takes a while to figure out what you were doing when you stopped.

The second reason why I have put off learning Python for so many years is a bit dumb. Learning any programming language necessarily takes you through the process of learning variable types, conditionals, loops, classes, functions, arrays, and such. It's so elementary. But unless you sit through it, you won't know how Python does these things. It's not that it's mind-numbingly difficult. Instead, it's mind-numbingly boring. I simply did not want to put myself through that. It's a lame reason, I know.

It's particularly lame because it is so easy to learn programming these days. There are so many resources available.

Low Lift
--------

Speaking of abundant resources, I have had a shell account for years that I haven't used to its potential because I haven't done programming. I've mostly used it for email, Gopher, and the occasional MUD. Fortunately, the community on the server encourages learning how to program. And they provide all I would need, including a database account.

What I hope to get out of it
----------------------------

I have the sense that I have been missing out on opportunities by not taking the time to learn Python. It's good for automation. It's good for working with data on AI, particularly machine learning. I suspect that learning Python will also be useful for routine IT tasks. But down the line, I think it will also come in handy for finding work opportunities.

Given that Python is great for working with data, I think there will be a natural segue to learning to work with databases. I don't know if data analytics is in my future. We'll cross that bridge when we get there. I think I'm more likely to delve into back end development.

Expectations
------------

I think that once I get past the boring parts, learning Python will become more interesting. Obviously, when you're learning, you aren't really solving any real problems. But once you get a better grasp of what can be done with Python, some ideas will be forthcoming to put the knowledge to good use. Therefore, I expect my eyes to open a bit once I gain some insight on what Python can do. I have a better handle on the compulsive part now. I'm more likely to take breaks, eat, and sleep these days. Overall, I expect to have a positive experience this time around.

Cambios en el diseño del formulario de registro de EzVisa [SPA-ENG]

Finally Decided To Learn Python