We can all be AI engineers – and we can do it with open source models
The article highlights the decreasing barriers to AI engineering, emphasizing essential components for AI applications, the importance of open-source models for data privacy, and the accessibility of development tools for all.
Read original articleThe article discusses the evolving landscape of AI engineering, emphasizing that the barriers to entry are diminishing due to advancements in tools and methodologies. Luke Marsden, who has experience in DevOps and MLOps, highlights that building AI applications can now be accomplished by those familiar with basic coding and deployment practices. He outlines six essential components for creating AI applications: models, prompts, knowledge bases, integrations, testing, and deployment. The use of open-source models is particularly significant, as it allows companies to maintain control over their data, addressing concerns related to privacy and compliance with regulations like GDPR. Marsden encourages developers to leverage existing tools such as Git and CI/CD pipelines for AI applications, asserting that anyone with a basic understanding of these technologies can create production-ready AI solutions. He also introduces the concept of "AISpec," a YAML file that simplifies the integration of various components in AI development. The article concludes by inviting readers to explore resources for building AI applications and emphasizes that AI engineering is now accessible to a broader audience without requiring advanced degrees.
- The barriers to AI engineering are decreasing, making it accessible to more developers.
- Key components of AI applications include models, prompts, knowledge bases, integrations, testing, and deployment.
- Open-source models allow companies to keep their data private and compliant with regulations.
- Familiarity with tools like Git and CI/CD pipelines is sufficient for building AI applications.
- The "AISpec" YAML file simplifies the integration of AI components for developers.
Related
Up to 90% of my code is now generated by AI
A senior full-stack developer discusses the transformative impact of generative AI on programming, emphasizing the importance of creativity, continuous learning, and responsible integration of AI tools in coding practices.
Engineering over AI
The article emphasizes the importance of engineering in code generation with large language models, highlighting skepticism due to hype, the need for structural understanding of codebases, and a solid technical foundation.
Throw more AI at your problems
The article advocates for using multiple LLM calls in AI development, emphasizing task breakdown, cost management, and improved performance through techniques like RAG, fine-tuning, and asynchronous workflows.
I have been running the 32B parameters qwen2.5-coder model on my 32G M2 Mac and and it is a huge help with coding.
The llama3.3-vision model does a great job processing screen shots. Small models like smollm2:latest can process a lot of text locally, very fast.
Open source front ends like Open WebUI are improving rapidly.
All the tools are lining up for do it yourself local AI.
The only commercial vendor right now that I think is doing a fairly good job at an integrated AI workflow is Google. Last month I had all my email directed to my gmail account, and the Gemini Advanced web app did a really good job integrating email, calendar, and google docs. Job well done. That said, I am back to using ProtonMail and trying to build local AIs for my workflows.
I am writing a book on the topic of local, personal, and private AIs.
You truly know how to align yourself with hype cycles?
I hope there will still be room for devs in the future.
If a model goes sideways how do you fix that? Could you find and fix flaws in the base model?
Is it just me? Why are people using them? I feel like objectively they look like fake garbage, but obviously that must be my subjective biases, because people keep using them.
So individual apps don't need to do anything to have AI.
I could go on and on.
Copy paste is great until you literally dont know where you are copy and pasting
But that's akin to web devs of old that stitched up some cruft in Perl or PHP and got their databases wiped by someone entering a SQL username. Yes, it kind of works under ideal conditions, but can you fix it when it breaks? Can you hedge against all or most relevant risks?
Probably not. Don't put it your toys into production, and don't tell other people you're a professional at it until you know how to fix and hedge and can be transparent about it with the people giving you money.
Related
Up to 90% of my code is now generated by AI
A senior full-stack developer discusses the transformative impact of generative AI on programming, emphasizing the importance of creativity, continuous learning, and responsible integration of AI tools in coding practices.
Engineering over AI
The article emphasizes the importance of engineering in code generation with large language models, highlighting skepticism due to hype, the need for structural understanding of codebases, and a solid technical foundation.
Throw more AI at your problems
The article advocates for using multiple LLM calls in AI development, emphasizing task breakdown, cost management, and improved performance through techniques like RAG, fine-tuning, and asynchronous workflows.