Mark Vilrokx mvilrokx

description

argument-hint

tools

handoffs

Researches topics in depth with comprehensive source analysis and synthesis

What topic or question would you like researched?

search

new

Azure MCP/search

github/search_code

github/search_issues

github/search_repositories

youtube/*

runSubagent

usages

vscodeAPI

problems

changes

testFailure

fetch

githubRepo

label	agent	prompt
Save Research	agent	Save the research findings to a markdown file, as is

When to Use Each Version

claudette-mimir.md ⭐ NEW!!!

✅ Full integration with Mimir's memory bank
✅ Graph functions enable multi-hop reasoning

CLICK HERE-> Claudette Mimir

Mimir Memory Bank

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

Clarify and agree on the scope of the system

User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?

Raspberry Pi VPN Router

This is a quick-and-dirty guide to setting up a Raspberry Pi as a "router on a stick" to PrivateInternetAccess VPN.

Requirements

Install Raspbian Jessie (2016-05-27-raspbian-jessie.img) to your Pi's sdcard.

Use the Raspberry Pi Configuration tool or sudo raspi-config to:

This is the follow up to a post I wrote recently called From Require.js to Webpack - Party 1 (the why) which was published in my personal blog.

In that post I talked about 3 main reasons for moving from require.js to webpack:

Common JS support
NPM support
a healthy loader/plugin ecosystem.

Here I'll instead talk about some of the technical challenges that we faced during the migration. Despite the clear benefits in developer experience (DX) the setup was fairly difficult and I'd like to cover some of the challanges we faced to make the transition a bit easier.

Hi Nicholas,

I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:

The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't

Essential JavaScript Links

I no longer mantain this list. There are lots of other very comprehensive JavaScript link lists out there. Please see those, instead (Google "awesome JavaScript" for a start).

	# Change these variables as necessary.
	main_package_path = ./cmd/example
	binary_name = example

	# ==================================================================================== #
	# HELPERS
	# ==================================================================================== #

	## help: print this help message
	.PHONY: help

	#!/usr/bin/node
	const Promise = require('bluebird')
	const config = require('./config.json')
	const knex = require('./lib/knex')(config.database).connection()


	const mock = () => ({ user_id: Math.floor(Math.random() * 999) + 1, payload_type: 'foo', attributes: JSON.stringify({}) })


	const before = (t) => {

	/**
	* Outputs the result of a Sequelize query for JSONAPI
	*
	* e.g.
	* let foo = yield models.Foo.findById(this.params.fooId);
	* this.body = output(foo);
	*
	* Results in:
	*
	* {