ReneNyffenegger

msys2 vs msys vs msysgit

MinGW doesn't provide a linux-like environment, that is MSYS(2) and/or Cygwin

Cygwin is an attempt to create a complete UNIX/POSIX environment on Windows. 
MinGW is a C/C++ compiler suite which allows you to create Windows executables - you only 
need the normal MSVC runtimes, which are part of any normal Microsoft Windows installation.

MinGW provides headers and libraries so that GCC (a compiler suite, 
not just a "unix/linux compiler") can be built and used against the Windows C runtime.

bwangila

youtube-dl INSTALLATION

youtube-dl is a handy little command-line utility that, with the right command, automagically downloads videos from Youtube as well as other platforms such as Vimeo, Lynda.com, BBC, CNN etc..(Full list of supported websites)

Kindly proceed to youtube-dl's Github repo for detailed installation instructions for your respective OS

In case of an error, make sure you have Python 2.6, 2.7 or 3.2+ installed as youtube-dl needs it to run.

USAGE

kolisn

import urllib2
import sqlite3
import pip
import os
import json
import pymysql.cursors
#inFile: SQL databse filename string (assuming .db) #outFile: JSON filename string
def getDataFromDBFile(inFile, outFile):
    try:
        conn=sqlite3.connect(inFile)  

Chaser324

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

bjacques

package mani;

import static org.hamcrest.Matchers.equalTo;
import static org.hamcrest.Matchers.is;
import static org.junit.Assert.assertThat;
import static org.mockito.Mockito.verify;
import static org.mockito.Mockito.verifyNoMoreInteractions;
import static org.mockito.Mockito.when;
import static org.mockito.MockitoAnnotations.initMocks;

kevin-smets

Default

Powerlevel10k

MatthewPatience

Set up Robolectric with Gradle

1. Open your top level build.gradle file.

2. Add Sonatype repo to buildscript repositories and Square Gradle Android Test Plugin to buildscript dependencies. (Older Gradle projects may automatically put this buildscript code in your project build.gradle, in which situation you should put the following in that file.)

chitchcock

Stevey's Google Platforms Rant

I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.

I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real

tdd

# Put this in your ~/.gitconfig or ~/.config/git/config
# Windows users: "~" is your profile's home directory, e.g. C:\Users\<YourName>
[user]
  name = Your Full Name
  email = your@email.tld
[color]
  # Enable colors in color-supporting terminals
  ui = auto
[alias]
  # List available aliases