Producing artifacts: media, code, documents, the visible output has clearly gotten easier. But the other things, like knowing what's worth building in the first place and making the right judgment call, still seem to be left to the humans.
83 karma · joined October 20, 2020
Producing artifacts: media, code, documents, the visible output has clearly gotten easier. But the other things, like knowing what's worth building in the first place and making the right judgment call, still seem to be left to the humans.
They already have strong tools. Just way too many paths They should make the recommended stack obvious and well-supported.
Now it's easier to traverse a live plan and to quickly make micro pivots as you go.
I also think that architecture needs to change. Design patterns that will help to provide as much context to the LLM as possible to increase understanding.
The more code, the more surface area the LLM needs to cover before understanding or implementing correctly.
Right now the solution to expensive token limits is the most token-efficient technology. let's reframe it better. Was react made to help humans organize code better or machines?
Is the High Code-to-Functionality Ratio 3 lines that do real work > 50 lines of setup really necessary?
AI coding tools are burning massive token budgets on boilerplate thousands of tokens just to render simple interfaces.
Consider the token cost of "Hello World":
- Tkinter: `import tkinter as tk; tk.Button(text="Hello").pack()`
- React: 500MB of node_modules, and dependencies
Right now context windows token limits are finite and costly. What do you think?
My prediction is that tooling that manage token and context efficiency will become essential.
What language did you use to write the code?
I also have another question, did you witness the transition from punched cards to terminals?
ex: 1055 & LOSS ( one zero five five & loss)
- Image Input to 3D model Output
- 3D model(format) as Input
Question: What is the current state of the art commercially available product in that niche?
Then someone said, "Sending HTML is old news; let's send JSON on the back end and reassemble everything with JavaScript." So we did.
Then someone said, "Why don't we put everything in a single file and call them components?" So we did.
Then someone said, "Why don't we push those components from the server instead?" So we did
Wait a minute???
int age = will never have string "December".
But in python both: age = 42 and age = "December" are possible.
A processor has different cores, Computers may have several hard-drives, 4 sticks of ram.
Each component can run in parallel.for example, if a long video processing task is underway and your text generation component is idle, it could assist.
Should the audio component fail , only that specific part would be affected.
Now our smartphones are 1000 times more powerful than the ENIAC and use less power.
Do you think Apple likes to jump on things? Apple usually tries not to be first, but definitely likes to polish .
One for each category: audio, text, video, image.
One analyzer to coordinate everything.
This would be my API that I could access with mobile devices.
Here's a scenario:
I could talk to my phone about ideas, in the background it would create apps prototypes, create posters, make music based on something i whistle, teach me ask i ask question about a topic.
We could delegate the mundane stuff to it.
A computer like device that can "generate text", "generate audio", "generate video" and also "train".
But
The documentation is solid, plenty of content online to get training.
Create index.php and put your content.
Link Jquery and Bootstrap/Bulma/Skeleton css framework
Start with the basics stuff and slowly increment, until you have a working prototype.
Start with the default PHP server: php -S localhost:8000
PHP is object oriented and have a ton of libraries for everything imaginable.
In a way they are related, is it why people from those countries pick it up so easily?
Like kids growing up in metropolitan areas immersed in English only environments
For example. You have a flower delivery service. Programmers you understand flowers, types of packages, schedules, customer interactions will have an edge over everyone else.
Especially with libraries/ framework that are 10+ years old Their documentation is extremely detailed.
So you have more confidence that you'll deliver a working product. Instead of reading github issues to fix an obscure error message.
Old does not always mean outdated.