I hereby claim:
- I am usrrname on github.
- I am jenc (https://keybase.io/jenc) on keybase.
- I have a public key ASAK7sMRMw1jcb09j8bHzMnwyXToNAobumcjX9mAP8qJIwo
To claim this, I am signing this object:
| <!doctype html> | |
| <html> | |
| <head> | |
| <style> | |
| *{ | |
| font-family:'Open Sans', Arial, Sans-serif; | |
| } | |
| body{ | |
| padding:1em; | |
| } |
| const reverseWords1 = (string) => { | |
| let newString = ' '; | |
| let items = string.split(' '); | |
| let results = ''; | |
| for (let i=items.length; i>=0; i--) { | |
| results += items[i] + newString; | |
| String(results) | |
| } | |
| return results; |
| #!/usr/bin/env bash | |
| echo "registry=https://pkgs.dev.azure.com/${ORG_NAME}/_packaging/${PACKAGE_NAME}/npm/registry/ | |
| always-auth=true" >> .npmrc |
| trigger: | |
| - main | |
| - feature/R20-22-azure-piplines | |
| variables: | |
| - group: radius-angular | |
| - name: projectName | |
| value: $[variables.PROJECT_NAME] | |
| - name: feedName | |
| value: $[variables.FEED_NAME] |
I hereby claim:
To claim this, I am signing this object:
So, nuxt problems:
• SSR rendering patterns and data hydration on server was not as maturely developed as NextJS ... this resulted in a lot of console noise and rendering flash
• at my last work we ended up switching the app to completely do client side rendering to improve page speed 😆
• overly strict foldering opinions esp for component naming... remember how all components would by default inherit the parent folder name?
Components like /Foo/Bar/Thing.vue would become named as <FooBarThing/> wherever you want to import it due to its build opinions.
• auto-imports were possible because at build time nuxt generates a series .d.ts in .nuxt/ of ALL composable and components such that they are globally namespaced. If you don't know about this it can be very easy to create conflicting and duplicate namespaced component prop types
| { | |
| "meta": { | |
| "theme": "professional" | |
| }, | |
| "basics": { | |
| "name": "Jen Chan", | |
| "email": "6406037+usrrname@users.noreply.github.com", | |
| "website": "https://jenchan.biz", | |
| "summary": "A software developer and tech lead with 9 years of experience across UX and product engineering, and over a decade of contribution to open source and online communities. Having worked on teams from early stage startups of 3 devs to an enterprise org with 3000 devs to deliver milestones on time and on budget, I'm attuned to developer pain points and delivery friction. I've turned my attention to improving the experience of building and maintaining software through developer enablement, tooling, SDK and automation work.", | |
| "location": { |
| name | tmux-processes |
|---|---|
| description | Run any long-running process in a named tmux session so it survives across Claude sessions. Use when starting any process that won't exit on its own — dev servers, clusters, watchers, builds, test runners, tail/follow commands, daemons, REPLs, port-forwards, agents, etc. — or when reading output from a previously started one, or when the user mentions tmux sessions, windows, or panes directly. The Bash tool's `run_in_background` only persists within the current Claude session; use this skill instead for anything that should outlive the session. |
Applies to any long-running process — examples below (kilter up, pnpm dev, tilt up) are illustrative, not a closed list. If the command doesn't exit on its own and you want to read its output later (this session or a future one), put it in tmux.