Fueled by vibes and with stars in their eyes, enterprises are not taking the time to understand genAI’s limitations and to create their own rules-based approach.
Overspending on AI infrastructure by cloud providers has some forecasting an AI bust, but there are signs that enterprises are starting to put AI to work.
Without skilled developers supervising AI coding assistants, they are likely to break your code rather than write it. Right now, only people can fine-tune and evaluate AI.
Yes, a tiny number of companies have relicensed their open source code. Let’s worry about actual problems, like security and megacompanies that contribute almost nothing.
Apache Airflow is a great data pipeline as code, but having most of its contributors work for Astronomer is another example of a problem with open source.
The inherent weaknesses of large language models are reason enough to explore other technologies, such as reinforcement learning or recurrent neural networks.
When the Open Source Definition isn’t applied to cloud-distributed software, and the General Public License allows cloud companies to grow rich without contributing much, everyone loses.
Is the complexity of billing better handled by buying software or building it? Lago offers developers a chance to get back to solving core business problems.
AI-generated code has transformed software development forever. That’s not necessarily good. A solid review process can shrink bloat and attack surfaces.
Data is the heart of the user experience, so shouldn’t developers start there? SQLite, NoSQL databases, and abstractions like Neurelo make that far easier to do.
GraphQL gives developers a flexible and unified way to connect data and services. Its query planning and policy engine make it a promising option for adding LLMs to the mix.