One philosophy is to consider code as scrap, a disposable byproduct<\/strong>.<\/strong>
It is non-technical people who typically embrace this philosophy. They review the outcome and largely ignore the code. The focus is on the prompts used to produce the desired outcome. Agents swarming and Vibe coding are examples of this philosophy.
The other philosophy is to consider code as a permanent asset.<\/strong>
This is because the code’s internal quality influences the external quality of the final product, including how easily it can be operated, used, supported, maintained, and evolved. AI-assisted coding and Inline suggestions are examples of this philosophy.<\/p>\n\n\n
![\"\"](\"https:\/\/www.smharter.com\/blog\/wp-content\/uploads\/ai-techniques-and-quality.png\")
<\/figure>\n<\/div>\n\n\n<\/p>\n\n\n\n
Today’s LLMs’ limitations still force a choice: hyper-speed or quality<\/strong> <\/p>\n\n\n\n \n\t <\/p>\n","protected":false},"excerpt":{"rendered":" Broadly speaking, AI-coding techniques fall into two distinct and alternative philosophies, you don’t want to confuse or mix. <\/p>\n","protected":false},"author":2,"featured_media":3589,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-3586","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai-assisted-coding"],"_links":{"self":[{"href":"https:\/\/www.smharter.com\/blog\/wp-json\/wp\/v2\/posts\/3586","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.smharter.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.smharter.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.smharter.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.smharter.com\/blog\/wp-json\/wp\/v2\/comments?post=3586"}],"version-history":[{"count":10,"href":"https:\/\/www.smharter.com\/blog\/wp-json\/wp\/v2\/posts\/3586\/revisions"}],"predecessor-version":[{"id":3605,"href":"https:\/\/www.smharter.com\/blog\/wp-json\/wp\/v2\/posts\/3586\/revisions\/3605"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.smharter.com\/blog\/wp-json\/wp\/v2\/media\/3589"}],"wp:attachment":[{"href":"https:\/\/www.smharter.com\/blog\/wp-json\/wp\/v2\/media?parent=3586"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.smharter.com\/blog\/wp-json\/wp\/v2\/categories?post=3586"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.smharter.com\/blog\/wp-json\/wp\/v2\/tags?post=3586"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
While we try to move toward a future of fully autonomous AI-orchestrated, multi-agent AI code generation, current LLMs are not there yet<\/span>. Even within a Human-driven approach, like for example AI-assisted coding, today’s LLMs gradually introduce, under the radar, small problems like code inconsistencies and sub-optimal design choices. These small issues accumulate over time, eventually compromising code readability, maintainability, evolvability, and system security, reliability, performance, scalability, etc.<\/p>\n\n\n\n
At this stage of the AI revolution, hyper<\/strong><\/strong>–speed still comes at the cost of quality.<\/strong> Choosing the right AI coding technique and philosophy requires a careful evaluation of the size\/maturity\/criticality of the product one is developing, and the expectations of its users:<\/p>\n\n\n![\"\"](\"https:\/\/www.smharter.com\/blog\/wp-content\/uploads\/Gemini_Generated_Image_8ag95d8ag95d8ag9.png\")
<\/figure>\n<\/div>\n\n\n
The classic trade-off between hyper<\/strong><\/strong>–speed (productivity) and quality<\/strong> persists in the code generated with the AI, a fact supported by recent research (see AI-assisted coding: how to ensure real productivity gains?<\/a>). It is therefore essential to align the AI coding technique used and its philosophy with the trade-offs needed by each product type (from mock-ups to legacy products):
<\/p>\n\n\n![\"\"](\"https:\/\/www.smharter.com\/blog\/wp-content\/uploads\/Gemini_Generated_Image_udzh70udzh70udzh.png\")
<\/figure>\n<\/div>\n\n\n
Conclusion: Choose wisely, remain consistent, and don’t overlook quality.<\/strong><\/p>\n\n\n\n
\n\n\n\n![\"\"](\"https:\/\/www.smharter.com\/blog\/wp-content\/uploads\/develop.png\")
<\/figure><\/div>\n<\/div>\n\n\n\nDevelop Technical Excellence that delivers.<\/h3>\n\t
\n\tSee how we can help.\n\t
\n\tYou, your team, your Tech.\n\t
\n\t
\n\t<\/p>\n\n\t