negoutputeng
POCs and demos are easy to build by anyone these days. The last 10% is what separates student projects from real products.
any engineer who has spent time in the trenches understands that fixing corner cases in code produced by inexperienced engineers consumes a lot of time.
in fact, poor overall design and lack of diligence tanks entire projects.
however, there are tech transitions and it appears we are in the midst of one - after which a new set of tech careers seem to emerge. internet/web/mobile/cloud/saas and whatnot. i fully expect the same to happen here.
so, hang in there, and keep your sword sharp.
after the dot-com bust, i took a job that involved a 70 mile commute (each way) which was about 100 minutes on the road on average each way. At the time, i thought that was the only option for me. turns out it was one the worst career choices i made.
i try to help anyone i know (with referrals) as i have personally seen the anxiety, stress, and emotional roller-coaster that accompany the job hunt.
trivia: js based https://ethercalc.net/ is in turn is derived from https://github.com/DanBricklin/socialcalc written by the spreadsheet inventor dan bricklin
As you have put it well, there is no notion of truthfulness encoded in the system as it is built. hence there is no way to fix the problem.
An analogy here is around the development of human languages as a means of communication and as a means of encoding concepts. The only languages that humans have developed that encode truthfulness in a verifiable manner are mathematical in nature. what is needed may be along the lines of encoding concepts with a theorem prover built-in - so what comes out is always valid - but then that will sound like a robot lol, and only a limited subset of human experience can be encoded in this manner.
it is not what the foundational knowledge "is" - but "how" the foundational knowledge is "unpacked" by each person from the first principles.
this was articulated by Descartes in "Rules for the direction of the mind" which remains sadly unread and forgotten.
the difference between the 2 approaches is that the author's approach does not clearly delineate what is meant by "learning". In fact, it could even encourage rote-learning of the foundational material. Descartes outlines an alternative.
An interesting anecdote about Descartes is that he "unlearnt" everything he knew early in life, and attempted to "rebuild" his knowledge. Few of us have the luxury to do that.
link: https://en.wikipedia.org/wiki/Rules_for_the_Direction_of_the...
ie, use it as a template-generating search-engine helper for most common things. for uncommon things, you have to prompt-guide it to get what you want.
All i got instead are lame tools for developers.
we are at a phase where the early adopters have seen the writing on the wall.. ie that llms are useful for a limited set of usecases. but there are lots of late adopters who are still awestruck and not disillusioned yet.
i am saying, the thing is snake-oil - a solution looking for a problem.
just goes to show, it is all a big song-and-dance. much ado about nothing.
so, they organize hackathons where devs build a hypothetical agentic framework nobody will dare use. So, mgmt can claim, look here what i have done to be agentic.
you should ask: would you dogfood your agent, and the answer is no way. these are meant purely for marketing purposes, as they dont meet an end user need.