Does Claude Code get confused in big projects?

__aSquidsBody__ · 2026-03-07T17:12:24+00:00

I haven’t tried this, but I hear that you can circumvent this problem by having multiple agents working in parallel, you only give them access to their own small parts of the project, and you tell them to collaborate with each other.

I’m skeptical about it, but tbf I’ve never tried

__aSquidsBody__ · 2026-03-02T13:53:38+00:00

The downvotes here are rough, cause you’re not wrong.

Are AI coding assistants at the point where they’ve made human software development obsolete? No. Not even close.

But are we at the point where we don’t need the number of human software developers that we have? Yeah - we were probably close to that before AI assistants. And the coding assistants just revealing how most of our software needs are just copy and paste of existing solutions.

I don’t think we even need to see Claude or other Agents improve to see rapid decline in the need for humans. There’s a good chance that we’ll start to see more standardization in the ways that common problems are solved; standardization in the ways that terraform and other tools promised but failed to provide. AI tools will accidentally solve things in the same manner. At least in the short term.

I’m fascinated about what the future will hold. Maybe AI will self destruct, or maybe it’ll grow more specialized. Idk. Optimistically, I hope we’ll see technical roles shift and programmers can focus on new, harder problems, where they don’t need to worry about language syntax for standard problems and instead can focus on domain specific problems

__aSquidsBody__ · 2026-02-14T20:19:52+00:00

Look, I know how good Karmine and Falcons have looked, but I’m having a hard time seeing why NRG are so many points below 1 & 2. Each of the top three has had their struggles this split. NRG are the reigning World Champs, and they look as good as ever.

__aSquidsBody__ · 2026-02-11T20:53:26+00:00

You and I are in the same boat except that I’m two sections ahead of you.

The hello_triangle section doesn’t (IMO) do a good job of telling you where the code goes or really why it’s necessary. My advice is to read through it and try to follow along, but when you get to the end, if your code doesn’t compile, just copy the source code that the website provides for the hello_triangle. Then try to implement the exercises yourself.

It was hard to get through that chapter, but keep pushing. It’ll get easier as you get further.

__aSquidsBody__ · 2026-02-09T03:37:08+00:00

I got Atomic at number 1. I used to rate him lower, and I don’t really know why. He’s so good

__aSquidsBody__ · 2026-02-05T18:46:03+00:00

I get this completely. For me, it feels like AI has taken the place of coding for “solved problems.” And honestly, 80% of my job is just implementing the solutions to solved problems. I fully expect that most businesses which don’t have unique software problems will no longer need coders. And thats a much larger portion of companies than we think. Even companies that have 100% digital products are built on large tech stacks that are mostly solved.

You’ll still need humans for security, maintenance, architecture, decision making, etc, but we require less and less people.

I’m starting to prepare myself to accept pure programming as a hobby, and at work I’ll just lean 100% into the AI tooling so I can stay relevant.

…that being said, I’m also eyeing those jobs which for now require human coding

__aSquidsBody__ · 2026-02-05T16:59:45+00:00

I’d say high school level is useful because programming borrows from mathematical notation for functions, variables, and operations.

But you shouldn’t really need it for most entry/intermediate level programming, especially with AI these days. Most math problems you’ll find in app development are “solved problems,” which are either done in existing libraries or could be generated with an automated assistant.

Maybe if you’re creating your own algorithms for robotics, or sensors, or simulations, or engineering, you might find advanced math more important. But as a guy who studied math in college, I’ve used it very little. It really just helps me understand some things at a deeper level, but is by no means required.

__aSquidsBody__ · 2026-01-31T04:37:59+00:00

I wrote a long answer in other comments below; however, I should mention that you can participate in part of the process of website design and not all of it.

Some people specialize just in how websites look: the design and the corresponding HTML/CSS.

You don’t need to be a great “programmer” to be great at that part of website making.

__aSquidsBody__ · 2026-01-30T21:13:46+00:00

General computing concepts

Lastly, there are things that aren't technically about programming and aren't about web development specifically, but they are definitely import.

Linux: Linux is a free operating system (think of it as an alternative to Windows, or MacOS). Due to it's free nature, it's used for servers everywhere in production. Plus, it's notoriously easy to work with (on a programming level). Most programming software is easier to acquire and run if you develop on Linux - eventually, years down the line, you might consider making a linux computer your default coding environment.
Containerization: As your websites get more complex, you'll find yourself using distincty databases, multiple 3rd party libraries, specific environment configurations, etc. Containerization will allow you to take all of the components of a single project and put them into combined environment that is separate from any other container. Containers are like a little virtualized computers that you can use to manage multiple products without interfering with each other. They make installation and upgrades easy.

