Explore >> Select a destination
|
You are here 
|
automationhacks.io | ||
| | | | |
ryanharter.com
|
|
| | | | | This is the third post in my Start to Finish series. Last time I talked about source control with Git. We've talked about basic tools, and about source control, so now we're ready to get into actually creating an Android app. In this part of the series, we're going to create a new project using Android Studio. Android Studio is Google's Integrated Development Environment (IDE) that we will use to create our Android app. | |
| | | | |
blog.jitendrapatro.me
|
|
| | | | | ||
| | | | |
piware.de
|
|
| | | | | ||
| | | | |
ezyang.github.io
|
|
| | | When you're learning to use a new framework or library, simple uses of the software can be done just by copy pasting code from tutorials and tweaking them as necessary. But at some point, it's a good idea to just slog through reading the docs from top-to-bottom, to get a full understanding of what is and is not possible in the software. One of the big wins of AI coding is that LLMs know so many things from their pretraining. For extremely popular frameworks that occur prominently in the pretraining set, an LLM is likely to have memorized most aspects of how to use the framework. But for things that are not so common or beyond the knowledge cutoff, you will likely get a model that hallucinates things. Ideally, an agentic model would know to do a web search and find the docs it needs. However, Sonnet does not currently support web search, so you have to manually feed it documentation pages as needed. Fortunately, Cursor makes this very convenient: simply dropping a URL inside a chat message will include its contents for the LLM. | ||
