djaiss

#!/usr/bin/env bash

# Ask for the administrator password upfront
sudo -v

# setup taps
brew tap caskroom/fonts
brew tap caskroom/cask

# install applications

djaiss

{"lastUpload":"2020-03-04T01:23:15.400Z","extensionVersion":"v3.4.3"}

djaiss

/**
     * Display a listing of the resource.
     *
     * @param Request $request
     *
     * @return \Illuminate\View\View|\Illuminate\Http\RedirectResponse
     */
    public function index(Request $request)
    {
        $user = auth()->user();

djaiss

@extends('layouts.skeleton')

@section('content')
<div>
  @csrf

  {{-- Breadcrumb --}}
  <div class="ph3 ph5-ns cf w-100 bg-white pv3 mb3">
    <div class="mw9 center">
      <div class="fl w-100 pa2">

djaiss

name: Unit tests

on: [push]

jobs:
  phpunit-tests:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v1
    - name: Copy .env

djaiss

Product managers

• There are hundreds of methods for building products and running teams. As a quality PM, it's important to have an open mind about all of it, but finding your own process and philosophy can be grounding. It helps you find your pillars so that you don't smash into things while you're building. Remember, however, that you can always find budget for remodelling. 😉
• The beautiy of a good process is when it just becomes how you do your work. When you forget you're following a process at all is when you know the process is working for you, your team, your company and your customers.
• The advice I give new Product Managers or PMs coming onto a team for the first time: put your ego away, don't be 'the big idea person' and help your team ship as much as possible. If you ship products you'll learn about them, and people around you will benefit from the momentum you're building.
• The advice I've given myself throughout my career: put your ego away, you don't have to be the 'the big

djaiss

Illuminate\Support\Collection {#1278
  #items: array:7 [
    0 => array:2 [
      "message" => "✓ Maintenance mode: on"
      "command" => "php artisan down --message=Upgrading Monica v2.3.1 --retry=10"
    ]
    1 => array:2 [
      "message" => "✓ Resetting application cache"
      "command" => "php artisan cache:clear"
    ]

djaiss

Commit Message Guidelines

In the last few yers, the number of programmers concerned about writting structured commit messages had dramatically grown. As exposed by Tim Pope in article readable commit messages are easy to follow when looking through the project history. Moreover the AngularJS contributing guides introduced conventions that can be used by automation tools to automatically generate useful documentation, or by developpers during debbuging process.

This document borrow some concepts, conventions and even text mainly from these two sources, extending them in order to provide a sensible guideline for writing commit messages.

• Goals
• Proposal
  • Commit Message Format

• Allowed ``

djaiss

var request = require('request')

request(
    {
        method: 'GET',
        uri: 'http://localhost:1080/email'
    }
    , function (error, response, body) {
        // body is the decompressed response body
        console.log('server encoded the data as: ' + (response.headers['content-encoding'] || 'identity'))

djaiss

relationship_type_partner_with_namerelationship_type_spouse' => 'mari',
'relationship_type_spouse_female' => 'femme',
'relationship_type_spouse_reverse' => 'mari',
'relationship_type_spouse_reverse_female' => 'femme',
'relationship_type_spouse_with_name' => 'le mari de X',
'relationship_type_spouse_female_with_name' => 'lepouse de X',
'relationship_type_spouse_reverse_with_name' => 'le mari de X',
'relationship_type_spouse_reverse_female_with_name' => 'l'epouse de femme',