carlosaore

Best Practices - Git
These are recommendations. They should be followed in the absence of good, justifiable reasons to do things differently.

General
Small and frequent commits, to facilitate the handling of any problems that may arise.
Commits with a significant name about the feature it’s implementing.
Branches with a significant name about the feature that is being worked on.
Pull requests done often, to make sure that everyone in the team is working on the same version. This also means that the work is adequately split into user stories that can be translated into features.
Pull requests have to be reviewed and approved by at least one person before being merged into the main branch.
Branches

carlosaore

const H1 = styled.h1`
     margin: none;
     position: absolute;
     transform: translate(0, -60%);
     top: 40%;
     margin: 2em;
     font-size: 2.8em;
     font-family: Arial, Helvetica, sans-serif;
     letter-spacing: 2px;
     line-height: 1.5em;

carlosaore

// 1. falsy values example

// [null, undefined, '', 0, -1].map(function (x) {
//   console.log(!!x);
// });

// false, false, false, false, true


// 2. Object compare (memory position)

carlosaore

People

:bowtie:	😄 :smile:	😆 :laughing:
😊 :blush:	😃 :smiley:	☺️ :relaxed:
😏 :smirk:	😍 :heart_eyes:	😘 :kissing_heart:
😚 :kissing_closed_eyes:	😳 :flushed:	😌 :relieved:
😆 :satisfied:	😁 :grin:	😉 :wink:
😜 :stuck_out_tongue_winking_eye:	😝 :stuck_out_tongue_closed_eyes:	😀 :grinning:
😗 :kissing:	😙 :kissing_smiling_eyes:	😛 :stuck_out_tongue:

carlosaore

Tricks For Getting Unstuck During a Coding Interview

From Interview Cake

Getting stuck during a coding interview is rough.

If you weren’t in an interview, you might take a break or ask Google for help. But the clock is ticking, and you don’t have Google.

You just have an empty whiteboard, a smelly marker, and an interviewer who’s looking at you expectantly. And all you can think about is how stuck you are.

carlosaore

Best Practices - Git

These are recommendations. They should be followed in the absence of good, justifiable reasons to do things differently.

General

• Small and frequent commits, to facilitate the handling of any problems that may arise.
• Commits with a significant name about the feature it’s implementing.
• Branches with a significant name about the feature that is being worked on.
• Pull requests done often, to make sure that everyone in the team is working on the same version. This also means that the work is adequately split into user stories that can be translated into features.
• Pull requests have to be reviewed and approved by at least one person before being merged into the main branch.

carlosaore

Fetch API cheatsheet

Simple GET request with the Fetch API

fetch('{url}')
    .then(response => console.log(response));

Simple POST request with the Fetch API

carlosaore

JAD-like project planning

After some initial brainstorming, if you are close to a consensus for what you want to do, you can establish the need for it by asking the following questions:

• What are the expected benefits?
• What opportunities does it address?
• What problems would it resolve?
• What are the risks?

Then, if you are up for it, try to agree on a "Project Scope Statement" by defining these scope deliverables:

• Project Objectives (if what is on the slides is not enough)
• Project Constraints

carlosaore

// Use caesar("word", 7) to encode
// Use caesar("dfhu", -7) to decode
// Basically, key to encode and -key to encode

// "I'm well, I'm alive. I'm in a refugee camp near the border. Will send more messages soon"
// "P't dlss, P't hspcl. P't pu h ylmbnll jhtw ulhy aol ivykly. Dpss zluk tvyl tlzzhnlz zvvu"
//
// "Your camp was in the news yesterday. They said you will get some relief packages soon. Stay strong!"
// "Fvby jhtw dhz pu aol uldz flzalykhf. Aolf zhpk fvb dpss nla zvtl ylsplm whjrhnlz zvvu. Zahf zayvun!"

carlosaore

const express = require("express");
const movies = require("./movies");
const connection = require("./config");

const port = 3000;
const app = express();

connection.connect(function(err) {
  if (err) {
    console.error('error connecting: ' + err.stack);