# LLM Programming Agents > Published Jan 01 0001, last updated Jul 07 2026 > By Ryan Fleck and written without LLMs! > Original manual at > Incredible writing of astonishing quality and insight - Happy Hacking! # The Problem with LLM Programming {#the-problem-with-llm-programming} **Language models have no clue what they are doing.** They don't think like you, and are tools - _don't make the mistake of trusting them like you would a person!_ **LLM generated code is riddled with subtle dangers** that can only be spotted by experienced programmers with domain knowledge. The output looks great to both the untrained and trained eye, and the dangers only become apparent when reading it line by line and seeing the _amalgamated assumptions of thousands of different codebases_. To reduce this danger, better programming languages that lean on the strengths of LLMs will grow in popularity. The industry will likely transition to **expressive** high-level languages like [Elixir](/elixir) which lean on functional programming concepts and have pattern-matching built in. The limited context required to write simple functions with a guaranteed incoming data shape (built-in strong pattern matching) is exactly what LLMs need to be highly productive. The powerful conciseness and expressiveness (the ability to describe a lot of functionality in only a few lines) is another key property that LLMs would probably prefer - if only they could better represent and conceptualize the underlying data flowing through those functions. As a result, languages like [Clojure](/clj) with fantastic **ergonomics** will likely not make the cut in the LLM age. While the language is highly concise, the shape of the data is not as evident from a glance at the code. If you are a student, **do not use LLMs** (with the exception of searching through documentation,) or your critical thinking skills will be heavily eroded. **LLMs do program better than those who only skim docs and copy-paste**, who fail to attain a deep understanding of the runtime or machine beneath a programming language, and ultimately those who fail to become competent computer programmers. _Don't end up like these slop farmers -- **develop your critical thinking skills**!_ Most of the domain-specific knowledge in this space is made from the **softest, fluffiest, most irritating fairy dust you can imagine**. The terminology is overburdened in order to help pump valuations and suck in VC cash. I respond poorly to this buzzword salad, and it sticks out like a red flag indicating danger and empty marketing baloney. Structured thinkers (like Computer Engineers and programmers in general,) are used to highly structured layers of systems with highly predictable outputs for given inputs. This reliability matters a lot when systems, from the code to the silicon, are tens of abstractive layers deep. Giving one million different whimsical names to _concatenated text inputs and text outputs_ is something that _Satan_ certainly dreamed up just to violate our pragmatic virtues. **Use discernment - cut to the meat of what is underneath the marketing crap.** _Ironically, it is this mindset that enables my success as the **GenAI Enablement Leader** in my [IT Consulting] practice._ Having a grounded understanding of the real capabilities of LLMs is essential for implementing and utilizing them for clients - whether the use case is graph-rag agents, enabling developers, _etc._ **Stay grounded** _(and your LLM as well,)_ and may your prompts have clarity, context, and good structure. # CCAR-F: Claude Certified Architect {#ccar-f-claude-certified-architect} The **Anthropic CCA (Claude Certified Architect) Certification** validates Claude knowledge with a 120-minute exam containing 60 multiple-choice questions[^fn:1]: 1. Agentic Architecture (27%) 2. Tool Design & MCP Integration (18%) 3. Claude Code (20%) 4. Prompt Engineering (20%) 5. Context Management & Reliability (15%) The questions are heavily weighted toward practical implementation. - The **best** related course: ["Claude with Amazon Bedrock"](https://anthropic.skilljar.com/claude-in-amazon-bedrock) - Request to take the exam at [anthropic.skilljar.com](https://anthropic.skilljar.com/claude-certified-architect-foundations-access-request) - Study Guide: [github.com/paullarionov/claude-certified-architect](https://github.com/paullarionov/claude-certified-architect/blob/main/guide_en.MD) - _IBMer? Check the [IBM learning plan](https://yourlearning.ibm.com/activity/PLAN-28EA8DF4C387) for this certificate._ {{< figure src="/images/2026-07-11--CCAR-F-Exam-Result-Crop.jpg?invert=true" >}} I passed the [CCAR-F](https://www.credly.com/badges/69cf522c-d129-4215-86ff-169b4d6f21fc) with a score of **960/1000** on **2026-07-11**. See [credly.com/users/ryan-c-fleck](https://www.credly.com/users/ryan-c-fleck) ## Claude Tips {#claude-tips} 1. Keep `CLAUDE.md` under 500 lines 2. Use `YOLO` mode for experimentation ## The Anthropic **"4D"** AI Fluency Framework {#the-anthropic-4d-ai-fluency-framework} Four interconnected **competencies** necessary to ensure our interactions with AI are effective, efficient, ethical, and safe: 1. **Delegation**: - Setting goals and deciding whether, when, and how to engage with AI 2. **Description**: - Effectively describing goals to prompt useful AI behaviors and outputs 3. **Discernment**: - Accurately assessing the usefulness of AI outputs and behaviors 4. **Diligence**: - Taking responsibility for what with do with AI and how we do it _(This framework is from an Anthropic training session - Copyright 2025 Rick Dakan, Joseph Feller, and Anthropic. Released under the CC BY-NC-SA 4.0 license.)_ [^fn:1]: Nina Duran: Become a Claude Certified Architect, [LinkedIn](https://www.linkedin.com/posts/ninadurann_become-a-claude-certified-architect-heres-share-7439014877488152577-nMh-/) > Thank you for reading! > Find more content at > Source page: > Site index: [llms.txt](https://manuals.ryanfleck.ca/llms.txt)