I can't get the trunk-based development flow. I understand the advantages for introducing new features to the app (flags are good for A/B testing, fewer merge conflicts).
But I can't understand how developers do refactoring with trunk-based flags. Also, do the flags stay there forever, or what is the best flow for this?
Can you give me a deep dive into how your teams handle this in production?
In Claude Code Web, I am getting Overloaded error. What's going on?
While developing, I don't really care about the Claude model, and just stick withthe preselected one (most often Sonnet 4.6).
Is anyone doing the same? What is the best way to optimize the model selection. Is there any auto model feature?
Any tips are welcome, I would like to optimize the token usage.
I am creating MCP for building plans to help AI to have feedback loop for its design (collisions, connections, relevance...).
Final step is to export all the created floorplan data back to the app. But here is the problem: It consumes lot of tokens because AI is in the middle of app and MCP. Is there some better way to get the exported data from MCP?
I’m building an app with AI chat, and now I’m going to add widgets on top of the AI responses — so you can get more user-friendly output or even interact with it instead of just reading text.
So, I’m curious:
For me, one annoying thing is when AI asks multiple questions in a single message — there’s no UI to answer them one by one, you just have to type all answers in one message. For example, Claude has already added a simple UI for this.
Looking forward to any ideas or experiences.
In development with AI, there is a need to not only write code, but tests as well. AI can help with both.
So here is my question — what do you focus more on: code or tests?
Or in other words, what is the better workflow:
Which workflow better suits your day-to-day work?
I am curious how other developers handle their git/branch workflow, because mine feels almost like that everyone has to figure out this approach as well.
Every time I start some development task, I:
So basically, before I start coding I have empty draft merge request every time. When everything is done in the task I just flip it out of draft and assign a reviewer.
This helps me track what I am working on and never needs to look for the branch I was working on.
It works very well for me, but now I started wondering if its standard / good practice or just me?
Do you do the same, or is there a better system I missed?
I started to hate props types that include the component name – like DashboardProps, MyTableProps, etc. Now I just name it simply Props every time, without component name prefix. Its better for refactoring and full text search.
Exporting props?
Only case, you should name it, is if you export props, you should use a unique name tied to the component. Yeah, make sense, but I don’t think you every really need to export props (at least in most cases).
If I need props of ComponentA somewhere else, I prefer to get the type like this:
type WrapperProps = ComponentProps<typeof ComponentA>
Why:
ComponentB needs props of ComponentA, you’re probably already using ComponentA there = no extra import just for the type (for example wrapper components)ComponentA imported yet (eg. hook), you can still do:​
import type { ComponentA } from './ComponentA';
type ComponentAProps = ComponentProps<typeof ComponentA>;
Curious how others do this – using ComponentNameProps or Props, and do you export wrapper props?