kernel-memory-dump

   OArguments arguments = new OArguments();
        arguments.add(Arrays.asList(1));
        JSONObject argsJSON = new JSONObject();
        JSONObject kwargs = new JSONObject();
        JSONObject context = new JSONObject();


        try {
            argsJSON.put("kwargs", kwargs);

kernel-memory-dump

// https://stackoverflow.com/questions/52928670/jwt-role-authentication-in-controller-asp-net-core-2-1

// MIDDLEWARE CODE 
// MIDDLEWARE CODE
public class AuthenticationMiddleware
{
    private readonly RequestDelegate _next;

    // Dependency Injection
    public AuthenticationMiddleware(RequestDelegate next)

kernel-memory-dump

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

---

kernel-memory-dump

/**
 * Retrieves all the rows in the active spreadsheet that contain data and logs the
 * values for each row.
 * For more information on using the Spreadsheet API, see
 * https://developers.google.com/apps-script/service_spreadsheet
 */
function readRows() {
  var sheet = SpreadsheetApp.getActiveSheet();
  var rows = sheet.getDataRange();
  var numRows = rows.getNumRows();

kernel-memory-dump

// see https://alligator.io/angular/takeuntil-rxjs-unsubscribe/


//  UsersModule  ==========================================================================

{
  path: 'users',
  component: UsersComponent,
  resolve: {

kernel-memory-dump

setTimeout(async () => {
    sync('./topkek.txt', "kek");
});
function sync(path, data) {
    const fs = require('fs');
    options = {
        encoding: 'utf8',
        mode: 438 /*=0666*/
    };

kernel-memory-dump

    // VPC
    const vpc = new ec2.Vpc(this, 'VPC');

    // Security group
    const webSg = new ec2.SecurityGroup(this, 'WebSG',{
      vpc: vpc,
      allowAllOutbound: true,
      description: "Web Server Security Group"
    });
    webSg.addIngressRule(ec2.Peer.anyIpv4(), ec2.Port.tcp(8080), 'Web from anywhere')

kernel-memory-dump

; BOOTSEC signature bruh 
bits 16 
org 0x7C00 

start: 

jmp entry

printmsg db "TOP KEK",13,10,0 

kernel-memory-dump

What Hiring Should Look Like

This is definitely not the first time I've written about this topic, but I haven't written formally about it in quite awhile. So I want to revisit why I think technical-position interviewing is so poorly designed, and lay out what I think would be a better process.

I'm just one guy, with a bunch of strong opinions and a bunch of flaws. So take these suggestions with a grain of salt. I'm sure there's a lot of talented, passionate folks with other thoughts, and some are probably a lot more interesting and useful than my own.

But at the same time, I hope you'll set aside the assumptions and status quo of how interviewing is always done. Just because you were hired a certain way, and even if you liked it, doesn't mean that it's a good interview process to repeat.

If you're happy with the way technical interviewing currently works at your company, fine. Just stop, don't read any further. I'm not going to spend any effort trying to convince you otherwise.

kernel-memory-dump

{
  "env": {
    "browser": true,
    "node": true,
    "es6": true
  },

  "plugins": ["react"],

  "ecmaFeatures": {