To run this, you can try:
curl -ksO https://gist.githubusercontent.com/nicerobot/2697848/raw/uninstall-node.sh
chmod +x ./uninstall-node.sh
./uninstall-node.sh
rm uninstall-node.sh
To run this, you can try:
curl -ksO https://gist.githubusercontent.com/nicerobot/2697848/raw/uninstall-node.sh
chmod +x ./uninstall-node.sh
./uninstall-node.sh
rm uninstall-node.sh
using System.Diagnostics; | |
using System.Windows; | |
using System.Windows.Controls; | |
using System.Windows.Controls.Primitives; | |
using System.Windows.Media; | |
namespace Kinnara.Phone.Controls | |
{ | |
public sealed class ScrollContent : ContentPresenter | |
{ |
(I wrote a bit about why Emacs and Vim on my blog and thought it might be nice to give some starting point for people that want to try it.)
If you just want to play around with Emacs & Evil mode do the following:
mkdir ~/.emacs.d/
init.el
into ~/.emacs.d/
So we're working on creating Android Material Awesome, a library which will hopefully incorperate the benefits of Material Design, Twitter's Bootstrap, and FontAwesome. What we really wanted is a project other people can easily include into their projects using gradle dependencies. To do this we needed to create a standalone library project so we could make it as lightweight as possible for including as a dependency, and a sample app that would use it for testing. These are the steps we took to get started in Android Studio (version 1.1).
The first thing we needed to do was to create two new projects, with all the default settings (Blank Activity etc). One for our sample app, and one for our library. We added both of ours into the same GitHub repo, however you can save them wherever you like.
Original: http://seclists.org/fulldisclosure/2015/Jun/108 | |
Modified by: ptantiku | |
------------------------------------------------------------------------------------ | |
content.html | |
------------------------------------------------------------------------------------ | |
<html> | |
<body> | |
This is not facebook.com! This is EVIL! | |
<script> |
aws codepipeline get-pipeline-state --region us-west-2 --name ${CODEBUILD_INITIATOR#codepipeline/} --query 'stageStates[?actionStates[?latestExecution.externalExecutionId==`'${CODEBUILD_BUILD_ID}'`]].latestExecution.pipelineExecutionId' --output text |
use actix_service::{Service, Transform}; | |
use actix_web::{dev::ServiceRequest, dev::ServiceResponse, Error}; | |
use futures::future::{ok, FutureResult}; | |
use futures::{Future, Poll}; | |
use slog::info; | |
// There are two step in middleware processing. | |
// 1. Middleware initialization, middleware factory get called with | |
// next service in chain as parameter. | |
// 2. Middleware's call method get called with normal request. |
Em agosto de 2020, Roney Gomes (https://github.com/roneygomes) pediu recomendações de livros sobre análise de negócio no twitter. Luciana Nunes e Vini Andrade foram duas das pessoas que responderam. As respostas são tão boas que eu não queria que elas se perdessem na efemeridade do twitter. Por isso criei esse gist.
A thread original, que inclui as respostas de Luciana: https://twitter.com/umbravirtual/status/1293306062854950912
A thread que Vini criou a partir do pedido de Roney: https://twitter.com/vbandrade/status/1293331989949566976?s=08
Vale a pena ler as threads porque elas explicam as razões por trás das recomendações. Quem só quiser o nomes do livros pode ler as listas a seguir.
Os livros recomendados por Luciana: