“Justin is a stellar developer. Simple as that. He would take on any project no matter the complexity. I appreciated how well he was able to problem solve and find creative solutions to different roadblocks he would encounter. As a UX Designer myself, he was a wonderful team member I could depend on, ideate with, and build great experiences with. He’s definitely a great asset to any team. ”
Justin Hendrickson
Saratoga Springs, Utah, United States
320 followers
277 connections
320 followers
277 connections
About
I love building cool products and teaching skills that help make the world a better…
Activity
-
An AI engineer talking to customers and prospects at a conference? Sounds like a great idea! It was great talking with credit union leaders at…
An AI engineer talking to customers and prospects at a conference? Sounds like a great idea! It was great talking with credit union leaders at…
Shared by Justin Hendrickson
Experience
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Education
-
-
-
-
-
-
Licenses & Certifications
Recommendations received
2 people have recommended Justin
Join now to viewOther similar profiles
Explore more posts
-
Curtis Kline
My Claude Code workflow went from chaos to calm. Here's the evolution. When I first started building apps with Claude Code, I did what I suspect most people do: "Build me an app that does X." "Fix the feature that doesn't work." Pure vibe coding. Claude is genuinely capable at this. But without structure or documentation, things got chaotic fast. I couldn't remember what we'd built. I'd forget feature ideas before getting around to them. And every time Claude's context window refreshed, we'd both be confused about where we left off. Phase 2: GitHub Issues This worked surprisingly well for a small app. Claude Code can use the GitHub CLI to read, update, and close issues—so I had a single source of truth for what needed doing. I also moved to GitHub Actions for deployments, which tightened up the whole process. But GitHub Issues has limits. The CLI doesn't have a robust feature set. Milestones exist, but the UI is clunky. If I wanted a non-technical collaborator to review progress, I'd have to explain a lot. Phase 3: Linear + Linearis CLI For a more complicated app I'm building now, I moved to Linear and installed the Linearis CLI. Game changer. (https://lnkd.in/g6fUZktk) I now have several projects (groups of features) with tickets inside them. Linear's UI is beautiful and functional—something a collaborator could actually navigate. The GitHub integration works seamlessly. The key insight: when Claude Code plans work on a ticket, I have it create sub-tickets for implementation. Small chunks mean Claude is less likely to hit the context window mid-task. That alone eliminated a lot of the confusion I used to deal with. The workflow still feels new, but (most of) the chaos is gone. Anyone else land on Linear or something else for managing AI-assisted builds? I'd love to hear what's working for you. Anthropic
25 Comments
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top content