Luis Carrasco

U.S. energy demand is surging — don’t get left behind. New gas projects and large industrial loads are reshaping power markets at breakneck speed. In this high-stakes landscape, timely and accurate data is essential. Halcyon’s Data Products, powered by a regularly updated authoritative data catalog of 4.5+ million documents from all 50 public utility commissions, ensure you always have the latest energy market intelligence. Download this guide to see how AI can help power sector stakeholders find new growth opportunities first.

6

The design-to-code handoff is one of the most expensive gaps in enterprise software development. Weeks of engineering time spent interpreting Figma files, reconciling spacing math, and rebuilding what designers already specified. On March 30, join Aditya Karra, Blitzy's Founding Designer, and Ben Bergerson, Senior AI Solutions Consultant, for a walk thru of Blitzy native Figma-to-production capability. No prototypes. No Refine PR. Production-ready code. - Every design token read before a single line of code is written - Responsive output across five viewports from one desktop frame - A new feature integrated into an existing codebase, brand-aligned, checked directly into the repo Designers and product teams can now move at the speed of design. Come see what that looks like in practice. Register with the link in the comments. March 30 | 12pm ET | Free with live Q&A #Blitzy #Webinar #Figma #Platform40 #FrontendDevelopment #EnterpriseAI #ProductVelocity

29

1 Comment

Thrilled to share my latest article: "The Mixed-Initiative Interface: Designing Control Handoffs Between Humans and AI." In a world where AI handles more decisions, the real UX frontier is the seamless transfer of control—ensuring humans can step in without losing context, state, or accountability. We're moving beyond rigid autonomy to dynamic systems where handoffs are graceful and empowering. Key insights include: - The Handoff Problem: Mixed-initiative systems allow bidirectional control shifts; the challenge is preserving state during transitions to avoid confusion. - Decision Ledger: An append-only log of actions, confidence scores, and reasoning to brief humans on AI's prior steps. - Non-Destructive Overrides: Use proposal queues for AI suggestions that can be reviewed or modified without halting workflows. - Calibrating Confidence: Dynamic thresholds based on consequence, reversibility, and confidence—err toward escalation to build trust. - Reversibility and Intervention Windows: Leverage event sourcing for undos and strategic delays to enable human oversight in high-stakes scenarios. This is essential for anyone building AI-powered products: think pricing optimization, fraud detection, or any domain blending human judgment with machine efficiency. Does this align with challenges you're facing in your work? Read the full piece here: https://lnkd.in/dX_y7YMa

5

The design-to-code handoff is one of the most time consuming gaps in enterprise software development. Weeks of engineering time spent interpreting Figma files, reconciling spacing math, and rebuilding what designers already specified. On March 30, join Aditya Karra, Blitzy's Founding Designer, and Ben Bergerson, Senior AI Solutions Consultant, for a walk thru of Blitzy native Figma-to-production capability. No prototypes. Production-ready, pixel-precise, front-end code. Our team will walk through - How Blitzy honors your component library and design tokens, with atomic-level UI accuracy to the original Figma file - Producing responsive behavior across all different front-end breakpoints from a single frame - A new feature integrated into an existing codebase, brand-aligned, checked directly into the repo Designers and product teams can now move at the speed of design. Come see what that looks like in practice. Link to register in the comments. March 30 | 12pm ET | Free with live Q&A #Blitzy #Webinar #Figma #Platform40 #FrontendDevelopment #EnterpriseAI #ProductVelocity

32

1 Comment

💥 I just found a foundational flaw in Claude. All models, all interfaces. Repro steps below: 1. Go to Claude settings 2. Attempt to update your email address 3. If you can’t find how to do it on your own, ask Claude how to change your Claude email address 4. Validate that Claude is not hallucinating by going to https://support.claude.com and searching for “How do I change the email address associated with my account?” 5. Shake your head and think “sorry users, I know we kind of slid past this when you signed up. Hope the email you used to sign up never gets compromised or needs to change – magic links or SSO are the only option (darn it). And if it does, hope you didn’t buy an annual PRO plan because no refunds / transfers even if to the same human ✌ (grrrr…)” Perhaps this behavior is the result of conscious prioritization based on a thorough understanding of needs / trade-offs. If this behavior was an oversight, then based on prior trips on the modernization train, this could be a massive slog of tech debt. Particularly in a hyper-growth business dependent on uninterrupted & high-integrity data access / entitlements / provenance. Product people – let's use this moment to build foresight! - Don’t abdicate PM or UX from “technical” discussions about data models, identity, or access control – decisions within these domains have incredible implications - Customer onboarding & admin workflows are foundational CX, not afterthoughts - If you’re using Claude Code, invest in Git + GitHub integration for improved resilience (and much more)

3

Most teams don't struggle with speed anymore. They struggle with building the right things. That's exactly where my brother thrives. He's a Principal Product Designer who brings real product thinking into design. The kind of person who helps teams cut through complexity and focus on what matters. If you're building serious products and need that level of thinking, take a look at his post below.

5

2 Comments