Android Dev to Backend Polyglot

Transcript

1. Android Dev to Backend Polyglot How lazy developers get more done with AI Nelson Osacky
2. Nelson Osacky Senior Software Engineer Sentry 6th Droidcon Berlin
3. How many backend devs? Either are a backend dev currently or were at one point?
4. How many use AI tools? Excluding Github Copilot and ChatGPT (sorry) OpenAI models or Codex count, Claude, Cursor, Firebender etc all count.
5. How many use text editors?
6. Lazy Developer
7. I choose a lazy person to do a hard job. Because a lazy person will find an easy way to do it. Bill Gates Not really but it is often attributed to him
8. My career
9. Android Dev Square, Soundcloud and others
11. Size Analysis, Build Distribution, AI Code Deletion
12. Typescript
13. Gradle AI is terrible at Gradle
15. Sentry
16. Great AI tools for devs
17. Claude workflows
18. Terminal Agent workflows They will all soon be the same anyways
19. Use ultrathink It uses more token and costs more Tip #1
20. Use ultrathink This isn’t good for the environment. Be conscience about this! Tip #1
21. Ask for simple solutions Tip #2
22. Write a good AGENTS.md Tip #3
23. Example • Write my AGENTS.md (/init) • Explain any gotchas or counterintuitive pieces of code • Build the app with gw assembleDebug • Run unit tests with gw unitTest • Run spotless apply before committing • We prefer coroutines, the RxJava code is legacy
24. Double check AI lies Tip #4
25. Double check • Read all the code that AI writes • Make sure the test is real! AI likes to write fake test or with fake data • Cleanup after it
26. Development lifecycle Plan Implement Test Debug
27. Development lifecycle Plan Implement Test Debug
28. Write client for backend Tip #5
29. Write client for the backend • The backend is at ../getsentry look at the code to understand how the build upload API works • Implement the sentry-cli build upload command based on the build upload API • Write a python server based on the build upload endpoint for my integration test
30. Use AI to rewrite code Rewrite Emerge into Sentry Tip #6
31. Use AI to examine the code Tip #7
32. Examine and rewrite with AI • Check in your old code in to the new codebase • In AGENTS.md, this old code is the base for the new features being implemented. Use it as a reference but don’t add new code there. • Examine the duplicate file analysis in the Emerge codebase to understand how it works • Write the duplicate file analysis feature based on the Emerge implementation in the Sentry codebase
33. Development lifecycle Plan Implement Test Debug
34. Write tools for you Tip #8
35. Write tools for you • Write a script to automate building and installing ◦ ./build_and_install.sh • In AGENTS.md, use build_and_install.sh • Update my AGENTS.md
36. Write tests Why are you writing these by hand? Tip #9
37. Write tests for you • Write a test for the new feature • Can you write a test that proves that the bug was resolved? • How would you test X feature? • Write a script to submit series of apk to the backend for testing load
38. Execute tests Tip #10
39. Run tests for you • Can you run this test? • Can you run all the PR checks?
40. Write commits and submit PRs for you Why are you writing these by hand? Tip #11
41. Write commits and submit PRs for you • Write a commit message for these changes • Write commit message or PR title conventions in AGENTS.md • Rebase my branch for me • Remove this commit from my git history
42. Slash commands for repetitive tasks DRY principle Tip #12
43. Slash commands for repetitive tasks • Slash commands are like bash scripts but for your agent • Create a commit message, push branch and create PR • /commit-push-pr • https:/ /github.com/anthropics/claude-code/blob/main/.cla ude/commands/commit-push-pr.md • Look at Anthropic repos for inspiration
44. Slash commands for repetitive tasks --- allowed-tools: Bash(git checkout --branch:*), Bash(git add:*), Bash(git status:*), Bash(git push:*), Bash(git commit:*), Bash(gh pr create:*) description: Commit, push, and open a PR --- ## Context - Current git status: !`git status` - Current git diff (staged and unstaged changes): !`git diff HEAD` - Current branch: !`git branch --show-current` ## Your task Based on the above changes: 1. Create a new branch if on main 2. Create a single commit with an appropriate message 3. Push the branch to origin 4. Create a pull request using `gh pr create` 5. You have the capability to call multiple tools in a single response. You MUST do all of the above in a single message. Do not use any other tools or do anything else. Do not send any other text or messages besides these tool calls.
45. Diagnose CI failures Tip #13
46. Diagnose CI failures • Can you fix the failing checks on this PR? • Can you check for any failures on this PR in 5 minutes? ◦ That doesn’t work yet, but I wish it did! ◦ It just echoed something to nowhere • Create a CI investigator agent /agents with permission to examine CI
47. Address PR comments Tip #14
48. Address PR comments • Can you address the PR comments on this PR? • Rebase my PR and fix merge conflicts
49. MCP Model context protocol
50. Read Documentation Tip #15
51. Documentation • Connect to docs • https:/ /context7.com/ • MCP server for documentation • Sentry docs • Help me setup Sentry • How does X work? • Write documentation for me!
52. Development lifecycle Plan Implement Test Debug
53. Read tickets/issues Tip #16
54. Deal with issue tracking • Connect to your issue tracker MCP • What issues are assigned to me? • What issue is the easiest to fix?
55. Resolve issues Tip #17
56. Deal with issue tracking • Can you link this PR to this issue and mark the issue as “In Review”? • Can you implement a fix for issue E-203? • Write your prompt in the issue ◦ Pretend the person reading the issue has 0 context
57. Development lifecycle Plan Implement Test Debug
58. Debug Tip #18
59. Debug • Add debug logging for this feature • Can you trace the codepath for this variable to this function?
60. Fix bugs Tip #19
61. Sentry MCP { "mcpServers": { "Sentry": { "url": "https://mcp.sentry.dev/mcp" } } }
62. Sentry MCP • Access Sentry issues and errors • Search for errors in specific files • Query projects and organizations • List and create Sentry DSN's for projects • Invoke Seer to automatically fix issues and retrieve the status and details of an issue fix
63. Fix bugs • Connect to the Sentry MCP • Explore crashes, issues • Solve crashes for me
64. Meet Seer: The AI debugger that works for you Seer is the only AI agent that uses the whole of Sentry’s context (errors, stack traces, commit history, logs, traces) to automatically debug the root cause of an issue and open a PR with a fix (and tests).
65. Clear the context often Tip #20
66. Clear the context often • Context windows are limited • Claude auto-compacts when approaching the context window (summarizes) • Clear before doing new work or switching branches • Claude can get confused or slow down
67. You are the main thread Opportunity cost of not running agents in the background Tip #21
68. https://claudelog.com/mechanics/you-are-the-main-thread/
69. You are the main thread • Work on multiple repos at once • Use git worktrees to work on multiple PRs at once
70. Full page Screenshot
71. Development lifecycle Plan Implement Test Debug
72. Development lifecycle Plan Implement Test Debug
73. • More best practices: https:/ /www.anthropic.com/engineering/claude-code-best -practices
74. Upcoming Sentry Features • Size Analysis • Build Distribution • Snapshot Testing
75. Serving +130k of the most innovative companies
76. Thank you Visit our booth for 3 months of free Sentry, stickers, etc Try sentry https:/ /sentry.io/signup/ We’re hiring https:/ /sentry.io/careers/ Nelson Osacky osacky.com