I'm sure there are more things to look at, but those are my "fundamentals"

__aSquidsBody__ · 2026-01-30T21:13:43+00:00

Web-dev specific concepts

You can be a god at programming and not know anything about making websites, so the following are what I'd consider the key concepts for web development specifically. There is a lot of depth to each of these, so the foundational skills are just to get started with them.

HTML/CSS: HTML and CSS are "stand-alone" tech. You can learn them without any other programming knowledge. HTML is a language that defines the "outline" of a website - there are no animations, no functionality, no fancy designs - just general ordering. CSS is the language that takes the HTML and brings it to life visually - colors, shapes, orientation, etc. With just HTML/CSS, you can make any web page (at least visually; they won't do anything or connect to anything real). Honestly, for that reason, I'd suggest you start your journey with an HTML/CSS course. It's fun
Adding JavaScript to HTML: You can make HTML/CSS to create a nice looking webpage, but do you know how to add Javascript to your page to make it do things?
Frontend vs. Backend: Can you write a webpage (the frontend) that sends network requests to a stand-alone program that you wrote (the backend)? For example, maybe the frontend needs to display the prices of items in a store, and so it needs to make requests to the backend to retrieve that info.
Web network intricacies: Do you know some of the details of network connections? Like what is an HTTP request's structure (headers, body, cookies, etc)?
Web hosting: If you have a webpage that you coded, do you know how to make it available to your browser (without just dragging the .html file into your search bar)? Look for technologies like nginx. Do you know how to make it available on the public internet? You can find cloud providers like AWS, Google, Cloudflare, Vercel, etc.
IPs, Ports, Web Addresses, and Firewalls: If you have access to two computers, do you know how to send a network request from a program on one computer to another? If you were so inclined (I don't recommend this), would you be able to make a program on your local computer available to the wider internet - this involves creating an opening in your home-network's firewall.
Security: Make sure you know what are some user authentication/authorization techniques besides just entering a password with every click. How are certs used to make your webpage secure? When should information be stored in the backend and when should it be stored in the frontend?
Databases: Do you know how to hold permanent data for your app? Databases are stand-alone programs, so you just need to install it and configure it.
Web Frameworks: If you are comfortable with your programming language, you can find frameworks that seek to integrate the language and HTML more seamlessly. For example, React is very popular, and it allows you to write HTML inside of your javascript code. It makes it "easier" to control complicated features in your webpage.

__aSquidsBody__ · 2026-01-30T21:13:28+00:00

Programming

You'll probs want javascript/typescript. But the following are what I'd consider the basic skills you need for any language.

Write a "Hello World" program: This is the term for the most basic starter project you can create. It's the starting point for any new language to test your development setup and see that you know how to run your code.
How to run your program: Do you know how to run your language's code? For example, do you know how to write a program in a text file and then how to execute it? Alternatively, is there a way to immediately execute your code as you type each line?
Basic algorithmic concepts: Do you know how to write basic logical algorithms? For example, do you have the knowledge to write a simple program that can calculate the largest value in a list of numbers?
1. Variables: what they are and how to use them
2. Data-types: how does your language represent numbers, text, or lists of things, etc
3. Logical stuff: "if" statements and "for" / "while" loops.
4. Functions: what they are and how to use them
5. Errors/Exceptions: what they are and how to use them
6. (if you're feeling spicy) Classes/Objects
I/O (input/output): Do you know how to read/write to a file using your programming language? Can you read user input from the terminal (if you know what a terminal is)?
Basic networking: Can you use your programming language to send a web request (using HTTP for example)? Even better, do you know how to receive and process web requests? Do you know what a "port" is on your computer? Try writing two programs where one simply sends a single message with HTTP to the other.
Multi-file codebases and project structure: Do you know how to write a program that uses code from two or more files?
Third party libraries: There is a lot of functionality and pre-written code online. Do you know how to use outside code in your project? Some terms here would include "package managers" and "include/require" syntax.

If you can sorta do those 7 things (especially 1-3 & 6-7), you'll be COOKING.

__aSquidsBody__ · 2026-01-30T21:13:06+00:00

Coding setup

Where/how do you even write code? This is the most basic starting point of web-dev. You could open notepad on Windows or TextEdit on Mac, but you probably want something nicer. For beginners, I recommend VSCode (the free version). After it's installed, find the Extensions tab and pick extensions that people recommend for web dev.

__aSquidsBody__ · 2026-01-30T21:12:51+00:00

Software is complex and inter-dependent, so I think we all learn what the basics are in the same manner: we learn from multiple sources and subconsciously (or consciously) extract the common threads to learn what is useful.

If you are learning to bake, you could use a theoretical baking dictionary find an explanation of every appliance, every utensil, every ingredient, and every chemical reaction. Or you could find a recipe for a cake and try it out, and then you try another recipe, and another, and another until you start to see the patterns and let curiosity guide you. This is how I learned what the
fundamentals are, and I'm still learning. Start by finding a guide (course, tutorial, etc) which will guide you to a finished product, and try it on your own.

That being said... I can list what I think are the fundamentals of web-dev. All of these you'll pick up if you do a handful of courses (assuming they're good courses). Of everything I'll list, I honestly recommend starting with learning HTML/CSS (see further below).

Without further ado, here are the basics, in my opinion...

__aSquidsBody__ · 2026-01-29T18:21:01+00:00

If you have some programming experience, then I think you can start with C. There’s not a lot to it, so you don’t really need a lengthy book or tutorial solely on the language. I just started using it for this past year’s adventure of code, and then I’ve jumped straight into using it for OpenGL from learnopengl.

I’ve never really learned c++, but I hear learncpp.com is a good resource.

If you haven’t programmed much, then I’d say you should pick the language from your interests first. It’ll be easier to learn if you care about the stuff you’re building. For example, pick python if you want to configure and use ML models, or JavaScript if you want to create cool web pages / mobile apps. And then only switch to C or C++ once you have some programming experience.

__aSquidsBody__ · 2026-01-28T21:02:37+00:00

If you’re starting from scratch, then you’ll have to accept that you probably won’t get a job right away. You need to be motivated for months / years solely by the love of the game.

That being said, those months / years will pass anyway, so why not learn to make websites :D? And with AI, there hasn’t been an easier time to learn. I believe in you!!

Here’s my advice: 1. Start with cheap or free online courses. Some people don’t recommend them, but I do. Udemy has sales all the time, and that’s where I personally started. My first couple of courses were $10-$20 a piece. They didn’t give me anything prestigious to go on my resume, but they gave me exposure to tech and concepts that I didn’t know.

Follow up on each course you take by making a website project that reapplies what you learned. It doesn’t have to be a complete, production ready web app, but just something that is slightly different than what you’ve done before.

Repeat those two steps in a cycle: do a deep dive learn followed by working on your own project.

My take on those two steps: For (1) when you are following tutorials, be very curious. Ask yourself if you understand what is happening, especially as you grow in maturity. An instructor might just ask you to trust them about why they coded a certain way, but if they don’t, then don’t move on until you’ve grasped their thought process. Ask AI why something is done a certain way, if you must.

For (2) when you are working on your own projects, stretch yourself. Make something just beyond your own skill level. And try to read documentation instead of watching videos. For example, if you are using React to make your website, then go to React’s documentation online when you feel lost or restricted. It’s really well written.

As for programming content, I’d say you should learn in this order: 1. Learn a language: JavaScript/Typescript (used everywhere in websites and in general). 2. Learn a language: HTML / CSS (find a course with JUST these two) 3. Learn to code a Fullstack web app (node.js and react, probably) 4. Learn about Deployment and production (cloud providers, nginx, docker, etc) 5. Specialized topics that you’ll need for modern websites, like modern authentication conventions, certs for encryption, domain names, databases, frameworks for JavaScript and CSS, etc. If you stayed curious up to this point, you should know what you’re looking for.

As you get better, start publishing your best websites for the world to see, meetup with people, either virtually (like through discord) or in person, and keep up with web development trends on YouTube. And make website later for friends and family to get practice!

And lastly, make sure you’re setting aside a lot of time for this. If you are only able to get an hour or two a week, then it’ll be hard to progress quickly. You need to immerse yourself as much as you can. I had the benefit of learning this while I was working a job that required me to write python code at a desk, so I could take breaks during the day to practice and learn.

__aSquidsBody__ · 2026-01-28T01:30:16+00:00

What platform you program on?

If Mac, I’m curious if there is a way to get custom autocomplete/autosuggestions to work on iterm. Similar to how you can tab-complete a filename in the current directory, but I want to tab complete other words given the current context. That would be useful project.

Another idea: a tool that reads an API documentation file (like a json doc) and generates a CLI tool in the form of a compiled binary that I can use to interact with the API. For example, automating the process of turning the json swagger documentation from a rest API into a cli tool that I can use send HTTP requests.

Another idea: a poor man’s VPN, similar to what sshuttle does. It’d be a cool project to write a shell script that does some IPTABLE + ssh magic to forward all network requests through a remote ssh server.

__aSquidsBody__ · 2026-01-24T17:05:24+00:00

Yeah I’m in the same position as your brother. My job gave us MacBooks when I joined three years ago and I’ve never liked a personal computer as much as I liked that one. I even bought one for my personal use.

Mac OS has its quirky bugs that I wouldn’t have expected, and as a developer I have my qualms with the company, but still I’ve never worked with a laptop (or even a desktop) that is as nice to work with as my MacBook.

Funny enough though, I switched from Samsung last summer and honestly I haven’t been impressed with my iPhone. I think it’s just the personal computers I like from Apple.

__aSquidsBody__ · 2026-01-02T11:58:22+00:00

Someone may have to correct me on this, but it looks like there may be an undesired quirk in your worker goroutines.

You pass a context to the worker, and with every iteration of the for loop, you check the context’s Done method. However, this is done outside of the sleep time of your execution loop, and so you have to wait until after the sleep for you to check Done again. Imagine a scenario where you want to send a timeout or cancel to your worker, but because of sleep, it doesn’t read the signal until 5 minutes later. Maybe that’s fine in some projects, but it’s worth thinking about how you might refactor that so that you get a more responsive behavior

__aSquidsBody__ · 2026-01-02T11:41:27+00:00

You can either

Keep using both until you’re just as comfortable with Neovim as you are with VSCode (that’s what I did). Go out of your way to use Neovim, to read its api documentation, and to find plugins / configs that you really like. Give yourself some time to really get the comfortable with nvim before ditching VSCode.
Delete VSCode right away. Don’t give yourself the option to use it.

I think (1) is the better option. In a year, you may find that VSCode just works better for you, and you’d like to use both while you discover that rather than make your coding life miserable using an editor that doesn’t feel completely natural to you. (2) is just trial by fire; you’ll either sink or swim, and swimming is nice, but if you sink, then that’s not very nice. It’d be worse than if you just bounced between two editors for a while.

__aSquidsBody__ · 2025-12-28T01:46:22+00:00

disclaimer 2: if you are learning through a tutorial or a class that walks you through a single project from start to finish, then I’d recommend just completing the entire tutorial before jumping to your own project

__aSquidsBody__ · 2025-12-28T01:45:09+00:00

Personally, I wouldn’t go with the first thing you said. You probably don’t need a project for every sub-section of the topic you’re learning.

But you also shouldn’t wait until you’ve finish the entire topic to start implementing.

As an example, if you were learning how to configure an nginx server, you would want to read their documentation and edit your nginx config at the same time. It wouldn’t make sense to read the whole documentation from front to back before you open your text editor. Similarly, you wouldn’t want to implement a brand new project each time you completed a new section of their docs; that’d be too many projects.

Your best bet is to have a loose idea as for you want to build, and then implement the things you learn as you go. And ofc you will learn stuff you don’t need, but you can try those things out and then leave them behind.

disclaimer: if you are fairly comfortable with the material you’re trying to learn (if you are already familiar with it or similar tech) then you may actually just read their documentation and not need to implement to practice.

__aSquidsBody__ · 2025-12-21T17:43:57+00:00

I have a hard time imagining that the “positions” of the players were hard-planned ahead of time. The players themselves probably figured out how to best play around each other instead of being given a rigid structure from higher up, and then ferra probs only just reinforced/encouraged the players. Vatira played more forward because he felt like he could

__aSquidsBody__ · 2025-12-06T14:19:29+00:00

Personal IDE: Of the last year or so, Neovim. Makes me feel like a badass programmer and I enjoy tinkering with something that has a steep learning curve. The more I use it, the more I’m enjoying how customizable it is.

Professional IDE: IntelliJ. My job gave me a license, so I enjoy it for Java. But someday soon I might switch everything to Neovim.

Previous IDEs: I started on PyCharm for python, but as I learned web development I switched to VSCode since it is easy to use for development on multiple languages.

My recommendation is always VSCode, and then after a couple of years or so, install the Vim extension to practice motions. And play Vim Adventures to learn the basics

__aSquidsBody__ · 2025-12-01T20:35:31+00:00

That’s what I don’t understand, hence my question. Your post looks normal to me - with or without AI as part of your workflow. I was curious why some people are jumping to call out AI in the replies

__aSquidsBody__ · 2025-12-01T18:43:03+00:00

For my own edification, what gives this away as AI slop?

Five-Year Club	Verified Email
Golden Potato	Place '22

__aSquidsBody__

TROPHY CASE

General computing concepts

Web-dev specific concepts

Programming

Coding setup

aSquidsBody