https://graphapp.ai

Graph AIGraph is an intelligent interface layer across your developer tools and projects, putting answers and insights at your fingertips in SlackGraph AI Link to homeJoin the waitlistThe first know-it-all teammate you’ll love working withGraph is an intelligent interface layer across your dev tools and projects, putting answers and insights at your fingertips in SlackGraph9:00 AM☕ Morning, @Sam! 2 things to put on your radar this AM:A lengthy exchange between @Liam and @Alex on PR-353. Based on the tone of the conversation they seem blockedOn Friday a decision was made by @Dave in #project-pluto to move forward with GraphQL instead of RESTAlso Sprint 13 is still on track for 98% completion. 💪Sam9:02 AMThanks for flagging those things. What else happened on Friday while I was out?GraphApp9:02 AMFriday was busy. Here are the highlights:3 tickets were moved to “Done”: LN-487 “API timeout fix”, LN-481 “User Roles Refactor”, and LN-479 “Google SSO”⚠️ There was a minor outage. Very minimal downtime and impact. More details in #EE-154 PRs were merged, but as of last night PR-41 is still openSam9:04 AMIs there new dev work related to the outage we’ll need to pick up next sprint?GraphApp9:05 AMYes, 2 tickets were created related to the outage:LN-990 “Load Balancer Optimization” unassigned (1 point)LN-991 “Failover System Upgrade” unassigned (3 points)Both are currently unassigned. Should I assign and add them to the next sprint?Sam9:07 AMThat’d be great. With this new work the sprint will be over capacity. Can you find something we can punt without putting Q4 goals at risk?GraphApp9:07 AMDone and done. ✅I’ve added both tickets to Sprint 14 and assigned them to @Charlie. He had extra capacity and is most familiar with that part of the app.If our goal is still to have the notification system refactored by EoQ, I’d push LN-488 “Password Reset Flow”. While important, it’s not critical to the notification system work. Should I move that ticket from Sprint 14 to 15?Sam9:09 AMSounds like a plan. Please nudge the owner of that ticket and let them know why we're shuffling things aroundGraphApp9:10 AMThat ticket was assigned to @Alisha. I’ll send her a Slack with the context of our decision.Sam9:12 AMSpeaking of Sprint 15, we'll probably need to kick off the foundational work for the SAML project in Sprint 15. Last week I did a rough pass at what this system will look likeBased on my diagram, can you put together an action plan, break down the work into milestones, and make suggestions for who should own what pieces of work? Keep in mind we have Thanksgiving coming up as well, so lots of OOOGraphApp9:12 AMSure! Here’s a breakdown of work, divided into 3 milestones.I’ve suggested owners and story points for milestone 1, which we should be able to complete in Sprint 15. Based on Thanksgiving OOO, I’ve assigned everyone 40% less than they normally take on. 🦃
Once you 👍 my plan I’ll assign the tickets and prep the sprint.Milestone 1: Foundational Setup - 18 tickets, 6 engineers:Read moreSam9:16 AMThanks. I’ll review and let you know if I have any feedbackI’ve got 15 minutes until meetings start. Can you link me to that decision thread you mentioned in the Pluto channel? Need to get up to speed on that before my 1:1sGraphApp9:16 AMNic made the decision to have the team move forward with the GraphQL API instead of the REST API. Based on the implications of that decision for our team’s work, wanted to ensure you had a chance to weigh in.The conversation is in #project-pluto. Here’s the thread:NicolasA REST API will be more scalable for this use case, right?Thread in#project-pluto|Jul 26th|view messageSam9:17 AMThe downstream implications could be an issue. I’ll dive in and get a better handle on what they’re thinkingWhile I’m doing that, can you prep me for my 1:1 with Liam at 9:30? You mentioned the PR he’s blocked on, I’ll review that with him. What else do I need to know since our last 1:1?GraphApp9:17 AMHere’s a list of highlights for your 1:1 with @Liam:🚧 As mentioned, he appears blocked on PR-353The majority of his week was working on LN-482 “Data Sync Patch”, which he moved to “Final QA” on FridayHe’s picking up LN-484 “Dark Mode Toggle” this week; there's some back and forth in the comment section of that ticket that looks contentious, so worth reviewing with him🎉 He jumped in and played an active role in Friday’s outage, which would be great to acknowledge and celebrateSam9:18 AMPerfect! If you could set a reminder to send me this kind of update ahead of every 1:1 with @Liam, that would be terrificGraphApp9:18 AM☑️ I’ve set a reminder to send you an update at 9:15am PT every Tuesday morning ahead of your weekly 1:1 with @Liam. What it isAn autonomous AI agent, by engineers for engineers. Graph analyzes code repos, monitors project management tools, and understands your team structure. Through this 360° view, Graph surfaces insights, answers any question, and allows you to take action across your dev stack. All without leaving Slack.Why you'll love itCatch up in secondsPreemptively address issuesCut planning by 90%Ramp up fastOn-demand tl;dr, from PRs to project progressAfter vacation, you’re up to speed in secondsWrap up your week with a weekly snapshotGet up to speed after a day of focused codingPrep for team meetings and 1:1s minutes beforehandSara9:15 AM@Graph, what did I miss while I was out last week?GraphApp9:16 AMWelcome back, @Sara! The team’s been busy:Sprint 6 was kicked off yesterday5 PRs merged, 7 tickets marked as “Done”👀 Some noisy commentary on PR-893. I'd recommend you take a lookYou were also mentioned on 5 Jira tickets while you were out. Want to see those now?Zero in on the most pressing prioritiesGet notified of excessive back and forth on PRsHighlight potential confusion or friction on ticketsSurface key project decisions buried in Slack threadsFollow the bread crumbs, from debate to doneJoshApp9:15 AM@Josh, a few things to put on your radar this morning:PR-897 has been open 42% longer than average. Based on noisy PR commentary, the team appears to be blockedA new sprint kicked off yesterday and LN-381 “Sidebar modal” still doesn’t have a wireframe attachedFollowing yesterday’s incident, there’s a contentious debate in #project-atlas about the priority of EE-482Josh9:16 AM@Graph, Got it. Can you ping @Terri re the wireframe? And link me to the debate in #project-atlas?GraphApp9:16 AMSure! I just messaged @Terri. And here's the Slack thread:NicolasCould we change the priority of EE-482?Thread in#project-atlas|Jul 26th|view messageDitch planning, start doingTurn a rough concept into a development planBreakdown PRDs into milestones and stories with a clickPrep your team’s next sprint in secondsManage Jira and Linear without ever leaving SlackSara9:15 AM@Graph, we need to build this system for an upcoming project. Can you create an action plan that breaks down the work into milestones and suggest which engineers should tackle each part?GraphApp9:16 AMHere’s a breakdown of work needed for this new system:I’ve divided the work into 3 milestones and suggested owners and story points for milestone 1. @Erik has 40% fewer tickets since he’s OOO next week. Once you okay my plan I’ll assign the tickets.Milestone 1: API connector - 12 tickets across 4 engineers:LN-431 “RESTful API endpoints” @Liam (3 points)Read moreSara9:18 AMLooks good. Go ahead and assign those, then drop them into our next sprint✅1Go from rookie to veteran in minutesOnboard new engineers in record timeJump-start work on new projects or in different areas of the codeInstantly pinpoint relevant changes during root cause analysisIdentify SMEs who can provide context and support in unfamiliar areas of your appJosh9:15 AM@Graph, our notification service is having an outage. Send me everything that’s changed in that part of the app over the last few daysGraph9:16 AM🚒 Here are the changes that impacted the notification service in the past 72 hours:@Jamie merged PR-756 on Thursday AM; It included some minor improvements to the SendGrid connector@Erick merged PR-761 on Thursday PM; A database upgrade and very likely culprit@Zoe from Platform Eng merged PR-770 on Friday AM; It included some big updates to an adjacent system that could have had downstream implications@Eva and @Dave have the most experience in this system, but unfortunately they’re on PT and not online yet.Josh9:17 AMI’ll dig into 761 and 770 and go from there. Please add this information to the EE ticket so it’s documented✅1Eager to serveGraph comes out-of-the-box with dozens of skills designed to make your R&D org happier, faster, and more productive“What’s the response time of this code review”“What’s the team sentiment on this project?”“Why hasn’t this PR been merged yet?”“What’s my team’s velocity on this epic?”“What urgent tasks are at risk?”“Has there been any scope creep?”“Are there any merge conflicts?”“What’s the cycle time of this PR?”“What tickets are blocked?”“What tickets are blocked?”“Has there been any scope creep?”“What’s my team’s velocity on this epic?”“Why hasn’t this PR been merged yet?”“What’s the team sentiment on this project?”“What’s the cycle time of this PR?”“What urgent tasks are at risk?”“Are there any merge conflicts?”“What’s the response time of this code review”Coming soonTeach an AI agent to fishSince every team is unique, teach Graph new skills that will enable it to adapt to the specific working style and rhythms of your teamCode happierJoin the waitlist ResourcesBlogEngineering GlossaryDevOps GlossaryGit GlossaryCloud Computing GlossaryContainerization & Orchestration GlossaryCompanySecurityCopyright © 2024 Shiny Planes, Inc. All rights reserved.Built with ❤️️ from the friendly folks at LaunchNotesenen1731468301https://graphapp.ai

Guhindura urubuga rwawe?

Uriko ukora iki?