Skip to content

Instantly share code, notes, and snippets.

View hcastro's full-sized avatar

Henry Castro hcastro

9 followers · 16 following
  • RVO Health
  • New York
View GitHub Profile
@hcastro
hcastro / nextjs-cache-invalidate.md
Created May 7, 2025 20:26
Cache Invalidation playbook (nextjs 15 / RSC)

1. Tell Next.js not to cache anything in this route

Add either (they are equivalent):

// src/app/components/page.tsx ─ very top of the file
export const revalidate = 0;            // Renders on **every** request
// --- or ---
export const dynamic = 'force-dynamic'; // Opt-out of Full-Route + Data cache
@hcastro
hcastro / nyc-rooftops.md
Last active May 4, 2025 13:11
Upscale NYC Rooftop Lounges

Upscale NYC Rooftop Lounges

# Venue Neighborhood Key View Food Focus Reserve?*
1 Nubeluz NoMad / Flatiron 270° Midtown panoramas Luxe tapas (caviar, oysters, jamón) OpenTable – highly
2 Overstory FiDi 360° skyline & harbor Gourmet bar bites (pair w/ award-winning cocktails) Resy – scarce
3 Panorama Room Roosevelt Island Midtown + East River sweep Seafood-forward plates, DJ Sundays Resy/OpenTable
4 Daintree Bryant Park Empire State front-ro
@hcastro
hcastro / publishing-pull-requests.md
Created April 4, 2025 02:49
Best Practices for Publishing Pull Requests in Modern Software Teams

Introduction

Pull requests (PRs) are a cornerstone of collaboration in modern software engineering. A well-crafted PR not only merges code but also communicates context and invites engagement from reviewers. In teams building applications across React Native (mobile), Next.js (web), and Node.js (backend), clear PR communication ensures that all team members – regardless of specialty – can understand and review changes effectively. In fact, a PR’s description and structure can be as valuable as the original task specification (How to Make a Proper Description for a Pull Request). High-quality PRs save time in reviews and reduce back-and-forth clarifications, leading to faster approvals and a healthier code review culture ([How to Make a Proper Description for a Pull Request](https://maddevs.io/blog/how-to-make-a-proper-description-for-a-pull-request/#:~:text=As%20a%20rev

@hcastro
hcastro / git-commit-assistant.mdc
Created April 2, 2025 15:13
git commit assistant
---
description: >
Git Commit Assistant rule to enforce clean,
structured, and traceable commit workflows. This rule should be applied
whenever a developer attempts to stage or commit changes. It ensures that:
- Commits are grouped logically and use conventional commit messages tied to Jira tickets.
- Feature branches are created from `development` with proper naming conventions.
- No direct work is allowed on `master`.
- Sensitive or excluded files (e.g., .env, secrets) are never accidentally committed.
This rule improves collaboration, auditability, and consistency across the codebase,
@hcastro
hcastro / gist:c9869d5d6ac3834fdc0843700c2eff0a
Last active March 21, 2024 09:14
raw activity that doesn't belong to my signed in user
{
"actor": {
"created_at": "2023-08-24T02:31:55.170365Z",
"updated_at": "2024-03-21T09:05:08.998329Z",
"id": "27886570af8249a590a8e933dc9cc464",
"data": {
"Age": 25,
"Children": "Not Provided",
"ChildrenAge": "Not Provided",
"DiagnosedDate": "2000",
@hcastro
hcastro / gist:0ec6d2f7c86466971efbaecacd049217
Created October 24, 2019 18:22
appium 1.15 unknown udid
2019-10-24 18:03:45:119 - [Appium] Welcome to Appium v1.15.0
2019-10-24 18:03:45:167 - [Appium] Non-default server args:
2019-10-24 18:03:45:168 - [Appium] logTimestamp: true
2019-10-24 18:03:45:168 - [Appium] defaultCapabilities: {
2019-10-24 18:03:45:168 - [Appium] usePrebuiltWDA: true
2019-10-24 18:03:45:169 - [Appium] derivedDataPath: /tmp/scratch9PW5T7.scratch/DerivedDataG_0Axd
2019-10-24 18:03:45:169 - [Appium] platformName: iOS
2019-10-24 18:03:45:169 - [Appium] automationName: XCUITest
2019-10-24 18:03:45:169 - [Appium] deviceName: 00008020-001C650A2288002E
2019-10-24 18:03:45:169 - [Appium] app: /tmp/scratch9PW5T7.scratch/share-TLawZk.scratch/app-yr4ROo.ipa