AdieuToLogic
Joined 11 years ago
Joined 11 years ago
_Bool find_last (size_t count, int *haystack, int needle, size_t *where)
{
for (const int *pos = haystack + count; pos-- != haystack;) {
if (*pos == needle) {
*where = pos - haystack;
return 1;
}
}
return 0;
}> I want to see a practical benefit to maintaining this with public funds versus the usual redlines.
The US government works for the people and, as such, changes made to the US Code over time must be traceable, discoverable, and therefore justifiable by or condemnable to those who are responsible for said changes without fear or favor.
That is as practical as it gets.
One of these situations prohibits the other.
You're missing the point. Understanding has nothing to do with code.
"Code" is short for "encode", which is an industry term for "encoding a solution". This implies a solution has been formulated before it is expressed in a programming language.
There is no "codebase" without a person or people who understand what solution to reify in the first place.
> A model can absolutely help create understanding in the person overseeing these changes, provided that person deigns to ask for it.
A model can assist a person to gain understanding, sure, but like you said yourself:
... provided that person deigns to ask for it.
By this statement alone, you have proven my point of:
In order for agentic coding to be a net positive, the
instructions given to the AI offering must be from people
who understand what a system currently does as well as what
functionality a product needs to provide in its future
desired state.In order for agentic coding to be a net positive, the instructions given to the AI offering must be from people who understand what a system currently does as well as what functionality a product needs to provide in its future desired state.
Agentic coding does not solve these fundamental concerns.
> Now, the kinds of changes that were simply unrealistic before are now entirely realistic. A refactor/migration that would have taken 6 months before, you can now get a working version done in a day, and another few days of QA.
Significantly changing a system implementation is a function of understanding, not time.
Given a starting solution state being A and a desired functionality state of A', the tooling used to codify the A -> A` delta is largely irrelevant. Specifically, in order to successfully deliver major product realignment requires awareness of what exists currently and understanding of what needs to be.
Code is neither stone nor clay.
When making software, remember that it is a snapshot of
your understanding of the problem. It states to all,
including your future-self, your approach, clarity, and
appropriateness of the solution for the problem at hand.
Choose your statements wisely.Honestly, I don't see how this is a problem.
> Which in the end is kinda the point of it.
Absolutely.
> Like your post says, with programming, it's mostly just a race to what achieves the goal ...
Unless the joy of whatever programming one does is found in the path taken.
> I started learning ARM assembly so I could make a lisp implementation in it. It will be useless, no one will use it, and an AI could bang one out in a few minutes ...
Who cares if anyone uses it or if some other tooling could replicate what you choose to do if, in doing so, you enjoy it.
Much like the "damn good croissants" you make, it doesn't matter what others could make. You make damn good croissants.
Your happiness is yours. Enjoy the path you take to find it.
If you perfer using the same language for both frontend and backend work, yet would like to have one more semantically rich than TypeScript, consider Scala.
For the frontend, ScalaJS[0].
For the backend, Scala[1].
The funny thing about Servant Leadership[0] is that it demands a leader see themselves as an equal with those whom they lead. Thus requiring acknowledgement that the title a person has does not establish their value, no matter what an org chart proclaims.
It is also possible that the proverb I provided to you is the origin of the oft quoted:
Better to remain silent and be thought a fool than to speak
and remove all doubt.
So there's that.Any reasonable definition of understanding is not dependent upon "whatever vibe you are going for", but instead must include at least an English dictionary definition of "understand" such as:
to grasp the meaning of[0]
And, for further clarification, "grasp" can be defined as: to lay hold of with the mind[1]
Which makes an equivalent term-expanded definition of "understand" to be: to lay hold of with the mind the meaning of
As such, there is no "sensible mathematical definition of understanding", unless you possess a complete mathematical model of the human mind.>> Understanding is a state of mind
> This is meaningless, it is a circular definition at best.
See above to as to why there is meaning in what I wrote.
>> It exists entirely within the individual and nowhere else
> Then why are we talking about it? What is the point if it is something that can only be defined per individual?
I like to think analyzing fundamental premises, often implicit, explicitly can help to identify fallacious positions.
> We are still not getting anywhere because you have not prescribed criteria to determine whether [an LLM] understands.
My apologies for being opaque. Let me clarify:
LLMs do not "understand". People interpreting LLM output
are the only entities involved which can "understand",
because "understanding" exists strictly within each
person who possesses it.
0 - https://www.merriam-webster.com/dictionary/understand"Might be out of sync" is a unique spelling of "crucified online". :-D
Use it for money laundering and fraud.