@riley_codes
Senior engineer @ a16z-backed startup. Obsessed with making AI work for developers.
This user has no followers yet.
This user is not following anyone yet.
Forces TDD discipline — writes tests before implementation, catches edge cases you'd miss.
I want to write code using Test-Driven Development. Given this function requirement: [DESCRIBE WHAT THE FUNCTION SHOULD DO] Please: 1. Write comprehensive test cases FIRST (before any implementation) 2. Include: happy path, edge cases, error cases, boundary values 3. Use [Jest/Vitest/Pytest — specify your framework] 4. After writing tests, write the minimal implementation that makes all tests pass 5. Then refactor the implementation for clarity while keeping tests green Show the tests and implementation separately.
Realistic system design interview simulation with a critical interviewer who actually challenges you.
Act as a senior staff engineer at a top tech company conducting a system design interview. The system to design: [e.g. "Design Twitter's feed system"] Walk me through this interview as if it's real: 1. Ask me clarifying questions first (don't assume) 2. Let me answer each question before moving on 3. After requirements are clear, guide me through: capacity estimation → high-level design → deep dives 4. Challenge my assumptions and push back when I'm hand-wavy 5. At the end, give me honest feedback: what I did well, what I missed, what a strong candidate would have said Start the interview now.
Migrates JS to strict TypeScript with proper types, interfaces, and JSDoc.
Convert the following JavaScript code to TypeScript. Requirements: 1. Add proper types for all variables, parameters, and return values 2. Use interfaces or type aliases for complex objects 3. Use enums where appropriate (don't overuse them) 4. Make it strict — no 'any' types unless absolutely necessary 5. Add JSDoc comments for exported functions 6. Note any type assertions you had to make and why JavaScript code: [PASTE JS CODE HERE]
Systematic debugging approach that explains the root cause, not just the fix.
I have a bug and I need help debugging it. Let's approach this systematically. Bug description: [DESCRIBE THE BUG] Expected behavior: [WHAT SHOULD HAPPEN] Actual behavior: [WHAT IS HAPPENING] Code: ``` [PASTE CODE] ``` Please: 1. Form a hypothesis about the root cause 2. Explain your reasoning step by step 3. Suggest the minimal fix 4. Explain how to prevent this class of bug in the future
Get a thorough code review from a simulated senior engineer. Catches real bugs and security issues.
You are a senior software engineer with 15 years of experience doing code reviews. Review the following code with a critical eye. For each issue you find, categorize it as: - 🔴 Critical (security vulnerability, data loss risk, major bug) - 🟡 Warning (performance issue, bad practice, tech debt) - 🟢 Suggestion (readability, style, minor improvement) Then provide a revised version of the code with all critical and warning issues fixed. Code to review: [PASTE CODE HERE]