luodaint

6 ms·

1.
Show HN: Feedjolt a Feedback tool wiith unlimited seats and developer friendly(feedjolt.com)
3 points by luodaint 4mo ago|0 comments
2.
Ask HN: Did agentic coding change the way you think about commit granularity?
1 points by luodaint 4mo ago|0 comments
3.
by luodaint 4mo ago
Agentic development transforms the scope of work. Once a session is committed to having one topic from the get-go — one move, one service, one abstraction — the diff generated from such a session is atomic by construction. Committing happen
4.
by luodaint 4mo ago
For organizations that make this an operational reality rather than a slogan, there is likely to be at least one individual for each product development cycle that has had recent contact with a customer. Not from reading a support transcrip
5.
by luodaint 4mo ago
Data from six months of production from one SaaS codebase provides a more limited response. Maintainability doesn't depend on the level of AI usage. Maintainability depends on the discipline during diff reviews. Good sessions: One topi
6.
by luodaint 4mo ago
Not those carefully designed constraints that I set up from the beginning, but short-term ones that I came up with after an agent failed in some way: "Validate JWT at the route level, not the component." "Call workspace provi
7.
by luodaint 4mo ago
Your extensions in VSCode have ambient access to your filesystem, your tokens, and your environment. The servers of tools like Claude Code or Cursor have that ambient access too. This was justified for Nx Console's purposes. This is ju
8.
by luodaint 4mo ago
In any case, once the agent session finishes, the constraint file for the next session is written by the same individual. In this case, if the individual didn't read every output line by the agent, he will not know what to include in t
9.
by luodaint 4mo ago
When it comes to the business logic of production use, this particular failure type is less obvious compared to benchmarking tasks. Benchmarking involves having the answer already known — it helps detect mismatches easily. Business logic pi
10.
Ask HN: Parallel agent code writers, how do you stop them from clashing quietly?
2 points by luodaint 4mo ago|0 comments
11.
by luodaint 4mo ago
Benchmarks measure turn-level capabilities: you feed a task into the system and then grade the result. Capability for production-level usage concerns session-level decision making: does the agent know when to stop editing, retain the right
12.
by luodaint 4mo ago
If you don't know what exactly the user needs, the AI feature is the pitch itself. "Powered by AI" is something to say when you do not know how to sell the outcome. It's also something to develop when you have not set up
13.
by luodaint 4mo ago
Metric that measures the quality beyond simple tokens count: correction loop frequency. When grep does not find a file of interest, the agent does not fail; it will continue working on an incomplete context. For a monolingual code base, the
14.
by luodaint 4mo ago
"The problem is that there are several bottlenecks internally," which include the requirements, specs, and testing. Another one not mentioned in the article. Before you had faster implementation times, something would take six wee
15.
by luodaint 4mo ago
Bearer tokens using mcp-remote are the pragmatic way forward out of the authentication mess. Spec-based implementations of OAuth 2.0/2.1, including dynamic client registration and token exchanges, are absolutely necessary on a large sc
16.
by luodaint 4mo ago
The difference that affected my approach: CLAUDE.md includes three types of content, which function differently. Facts (directory organization, commands, references in docs), always work. There’s no discussion here. Constraints related to r
17.
by luodaint 4mo ago
When an agent writes a component, the styles come along with the JSX. "flex items-center gap-4 bg-purple-600 rounded-lg" doesn’t require any mental context switch to a separate stylesheet file. Custom classes force you into a sepa
18.
by luodaint 4mo ago
Those sessions which stayed together had something in common: singularity of concern. 1 session = 1 feature, 1 bug, 1 migration. As soon as you have a session covering several subsystems, the diff becomes too large to read properly, and pro
19.
by luodaint 4mo ago
As a result of shipping a working product for six months with Claude Code integrated into SaaS production, the only surviving constraints had all been less than 50 lines: migrations' generation vs execution conventions, authentication
20.
by luodaint 4mo ago
The idea of the Pydantic-as-code-smell hinges on the objective being type-safety throughout the codebase. It isn't the aim when an agent creates the majority of the internal logic. The winning architectural approach: enforcement at the
21.
by luodaint 4mo ago
The problem is that you create an HTTP client for each incoming request. In other words, you recreate SSL context and cause reference cycles with each request. From the memory point of view, the program seems to have a memory leak. However,
22.
by luodaint 4mo ago
There is an iterative kind which applies specifically to the code-writing agents. Accepting the output of your coding assistant without checking whether it is correct will cause the loss of knowledge about your codebase. Context files, such
23.
by luodaint 4mo ago
Drop-the-database events occur whenever the review process is bypassed. It’s “Just run it; the agent wrote it” that undermines trust. The migration may be semantically correct yet practically incorrect, such as renaming a column to break a
24.
by luodaint 4mo ago
The framing of the "career-ending" doesn't get what's really changing. As a solo founder, I've shipped a complete multi-tenant SaaS product: auth, multi-tenancy, webhooks, multiple programming languages, all done vi
25.
by luodaint 4mo ago
My mindframe about error messaging: Errors are just a form of routing decision. The quality of the error message lies in the destination, not the message itself.
26.
by luodaint 4mo ago
The article is all about technical communication — diagrams, architectural discussions, code snippets. The more difficult piece to communicate is product sense: which user feedback indicates a genuine trend, when a feature request is a work
27.
by luodaint 4mo ago
Good point about subjectivity; it depends entirely on what you are reviewing for. Static typing holds more ground while making assumptions about contracts between components in huge codebases written by many developers. But in the realm of
28.
by luodaint 4mo ago
But under this frame, it appears that the developer's task involves prompt engineering. This is not the case. Even if an agent generates 90% of the code, each and every diff is going to be in my review queue. Code readability of Python
29.
by luodaint 4mo ago
The architecture assignment that I found most useful did not come from a book. It involved the attempt to articulate my system to an agent session starting with no background information at all. If the agent cannot deduce the constraint, th
30.
by luodaint 4mo ago
Notable that in each step, there’s an added abstraction; specifically, an authentication abstraction is the hardest one to reverse. Using a passwordless login from scratch (magic link + Google OAuth2, sessions stored in Postgres without an

More ›