Skip to content

Instantly share code, notes, and snippets.

// ==UserScript==
// @name Show Entity Guids
// @namespace https://www.niche.com/
// @version 1.1
// @description show entity guids
// @author Geoff
// @match https://www.niche.com/*
// @grant none
// @require http://code.jquery.com/jquery-latest.js
// ==/UserScript==
{
"template": "Page",
"config": {
"title": "client-home"
},
"contents": [
{
"template": "client_account_home"
}
]
{
"template": "Page",
"config": {
"title": "CS Home"
},
"contents": [
{
"template": "cs_account_home"
}
]

Less

@max-nth-child: 7;

.make-animation-delay (@index, @delay) when (@index < @max-nth-child) {
  .mega-menu__item:nth-child(@{index}) {
    animation-delay: unit(@delay, s);
  }
  
 .make-animation-delay(@index + 1, @delay + 0.06);

current pattern

top of file:

const _getDependencies = () => ({
  LION_NAME: 'simba',
  roar: _roar,
})

To support adding a conditional link to the user dropdown - these are just my loose notes, any dev picking this up please feel free to do whatever works best for you

  • For logged in users dropdown, logged out dropdown will be unaffected

Current implementation

Loose plan

Gather user demographics from store and pass (as demographics key, so we can later pass other objects by name) into function defined on the user-logged-in.js list entry that determines whether or not the link can show, maybe something like function canDisplay({ demographics }) that just returns a boolean?

  • Lets us re-use this appro

Onboarding

how much information is thrown at us up front, as I clearly didn't absorb it all. Something to think about is how to get people to absorb more, or how to better schedule/layer the intros, or somehow refresh us later with it again.

I started to think of the group I sat in those intro meetings with as my cohort. We all started together, and it might be nice if groups of new people could connect and stay connected somehow. I think it would have been nice to lean on other new people and talk if we were having similar problems, learning curves, questions, etc.

Can we better utilize Tuesday lunches? Interest in chatting with other members of other teams in a dedicated sense - easy to forget to grab coffee with someone if you're both busy. Even interest from folks who have been here a while.

  • Should GitHub handles match Slack username, for consistency?
  • Should we have people get set up in Expensify (week/month 1/etc)?
  • Desks for new folks?