u/Substantial_Ask2311 — reddlx

Streamlining NEC/IEEE calculations: Is anyone else using a digital cheat sheet for daily design math?

I’ve been working on a project to solve the constant context-switching between design software, 500-page NEC PDFs, and custom Excel sheets for basic calculations.

I ended up building a personal workflow I call GridPulse... a chrome browser extension sidebar that consolidates a few things I use daily:

Fault Currents: Short-circuit analysis based on IEEE C37 / IEC 60909 (including X/R and transformer Z).
NEC 310.16: Automatic derating for ambient temp and conduit fill (60/75/90°C ratings).
Motor Calculations: FLA and OCPD sizing per Table 430.250.

The main priority was keeping it 100% local-storage based (Chrome Storage API) so I don't have to worry about project data or NDAs being compromised by external servers.

I am looking for some "math-checks" or workflow feedback from the community:

How are you guys currently handling voltage drop limits for feeders vs branch circuits—do you strictly follow the 3%/5% NEC suggestion or use custom limits?
Has anyone integrated local AI (like Groq) into their calculation reviews yet for code citations, or is the risk of "hallucinations" still too high for professional engineering?
What is the one "quick ref" table you find yourself looking up the most in a typical week?

Curious to hear some workflow tips from other designers here!

reddit.com

u/Substantial_Ask2311 — 10 hours ago

▲ 0 r/ProductManagement_IN

Tired of "Who said what?" and searching through 100 Slack threads to find a single product decision. So I built a fix.

Hi everyone,

If you work in a typical Indian tech setup...high-speed sprints, 10 daily "sync" meetings, and requirements that change faster than the weather.. you know the pain of Decision Debt.

We make dozens of calls every week: architecture trade-offs, dependency pivots, RICE scoring. But the why behind those calls always ends up buried in a Slack thread or a dead Google Doc. Six months later, when leadership asks why we didn't go with Option B, nobody remembers.

I got tired of the "documentation overhead," so I built "Decision Deck", a lightweight Chrome sidebar to log decisions instantly without leaving Jira or GitHub.

How it works (for those of us in the trenches):
- Alt+D Capture: Log a decision, the rationale, and the "One-way/Two-way door" risk status immediately. No context switching.
- Automatic Context: It saves the URL of the Jira ticket or PRD you're currently on, so the "source of truth" is always linked.
- In-Browser RICE Calculator: Stop maintaining that one prioritization spreadsheet that always breaks. Score features directly in the sidebar.
- 100% Local & Private: I know how strict our corporate security is. Everything is stored locally in your browser (Chrome Storage API). No accounts, no servers, no data leaving your machine.

I’m looking for some honest feedback....

Is "decision tracking" something you actually struggle with, or have you found a better way?

For those in high-pressure roles, does the RICE framework work for you, or do you prefer MoSCoW?

It’s completely local (Chrome Storage API), so there are no security concerns regarding external data hosting. Would love any feedback on the workflow!

Chrome Extension Link: https://chromewebstore.google.com/detail/decision-deck/dibleooihnljeaclfilhlifdbjinchoa

u/Substantial_Ask2311 — 11 hours ago

▲ 1 r/ProductManagement

I got tired of losing product decisions in Slack threads and meeting notes, so I built a Chrome extension to track them

We have all been there..Six months into a project, someone asks why we decided on Option B over Option A, and you’re stuck digging through 400 Slack messages and a dead Confluence page trying to find the rationale.

As a PM/TPgM, we make dozens of calls daily..dependency trade-offs, architecture pivots, RICE scoring. I needed a "Decision Journal" that didn't require me to open another tab or a heavy Notion doc.

I built Decision Deck, a lightweight Chrome extension specifically for this...

What it does:
- Alt+D Capture: Hit a shortcut on Jira, GitHub, or any PRD to log a decision instantly. It auto-saves the source URL for context.
- Structured Metadata: Track "One-Way vs. Two-Way Doors," confidence levels, and stakeholders.
- In-Browser RICE: A built-in calculator so you can stop maintaining that one "Prioritization" spreadsheet that always breaks.
- 100% Local/Private: No accounts, no servers. Your data stays in your browser storage (crucial for sensitive roadmap stuff).

It has been a game-changer for my own Product Review prep. I would love for this community to try it out and tell me what’s missing!!!

I am calling it "Decision Deck", check out the chrome extension on Chrome Webstore. I am not allowed to link it here per the rules (except on Fridays!), but I would love to hear how others are solving the "where did we decide that?" problem...

reddit.com

u/Substantial_Ask2311 — 11 hours ago