[2026-11-19] eagle: work/zoom-transcripts/2026-10-16 All-Company Meeting 2026-10-16 21 31(GMT+6 00) klekRLtLSEuMv0PCCPCjtA/transcript.json work/zoom-transcripts/2026-10-16 All-Company Meeting 2026-10-16 21 31(GMT+6 00) klekRLtLSEuMv0PCCPCjtA/transcript.md work/zoom-transcripts/2026-10-19 Michal Smaga's Personal Meeting Room QvxllpCuTTSLGEZp-R6jQw/transcript.json work/zoom-transcripts/2026-10-19 Michal Smaga's Personal Meeting Room QvxllpCuTTSLGEZp-R6jQw/transcript.md work/zoom-transcripts/2026-10-20 Dominik Kapusta's Personal Meeting Room Mg62hl1GSI2gw4XeGvHAsg/transcript.json work/zoom-transcripts/2026-10-20 Dominik Kapusta's Personal Meeting Room Mg62hl1GSI2gw4XeGvHAsg/transcript.md work/zoom-transcripts/index.json work/zoom-transcripts/sync-status.json work/zoom-transcripts/undated All-Company Meeting bPprGg5DTye9H-RQXkwMuw/transcript.json work/zoom-transcripts/undated All-Company Meeting bPprGg5DTye9H-RQXkwMuw/transcript.md
This commit is contained in:
1 parent
47fcad4344
commit
df6f0f149c
12 files changed
+3071
-791
No files matched your search
+85
@@ -23,6 +23,91 @@
|
||||
"time": "21:31:26",
|
||||
"speaker": "Gabriel Weinberg",
|
||||
"text": "Yeah."
|
||||
},
|
||||
{
|
||||
"time": "21:31:34",
|
||||
"speaker": "Anne Hildebrand",
|
||||
"text": "And also, uh, we want to make sure you get your questions answered around anything you want to discuss there, so submit a PeopleOps form, that's one way to do it. Um, if you do submit it without your name on the form, remember that the responses go to the project I've dropped in the channel there, so make sure not to miss those. That's it for me."
|
||||
},
|
||||
{
|
||||
"time": "21:31:58",
|
||||
"speaker": "Viktor Jansson",
|
||||
"text": "Alright, objective update from 05 Search Revenue. Last week, we held an assessment and switched the focus to evaluate ad experience and optimizations for search revenue. We will do this by evaluating if we can show ads from other providers for commercial queries, where Microsoft doesn't give us any ads, and how we can improve our overall shopping and product experience. For the optimizations, we have a few products in the pipeline, mainly for optimizing product ads, which we expect a potential $4 million a year revenue increase for. And the Duckbill Award goes to Renato, who ran a product during Quick Win Days to highlight prices for products on sale, which added half a million dollars a year, while at the same time helping our users to find discounted products. Great example of time well spent during Quick Win Days with a large impact to the objective KPIs. Over to Kirby for more million dollar updates."
|
||||
},
|
||||
{
|
||||
"time": "21:32:56",
|
||||
"speaker": "Kirby (she/they)",
|
||||
"text": "Hey, thanks Victor. So we built a lot this past cycle. We hit 150,000 active subscribers. We're tracking toward 180,000 by the end of this year, which is the stretch goal that we set out in our last cycle. And it's not official yet, but tentatively, we're working toward 300,000 as the goal for the end of next year, end of 2027. So more exciting updates to come. This slide is mostly about one A/B test that we did, and I want to take a minute to explain it, because it's really interesting. So we, in rough numbers, about 800 people start a subscription every day. Some of them are going direct into a paid subscription. Some of them are starting a free trial. Also, every day we have between 4 and 500 people canceling their subscription. So more than half. And the difference between those numbers is net subscriber additions. That's OO's KPI. So we're not just trying to get more people to start a subscription. We're also trying to get fewer people to cancel. And one way we're doing that is by giving people a better day zero experience as soon as they subscribe, creating subscriber onboarding. But another way we're doing it is by shifting people over to yearly plans. So we've got monthly, we've got yearly. Monthly plans have a 14% churn rate. That's the likelihood that someone will cancel every month. Yearly plans, it's only 2%, because you only have one opportunity to churn. every year. So to try to shift people toward yearly, we tested removing the free trial option from monthly plans to make yearly a little more appealing. And we did this first on Android, and we saw what we expected or what we hoped for. which is that fewer people are getting a subscription, because some people will see that there's no free trial on monthly, they don't want yearly, they bounce. But of the people who do stick around, more of them are on yearly, and we modeled it out so that we'd catch up with where. our growth would have been within a few months. Then we also did it on iOS, and we saw something surprising, which is that iOS users will just buy the monthly subscription with no free trial, and more of them are going yearly also. So the number of extra people we got on iOS. cancels out the people we lost on Android. So there's no cost. It's not going to take any time to catch up with where our growth would have been. We're just getting the extra lifetime value of each of these users by shifting more people over to yearly. And we're going to reduce the churn rate from where it is now, 9.5%, which is pretty good compared to the industry standard for VPNs. We want it to be at 7% and we want it to stay there. And a year from now, just from this one experiment. we're going to get down to 7.2% churn from having more people coming in on yearly plans. So if you're close to OO, you know that we work really hard to get one experiment out right after the last one. And this is why we never know. when we're gonna have one that's even more valuable than we'd anticipated. In lifetime value, which is different from revenue, but it's the projected amount of revenue we expect to get per user, we're adding 5 million in lifetime value per. year just from this one experiment. So the next time we're moving quickly to get something out for an experiment, out of the way, because these are really valuable and interesting. And congratulations to the team for all the work that got done. Super congratulations to Bartek, who's come on in a tech lead role. And as soon as he got to the objective, he got up to speed really quickly. and is our Duckbill winner because he has been accelerating the timelines in project after project by just thinking of something we didn't think of, coming up with a simpler way to solve something, and he connected the dots between incidents that we've been seeing across platforms where users are getting logged out and we don't know why. And he'd figured out a path forward, turned it into an SLO, and owned it, and is getting it fixed. Congratulations, Bartek. And next, on to Russell, I think."
|
||||
},
|
||||
{
|
||||
"time": "21:37:23",
|
||||
"speaker": "russell holt",
|
||||
"text": "Thanks, Gary. Hi, yeah, Russell here with an update for OE, where we are working on cookie prompt management and ad blocking. Um, for CPM, we've been, uh, improving the automated pipeline, which processes. uh, fixes and unhandled sites. And at this point, about 50% of these changes, uh, to our data set are fully automated, meaning no human involvement, which is pretty exciting. And right now we're at about overall 73% coverage, uh, in the US. Right now. So, one thing that we did this cycle is we finally got a reasonable opt-in rate. um, of 65% on Android, similar to iOS for CPM. Uh, which is a flow we've been struggling with for a bit, because we have a lot of cases where we need user consent. to automatically do something for them for legal reasons. And in this case, it was we need to accept cookies under certain circumstances to raise that coverage to improve the experience. And it's been a little bit of trouble, but that was great. So, on this cycle, we're really doubling down on the CPM automation, making the agent faster, more accurate, improving heuristic pop-up detection, doing regression testing, and this is really the key. to the long-term maintenance mode for CPM, which is finally in sight again, which we're pretty excited about. Um, and on the ad blocking side, uh, we're moving forward with two of the main feature requests. that we got from our analysis after the big YouTube ad blocking launch. Um, which will be… One, expanding ad blocking to a selection of top sites, starting with adult sites. And then two, on YouTube specifically, giving users the ability to skip sponsored segments. sponsored content segments, which look like ads to people. Uh, through YouTube. So, the goal there is to give people more control. and make a better default experience, even for YouTube Premium. where people see these sponsored segments as ads, so better not block. All right, that's it for OE. I guess on to Emmanuelle."
|
||||
},
|
||||
{
|
||||
"time": "21:39:42",
|
||||
"speaker": "Emanuele Feliziani",
|
||||
"text": "Yes, Russell, thanks. Exciting updates on the CDM and unblocking stuff. We had OI assessment last week. We will keep the focus on ChatSync. We will have a hopefully final push to stabilize the ChatSync system. So this will be more of a milestone focus. And we'll focus, yes, on stabilization. What we've done in the sparse cycle, we've optimized. the Syncflow on several platforms, both mobile and, uh, like, native and, um, and third-party, and we also shipped, uh, promos for ChatSync. For third parties, we've seen a significant inflow of users from those promos. We've doubled the daily activations and the daily active users for third parties specifically is up almost 5x. And it's 30% across all platforms. So really nice bump in users there. We're still not happy with the adoption. We want more. We are also not happy with the conversion rates. So we will keep iterating. in the… in future cycles, so after this one. Uh, in the meantime, we are also running, uh, user research to try and understand the drop of… the drop of points, the points of confusion. For users during the sync setup flow and see where we can be more helpful towards our users, making sure that they are able to set up sync. um… across multiple devices especially. We'll also look into ways to make the sync entry point more prominent. We've already seen that people struggle to find it in the settings, it's kind of buried, so we try to make it more prominent, lift it up a little bit, make it more intuitive how to use it. Um, and yeah. That's it for ROI. The duck bill goes to Pablo Serrano, the pub RR. designer, Serrano, uh, designer Pablo, we also have a Pablo on the back end. Uh, and yeah, he's, he's been great. Uh, he's been great for a long time and this cycle we are happy to congratulate him, uh, with, with the award. And, uh, yeah, he's been, uh, he's been great, uh, on the project advisory side, very quick and tidy on the design front. And he's been, diving into the metrics with, with Gusto. So, really happy to see Pablo grow in this role. Thanks, Pablo, and congrats. Uh, next up, I think, is, uh, team member, uh, updates with John Russell."
|
||||
},
|
||||
{
|
||||
"time": "21:42:36",
|
||||
"speaker": "Jon Russo",
|
||||
"text": "Hi. Didn't realize I was coming up this soon. But, hi, everybody. I'm John from the CloudOps team. I guess I'm Matt. Two different angles here. One from the work side. Recently, I started working on some of our Kubernetes stuff, which is really exciting and a little intimidating for me. I've been wanting to kind of dip my toes into this technology for a while, and it's nice to be able to finally do it. I got a lot of people on the team helping me in that, and kind of designing a new deployment spec for some of our new Kubernetes clusters. So that's fun and exciting in the infra velocity kind of project there. On a personal side, two pretty exciting things coming up. One tomorrow, I've been doing a lot of trail running this past year, and I have a half marathon coming up at a place called Von Trapp Mountain. Um, it's just outside of Stowe, Vermont, if anybody knows the area. Uh, the Von Trapp family is famous from The Sound of Music, uh, movies way back in the day, and it's an absolutely beautiful property up there. Um, so it's gonna be a fun race, um… there that has about 2,000 feet of elevation gain in it. I think that's roughly like 600 meters for the Europeans. The weather is looking pretty terrible, actually, so it might be a bit of a slop fest. We're expected to get an inch of rain today, and then it's going to be 33 degrees Fahrenheit at the start of the race, about 1 degree Celsius, so pretty dang cold. Um, and then the other side is that, uh, about a couple weeks ago, I booked a trip to Japan for end of January. Uh, this is something I've always wanted to do. It's been a bucket list trip for me to go skiing there. Um, so me and a couple friends are going to Hokkaido for two weeks. And, uh, traveling around in a van, and kind of exploring all the resorts there, and doing some backcountry skiing, uh, maybe even backcountry skiing into a volcano. Um, so that should be fun. Yeah, that's it for me. Thanks."
|
||||
},
|
||||
{
|
||||
"time": "21:44:56",
|
||||
"speaker": "Stephen",
|
||||
"text": "Oh, I think this is me. Hi, so we've been working on a refreshed new tab page for iOS for a while, and we're finally getting ready for the first internal release. It should be next week. I think there's a link in there if you want to enable it early. I tried to make a video. So this would work out well, but that didn't work. So we're gonna do it live demo real quick. So hopefully this does work out. I'm gonna try to. share this via… My phone. So if it doesn't work, someone please yell at me. Okay. Hopefully you can see my phone."
|
||||
},
|
||||
{
|
||||
"time": "21:45:37",
|
||||
"speaker": "Spencer",
|
||||
"text": "Yes."
|
||||
},
|
||||
{
|
||||
"time": "21:45:38",
|
||||
"speaker": "Stephen",
|
||||
"text": "Okay, awesome. Thank you. So… So here's the new tab — the new, new tab page. Kind of a weird phrasing. But you can see it's more brand forward. We have Dax there. He's got some Dax greetings. We have a nice background illustration there in the background. And the greetings will update. Probably not this frequently, but you can kind of see there's a few in there and we're going to update them based on time of day and some other stuff. The toggle's right there so you can switch between chat and search pretty easily. And you can see we have. Placeholder favorites now. So these are not hidden by default. So this is kind of inviting people to add more favorites. I could add one. Maybe. Yep, and there's that one, so that goes there. But we don't show the, uh… icon until you go there once. And then we also have… The return to hatch there. So you can get back to that. You can swipe it away if you want. Also get to your new tabs easier. And… I think I lost my window. I have too many DuckDuckGo's going here. You can also… Have a lot of favorites. So they scroll and expand and contract. And you can use the customization right on the page now, so you can toggle them on and off. From here, change some settings, we're gonna add some more there as well, and it also has… Dark mode, so if you want a cool fancy dark mode, you can have that as well, and everything should look… Nice there as well. So if you want to try that out, you can wait till next week, or you can follow the link and turn it on for yourself now."
|
||||
},
|
||||
{
|
||||
"time": "21:47:35",
|
||||
"speaker": "Julia Abreu",
|
||||
"text": "We had one more demo added to the agenda, but there is no name there. So, how to enable Redesign NTP? Does anyone…"
|
||||
},
|
||||
{
|
||||
"time": "21:47:45",
|
||||
"speaker": "Gabriel Weinberg",
|
||||
"text": "I think that's Brett Stevens."
|
||||
},
|
||||
{
|
||||
"time": "21:47:46",
|
||||
"speaker": "Stephen",
|
||||
"text": "Oh, yeah, that was part of mine, sorry."
|
||||
},
|
||||
{
|
||||
"time": "21:47:48",
|
||||
"speaker": "Gabriel Weinberg",
|
||||
"text": "Yeah."
|
||||
},
|
||||
{
|
||||
"time": "21:47:48",
|
||||
"speaker": "Julia Abreu",
|
||||
"text": "Oh, okay, cool. Just wanted to make sure that there was no extra in there. Uh, okay, before we wrap up, I just wanted to say or remind everybody that next day we have Hack Days. Um, it's the last Hack Days of the year. We will have a quick win in, uh, December. If you want to check the dates, you can see the AOR for special days. I am just drafting the calendar for next year, so I'll get Gabriel to take a look, and then I will post it as well under the AOR. I am working on some ideas on how to make the meeting for the demos a little shorter. I don't want to make it. every demo shorter than 2 minutes, because, um, I know you all wouldn't like that, but I'm trying to figure out, um, some ways that maybe we can split demos in different days, or, like, so if you have any ideas, or if you would like to help in any way. please go ahead and ping me. And otherwise, I just have one personal update that is special for Elle. Um, this is Maple. This is our third Dash Hound. Um, I am completely out of control now that I have a garden, so, um, I might be just sharing a new Dutch hound every week. Uh, and if I get her to not bark at everyone, I will bring her to our next meetup, uh, because the other two are not. very well trained. Um, so that's it for me. I hope you all have a great weekend, and uh… we'll roll out GPT for next week."
|
||||
},
|
||||
{
|
||||
"time": "21:49:17",
|
||||
"speaker": "Gabriel Weinberg",
|
||||
"text": "Yeah, one idea for you, Julia, for everyone here, is that to make less demos, you can collaborate with each other on projects, so… I'm not sure our best process for that at the moment, but there's the Hack Days project. You can say what you're gonna work on in there and try to recruit people. There's, we have a Mattermost channel too, don't we? Do you? Or if not, maybe we should."
|
||||
},
|
||||
{
|
||||
"time": "21:49:37",
|
||||
"speaker": "Julia Abreu",
|
||||
"text": "We do have, yes, specialties."
|
||||
},
|
||||
{
|
||||
"time": "21:49:40",
|
||||
"speaker": "Gabriel Weinberg",
|
||||
"text": "Maybe that's the place to go. Go to the Mattermost channel. Um, okay, hope everyone's gonna be good."
|
||||
}
|
||||
]
|
||||
}
|
||||
+17
@@ -15,3 +15,20 @@ source: "https://us01mynotes.zoom.us/klekRLtLSEuMv0PCCPCjtA"
|
||||
- **21:31:08 · Gabriel Weinberg:** Hello? That was a nice fade out. Um… Okay… No new team members, no AOR updates. Um, we had one company update, there's no name by it.
|
||||
- **21:31:23 · Anne Hildebrand:** Sorry, that was me. Um, yes, this is Anne. Uh, just a reminder to check your inboxes for the outcome of the compensation review.
|
||||
- **21:31:26 · Gabriel Weinberg:** Yeah.
|
||||
- **21:31:34 · Anne Hildebrand:** And also, uh, we want to make sure you get your questions answered around anything you want to discuss there, so submit a PeopleOps form, that's one way to do it. Um, if you do submit it without your name on the form, remember that the responses go to the project I've dropped in the channel there, so make sure not to miss those. That's it for me.
|
||||
- **21:31:58 · Viktor Jansson:** Alright, objective update from 05 Search Revenue. Last week, we held an assessment and switched the focus to evaluate ad experience and optimizations for search revenue. We will do this by evaluating if we can show ads from other providers for commercial queries, where Microsoft doesn't give us any ads, and how we can improve our overall shopping and product experience. For the optimizations, we have a few products in the pipeline, mainly for optimizing product ads, which we expect a potential $4 million a year revenue increase for. And the Duckbill Award goes to Renato, who ran a product during Quick Win Days to highlight prices for products on sale, which added half a million dollars a year, while at the same time helping our users to find discounted products. Great example of time well spent during Quick Win Days with a large impact to the objective KPIs. Over to Kirby for more million dollar updates.
|
||||
- **21:32:56 · Kirby (she/they):** Hey, thanks Victor. So we built a lot this past cycle. We hit 150,000 active subscribers. We're tracking toward 180,000 by the end of this year, which is the stretch goal that we set out in our last cycle. And it's not official yet, but tentatively, we're working toward 300,000 as the goal for the end of next year, end of 2027. So more exciting updates to come. This slide is mostly about one A/B test that we did, and I want to take a minute to explain it, because it's really interesting. So we, in rough numbers, about 800 people start a subscription every day. Some of them are going direct into a paid subscription. Some of them are starting a free trial. Also, every day we have between 4 and 500 people canceling their subscription. So more than half. And the difference between those numbers is net subscriber additions. That's OO's KPI. So we're not just trying to get more people to start a subscription. We're also trying to get fewer people to cancel. And one way we're doing that is by giving people a better day zero experience as soon as they subscribe, creating subscriber onboarding. But another way we're doing it is by shifting people over to yearly plans. So we've got monthly, we've got yearly. Monthly plans have a 14% churn rate. That's the likelihood that someone will cancel every month. Yearly plans, it's only 2%, because you only have one opportunity to churn. every year. So to try to shift people toward yearly, we tested removing the free trial option from monthly plans to make yearly a little more appealing. And we did this first on Android, and we saw what we expected or what we hoped for. which is that fewer people are getting a subscription, because some people will see that there's no free trial on monthly, they don't want yearly, they bounce. But of the people who do stick around, more of them are on yearly, and we modeled it out so that we'd catch up with where. our growth would have been within a few months. Then we also did it on iOS, and we saw something surprising, which is that iOS users will just buy the monthly subscription with no free trial, and more of them are going yearly also. So the number of extra people we got on iOS. cancels out the people we lost on Android. So there's no cost. It's not going to take any time to catch up with where our growth would have been. We're just getting the extra lifetime value of each of these users by shifting more people over to yearly. And we're going to reduce the churn rate from where it is now, 9.5%, which is pretty good compared to the industry standard for VPNs. We want it to be at 7% and we want it to stay there. And a year from now, just from this one experiment. we're going to get down to 7.2% churn from having more people coming in on yearly plans. So if you're close to OO, you know that we work really hard to get one experiment out right after the last one. And this is why we never know. when we're gonna have one that's even more valuable than we'd anticipated. In lifetime value, which is different from revenue, but it's the projected amount of revenue we expect to get per user, we're adding 5 million in lifetime value per. year just from this one experiment. So the next time we're moving quickly to get something out for an experiment, out of the way, because these are really valuable and interesting. And congratulations to the team for all the work that got done. Super congratulations to Bartek, who's come on in a tech lead role. And as soon as he got to the objective, he got up to speed really quickly. and is our Duckbill winner because he has been accelerating the timelines in project after project by just thinking of something we didn't think of, coming up with a simpler way to solve something, and he connected the dots between incidents that we've been seeing across platforms where users are getting logged out and we don't know why. And he'd figured out a path forward, turned it into an SLO, and owned it, and is getting it fixed. Congratulations, Bartek. And next, on to Russell, I think.
|
||||
- **21:37:23 · russell holt:** Thanks, Gary. Hi, yeah, Russell here with an update for OE, where we are working on cookie prompt management and ad blocking. Um, for CPM, we've been, uh, improving the automated pipeline, which processes. uh, fixes and unhandled sites. And at this point, about 50% of these changes, uh, to our data set are fully automated, meaning no human involvement, which is pretty exciting. And right now we're at about overall 73% coverage, uh, in the US. Right now. So, one thing that we did this cycle is we finally got a reasonable opt-in rate. um, of 65% on Android, similar to iOS for CPM. Uh, which is a flow we've been struggling with for a bit, because we have a lot of cases where we need user consent. to automatically do something for them for legal reasons. And in this case, it was we need to accept cookies under certain circumstances to raise that coverage to improve the experience. And it's been a little bit of trouble, but that was great. So, on this cycle, we're really doubling down on the CPM automation, making the agent faster, more accurate, improving heuristic pop-up detection, doing regression testing, and this is really the key. to the long-term maintenance mode for CPM, which is finally in sight again, which we're pretty excited about. Um, and on the ad blocking side, uh, we're moving forward with two of the main feature requests. that we got from our analysis after the big YouTube ad blocking launch. Um, which will be… One, expanding ad blocking to a selection of top sites, starting with adult sites. And then two, on YouTube specifically, giving users the ability to skip sponsored segments. sponsored content segments, which look like ads to people. Uh, through YouTube. So, the goal there is to give people more control. and make a better default experience, even for YouTube Premium. where people see these sponsored segments as ads, so better not block. All right, that's it for OE. I guess on to Emmanuelle.
|
||||
- **21:39:42 · Emanuele Feliziani:** Yes, Russell, thanks. Exciting updates on the CDM and unblocking stuff. We had OI assessment last week. We will keep the focus on ChatSync. We will have a hopefully final push to stabilize the ChatSync system. So this will be more of a milestone focus. And we'll focus, yes, on stabilization. What we've done in the sparse cycle, we've optimized. the Syncflow on several platforms, both mobile and, uh, like, native and, um, and third-party, and we also shipped, uh, promos for ChatSync. For third parties, we've seen a significant inflow of users from those promos. We've doubled the daily activations and the daily active users for third parties specifically is up almost 5x. And it's 30% across all platforms. So really nice bump in users there. We're still not happy with the adoption. We want more. We are also not happy with the conversion rates. So we will keep iterating. in the… in future cycles, so after this one. Uh, in the meantime, we are also running, uh, user research to try and understand the drop of… the drop of points, the points of confusion. For users during the sync setup flow and see where we can be more helpful towards our users, making sure that they are able to set up sync. um… across multiple devices especially. We'll also look into ways to make the sync entry point more prominent. We've already seen that people struggle to find it in the settings, it's kind of buried, so we try to make it more prominent, lift it up a little bit, make it more intuitive how to use it. Um, and yeah. That's it for ROI. The duck bill goes to Pablo Serrano, the pub RR. designer, Serrano, uh, designer Pablo, we also have a Pablo on the back end. Uh, and yeah, he's, he's been great. Uh, he's been great for a long time and this cycle we are happy to congratulate him, uh, with, with the award. And, uh, yeah, he's been, uh, he's been great, uh, on the project advisory side, very quick and tidy on the design front. And he's been, diving into the metrics with, with Gusto. So, really happy to see Pablo grow in this role. Thanks, Pablo, and congrats. Uh, next up, I think, is, uh, team member, uh, updates with John Russell.
|
||||
- **21:42:36 · Jon Russo:** Hi. Didn't realize I was coming up this soon. But, hi, everybody. I'm John from the CloudOps team. I guess I'm Matt. Two different angles here. One from the work side. Recently, I started working on some of our Kubernetes stuff, which is really exciting and a little intimidating for me. I've been wanting to kind of dip my toes into this technology for a while, and it's nice to be able to finally do it. I got a lot of people on the team helping me in that, and kind of designing a new deployment spec for some of our new Kubernetes clusters. So that's fun and exciting in the infra velocity kind of project there. On a personal side, two pretty exciting things coming up. One tomorrow, I've been doing a lot of trail running this past year, and I have a half marathon coming up at a place called Von Trapp Mountain. Um, it's just outside of Stowe, Vermont, if anybody knows the area. Uh, the Von Trapp family is famous from The Sound of Music, uh, movies way back in the day, and it's an absolutely beautiful property up there. Um, so it's gonna be a fun race, um… there that has about 2,000 feet of elevation gain in it. I think that's roughly like 600 meters for the Europeans. The weather is looking pretty terrible, actually, so it might be a bit of a slop fest. We're expected to get an inch of rain today, and then it's going to be 33 degrees Fahrenheit at the start of the race, about 1 degree Celsius, so pretty dang cold. Um, and then the other side is that, uh, about a couple weeks ago, I booked a trip to Japan for end of January. Uh, this is something I've always wanted to do. It's been a bucket list trip for me to go skiing there. Um, so me and a couple friends are going to Hokkaido for two weeks. And, uh, traveling around in a van, and kind of exploring all the resorts there, and doing some backcountry skiing, uh, maybe even backcountry skiing into a volcano. Um, so that should be fun. Yeah, that's it for me. Thanks.
|
||||
- **21:44:56 · Stephen:** Oh, I think this is me. Hi, so we've been working on a refreshed new tab page for iOS for a while, and we're finally getting ready for the first internal release. It should be next week. I think there's a link in there if you want to enable it early. I tried to make a video. So this would work out well, but that didn't work. So we're gonna do it live demo real quick. So hopefully this does work out. I'm gonna try to. share this via… My phone. So if it doesn't work, someone please yell at me. Okay. Hopefully you can see my phone.
|
||||
- **21:45:37 · Spencer:** Yes.
|
||||
- **21:45:38 · Stephen:** Okay, awesome. Thank you. So… So here's the new tab — the new, new tab page. Kind of a weird phrasing. But you can see it's more brand forward. We have Dax there. He's got some Dax greetings. We have a nice background illustration there in the background. And the greetings will update. Probably not this frequently, but you can kind of see there's a few in there and we're going to update them based on time of day and some other stuff. The toggle's right there so you can switch between chat and search pretty easily. And you can see we have. Placeholder favorites now. So these are not hidden by default. So this is kind of inviting people to add more favorites. I could add one. Maybe. Yep, and there's that one, so that goes there. But we don't show the, uh… icon until you go there once. And then we also have… The return to hatch there. So you can get back to that. You can swipe it away if you want. Also get to your new tabs easier. And… I think I lost my window. I have too many DuckDuckGo's going here. You can also… Have a lot of favorites. So they scroll and expand and contract. And you can use the customization right on the page now, so you can toggle them on and off. From here, change some settings, we're gonna add some more there as well, and it also has… Dark mode, so if you want a cool fancy dark mode, you can have that as well, and everything should look… Nice there as well. So if you want to try that out, you can wait till next week, or you can follow the link and turn it on for yourself now.
|
||||
- **21:47:35 · Julia Abreu:** We had one more demo added to the agenda, but there is no name there. So, how to enable Redesign NTP? Does anyone…
|
||||
- **21:47:45 · Gabriel Weinberg:** I think that's Brett Stevens.
|
||||
- **21:47:46 · Stephen:** Oh, yeah, that was part of mine, sorry.
|
||||
- **21:47:48 · Gabriel Weinberg:** Yeah.
|
||||
- **21:47:48 · Julia Abreu:** Oh, okay, cool. Just wanted to make sure that there was no extra in there. Uh, okay, before we wrap up, I just wanted to say or remind everybody that next day we have Hack Days. Um, it's the last Hack Days of the year. We will have a quick win in, uh, December. If you want to check the dates, you can see the AOR for special days. I am just drafting the calendar for next year, so I'll get Gabriel to take a look, and then I will post it as well under the AOR. I am working on some ideas on how to make the meeting for the demos a little shorter. I don't want to make it. every demo shorter than 2 minutes, because, um, I know you all wouldn't like that, but I'm trying to figure out, um, some ways that maybe we can split demos in different days, or, like, so if you have any ideas, or if you would like to help in any way. please go ahead and ping me. And otherwise, I just have one personal update that is special for Elle. Um, this is Maple. This is our third Dash Hound. Um, I am completely out of control now that I have a garden, so, um, I might be just sharing a new Dutch hound every week. Uh, and if I get her to not bark at everyone, I will bring her to our next meetup, uh, because the other two are not. very well trained. Um, so that's it for me. I hope you all have a great weekend, and uh… we'll roll out GPT for next week.
|
||||
- **21:49:17 · Gabriel Weinberg:** Yeah, one idea for you, Julia, for everyone here, is that to make less demos, you can collaborate with each other on projects, so… I'm not sure our best process for that at the moment, but there's the Hack Days project. You can say what you're gonna work on in there and try to recruit people. There's, we have a Mattermost channel too, don't we? Do you? Or if not, maybe we should.
|
||||
- **21:49:37 · Julia Abreu:** We do have, yes, specialties.
|
||||
- **21:49:40 · Gabriel Weinberg:** Maybe that's the place to go. Go to the Mattermost channel. Um, okay, hope everyone's gonna be good.
|
||||
-650
@@ -23,656 +23,6 @@
|
||||
"time": "18:10:09",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Uh, I think I'm, I'm like… done reviewing the first one about the pixel. I had the issue that I wasn't able to reproduce it, like, I was trying to kill the WebKit process."
|
||||
},
|
||||
{
|
||||
"time": "18:10:22",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "18:10:23",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Do you have any, like, extra steps?"
|
||||
},
|
||||
{
|
||||
"time": "18:10:27",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Uh, so generally it fails from the second try on this exact test page that is attached there."
|
||||
},
|
||||
{
|
||||
"time": "18:10:37",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "So after, after I, I killed the, the, the…"
|
||||
},
|
||||
{
|
||||
"time": "18:10:37",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay."
|
||||
},
|
||||
{
|
||||
"time": "18:10:41",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Web extension, web process. I should reload the page?"
|
||||
},
|
||||
{
|
||||
"time": "18:10:47",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yes, in general."
|
||||
},
|
||||
{
|
||||
"time": "18:10:49",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Do I need to do it, like, quickly, or do I need to, like…"
|
||||
},
|
||||
{
|
||||
"time": "18:10:53",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Um…"
|
||||
},
|
||||
{
|
||||
"time": "18:10:53",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Wait a bit."
|
||||
},
|
||||
{
|
||||
"time": "18:10:55",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Usually… yeah. I don't know, within one second, just kill the process, then reload the page."
|
||||
},
|
||||
{
|
||||
"time": "18:11:02",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:11:03",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "If it doesn't work from the first try, you just give it and reload again, and usually from second attempt, it does, uh… Uh, hang the… the extension. So it's not… it's not the genuine issue, so it's the…"
|
||||
},
|
||||
{
|
||||
"time": "18:11:20",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, artificial."
|
||||
},
|
||||
{
|
||||
"time": "18:11:22",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "artificial reproducing step that we didn't enable with the feature flag of the fix that went before, but it should be still here, and we… and allow to… To produce it. Uh, that's… So generally, yeah, I think you've seen the comment I posted to… to the… Project communication task. And the data, the data analysis."
|
||||
},
|
||||
{
|
||||
"time": "18:11:52",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, yeah, yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:11:52",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "So… so generally there is, uh… yeah, it's kind of heavy codecs and cloud work, and, um… I cannot… Oh. I cannot tell that I understand, like, 100% what is happening beneath, uh, under the hood, and… Um… Generally, we have reproduced most of the… of the stall issues, uh, with some… Thank you. my display on black. Wow. I just need to switch off something, I guess."
|
||||
},
|
||||
{
|
||||
"time": "18:12:35",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "I can hear you, I cannot see you."
|
||||
},
|
||||
{
|
||||
"time": "18:12:36",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Hello? Yeah, I cannot see you, because… Give it a minute. Yeah. No. Fuck. And… Good morning, Mark. Sorry. One moment, Amy. I need to burn off something."
|
||||
},
|
||||
{
|
||||
"time": "18:13:10",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Did your laptop display died?"
|
||||
},
|
||||
{
|
||||
"time": "18:13:13",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Not yet, I guess. I hope. Uh, here… Here we are. Uh-huh. So, we do. Yeah. All right, I'm back. And… Oh, yeah, I just got some. Testing. Fairness around here. Uh, where was I? Yeah, the issues. Uh, so generally, there's four issues in the work, and uh… One is behind the disabled feature flag. Because it reloads the page, and I don't think it's optimal. And probably a couple of more go next, and we'll leave. the smallest groups for the next iteration, I guess. So here we have to, uh… To expand the diagnostics. So generally, to fulfill the privacy triage, uh, I was requested to… To reduce what we… actually submit, and the decision was to merge the events into a single event. It should not generally harm our, uh… our data. We can lose something in case the browser crashes, or if it's reloaded. But I guess it's acceptable at this point, since we get these isolated groups already. And we just need some proofs. for the remaining and the pixels. Prior to this."
|
||||
},
|
||||
{
|
||||
"time": "18:15:02",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yes. So, so the first…"
|
||||
},
|
||||
{
|
||||
"time": "18:15:04",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Pixel fire for the pixel, yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:15:06",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "First PR is the pixels, yeah? So the one from the PR."
|
||||
},
|
||||
{
|
||||
"time": "18:15:09",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yes, so the suggestion is to improve the diagnostics first, and then the stacked ones go onto it."
|
||||
},
|
||||
{
|
||||
"time": "18:15:18",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, and what is the status of the other, like, PRs, the follow-up ones, with the fixes?"
|
||||
},
|
||||
{
|
||||
"time": "18:15:24",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Uh, so we have the… the recovery. And… First one is InitLoss. And InitLoss includes P1 and P2 as inputs. As I remember. Yeah, and P4, that's not enabled at the moment. It's, uh, 7379. It should be… Should be generated already. For review. And another one is 7459. It's also open. And… Well, generally, should also be pretty much ready, so the… There is integration tests, integration test harness that's supposed to only be run once to reproduce the issue."
|
||||
},
|
||||
{
|
||||
"time": "18:16:38",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "18:16:39",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "In, like, lab condition."
|
||||
},
|
||||
{
|
||||
"time": "18:16:40",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Can you say. Which one was the last PR?"
|
||||
},
|
||||
{
|
||||
"time": "18:16:45",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "The last one, uh, 7459. This one."
|
||||
},
|
||||
{
|
||||
"time": "18:17:00",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, yeah, yeah, I got it, yeah, the network one, yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:17:11",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "So the first, that is 7379, it should… So basically, we guess that it may be not an issue. And it's maybe an issue of slow. Slow loading and the fix itself is triggering the background will be load with the navigation itself. Because, uh, the initial… initial startup, or return from background, maybe not, uh, warming up the web view. Or, um… Or our extension. And, uh… The situation with P4 is that we may need to reload the page after, you know, after the extension is loaded, so it is applied to the page. And, uh, I was planning to investigate it further. Is there a way to run the… Plug in after the page is already loaded, maybe send another page load event. And see if it… if it just works. Uh, but the reload is there. And the feature flag."
|
||||
},
|
||||
{
|
||||
"time": "18:18:36",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "And do you think, like, uh… Are we able to detect the fourth one without the feature flag? Just to get the pixels about, like, how…"
|
||||
},
|
||||
{
|
||||
"time": "18:18:48",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Just to get the pixels… yeah, I guess so. I guess so we can make the pixel."
|
||||
},
|
||||
{
|
||||
"time": "18:18:59",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, because it would be get, like. It's good to get the signal, like, how many of those cases they potentially would be fixed by the future flag."
|
||||
},
|
||||
{
|
||||
"time": "18:19:11",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, I agree."
|
||||
},
|
||||
{
|
||||
"time": "18:19:12",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, but I mean, like, reloading the page is kind of, like, a risky thing, yeah, it can be disruptive, and… The question is, like, how frequently it would be."
|
||||
},
|
||||
{
|
||||
"time": "18:19:22",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "18:19:23",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, and probably we would also have, like, the question is, like, how much confidence that they are actually, like, experiencing the problem. Just not to do the the, like, the reload. When there's no… not an issue for that."
|
||||
},
|
||||
{
|
||||
"time": "18:19:57",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay, and the next one is the network. Network process crash. Uh, it's a bit trickier. I… I didn't finish going through it. Actually… But, uh… So general state of it, it's kind of reproduced on the integration test harness. And the fix… Seems… to fix it. So, again, it's kinda… not… non-proved concepts and kind of speculative fixes. And we are hoping to… So first of all, those should be feature flagged, just in case anything goes wrong with it. You can private selectors or whatever are disturbing. The overall extension flow, so we could disable it remotely, and uh… Yeah, so again, I'm… Oh… Not 100% sure on those, but how it is reproduced in the test harness and by the automation. It seems we could use those fixes. Another one pending, it's not opened yet, is the base URL thing. And, uh… And the speculative steps to reproduce is, uh, if we reload the, um… if we update the web extension. it changes the base URL. Because we don't have this table base irrelevant. Those… It was flagged in the early research phase. Uh, what I'm not sure with it, uh, does it harm any… Can it bring any privacy or security concerns with it if we…"
|
||||
},
|
||||
{
|
||||
"time": "18:22:09",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "But which base? I, I don't, I don't get it, like, fully, like, with me."
|
||||
},
|
||||
{
|
||||
"time": "18:22:13",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "The extension was 0. So it's UUID that's generated for the extension every time it's launched. And when it changes, it brings some… Disturbance into the web extension."
|
||||
},
|
||||
{
|
||||
"time": "18:22:28",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay."
|
||||
},
|
||||
{
|
||||
"time": "18:22:29",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "And if we set it fixed as a fixed UID. For our web extension, it generally follows the WebKit rules as I understand it and may fix another part of the failures."
|
||||
},
|
||||
{
|
||||
"time": "18:22:44",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Mhmm. But it's only only on update, like, when we uninstall and install again, right?"
|
||||
},
|
||||
{
|
||||
"time": "18:22:45",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "And, uh… Yeah, but I, uh… I can guess it may be some significant portion of users that receive the service related to the app updates. As, uh, as it was, uh, as it was… described and issued initially."
|
||||
},
|
||||
{
|
||||
"time": "18:23:14",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay, so it's like, uh… 3… Three PRs with fixes. and potentially four."
|
||||
},
|
||||
{
|
||||
"time": "18:23:24",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mmhm. network, the P1 one, uh, base URL. One for the loading. And, uh, yeah, potentially the fifth one. So, yeah, currently there is four, uh, four fixes in… in my… On my… work."
|
||||
},
|
||||
{
|
||||
"time": "18:23:53",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "So, do you have any, like, doubts, like, that, like, some of the fixes are, like, too risky, and, like, for example, the reload one? you would be not too sure about, like, shipping that one? Because I'm just, like, thinking…"
|
||||
},
|
||||
{
|
||||
"time": "18:24:05",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Uh, Zip?"
|
||||
},
|
||||
{
|
||||
"time": "18:24:07",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "thinking about, like, probably we can have the questions from Russell or someone, like. How much more time we can spend here, like, just to, like, focus on the, like, bare minimum, because probably, like, just to, like… better calculate the effort that we want to put into it."
|
||||
},
|
||||
{
|
||||
"time": "18:24:27",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, generally, we already had this question by Russell, as I mentioned, and I tried to answer it today."
|
||||
},
|
||||
{
|
||||
"time": "18:24:30",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, yeah, yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:24:37",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "No, we've seen it. Uh, so the issue here is, uh, that we cannot distribute. the failures. You cannot tell there is one main… ah, yeah, there is another. Another one… And… Great deeds. Yeah, another genuine one that is kind of proved is window git close. So the original. Window and tab merging management, uh, fix it, uh… It didn't cover every… Every issue with the pin tab, and there is still one more remaining, uh, for the window closing, and, uh, yeah, should be a short one. Uh, it should cover the genuine issue of closing in tab using the web extension."
|
||||
},
|
||||
{
|
||||
"time": "18:25:31",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "But it's only McCoy, right?"
|
||||
},
|
||||
{
|
||||
"time": "18:25:32",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "I don't know. Yeah, my question. So, yeah, that is, uh, for… Four, one, two, three, one, two, three, four main groups that are targeted here, one requiring the page reload. And the P3 that, uh, without… Context without view, it may be the pin tab. And we have one iOS of 0.03%. macOS at around 6%, but it may be wrong. And we have the other group that cannot be considered at the moment. Maybe it gets fixed with the four fixes, or maybe we receive some more data. So I try to express this point in the conversation task. But if the hypothesis are correct, we should cover most of the cases."
|
||||
},
|
||||
{
|
||||
"time": "18:26:37",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "So, do you estimate to get them done this week?"
|
||||
},
|
||||
{
|
||||
"time": "18:26:37",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "So, yeah. Yeah, so the point here is to timebox it to…"
|
||||
},
|
||||
{
|
||||
"time": "18:26:45",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "To merge it this week, and so we can, like, get it internally next week, right?"
|
||||
},
|
||||
{
|
||||
"time": "18:26:45",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Two currents. Yeah. Yeah, so if we… if we get it to the release… I mean, the data analysis, the data attribution extension, and those fixes, if we get it to internal. Today and tomorrow. Uh, we can reason about it on… Next week."
|
||||
},
|
||||
{
|
||||
"time": "18:27:11",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay, so you would mean to merge it to… Release branches."
|
||||
},
|
||||
{
|
||||
"time": "18:27:17",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yes, if it's possible."
|
||||
},
|
||||
{
|
||||
"time": "18:27:22",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "So, the two first PRs, like, one for the telemetry for the pixels, and the second with the P1 and P2, right?"
|
||||
},
|
||||
{
|
||||
"time": "18:27:31",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Um… It depends, I guess, if we can do it, if it's possible, I would give a go for all of them. Again, behind the feature flags."
|
||||
},
|
||||
{
|
||||
"time": "18:27:43",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, let's try. So, like, I'm… I'm… I'm… I'm done, like… reading and commenting for the first PRs, there are a couple of, like. leftovers for the dead code, so please check the comments. I'll try to, like, try forcing to reproduce it."
|
||||
},
|
||||
{
|
||||
"time": "18:27:55",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mmhm."
|
||||
},
|
||||
{
|
||||
"time": "18:28:01",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "So so I get it and then I can move to the next PR. I can focus today on that. So we have the the the chart."
|
||||
},
|
||||
{
|
||||
"time": "18:28:08",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay, good. And when we have those reviewed, we can open the exception and try to push it to the internal."
|
||||
},
|
||||
{
|
||||
"time": "18:28:18",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "I mean, like, if it's, like, Monday, Tuesday, you can do it probably, like, for free."
|
||||
},
|
||||
{
|
||||
"time": "18:28:24",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mm-hmm, okay."
|
||||
},
|
||||
{
|
||||
"time": "18:28:24",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "If it's later than tomorrow. Yeah. Okay. Okay, so let's try to do that."
|
||||
},
|
||||
{
|
||||
"time": "18:28:30",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay, I'll… I'll keep you pinged, yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:28:31",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "And… Please ping me when you have the following one, because I want to, like…"
|
||||
},
|
||||
{
|
||||
"time": "18:28:37",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "18:28:38",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Schedule the time for them, uh, like, in between my, my work, just to, just to not, like… Delay you. Uh, yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:28:47",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, I guess it's… I guess it may take some time, maybe the rest of your day today, and those two PRs. Could feel it."
|
||||
},
|
||||
{
|
||||
"time": "18:28:58",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, so I'll focus on that, not to block you, so let's push for the first two ones, and yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:29:04",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mmhm."
|
||||
},
|
||||
{
|
||||
"time": "18:29:04",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "And the others, like, later in the week."
|
||||
},
|
||||
{
|
||||
"time": "18:29:07",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "18:29:08",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, I agree."
|
||||
},
|
||||
{
|
||||
"time": "18:29:09",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "So, and yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:29:10",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Just to try to get them out as soon as possible to get some results."
|
||||
},
|
||||
{
|
||||
"time": "18:29:16",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "And yes, since it's highly speculative, I would give it another mid-mortem. So yeah, time box it to this week. I'd say to the first half of this week. Because there is not much work really to be done about it. Just, uh… Just so you know, I have, like, a huge testing harness work tree, and I'm trying to split the parts from it that reproduce one another issue and make it into…"
|
||||
},
|
||||
{
|
||||
"time": "18:29:48",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "No doubt."
|
||||
},
|
||||
{
|
||||
"time": "18:29:53",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "into digestible pull requests. But generally, most of them are kind of reproduced in the lab. But we have no any proofs that they actually match the production issues because they are based on the event sequence that we get."
|
||||
},
|
||||
{
|
||||
"time": "18:30:08",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:30:14",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "We got to produce the event sequence that we are receiving, but we still cannot reason about the real issues leading to those. So, yeah, that's the state. All right, thank you. I won't take more of your time."
|
||||
},
|
||||
{
|
||||
"time": "18:30:31",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "So, after this week, you would put the, like, you would have the mid-mortem this week, or, like, next week after the…"
|
||||
},
|
||||
{
|
||||
"time": "18:30:41",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Next week, so let's try to get it out and have some data. The meeting is on Tuesday, right? So we could have the data analyzed and, uh, have a mid-mortem. and decide on the next steps whether we need. Keep on going, or we are satisfied with those, or we just give up and…"
|
||||
},
|
||||
{
|
||||
"time": "18:31:06",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah. But do you think, like, on Tuesday, you will have, like, any meaningful data? It will be, like, just out for two days. Right?"
|
||||
},
|
||||
{
|
||||
"time": "18:31:13",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Uh, yes, we should, uh, since we… we received most of the current data by Tuesday. And it didn't change significantly throughout the week. I think there is a lot of issues are reported."
|
||||
},
|
||||
{
|
||||
"time": "18:31:36",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay."
|
||||
},
|
||||
{
|
||||
"time": "18:31:37",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "And there's more than enough data to analyze. So, yeah, Tuesday should be should be fine to have a big more time. I'll probably update the comments. Highlighting this."
|
||||
},
|
||||
{
|
||||
"time": "18:31:51",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay, sounds good. Okay, so I'm back to reviewing it, and, like, let's… Probably tomorrow you can, like, will you be on the OE weekly?"
|
||||
},
|
||||
{
|
||||
"time": "18:32:05",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yes, tomorrow, tomorrow, tomorrow, tomorrow is Tuesday, yes, I think so."
|
||||
},
|
||||
{
|
||||
"time": "18:32:11",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, so we can recap the plan and see. So this is, like, your top priority, right? You're focusing on…"
|
||||
},
|
||||
{
|
||||
"time": "18:32:20",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, yeah. So, I mean, there is, uh, there is enough work for me outside of the top priority. Like where you are and pushing other stuff forward. But, yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:32:39",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Makes sense. Cool. Are you blocked by anything, or just, like, this is, like… The general, like, work is enough for you."
|
||||
},
|
||||
{
|
||||
"time": "18:32:49",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Alright. Blocked with the data missing. And, uh, so… Only the pull requests are on the plate. Bottle making it. And, uh, yeah, the gaps between the releases, so we… keep perceiving it and. Analyzing how it goes."
|
||||
},
|
||||
{
|
||||
"time": "18:33:11",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Have you assigned me to all of the PRs? Because, uh, I see them…"
|
||||
},
|
||||
{
|
||||
"time": "18:33:15",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Not yet, I guess. Let me assign the network process. I didn't go through it myself yet, but yeah, I've assigned it to you."
|
||||
},
|
||||
{
|
||||
"time": "18:33:29",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Yeah, I think, like, something is broken with the…"
|
||||
},
|
||||
{
|
||||
"time": "18:33:33",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, yeah, I'll… I'm on it."
|
||||
},
|
||||
{
|
||||
"time": "18:33:36",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "No, no, like, I mean, like, uh, I'm browsing through the, the, this PR, these are the PRs, and, like, I'm filtering by the assigned to me. And I only picked it up."
|
||||
},
|
||||
{
|
||||
"time": "18:33:47",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Ah, assignees. I need to assign them. We generally don't assign the PRs, just set a reviewer."
|
||||
},
|
||||
{
|
||||
"time": "18:33:54",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "I don't know, like, you have the filter, like, review requested."
|
||||
},
|
||||
{
|
||||
"time": "18:34:00",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "18:34:01",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "They can…"
|
||||
},
|
||||
{
|
||||
"time": "18:34:01",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, let me just send. Yes, I need. and requests. Yeah, so there is three pull requests."
|
||||
},
|
||||
{
|
||||
"time": "18:34:07",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Can you… can you see? So those are, like, open PRs from you all, but you have the filter for review, and it's, like, awaiting review from…"
|
||||
},
|
||||
{
|
||||
"time": "18:34:14",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yep."
|
||||
},
|
||||
{
|
||||
"time": "18:34:18",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Me? I only get two of them."
|
||||
},
|
||||
{
|
||||
"time": "18:34:24",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay. 7, 4, 5, 5, 7."
|
||||
},
|
||||
{
|
||||
"time": "18:34:26",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Which is weird."
|
||||
},
|
||||
{
|
||||
"time": "18:34:29",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Oh, 7376 is missing for some reason. Probably you gave a review for it already. And it's waiting for…"
|
||||
},
|
||||
{
|
||||
"time": "18:34:38",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay."
|
||||
},
|
||||
{
|
||||
"time": "18:34:40",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "For the resolutions. Angus."
|
||||
},
|
||||
{
|
||||
"time": "18:34:43",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay, so maybe it's like, yeah."
|
||||
},
|
||||
{
|
||||
"time": "18:34:46",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, so currently two more in stock."
|
||||
},
|
||||
{
|
||||
"time": "18:34:50",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay. So it's it's in the stack, so I can get them from from the list. Right?"
|
||||
},
|
||||
{
|
||||
"time": "18:34:55",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yep."
|
||||
},
|
||||
{
|
||||
"time": "18:34:56",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay, cool. Can I help you in any other way?"
|
||||
},
|
||||
{
|
||||
"time": "18:34:59",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Review stuck. Yes, stuck, stuck, stuck. Create stuck. Create stuck. And now those are in the stacks. Okay, good."
|
||||
},
|
||||
{
|
||||
"time": "18:35:15",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Do you need any other help?"
|
||||
},
|
||||
{
|
||||
"time": "18:35:18",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Not at the moment. I'm going to update the first one, telemetry one. And give you a ping, and uh… And when I complete the third one, I'll ping you as well, and probably… Probably the window did close, should be an easy one for today. As well. If it sounds good."
|
||||
},
|
||||
{
|
||||
"time": "18:35:46",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Okay. Okay, so I'm on the PRs. Please check the comments for the first one. I'm all moving for the second one."
|
||||
},
|
||||
{
|
||||
"time": "18:35:58",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Sure. Okay, thank you."
|
||||
},
|
||||
{
|
||||
"time": "18:36:03",
|
||||
"speaker": "Michal Smaga",
|
||||
"text": "Thank you."
|
||||
}
|
||||
]
|
||||
}
|
||||
-130
@@ -15,133 +15,3 @@ source: "https://us01mynotes.zoom.us/QvxllpCuTTSLGEZp-R6jQw"
|
||||
- **18:10:01 · Michal Smaga:** Good.
|
||||
- **18:10:01 · Alex Martemyanov:** I'm pretty good. Jumping between windows. Yes.
|
||||
- **18:10:09 · Michal Smaga:** Uh, I think I'm, I'm like… done reviewing the first one about the pixel. I had the issue that I wasn't able to reproduce it, like, I was trying to kill the WebKit process.
|
||||
- **18:10:22 · Alex Martemyanov:** Mm-hmm.
|
||||
- **18:10:23 · Michal Smaga:** Do you have any, like, extra steps?
|
||||
- **18:10:27 · Alex Martemyanov:** Uh, so generally it fails from the second try on this exact test page that is attached there.
|
||||
- **18:10:37 · Michal Smaga:** So after, after I, I killed the, the, the…
|
||||
- **18:10:37 · Alex Martemyanov:** Okay.
|
||||
- **18:10:41 · Michal Smaga:** Web extension, web process. I should reload the page?
|
||||
- **18:10:47 · Alex Martemyanov:** Yes, in general.
|
||||
- **18:10:49 · Michal Smaga:** Do I need to do it, like, quickly, or do I need to, like…
|
||||
- **18:10:53 · Alex Martemyanov:** Um…
|
||||
- **18:10:53 · Michal Smaga:** Wait a bit.
|
||||
- **18:10:55 · Alex Martemyanov:** Usually… yeah. I don't know, within one second, just kill the process, then reload the page.
|
||||
- **18:11:02 · Michal Smaga:** Yeah.
|
||||
- **18:11:03 · Alex Martemyanov:** If it doesn't work from the first try, you just give it and reload again, and usually from second attempt, it does, uh… Uh, hang the… the extension. So it's not… it's not the genuine issue, so it's the…
|
||||
- **18:11:20 · Michal Smaga:** Yeah, artificial.
|
||||
- **18:11:22 · Alex Martemyanov:** artificial reproducing step that we didn't enable with the feature flag of the fix that went before, but it should be still here, and we… and allow to… To produce it. Uh, that's… So generally, yeah, I think you've seen the comment I posted to… to the… Project communication task. And the data, the data analysis.
|
||||
- **18:11:52 · Michal Smaga:** Yeah, yeah, yeah.
|
||||
- **18:11:52 · Alex Martemyanov:** So… so generally there is, uh… yeah, it's kind of heavy codecs and cloud work, and, um… I cannot… Oh. I cannot tell that I understand, like, 100% what is happening beneath, uh, under the hood, and… Um… Generally, we have reproduced most of the… of the stall issues, uh, with some… Thank you. my display on black. Wow. I just need to switch off something, I guess.
|
||||
- **18:12:35 · Michal Smaga:** I can hear you, I cannot see you.
|
||||
- **18:12:36 · Alex Martemyanov:** Hello? Yeah, I cannot see you, because… Give it a minute. Yeah. No. Fuck. And… Good morning, Mark. Sorry. One moment, Amy. I need to burn off something.
|
||||
- **18:13:10 · Michal Smaga:** Did your laptop display died?
|
||||
- **18:13:13 · Alex Martemyanov:** Not yet, I guess. I hope. Uh, here… Here we are. Uh-huh. So, we do. Yeah. All right, I'm back. And… Oh, yeah, I just got some. Testing. Fairness around here. Uh, where was I? Yeah, the issues. Uh, so generally, there's four issues in the work, and uh… One is behind the disabled feature flag. Because it reloads the page, and I don't think it's optimal. And probably a couple of more go next, and we'll leave. the smallest groups for the next iteration, I guess. So here we have to, uh… To expand the diagnostics. So generally, to fulfill the privacy triage, uh, I was requested to… To reduce what we… actually submit, and the decision was to merge the events into a single event. It should not generally harm our, uh… our data. We can lose something in case the browser crashes, or if it's reloaded. But I guess it's acceptable at this point, since we get these isolated groups already. And we just need some proofs. for the remaining and the pixels. Prior to this.
|
||||
- **18:15:02 · Michal Smaga:** Yes. So, so the first…
|
||||
- **18:15:04 · Alex Martemyanov:** Pixel fire for the pixel, yeah.
|
||||
- **18:15:06 · Michal Smaga:** First PR is the pixels, yeah? So the one from the PR.
|
||||
- **18:15:09 · Alex Martemyanov:** Yes, so the suggestion is to improve the diagnostics first, and then the stacked ones go onto it.
|
||||
- **18:15:18 · Michal Smaga:** Yeah, and what is the status of the other, like, PRs, the follow-up ones, with the fixes?
|
||||
- **18:15:24 · Alex Martemyanov:** Uh, so we have the… the recovery. And… First one is InitLoss. And InitLoss includes P1 and P2 as inputs. As I remember. Yeah, and P4, that's not enabled at the moment. It's, uh, 7379. It should be… Should be generated already. For review. And another one is 7459. It's also open. And… Well, generally, should also be pretty much ready, so the… There is integration tests, integration test harness that's supposed to only be run once to reproduce the issue.
|
||||
- **18:16:38 · Michal Smaga:** Mm-hmm.
|
||||
- **18:16:39 · Alex Martemyanov:** In, like, lab condition.
|
||||
- **18:16:40 · Michal Smaga:** Can you say. Which one was the last PR?
|
||||
- **18:16:45 · Alex Martemyanov:** The last one, uh, 7459. This one.
|
||||
- **18:17:00 · Michal Smaga:** Yeah, yeah, yeah, I got it, yeah, the network one, yeah.
|
||||
- **18:17:11 · Alex Martemyanov:** So the first, that is 7379, it should… So basically, we guess that it may be not an issue. And it's maybe an issue of slow. Slow loading and the fix itself is triggering the background will be load with the navigation itself. Because, uh, the initial… initial startup, or return from background, maybe not, uh, warming up the web view. Or, um… Or our extension. And, uh… The situation with P4 is that we may need to reload the page after, you know, after the extension is loaded, so it is applied to the page. And, uh, I was planning to investigate it further. Is there a way to run the… Plug in after the page is already loaded, maybe send another page load event. And see if it… if it just works. Uh, but the reload is there. And the feature flag.
|
||||
- **18:18:36 · Michal Smaga:** And do you think, like, uh… Are we able to detect the fourth one without the feature flag? Just to get the pixels about, like, how…
|
||||
- **18:18:48 · Alex Martemyanov:** Just to get the pixels… yeah, I guess so. I guess so we can make the pixel.
|
||||
- **18:18:59 · Michal Smaga:** Yeah, because it would be get, like. It's good to get the signal, like, how many of those cases they potentially would be fixed by the future flag.
|
||||
- **18:19:11 · Alex Martemyanov:** Yeah, I agree.
|
||||
- **18:19:12 · Michal Smaga:** Yeah, but I mean, like, reloading the page is kind of, like, a risky thing, yeah, it can be disruptive, and… The question is, like, how frequently it would be.
|
||||
- **18:19:22 · Alex Martemyanov:** Mm-hmm.
|
||||
- **18:19:23 · Michal Smaga:** Yeah, and probably we would also have, like, the question is, like, how much confidence that they are actually, like, experiencing the problem. Just not to do the the, like, the reload. When there's no… not an issue for that.
|
||||
- **18:19:57 · Alex Martemyanov:** Okay, and the next one is the network. Network process crash. Uh, it's a bit trickier. I… I didn't finish going through it. Actually… But, uh… So general state of it, it's kind of reproduced on the integration test harness. And the fix… Seems… to fix it. So, again, it's kinda… not… non-proved concepts and kind of speculative fixes. And we are hoping to… So first of all, those should be feature flagged, just in case anything goes wrong with it. You can private selectors or whatever are disturbing. The overall extension flow, so we could disable it remotely, and uh… Yeah, so again, I'm… Oh… Not 100% sure on those, but how it is reproduced in the test harness and by the automation. It seems we could use those fixes. Another one pending, it's not opened yet, is the base URL thing. And, uh… And the speculative steps to reproduce is, uh, if we reload the, um… if we update the web extension. it changes the base URL. Because we don't have this table base irrelevant. Those… It was flagged in the early research phase. Uh, what I'm not sure with it, uh, does it harm any… Can it bring any privacy or security concerns with it if we…
|
||||
- **18:22:09 · Michal Smaga:** But which base? I, I don't, I don't get it, like, fully, like, with me.
|
||||
- **18:22:13 · Alex Martemyanov:** The extension was 0. So it's UUID that's generated for the extension every time it's launched. And when it changes, it brings some… Disturbance into the web extension.
|
||||
- **18:22:28 · Michal Smaga:** Okay.
|
||||
- **18:22:29 · Alex Martemyanov:** And if we set it fixed as a fixed UID. For our web extension, it generally follows the WebKit rules as I understand it and may fix another part of the failures.
|
||||
- **18:22:44 · Michal Smaga:** Mhmm. But it's only only on update, like, when we uninstall and install again, right?
|
||||
- **18:22:45 · Alex Martemyanov:** And, uh… Yeah, but I, uh… I can guess it may be some significant portion of users that receive the service related to the app updates. As, uh, as it was, uh, as it was… described and issued initially.
|
||||
- **18:23:14 · Michal Smaga:** Okay, so it's like, uh… 3… Three PRs with fixes. and potentially four.
|
||||
- **18:23:24 · Alex Martemyanov:** Mmhm. network, the P1 one, uh, base URL. One for the loading. And, uh, yeah, potentially the fifth one. So, yeah, currently there is four, uh, four fixes in… in my… On my… work.
|
||||
- **18:23:53 · Michal Smaga:** So, do you have any, like, doubts, like, that, like, some of the fixes are, like, too risky, and, like, for example, the reload one? you would be not too sure about, like, shipping that one? Because I'm just, like, thinking…
|
||||
- **18:24:05 · Alex Martemyanov:** Uh, Zip?
|
||||
- **18:24:07 · Michal Smaga:** thinking about, like, probably we can have the questions from Russell or someone, like. How much more time we can spend here, like, just to, like, focus on the, like, bare minimum, because probably, like, just to, like… better calculate the effort that we want to put into it.
|
||||
- **18:24:27 · Alex Martemyanov:** Yeah, generally, we already had this question by Russell, as I mentioned, and I tried to answer it today.
|
||||
- **18:24:30 · Michal Smaga:** Yeah, yeah, yeah.
|
||||
- **18:24:37 · Alex Martemyanov:** No, we've seen it. Uh, so the issue here is, uh, that we cannot distribute. the failures. You cannot tell there is one main… ah, yeah, there is another. Another one… And… Great deeds. Yeah, another genuine one that is kind of proved is window git close. So the original. Window and tab merging management, uh, fix it, uh… It didn't cover every… Every issue with the pin tab, and there is still one more remaining, uh, for the window closing, and, uh, yeah, should be a short one. Uh, it should cover the genuine issue of closing in tab using the web extension.
|
||||
- **18:25:31 · Michal Smaga:** But it's only McCoy, right?
|
||||
- **18:25:32 · Alex Martemyanov:** I don't know. Yeah, my question. So, yeah, that is, uh, for… Four, one, two, three, one, two, three, four main groups that are targeted here, one requiring the page reload. And the P3 that, uh, without… Context without view, it may be the pin tab. And we have one iOS of 0.03%. macOS at around 6%, but it may be wrong. And we have the other group that cannot be considered at the moment. Maybe it gets fixed with the four fixes, or maybe we receive some more data. So I try to express this point in the conversation task. But if the hypothesis are correct, we should cover most of the cases.
|
||||
- **18:26:37 · Michal Smaga:** So, do you estimate to get them done this week?
|
||||
- **18:26:37 · Alex Martemyanov:** So, yeah. Yeah, so the point here is to timebox it to…
|
||||
- **18:26:45 · Michal Smaga:** To merge it this week, and so we can, like, get it internally next week, right?
|
||||
- **18:26:45 · Alex Martemyanov:** Two currents. Yeah. Yeah, so if we… if we get it to the release… I mean, the data analysis, the data attribution extension, and those fixes, if we get it to internal. Today and tomorrow. Uh, we can reason about it on… Next week.
|
||||
- **18:27:11 · Michal Smaga:** Okay, so you would mean to merge it to… Release branches.
|
||||
- **18:27:17 · Alex Martemyanov:** Yes, if it's possible.
|
||||
- **18:27:22 · Michal Smaga:** So, the two first PRs, like, one for the telemetry for the pixels, and the second with the P1 and P2, right?
|
||||
- **18:27:31 · Alex Martemyanov:** Um… It depends, I guess, if we can do it, if it's possible, I would give a go for all of them. Again, behind the feature flags.
|
||||
- **18:27:43 · Michal Smaga:** Yeah, let's try. So, like, I'm… I'm… I'm… I'm done, like… reading and commenting for the first PRs, there are a couple of, like. leftovers for the dead code, so please check the comments. I'll try to, like, try forcing to reproduce it.
|
||||
- **18:27:55 · Alex Martemyanov:** Mmhm.
|
||||
- **18:28:01 · Michal Smaga:** So so I get it and then I can move to the next PR. I can focus today on that. So we have the the the chart.
|
||||
- **18:28:08 · Alex Martemyanov:** Okay, good. And when we have those reviewed, we can open the exception and try to push it to the internal.
|
||||
- **18:28:18 · Michal Smaga:** I mean, like, if it's, like, Monday, Tuesday, you can do it probably, like, for free.
|
||||
- **18:28:24 · Alex Martemyanov:** Mm-hmm, okay.
|
||||
- **18:28:24 · Michal Smaga:** If it's later than tomorrow. Yeah. Okay. Okay, so let's try to do that.
|
||||
- **18:28:30 · Alex Martemyanov:** Okay, I'll… I'll keep you pinged, yeah.
|
||||
- **18:28:31 · Michal Smaga:** And… Please ping me when you have the following one, because I want to, like…
|
||||
- **18:28:37 · Alex Martemyanov:** Mm-hmm.
|
||||
- **18:28:38 · Michal Smaga:** Schedule the time for them, uh, like, in between my, my work, just to, just to not, like… Delay you. Uh, yeah.
|
||||
- **18:28:47 · Alex Martemyanov:** Yeah, I guess it's… I guess it may take some time, maybe the rest of your day today, and those two PRs. Could feel it.
|
||||
- **18:28:58 · Michal Smaga:** Yeah, so I'll focus on that, not to block you, so let's push for the first two ones, and yeah.
|
||||
- **18:29:04 · Alex Martemyanov:** Mmhm.
|
||||
- **18:29:04 · Michal Smaga:** And the others, like, later in the week.
|
||||
- **18:29:07 · Alex Martemyanov:** Mm-hmm.
|
||||
- **18:29:08 · Michal Smaga:** Yeah, I agree.
|
||||
- **18:29:09 · Alex Martemyanov:** So, and yeah.
|
||||
- **18:29:10 · Michal Smaga:** Just to try to get them out as soon as possible to get some results.
|
||||
- **18:29:16 · Alex Martemyanov:** And yes, since it's highly speculative, I would give it another mid-mortem. So yeah, time box it to this week. I'd say to the first half of this week. Because there is not much work really to be done about it. Just, uh… Just so you know, I have, like, a huge testing harness work tree, and I'm trying to split the parts from it that reproduce one another issue and make it into…
|
||||
- **18:29:48 · Michal Smaga:** No doubt.
|
||||
- **18:29:53 · Alex Martemyanov:** into digestible pull requests. But generally, most of them are kind of reproduced in the lab. But we have no any proofs that they actually match the production issues because they are based on the event sequence that we get.
|
||||
- **18:30:08 · Michal Smaga:** Yeah.
|
||||
- **18:30:14 · Alex Martemyanov:** We got to produce the event sequence that we are receiving, but we still cannot reason about the real issues leading to those. So, yeah, that's the state. All right, thank you. I won't take more of your time.
|
||||
- **18:30:31 · Michal Smaga:** So, after this week, you would put the, like, you would have the mid-mortem this week, or, like, next week after the…
|
||||
- **18:30:41 · Alex Martemyanov:** Next week, so let's try to get it out and have some data. The meeting is on Tuesday, right? So we could have the data analyzed and, uh, have a mid-mortem. and decide on the next steps whether we need. Keep on going, or we are satisfied with those, or we just give up and…
|
||||
- **18:31:06 · Michal Smaga:** Yeah. But do you think, like, on Tuesday, you will have, like, any meaningful data? It will be, like, just out for two days. Right?
|
||||
- **18:31:13 · Alex Martemyanov:** Uh, yes, we should, uh, since we… we received most of the current data by Tuesday. And it didn't change significantly throughout the week. I think there is a lot of issues are reported.
|
||||
- **18:31:36 · Michal Smaga:** Okay.
|
||||
- **18:31:37 · Alex Martemyanov:** And there's more than enough data to analyze. So, yeah, Tuesday should be should be fine to have a big more time. I'll probably update the comments. Highlighting this.
|
||||
- **18:31:51 · Michal Smaga:** Okay, sounds good. Okay, so I'm back to reviewing it, and, like, let's… Probably tomorrow you can, like, will you be on the OE weekly?
|
||||
- **18:32:05 · Alex Martemyanov:** Yes, tomorrow, tomorrow, tomorrow, tomorrow is Tuesday, yes, I think so.
|
||||
- **18:32:11 · Michal Smaga:** Yeah, so we can recap the plan and see. So this is, like, your top priority, right? You're focusing on…
|
||||
- **18:32:20 · Alex Martemyanov:** Yeah, yeah. So, I mean, there is, uh, there is enough work for me outside of the top priority. Like where you are and pushing other stuff forward. But, yeah.
|
||||
- **18:32:39 · Michal Smaga:** Makes sense. Cool. Are you blocked by anything, or just, like, this is, like… The general, like, work is enough for you.
|
||||
- **18:32:49 · Alex Martemyanov:** Alright. Blocked with the data missing. And, uh, so… Only the pull requests are on the plate. Bottle making it. And, uh, yeah, the gaps between the releases, so we… keep perceiving it and. Analyzing how it goes.
|
||||
- **18:33:11 · Michal Smaga:** Have you assigned me to all of the PRs? Because, uh, I see them…
|
||||
- **18:33:15 · Alex Martemyanov:** Not yet, I guess. Let me assign the network process. I didn't go through it myself yet, but yeah, I've assigned it to you.
|
||||
- **18:33:29 · Michal Smaga:** Yeah, I think, like, something is broken with the…
|
||||
- **18:33:33 · Alex Martemyanov:** Yeah, yeah, I'll… I'm on it.
|
||||
- **18:33:36 · Michal Smaga:** No, no, like, I mean, like, uh, I'm browsing through the, the, this PR, these are the PRs, and, like, I'm filtering by the assigned to me. And I only picked it up.
|
||||
- **18:33:47 · Alex Martemyanov:** Ah, assignees. I need to assign them. We generally don't assign the PRs, just set a reviewer.
|
||||
- **18:33:54 · Michal Smaga:** I don't know, like, you have the filter, like, review requested.
|
||||
- **18:34:00 · Alex Martemyanov:** Mm-hmm.
|
||||
- **18:34:01 · Michal Smaga:** They can…
|
||||
- **18:34:01 · Alex Martemyanov:** Yeah, let me just send. Yes, I need. and requests. Yeah, so there is three pull requests.
|
||||
- **18:34:07 · Michal Smaga:** Can you… can you see? So those are, like, open PRs from you all, but you have the filter for review, and it's, like, awaiting review from…
|
||||
- **18:34:14 · Alex Martemyanov:** Yep.
|
||||
- **18:34:18 · Michal Smaga:** Me? I only get two of them.
|
||||
- **18:34:24 · Alex Martemyanov:** Okay. 7, 4, 5, 5, 7.
|
||||
- **18:34:26 · Michal Smaga:** Which is weird.
|
||||
- **18:34:29 · Alex Martemyanov:** Oh, 7376 is missing for some reason. Probably you gave a review for it already. And it's waiting for…
|
||||
- **18:34:38 · Michal Smaga:** Okay.
|
||||
- **18:34:40 · Alex Martemyanov:** For the resolutions. Angus.
|
||||
- **18:34:43 · Michal Smaga:** Okay, so maybe it's like, yeah.
|
||||
- **18:34:46 · Alex Martemyanov:** Yeah, so currently two more in stock.
|
||||
- **18:34:50 · Michal Smaga:** Okay. So it's it's in the stack, so I can get them from from the list. Right?
|
||||
- **18:34:55 · Alex Martemyanov:** Yep.
|
||||
- **18:34:56 · Michal Smaga:** Okay, cool. Can I help you in any other way?
|
||||
- **18:34:59 · Alex Martemyanov:** Review stuck. Yes, stuck, stuck, stuck. Create stuck. Create stuck. And now those are in the stacks. Okay, good.
|
||||
- **18:35:15 · Michal Smaga:** Do you need any other help?
|
||||
- **18:35:18 · Alex Martemyanov:** Not at the moment. I'm going to update the first one, telemetry one. And give you a ping, and uh… And when I complete the third one, I'll ping you as well, and probably… Probably the window did close, should be an easy one for today. As well. If it sounds good.
|
||||
- **18:35:46 · Michal Smaga:** Okay. Okay, so I'm on the PRs. Please check the comments for the first one. I'm all moving for the second one.
|
||||
- **18:35:58 · Alex Martemyanov:** Sure. Okay, thank you.
|
||||
- **18:36:03 · Michal Smaga:** Thank you.
|
||||
+1595
File diff suppressed because it is too large.
Load diff
+319
@@ -15,3 +15,322 @@ source: "https://us01mynotes.zoom.us/Mg62hl1GSI2gw4XeGvHAsg"
|
||||
- **15:04:34 · Dominik Kapusta:** How are you?
|
||||
- **15:04:35 · Alex Martemyanov:** I don't know. Pretty, pretty fine, I guess. Mmhm. Still a lot, a lot of things. I'm going through my head.
|
||||
- **15:04:50 · Dominik Kapusta:** Hmm.
|
||||
- **15:04:51 · Alex Martemyanov:** And… That gives me some… Darn this. Um, but…
|
||||
- **15:04:58 · Dominik Kapusta:** What is going on?
|
||||
- **15:05:00 · Alex Martemyanov:** Yeah, overall… overall, I think it's… It's going pretty fine. There is some… Operational… issues, um, that I'm trying to get resolved. But otherwise… We should be pretty fine. So yeah, the top.
|
||||
- **15:05:22 · Dominik Kapusta:** um… Is this related to… Sorry. Yeah, I mean, go on. We'll get to that.
|
||||
- **15:05:24 · Alex Martemyanov:** The top priority. Yeah, so the top priority thing, uh… Basically… basically, I'm getting pinged by, uh, Russell. Like… How long the project is gonna take anymore.
|
||||
- **15:05:45 · Dominik Kapusta:** Yeah, I saw that.
|
||||
- **15:05:46 · Alex Martemyanov:** I'm trying to give some reasoning behind it. So basically. We have two-week spans for testing the data and releasing the fixes, and you have eight theories to… to work on, and basically nobody.
|
||||
- **15:06:03 · Dominik Kapusta:** Mm-hmm.
|
||||
- **15:06:07 · Alex Martemyanov:** have an idea on what actually is happening under the hood. So… I guess it should be fine. I'm trying to get the project updated and timebox the current.
|
||||
- **15:06:19 · Dominik Kapusta:** Mm-hmm.
|
||||
- **15:06:22 · Alex Martemyanov:** Fixes for this week, and uh… Try to get them try to merge it to the release today. So we have the data and… Fixes. the next… What are these? So, to the next… for the next OE meeting, we'll have… data to analyze and to run another mid-mortem to decide on the project life.
|
||||
- **15:06:49 · Dominik Kapusta:** What day is the OE meeting on?
|
||||
- **15:06:52 · Alex Martemyanov:** Tuesday, late.
|
||||
- **15:06:53 · Dominik Kapusta:** Tuesday, okay. Okay, okay.
|
||||
- **15:06:56 · Alex Martemyanov:** Uh, so yeah, today, uh, is gonna be… Another call. I'm gonna talk about it again. And I guess we should be fine. There is still a lot of unknowns, and I'm trying to fix it in the last minute, just… Just talking to Michal at the moment about the… Fixes, because… the telemetry update for the request is kinda approved as of yesterday, but today I started to reason about it again, and found some issues that we may have with it, that may be polluting our data, and we may need to…
|
||||
- **15:07:32 · Dominik Kapusta:** Oh.
|
||||
- **15:07:39 · Alex Martemyanov:** Tune it a little bit more. Uh, so it's… Could be more accurate, especially related to iOS background loading. Because it's handled another way than on macOS, and I just haven't talked about it. Uh, so… Otherwise, we have four, I guess. One is merged. Do this up. Three fixes going today, and probably one or two more. Going later. So, getting to the next release.
|
||||
- **15:08:16 · Dominik Kapusta:** Mm-hmm.
|
||||
- **15:08:19 · Alex Martemyanov:** Oh… It's kind of heavy from the… Mental perspective. Because, uh… Thinking of it from, uh… like, 2 years ago, without all this AI stuff. the project would really take at least half a year, or maybe even more, of such a scale, and it's comparable to the navigation refactoring, or so, just to dig inside it. And of course, I cannot.
|
||||
- **15:08:42 · Dominik Kapusta:** Thank you. Yeah. Okay. Mm-hmm. Yeah, yeah.
|
||||
- **15:08:53 · Alex Martemyanov:** Digest everything in the web extension stack and everything that's getting fixed and tested and everything.
|
||||
- **15:08:58 · Dominik Kapusta:** Sure.
|
||||
- **15:09:01 · Alex Martemyanov:** But I have to go through the pull requests, switch the chats, and uh…
|
||||
- **15:09:06 · Dominik Kapusta:** No.
|
||||
- **15:09:06 · Alex Martemyanov:** Get it through my head, which is kind of exhausting.
|
||||
- **15:09:12 · Dominik Kapusta:** Yeah, yeah, totally.
|
||||
- **15:09:12 · Alex Martemyanov:** And, uh… In the background, I'm also going through the AUR stuff. Which is some tests. As you've seen.
|
||||
- **15:09:26 · Dominik Kapusta:** Mm-hmm. Oh, yes, I have… I have some, uh, code reviews. I owe you some code reviews, I guess? No, not anymore. Okay. Ah, yeah, I… yeah, yeah, yeah, that was one that I asked you to… to assign to someone through my OS, yeah.
|
||||
- **15:09:26 · Alex Martemyanov:** These are some tasks. I… no, you don't. I actually… Yeah, there's one that I already sent from you, and another one was just, uh… Uh… so you were just… In the copy of it.
|
||||
- **15:09:50 · Dominik Kapusta:** Mmhm.
|
||||
- **15:09:51 · Alex Martemyanov:** And I applied the self-review. Uh, process, because the change is only included in the test.
|
||||
- **15:09:55 · Dominik Kapusta:** True. Yes, yes, sounds good.
|
||||
- **15:09:58 · Alex Martemyanov:** Ah, there is still a deck of pull requests still up. Sure. How many? In 12 years. Yeah, happening in parallel. I also… I also try to keep the wheels rolling on the unit test thing, because if it gets outdated, it would require to start the whole thing from scratch.
|
||||
- **15:10:34 · Dominik Kapusta:** Yeah, yeah, right.
|
||||
- **15:10:37 · Alex Martemyanov:** Okay. Okay. Probably later today or tomorrow. And looking forward for the holidays. And this was kind of another topic to discuss later today.
|
||||
- **15:10:51 · Dominik Kapusta:** Alright, what's… What's on your plate for the Hug Days?
|
||||
- **15:11:01 · Alex Martemyanov:** Yeah, from the good side of all this work, I kind of cleaned up my backlog, almost. There is still fire window animation, and uh… And, uh… And I'm failing Excel reports. And feature flags, basically. All the other stuff is currently inactive, and uh… pull requests are… open or about to get open. Uh, so… it should simplify my life a lot.
|
||||
- **15:11:37 · Dominik Kapusta:** Nice.
|
||||
- **15:11:37 · Alex Martemyanov:** I hope. From the hack days, from the hack days, I basically run AI. Yesterday's night, I just… Thank you.
|
||||
- **15:11:48 · Dominik Kapusta:** Mmhm.
|
||||
- **15:11:49 · Alex Martemyanov:** Get another medical phase, I guess. Burst on the ideas and evaluate it around 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11.
|
||||
- **15:11:53 · Dominik Kapusta:** No.
|
||||
- **15:12:05 · Alex Martemyanov:** Um… 11. It is. So… I'm thinking how to get it not wasted because some of them may be viable and some of them may need. Some. ship reviews or iteration with the design team, and I am just wondering… I think the macOS browser kinda… active development on Pose. I mean, not bug fixing, but adding new features. Mm-hmm. But still we have this 3D delight highlighted by Gabriel and.
|
||||
- **15:12:47 · Dominik Kapusta:** Yeah. Oh. Yep. But the macOS development… macOS development is not on pause.
|
||||
- **15:12:52 · Alex Martemyanov:** I see that I'm right. Alright. It's, uh, deprioritized, or… how's it called? So, there is… Yeah, there is, there is, there is.
|
||||
- **15:13:12 · Dominik Kapusta:** I don't think I understand that. What do you mean by… But development is on hold.
|
||||
- **15:13:19 · Alex Martemyanov:** I mean, is it, uh, real to get, uh… Some new features for macOS browser released. Or is it just this demo stuff and that's it?
|
||||
- **15:13:31 · Dominik Kapusta:** Mmm… I… I'd like to say, I don't think it's necessarily true, but, um… Well, it depends on the feature, probably, that's demoed. Um… There are some… well, there is a backlog of. macOS… potential macOS projects. if you… if you go to… well, so, this is part of our rubric, but within this our rubric, I'm also making this… Digests. of macOS-only projects, and the latest one, which is probably from… September is… Here. And… So the list of projects in this task is taken from our rubric and they are… ordered by the score in the rubric. So, from the top… and there are… yeah, like, macOS Native, the projects in this list don't depend on each other or on design projects. Unless specified otherwise. And from the top. You have password manager extensions, which is a big deal, of course. The next one is import history from third-party browsers. This is being picked up, this is being worked on by Andre. The next one is force websites to use dark mode. We will actually be removing this… current experience, which is internal, and replacing it with the Dark Reader extension, a proper, regular Dark Reader extension that works just fine. In our browser right now. And then we… and then the actual features start. Which is tab groups. And the prerequisite to tab groups is multi-select on tabs. Selecting and dragging multiple tabs at once. And this is… I think it's very hard to do well, because there will be plenty of… Uh, quirks related with… to the… look and feel of that field, essentially. The interaction…
|
||||
- **15:16:01 · Alex Martemyanov:** Metal… What do you think about me stealing some of those, like, tab groups and multi-select to my Hug Days project? And, uh… Trying to hook it and basically it gets impacted. They all have objective in such way to get to continue basically the development as an extra priority.
|
||||
- **15:16:17 · Dominik Kapusta:** Thank you. Yeah. Yeah. Okay. Yeah, yeah. Uh…
|
||||
- **15:16:23 · Alex Martemyanov:** I mean, just an idea.
|
||||
- **15:16:26 · Dominik Kapusta:** I can't say it will work. But… You could never… you could still just… Just give it a try because it counts, like whatever you do. For Hug Days, that's… I mean, for Hug Days, you can bring your own ideas, but you can as well just accelerate existing roadmaps, and this is exactly it. I, for instance, once I teamed up with Shane, and we did the… NewTapPage prototype? Something like that. And then we turned it into a proper NewTapPage, uh… HTML NewTapPage project.
|
||||
- **15:17:04 · Alex Martemyanov:** Mm-hmm.
|
||||
- **15:17:05 · Dominik Kapusta:** So… so you could… if you feel like working on… selecting and dragging multiple tabs at once, that would be great, because I think everyone is afraid of that. And if you could just… just do it, then that would be an amazing addition. And I think this is also something that we could ship independently. We don't need tab groups to ship this thing. This is why it's extracted as a separate project.
|
||||
- **15:17:35 · Alex Martemyanov:** Mmhm. Well, okay, then it sounds like an idea. Oh… Nice. Nice. And, uh, so virtually… Actually, the list of the experiments I've had. I may try to demo something. Uh, so… So, basically, let me share my screen, I guess. Craft recording, system settings. Sure. Okay, can you see it?
|
||||
- **15:18:18 · Dominik Kapusta:** Yes.
|
||||
- **15:18:19 · Alex Martemyanov:** Yeah, so, yeah, first of all, it's running VS Code.
|
||||
- **15:18:23 · Dominik Kapusta:** Of course.
|
||||
- **15:18:24 · Alex Martemyanov:** Yeah, and trying not to open Xcode. I just demoed Xcode to my wife yesterday evening, trying to describe what am I doing and why, showing all these glitches and tabs blinking.
|
||||
- **15:18:37 · Dominik Kapusta:** And… the…
|
||||
- **15:18:40 · Alex Martemyanov:** Like the best ID by Apple.
|
||||
- **15:18:43 · Dominik Kapusta:** Mmhm.
|
||||
- **15:18:44 · Alex Martemyanov:** She was very laughing about it. Like, yeah, Apple's really make makes an amazing stuff.
|
||||
- **15:18:51 · Dominik Kapusta:** No.
|
||||
- **15:18:52 · Alex Martemyanov:** And, uh, yeah, me complaining that nobody really understands it. And still prefers to use Xcode. But yeah, anyways, it's working, debugging. Yeah, I can jump to the symbols here. And something I'm going to demo in today's Apple. Apple Weekly. Uh, on the… in the post-mortem, showing the actual results and, uh, sharing the… In the repo, this can be used. So, basically, it uses, uh, Git hooks to install this extension to every, uh, every checkout I make locally.
|
||||
- **15:19:23 · Dominik Kapusta:** Mm-hmm.
|
||||
- **15:19:32 · Alex Martemyanov:** And it just works. Uh, I also made a helper or work trees for, uh, this, uh.
|
||||
- **15:19:36 · Dominik Kapusta:** Okay.
|
||||
- **15:19:41 · Alex Martemyanov:** How is it called? Raycast.
|
||||
- **15:19:42 · Dominik Kapusta:** Nice. Yeah. Yeah, I like that. Mm-hmm.
|
||||
- **15:19:44 · Alex Martemyanov:** Yes, so we can search any, like, fire, something, it filters the active work trees, showing the state, and I can directly open it with VS Code, or Explode, or Terminal, or even delete ones.
|
||||
- **15:19:51 · Dominik Kapusta:** Hmm. Nice. Yeah, yeah. Haha, cool.
|
||||
- **15:19:58 · Alex Martemyanov:** Oh. So this build succeeded. I guess it's launching. Is it launching? Very much.
|
||||
- **15:20:13 · Dominik Kapusta:** I don't know.
|
||||
- **15:20:14 · Alex Martemyanov:** I guess it's not launching, just building. And yeah, so this still issue of resolving packages. Basically, the benefits we would get if… Migrated to SPM, getting rid of this stage that eats like ten seconds. But otherwise, it's working. And we… what we have else for this while it's loading. No one's listening. That's fine, I guess. Yeah, it's launching. Here… here we are.
|
||||
- **15:21:07 · Dominik Kapusta:** Mm-hmm.
|
||||
- **15:21:08 · Alex Martemyanov:** Yeah, something that I was doing for this project is the burn animation here.
|
||||
- **15:21:08 · Dominik Kapusta:** Nice.
|
||||
- **15:21:16 · Alex Martemyanov:** So it's like burning the window. Uh, completely not… not going through it, but when the fire animation goes and, uh, just…
|
||||
- **15:21:25 · Dominik Kapusta:** Ah, nice. You know.
|
||||
- **15:21:28 · Alex Martemyanov:** clears it behind.
|
||||
- **15:21:30 · Dominik Kapusta:** Oh man, that's so great!
|
||||
- **15:21:32 · Alex Martemyanov:** And there is one more thing.
|
||||
- **15:21:35 · Dominik Kapusta:** It's… just one thing, it's not looking… it's not looking super sharp while you're sharing the screen, so maybe worth recording an animation and just sharing. somewhere.
|
||||
- **15:21:47 · Alex Martemyanov:** Yeah, maybe there is actually a choice of animation and we can do this.
|
||||
- **15:21:53 · Dominik Kapusta:** Awesome.
|
||||
- **15:21:54 · Alex Martemyanov:** Or we can do what? we can do… this… Okay.
|
||||
- **15:22:05 · Dominik Kapusta:** Nice.
|
||||
- **15:22:05 · Alex Martemyanov:** I just was thinking it would be, it could be nice to bring it to… to production, generally.
|
||||
- **15:22:13 · Dominik Kapusta:** Mmhm.
|
||||
- **15:22:13 · Alex Martemyanov:** And, uh, there is another fix of the… A link preview that shows the link text on the left. Bottom corner.
|
||||
- **15:22:24 · Dominik Kapusta:** Mm-hmm.
|
||||
- **15:22:24 · Alex Martemyanov:** And if you put the cursor in the left down corner, it's overlapping. And so adding another window, I guess it should have a small quick ship review and just go to production since we have a task for it in the backlog.
|
||||
- **15:22:31 · Dominik Kapusta:** Yeah, okay.
|
||||
- **15:22:42 · Alex Martemyanov:** But the fire, maybe I should talk to Stephen, I guess, just suggesting it as an improvement and show a demo.
|
||||
- **15:22:43 · Dominik Kapusta:** Okay. Mm-hmm.
|
||||
- **15:22:54 · Alex Martemyanov:** And we may… Mayrama project, maybe… Make it a little bit sharper. Or make some extra tuning. but, yeah. Otherwise, the principle is pretty simple. We are just… instead of all this, uh… jumping across, uh… the animation layer, tabs, tab bar, and everything, it just makes a snapshot, and… deals animation on top of it, hiding window instantaneously, doing all the job behind the scenes.
|
||||
- **15:23:20 · Dominik Kapusta:** Mm-hmm, yeah, yeah. Sounds simple, now that you've said that.
|
||||
- **15:23:28 · Alex Martemyanov:** Yeah, basically everything's just one shot made by AI.
|
||||
- **15:23:29 · Dominik Kapusta:** It's just. Mmhm. Yeah, yeah.
|
||||
- **15:23:35 · Alex Martemyanov:** Another thing I made is, uh… reviving the old projects on the browser profiles and dedicated apps for websites.
|
||||
- **15:23:45 · Dominik Kapusta:** Mmhm.
|
||||
- **15:23:46 · Alex Martemyanov:** and rewriting it using the web storage, or how is it called? Basically a FHIR window, but a stored FHIR window with naming profiles. It is… it was also a… feature user were asking for for a long time, I guess.
|
||||
- **15:24:05 · Dominik Kapusta:** So what exactly? Like a separate storage?
|
||||
- **15:24:07 · Alex Martemyanov:** Uh, profiles. Profiles, separate storage, yes. And, uh, dedicated apps, actually, that Safari does.
|
||||
- **15:24:09 · Dominik Kapusta:** Profiles, okay. Yeah, yeah, yeah, yeah. Yes. Yes.
|
||||
- **15:24:18 · Alex Martemyanov:** Uh, what else was there?
|
||||
- **15:24:19 · Dominik Kapusta:** Profiles is a big deal, because profiles can be understood in various ways, and one of the ways is just separate instances of the app, really, with separate bookmarks, separate settings, and so on and so on. Umm. Yeah, okay.
|
||||
- **15:24:37 · Alex Martemyanov:** Yeah, another one was bookmarks and history search from the menus and the bookmarks bar when you start typing, like in the help menu.
|
||||
- **15:24:44 · Dominik Kapusta:** Mm-hmm. Mmhm.
|
||||
- **15:24:48 · Alex Martemyanov:** And it searches… Bookmarklets. I guess that would require privacy triage or security triage.
|
||||
- **15:24:58 · Dominik Kapusta:** Probably not. I'm not sure, because Windows supports it.
|
||||
- **15:25:03 · Alex Martemyanov:** Hmm, okay.
|
||||
- **15:25:03 · Dominik Kapusta:** I've just, I've just, I've just tested it last week, because we needed something. I don't remember why, but the topic of bookmarklets appeared, and I was testing Windows, and they just support it, so…
|
||||
- **15:25:17 · Alex Martemyanov:** Thank you.
|
||||
- **15:25:19 · Dominik Kapusta:** Maybe it was because they moved to Chromium, I don't know. Yeah, let me quickly check.
|
||||
- **15:25:19 · Alex Martemyanov:** Okay, that should be fine then. Yeah, for sure, Chromium does support it.
|
||||
- **15:25:26 · Dominik Kapusta:** Oh, my God. Yeah, yeah, yeah, of course, of course.
|
||||
- **15:25:29 · Alex Martemyanov:** But from our side, it may require some extra precautions, like security or privacy.
|
||||
- **15:25:38 · Dominik Kapusta:** Mm-hmm.
|
||||
- **15:25:38 · Alex Martemyanov:** Because they are not Chromium, essentially.
|
||||
- **15:25:40 · Dominik Kapusta:** Yeah. This is the issue that we got on Reddit. And, uh… And I had a task, I had a task to scope a project to support bookmarklets.
|
||||
- **15:25:52 · Alex Martemyanov:** Mm-hmm. Okay, and uh… What else? Basically, the last thing was the tab groups, research.
|
||||
- **15:26:09 · Dominik Kapusta:** Mm-hmm.
|
||||
- **15:26:10 · Alex Martemyanov:** And, uh, it's… Didn't produce any. testable thing, but anyways, I think that should be more than enough for a demo, and maybe even grow to some projects like our groups, for example.
|
||||
- **15:26:20 · Dominik Kapusta:** Yeah, totally. Mm-hmm. Mm-hmm. Yeah, sure.
|
||||
- **15:26:27 · Alex Martemyanov:** So, yeah, that's how the late night went yesterday.
|
||||
- **15:26:31 · Dominik Kapusta:** just. Just, just a thought that… We've had a couple of… Hug Days demos for type groups already, in the past Hug Days. So, just so you know, um…
|
||||
- **15:26:43 · Alex Martemyanov:** Yeah, sure.
|
||||
- **15:26:48 · Dominik Kapusta:** I don't know what to say. I just wanted to say that we've seen it a couple of times, nothing happened out of it. Probably because there's always more important work to do. But I think… If you would be able to add multiple selection. And drag and drop for multiple tabs at once, that would be a killer feature, that would be something that we could totally just add. to the browser right now, which… because it's more… it's much simpler than tab groups, right? Conceptually. Just a…
|
||||
- **15:27:25 · Alex Martemyanov:** Yep.
|
||||
- **15:27:26 · Dominik Kapusta:** a single interaction, really, yeah. So if you want to make impact quickly, then that would be simple. And the tab groups… we did tab groups a few times, so… and of course, you can do tab groups, everyone knows that. You can do tab groups.
|
||||
- **15:27:26 · Alex Martemyanov:** Yeah, you're right.
|
||||
- **15:27:41 · Dominik Kapusta:** Um… No.
|
||||
- **15:27:43 · Alex Martemyanov:** Yeah, there is one… one more thing I tried. It's basically the raycast, and uh… Integration. Like… Tapping.
|
||||
- **15:27:57 · Dominik Kapusta:** Nice.
|
||||
- **15:27:57 · Alex Martemyanov:** Dr. Yai. Searching… or bookmark search. And the same, basically, for the, uh… Or, how is it called? Spotlight. Yeah, so I'm also thinking if it could be… somehow released, or… I don't know. Probably should go through the product.
|
||||
- **15:28:35 · Dominik Kapusta:** Yeah, but… so that Spotlight plugin… it would be shipped with the app, and then Spotlight would… get extra functionality if DuckDuckGo is installed? Mm-hmm.
|
||||
- **15:28:45 · Alex Martemyanov:** Uh, yeah, Spotlight is… Spotlight is shipped within the app, and Raycast needs an extension.
|
||||
- **15:28:50 · Dominik Kapusta:** Mmhm. Okay, yeah.
|
||||
- **15:28:54 · Alex Martemyanov:** distributed through the Raycast store.
|
||||
- **15:28:57 · Dominik Kapusta:** Right. Yeah, that Spotlight plugin would be cool, for sure. So I guess it's just a target in the app, right? Like some… Up extension, something like that.
|
||||
- **15:29:08 · Alex Martemyanov:** Uh… Probably.
|
||||
- **15:29:10 · Dominik Kapusta:** Mm-hmm. Okay. Yeah, sure.
|
||||
- **15:29:11 · Alex Martemyanov:** I haven't seen the code.
|
||||
- **15:29:16 · Dominik Kapusta:** Oh, okay. Funny. Great.
|
||||
- **15:29:22 · Alex Martemyanov:** Yeah, so… So that's the plan for the holidays, I think should be plenty.
|
||||
- **15:29:27 · Dominik Kapusta:** Mm-hmm.
|
||||
- **15:29:30 · Alex Martemyanov:** And, uh… And yeah, we have the upcoming… Performance review, right?
|
||||
- **15:29:37 · Dominik Kapusta:** Yes, we do. And I would like you to… Spend a moment. This week. Probably. Well, if not this week, then you'll have to do it on Monday, which is… which may be tricky, I don't know, but Monday will be the due date for your self-reflection, which I think now is called self-assessment. One second.
|
||||
- **15:30:05 · Alex Martemyanov:** Mm-hmm.
|
||||
- **15:30:06 · Dominik Kapusta:** uh… Oh. Where is it? I don't know. Ah, I know. One second. self assessment template. Yes. Here's the link. There are also… Trainings. For on the performance review this week. I don't know the dates, but… It's happening. Performance review trainings.
|
||||
- **15:30:51 · Alex Martemyanov:** Mm-hmm. And that's basically the usual stuff.
|
||||
- **15:31:00 · Dominik Kapusta:** Thursday, 9am ET. That's… late for you. 7:30, 7:00, 7:00 PM, I guess.
|
||||
- **15:31:15 · Alex Martemyanov:** 9 a.m. ET. ET, 9… AM. Yeah, 7, it's fine.
|
||||
- **15:31:26 · Dominik Kapusta:** So… It's the usual stuff. But… But, yeah, uh… There are also recordings here. And, uh… The thing with the self-assessment thingy is that the template is new. And it's shorter, it's supposed to be shorter than the self-reflection. You have these five… Five sections, project management, which essentially map to dimensions. And then the looking ahead section, and you're supposed to fill each of them with… Well, with your assessment of the last period and keep it 150 words or shorter. Each section.
|
||||
- **15:32:30 · Alex Martemyanov:** Thursday, 9 AM is… Is it Thursday?
|
||||
- **15:32:37 · Dominik Kapusta:** Yes. My name is T.
|
||||
- **15:32:40 · Alex Martemyanov:** Yes, but… Okay. Not to miss it as I lost time mixing the dates.
|
||||
- **15:32:48 · Dominik Kapusta:** Mm-hmm. Ah, yeah, yeah, yeah. So, that's the self-assessment template, and… Umm… I will probably be working on mine this week, sometime during Hug Days, just so that on Monday I can just… Just verify that it… oh, copy it over to the official task and verify if it makes sense and just complete it. And you're supposed to complete it on Monday.
|
||||
- **15:33:07 · Alex Martemyanov:** Mmhm.
|
||||
- **15:33:18 · Dominik Kapusta:** And then… I'll be working on your review for the next three days. And that's… and that's roughly it. And then talking with review advisors and blah blah blah. for your career… for your growth areas. I've updated them after our discussion last time. I updated them with. A shout out. And essentially kept the previous growth areas, uh… so here's the link again. And that's that. So, essentially… I just reflected what was in the feedback. About the communication project, like…
|
||||
- **15:34:10 · Alex Martemyanov:** Mmhm.
|
||||
- **15:34:13 · Dominik Kapusta:** You can surely… Oh. Relay your thoughts into comments and updates on the project, but just remember to… to do it unprompted, to avoid being pinged on that, and that would be great. And then, I think it's the only thing missing, uh… Here. And then you didn't have a chance… so you did great with, um… With, uh, code reviews and the ship review, uh… contributions to Andre's project. So… have a look at more opportunities like that, and also have a look at tech designs that appear in the Apple team.
|
||||
- **15:35:01 · Alex Martemyanov:** Mm-hmm.
|
||||
- **15:35:03 · Dominik Kapusta:** Um, to… share your thoughts on that, and I think that's what we need to be looking for. What we're looking for, essentially, is… because the rest… the rest, you're just… you're just doing it. You're doing functional expertise. it's… it's a clear D double star, and we… uh… we also won't move it to E until you're at least D star in project management, that's what I've been told. It would be hard to bump. Functional expertise to E without at least a star in project management. So that remains at this DW star. Organization leadership, you're at this star already. Uh… I know they're doing that. You're just… just… just… just… uh… Um, focusing on, uh… improving the macOS browser in many ways, and fixing issues as they come, and fixing stability of tests, and so on and so on, and you're just actually working on it. Um… Mostly on your own. Uh, which is… Which is not bad, either. I mean, not bad anyway, but… it's just how we work here, right? You have your backlog, and you work on that, and you know what you need to do, so that's great. Some of the initiatives… are not necessarily… ideal for the team, at least. I mean, you've worked on the VS Code thingy, it appears not to be… very appealing to the entire team. So, there may be discussions of whether this was… Time well spent. But we've had that… we've had that discussion at some point. Oh, you… so, what's… undiscussable is that. As part of this effort, you did a lot of improvements to the macOS codebase, and that's great. And then we stopped at some point. Which probably was the right point, when… The rest of the team learned about everything, and they started asking questions, and you open a proposal, and tech design, and there was a longer discussion, and the…
|
||||
- **15:37:26 · Alex Martemyanov:** Yeah, there was a discussion of actual effort to implement the… the actual thing was relatively low, so it was more about the refactoring itself, and…
|
||||
- **15:37:26 · Dominik Kapusta:** Think was. was closed. Yeah. Mm-hmm. For…
|
||||
- **15:37:37 · Alex Martemyanov:** fixes that are proceeding it.
|
||||
- **15:37:39 · Dominik Kapusta:** For the future, I think you could… you could go with, uh… a proposal earlier than that, maybe, if that makes sense. I know there was that tech design a year ago, but, you know, a year is a long time, people sort of forgot about that in the meantime. Yeah, but… But overall, it was… it was… it was… I mean, a lot of it was worth it. And I wouldn't really… be connecting that incident that we had with the VS Code, uh, initiative. It just happens, right? It's… sometimes it happens. We'll talk about it in the Apple Weekly. it's not easy to test everything on macOS 12, unless we will be… we want to accept that we'll be working, like, twice… I mean, half as fast, so 50% slower.
|
||||
- **15:38:38 · Alex Martemyanov:** Well, the answer would be QA, but yeah, I know.
|
||||
- **15:38:39 · Dominik Kapusta:** Thank you. Yeah, yeah. And. Yeah, so that's organizational, and the one that you're… that I'm trying to push you into more is team leadership, and that means… Well, project advising. That's one thing, but it's very hard to get to project advising if you're jumping between objectives. And also, it works… better if you have proven project management skills first, but you're… I think you're almost there. Um… Next thing I wanted to say is… Yeah, project advising, but outside of project advising, it's… Growing people via code reviews, via, um… Should preview commands and take design commands.
|
||||
- **15:39:37 · Alex Martemyanov:** Mm-hmm.
|
||||
- **15:39:38 · Dominik Kapusta:** So, yeah, that could be a way to bump your team leadership. Uh, and also this… Cycle is short. So let's see if we can… Bump anything. But… If we can, that would be great. I was thinking about project management, but let's see what… Let's see what happens. Let's see if I'm able to defend that. The conclusion may be that, yeah, you still need more time. And then we'll have to wait until next cycle. Yeah, but let's see. Let's see. I'll do my best. And you can help me by writing yourself a section.
|
||||
- **15:40:22 · Alex Martemyanov:** It's fine.
|
||||
- **15:40:29 · Dominik Kapusta:** on time.
|
||||
- **15:40:31 · Alex Martemyanov:** Mm-hmm.
|
||||
- **15:40:34 · Dominik Kapusta:** Good. So that's the… that's the, uh, growth areas and shoutouts. Next week, I would ideally… not have a meeting, not have any meetings on Tuesday, because I'll be busy writing reviews. So, yeah, we could just skip it next week.
|
||||
- **15:40:53 · Alex Martemyanov:** Good.
|
||||
- **15:41:01 · Dominik Kapusta:** I had one more thing. That I don't remember. Oh, I was looking at… I was actually thinking actively about your proposal for macOS 12 testing, and I… at the end, I wrote that we'll have this post-mortem, and hopefully we'll talk more as a team.
|
||||
- **15:41:11 · Alex Martemyanov:** Mm, yep.
|
||||
- **15:41:21 · Dominik Kapusta:** About possible solutions for that, but… Uh, in the meantime, I noticed that Bitrise have removed macOS 13 image, so they only have macOS 14, and I think they will keep the macOS 14 for, like, a year more. while GitHub is removing macOS 14 in November. But that's macOS 14, and 13 is out already, and 12 as well, of course. So I don't know.
|
||||
- **15:41:50 · Alex Martemyanov:** Uh, well, let me… Let me ask you another question, which may also need some thoughts.
|
||||
- **15:42:00 · Dominik Kapusta:** Yeah.
|
||||
- **15:42:01 · Alex Martemyanov:** So let me share my screen. So basically this is the… The system also was, um… Via coding in parallel, so it's the virtual machine fleet.
|
||||
- **15:42:12 · Dominik Kapusta:** Mmhm. Mmhm.
|
||||
- **15:42:16 · Alex Martemyanov:** Uh, controller, like, maintaining images, right, and activity, leases, uh, Xcode installs, uh… Uh, system protection, disabling, TC\CC, and all this stuff. And it's basically controlling my current Mac with the external drive, controlling older MacBook, which can be booted and also used for.
|
||||
- **15:42:38 · Dominik Kapusta:** Mmhm.
|
||||
- **15:42:43 · Alex Martemyanov:** Remote debugging and remote UI test and so on. And yeah, and some virtual machines extra. Uh, there is one note on the, uh… Yeah, and this is supposed to be, like, uh… orchestrator over the TART system that's used on production runners, like Detraze, I think.
|
||||
- **15:43:11 · Dominik Kapusta:** Yeah, yeah, yeah, yeah.
|
||||
- **15:43:13 · Alex Martemyanov:** And it provides MCP controls, which is supposed to give agents ability to run the UI tests, boot up, get a lease for virtual machine, run the tests, shut it down, perform cleanup and so on. And… Still, there is this rule about external MCP and tools that should be approved by org. Uh, highlighted in the… bug days, uh… Agenda? So…
|
||||
- **15:43:51 · Dominik Kapusta:** Okay.
|
||||
- **15:43:52 · Alex Martemyanov:** I'm thinking whether or should I present it to the team as a possible solution for integration and including macOS 12 and 13 tests support.
|
||||
- **15:44:02 · Dominik Kapusta:** I think we can talk about it. I think we can talk about it. Ideally, we would have… A machine. Somewhere. That runs this. And that machine… so, if that machine could… run virtualization on its own. and be used for testing on macOS 12 and 14, that would be great. And we wouldn't… be doing that. On a regular basis, but… So I was talking about it a little bit with Jonathan, and he said, if we are able to run tests once a week. That would be something already. At least know if the app is crashing or not. Like the proper smoke test. If there is a smoke, then something is wrong. About, uh… We don't seem to have… a way of… Um… Setting this up as part of CI. And that would be ideal, but… But we won't be able to do it. And I wouldn't rely on local setups, because… Most likely, people… Wouldn't. Random. Essentially. Unless it's… it's really straightforward. But maybe you can make it straightforward. To some extent. So that if we had these setups and we could just say, okay, test. test on macOS 12 now, and if it all worked, that would be amazing, that would be great, actually. And that would be…
|
||||
- **15:45:51 · Alex Martemyanov:** Maybe…
|
||||
- **15:45:53 · Dominik Kapusta:** A big thing.
|
||||
- **15:45:55 · Alex Martemyanov:** Should I… Should I raise a question?
|
||||
- **15:46:00 · Dominik Kapusta:** Mm-hmm.
|
||||
- **15:46:00 · Alex Martemyanov:** or… I don't know… proposal, voting… Thoughts sharing during the Apple Weekly. suggesting this kind of a solution that can be potentially used as an agent MCP for automated testing.
|
||||
- **15:46:11 · Dominik Kapusta:** Mmhm.
|
||||
- **15:46:19 · Alex Martemyanov:** Like, any testing, unit testing, integration testing, UI testing, essentially.
|
||||
- **15:46:19 · Dominik Kapusta:** Mmhm.
|
||||
- **15:46:27 · Alex Martemyanov:** Yeah, unit testing won't work because…
|
||||
- **15:46:30 · Dominik Kapusta:** No, yeah, yeah, it wouldn't.
|
||||
- **15:46:30 · Alex Martemyanov:** Maybe it would work with the test bundle directly moved. Yeah, there is some ways, but yeah, mostly for UI testing or agent-based screen control.
|
||||
- **15:46:33 · Dominik Kapusta:** Ah, hmm. Mm-hmm. Yeah, we can limit it to UI testing, sure.
|
||||
- **15:46:43 · Alex Martemyanov:** So, whether anybody is, uh, wishing to have… something similar to have, uh, this kind of local setup. It supports, uh, remote debugging from VS Code as well, by the way, so we can just…
|
||||
- **15:46:57 · Dominik Kapusta:** Okay.
|
||||
- **15:46:58 · Alex Martemyanov:** Select the virtual machine where you want to run the browser, and it will boot up, show the screen, and connect to it, and you will be debugging, like. And.
|
||||
- **15:47:07 · Dominik Kapusta:** with… with Xcode. Uh, local?
|
||||
- **15:47:11 · Alex Martemyanov:** Yes, with local export.
|
||||
- **15:47:12 · Dominik Kapusta:** Install? But you have to have the lower version.
|
||||
- **15:47:14 · Alex Martemyanov:** Without Xcode.
|
||||
- **15:47:17 · Dominik Kapusta:** Or.
|
||||
- **15:47:18 · Alex Martemyanov:** Yeah, of course, you have to install the Xcode tools in the virtual machine, which is managed automatically.
|
||||
- **15:47:25 · Dominik Kapusta:** Mm-hmm.
|
||||
- **15:47:26 · Alex Martemyanov:** But you just click run in VS Code, and it just runs. Like, Xcode would do, but Xcode does not support remote debugging.
|
||||
- **15:47:30 · Dominik Kapusta:** Okay. Yeah. Look…
|
||||
- **15:47:37 · Alex Martemyanov:** I'm not quite sure that I can demo it right now, but this feature is already baked in. I just haven't tested it directly and it even starts instantly without all this loading of symbols.
|
||||
- **15:47:40 · Dominik Kapusta:** Yeah, yeah, yeah.
|
||||
- **15:47:53 · Alex Martemyanov:** Because the dynamic library cache is also loaded and available from the virtual machines. So it just can be straight debugged from the host.
|
||||
- **15:47:57 · Dominik Kapusta:** Mm-hmm. Yeah, to be fair, that sounds… really tempting to me. Uh… But… Only if it was… very simple to use, as in, I tell my agent, run this test on macOS 12, and it does everything, setting up the virtual machine, uh, installing an image. Copying the app and running it.
|
||||
- **15:48:36 · Alex Martemyanov:** Yeah, so that's… that's… that's the question I…
|
||||
- **15:48:37 · Dominik Kapusta:** Ruby.
|
||||
- **15:48:41 · Alex Martemyanov:** Thinking to just bring up during the Apple Weekly, and just ask if anybody would use.
|
||||
- **15:48:47 · Dominik Kapusta:** Yeah.
|
||||
- **15:48:48 · Alex Martemyanov:** Something like it, if it's.
|
||||
- **15:48:49 · Dominik Kapusta:** Yeah, okay.
|
||||
- **15:48:50 · Alex Martemyanov:** ready available and one click from running.
|
||||
- **15:48:54 · Dominik Kapusta:** Mm-hmm. Mm-hmm. Uh…
|
||||
- **15:48:56 · Alex Martemyanov:** justifying the Xcode project as well.
|
||||
- **15:48:59 · Dominik Kapusta:** So… So, we have that thing called Apple Engineering Expectations. And… One of the expectations is testing supported macOS versions, and we have it here. And then… It says… something about ensuring that older macOS versions are included in the testing process. This is actually… Kind of a dead lull, because no one does this. Virtually no one. You do it, right? But also not for everything, right? Not for dropping the storyboard. Fine, I mean fine, right? I wouldn't do it either, and I would just see the crash and fix it.
|
||||
- **15:49:42 · Alex Martemyanov:** No, I don't.
|
||||
- **15:49:54 · Dominik Kapusta:** But. So we have this, and it's like a wishful thinking. People should be doing that, but people are not doing that, because it's so much work. Um, so…
|
||||
- **15:50:03 · Alex Martemyanov:** Yeah, so basically it has this use virtual body. That means you should install virtual body, you should download an image, you should manually go through the setup assistant, you should manually download Xcode.
|
||||
- **15:50:12 · Dominik Kapusta:** Yeah, yes, maintain it. Yes, yes.
|
||||
- **15:50:17 · Alex Martemyanov:** pass the app to it, and have NSAlert-based debugging.
|
||||
- **15:50:22 · Dominik Kapusta:** Mmhm.
|
||||
- **15:50:23 · Alex Martemyanov:** But I'm kind of suggesting the other way when you install this Verfil's piece of software and you just click run from VS Code and it just works.
|
||||
- **15:50:26 · Dominik Kapusta:** No. No. Mm-hmm. Yeah, yeah.
|
||||
- **15:50:40 · Alex Martemyanov:** So, just something to discuss.
|
||||
- **15:50:44 · Dominik Kapusta:** Yeah. That sounds good to me.
|
||||
- **15:50:46 · Alex Martemyanov:** I don't know, maybe you can talk about this. expectation to support the older macOS as well, and vote up for it.
|
||||
- **15:50:53 · Dominik Kapusta:** Mm-hmm. Totally, totally.
|
||||
- **15:50:56 · Alex Martemyanov:** And, then we can make a proposal to. To include this system as, like, an official setup, maybe?
|
||||
- **15:51:05 · Dominik Kapusta:** Mmhm.
|
||||
- **15:51:05 · Alex Martemyanov:** And run it under an official project in the AOR.
|
||||
- **15:51:11 · Dominik Kapusta:** Sure. Sure, sounds good. Sounds good. That would be great.
|
||||
- **15:51:22 · Alex Martemyanov:** Okay, then.
|
||||
- **15:51:27 · Dominik Kapusta:** Nice. Is there anything else we should cover? Bye-bye.
|
||||
- **15:51:33 · Alex Martemyanov:** Uh, yeah, about the separate project file… It's kind of part of…
|
||||
- **15:51:38 · Dominik Kapusta:** Oh, yes. Mmhm.
|
||||
- **15:51:39 · Alex Martemyanov:** This, I mean…
|
||||
- **15:51:41 · Dominik Kapusta:** Yeah, I mean, that…
|
||||
- **15:51:42 · Alex Martemyanov:** The bigger… the bigger picture includes it. Oh, yeah. It has some couple of talks. Introduced retrofitting some XC tests.
|
||||
- **15:51:51 · Dominik Kapusta:** Oh.
|
||||
- **15:51:57 · Alex Martemyanov:** thing to be supported on macOS 12. It's one file.
|
||||
- **15:52:00 · Dominik Kapusta:** Okay. Okay. Okay. Bye.
|
||||
- **15:52:02 · Alex Martemyanov:** Of, like, 400 lines, and uh… And using all the runner. Oh. So it's 100% doable. My agents are running those tests using this hack. Uh, without separate project, but they are building it locally, deploying, and using the hub to run it. And I'm not sure whether it's final, uh… final architecture we want, and there is a lot of mistakes. Agents are… Okay. during the process, and maybe separating this Xcode project. Would simplify things a little bit.
|
||||
- **15:52:46 · Dominik Kapusta:** Mmhm. Okay, but the idea is to completely remove UI tests from the Xcode project, or just have another project for macOS 12 and older?
|
||||
- **15:52:56 · Alex Martemyanov:** Not remove, but rebase. So like we have iOS project and macOS project, we'll have a third project for macOS UI tests because it's a separate project.
|
||||
- **15:53:03 · Dominik Kapusta:** Mm-hmm. Okay.
|
||||
- **15:53:08 · Alex Martemyanov:** It does not require any of the dependencies to resolve it every time. It will make the build faster, excluding submodels and the package resolution.
|
||||
- **15:53:10 · Dominik Kapusta:** Mm-hmm. Mm-hmm. Yeah, I see. Okay.
|
||||
- **15:53:19 · Alex Martemyanov:** Uh, like, currently, build takes a lot of time for… on each runner.
|
||||
- **15:53:19 · Dominik Kapusta:** Uh, one… fine. One thing, sure, one thing that is. Handy today is that you can just… stay in the same Xcode project and just run UI tests.
|
||||
- **15:53:36 · Alex Martemyanov:** Yeah, and we are basically not risking anything.
|
||||
- **15:53:37 · Dominik Kapusta:** So…
|
||||
- **15:53:40 · Alex Martemyanov:** in production. If it won't work, we will put it back.
|
||||
- **15:53:45 · Dominik Kapusta:** Yeah, yeah, yeah, yeah, sure, but your plan would be to… move these UI tests from the macOS Xcode project to that separate Xcode project, so that if you want to run UI tests, if you want to run UI tests, you would have to… locally, you would have to do what?
|
||||
- **15:53:57 · Alex Martemyanov:** through your iTest project, yeah.
|
||||
- **15:54:04 · Dominik Kapusta:** First build the app.
|
||||
- **15:54:04 · Alex Martemyanov:** Hmm, same thing.
|
||||
- **15:54:06 · Dominik Kapusta:** Which is what?
|
||||
- **15:54:06 · Alex Martemyanov:** Same thing. Have the dependency, choose the scheme, and run it. I guess nothing changes from… Nothing should change from it, from the current setup.
|
||||
- **15:54:24 · Dominik Kapusta:** But you… Didn't you say that you want to… move these tests from one Xcode project to another.
|
||||
- **15:54:33 · Alex Martemyanov:** Uh, yes, but I think… I assume the expectation is to load and work from the export workspace file.
|
||||
- **15:54:42 · Dominik Kapusta:** Ah…
|
||||
- **15:54:42 · Alex Martemyanov:** Isn't it?
|
||||
- **15:54:43 · Dominik Kapusta:** Okay, yeah, yeah, sure.
|
||||
- **15:54:44 · Alex Martemyanov:** I mean, yeah, if you run the macOS project directly, it won't be there, but if you load the whole file, it's still there.
|
||||
- **15:54:48 · Dominik Kapusta:** Yeah, yeah, yeah, I'm… yeah, totally. I'm just not using the AI workspace at all, but that's just me, so…
|
||||
- **15:54:55 · Alex Martemyanov:** So, yeah, that's a cone.
|
||||
- **15:54:58 · Dominik Kapusta:** Huh-huh. But that's okay, I mean, I know that I'm the minority. Plenty of people use the workspace, so we should be fine.
|
||||
- **15:55:10 · Alex Martemyanov:** Yeah, so that's the deal, and it should… Should just work.
|
||||
- **15:55:15 · Dominik Kapusta:** All right. Uh, alright, great. Great. Let's talk more about it in the Apple Weekly, for sure. All right, all right, all right. Anything else? You mentioned some organizational issues.
|
||||
- **15:55:39 · Alex Martemyanov:** Uh…
|
||||
- **15:55:40 · Dominik Kapusta:** Anything I can help you with?
|
||||
- **15:55:42 · Alex Martemyanov:** Some of operational issues. And, uh…
|
||||
- **15:55:45 · Dominik Kapusta:** Operational, yeah.
|
||||
- **15:55:47 · Alex Martemyanov:** I mean, there's all in the… Events reporting, uh… I'm talking with Michal about it.
|
||||
- **15:55:54 · Dominik Kapusta:** Ah, okay, okay.
|
||||
- **15:55:55 · Alex Martemyanov:** Just… just in the moment, and I hope we can get it… get it released today, just so it gets to the internal…
|
||||
- **15:56:03 · Dominik Kapusta:** Mmhm.
|
||||
- **15:56:03 · Alex Martemyanov:** Or can I do it tomorrow? It's too…
|
||||
- **15:56:07 · Dominik Kapusta:** Um… ideally today. You can, of course, do it tomorrow with a release exception.
|
||||
- **15:56:09 · Alex Martemyanov:** problematic, yeah. Yeah, okay. So, yeah, I'm trying to get it released today, and… And report it in the OEE stand-up meeting. And that's it.
|
||||
- **15:56:25 · Dominik Kapusta:** Sounds good.
|
||||
- **15:56:26 · Alex Martemyanov:** Otherwise, there's pretty much none of the tasks on me remaining. Except for the old Greek twins that are just hanging on me.
|
||||
- **15:56:37 · Dominik Kapusta:** Now.
|
||||
- **15:56:38 · Alex Martemyanov:** Thank you.
|
||||
- **15:56:39 · Dominik Kapusta:** All right.
|
||||
- **15:56:40 · Alex Martemyanov:** And…
|
||||
- **15:56:42 · Dominik Kapusta:** Alright, cool. Uh… fine. If you need anything from me these hack days, let me know. Um… Please work on the… Yeah, going on.
|
||||
- **15:56:52 · Alex Martemyanov:** Yeah, so basically… What's the expectation on the holidays? Uh, for the changes, like fire animation, or… something… like, bookmark search. Is it… should I contact Steven on it and, uh, try to… Push. Yes. Quick project.
|
||||
- **15:57:14 · Dominik Kapusta:** I think… so what you've shared with me right now, I couldn't see… the animation was not looking great on the shared screen, right? I only saw a few frames at the beginning and at the end, but if you can record the video… Uh, and if it really is, like, the window is being burned, so you can see the window underneath of what was burned, and then I think it's…
|
||||
- **15:57:36 · Alex Martemyanov:** Yeah. Cheers.
|
||||
- **15:57:41 · Dominik Kapusta:** It would be an amazing thing to have, and if you could… I mean, you can show it to Steven at any time, because you have it, you can just record a video and send to him and say, what do you think about it? I'm… and that would probably be greatly appreciated. I'm not sure if they would want these pixel animations. Because we like the fire thingy and just because of that. But yeah, definitely send that to Steven. And, yeah, I think we could, we could… Try and move forward with it.
|
||||
- **15:58:20 · Alex Martemyanov:** Okay, and I'll try to experiment with the tab grouping, dragging, whatever, maybe it will grow to the project. For me, it's called Popoyama. Right.
|
||||
- **15:58:35 · Dominik Kapusta:** Right, right.
|
||||
- **15:58:38 · Alex Martemyanov:** And, uh, yeah, the rest of the week for the, uh… So, reflection.
|
||||
- **15:58:44 · Dominik Kapusta:** Mm-hmm. Sounds good. Awesome.
|
||||
- **15:58:45 · Alex Martemyanov:** And that's it.
|
||||
- **15:58:47 · Dominik Kapusta:** Cool, cool. Sounds great. All right.
|
||||
- **15:58:49 · Alex Martemyanov:** And yeah, today, today about weekly, I have three demo sessions. And one postmortem.
|
||||
- **15:58:58 · Dominik Kapusta:** Yeah, which is fine. Looking forward to it.
|
||||
- **15:59:01 · Alex Martemyanov:** Ah, postmortem, I should fill the template, yeah.
|
||||
- **15:59:01 · Dominik Kapusta:** All right. Yeah. Yeah, all right. Cool, uh, so I'll see you later, and we'll catch up later this week if needed. Thanks a lot.
|
||||
- **15:59:15 · Alex Martemyanov:** Okay, sure. Yeah.
|
||||
@@ -86,8 +86,8 @@
|
||||
"note_modified_at": "2026-10-16T15:51:25.415Z",
|
||||
"source_url": "https://us01mynotes.zoom.us/klekRLtLSEuMv0PCCPCjtA",
|
||||
"folder": "2026-10-16 All-Company Meeting 2026-10-16 21 31(GMT+6 00) klekRLtLSEuMv0PCCPCjtA",
|
||||
"sha256": "86407aecffbf09effe200b26e80a01887ee197ba99d5caea70c124743fbee3fb",
|
||||
"cues": 3
|
||||
"sha256": "34ef73307fe86cc2d6f98caf57a719ae46937fb2d0efea3a18e03e21a42f1e00",
|
||||
"cues": 20
|
||||
},
|
||||
"AEmGnEdJQfCMmCjwLyGtGA": {
|
||||
"title": "Зал персональной конференции Alex Martemyanov 2026-10-09 18:51(GMT+6:00)",
|
||||
@@ -158,8 +158,8 @@
|
||||
"note_modified_at": "2026-11-10T10:01:44.278Z",
|
||||
"source_url": "https://us01mynotes.zoom.us/p5FdcX9WT-afBpWjRgaW0w",
|
||||
"folder": "undated Dominik Kapusta's Personal Meeting Room p5FdcX9WT-afBpWjRgaW0w",
|
||||
"sha256": "5d3aeb038b4212d9cdd785c7b1683d37ea04faf0816463ce4e37873af9bb8dbb",
|
||||
"cues": 3
|
||||
"sha256": "21d3c3d8f4c7fea11976f5cb54b98a121c895c7aabcb1b541c6d3f6f1167460a",
|
||||
"cues": 130
|
||||
},
|
||||
"e5TYWRytRz2WwWSe68BSWQ": {
|
||||
"title": "O-E 2026",
|
||||
@@ -218,8 +218,8 @@
|
||||
"note_modified_at": "2026-10-23T15:29:29.141Z",
|
||||
"source_url": "https://us01mynotes.zoom.us/bPprGg5DTye9H-RQXkwMuw",
|
||||
"folder": "undated All-Company Meeting bPprGg5DTye9H-RQXkwMuw",
|
||||
"sha256": "67d79d187f34012b3d4e50ea54ba7648c909bfe24d067a4bc04ba72cd8f9cbb6",
|
||||
"cues": 3
|
||||
"sha256": "92c8cdc1104e86fdbead212d4f69caf87623d332e2ad67f7807cdc248acd9fb3",
|
||||
"cues": 50
|
||||
},
|
||||
"r6weCpT7SnasTUiybJW95w": {
|
||||
"title": "Apple Weekly Team Meeting - Zoom ID",
|
||||
@@ -350,8 +350,8 @@
|
||||
"note_modified_at": "2026-10-20T09:04:33.786Z",
|
||||
"source_url": "https://us01mynotes.zoom.us/Mg62hl1GSI2gw4XeGvHAsg",
|
||||
"folder": "2026-10-20 Dominik Kapusta's Personal Meeting Room Mg62hl1GSI2gw4XeGvHAsg",
|
||||
"sha256": "be62837e60b31b10dcb7402a7696d655fc888703e8a91db94ee3e13df9dd4040",
|
||||
"cues": 3
|
||||
"sha256": "f5020ecd26269cc74c4c5e31200220dfd47607f197a79607112ecdd353785740",
|
||||
"cues": 322
|
||||
},
|
||||
"QvxllpCuTTSLGEZp-R6jQw": {
|
||||
"title": "Michal Smaga's Personal Meeting Room",
|
||||
@@ -362,8 +362,8 @@
|
||||
"note_modified_at": "2026-10-19T12:37:38.903Z",
|
||||
"source_url": "https://us01mynotes.zoom.us/QvxllpCuTTSLGEZp-R6jQw",
|
||||
"folder": "2026-10-19 Michal Smaga's Personal Meeting Room QvxllpCuTTSLGEZp-R6jQw",
|
||||
"sha256": "a4b3c5ce7fafb99496019591da19f9a103e35cf5f37ec42aa8f154021fdebcae",
|
||||
"cues": 133
|
||||
"sha256": "5cf16938df6ebe0110bec8e8b4311fcbe55a764bd2bb72f64faa049ba1777d9e",
|
||||
"cues": 3
|
||||
},
|
||||
"KcmYOq5_SQGPxdkdbhRx9A": {
|
||||
"title": "Dominik Kapusta's Personal Meeting Room",
|
||||
|
||||
@@ -1 +1 @@
|
||||
{"observed_at":"2026-11-19T07:44:52.473Z","scanned":31,"imported":6,"skipped":25,"withoutTranscript":0,"coverage":"complete","sections":[{"name":"Owned by me","pages":5,"notes":86,"complete":true,"terminal_cursor":true},{"name":"Shared with me","pages":1,"notes":0,"complete":true,"terminal_cursor":true},{"name":"Starred","pages":1,"notes":0,"complete":true,"terminal_cursor":true}],"discovered":86,"gaps":[],"recovered_transcripts":0,"policy":"reread_all_owned_shared_and_starred_notes_since_cutoff","since":"2026-09-30"}
|
||||
{"observed_at":"2026-11-19T08:16:23.181Z","scanned":31,"imported":5,"skipped":26,"withoutTranscript":0,"coverage":"complete","sections":[{"name":"Owned by me","pages":5,"notes":86,"complete":true,"terminal_cursor":true},{"name":"Shared with me","pages":1,"notes":0,"complete":true,"terminal_cursor":true},{"name":"Starred","pages":1,"notes":0,"complete":true,"terminal_cursor":true}],"discovered":86,"gaps":[],"recovered_transcripts":0,"policy":"reread_all_owned_shared_and_starred_notes_since_cutoff","since":"2026-09-30"}
|
||||
+235
@@ -23,6 +23,241 @@
|
||||
"time": "21:31:17",
|
||||
"speaker": "Zach",
|
||||
"text": "Yep. Uh, yeah, sorry. Um, yeah, so just quick announcement there. Uh, Julio's moving to the, uh, DRI for that, um, and Mario is going to be, uh, the secondary. Um, so they've both been pretty heavily involved in, uh, that process, and we're excited for this transition."
|
||||
},
|
||||
{
|
||||
"time": "21:31:40",
|
||||
"speaker": "Josh Frank",
|
||||
"text": "I believe I'm next. So hey, everybody. I'm taking a quick break from the gym where you can frequently find me to tell you about random access learning. Just put the link in the chat. We have a session Thursday next week. 12:00 PM Eastern time, I think that's US Eastern, on corporate sustainability and being carbon negative in the AI era. So please, everybody, come to that if you can."
|
||||
},
|
||||
{
|
||||
"time": "21:32:17",
|
||||
"speaker": "AC",
|
||||
"text": "Everybody Ă last week we had our away mobile browser experience. Assessment our goals days a same they car our Browser mobile, browser experience from good to great in the previous cycle. We ship the android. And dialog."
|
||||
},
|
||||
{
|
||||
"time": "21:32:55",
|
||||
"speaker": "AC",
|
||||
"text": "Internal the keyboard now always on the new tape. Device to device migration. We want to ship this before black friday. A ui that s case for split. Screen. And we want to what support for many bar. We are going to start also the new tupage experiment for new users. And they think next these mark."
|
||||
},
|
||||
{
|
||||
"time": "21:34:04",
|
||||
"speaker": "Mark Ingram",
|
||||
"text": "Hey, everyone. I'm Mark from OL, the Desktop Browsers Objective. Some exciting news this week is Ivy is taking over as the ODRI, and I'll be moving on to the advisor role. I'll keep it short because I know we're on hack days this week, but I also, just before introing Ivy, I want to announce my new midlife crisis to everybody, which is. I decided to start learning the drums, and I can see Carl's excited face on the screen. Okay, that's my midlife crisis update. Over. Ivy, do you want to say hi?"
|
||||
},
|
||||
{
|
||||
"time": "21:34:31",
|
||||
"speaker": "I(",
|
||||
"text": "Yeah, I'm just really excited to take over OL, and stay tuned for some exciting news about extensions on macOS coming really soon."
|
||||
},
|
||||
{
|
||||
"time": "21:34:43",
|
||||
"speaker": "Julia Abreu",
|
||||
"text": "All right. Congrats, Ivy. That's exciting. So I'm kicking us off today. I'm going to actually share my whole screen because I'm going to be moving from one side to the other. So I have two demos today. So we have the Julia special, two demos. Um, my first demo is… since the meetup, I've been thinking about how, um… We need to, like, I've been thinking about the new objectives that we have about word of mouth and how we talk about DuckDuckGo and how, especially for ducklings, is hard to answer some of the questions that we get once you first join DuckDuckGo. So I wanted to create something that helps them answer those questions and understand our products better. So I do want to shout out Ben Smith because he created this. I just basically said the idea. Um, so this is an artifact, um, and you will see the different tabs here, so you have different questions per tab. Um, and then you have the specific questions here, which you can click on and see them in writing. Or, if you want to, you can actually listen to it as. kind of like a podcast episode. Um, so… let me know if you can actually hear this. I'm just gonna play a couple of seconds. Episode 1. The Big Picture. Last week, a friend of mine looked up, is it normal for your knee to click? Just once. For the next week, every website they visited tried to sell them knee supports, walking sticks, and one of those… So you get the gist of it. I hope you got to hear that. Um, so this is still a work in progress. We're going to be creating this content. Um, I really didn't want to… to be in audio, because I feel like if you get that in writing, it's different explaining as a human. So, this is what we're building. And then, the second thing I'm building… dang, the Zoom… The Zoom thing doesn't let me go to the other one. Okay, here. So this is the second thing that I built. This is coming from feedback from people who went on leave, which was around how to catch up with everything that had been happening since they were gone. Um, so this is a how… what do you miss? Uh, so basically, you add here the date you started your leave, and then the start of the date you return. Um, you click catch me up. Uh, it takes a couple of seconds, but it basically gives you, like, a summary of a bunch of things that happened while you were out. So, um… company-wide posts, uh, what was published, what was answered in odds and ends, so all the Q&A, which objectives are up-to-date, like, which assessment was the last thing, and what we're working on right now, uh, things that were shipped, uh, also, like, new AORs, retired AORs, so here, as you can see, like, one, um, sample of, like, the announcements. It gives you just, like, a summary of all the announcements. Um, and we also have a people tab, so, like, new hires, which teams they are in, uh, people who left, and then it also shows you, um, green bow ties, spotlights, in case you want to catch up with all the spotlights that were posted that. Um, the time you were away. I do want to add a tab for specifically functional team updates, so, like, if there's a new process or anything specific to the functional team, I'm just not sure yet where to get that information from. Um, so… working on that. If you have suggestions, or if you would like to be… try out these things, let me know. I would love the feedback. Um, and now, this is it for my demos. Now I have a demo by, um, Robert, who couldn't be here. So, also, please ping me if you can't, uh, hear this. Hello, hello, hello. I worked on three hacks this time around. I'll try to get through it all quickly. The first is to do with increasing Duck AI prompts. I thought that maybe a nice way to do that would be to add a bit of discoverability into our browser. So if you are looking at a foreign language page, then you get a suggestion to translate it. Can someone, uh, unmute themselves and just let me know if you can hear this? Because I'm, like, concerned because I can't see that. Okay, thank you."
|
||||
},
|
||||
{
|
||||
"time": "21:38:59",
|
||||
"speaker": "Anne Hildebrand",
|
||||
"text": "Yes."
|
||||
},
|
||||
{
|
||||
"time": "21:38:59",
|
||||
"speaker": "Zaahir Moolla",
|
||||
"text": "We can hear."
|
||||
},
|
||||
{
|
||||
"time": "21:39:02",
|
||||
"speaker": "Julia Abreu",
|
||||
"text": "And, um, so yep, that sends the page content off into Duck AI and translates it. We already had this feature, but, you know, just adding the prompt up there. That works. And there's lots of… this is very exploratory. There's lots of different ideas along these lines that we could look into, such as, if it's a long article, maybe we, um, tell the user how long it'll take and prompt to summarize, or on a shopping page, we could prompt them to, um, compare. Uh, the cool thing is that these suggestions here, these three options, that's all generated by our local LLM, so it's completely private. Um, nothing's, uh, hitting our servers until you click on one of those. Um, most recipes too. And this is a cool one, if you, um, are looking at an event, you can ask DuckAI to compute the event details. And I added this, um… dynamic UI, this card at the bottom of the Doug AI answer, and it gives you a button to add it to your calendar. Uh, one cool idea is, if you're looking at a privacy page, it could offer to help the user understand what it is they're agreeing to, so very within our brand. And another cool idea, just because YouTube features always seem to perform really well for us, is we could, um, prompt the user to, uh, do things using the transcript that appears in YouTube here. So this actually extracts the transcript from this panel. And it can send it to DocAI. Okay. Hack number two is, um, fixing a personal frustration of mine. So, I'm a Raycast user, and I'm always doing things like… um, converting currencies and, like, complex queries like this. And, uh, it frustrates me to no end that, um, that doesn't work when you plug it into DuckDuckGo. And so what I did is I had Claude reverse engineer the raycast calculator, and I've plopped that into SERP, and so now you can, um, jump into SERP running on this test machine, and do complex queries like that. And there's all sorts of things you can do. Mixed currencies is kind of cool. Um, one thing I use a lot is, like. Adding different units. And there's also, like, sort of… Complex math bits that are kind of fun. And the way that I handled this in the UI is that —. The simple calculator stays if you're doing a simple expression. And same if you're just doing a regular. conversion, then we get the existing UI for that too, because it's nicer since it has the dropdowns. Okay, and my third hack is yet another frustration that I've had for a while. So here we are looking at my phone. Oops. And, um, so we've always been able to switch tabs by swiping on the address bar at the bottom there, and that is quite nice. But what we haven't been able to do is swipe up to go to the tab switcher. And so I added that, and it turns out that Bartosz had already been working on this, so he has helped me a lot with this. Thank you very much. And yeah, it's really nice that you can… it tracks your finger, so you can kind of drag out halfway. Real smooth. And Bartosz added, you can drag out halfway and swipe to the right. Those are my hacks. Thank you very much. All right, and we're not done yet. I have another one by Pablo. When people want their data on another device they don't go looking for things and sync it back up doesn't really tell them what it does. Chanel's usability insight report made that very clear. And the problem is getting bigger. Zac AI chats, uh, can easily be lost. Um, the more stuff we add to Zac AI, um, the more. things that are worth keeping, Sink and Backup will just not be enough. So, we are proposing MyTacticGo, a private account. It's private because it's from us, and it needs no personal data to sign in, so no email and no password to remember. It is encrypted, your data is backed up, unsynced, and we show what's ready to go, like 100 passwords or 244 bookmarks, so the value is very concrete. On desktop, MyTacticGo lives in the toolbar, where people actually look. It lists what will be synced, like your chats and passwords and bookmarks, but it also brings your subscription. So, this can become, actually, your home base, and it shows your plan and your connected devices, so it is a great opportunity for… for dependability, um, and cross-promoting other… other features and understanding our… our ecosystem. All in one place. That's it for me, and I think we're. It's Andrea next."
|
||||
},
|
||||
{
|
||||
"time": "21:44:01",
|
||||
"speaker": "Andrea Soto",
|
||||
"text": "Okay, so I was thinking that we want to increase word of mouth, and stickers are a great way to do it. We also have our Easter egg. Um, logos, that would be great to… sell as stickers, so I added the option next to the logo when you click it to be able to buy the stickers on desktop and mobile. Or $2, so… That's my hack days project. Valent, you're next."
|
||||
},
|
||||
{
|
||||
"time": "21:44:35",
|
||||
"speaker": "Balint Farkas",
|
||||
"text": "Hey, folks. So I'm working on the DuckDuckGo Chromium browser, also known as Duckium. We use Agentic workflows all the time, and it can, of course, see the code, but it cannot see the internals of the browser. So it can see the code, it can drive the browser via Chromium DevTools protocol, but it cannot see our own services like Sync. pixels, burn, feature flags, and so on. So I've exposed them to AI. You can just connect to the browser from your own AI terminal and then ask stuff, for example, why can't I see sync and backup in the menu? It should be here. The answer is because the feature flag in this live session isn't on. Or you can ask spicier stuff, such as performance search for I love cats, which it can do via Chromium DevTools protocol, and observe what pixels have been fired, which comes from the internals observation that I just added. And you can correlate these things and observe the browser's behavior as it happens, which will enable us more sophisticated debugging scenarios, and what's more important, more sophisticated Agentic workflows. That's my first thing. And the second thing is for Mark Sabu, who is out currently, and I'm sharing his video in a second."
|
||||
},
|
||||
{
|
||||
"time": "21:45:52",
|
||||
"speaker": "Andrea Soto",
|
||||
"text": "Thank you."
|
||||
},
|
||||
{
|
||||
"time": "21:46:02",
|
||||
"speaker": "Balint Farkas",
|
||||
"text": "Should be running. Hey folks! I'll walk you through the life of a Windows Release DRI in the next two minutes. After the last quick one days, we iterated on the design together with the release team, and I spent the last two days building it. The Windows Release Command Center. Until now, all of this was manual. We kept Asana and GitHub Actions in sync."
|
||||
},
|
||||
{
|
||||
"time": "21:46:10",
|
||||
"speaker": "Andrea Soto",
|
||||
"text": "Ooh."
|
||||
},
|
||||
{
|
||||
"time": "21:46:22",
|
||||
"speaker": "Balint Farkas",
|
||||
"text": "and dispatch every workflow by hand. Now the ODRI can check the state at a glance, and the release DRI can get through their duties by following the steps in the app. This is the state of every channel, which build is where, and at what rollout percentage. It all comes live from Asana. No more opening 5 tasks and 3 workflow pages to figure out where we are. The calendar shows what's coming up, branch cuts, rollout steps, so nobody gets surprised by a deadline. Clicking the release opens the DRI view. It shows the next section and flags anything that needs attention. Say we want to take 177 to 100% stable. I click this button and it dispatches the workflow. Because it's at 100%, the app asked me to follow these steps and upload it to the Microsoft Store. But I'm actually the DRI of 176, and I will need to do a hotfix. Hotfixing used to be the most manual part. Now I just pick from develop. Like PES, a PR that needs to be hotfixed. and just displays the bot with creation, which will actually just do this. I already done that to not block the demo. Umm. So I will need to upload the release notes. It loads the release notes automatically. So I can just approve it and upload. And now that it's done, I can just go back and simply follow the remaining steps to finish the release. And obviously, every flow syncs back into Asana, so the runbook still works if the app is down. That was Release Command Center. I hope it makes release weeks a little calmer and gives every DRI back some time for actual work. Oh, and sorry about the editing. I'm a dev, so this video was shipped as an MVP. Thanks, Odo! That's it for me."
|
||||
},
|
||||
{
|
||||
"time": "21:48:10",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, hey. Hey, everyone. This is me, Alex. There are so many new faces. I'm pretty sure some of you have no idea who I am. Which is fine, sometimes I'm not entirely sure myself. I'm Alex, from the Apple team, working on our macOS browser. And I thought I'd make it greater again. What would you expect from a macOS browser? During this hack… in the hack days. They say Julius was a hacker, performing live demos, chewing water into wine, accepting some cookies. Not bad for a hack days project, right? All right. Showtime. Could you please stop sharing?"
|
||||
},
|
||||
{
|
||||
"time": "21:48:55",
|
||||
"speaker": "Mark Ingram",
|
||||
"text": "Thank you, Alan."
|
||||
},
|
||||
{
|
||||
"time": "21:48:56",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Got it."
|
||||
},
|
||||
{
|
||||
"time": "21:48:57",
|
||||
"speaker": "Balint Farkas",
|
||||
"text": "Yeah, yeah, yeah, I'm trying, uh…"
|
||||
},
|
||||
{
|
||||
"time": "21:48:59",
|
||||
"speaker": "Julia Abreu",
|
||||
"text": "It's a very…"
|
||||
},
|
||||
{
|
||||
"time": "21:49:03",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah. Okay, first try failed miserably. Let's try again. Yeah, Kira. Hello. I hope you can hear the sound. Yeah, hope you can hear the sound. But seriously. What's happening to the world? AI is everywhere, too much information, too much liquid glass and beige. Sometimes I just want to burn it all down. Like this. Yeah, much better. Let's do it again. Where shall we start now? Sometimes I just want to run away back to something familiar. Or maybe look for some happiness. Or maybe I just need to talk to somebody. Yeah, maybe the problem isn't the internet. Maybe it's just how we see it. I wish I could change the whole settings of my life. how it appears. What if we could go back? Somewhere like this. And buttons look like buttons. Windows look like windows. Smells like Christmas morning, hot chocolate and mandarins, back when everybody was still around. Remember, on the websites. had some personality. When every page told you someone had paid attention to it. And speaking of the little things… You see? Even the tooltip. Respect your personal space. Your privacy. You just need to start and ask for some help. Here we are. Your protection, your privacy, your peace of mind. Thank you. That's all from me."
|
||||
},
|
||||
{
|
||||
"time": "21:50:57",
|
||||
"speaker": "Deepak",
|
||||
"text": "I'll go next. Let's add the photo. Cool. Clearing my screen… What? I didn't work. Trying again. Okay. Can you all see my screen now?"
|
||||
},
|
||||
{
|
||||
"time": "21:51:30",
|
||||
"speaker": "John Boileau",
|
||||
"text": "Yep."
|
||||
},
|
||||
{
|
||||
"time": "21:51:31",
|
||||
"speaker": "Julia Abreu",
|
||||
"text": "We can see it."
|
||||
},
|
||||
{
|
||||
"time": "21:51:32",
|
||||
"speaker": "Deepak",
|
||||
"text": "Okay. Cool. Playing a video, if you can't hear the audio, please. DuckyEye can generate a lot of great images, but only if you know exactly what to promote. ChatGPT, Gemini, and other tools have solved this with pre-existing templates for images, which has also led to a lot of virality for them. Well, now we have them too. If you go to new images, we have 15 of these different templates ranging from anime to 80s portraits to caricatures. Clicking on any of them populates the input field with the corresponding prompt. Some of them require you to upload a reference image, which is indicated by this icon, and then a user is notified to do that with this tooltip. I already did this one. So if you look at this, this was the reference image and I think it did a pretty good job. We also prompt the user to try more styles, so they can click on any of the, uh, styles, and then the original image gets, uh, pre-filled here with the. Uh, a defense bill. Another thing that really irked me was that after all of these images were generated, they were scattered across charts, and there was no one place to see them. Well, now we have this My Images tab. where you can see all of the different images that we have generated. You can delete one or all of them from here, and you can also go to the chart, where. they were generated, or use them as a reference for your next image. One cool thing that we do here is, if you do delete this image, then in the original conversation, where this was generated, we have this image deleted placeholder here, so that the continuity of the chat is not lost. That's it. Thank you. Yeah, that's it. Thank you."
|
||||
},
|
||||
{
|
||||
"time": "21:53:20",
|
||||
"speaker": "DR",
|
||||
"text": "All right, so I go next. Let me see. Here. Can you see the screen? All right. So, uh, starting next Monday, our internal release, actually internal users, uh, in the internal release, will have, uh, the possibility of installing from the web, uh, Chrome Web Store 1Password. And this video showcases how it works, that it connects to the desktop app that you have installed. You can see that it works for registering your email and autofilling your password for it. You have to unlock it first, though. You can see here how it works with Touch ID. Um… You can fill the login, password. Then it's going to ask you to save it. You can also, of course, use it to log in to a site, those details. So you guys see here. Then it also works for passkeys, where you can register a passkey for one of the accounts that you already have in 1Password. Um… Again, it's going to probably ask for authentication. And then use that same passkey. To log into the site. In this example, it didn't ask for additional authentication because it was so close to the previous one, but it's working quite nicely. And we'll be posting an announcement with details on how you can provide feedback for this. I said it's quite complicated on the technical side. Thank you. Hold on."
|
||||
},
|
||||
{
|
||||
"time": "21:54:58",
|
||||
"speaker": "AO",
|
||||
"text": "Hey, Elle. This is a demo that Alex, Elle, and I did. So double Alex demo. or DACAI artifacts. Hey everyone! During Hack Days, we explored DACAI artifacts. Documents, presentations, and visuals. But you know what? It's boring, so here's the twist. This presentation was built entirely in DACAI. See? It's right here, inside the chat. And you know what? I can even download it as a PowerPoint file. Now check this out. Let's ask how much I could save. I get an answer, but only for this one case. Different numbers, we need to try again. Or I can get an app that does that for me. Duck AI builds it right here, next to the chat. You can watch it come together. Not a code block, not a screenshot, a real working app. Now I can change the amount, the time, the rate, and it updates instantly. Have a PDF? You can turn it into just about anything. Study notes, a brief, key takeaways, whatever you need, as a document. You have full control over your doc and markdown. You can also let Duck AI rework it. When you are done editing, you can now export your doc. With Artifacts, you can build your own website too. If you want something different, you can just point DuckAI at it and ask for an edit. Every version is saved, so if you don't like your change, you can go back in one click. Artifacts also work well with our browser features. Let's say I have a really long article, and absolutely no desire to read all of it. Attach the top, and Dakia will summarize the main takeaways visually. Just a few seconds, and it's ready, clear, structured, and much easier to understand. And of course, artifacts work great on mobile too. Try them yourself! That's it. Thank you."
|
||||
},
|
||||
{
|
||||
"time": "21:57:18",
|
||||
"speaker": "Gary K",
|
||||
"text": "All right, I'm up. Let me share with sound. a video… Here we go. Any time there is an incident, the first question is always, what changed? And the answer is potentially in a lot of different places. So I've created a command line tool that will aggregate the events that are likely to be interesting for anyone investigating new behavior. What changed is a tool that can access Azure activity logs, Asana deployment plans, Jenkins jobs, GitHub pull requests and actions, REX commands, and Mattermost notifications. Because there can be a lot of data in these sources, the tool ships with default settings that are designed to give high signal-to-noise ratio. These settings can be overwritten via a config file. or a runtime flag. Users can search backwards from now or over a specific window of time, from minutes to days. There are a host of flags designed to make it easy to use. Users can opt in to format the output as JSON and perform further filtering. and transformations using JQ. What changed uses your own credentials, so security posture is maintained. What Changed is available now at www.duckduckgo.com/gcurtis/whatchanged. Thank you. Like and subscribe for more great content. Thank you."
|
||||
},
|
||||
{
|
||||
"time": "21:58:52",
|
||||
"speaker": "Tom Strba",
|
||||
"text": "Nice. Hey everyone. So over the last couple of weeks in OJ and OM, we have been trying to build tools for Duck AI. What does it mean? We would like Duck AI to be able to get context automatically from your browser. And not only that, we would like to. Duck AI to be able to control the browser. So, during hack days, I tried to put all the pieces together, and uh… I would like to show you a proof of concept that I managed to build, so… Let's say I have, uh… Couple of, uh… shoes I am trying to buy. And I would like Duck AI to recommend me which shoes should I buy. So… I will ask you. Which shoes should I buy from all these options? And I'm not providing more context. It will basically get the list of my tabs. It will read the content and it will recommend me, oh, this is the best for speed for daily trainer. whatever but this is not where the fun ends this is where the fun starts so how about now we ask Duck AI. to buy our choice. So for example, buy me stride arrow three. And Duck AI will basically open a new tab and start buying shoes for me. As you can see, here is the store and it's starting to fill the form and it doesn't know which. shoe size it should buy, so it asks me. I will just respond, for example. 10, and it now reads the form. As you can see, it filled. The 10, and now there is a… the website needs the address. So the fun part is that we already have the identity in the browser. So Dakia asks me, hey, can I use this identity from the browser to fill it? And yes, of course, let's share it. If we take a look at the store… by the way, this is the store I built for myself for testing. The address is now filled. and it asks me, it asks me last time, hey, how about, uh, I'm gonna, I'm gonna submit the form, are you, are you sure? Yes. I am sure. And my shoes are now ordered. I didn't need to click on that website. I just wanted you to see what is happening in the background. But Duck AI now or soon will be able to buy. stuff for you or do anything in the browser you want it to do. Uh, that's the first demo I wanted to show you. And the second one, this one will be really quick, and it's, like, internal tool enhancement. Uh, if you… Often test a Mac. make ship reviews, you know the process. You need to download the DMG, attach it manually. Then drag and drop it. The instance is running, so you need to quit it. Then drag and drop again, wait for installation and then run it. So I build the button and now you will just click to run and you can start reading the. ship review, and everything will happen in the background, and after the build is downloaded, I'm gonna speed this up a little bit, it will basically just runs, and you can start testing. Um, that's it for me, thank you."
|
||||
},
|
||||
{
|
||||
"time": "22:02:22",
|
||||
"speaker": "I(",
|
||||
"text": "All right. I'm just getting my screen up. Please let me know if you can see it. All right, looks like it's there. All right. So as a user, why should I care about the protections report on our browser? It's a list of numbers and icons. What is the actual benefit? So I reworked it. I started with the bottom line. Companies are watching you. It's creepy. Also highlighted right away that there's an issue to be fixed. Privacy isn't your default, and here's why that matters. The more of your everyday browsing happens in our app, the less these companies get to see. So let's expand this. Immediately, we get a creepy, interactive, prying eye that follows your cursor around. And we get useful info. We block tracking attempts, but why? They target you with ads, they watch what you read, and they record what you click. It's creepy. So who's watching? Well, Google does a lot of spying, and it was on 4 out of the 5 sites he visited. And Facebook was on almost half. Again. It's really creepy. So I wondered how we could make this more like a personal infographic. Here we highlight the nosiest site of the week, and we show a ring of trackers from that site that blink like eyes to drive home the visceral idea that you're being watched. Now, we empower you to understand some of what we're doing by showing you how we prevent a digital fingerprint view from being created. You can hover over each component of the fingerprint and see what we've hid from creepy companies. And how many times? And finally, we contrast this with Chrome. Where companies swarm around your cursor, and cookie pops and ads fill the screen. We drive home the fact that Chrome is owned by Google, and that unlike on Chrome, DuckDuckGo blocks Google's tracking attempts. So maybe this really creeped you out. Why are so many companies watching you read the news? Let's share that. And just like that, a promotional infographic can be shared with a link to download our browser. So try it out for yourself on Windows on the link task. Thanks."
|
||||
},
|
||||
{
|
||||
"time": "22:04:41",
|
||||
"speaker": "Vinay Nadig",
|
||||
"text": "All right, that's me next. Let me share my screen. Alright, so for hack days, I have. built an app called, QuackTime. What it does is, it lets you schedule ad hoc meetings, through Mattermost without having to do the whole song and dance of matching time zones across. uh, different geographies. So, to use that, go to QuackTime, go to Metamost, or any DM, QuackTime and DM duration, in this case 60 minutes, and then we'll set a type build. You will get a link, you can open it. you will end up on this interface, basically. You will see that all your, uh… uh, working hours and free, uh, slots through Outlook has already been filled in. And that would be the same case for another person as well. So, the other person will also open the same link. And yeah, so you can see that I'm working with Adrian, so I have this much overlap with him, so you can select whichever task that you want. And, oh, sorry. You can propose it. And the other person will… See an option to accept that. And once you accept it, an invite will be sent automatically at the correct time, along with the Zoom link for… which uses your personal Zoom link. That's pretty much it. I'll stop there."
|
||||
},
|
||||
{
|
||||
"time": "22:06:17",
|
||||
"speaker": "Nicklas Jensen",
|
||||
"text": "All right, I'm next up here, and I am going to be sharing some porn. out of a conversation, actually, in a Zoom chat. So, one of the things on the meetup that happened was that we, uh… At least for a lot of the ducklings, we were freaking out about how much merch and how many things have been over the years. So the idea was to create a hall of fame for specifically T-shirts. So Miguel and I worked on that. For this, uh… For these hack days, the goal is you have a timeline, you can see all of the different designs that have been over the years. These are all the ones that Miguel could get a hold of so far. You can vote for your favorite ones. And also, if you don't feel like going through them all manually, you can just… pick out of sort of a random generated thing. And yeah, that's the T-shirt Hall of Fame. How do I stop sharing? Thank you."
|
||||
},
|
||||
{
|
||||
"time": "22:07:30",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "All right, here's a demo of the… Long overdue feature on… macOS, which is the reader mode. Um… Reader mode. extracts text from websites. And here you can see that, uh, we're navigating to a website that, uh, is eligible for being displayed in reader mode, which contains relatively more text, uh, and, um… Just with a single button in the address bar, um… we turn on the reader mode, then we navigate away from that website, it just resets to a regular view. here, uh, you can see, uh, visiting another website, uh, that's also eligible for reader mode, and here's, uh, here's how it works, but it's not all, because I've worked on that, uh, during Hug Days, but. Um… a parallel to my work, actually. Marios was doing the same thing for iOS, so here it is, um… Here, the reader mode, uh… Button is in the website, uh… menu… And this demo will also show you that it respects the browser theme. So that, um… shows correctly in the dark theme as well. Even if you visit a website that… uh, doesn't honor the system theme, uh, then the reader mode, of course, uh, will be dark in this case, when the Guardian was in, uh, in light theme. Yeah, and this all was possible. to do thanks to a library by Meek that extracts. text from, from websites. So really the integration. It was fairly minimal here, and it was just a bit of work. That's why I said it was long overdue, because that library was published a few months ago already. That's it. Thank you."
|
||||
},
|
||||
{
|
||||
"time": "22:10:01",
|
||||
"speaker": "Valerie Kraucunas",
|
||||
"text": "Alrighty, hello. Um, so, I'm Valerie. I work on the front-end team. Um, the thing I've been really heavily focused on all year is the rebrand, and that… with that has come… turning over, uh, style values from one… one way to a new way. Um… with that, we have these things called design tokens, which is basically, like, a codified design decision. And so, when we're styling… the new rebranded stuff we're using, or at least we want to be using all of these things. That said, um, a lot of times when you are handed designs that are rebranded. You end up with this scenario of… It'll be a mix of using the new style tokens and the old style tokens. So in this case, like the SDS styles are a legacy thing. Um, and I want to be very clear, this is not a shame. This is not a shame campaign or anything on designers, because oftentimes when they are building these things, they are… they have the old way in the same file as the. new way. And so it's really, really tedious to get down into every single nook and cranny and node or layer to make sure that you're using the new styles on everything and to make it even more complicated. So when developers see this, we just see this and we're like, why is this still here? Why are we still using SDS things? But when you get over into the design look, so this first column is when they're picking the first padding value, so space X07. When they're picking the second column value, space X03. They look the same. It's really easy to co-mingle the old style and the new. And so, um, basically my concept is to… be able to hand a Claude skill a Figma link, and have it go and traverse the entire. All child nodes of that, um… of whatever you linked over. So. I'm going to try this. I doubt it will… I doubt it'll work. It does not go as fast as I would like it to, but we'll give it a go. So, basically, what happens is you, you know, invoke it with the Figma link, then you give it an Asana link. And give it a name. Um… What that ends up spitting out is a nice report for designers to be able to go and update all the things that are using, uh, old values, or possibly things that are just out of system. As well, um, now I want to be clear, I'm standing on the shoulders of giants here, because, um, while we've been doing the SERP rebrand, uh, my partner in crime, Rachel Lim, created a… skill called Marlin Rebrando, which is basically a dictionary of, uh, knowledge for this was the old way, this is the new way, these are the things we should be checking for when we are executing the rebrand and the code. Um, so my skill is heavily relying on that, but, um… What it'll basically do is it will just… fully traverse like a node tree, if you will, all the way down. Um… And yeah, the things that we're looking for are the use of legacy variables. This is run from within the DDG. repo, for now, at least. So what it will do also is it'll look at the currently installed design token package and make sure that there aren't values being used in the designs that don't exist in. the installed package, then also looking for just colors that aren't tied to a system value, unselled text, et cetera. So what this ends up doing is it will create a. design token report, and. give the designers a link to the layer that. his, uh… has a property on it that's a problem, if you will, and then give it an idea of, like, this is an unexpected value, and then has an expected or a suggested value. The nice part about this as well is that developers. don't necessarily have to wait on designers to go. What?"
|
||||
},
|
||||
{
|
||||
"time": "22:14:28",
|
||||
"speaker": "Julia Abreu",
|
||||
"text": "Well… I'm so sorry, I hate to do it, but I have to interrupt you, because we're at 4 minutes now."
|
||||
},
|
||||
{
|
||||
"time": "22:14:35",
|
||||
"speaker": "Valerie Kraucunas",
|
||||
"text": "Oh, shoot, I'm so sorry. Okay, well…"
|
||||
},
|
||||
{
|
||||
"time": "22:14:36",
|
||||
"speaker": "Julia Abreu",
|
||||
"text": "Sorry."
|
||||
},
|
||||
{
|
||||
"time": "22:14:38",
|
||||
"speaker": "Valerie Kraucunas",
|
||||
"text": "Making everybody's life better, that's all."
|
||||
},
|
||||
{
|
||||
"time": "22:14:50",
|
||||
"speaker": "Stano",
|
||||
"text": "Okay, I believe I was next. Um, I'm gonna… I hope you can see my screen now. Someone please confirm."
|
||||
},
|
||||
{
|
||||
"time": "22:15:00",
|
||||
"speaker": "Julia Abreu",
|
||||
"text": "No, we cannot."
|
||||
},
|
||||
{
|
||||
"time": "22:15:01",
|
||||
"speaker": "Jason Ashby",
|
||||
"text": "Nope."
|
||||
},
|
||||
{
|
||||
"time": "22:15:02",
|
||||
"speaker": "Stano",
|
||||
"text": "You cannot? Let me try again. Where is… The sun got stuck."
|
||||
},
|
||||
{
|
||||
"time": "22:15:24",
|
||||
"speaker": "Julia Abreu",
|
||||
"text": "Did you find the share button?"
|
||||
},
|
||||
{
|
||||
"time": "22:15:27",
|
||||
"speaker": "Stano",
|
||||
"text": "Give me a sec, I reconnected. You can take it out of my budget, I'll make it quick. It does not want to work. You can skip me. Go on."
|
||||
},
|
||||
{
|
||||
"time": "22:15:45",
|
||||
"speaker": "Anh Do",
|
||||
"text": "Okay, looks like I'm next. So let me try to share my screen. Wow. Uh, how do I share, like, a… Particular windows, um… Sorry, um, I had so many windows opening at the moment. Oh, come on. Guys, it is not fun. Sorry. OK, I'm going to share my desktop then. One sec. Hopefully, you can see that on my screen. Can anyone see it? Okay. So for context, in OK, we are helping people in the US to remove personal information from data broker by submitting our request on their."
|
||||
},
|
||||
{
|
||||
"time": "22:16:21",
|
||||
"speaker": "Julia Abreu",
|
||||
"text": "I can see it."
|
||||
},
|
||||
{
|
||||
"time": "22:16:33",
|
||||
"speaker": "Anh Do",
|
||||
"text": "behalf. But recently, we have a lot of issues with broker block our archive with CloudFlare and CAPTCHA, so we can submit the form for the users. So this demo has been built based on Ben Smith design prototype. Let me play that."
|
||||
}
|
||||
]
|
||||
}
|
||||
+47
@@ -15,3 +15,50 @@ source: "https://us01mynotes.zoom.us/bPprGg5DTye9H-RQXkwMuw"
|
||||
- **21:29:37 · John Boileau:** And this way.
|
||||
- **21:30:59 · Gabriel Weinberg:** Hello, everybody. We have a few quick updates that we're going to mainly do the Hack Day's showcase today that Julia's leading. Everyday AI Guild. That's Zac. Okay. Yeah, there it is. All right. Yeah.
|
||||
- **21:31:17 · Zach:** Yep. Uh, yeah, sorry. Um, yeah, so just quick announcement there. Uh, Julio's moving to the, uh, DRI for that, um, and Mario is going to be, uh, the secondary. Um, so they've both been pretty heavily involved in, uh, that process, and we're excited for this transition.
|
||||
- **21:31:40 · Josh Frank:** I believe I'm next. So hey, everybody. I'm taking a quick break from the gym where you can frequently find me to tell you about random access learning. Just put the link in the chat. We have a session Thursday next week. 12:00 PM Eastern time, I think that's US Eastern, on corporate sustainability and being carbon negative in the AI era. So please, everybody, come to that if you can.
|
||||
- **21:32:17 · AC:** Everybody Ă last week we had our away mobile browser experience. Assessment our goals days a same they car our Browser mobile, browser experience from good to great in the previous cycle. We ship the android. And dialog.
|
||||
- **21:32:55 · AC:** Internal the keyboard now always on the new tape. Device to device migration. We want to ship this before black friday. A ui that s case for split. Screen. And we want to what support for many bar. We are going to start also the new tupage experiment for new users. And they think next these mark.
|
||||
- **21:34:04 · Mark Ingram:** Hey, everyone. I'm Mark from OL, the Desktop Browsers Objective. Some exciting news this week is Ivy is taking over as the ODRI, and I'll be moving on to the advisor role. I'll keep it short because I know we're on hack days this week, but I also, just before introing Ivy, I want to announce my new midlife crisis to everybody, which is. I decided to start learning the drums, and I can see Carl's excited face on the screen. Okay, that's my midlife crisis update. Over. Ivy, do you want to say hi?
|
||||
- **21:34:31 · I(:** Yeah, I'm just really excited to take over OL, and stay tuned for some exciting news about extensions on macOS coming really soon.
|
||||
- **21:34:43 · Julia Abreu:** All right. Congrats, Ivy. That's exciting. So I'm kicking us off today. I'm going to actually share my whole screen because I'm going to be moving from one side to the other. So I have two demos today. So we have the Julia special, two demos. Um, my first demo is… since the meetup, I've been thinking about how, um… We need to, like, I've been thinking about the new objectives that we have about word of mouth and how we talk about DuckDuckGo and how, especially for ducklings, is hard to answer some of the questions that we get once you first join DuckDuckGo. So I wanted to create something that helps them answer those questions and understand our products better. So I do want to shout out Ben Smith because he created this. I just basically said the idea. Um, so this is an artifact, um, and you will see the different tabs here, so you have different questions per tab. Um, and then you have the specific questions here, which you can click on and see them in writing. Or, if you want to, you can actually listen to it as. kind of like a podcast episode. Um, so… let me know if you can actually hear this. I'm just gonna play a couple of seconds. Episode 1. The Big Picture. Last week, a friend of mine looked up, is it normal for your knee to click? Just once. For the next week, every website they visited tried to sell them knee supports, walking sticks, and one of those… So you get the gist of it. I hope you got to hear that. Um, so this is still a work in progress. We're going to be creating this content. Um, I really didn't want to… to be in audio, because I feel like if you get that in writing, it's different explaining as a human. So, this is what we're building. And then, the second thing I'm building… dang, the Zoom… The Zoom thing doesn't let me go to the other one. Okay, here. So this is the second thing that I built. This is coming from feedback from people who went on leave, which was around how to catch up with everything that had been happening since they were gone. Um, so this is a how… what do you miss? Uh, so basically, you add here the date you started your leave, and then the start of the date you return. Um, you click catch me up. Uh, it takes a couple of seconds, but it basically gives you, like, a summary of a bunch of things that happened while you were out. So, um… company-wide posts, uh, what was published, what was answered in odds and ends, so all the Q&A, which objectives are up-to-date, like, which assessment was the last thing, and what we're working on right now, uh, things that were shipped, uh, also, like, new AORs, retired AORs, so here, as you can see, like, one, um, sample of, like, the announcements. It gives you just, like, a summary of all the announcements. Um, and we also have a people tab, so, like, new hires, which teams they are in, uh, people who left, and then it also shows you, um, green bow ties, spotlights, in case you want to catch up with all the spotlights that were posted that. Um, the time you were away. I do want to add a tab for specifically functional team updates, so, like, if there's a new process or anything specific to the functional team, I'm just not sure yet where to get that information from. Um, so… working on that. If you have suggestions, or if you would like to be… try out these things, let me know. I would love the feedback. Um, and now, this is it for my demos. Now I have a demo by, um, Robert, who couldn't be here. So, also, please ping me if you can't, uh, hear this. Hello, hello, hello. I worked on three hacks this time around. I'll try to get through it all quickly. The first is to do with increasing Duck AI prompts. I thought that maybe a nice way to do that would be to add a bit of discoverability into our browser. So if you are looking at a foreign language page, then you get a suggestion to translate it. Can someone, uh, unmute themselves and just let me know if you can hear this? Because I'm, like, concerned because I can't see that. Okay, thank you.
|
||||
- **21:38:59 · Anne Hildebrand:** Yes.
|
||||
- **21:38:59 · Zaahir Moolla:** We can hear.
|
||||
- **21:39:02 · Julia Abreu:** And, um, so yep, that sends the page content off into Duck AI and translates it. We already had this feature, but, you know, just adding the prompt up there. That works. And there's lots of… this is very exploratory. There's lots of different ideas along these lines that we could look into, such as, if it's a long article, maybe we, um, tell the user how long it'll take and prompt to summarize, or on a shopping page, we could prompt them to, um, compare. Uh, the cool thing is that these suggestions here, these three options, that's all generated by our local LLM, so it's completely private. Um, nothing's, uh, hitting our servers until you click on one of those. Um, most recipes too. And this is a cool one, if you, um, are looking at an event, you can ask DuckAI to compute the event details. And I added this, um… dynamic UI, this card at the bottom of the Doug AI answer, and it gives you a button to add it to your calendar. Uh, one cool idea is, if you're looking at a privacy page, it could offer to help the user understand what it is they're agreeing to, so very within our brand. And another cool idea, just because YouTube features always seem to perform really well for us, is we could, um, prompt the user to, uh, do things using the transcript that appears in YouTube here. So this actually extracts the transcript from this panel. And it can send it to DocAI. Okay. Hack number two is, um, fixing a personal frustration of mine. So, I'm a Raycast user, and I'm always doing things like… um, converting currencies and, like, complex queries like this. And, uh, it frustrates me to no end that, um, that doesn't work when you plug it into DuckDuckGo. And so what I did is I had Claude reverse engineer the raycast calculator, and I've plopped that into SERP, and so now you can, um, jump into SERP running on this test machine, and do complex queries like that. And there's all sorts of things you can do. Mixed currencies is kind of cool. Um, one thing I use a lot is, like. Adding different units. And there's also, like, sort of… Complex math bits that are kind of fun. And the way that I handled this in the UI is that —. The simple calculator stays if you're doing a simple expression. And same if you're just doing a regular. conversion, then we get the existing UI for that too, because it's nicer since it has the dropdowns. Okay, and my third hack is yet another frustration that I've had for a while. So here we are looking at my phone. Oops. And, um, so we've always been able to switch tabs by swiping on the address bar at the bottom there, and that is quite nice. But what we haven't been able to do is swipe up to go to the tab switcher. And so I added that, and it turns out that Bartosz had already been working on this, so he has helped me a lot with this. Thank you very much. And yeah, it's really nice that you can… it tracks your finger, so you can kind of drag out halfway. Real smooth. And Bartosz added, you can drag out halfway and swipe to the right. Those are my hacks. Thank you very much. All right, and we're not done yet. I have another one by Pablo. When people want their data on another device they don't go looking for things and sync it back up doesn't really tell them what it does. Chanel's usability insight report made that very clear. And the problem is getting bigger. Zac AI chats, uh, can easily be lost. Um, the more stuff we add to Zac AI, um, the more. things that are worth keeping, Sink and Backup will just not be enough. So, we are proposing MyTacticGo, a private account. It's private because it's from us, and it needs no personal data to sign in, so no email and no password to remember. It is encrypted, your data is backed up, unsynced, and we show what's ready to go, like 100 passwords or 244 bookmarks, so the value is very concrete. On desktop, MyTacticGo lives in the toolbar, where people actually look. It lists what will be synced, like your chats and passwords and bookmarks, but it also brings your subscription. So, this can become, actually, your home base, and it shows your plan and your connected devices, so it is a great opportunity for… for dependability, um, and cross-promoting other… other features and understanding our… our ecosystem. All in one place. That's it for me, and I think we're. It's Andrea next.
|
||||
- **21:44:01 · Andrea Soto:** Okay, so I was thinking that we want to increase word of mouth, and stickers are a great way to do it. We also have our Easter egg. Um, logos, that would be great to… sell as stickers, so I added the option next to the logo when you click it to be able to buy the stickers on desktop and mobile. Or $2, so… That's my hack days project. Valent, you're next.
|
||||
- **21:44:35 · Balint Farkas:** Hey, folks. So I'm working on the DuckDuckGo Chromium browser, also known as Duckium. We use Agentic workflows all the time, and it can, of course, see the code, but it cannot see the internals of the browser. So it can see the code, it can drive the browser via Chromium DevTools protocol, but it cannot see our own services like Sync. pixels, burn, feature flags, and so on. So I've exposed them to AI. You can just connect to the browser from your own AI terminal and then ask stuff, for example, why can't I see sync and backup in the menu? It should be here. The answer is because the feature flag in this live session isn't on. Or you can ask spicier stuff, such as performance search for I love cats, which it can do via Chromium DevTools protocol, and observe what pixels have been fired, which comes from the internals observation that I just added. And you can correlate these things and observe the browser's behavior as it happens, which will enable us more sophisticated debugging scenarios, and what's more important, more sophisticated Agentic workflows. That's my first thing. And the second thing is for Mark Sabu, who is out currently, and I'm sharing his video in a second.
|
||||
- **21:45:52 · Andrea Soto:** Thank you.
|
||||
- **21:46:02 · Balint Farkas:** Should be running. Hey folks! I'll walk you through the life of a Windows Release DRI in the next two minutes. After the last quick one days, we iterated on the design together with the release team, and I spent the last two days building it. The Windows Release Command Center. Until now, all of this was manual. We kept Asana and GitHub Actions in sync.
|
||||
- **21:46:10 · Andrea Soto:** Ooh.
|
||||
- **21:46:22 · Balint Farkas:** and dispatch every workflow by hand. Now the ODRI can check the state at a glance, and the release DRI can get through their duties by following the steps in the app. This is the state of every channel, which build is where, and at what rollout percentage. It all comes live from Asana. No more opening 5 tasks and 3 workflow pages to figure out where we are. The calendar shows what's coming up, branch cuts, rollout steps, so nobody gets surprised by a deadline. Clicking the release opens the DRI view. It shows the next section and flags anything that needs attention. Say we want to take 177 to 100% stable. I click this button and it dispatches the workflow. Because it's at 100%, the app asked me to follow these steps and upload it to the Microsoft Store. But I'm actually the DRI of 176, and I will need to do a hotfix. Hotfixing used to be the most manual part. Now I just pick from develop. Like PES, a PR that needs to be hotfixed. and just displays the bot with creation, which will actually just do this. I already done that to not block the demo. Umm. So I will need to upload the release notes. It loads the release notes automatically. So I can just approve it and upload. And now that it's done, I can just go back and simply follow the remaining steps to finish the release. And obviously, every flow syncs back into Asana, so the runbook still works if the app is down. That was Release Command Center. I hope it makes release weeks a little calmer and gives every DRI back some time for actual work. Oh, and sorry about the editing. I'm a dev, so this video was shipped as an MVP. Thanks, Odo! That's it for me.
|
||||
- **21:48:10 · Alex Martemyanov:** Yeah, hey. Hey, everyone. This is me, Alex. There are so many new faces. I'm pretty sure some of you have no idea who I am. Which is fine, sometimes I'm not entirely sure myself. I'm Alex, from the Apple team, working on our macOS browser. And I thought I'd make it greater again. What would you expect from a macOS browser? During this hack… in the hack days. They say Julius was a hacker, performing live demos, chewing water into wine, accepting some cookies. Not bad for a hack days project, right? All right. Showtime. Could you please stop sharing?
|
||||
- **21:48:55 · Mark Ingram:** Thank you, Alan.
|
||||
- **21:48:56 · Alex Martemyanov:** Got it.
|
||||
- **21:48:57 · Balint Farkas:** Yeah, yeah, yeah, I'm trying, uh…
|
||||
- **21:48:59 · Julia Abreu:** It's a very…
|
||||
- **21:49:03 · Alex Martemyanov:** Yeah. Okay, first try failed miserably. Let's try again. Yeah, Kira. Hello. I hope you can hear the sound. Yeah, hope you can hear the sound. But seriously. What's happening to the world? AI is everywhere, too much information, too much liquid glass and beige. Sometimes I just want to burn it all down. Like this. Yeah, much better. Let's do it again. Where shall we start now? Sometimes I just want to run away back to something familiar. Or maybe look for some happiness. Or maybe I just need to talk to somebody. Yeah, maybe the problem isn't the internet. Maybe it's just how we see it. I wish I could change the whole settings of my life. how it appears. What if we could go back? Somewhere like this. And buttons look like buttons. Windows look like windows. Smells like Christmas morning, hot chocolate and mandarins, back when everybody was still around. Remember, on the websites. had some personality. When every page told you someone had paid attention to it. And speaking of the little things… You see? Even the tooltip. Respect your personal space. Your privacy. You just need to start and ask for some help. Here we are. Your protection, your privacy, your peace of mind. Thank you. That's all from me.
|
||||
- **21:50:57 · Deepak:** I'll go next. Let's add the photo. Cool. Clearing my screen… What? I didn't work. Trying again. Okay. Can you all see my screen now?
|
||||
- **21:51:30 · John Boileau:** Yep.
|
||||
- **21:51:31 · Julia Abreu:** We can see it.
|
||||
- **21:51:32 · Deepak:** Okay. Cool. Playing a video, if you can't hear the audio, please. DuckyEye can generate a lot of great images, but only if you know exactly what to promote. ChatGPT, Gemini, and other tools have solved this with pre-existing templates for images, which has also led to a lot of virality for them. Well, now we have them too. If you go to new images, we have 15 of these different templates ranging from anime to 80s portraits to caricatures. Clicking on any of them populates the input field with the corresponding prompt. Some of them require you to upload a reference image, which is indicated by this icon, and then a user is notified to do that with this tooltip. I already did this one. So if you look at this, this was the reference image and I think it did a pretty good job. We also prompt the user to try more styles, so they can click on any of the, uh, styles, and then the original image gets, uh, pre-filled here with the. Uh, a defense bill. Another thing that really irked me was that after all of these images were generated, they were scattered across charts, and there was no one place to see them. Well, now we have this My Images tab. where you can see all of the different images that we have generated. You can delete one or all of them from here, and you can also go to the chart, where. they were generated, or use them as a reference for your next image. One cool thing that we do here is, if you do delete this image, then in the original conversation, where this was generated, we have this image deleted placeholder here, so that the continuity of the chat is not lost. That's it. Thank you. Yeah, that's it. Thank you.
|
||||
- **21:53:20 · DR:** All right, so I go next. Let me see. Here. Can you see the screen? All right. So, uh, starting next Monday, our internal release, actually internal users, uh, in the internal release, will have, uh, the possibility of installing from the web, uh, Chrome Web Store 1Password. And this video showcases how it works, that it connects to the desktop app that you have installed. You can see that it works for registering your email and autofilling your password for it. You have to unlock it first, though. You can see here how it works with Touch ID. Um… You can fill the login, password. Then it's going to ask you to save it. You can also, of course, use it to log in to a site, those details. So you guys see here. Then it also works for passkeys, where you can register a passkey for one of the accounts that you already have in 1Password. Um… Again, it's going to probably ask for authentication. And then use that same passkey. To log into the site. In this example, it didn't ask for additional authentication because it was so close to the previous one, but it's working quite nicely. And we'll be posting an announcement with details on how you can provide feedback for this. I said it's quite complicated on the technical side. Thank you. Hold on.
|
||||
- **21:54:58 · AO:** Hey, Elle. This is a demo that Alex, Elle, and I did. So double Alex demo. or DACAI artifacts. Hey everyone! During Hack Days, we explored DACAI artifacts. Documents, presentations, and visuals. But you know what? It's boring, so here's the twist. This presentation was built entirely in DACAI. See? It's right here, inside the chat. And you know what? I can even download it as a PowerPoint file. Now check this out. Let's ask how much I could save. I get an answer, but only for this one case. Different numbers, we need to try again. Or I can get an app that does that for me. Duck AI builds it right here, next to the chat. You can watch it come together. Not a code block, not a screenshot, a real working app. Now I can change the amount, the time, the rate, and it updates instantly. Have a PDF? You can turn it into just about anything. Study notes, a brief, key takeaways, whatever you need, as a document. You have full control over your doc and markdown. You can also let Duck AI rework it. When you are done editing, you can now export your doc. With Artifacts, you can build your own website too. If you want something different, you can just point DuckAI at it and ask for an edit. Every version is saved, so if you don't like your change, you can go back in one click. Artifacts also work well with our browser features. Let's say I have a really long article, and absolutely no desire to read all of it. Attach the top, and Dakia will summarize the main takeaways visually. Just a few seconds, and it's ready, clear, structured, and much easier to understand. And of course, artifacts work great on mobile too. Try them yourself! That's it. Thank you.
|
||||
- **21:57:18 · Gary K:** All right, I'm up. Let me share with sound. a video… Here we go. Any time there is an incident, the first question is always, what changed? And the answer is potentially in a lot of different places. So I've created a command line tool that will aggregate the events that are likely to be interesting for anyone investigating new behavior. What changed is a tool that can access Azure activity logs, Asana deployment plans, Jenkins jobs, GitHub pull requests and actions, REX commands, and Mattermost notifications. Because there can be a lot of data in these sources, the tool ships with default settings that are designed to give high signal-to-noise ratio. These settings can be overwritten via a config file. or a runtime flag. Users can search backwards from now or over a specific window of time, from minutes to days. There are a host of flags designed to make it easy to use. Users can opt in to format the output as JSON and perform further filtering. and transformations using JQ. What changed uses your own credentials, so security posture is maintained. What Changed is available now at www.duckduckgo.com/gcurtis/whatchanged. Thank you. Like and subscribe for more great content. Thank you.
|
||||
- **21:58:52 · Tom Strba:** Nice. Hey everyone. So over the last couple of weeks in OJ and OM, we have been trying to build tools for Duck AI. What does it mean? We would like Duck AI to be able to get context automatically from your browser. And not only that, we would like to. Duck AI to be able to control the browser. So, during hack days, I tried to put all the pieces together, and uh… I would like to show you a proof of concept that I managed to build, so… Let's say I have, uh… Couple of, uh… shoes I am trying to buy. And I would like Duck AI to recommend me which shoes should I buy. So… I will ask you. Which shoes should I buy from all these options? And I'm not providing more context. It will basically get the list of my tabs. It will read the content and it will recommend me, oh, this is the best for speed for daily trainer. whatever but this is not where the fun ends this is where the fun starts so how about now we ask Duck AI. to buy our choice. So for example, buy me stride arrow three. And Duck AI will basically open a new tab and start buying shoes for me. As you can see, here is the store and it's starting to fill the form and it doesn't know which. shoe size it should buy, so it asks me. I will just respond, for example. 10, and it now reads the form. As you can see, it filled. The 10, and now there is a… the website needs the address. So the fun part is that we already have the identity in the browser. So Dakia asks me, hey, can I use this identity from the browser to fill it? And yes, of course, let's share it. If we take a look at the store… by the way, this is the store I built for myself for testing. The address is now filled. and it asks me, it asks me last time, hey, how about, uh, I'm gonna, I'm gonna submit the form, are you, are you sure? Yes. I am sure. And my shoes are now ordered. I didn't need to click on that website. I just wanted you to see what is happening in the background. But Duck AI now or soon will be able to buy. stuff for you or do anything in the browser you want it to do. Uh, that's the first demo I wanted to show you. And the second one, this one will be really quick, and it's, like, internal tool enhancement. Uh, if you… Often test a Mac. make ship reviews, you know the process. You need to download the DMG, attach it manually. Then drag and drop it. The instance is running, so you need to quit it. Then drag and drop again, wait for installation and then run it. So I build the button and now you will just click to run and you can start reading the. ship review, and everything will happen in the background, and after the build is downloaded, I'm gonna speed this up a little bit, it will basically just runs, and you can start testing. Um, that's it for me, thank you.
|
||||
- **22:02:22 · I(:** All right. I'm just getting my screen up. Please let me know if you can see it. All right, looks like it's there. All right. So as a user, why should I care about the protections report on our browser? It's a list of numbers and icons. What is the actual benefit? So I reworked it. I started with the bottom line. Companies are watching you. It's creepy. Also highlighted right away that there's an issue to be fixed. Privacy isn't your default, and here's why that matters. The more of your everyday browsing happens in our app, the less these companies get to see. So let's expand this. Immediately, we get a creepy, interactive, prying eye that follows your cursor around. And we get useful info. We block tracking attempts, but why? They target you with ads, they watch what you read, and they record what you click. It's creepy. So who's watching? Well, Google does a lot of spying, and it was on 4 out of the 5 sites he visited. And Facebook was on almost half. Again. It's really creepy. So I wondered how we could make this more like a personal infographic. Here we highlight the nosiest site of the week, and we show a ring of trackers from that site that blink like eyes to drive home the visceral idea that you're being watched. Now, we empower you to understand some of what we're doing by showing you how we prevent a digital fingerprint view from being created. You can hover over each component of the fingerprint and see what we've hid from creepy companies. And how many times? And finally, we contrast this with Chrome. Where companies swarm around your cursor, and cookie pops and ads fill the screen. We drive home the fact that Chrome is owned by Google, and that unlike on Chrome, DuckDuckGo blocks Google's tracking attempts. So maybe this really creeped you out. Why are so many companies watching you read the news? Let's share that. And just like that, a promotional infographic can be shared with a link to download our browser. So try it out for yourself on Windows on the link task. Thanks.
|
||||
- **22:04:41 · Vinay Nadig:** All right, that's me next. Let me share my screen. Alright, so for hack days, I have. built an app called, QuackTime. What it does is, it lets you schedule ad hoc meetings, through Mattermost without having to do the whole song and dance of matching time zones across. uh, different geographies. So, to use that, go to QuackTime, go to Metamost, or any DM, QuackTime and DM duration, in this case 60 minutes, and then we'll set a type build. You will get a link, you can open it. you will end up on this interface, basically. You will see that all your, uh… uh, working hours and free, uh, slots through Outlook has already been filled in. And that would be the same case for another person as well. So, the other person will also open the same link. And yeah, so you can see that I'm working with Adrian, so I have this much overlap with him, so you can select whichever task that you want. And, oh, sorry. You can propose it. And the other person will… See an option to accept that. And once you accept it, an invite will be sent automatically at the correct time, along with the Zoom link for… which uses your personal Zoom link. That's pretty much it. I'll stop there.
|
||||
- **22:06:17 · Nicklas Jensen:** All right, I'm next up here, and I am going to be sharing some porn. out of a conversation, actually, in a Zoom chat. So, one of the things on the meetup that happened was that we, uh… At least for a lot of the ducklings, we were freaking out about how much merch and how many things have been over the years. So the idea was to create a hall of fame for specifically T-shirts. So Miguel and I worked on that. For this, uh… For these hack days, the goal is you have a timeline, you can see all of the different designs that have been over the years. These are all the ones that Miguel could get a hold of so far. You can vote for your favorite ones. And also, if you don't feel like going through them all manually, you can just… pick out of sort of a random generated thing. And yeah, that's the T-shirt Hall of Fame. How do I stop sharing? Thank you.
|
||||
- **22:07:30 · Dominik Kapusta:** All right, here's a demo of the… Long overdue feature on… macOS, which is the reader mode. Um… Reader mode. extracts text from websites. And here you can see that, uh, we're navigating to a website that, uh, is eligible for being displayed in reader mode, which contains relatively more text, uh, and, um… Just with a single button in the address bar, um… we turn on the reader mode, then we navigate away from that website, it just resets to a regular view. here, uh, you can see, uh, visiting another website, uh, that's also eligible for reader mode, and here's, uh, here's how it works, but it's not all, because I've worked on that, uh, during Hug Days, but. Um… a parallel to my work, actually. Marios was doing the same thing for iOS, so here it is, um… Here, the reader mode, uh… Button is in the website, uh… menu… And this demo will also show you that it respects the browser theme. So that, um… shows correctly in the dark theme as well. Even if you visit a website that… uh, doesn't honor the system theme, uh, then the reader mode, of course, uh, will be dark in this case, when the Guardian was in, uh, in light theme. Yeah, and this all was possible. to do thanks to a library by Meek that extracts. text from, from websites. So really the integration. It was fairly minimal here, and it was just a bit of work. That's why I said it was long overdue, because that library was published a few months ago already. That's it. Thank you.
|
||||
- **22:10:01 · Valerie Kraucunas:** Alrighty, hello. Um, so, I'm Valerie. I work on the front-end team. Um, the thing I've been really heavily focused on all year is the rebrand, and that… with that has come… turning over, uh, style values from one… one way to a new way. Um… with that, we have these things called design tokens, which is basically, like, a codified design decision. And so, when we're styling… the new rebranded stuff we're using, or at least we want to be using all of these things. That said, um, a lot of times when you are handed designs that are rebranded. You end up with this scenario of… It'll be a mix of using the new style tokens and the old style tokens. So in this case, like the SDS styles are a legacy thing. Um, and I want to be very clear, this is not a shame. This is not a shame campaign or anything on designers, because oftentimes when they are building these things, they are… they have the old way in the same file as the. new way. And so it's really, really tedious to get down into every single nook and cranny and node or layer to make sure that you're using the new styles on everything and to make it even more complicated. So when developers see this, we just see this and we're like, why is this still here? Why are we still using SDS things? But when you get over into the design look, so this first column is when they're picking the first padding value, so space X07. When they're picking the second column value, space X03. They look the same. It's really easy to co-mingle the old style and the new. And so, um, basically my concept is to… be able to hand a Claude skill a Figma link, and have it go and traverse the entire. All child nodes of that, um… of whatever you linked over. So. I'm going to try this. I doubt it will… I doubt it'll work. It does not go as fast as I would like it to, but we'll give it a go. So, basically, what happens is you, you know, invoke it with the Figma link, then you give it an Asana link. And give it a name. Um… What that ends up spitting out is a nice report for designers to be able to go and update all the things that are using, uh, old values, or possibly things that are just out of system. As well, um, now I want to be clear, I'm standing on the shoulders of giants here, because, um, while we've been doing the SERP rebrand, uh, my partner in crime, Rachel Lim, created a… skill called Marlin Rebrando, which is basically a dictionary of, uh, knowledge for this was the old way, this is the new way, these are the things we should be checking for when we are executing the rebrand and the code. Um, so my skill is heavily relying on that, but, um… What it'll basically do is it will just… fully traverse like a node tree, if you will, all the way down. Um… And yeah, the things that we're looking for are the use of legacy variables. This is run from within the DDG. repo, for now, at least. So what it will do also is it'll look at the currently installed design token package and make sure that there aren't values being used in the designs that don't exist in. the installed package, then also looking for just colors that aren't tied to a system value, unselled text, et cetera. So what this ends up doing is it will create a. design token report, and. give the designers a link to the layer that. his, uh… has a property on it that's a problem, if you will, and then give it an idea of, like, this is an unexpected value, and then has an expected or a suggested value. The nice part about this as well is that developers. don't necessarily have to wait on designers to go. What?
|
||||
- **22:14:28 · Julia Abreu:** Well… I'm so sorry, I hate to do it, but I have to interrupt you, because we're at 4 minutes now.
|
||||
- **22:14:35 · Valerie Kraucunas:** Oh, shoot, I'm so sorry. Okay, well…
|
||||
- **22:14:36 · Julia Abreu:** Sorry.
|
||||
- **22:14:38 · Valerie Kraucunas:** Making everybody's life better, that's all.
|
||||
- **22:14:50 · Stano:** Okay, I believe I was next. Um, I'm gonna… I hope you can see my screen now. Someone please confirm.
|
||||
- **22:15:00 · Julia Abreu:** No, we cannot.
|
||||
- **22:15:01 · Jason Ashby:** Nope.
|
||||
- **22:15:02 · Stano:** You cannot? Let me try again. Where is… The sun got stuck.
|
||||
- **22:15:24 · Julia Abreu:** Did you find the share button?
|
||||
- **22:15:27 · Stano:** Give me a sec, I reconnected. You can take it out of my budget, I'll make it quick. It does not want to work. You can skip me. Go on.
|
||||
- **22:15:45 · Anh Do:** Okay, looks like I'm next. So let me try to share my screen. Wow. Uh, how do I share, like, a… Particular windows, um… Sorry, um, I had so many windows opening at the moment. Oh, come on. Guys, it is not fun. Sorry. OK, I'm going to share my desktop then. One sec. Hopefully, you can see that on my screen. Can anyone see it? Okay. So for context, in OK, we are helping people in the US to remove personal information from data broker by submitting our request on their.
|
||||
- **22:16:21 · Julia Abreu:** I can see it.
|
||||
- **22:16:33 · Anh Do:** behalf. But recently, we have a lot of issues with broker block our archive with CloudFlare and CAPTCHA, so we can submit the form for the users. So this demo has been built based on Ben Smith design prototype. Let me play that.
|
||||
+635
@@ -23,6 +23,641 @@
|
||||
"time": "16:02:10",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Jest."
|
||||
},
|
||||
{
|
||||
"time": "16:02:13",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "And basically no progress on other stuff yet."
|
||||
},
|
||||
{
|
||||
"time": "16:02:19",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "I need to finish the priority cleanup. So basically last week we've discussed it during the OE that we should. Basically wrap up the project with the. No visible outcomes. There was a slight decline in the numbers and several genuine bugs fixed, but they were not representing the main feature breakage."
|
||||
},
|
||||
{
|
||||
"time": "16:02:45",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Nie. Drop, Ios."
|
||||
},
|
||||
{
|
||||
"time": "16:02:50",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "I know."
|
||||
},
|
||||
{
|
||||
"time": "16:02:57",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Łazać."
|
||||
},
|
||||
{
|
||||
"time": "16:03:00",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "There was some decline, maybe a third. So there was a decline in some part. of the numbers, but there is still around 40%. of the event sequence of the received events that so basically most of it is. The data we received for most of the breakage pixels represents just regular normal flow and nothing obviously."
|
||||
},
|
||||
{
|
||||
"time": "16:03:34",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Bardzo."
|
||||
},
|
||||
{
|
||||
"time": "16:03:34",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "pointing to anything. So the discussion during the OE was to basically clean up the inefficient fixes that we've got. The feature flags for the features that are removed and some. Um, like the pinned tabs management fix, uh, that are, um, staying without the feature flag. And, uh… Yeah, clean up the data that's being collected, because we've collected enough of it, and, uh, implement some permanent data collection that stays there for, uh. for diagnostics for the future possible breakages. And try to add some in. inside of the extension, some metrics inside of the extension to, um, to track the loading progress, basically. Where we… where do we stop, and where the messaging."
|
||||
},
|
||||
{
|
||||
"time": "16:04:23",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Ok."
|
||||
},
|
||||
{
|
||||
"time": "16:04:31",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Stops. and try to reason about it from from that perspective."
|
||||
},
|
||||
{
|
||||
"time": "16:04:37",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Misji."
|
||||
},
|
||||
{
|
||||
"time": "16:04:39",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "So, uh… So yeah, probably today I'm going to open the featured slugs and clean up PR. And. later this week will complete. So I've updated the project, moving on the post-mortem to the next week, since last week I had no time to. completed due to some circumstances. And, uh… That's mostly it. I still got some. PRs requiring my attention, like the crash reporting fix. So, yeah, no updates since last week. On it. So, basically, my concern about it is, uh, we may, uh, we may break the existing macOS collection while fixing iOS collection, so I need to… reproduce it, reproduce the crash and. this slowdown condition and normal conditions and see how it if it still works and nothing breaks and then I'll proceed with it."
|
||||
},
|
||||
{
|
||||
"time": "16:05:49",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Collection as in…"
|
||||
},
|
||||
{
|
||||
"time": "16:05:52",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "The App Store reports."
|
||||
},
|
||||
{
|
||||
"time": "16:05:53",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Crosscode? Yeah, cross-collection, mhm."
|
||||
},
|
||||
{
|
||||
"time": "16:05:57",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, so matching against process identifier or by date."
|
||||
},
|
||||
{
|
||||
"time": "16:06:02",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Yeah. Yeah, yeah, yeah, yeah."
|
||||
},
|
||||
{
|
||||
"time": "16:06:05",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mmm."
|
||||
},
|
||||
{
|
||||
"time": "16:06:05",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Oh. Right."
|
||||
},
|
||||
{
|
||||
"time": "16:06:14",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "And… That is it, I guess, so… I'm. I'm not top performing for the last week. So just… Just completing the TP stuff."
|
||||
},
|
||||
{
|
||||
"time": "16:06:35",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Yeah, which is…"
|
||||
},
|
||||
{
|
||||
"time": "16:06:36",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "And yeah, there was…"
|
||||
},
|
||||
{
|
||||
"time": "16:06:38",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Expected."
|
||||
},
|
||||
{
|
||||
"time": "16:06:39",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "And there was the maintenance, the release maintenance. Luckily, it was growing weak."
|
||||
},
|
||||
{
|
||||
"time": "16:06:46",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "16:06:47",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "So nothing else ended from it."
|
||||
},
|
||||
{
|
||||
"time": "16:06:48",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "I saw that, yeah, that's good, that's good. All right. Nice. That's fine. So you're going to wrap up your project. Will you run the postmortem this week or next week?"
|
||||
},
|
||||
{
|
||||
"time": "16:07:05",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Next week, next week."
|
||||
},
|
||||
{
|
||||
"time": "16:07:06",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Next week. Mm-hmm. Okay."
|
||||
},
|
||||
{
|
||||
"time": "16:07:07",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "So this week, I'm, uh… Completing the cleanup. And the next week is time for the postmortem."
|
||||
},
|
||||
{
|
||||
"time": "16:07:18",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Sounds good. Alright, and then… Do you have… Do you know anything about… You're next. Top priority?"
|
||||
},
|
||||
{
|
||||
"time": "16:07:32",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Uh, nope."
|
||||
},
|
||||
{
|
||||
"time": "16:07:35",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Yeah, because there won't be any follow-up… there won't be any follow-up in OE for…"
|
||||
},
|
||||
{
|
||||
"time": "16:07:35",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "I guess I should make one."
|
||||
},
|
||||
{
|
||||
"time": "16:07:41",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "For this. I mean…"
|
||||
},
|
||||
{
|
||||
"time": "16:07:44",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Well, I guess not, at least for the moment."
|
||||
},
|
||||
{
|
||||
"time": "16:07:45",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Immediate follow up at least. Yeah, yeah, yeah."
|
||||
},
|
||||
{
|
||||
"time": "16:07:49",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "And, uh… So if we are shifting the diagnostics into the JavaScript part, it's probably… due to some someone else to. Keep up with it."
|
||||
},
|
||||
{
|
||||
"time": "16:08:05",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "No."
|
||||
},
|
||||
{
|
||||
"time": "16:08:05",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "So maybe there will be a follow-up task to perform the data analysis next week."
|
||||
},
|
||||
{
|
||||
"time": "16:08:12",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "16:08:12",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "So just one, one cloud shot. To fetch the data, to perform the analysis, to see the trends, and if… Anything new is highlighted from it. So I could person. Wrap up up a date. And that's it. And it goes after."
|
||||
},
|
||||
{
|
||||
"time": "16:08:29",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Yeah, yeah."
|
||||
},
|
||||
{
|
||||
"time": "16:08:31",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Two weeks from now, I guess, when the release is out."
|
||||
},
|
||||
{
|
||||
"time": "16:08:39",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "All right, fine, we'll need to learn what's next for you. When would you be opening? When would you be opening a top priority, Fred?"
|
||||
},
|
||||
{
|
||||
"time": "16:08:47",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Gosh. Probably now."
|
||||
},
|
||||
{
|
||||
"time": "16:08:53",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Yep."
|
||||
},
|
||||
{
|
||||
"time": "16:08:55",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "It's really, it's a good time."
|
||||
},
|
||||
{
|
||||
"time": "16:08:55",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Okay. Okay, this is interesting then. There will be some work. shaping up in OB. If you're up for it, that may be interesting. I'm not sure how much native support they need, but… It is… considered a big problem these days, and that's the fact that all the JavaScript code injected into our websites causes performance issues. And side breakage. But… Yeah, well, both of them, essentially. And I'm, like I said, I'm not sure… If… A native engineer would be needed immediately. But if so, then… that… That would be very important. So this is very important. And… Let me see… So the assessment is this Thursday. And the projects… Okay. Let's see. Let's see. I see there is a… So this is the assessment task. And there is a subtask for the… staffing for the Apple team, so it sounds like they will need… they will need someone from the Apple team. This is not finalized yet, but… But, uh… Should probably be… should probably be… filled out today, I hope. I'll have the proposed critical path and Gantt chart ready for review on Tuesday. I'm proposing OB focus on performance this cycle, specifically the cost of the JS and config we inject into every frame."
|
||||
},
|
||||
{
|
||||
"time": "16:11:21",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Thank you."
|
||||
},
|
||||
{
|
||||
"time": "16:11:21",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "They may at least need someone on the native side to, I don't know, implement some. measurements. I suppose. If this is something that… would be of interest to you, then that's great, because if not, I think you will still be mentioned there. What do you think?"
|
||||
},
|
||||
{
|
||||
"time": "16:11:58",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Visibility. What is this discussion? That you mentioned."
|
||||
},
|
||||
{
|
||||
"time": "16:12:04",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "I was just reading the last comment in the thread."
|
||||
},
|
||||
{
|
||||
"time": "16:12:07",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay."
|
||||
},
|
||||
{
|
||||
"time": "16:12:08",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "From Dave."
|
||||
},
|
||||
{
|
||||
"time": "16:12:22",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mmm… Well, looking at my current TP, if it can be reproduced, it would be more of a… something that I would be interested in, if… And if it's something like we got some breakage to fix it. Not so exciting, I'd say."
|
||||
},
|
||||
{
|
||||
"time": "16:12:52",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Yeah, yeah, yeah, I can tell. I can tell. This, however, should be easier. On the functional side, on the technical side, it should be easier. at least from…"
|
||||
},
|
||||
{
|
||||
"time": "16:13:10",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, at least if there is exact cases reported on or some exact websites."
|
||||
},
|
||||
{
|
||||
"time": "16:13:13",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Yeah, I know. Uh, it may be… it may be about… it may be about just measuring things."
|
||||
},
|
||||
{
|
||||
"time": "16:13:17",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "It should be easier."
|
||||
},
|
||||
{
|
||||
"time": "16:13:22",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "So that front-end engineers can… Do changes, make changes. But I don't know. I don't know the details. Let's see. Trim the Apple Cs. Bundle and isolated world."
|
||||
},
|
||||
{
|
||||
"time": "16:13:37",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay, I'm fine to get mentioned on the thread, and so for the next TP, I'll probably open it on Thursday, I guess."
|
||||
},
|
||||
{
|
||||
"time": "16:13:38",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Interesting. Mmhm."
|
||||
},
|
||||
{
|
||||
"time": "16:13:47",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Makes sense."
|
||||
},
|
||||
{
|
||||
"time": "16:13:49",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Yeah, probably. I think it makes a lot of sense. I will be AFK for the rest of the week. Um, Bob…"
|
||||
},
|
||||
{
|
||||
"time": "16:13:57",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "16:13:59",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "It's not a problem, of course. Um… I will try to… Try to reach out to Jonathan to ask. If he knows anything about OB plans for a pool. Or if he knows anything about anything else. Any other objective that might need Apple people and I'll let you know. Do you want to talk about your performance review?"
|
||||
},
|
||||
{
|
||||
"time": "16:14:31",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Uh, yes, I guess so."
|
||||
},
|
||||
{
|
||||
"time": "16:14:35",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Why not? Right. All right. I linked it in the agenda, updated the link to the latest review. So, congrats on the promotion!"
|
||||
},
|
||||
{
|
||||
"time": "16:14:52",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Thanks."
|
||||
},
|
||||
{
|
||||
"time": "16:14:52",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Amazing, you made it."
|
||||
},
|
||||
{
|
||||
"time": "16:14:53",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "I guess it was a lot of your efforts."
|
||||
},
|
||||
{
|
||||
"time": "16:14:55",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "uh…"
|
||||
},
|
||||
{
|
||||
"time": "16:15:00",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Involved to make it go through."
|
||||
},
|
||||
{
|
||||
"time": "16:15:06",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Just a bit, really. It's, you know, this… this performance review time is overall great. I mean, I like it. I like… I like working on it, because it's, uh…"
|
||||
},
|
||||
{
|
||||
"time": "16:15:17",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Bye."
|
||||
},
|
||||
{
|
||||
"time": "16:15:19",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Um… okay. It's a great time. When you can appreciate people you work with and be able to do something for them. uh… make them… make their efforts visible and recognized. So, if that works, then that's great. This time it worked, so that's amazing. Uh, but… At the end of the day, it's just your work. put into the project. Uh, and, uh, and that got you… a bump in project management, which is amazing, which is… it's essentially hard facts, especially this year. If you look at the… if you look at the review… Format. It's… Like, dry facts. Nothing else, no pros, no…"
|
||||
},
|
||||
{
|
||||
"time": "16:16:13",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "16:16:15",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Did a great job! everyone likes you, and so on and so on, like it used to be in the previous years. This time, it's, like, super, super concrete. With dates, with complexity assessments, with… The amount of direction needed."
|
||||
},
|
||||
{
|
||||
"time": "16:16:32",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mmhm."
|
||||
},
|
||||
{
|
||||
"time": "16:16:33",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "with clear impact stated in each bullet point. So it's just your work. distilled into a few sentences. So… Yeah, great job and keep doing that. I have to say… I have to say, I didn't ask for a promotion, because… I learned that these are the rules. The rules are, you have to have a star in all… in 4 out of 5 dimensions. So you would have to have a star in project management, and in… Team leadership. So I was like, okay, I would like to bump Alexa's project management. But I'm keeping the level at D, because… That's what the rules are, and the rules are in Asana. Um… These are the rules. Alex. There is a task about it. So I read through that task to be 100% sure that I'm doing the right thing, and I said. We have four stars in total, but not… in four dimensions, so it remains D. And everyone agreed with me. And then the calibration committee visited the review just on… it's actually last Friday afternoon. And they said, well, we decided to promote Alex based on that, because… Because we… that's what they thought would be the right thing, and also they are working on updating these rules here. to allow promotions in more, like, spiky profiles, when you have two stars somewhere, and no stars elsewhere. Uh, so…"
|
||||
},
|
||||
{
|
||||
"time": "16:18:26",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mm-hmm. No, I see."
|
||||
},
|
||||
{
|
||||
"time": "16:18:31",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Yeah, that… that happened. Oh, actually…"
|
||||
},
|
||||
{
|
||||
"time": "16:18:31",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Thank you."
|
||||
},
|
||||
{
|
||||
"time": "16:18:35",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Oh, actually, there is a change in that. If you see… The latest edit in that task. there is a sentence added. In exceptional cases, someone may have spiky dimensions performing more than one level above the next level. these can balance out dimensions that are not yet at the next level and will be reviewed case by case. So, in your case, that warranted a promotion, so that's great. Um…"
|
||||
},
|
||||
{
|
||||
"time": "16:19:00",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "I see."
|
||||
},
|
||||
{
|
||||
"time": "16:19:01",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "All right, so we have this. Um, and… Well, you proved that you're… operating on the D-star level when it comes to project management. Um, and uh… Where is your review again? Yes. So we have this, we… I didn't have the… evidence to… ask… bump Team Leadership to the star, but this is something we should… focus on… In the coming year."
|
||||
},
|
||||
{
|
||||
"time": "16:19:48",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay."
|
||||
},
|
||||
{
|
||||
"time": "16:19:48",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "And it will be… Tricky. Because you're not a project advisor. And it will be… Even trickier, because you may… In your current… Work. setting. It may be tricky for you to become a project advisor, but… Let's do whatever we can to try and push that. So, in short, to become a project advisor, you should probably be able to stay in a single objective for some time. On a positive side, we have 12 months. Or six months, let's say, until you're able to operate. to work as a project advisor and make impact, right? And also, I wanted to… Clarify that it's not required. It's not required that you grow to D-star in team leadership by next cycle. It would just be great, it would be the right thing. It's just what's missing in the distal level, so… So we should focus on that specifically. Uh, team leadership… is… Essentially about accelerating the work that is being done. And it's a quote from the Professional Levels PDF. Organizational leadership is accelerating how we work. overall, like, overall, and team leadership is accelerating the work that is currently being done. So, organizational leadership is figuring out new processes, or improving existing processes, and team leadership is finding people that. Struggle at a given time and helping them move forward."
|
||||
},
|
||||
{
|
||||
"time": "16:21:49",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mmhm."
|
||||
},
|
||||
{
|
||||
"time": "16:21:51",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "And, uh… the project advisor role fits here very, very well. So it's very easy, if you're a project advisor, if you're advising projects, then you can just help move projects forward. If you're not a project advisor, you can still do it. You can still do it, but it requires you to proactively go. Go through projects and see if there's something you can help somewhere. And I imagine… It can be very hard if… You're just starting out on that? So… and I'm also… You know, we have plenty of time. But, uh, it would be great to have. Some evidence of you doing things like that. In a year from now."
|
||||
},
|
||||
{
|
||||
"time": "16:22:44",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "16:22:47",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Let's see, I'll try to… I'll be trying to… let you know about opportunities to do that."
|
||||
},
|
||||
{
|
||||
"time": "16:22:58",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay, so…"
|
||||
},
|
||||
{
|
||||
"time": "16:22:58",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "You could also, if you have… Yeah, you could also, like… Look at some projects here and there. OL seems… straightforward, the most straightforward here. However, OL these days is about web extensions, mostly. And we seem to be covered there, but if there's anything… coming up in OL that I think would benefit from your help. Then the easiest is to just add yourself to the project and keep following whatever is happening there. Look at the subtasks. I don't know, help? help the DRI essentially move forward, um… And let's see how it goes. We'll… We will revisit growth areas, and also… Try to formulate something that… Not really, like, describes… What needs to happen? So that's team leadership, and that should be the main focus for next cycle. Uh, apart from that, just keep up your project management, and also getting to this start in project management, showing that you can… run projects smoothly and keep stakeholders up to date and essentially. yeah, do a good job as a… as a project DRI is… is something that will help you become a project advisor, I believe, uh, I'm sure. But the process… the process is that the ODRI selects new project advisors, and this is the main blocker now."
|
||||
},
|
||||
{
|
||||
"time": "16:24:36",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay, yeah."
|
||||
},
|
||||
{
|
||||
"time": "16:24:44",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "So, just to end my speech… Even if you're… bored with… Uh, analyzing site breakage, or various types of breakage. Maybe if it's something that you have actually… Uh, you have a lot of experience in… maybe it would be… easier, helpful to… To stay in this area. If that's possible, if… You know, if staffing allows for that. Uh, and gain a little bit more depth. which would allow you to grow others, perhaps advise projects at some point. But let's see. For now… Take it easy. Take it easy. It's not that you have to start smashing it first week after the review. So yeah, wrap up your project. Let's see what comes next. If the next thing for you is OB, then I think it will be good. If not, we'll rearrange things and see how can we grow in."
|
||||
},
|
||||
{
|
||||
"time": "16:25:55",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "16:26:03",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "In a different setting, but yeah. That's what I wanted to say overall. What do you think about it?"
|
||||
},
|
||||
{
|
||||
"time": "16:26:10",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Yeah, sounds wise, uh… I guess so. There is. some… opportunities to be looked for in the tech designs and. Some other projects that are ongoing, related to my expertise, and uh…"
|
||||
},
|
||||
{
|
||||
"time": "16:26:28",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Yeah, totally."
|
||||
},
|
||||
{
|
||||
"time": "16:26:31",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "And… Yeah, let's look for… for the OB, uh… Next project."
|
||||
},
|
||||
{
|
||||
"time": "16:26:39",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Mmhm."
|
||||
},
|
||||
{
|
||||
"time": "16:26:40",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Maybe there's something that could be done."
|
||||
},
|
||||
{
|
||||
"time": "16:26:46",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Cool. Cool, cool, cool. That's, that sounds good. All right, and with that, like I said, for now, let's just see what happens. Let's see where you land next next week. Mmhm. And I think that's all I had. Can I help you with anything? Is there anything you wanted to… Raise. talk about."
|
||||
},
|
||||
{
|
||||
"time": "16:27:22",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay. I… I don't know. Not really, not anything. In this tech, um…"
|
||||
},
|
||||
{
|
||||
"time": "16:27:48",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "That's fine. That's fine."
|
||||
},
|
||||
{
|
||||
"time": "16:27:52",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "So, yeah, there was, uh, some work, like, kinda planned for, uh, the UI test runners and, uh, all this stuff, but, uh… I'm… At the moment, I'm not doing anything related to it, just completing the TPM."
|
||||
},
|
||||
{
|
||||
"time": "16:28:09",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Mm-hmm."
|
||||
},
|
||||
{
|
||||
"time": "16:28:10",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Um, the open… They opened, they already closed pull requests that I need to complete and. That's… that's all that's on my plate. At the moment, so I'm planning to move forward with this."
|
||||
},
|
||||
{
|
||||
"time": "16:28:28",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Mmhm."
|
||||
},
|
||||
{
|
||||
"time": "16:28:28",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "organizational leadership stuff."
|
||||
},
|
||||
{
|
||||
"time": "16:28:32",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Okay."
|
||||
},
|
||||
{
|
||||
"time": "16:28:32",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "But not… not right now."
|
||||
},
|
||||
{
|
||||
"time": "16:28:37",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Sure, sure. I mean, that's fine. Totally fine to… Like I said, to take it easy for now. Um, alright, uh…"
|
||||
},
|
||||
{
|
||||
"time": "16:28:52",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "I mean, for sure, I… I will need to, uh, sync up with you, and… On that area, when I get my hands on it."
|
||||
},
|
||||
{
|
||||
"time": "16:29:00",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Mm-hmm. Yeah, yeah, we can do it next."
|
||||
},
|
||||
{
|
||||
"time": "16:29:03",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "But yeah, just not ready."
|
||||
},
|
||||
{
|
||||
"time": "16:29:05",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "next week, um… Later. Should be fine. All right, all right."
|
||||
},
|
||||
{
|
||||
"time": "16:29:15",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Thank you."
|
||||
},
|
||||
{
|
||||
"time": "16:29:20",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Good. So if nothing else, we can wrap it up here. I don't have any other announcements, any other important info. I'm also… deep down in my project, trying to open a ship review today, so let's see. And then I'm taking 3 days off, finally. So I'll be back next week."
|
||||
},
|
||||
{
|
||||
"time": "16:29:43",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay."
|
||||
},
|
||||
{
|
||||
"time": "16:29:43",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "But we'll see each other weekly. If I know anything from Jonathan, I'll let you know. Because I'm curious myself. So let's see. Good. If that's it, we can wrap it up here. Congrats again. You're doing a great job. It's a pleasure to be working with you, and yeah, we'll keep smashing it, hopefully, starting next week."
|
||||
},
|
||||
{
|
||||
"time": "16:30:05",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Thanks."
|
||||
},
|
||||
{
|
||||
"time": "16:30:12",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Awesome."
|
||||
},
|
||||
{
|
||||
"time": "16:30:13",
|
||||
"speaker": "Alex Martemyanov",
|
||||
"text": "Okay."
|
||||
},
|
||||
{
|
||||
"time": "16:30:14",
|
||||
"speaker": "Dominik Kapusta",
|
||||
"text": "Thank you. Thanks and have a great rest of the day. See ya."
|
||||
}
|
||||
]
|
||||
}
|
||||
+127
@@ -15,3 +15,130 @@ source: "https://us01mynotes.zoom.us/p5FdcX9WT-afBpWjRgaW0w"
|
||||
- **16:01:44 · Dominik Kapusta:** Is it going.
|
||||
- **16:01:46 · Alex Martemyanov:** And then… I'm pretty good. Thank you. After you… after last week's, uh… I was… So all this RKAFK, so I'm… Wrapping up the top priority project. Mostly, mostly it finally merged the link tooltip thing from the Hug days.
|
||||
- **16:02:10 · Dominik Kapusta:** Jest.
|
||||
- **16:02:13 · Alex Martemyanov:** And basically no progress on other stuff yet.
|
||||
- **16:02:19 · Alex Martemyanov:** I need to finish the priority cleanup. So basically last week we've discussed it during the OE that we should. Basically wrap up the project with the. No visible outcomes. There was a slight decline in the numbers and several genuine bugs fixed, but they were not representing the main feature breakage.
|
||||
- **16:02:45 · Dominik Kapusta:** Nie. Drop, Ios.
|
||||
- **16:02:50 · Alex Martemyanov:** I know.
|
||||
- **16:02:57 · Dominik Kapusta:** Łazać.
|
||||
- **16:03:00 · Alex Martemyanov:** There was some decline, maybe a third. So there was a decline in some part. of the numbers, but there is still around 40%. of the event sequence of the received events that so basically most of it is. The data we received for most of the breakage pixels represents just regular normal flow and nothing obviously.
|
||||
- **16:03:34 · Dominik Kapusta:** Bardzo.
|
||||
- **16:03:34 · Alex Martemyanov:** pointing to anything. So the discussion during the OE was to basically clean up the inefficient fixes that we've got. The feature flags for the features that are removed and some. Um, like the pinned tabs management fix, uh, that are, um, staying without the feature flag. And, uh… Yeah, clean up the data that's being collected, because we've collected enough of it, and, uh, implement some permanent data collection that stays there for, uh. for diagnostics for the future possible breakages. And try to add some in. inside of the extension, some metrics inside of the extension to, um, to track the loading progress, basically. Where we… where do we stop, and where the messaging.
|
||||
- **16:04:23 · Dominik Kapusta:** Ok.
|
||||
- **16:04:31 · Alex Martemyanov:** Stops. and try to reason about it from from that perspective.
|
||||
- **16:04:37 · Dominik Kapusta:** Misji.
|
||||
- **16:04:39 · Alex Martemyanov:** So, uh… So yeah, probably today I'm going to open the featured slugs and clean up PR. And. later this week will complete. So I've updated the project, moving on the post-mortem to the next week, since last week I had no time to. completed due to some circumstances. And, uh… That's mostly it. I still got some. PRs requiring my attention, like the crash reporting fix. So, yeah, no updates since last week. On it. So, basically, my concern about it is, uh, we may, uh, we may break the existing macOS collection while fixing iOS collection, so I need to… reproduce it, reproduce the crash and. this slowdown condition and normal conditions and see how it if it still works and nothing breaks and then I'll proceed with it.
|
||||
- **16:05:49 · Dominik Kapusta:** Collection as in…
|
||||
- **16:05:52 · Alex Martemyanov:** The App Store reports.
|
||||
- **16:05:53 · Dominik Kapusta:** Crosscode? Yeah, cross-collection, mhm.
|
||||
- **16:05:57 · Alex Martemyanov:** Yeah, so matching against process identifier or by date.
|
||||
- **16:06:02 · Dominik Kapusta:** Yeah. Yeah, yeah, yeah, yeah.
|
||||
- **16:06:05 · Alex Martemyanov:** Mmm.
|
||||
- **16:06:05 · Dominik Kapusta:** Oh. Right.
|
||||
- **16:06:14 · Alex Martemyanov:** And… That is it, I guess, so… I'm. I'm not top performing for the last week. So just… Just completing the TP stuff.
|
||||
- **16:06:35 · Dominik Kapusta:** Yeah, which is…
|
||||
- **16:06:36 · Alex Martemyanov:** And yeah, there was…
|
||||
- **16:06:38 · Dominik Kapusta:** Expected.
|
||||
- **16:06:39 · Alex Martemyanov:** And there was the maintenance, the release maintenance. Luckily, it was growing weak.
|
||||
- **16:06:46 · Dominik Kapusta:** Mm-hmm.
|
||||
- **16:06:47 · Alex Martemyanov:** So nothing else ended from it.
|
||||
- **16:06:48 · Dominik Kapusta:** I saw that, yeah, that's good, that's good. All right. Nice. That's fine. So you're going to wrap up your project. Will you run the postmortem this week or next week?
|
||||
- **16:07:05 · Alex Martemyanov:** Next week, next week.
|
||||
- **16:07:06 · Dominik Kapusta:** Next week. Mm-hmm. Okay.
|
||||
- **16:07:07 · Alex Martemyanov:** So this week, I'm, uh… Completing the cleanup. And the next week is time for the postmortem.
|
||||
- **16:07:18 · Dominik Kapusta:** Sounds good. Alright, and then… Do you have… Do you know anything about… You're next. Top priority?
|
||||
- **16:07:32 · Alex Martemyanov:** Uh, nope.
|
||||
- **16:07:35 · Dominik Kapusta:** Yeah, because there won't be any follow-up… there won't be any follow-up in OE for…
|
||||
- **16:07:35 · Alex Martemyanov:** I guess I should make one.
|
||||
- **16:07:41 · Dominik Kapusta:** For this. I mean…
|
||||
- **16:07:44 · Alex Martemyanov:** Well, I guess not, at least for the moment.
|
||||
- **16:07:45 · Dominik Kapusta:** Immediate follow up at least. Yeah, yeah, yeah.
|
||||
- **16:07:49 · Alex Martemyanov:** And, uh… So if we are shifting the diagnostics into the JavaScript part, it's probably… due to some someone else to. Keep up with it.
|
||||
- **16:08:05 · Dominik Kapusta:** No.
|
||||
- **16:08:05 · Alex Martemyanov:** So maybe there will be a follow-up task to perform the data analysis next week.
|
||||
- **16:08:12 · Dominik Kapusta:** Mm-hmm.
|
||||
- **16:08:12 · Alex Martemyanov:** So just one, one cloud shot. To fetch the data, to perform the analysis, to see the trends, and if… Anything new is highlighted from it. So I could person. Wrap up up a date. And that's it. And it goes after.
|
||||
- **16:08:29 · Dominik Kapusta:** Yeah, yeah.
|
||||
- **16:08:31 · Alex Martemyanov:** Two weeks from now, I guess, when the release is out.
|
||||
- **16:08:39 · Dominik Kapusta:** All right, fine, we'll need to learn what's next for you. When would you be opening? When would you be opening a top priority, Fred?
|
||||
- **16:08:47 · Alex Martemyanov:** Gosh. Probably now.
|
||||
- **16:08:53 · Dominik Kapusta:** Yep.
|
||||
- **16:08:55 · Alex Martemyanov:** It's really, it's a good time.
|
||||
- **16:08:55 · Dominik Kapusta:** Okay. Okay, this is interesting then. There will be some work. shaping up in OB. If you're up for it, that may be interesting. I'm not sure how much native support they need, but… It is… considered a big problem these days, and that's the fact that all the JavaScript code injected into our websites causes performance issues. And side breakage. But… Yeah, well, both of them, essentially. And I'm, like I said, I'm not sure… If… A native engineer would be needed immediately. But if so, then… that… That would be very important. So this is very important. And… Let me see… So the assessment is this Thursday. And the projects… Okay. Let's see. Let's see. I see there is a… So this is the assessment task. And there is a subtask for the… staffing for the Apple team, so it sounds like they will need… they will need someone from the Apple team. This is not finalized yet, but… But, uh… Should probably be… should probably be… filled out today, I hope. I'll have the proposed critical path and Gantt chart ready for review on Tuesday. I'm proposing OB focus on performance this cycle, specifically the cost of the JS and config we inject into every frame.
|
||||
- **16:11:21 · Alex Martemyanov:** Thank you.
|
||||
- **16:11:21 · Dominik Kapusta:** They may at least need someone on the native side to, I don't know, implement some. measurements. I suppose. If this is something that… would be of interest to you, then that's great, because if not, I think you will still be mentioned there. What do you think?
|
||||
- **16:11:58 · Alex Martemyanov:** Visibility. What is this discussion? That you mentioned.
|
||||
- **16:12:04 · Dominik Kapusta:** I was just reading the last comment in the thread.
|
||||
- **16:12:07 · Alex Martemyanov:** Okay.
|
||||
- **16:12:08 · Dominik Kapusta:** From Dave.
|
||||
- **16:12:22 · Alex Martemyanov:** Mmm… Well, looking at my current TP, if it can be reproduced, it would be more of a… something that I would be interested in, if… And if it's something like we got some breakage to fix it. Not so exciting, I'd say.
|
||||
- **16:12:52 · Dominik Kapusta:** Yeah, yeah, yeah, I can tell. I can tell. This, however, should be easier. On the functional side, on the technical side, it should be easier. at least from…
|
||||
- **16:13:10 · Alex Martemyanov:** Yeah, at least if there is exact cases reported on or some exact websites.
|
||||
- **16:13:13 · Dominik Kapusta:** Yeah, I know. Uh, it may be… it may be about… it may be about just measuring things.
|
||||
- **16:13:17 · Alex Martemyanov:** It should be easier.
|
||||
- **16:13:22 · Dominik Kapusta:** So that front-end engineers can… Do changes, make changes. But I don't know. I don't know the details. Let's see. Trim the Apple Cs. Bundle and isolated world.
|
||||
- **16:13:37 · Alex Martemyanov:** Okay, I'm fine to get mentioned on the thread, and so for the next TP, I'll probably open it on Thursday, I guess.
|
||||
- **16:13:38 · Dominik Kapusta:** Interesting. Mmhm.
|
||||
- **16:13:47 · Alex Martemyanov:** Makes sense.
|
||||
- **16:13:49 · Dominik Kapusta:** Yeah, probably. I think it makes a lot of sense. I will be AFK for the rest of the week. Um, Bob…
|
||||
- **16:13:57 · Alex Martemyanov:** Mm-hmm.
|
||||
- **16:13:59 · Dominik Kapusta:** It's not a problem, of course. Um… I will try to… Try to reach out to Jonathan to ask. If he knows anything about OB plans for a pool. Or if he knows anything about anything else. Any other objective that might need Apple people and I'll let you know. Do you want to talk about your performance review?
|
||||
- **16:14:31 · Alex Martemyanov:** Uh, yes, I guess so.
|
||||
- **16:14:35 · Dominik Kapusta:** Why not? Right. All right. I linked it in the agenda, updated the link to the latest review. So, congrats on the promotion!
|
||||
- **16:14:52 · Alex Martemyanov:** Thanks.
|
||||
- **16:14:52 · Dominik Kapusta:** Amazing, you made it.
|
||||
- **16:14:53 · Alex Martemyanov:** I guess it was a lot of your efforts.
|
||||
- **16:14:55 · Dominik Kapusta:** uh…
|
||||
- **16:15:00 · Alex Martemyanov:** Involved to make it go through.
|
||||
- **16:15:06 · Dominik Kapusta:** Just a bit, really. It's, you know, this… this performance review time is overall great. I mean, I like it. I like… I like working on it, because it's, uh…
|
||||
- **16:15:17 · Alex Martemyanov:** Bye.
|
||||
- **16:15:19 · Dominik Kapusta:** Um… okay. It's a great time. When you can appreciate people you work with and be able to do something for them. uh… make them… make their efforts visible and recognized. So, if that works, then that's great. This time it worked, so that's amazing. Uh, but… At the end of the day, it's just your work. put into the project. Uh, and, uh, and that got you… a bump in project management, which is amazing, which is… it's essentially hard facts, especially this year. If you look at the… if you look at the review… Format. It's… Like, dry facts. Nothing else, no pros, no…
|
||||
- **16:16:13 · Alex Martemyanov:** Mm-hmm.
|
||||
- **16:16:15 · Dominik Kapusta:** Did a great job! everyone likes you, and so on and so on, like it used to be in the previous years. This time, it's, like, super, super concrete. With dates, with complexity assessments, with… The amount of direction needed.
|
||||
- **16:16:32 · Alex Martemyanov:** Mmhm.
|
||||
- **16:16:33 · Dominik Kapusta:** with clear impact stated in each bullet point. So it's just your work. distilled into a few sentences. So… Yeah, great job and keep doing that. I have to say… I have to say, I didn't ask for a promotion, because… I learned that these are the rules. The rules are, you have to have a star in all… in 4 out of 5 dimensions. So you would have to have a star in project management, and in… Team leadership. So I was like, okay, I would like to bump Alexa's project management. But I'm keeping the level at D, because… That's what the rules are, and the rules are in Asana. Um… These are the rules. Alex. There is a task about it. So I read through that task to be 100% sure that I'm doing the right thing, and I said. We have four stars in total, but not… in four dimensions, so it remains D. And everyone agreed with me. And then the calibration committee visited the review just on… it's actually last Friday afternoon. And they said, well, we decided to promote Alex based on that, because… Because we… that's what they thought would be the right thing, and also they are working on updating these rules here. to allow promotions in more, like, spiky profiles, when you have two stars somewhere, and no stars elsewhere. Uh, so…
|
||||
- **16:18:26 · Alex Martemyanov:** Mm-hmm. No, I see.
|
||||
- **16:18:31 · Dominik Kapusta:** Yeah, that… that happened. Oh, actually…
|
||||
- **16:18:31 · Alex Martemyanov:** Thank you.
|
||||
- **16:18:35 · Dominik Kapusta:** Oh, actually, there is a change in that. If you see… The latest edit in that task. there is a sentence added. In exceptional cases, someone may have spiky dimensions performing more than one level above the next level. these can balance out dimensions that are not yet at the next level and will be reviewed case by case. So, in your case, that warranted a promotion, so that's great. Um…
|
||||
- **16:19:00 · Alex Martemyanov:** I see.
|
||||
- **16:19:01 · Dominik Kapusta:** All right, so we have this. Um, and… Well, you proved that you're… operating on the D-star level when it comes to project management. Um, and uh… Where is your review again? Yes. So we have this, we… I didn't have the… evidence to… ask… bump Team Leadership to the star, but this is something we should… focus on… In the coming year.
|
||||
- **16:19:48 · Alex Martemyanov:** Okay.
|
||||
- **16:19:48 · Dominik Kapusta:** And it will be… Tricky. Because you're not a project advisor. And it will be… Even trickier, because you may… In your current… Work. setting. It may be tricky for you to become a project advisor, but… Let's do whatever we can to try and push that. So, in short, to become a project advisor, you should probably be able to stay in a single objective for some time. On a positive side, we have 12 months. Or six months, let's say, until you're able to operate. to work as a project advisor and make impact, right? And also, I wanted to… Clarify that it's not required. It's not required that you grow to D-star in team leadership by next cycle. It would just be great, it would be the right thing. It's just what's missing in the distal level, so… So we should focus on that specifically. Uh, team leadership… is… Essentially about accelerating the work that is being done. And it's a quote from the Professional Levels PDF. Organizational leadership is accelerating how we work. overall, like, overall, and team leadership is accelerating the work that is currently being done. So, organizational leadership is figuring out new processes, or improving existing processes, and team leadership is finding people that. Struggle at a given time and helping them move forward.
|
||||
- **16:21:49 · Alex Martemyanov:** Mmhm.
|
||||
- **16:21:51 · Dominik Kapusta:** And, uh… the project advisor role fits here very, very well. So it's very easy, if you're a project advisor, if you're advising projects, then you can just help move projects forward. If you're not a project advisor, you can still do it. You can still do it, but it requires you to proactively go. Go through projects and see if there's something you can help somewhere. And I imagine… It can be very hard if… You're just starting out on that? So… and I'm also… You know, we have plenty of time. But, uh, it would be great to have. Some evidence of you doing things like that. In a year from now.
|
||||
- **16:22:44 · Alex Martemyanov:** Mm-hmm.
|
||||
- **16:22:47 · Dominik Kapusta:** Let's see, I'll try to… I'll be trying to… let you know about opportunities to do that.
|
||||
- **16:22:58 · Alex Martemyanov:** Okay, so…
|
||||
- **16:22:58 · Dominik Kapusta:** You could also, if you have… Yeah, you could also, like… Look at some projects here and there. OL seems… straightforward, the most straightforward here. However, OL these days is about web extensions, mostly. And we seem to be covered there, but if there's anything… coming up in OL that I think would benefit from your help. Then the easiest is to just add yourself to the project and keep following whatever is happening there. Look at the subtasks. I don't know, help? help the DRI essentially move forward, um… And let's see how it goes. We'll… We will revisit growth areas, and also… Try to formulate something that… Not really, like, describes… What needs to happen? So that's team leadership, and that should be the main focus for next cycle. Uh, apart from that, just keep up your project management, and also getting to this start in project management, showing that you can… run projects smoothly and keep stakeholders up to date and essentially. yeah, do a good job as a… as a project DRI is… is something that will help you become a project advisor, I believe, uh, I'm sure. But the process… the process is that the ODRI selects new project advisors, and this is the main blocker now.
|
||||
- **16:24:36 · Alex Martemyanov:** Okay, yeah.
|
||||
- **16:24:44 · Dominik Kapusta:** So, just to end my speech… Even if you're… bored with… Uh, analyzing site breakage, or various types of breakage. Maybe if it's something that you have actually… Uh, you have a lot of experience in… maybe it would be… easier, helpful to… To stay in this area. If that's possible, if… You know, if staffing allows for that. Uh, and gain a little bit more depth. which would allow you to grow others, perhaps advise projects at some point. But let's see. For now… Take it easy. Take it easy. It's not that you have to start smashing it first week after the review. So yeah, wrap up your project. Let's see what comes next. If the next thing for you is OB, then I think it will be good. If not, we'll rearrange things and see how can we grow in.
|
||||
- **16:25:55 · Alex Martemyanov:** Mm-hmm.
|
||||
- **16:26:03 · Dominik Kapusta:** In a different setting, but yeah. That's what I wanted to say overall. What do you think about it?
|
||||
- **16:26:10 · Alex Martemyanov:** Yeah, sounds wise, uh… I guess so. There is. some… opportunities to be looked for in the tech designs and. Some other projects that are ongoing, related to my expertise, and uh…
|
||||
- **16:26:28 · Dominik Kapusta:** Yeah, totally.
|
||||
- **16:26:31 · Alex Martemyanov:** And… Yeah, let's look for… for the OB, uh… Next project.
|
||||
- **16:26:39 · Dominik Kapusta:** Mmhm.
|
||||
- **16:26:40 · Alex Martemyanov:** Maybe there's something that could be done.
|
||||
- **16:26:46 · Dominik Kapusta:** Cool. Cool, cool, cool. That's, that sounds good. All right, and with that, like I said, for now, let's just see what happens. Let's see where you land next next week. Mmhm. And I think that's all I had. Can I help you with anything? Is there anything you wanted to… Raise. talk about.
|
||||
- **16:27:22 · Alex Martemyanov:** Okay. I… I don't know. Not really, not anything. In this tech, um…
|
||||
- **16:27:48 · Dominik Kapusta:** That's fine. That's fine.
|
||||
- **16:27:52 · Alex Martemyanov:** So, yeah, there was, uh, some work, like, kinda planned for, uh, the UI test runners and, uh, all this stuff, but, uh… I'm… At the moment, I'm not doing anything related to it, just completing the TPM.
|
||||
- **16:28:09 · Dominik Kapusta:** Mm-hmm.
|
||||
- **16:28:10 · Alex Martemyanov:** Um, the open… They opened, they already closed pull requests that I need to complete and. That's… that's all that's on my plate. At the moment, so I'm planning to move forward with this.
|
||||
- **16:28:28 · Dominik Kapusta:** Mmhm.
|
||||
- **16:28:28 · Alex Martemyanov:** organizational leadership stuff.
|
||||
- **16:28:32 · Dominik Kapusta:** Okay.
|
||||
- **16:28:32 · Alex Martemyanov:** But not… not right now.
|
||||
- **16:28:37 · Dominik Kapusta:** Sure, sure. I mean, that's fine. Totally fine to… Like I said, to take it easy for now. Um, alright, uh…
|
||||
- **16:28:52 · Alex Martemyanov:** I mean, for sure, I… I will need to, uh, sync up with you, and… On that area, when I get my hands on it.
|
||||
- **16:29:00 · Dominik Kapusta:** Mm-hmm. Yeah, yeah, we can do it next.
|
||||
- **16:29:03 · Alex Martemyanov:** But yeah, just not ready.
|
||||
- **16:29:05 · Dominik Kapusta:** next week, um… Later. Should be fine. All right, all right.
|
||||
- **16:29:15 · Alex Martemyanov:** Thank you.
|
||||
- **16:29:20 · Dominik Kapusta:** Good. So if nothing else, we can wrap it up here. I don't have any other announcements, any other important info. I'm also… deep down in my project, trying to open a ship review today, so let's see. And then I'm taking 3 days off, finally. So I'll be back next week.
|
||||
- **16:29:43 · Alex Martemyanov:** Okay.
|
||||
- **16:29:43 · Dominik Kapusta:** But we'll see each other weekly. If I know anything from Jonathan, I'll let you know. Because I'm curious myself. So let's see. Good. If that's it, we can wrap it up here. Congrats again. You're doing a great job. It's a pleasure to be working with you, and yeah, we'll keep smashing it, hopefully, starting next week.
|
||||
- **16:30:05 · Alex Martemyanov:** Thanks.
|
||||
- **16:30:12 · Dominik Kapusta:** Awesome.
|
||||
- **16:30:13 · Alex Martemyanov:** Okay.
|
||||
- **16:30:14 · Dominik Kapusta:** Thank you. Thanks and have a great rest of the day. See ya.
|
||||
Reference in new issue
Block a user