From SysOps to DevOps/Full Stack

Detailing my Journey from System Administrator to Developer

Choosing our next language.

Once Flatiron is completed, we can now choose new technology options. I am not the biggest fan of ruby, and I will be looking into other language options and technologies. To make our choice more manageable, we can look at several factors to narrow down your selection.

Javascript in the Browser(s)

JavaScript runs different across browser vendors, versions, and extensions, making it difficult to determine if code will run as intended. To minimize the chances of an issue, we must employ strategies:

Rail and least Privilage

A recommended best practice of securing servers is to reduce the attack surface. This involves removing or turning off anything that is not needed by the server. For instance, Microsoft server has modes that disable graphical user interface and even RDP. This will both diminish a server’s chance of getting exploited and odd interactions that can happen between services. In addition to security and stability advantages, it can also reduce server requirements.

Sinatra Blog: Working with Emails.

The email has become one of the de facto ways a user is identified on a system (at least in the USA). This is due to their uniqueness, and popularity, and end-user simplicity. If a user needs to verify their email ownership or reset their password, simply send an email with a link for the user to for them to click on. However, while email is simple for the end-user, there are important considerations for application authors. Email is not secure and should not contain sensitive information. Anti-Spam and anti-virus efforts have made working with email more complex. Comprise of an email account can lead to compromise of your application’s account.

Performance effect of SQLite constraints

Note: This is not related to Active record or ruby sqlite3 gem.