thirdy

1. When getting an error. Google the error first before suspecting any other causes.
2. Do not git pull when you are independently working on another feature. Other changes might delay you, e.g. DB changes that needs extra setup.

thirdy

const MY_DOMAIN = "your domain"
const START_PAGE = "start page url"

addEventListener('fetch', event => {
  event.respondWith(fetchAndApply(event.request))
})

const corsHeaders = {
  "Access-Control-Allow-Origin": "*",
  "Access-Control-Allow-Methods": "GET, HEAD, POST,PUT, OPTIONS",

thirdy

Team Leading

1. Get to know members individually so they can easily communicate complex issues
2. Regularly assess individual progress, provide guidance and coaching
3. Clearly communicate goals and context
4. Regularly inform management of progress and potential risk
5. Shield team from feature creep and premature requirements
6. Establish clear development process

• All code committed must be code reviewed
• Maintain reliable automated test suite and act as living documentation

thirdy

                                                                               
                                                                               
                                                                               
                                                                               
        * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *      
        *                                                               *      
        *   * * * * * * * * * * * * * * * * * * * * * * * * * * * * *   *      
        *   *                                                       *   *      
        *   *   * * * * * * * * * * * * * * * * * * * * * * * * *   *   *      
        *   *   *                                               *   *   *      

thirdy

Whats the worst part of working here?

Answer:
 if they say 'nothing' - then they are lying or not aware
 
 Do your engineers write unit test?
 
  Do you write unit test?
  
  - Idea is to open up discussion about Unit Testing

thirdy

cd "C:%HOMEPATH%\.IntelliJIdea*\config"
rmdir "eval" /s /q
del "options\options.xml"
reg delete "HKEY_CURRENT_USER\Software\JavaSoft\Prefs\jetbrains\idea" /f

:: It is Highly Advised to Purchase the JetBrain Softwares
:: This is only for the case You just want to Extend the 
:: Trial Period and Evaluate the IDE for some more Time

thirdy

; Bind F1 to a single Mouse Click
; This is my first AutoIt script
; Motivation for this script is to ease pressure to my right index finger
; License - GPLv3

#include <AutoItConstants.au3>

HotKeySet("{F1}", "MouseSingleClick")

While 1

thirdy

https://superuser.com/questions/468580/create-application-shortcut-chromes-feature-in-firefox

thirdy

Materials being read in progress are noted, otherwise finished reading.

Blog

1. Just Say No to More End-to-End Tests - https://testing.googleblog.com/2015/04/just-say-no-to-more-end-to-end-tests.html

• Note on Java exceptions: One sure way to help in easily understanding problems is to have a well designed exception mechanism. You do not want generic exceptions like RuntimeException. You do not want badly wrapped exceptions - I've seen a string manipulation method that throws HttpInternalServerException. Ideally you need an exception stack trace that provides you context and a consistent way of reading them. And most important of all, you do not want exceptions getting lost somewhere. A big problem with a codebase that is already using badly designed exception is that it can be a risky change since it will probabably affect most of the existing code - imagine an exception class that is written in an xml config.
• Note on the [linked sample source code](https://github.com/google/guava/blob/master/gu

thirdy

/*  Copyright 2017 Vicente de Rivera III
 
     This program is free software: you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation, either version 3 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the