LLMs Write Code, But Don't Fix Silos

Generative AI is changing how software gets built by shifting where developer skill is applied. The thesis is straightforward: LLMs accelerate code production, but they do not eliminate organizational silos, ownership gaps, or compliance risk. Speed is real. Structural friction is not solved by generation.

Generative AI in Software Engineering: An Overview

For teams in Banking, Education, HealthTech, FinTech and Tax Returns, generative AI is most visible as an assistant in the IDE: autocomplete, summarization, and draft generation from natural language prompts. The underlying concept is an overview of generative AI concepts, from the fundamentals of large language models to responsible AI principles [1].

In practice, that means a developer can describe intent in plain language and receive candidate code, tests, or documentation in return. The value is not in the novelty of generation but in compressing the time from idea to first working draft.

What does not change is the need for domain constraints. A tax calculation, a clinical decision support rule, or a payment authorization flow all carry regulatory and risk requirements that an LLM cannot infer from syntax alone. Generative AI is a productivity layer on top of existing engineering practices, not a substitute for them.

Code Generation and Bug Fixing: The Promise and the Pitfalls

Code generation is the headline use case. It works best as a prototyping tool. As one practitioner notes, for now I think copilot is a really powerful prototyping tool [2].

The benefit is clear for teams under delivery pressure: first drafts appear faster, boilerplate is reduced, and developers can explore multiple implementations quickly.

The pitfalls are equally clear. LLMs performed consistently better in healthy code bases, and the risk of defects was 30% higher in less-healthy code [3]. In legacy banking cores, fragmented education platforms, or HealthTech systems with accumulated compliance patches, the context window is noisy and the model’s suggestions degrade.

Cost and accountability also remain open questions. The true cost of tokens is currently unknown, and it could be so cheap that we don’t care how many tokens we send to LLMs, or it could be high enough that we have to be very careful [3]. For FinTech and tax software where auditability matters, an unpriced token cost model makes long-term planning difficult.

A second structural risk is skill concentration. LLMs are eating specialty skills, and the ability of LLMs to write lots of code may mean they code around the silos rather than eliminating them [3]. The concern is that fewer specialist front-end and back-end developers are needed as the LLM-driving skills become more important than the details of platform usage [3]. That can widen the gap between teams that can steer the model and those that are displaced by it.

Feature Suggestion and Prototyping: The Power and Limits of LLMs

Where LLMs add the most value is in early exploration, and where they are most limited is in late-stage validation. A product owner can sketch a feature in natural language, receive a working prototype, and validate direction before engineering commits. The same workflow breaks down when the prototype requires regulatory sign-off, integration with legacy APIs, or non-functional requirements like auditability.

Amazon Q Developer is positioned as an assistant for that workflow. Amazon Q Developer has the highest reported code acceptance rates in the industry for assistants that perform multi-line code suggestions [4]. Reported adoption includes BT Group recently reporting they accepted 37% of Q’s code suggestions and National Australia Bank reporting a 50% acceptance rate [4].

The same family of tools can automate mechanical upgrades. Q can also automate app upgrades, reducing days of work to minutes [4]. For banks and health systems with many internal applications, reducing the manual effort of dependency updates is a tangible operational win, provided changes are reviewed for behavioral risk.

A typical prototyping loop looks like this:

The loop keeps the human in the decision role. The model proposes, the developer validates against regulatory, clinical, or financial rules, and the prototype is promoted only after review.

For feature suggestion, the pattern is similar:

# Example: generate a draft validation function from a spec
# Prompt: "Create a Python function that validates a tax ID format for AU, returns error messages"
def validate_au_tax_id(tax_id: str) -> tuple[bool, str]:
  if not tax_id or len(tax_id)!= 11:
  return False, "Tax ID must be 11 characters"
  if not tax_id.isdigit():
  return False, "Tax ID must be numeric"
  # Simplified Luhn-like check placeholder
  return True, "Valid"

The draft is fast. The validation logic, edge cases, and legal interpretation still require domain experts.

Real-World Applications: Banking, Education, and HealthTech

In Banking and FinTech, the immediate use is internal tooling and non-customer-facing services. Generating reconciliation scripts, test data, and API client scaffolding reduces toil. The constraint is data handling: models must not be exposed to PII or card data, and suggestions must be reviewed for PCI DSS and financial regulations.

In Education, generative assistants help with learning management system extensions, automated grading helpers, and accessibility improvements. The constraint is student data privacy and equity of access. A generated feature that works for one course may fail compliance checks for another.

In HealthTech, the value is in accelerating interoperability work, such as FHIR mapping and documentation generation. The limitation is clinical safety. An LLM can propose a code snippet for a medication reminder, but it cannot certify clinical correctness. Review by a qualified clinician remains non-negotiable.

Across these sectors, Amazon Q Business illustrates how assistants connect to enterprise context. With Amazon Q Business, employees can get answers to questions across business data such as company policies, product information, business results, code base, people, and many other topics by connecting to enterprise data repositories to summarize the data logically, analyze trends, and engage in dialog about the data [4]. That capability is useful for onboarding engineers to legacy banking systems or for retrieving policy constraints before coding.

The Future of Software Development: Opportunities and Challenges

Capability	Typical Benefit	Key Limitation in Regulated Sectors
Multi-line code suggestion	Faster first drafts, higher acceptance rates	Requires review for compliance and safety
Prototyping / MVP helper	Quick validation of ideas	Prototype quality varies with code health
Automated upgrades	Reduces days of work to minutes	Risk of silent behavioral change in critical paths
Enterprise Q&A	Faster context retrieval	Data governance and model exposure controls

Opportunities center on developer experience and maintenance. Challenges center on governance, cost predictability, and organizational change.

The future skill set shifts toward prompt design, model steering, and rigorous review. Teams that treat LLMs as junior pair programmers with strong opinions will get the most value. Teams that expect LLMs to eliminate silos will be disappointed. The silos are organizational, not syntactic.

Opportunities and Challenges

Opportunities: faster prototyping, reduced toil for boilerplate and upgrades, improved onboarding via enterprise Q&A.

Challenges: defect risk rises in unhealthy code bases [3]; token cost is uncertain [3]; skill concentration may displace specialists [3]; compliance, auditability, and data governance remain human responsibilities.

Conclusion and Next Steps

LLMs write code. They do not fix ownership boundaries, unclear requirements, or risk aversion. For Banking, Education, HealthTech, FinTech and Tax Returns, the winning pattern is narrow, well-guarded use: prototype fast, review thoroughly, and keep the human accountable for what the code means in the real world.

If you are adopting LLMs today, start with a bounded prototyping loop, measure acceptance and defect rate per code health tier, and document who owns review for regulatory and safety decisions.

References

1. Beginner: Introduction to Generative AI | Google Skills — cloudskillsboost.google
2. Ask HN: How do I stay on top of AI within software development? — news.ycombinator.com (28 February 2023)
3. Fragments: February 18 — martinfowler.com (18 February 2026)
4. Accelerate software development and leverage your business data with generative AI assistance from Amazon Q | Amazon Web Services — aws.amazon.com (30 April 2024)