John Mendez JM-Mendez

%%tana%%

Cheat Sheet
- ✨ Tana Expressions
  - Title #tana-expression
    - Description:: A title expression composes values from the node into a title.
    - Attributes:: Search for Tana "Title" Attributes
  - Search #tana-expression
    - Description:: The search expression consists of a flat list of match-clauses that must be true for a node to match the search.
    - Attributes:: Search for Search Attributes + Search for Search Field Values
🧩 Tana Attributes

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

Logseq Plugin Setup Guide

[WIP] Logseq Plugin System is currently under Alpha Testing phase.

For Developers

In this short guide, it will walk you through the steps needed to set up your development environment for writing and running a hello world simple inside of Logseq Desktop Client. You know Logseq Plugin based on Web Technologies composed of JS & HTML & CSS, but neither are mandatory, you can develop plugins use any language which can be translated to javascript (Logseq made by Clojurescript!). We will use Typescript to demonstrate this sample. Because there is a type definition file to make development experience even better.

Install Node.js and NPM

Steps:

Download the latest zsh package: https://packages.msys2.org/package/zsh?repo=msys&variant=x86_64

Example:

zsh-5.7.1-1-x86_64.pkg.tar.xz

Set up cmder to use msysgit / bash by default

Install cmder_mini (msysgit is already installed, so no need for full version)
In Cmder, open settings: Win + Alt + P
Under Startup > Tasks, add a task called {bash} with the following settings:
- Task parameters (set icon):
  - For Cmder icon: /icon "%CMDER_ROOT%\cmder.exe"
  - For Git icon: /icon "C:\Program Files (x86)\Git\etc\git.ico"
- Commands (open Git's bash shell):
"C:\Program Files (x86)\Git\bin\sh.exe" -l -new_console:d:%USERPROFILE%

Using JSDOC-Based TypeScript

Get Started

Choose your editor

WebStorm, Rider
- Partial support, not enough intelli hints
- Toggle on TypeScript language service
VSCode

	/------------ CUSTOM COLORS ------------------/

	/*
	Title: Custom colors for Logseq
	Author:: @CatoMinor3
	Version:: 1
	Date:: February 6, 2021
	Support:
	- Paypal: https://www.paypal.me/catominor3
	- Patreon: https://www.patreon.com/catominor

	# Copied and modified from https://dev.to/cravacuore/comment/i7g0
	# Inspired by making a mixture the following themes:
	# robbyrussell + arrow + lambda
	# changing some colors and elements positions

	local ret_status="%(?:%{$fg_bold[grey]%}λ :%{$fg_bold[red]%} λ )"

	# ellipsis https://github.com/ohmyzsh/ohmyzsh/issues/7525#issuecomment-456074298
	PROMPT=' ${ret_status}%{$fg[magenta]%}%c %{$fg[black]%}git:(%{$fg[cyan]%}%30>...>$(git_current_branch)%>>%{$fg[black]%}$(parse_git_dirty)%{$reset_color%} ➤ %{$reset_color%}'

	function New-Symlink {
	<#
	.SYNOPSIS
	Creates a symbolic link.
	#>
	param (
	[Parameter(Position=0, Mandatory=$true)]
	[string] $Link,
	[Parameter(Position=1, Mandatory=$true)]
	[string] $Target

	import React, { useContext } from "react";
	import Dashboard from "./Dashboard";
	import Login from "./Login";
	import AppContext from "./AppContext";

	export default () => {
	const { machine, error } = useContext(AppContext);
	console.log("executing App component...");

	return (