richin13

Writing Style Prompt

• Focus on clarity: Make your message really easy to understand.
  • Example: "Please send the file by Monday."
• Be direct and concise: Get to the point; remove unnecessary words.
  • Example: "We should meet tomorrow."
• Use simple language: Write plainly with short sentences.
  • Example: "I need help with this issue."
• Stay away from fluff: Avoid unnecessary adjectives and adverbs.
• Example: "We finished the task."

qoomon

Conventional Commit Messages

See how a minor change to your commit message style can make a difference.

git commit -m"<type>(<optional scope>): <description>" \
  -m"<optional body>" \
  -m"<optional footer>"

swalkinshaw

Moved to Shopify/graphql-design-tutorial

rondy

FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.

---

Effective Engineer - Notes

• By Edmond Lau
• Highly Recommended 👍
• http://www.theeffectiveengineer.com/

What's an Effective Engineer?

yefim

{
  "AWSEBDockerrunVersion": "1",
  "Image": {
    "Name": "<AWS_ACCOUNT_ID>.dkr.ecr.us-east-1.amazonaws.com/<NAME>:<TAG>",
    "Update": "true"
  },
  "Ports": [
    {
      "ContainerPort": "443"
    }

philipstanislaus

# Sample Nginx config with sane caching settings for modern web development
#
# Motivation: 
# Modern web development often happens with developer tools open, e. g. the Chrome Dev Tools. 
# These tools automatically deactivate all sorts of caching for you, so you always have a fresh 
# and juicy version of your assets available.
# At some point, however, you want to show your work to testers, your boss or your client. 
# After you implemented and deployed their feedback, they reload the testing page – and report 
# the exact same issues as before! What happened? Of course, they did not have developer tools 
# open, and of course, they did not empty their caches before navigating to your site. 

MichaelPote

/*
 * http://www.myersdaily.org/joseph/javascript/md5-text.html
 */
(function (global) {

  var md5cycle = function (x, k) {
    var a = x[0],
      b = x[1],
      c = x[2],
      d = x[3];

akrabat

<?php
// All file paths relative to root
chdir(dirname(__DIR__));
require "vendor/autoload.php";

$settings = ['foo' => 'FOO', 'bar' => 'BAR'];
$app = new \Slim\App($settings);


// Set some things into the container

chrismdp

# You don't need Fog in Ruby or some other library to upload to S3 -- shell works perfectly fine
# This is how I upload my new Sol Trader builds (http://soltrader.net)
# Based on a modified script from here: http://tmont.com/blargh/2014/1/uploading-to-s3-in-bash

S3KEY="my aws key"
S3SECRET="my aws secret" # pass these in

function putS3
{
  path=$1

sverhoeven

Create sp in simplesamlphp

1. Add SP to authsources.php

    'default-sp' => array(
            'saml:SP',
            'entityID' => 'https://svwiki.cloudapp.net',
            'discoURL' => NULL,
            'privatekey' => 'saml.pem',
   

'certificate' => 'saml.crt',