keithba
I’ve been very fascinated by the concept of a programming language designed for LLMs, both to that advantage of their strengths and to try and minimize their weaknesses.
Here’s a take I experimented with last year (feel very free to steal anything useful): https://github.com/GoogleCloudPlatform/aether/tree/feature/v...
(Note: main has a version that was an ugly syntax, the branch in the link was for a prettier attempt)
Every developer I’ve seen use these tools has have engaged in a meaningful contribution: specific directions across multiple prompts, often (though not always) editing the code afterwards, manually running the code and promoting for changes, etc.
Until the courts, legislators, or the copyright office define something otherwise, I’m highly confident of my assertion. (Mostly because of the insane number of hours I’ve spent with counsel on this. And, as a disclaimer, since I am biased: I worked on Copilot and Google’s various AI assisted coding products as an SVP and VP.)
I’ve worked with ashtom for over a decade. He’s a coding machine - easily one of the most technical executives (who ships real production code.)
Conductor: Context-driven development for Gemini CLI
https://github.com/GoogleCloudPlatform/aether
This was completely vibe coded - I never had to edit the code, though it was very interactive. The whole thing tool less than a month of some evenings and weekends.
(Note: it’s ugly on purpose, as I’m playing with ideas around languages that LLMs would naturally be effective using.)
5 Things to Try with Gemini 3 Pro in Gemini CLI
https://github.com/GoogleCloudPlatform/aether
Note: the syntax is ugly as a trade-off to make it explicit and unambiguous for LLMs to use.
Google's Gemini CLI Agent Comes to Zed
Auto-GPT: An Autonomous GPT-4 Experiment
For those who are interested, on the first Wednesday of each month, I write a blog post on our availability. Most recent one is here: https://github.blog/2021-03-03-github-availability-report-fe...
The Future is Tiny
We are looking at what we can do to make the SPA + mobile workflow super easy, though. Stay tuned on this. In the meantime, feel free to reach out to me as I'd love to ask you some more questions.
We've gone out of our way to make sure everything in the product is accessible via our REST API, and we also have a CLI you can install from npm.
Feel free to reach out to me and we could discuss your scenarios in more detail. There are other tools that may fit your scenario better.
Microsoft is very serious about creating amazing developer tool across any app, platform, and language for a variety of reasons. Making Azure the most productive place to power your app is part of it, of course. But, in the long run, the easier we make development, the more the world benefits.
We offer a full REST API and webhooks, so this also something you could cook up as an extension to the product in the meantime.
We are very proud of what we've built here. Regardless of how you built your app (Swift, Java, React Native, Xamarin), we offer CI, releasing to your beta users and the app stores, Crash reporting, analytics, and even push messaging. Let us know your thoughts!
Azure provides services for powering application and services (including compute, containers, storage, databases.)
App Center is focused on many of the lifecycle services (like CI, Crash reporting, distributing to beta testers and stores, etc).
App Center isn't part of the Visual Studio IDE. It's a Web-hosted service for app developers providing CI/CD, testing, and many other services.
My Year of Saying No
The Testing service supports iOS and Android apps written in any language or platform.