speakingcode

Manage Dotfiles with Git

Method 1: Bare Git Repository

This approach uses only Git, without symbolic links or extra tools. It involves creating a bare repository in your home directory and using an alias to manage it.

Setup Steps

Initialize a bare repository:

git init --bare $HOME/.dotfiles

speakingcode

Statistics and Data

Global/National

• worldwide stats by nation, near real-time:
  https://www.worldometers.info/coronavirus/

• worldwide daily deaths and new cases:
  https://www.worldometers.info/coronavirus/worldwide-graphs/#daily-cases
  https://www.worldometers.info/coronavirus/worldwide-graphs/#daily-deaths

speakingcode

~|| chicken breast • cauliflower • carrots • broccoli • cucumber ||~
•
• 𝓯𝓸𝓵𝓵𝓸𝔀 ~@loveandplate~ 𝓽𝓸 𝓼𝓮𝓮 𝓶𝔂 𝓬𝓻𝓮𝓪𝓽𝓲𝓸𝓷𝓼 •
•
• chicken breast/rosemary/black pepper
• purple cauliflower/nutmeg/coriander/almond milk
• carrots/honey
• broccoli/orange cauliflower/garlic
• cucumber/vinegar/dill
•

speakingcode

regla rails project:

docker run -it --rm --user "$(id -u):$(id -g)" -v "$PWD":/usr/src/app -w /usr/src/app rails rails new --skip-bundle webapp

api mode:

docker run -it --rm --user "$(id -u):$(id -g)" -v "$PWD":/usr/src/app -w /usr/src/app rails rails new --skip-bundle webapp --api

speakingcode

suppose we want to get the operator details about the operator for a particular user's location to minimize the size of payloads, the REST api doesn't give back all the relational data for each model, only foreign keys to the related models.

so we fetch the user info (by id), and in the xample we assume the user info has a location_id, then we fetch the location whose id matches, then we assume that has a operator_id. then we get the operator whose id matches that

callbacks:

//chaining three requests
const getOperatorForUsersLocation = (user_id, successCallback, errorcallBack)  => {

speakingcode

all of this is writtern assuming you want to seriously pursue being a badass in infosec. adjust accordingly

basics/computer fundamentals

ok so the thing to remember is security is very broad. there's a sort of core set of topics but there's just so much one off stuff, because ultimately it's all about access to information and services and in reality information systems are composed of networks of myriad devices running myriad software. there are many vectors of attack and many points of failure.

offensively security is all about using things in unintended ways and understanding the 'unexpected' outcomes, manipulating them for favor. defensively, it is about predicting unintended uses and ensuring the design of systems protects against them. both require intimate knowledge of the system. so the foundation of any good security expert is systems knowledge. that said, the obvious things you need to understand at least basics about:

• computer hardware and architecture
  • processors, instruction sets
• me

speakingcode

[18:08] <@speakingcode> isn't everything jsut code though/
[18:08] <@speakingcode> do words really have meaning? every word is defined with other words
[18:09] <@speakingcode> every concept is just a represenation of something else
[18:09] <@speakingcode> welcome to the deconsturctionist terror
[18:09] <@speakingcode> this is why math is divine
[18:09] <@speakingcode> numbers are the only thing to have inherent meaning
[18:09] <@speakingcode> _only_
[18:11] < razorsharph> The problem with learning how to program and code by myself online is that when I start learning one thing I end up having to stop because I dont understand something and then have to go and learn a whole new thing in order to understand the initial 
                       problem
[18:11] < razorsharph> And it happens over and over and over

speakingcode

//Node Code
//
var base64 = require('base64-stream');
var request = require('request').defaults({encoding: null});

exports.show = function (req, res) {
  request.get(apiURL + req.params.slug,
    function (error, response, body) {
      if (response) {

speakingcode

package com.argodata.match.empi.tools.hl7log

import org.springframework.stereotype.Component

/**
 * Created by dlissner on 8/22/14.
 */
@Component
class Hl7LogParser {
    def messageTypePattern  = ~/ADT\^A[0-9]{2}/,

speakingcode

// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console