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

JM-Mendez

# push all branches to orgin
git push --force-with-lease --all origin

# rebase and update all branches before leading up
# to this branch from main
git rebase --update-refs main feature

JM-Mendez

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

JM-Mendez

# 1. install vscode in path
# 2. set vscode as git editor in terminal
git config --global core.editor "code --wait"

# 3. write git message using vscode
git commit -m

JM-Mendez

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

JM-Mendez

# After updating .gitattributes, this will remove the local files and get them from the index
# with the correct line endings.

git rm --cached -r . 
git reset --hard

JM-Mendez

/*------------ 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

JM-Mendez

Currently:

[What happens now in the regression]

---

Expected:

[What the correct behavior should be]

---

STEPS TO REPRODUCE:

[If needed, add steps to reproduce]

JM-Mendez

;; based on @babygau's answer here https://stackoverflow.com/a/40559502
#NoEnv ; recommended for performance and compatibility with future autohotkey releases.
; #UseHook
#InstallKeybdHook
#SingleInstance force
#WinActivateForce
SetTitleMatchMode, 2
SendMode Input

GroupAdd, vscode, ahk_exe Code.exe

JM-Mendez

git config --global core.editor code --wait