In this talk, I'll share how to streamline the entire AI integration from private data all the way to our JS projects, all in one line of code using Unbody.io. We'll explore the challenges that non-ai developers are facing with getting into AI world, and the simplicity behind Unbody, avoiding intimidating AI jargon, and focus on its practical application.

A fairly unknown feature of git is the concept of "working trees". In a nutshell, it allows you to have branches checked out as regular folders. This seemingly simple feature can be a game changer when working between multiple in-progress branches. Forget about stashing, or cross-branch dependency changes nightmares. You can even keep working while another branch is being built or tested! After this talk, you will know how to create and manage worktrees, how to get around their caveats, and the best way to make them the new base of your regular workflow.

APIs are the cornerstone of communication between services, yet we still treat the design of them as an afterthought. We spend huge amounts of time considering UIs and how users interact with them, why don't we do the same for APIs?

In this talk, I'll share how to streamline the entire AI integration from private data all the way to our JS projects, all in one line of code using Unbody.io. We'll explore the challenges that non-ai developers are facing with getting into AI world, and the simplicity behind Unbody, avoiding intimidating AI jargon, and focus on its practical application.

A fairly unknown feature of git is the concept of "working trees". In a nutshell, it allows you to have branches checked out as regular folders. This seemingly simple feature can be a game changer when working between multiple in-progress branches. Forget about stashing, or cross-branch dependency changes nightmares. You can even keep working while another branch is being built or tested! After this talk, you will know how to create and manage worktrees, how to get around their caveats, and the best way to make them the new base of your regular workflow.

APIs are the cornerstone of communication between services, yet we still treat the design of them as an afterthought. We spend huge amounts of time considering UIs and how users interact with them, why don't we do the same for APIs?