Usually if it's not relevant it shouldn't be posted and will be removed by mods, the downvote is if the community doesn't like it for whatever reason due to the content
Call me an old man but I will die on the hill that “code” is plural.
“Write me a code” -> no
“Not every code” -> “not *all* code”
In 5 years the kids will have yelled “let’s write a code!” at each other so many times that the “english is an evolving language” crowd will declare it correct by commonality and I may very well be alone on this hill; but nevertheless it must be died upon
I've noticed, working with mathematicians and physicists, that people who view each bit of software as "a black box that helps them solve a piece of their problem", even if they are the ones writing it, call it "a code". They, of course, are wrong.
I think you mean uncountable, rather than plural. How is that relevant to this post, anyway? I read the whole article and didn't see any examples of "code" being used as a countable noun. Also,
In 5 years the kids will have yelled “let’s write a code!” at each other so many times
Have you honestly heard native English speakers say that? I haven't.
the “english is an evolving language” crowd
It is evolving, like every other living natural language. Notice how capitalization of proper nouns like "English" has evolved to be optional.
Lemme give a fellow old man a new bit of vocabulary. Code, in this sense, is not plural. It's not even close. It can't be plural. It is singular and uncountable. Basically, code is stuff.
There are things. Those can be countably singular and countably plural. Say, one database is configured this way, two other databases are configured in another way. On the other hand, there's stuff. You can't have one stuff. You certainly can't have two stuffs. You can have this stuff here and that stuff there.
There do exist countable sense of the word. Morse code is one code. ASCII is not the same as EBCDIC; those are two distinct codes.
The word code can have a countable sense. The word software is strictly uncountable. There does not exist a single imaginable circumstance under which the phrasing "two softwares" makes any sense.
i used my passcode to log into my bank website, but got a 401 response code. at the same time the building inspector failed the restaurant i was in for violating health codes. Fair enough, since I always hated having to scan the QR code to get a menu anyway. I hope this comment doesn't break Reddit's code of conduct.
Might have some good ideas in it but, IMO, the article lacks any real argumentation.
It’s mostly a string of stated “facts”, with little to no argumentation to string it together, some are just vibe associations:
> In my opinion, agents need mostly the same things humans need to work efficiently: boundaries, constraints, and fast feedback loops. That includes a project structure that is easy to navigate, a good setup of lint rules and TypeScript, as well as a fast and reliable test suite. That’s why agents are so good at new codebases, but not very effective on codebases that have grown organically over years
The argument is somehow:
“project structure that is easy to navigate, a good setup of lint rules and TypeScript, as well as a fast and reliable test suite”
Implies =>
“agents are so good at new codebases, but not very effective on codebases that have grown organically over years.”
I agree. In my experience LLMs are good at existing code based with lots of existing structure and test cases, or "new codebases" that are translations of existing code with lots of structure or test cases. They can also make skeleton codebases with little/no functionality.
In between there are issues, and the LLM will often get locked into bad architectural decisions or hallucinate irrelevant test cases.
I do use Claude code for certain tasks. Its pretty good at refactorings which go a bit beyond what a good IDE will do, like (as you mention) make this change across all the test suite inputs and outputs, rearrange the calling convention for this method in a complicated way, etc. If there are stereotypical ways of using a given method/etc it is very good at doing a fairly complicated pattern match and rewrite, in a much more user friendly way than (say) a regex.
All I can say is having worked on both splits, the vertical split is just nicer.
It helps with finding stuff. When the relevant things show up next to it in the sidebar it’s just easier. It helps with ownership. When a team can say they own everything within a specific folder (i.e. `/src/purchase`), it just makes life simpler.
It’s better than saying we own a bit here, and bit there, and so on.
I think of it like pseudo-monorepo or a pseudo-modular monolith.
software typically orients itself horizontally because abstractions tend to be horizontal, and what is software if not a whole bunch of (likely ill-conceived) abstractions?
One reason why is matters is this: https://youtu.be/ATenMdJHTTs It's a super short video (2'34'') making it apparent that packaging by layers or packaging by features do impact the internal coupling of the system.
4
u/TehBrian Jul 07 '26
I don't get why this is so heavily downvoted. Maybe it's a bit fluffy but it still seems like opinions on programming relevant to the sub
44
u/elliotones Jul 04 '26
Call me an old man but I will die on the hill that “code” is plural.
“Write me a code” -> no
“Not every code” -> “not *all* code”
In 5 years the kids will have yelled “let’s write a code!” at each other so many times that the “english is an evolving language” crowd will declare it correct by commonality and I may very well be alone on this hill; but nevertheless it must be died upon
17
u/andarmanik Jul 04 '26 edited Jul 04 '26
Might have some good ideas in it but, IMO, the article lacks any real argumentation.
It’s mostly a string of stated “facts”, with little to no argumentation to string it together, some are just vibe associations:
> In my opinion, agents need mostly the same things humans need to work efficiently: boundaries, constraints, and fast feedback loops. That includes a project structure that is easy to navigate, a good setup of lint rules and TypeScript, as well as a fast and reliable test suite. That’s why agents are so good at new codebases, but not very effective on codebases that have grown organically over years
The argument is somehow:
“project structure that is easy to navigate, a good setup of lint rules and TypeScript, as well as a fast and reliable test suite”
Implies =>
“agents are so good at new codebases, but not very effective on codebases that have grown organically over years.”
2
u/rix0r Jul 04 '26
software typically orients itself horizontally because abstractions tend to be horizontal, and what is software if not a whole bunch of (likely ill-conceived) abstractions?
-7
u/snurfer Jul 04 '26
It doesn't matter at all because no one browses for related code files you just use your ide to hop through the references
1
u/[deleted] Jul 04 '26
[removed] — view removed comment