Editing
Ai Code Generation
(section)
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== <span style="color: #FFFFFF;">Understanding</span> == Code generation LLMs work by treating code as a language β and indeed, code has grammar (syntax), semantics (meaning), and pragmatics (conventions). Pre-training on billions of lines of code from GitHub, Stack Overflow, and documentation teaches models the statistical structure of programs. What makes code particularly well-suited for LLMs: * Code is highly self-consistent: a good program cannot contain contradictions * Code has ground truth via execution: we can verify whether generated code is correct by running it * Code has dense structural patterns that LLMs excel at learning * The internet contains vast amounts of code with explanations (docstrings, comments, Stack Overflow) '''Fill-in-the-middle (FIM)''' training is key to IDE integration. Models are trained not just to predict the next token, but to predict a missing middle section given both prefix and suffix context β enabling Copilot-style completion that respects what comes after the cursor. '''Execution feedback''' is what separates code generation from other text tasks. Unlike prose, code can be run, and its output is factual β the test either passes or fails. This enables: * Iterative self-correction: generate β test β observe error β fix * Automated evaluation: pass@k is objective, not subjective * RLHF with execution signals: reward model trained on test pass/fail '''The abstraction gap''': LLMs generate code at the semantic level of their training data. They're excellent at boilerplate, algorithms with common patterns, and API usage. They struggle with novel algorithms, complex state management across large codebases, and security-sensitive code that requires deep domain understanding. </div> <div style="background-color: #8B0000; color: #FFFFFF; padding: 20px; border-radius: 8px; margin-bottom: 15px;">
Summary:
Please note that all contributions to BloomWiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
BloomWiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Page
Discussion
English
Views
Read
Edit
View history
More
Search
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Tools
What links here
Related changes
Special pages
Page information