Now, I resell the output of AI supervised by engineers.
We can tell when it makes mistakes. It used to make a ton. Now, with the right context, it really makes very few mistakes (which it can find itself and fix itself)
366 karma · joined February 15, 2024
You can read about me and get my contact details in my website: https://www.salomonmuriel.com
meet.hn/city/co-Bogota Capital District - Municipality
Socials: - linkedin.com/in/smuriel - cal.com/salomuriel
Interests: Entrepreneurship, Hacking, Maker Culture, Programming, Social Impact, Education, Python, Go, Typescript, Data Science, Web Development
---
Now, I resell the output of AI supervised by engineers.
We can tell when it makes mistakes. It used to make a ton. Now, with the right context, it really makes very few mistakes (which it can find itself and fix itself)
It one shot the infrastructure to use and created the terraform file to put it up anywhere. It deployed it.
It caught some of the errors it had made by itself after load-testing, and corrected them. It created the load test itself (following patterns from previews projects we had).
It did all of this in a week. With human supervision on each step, but in a fucking week. We gave it all the context it needed and one-shotted everything.
It is more than god-level. If you are not getting these increases in productivity, you are using it wrong.
Almost all commits live in tandem with some large feature or change being made. The reason for absolutely all of them is the same - build the thing .
I'd argue that we need to apply this to companies too. Stop building startups (which start losing money and may never ever make a profit in the process of scaling) and start creating companies (which make a profit ASAP and may never scale).
Hire him and put him in R&D in some robotics company.
English is fucked up. The only way to learn how to speak it properly is by memorization.
Other languages like Spanish or Korean keep a near-perfect one to one correspondence between written form and expected pronunciation.
You upload interviews with family members (text, audio or video all work) and the system automatically transcribes the text, finds key people or events, and puts it together with other information you may have gathered about those events or people before. Like building a genealogical tree but with the actual details about people's lives.
In the works to also attach pictures of said people and events to give it some life.
LLMs will produce code with good structure, as long as you provide that architecture before hand.
The reason message queue systems exist is scale. Good luck sending a notification at 9am to your 3 million users and keeping your database alive in the sudden influx of activity. You need to queue that load.
The logistics between growers to distributors to store and customers add a ton of cost to your food. In the order of 200%.
The reliance on external food sources for many ingredients exacerbates this even more.
Many business models in other countries are based on lowering logistics, doing basically grower-to-customer directly and evading all the middlemen. No refrigeration, better quality, cheaper food.
Your other criticism I agree with.
Dumb phrase.
They buy the team, the know-how, the customers, the brand. The repo is open source up until now, but they can create a paid offering with premium features over the open source code. They can also offer specialized hosting for that solution (which is a very clear advantage of joining with cloud flare)