From 5c7d92448d460ba71a5eff77530bba918021a76c Mon Sep 17 00:00:00 2001 From: Alexey Martemyanov Date: Sun, 18 Oct 2026 02:19:25 +0600 Subject: [PATCH] [2026-10-18] eagle: work/zoom-transcripts/2026-10-15 Dominik Kapusta's Personal Meeting Room 2026-10-15 16 05(GMT+6 00) nzWOuhyzSdCjNqMRh6X13w/transcript.json work/zoom-transcripts/2026-10-15 Dominik Kapusta's Personal Meeting Room 2026-10-15 16 05(GMT+6 00) nzWOuhyzSdCjNqMRh6X13w/transcript.md work/zoom-transcripts/index.json --- .../transcript.json | 1669 +++++++++++++++++ .../transcript.md | 345 ++++ work/zoom-transcripts/index.json | 8 + 3 files changed, 2022 insertions(+) create mode 100644 work/zoom-transcripts/2026-10-15 Dominik Kapusta's Personal Meeting Room 2026-10-15 16 05(GMT+6 00) nzWOuhyzSdCjNqMRh6X13w/transcript.json create mode 100644 work/zoom-transcripts/2026-10-15 Dominik Kapusta's Personal Meeting Room 2026-10-15 16 05(GMT+6 00) nzWOuhyzSdCjNqMRh6X13w/transcript.md mode change 100755 => 100644 work/zoom-transcripts/index.json diff --git a/work/zoom-transcripts/2026-10-15 Dominik Kapusta's Personal Meeting Room 2026-10-15 16 05(GMT+6 00) nzWOuhyzSdCjNqMRh6X13w/transcript.json b/work/zoom-transcripts/2026-10-15 Dominik Kapusta's Personal Meeting Room 2026-10-15 16 05(GMT+6 00) nzWOuhyzSdCjNqMRh6X13w/transcript.json new file mode 100644 index 00000000..319f4681 --- /dev/null +++ b/work/zoom-transcripts/2026-10-15 Dominik Kapusta's Personal Meeting Room 2026-10-15 16 05(GMT+6 00) nzWOuhyzSdCjNqMRh6X13w/transcript.json @@ -0,0 +1,1669 @@ +{ + "schema_version": 1, + "note_id": "nzWOuhyzSdCjNqMRh6X13w", + "title": "Dominik Kapusta's Personal Meeting Room 2026-10-15 16:05(GMT+6:00)", + "meeting_date": "2026-10-15", + "source_url": "https://us01mynotes.zoom.us/nzWOuhyzSdCjNqMRh6X13w", + "transcript": [ + { + "time": "16:05:14", + "speaker": "Dominik Kapusta", + "text": "Ай Горю?" + }, + { + "time": "16:05:15", + "speaker": "Alex Martemyanov", + "text": "Oh. Still commuting, yeah. Much better, I think. And yeah, reaching you." + }, + { + "time": "16:05:25", + "speaker": "Dominik Kapusta", + "text": "Отгод. Гуд. Туф. Ера." + }, + { + "time": "16:05:27", + "speaker": "Alex Martemyanov", + "text": "Eventful week. Let's see. A lot of things happening in parallel. And yeah, for today, I kinda… Already tired. Probably still not 100% recovered. But, yeah, anyways, I tried to update our agenda." + }, + { + "time": "16:05:45", + "speaker": "Alex Martemyanov", + "text": "Бад. Я. Энивэйс?" + }, + { + "time": "16:05:46", + "speaker": "Dominik Kapusta", + "text": "Я?" + }, + { + "time": "16:05:53", + "speaker": "Alex Martemyanov", + "text": "And, uh… Yeah, so basically… From the last update, from the last Friday's update on my top priority, there is… Not much of actual update happened since I spent most of the Monday. And… with the… It abuse the incident thing. The other stuff, and just get to the…" + }, + { + "time": "16:06:21", + "speaker": "Dominik Kapusta", + "text": "Ням?" + }, + { + "time": "16:06:24", + "speaker": "Alex Martemyanov", + "text": "Do the actual priority thing, and uh… Today, I'm… trying to get through it, and first of all, it's blocked with this, uh, domain name called Crash. The time kinda keep iterating. Miss Claude." + }, + { + "time": "16:06:40", + "speaker": "Dominik Kapusta", + "text": "Вот краш вот. Краш. Свои?" + }, + { + "time": "16:06:42", + "speaker": "Alex Martemyanov", + "text": "The domain and the domain and code, the WebKit proxy error thing." + }, + { + "time": "16:06:46", + "speaker": "Dominik Kapusta", + "text": "А. Аа, Окей?" + }, + { + "time": "16:06:49", + "speaker": "Alex Martemyanov", + "text": "Yeah, I'm just, uh… I'm just about to open it, and just final validation of the bills passing. I'm just basically ready, and I'll ping you if you can. Uh, it goes to a normal… normal release, since it's not… Not high occurrences are normally on the 86 machines, but anyways, it's naturally preceding the telemetry fix and all the other stuff. Yeah, and on the top priority, I got several stages. I think there is, um… Three, four. Even… Yeah, at least three VRs. Stacked PRs pending. So first of all, we need adjusting the attribution because currently it misses some identified points. And, uh, we need some proofs of it, actually. of the events actually happening. So basically, I've identified it to… The background issue is lock screen or unloading browser and the network process crash that may also. I don't know. We affected the CPM error and basically those like 80% of the telemetry." + }, + { + "time": "16:08:18", + "speaker": "Dominik Kapusta", + "text": "Окей?" + }, + { + "time": "16:08:25", + "speaker": "Alex Martemyanov", + "text": "It got reproduced in the. Best homeless setup. That was made for evaluating the theories. So, if it goes well, we should… We should probably cover like 80% of those and hopefully receive some extra data to cover the rest. Um, so… That's moving, although I'm kind of feeling a little… Bring the trade. and all of this. Uh, but yeah, I was hoping to open everything today so we could review it tomorrow, but realistically… It's probably gonna be only the attribution fix, so request for today and the crash fix. And for tomorrow, yeah. I'll try to… Uh, to discuss it with Michal, if we can… We can get it through." + }, + { + "time": "16:09:30", + "speaker": "Dominik Kapusta", + "text": "All right. Uh, okay." + }, + { + "time": "16:09:32", + "speaker": "Alex Martemyanov", + "text": "So, yeah, later today, I'll give an update on the project, uh, when I… when I have the request open." + }, + { + "time": "16:09:35", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm. Yeah, sure." + }, + { + "time": "16:09:40", + "speaker": "Alex Martemyanov", + "text": "So, it may be…" + }, + { + "time": "16:09:43", + "speaker": "Dominik Kapusta", + "text": "Yeah, uh, I'm looking at these fixed CPM breakage issues. Breakage. WebKit issues, I guess. Uh, and there are four subtasks, which…" + }, + { + "time": "16:09:51", + "speaker": "Alex Martemyanov", + "text": "Yep." + }, + { + "time": "16:09:56", + "speaker": "Dominik Kapusta", + "text": "So there will be four pull requests?" + }, + { + "time": "16:09:57", + "speaker": "Alex Martemyanov", + "text": "All of them have contacts." + }, + { + "time": "16:10:00", + "speaker": "Dominik Kapusta", + "text": "Double." + }, + { + "time": "16:10:00", + "speaker": "Alex Martemyanov", + "text": "Yes, I guess so." + }, + { + "time": "16:10:01", + "speaker": "Dominik Kapusta", + "text": "Mmhm. Okay." + }, + { + "time": "16:10:03", + "speaker": "Alex Martemyanov", + "text": "I'm planning to… to give it some… details in the research and in the tasks themselves. on, uh… kind of describing the approaches, but yeah, it comes a bit later. So, yeah, it's to be updated. They'll post in a project a bit later today." + }, + { + "time": "16:10:27", + "speaker": "Dominik Kapusta", + "text": "Sounds good." + }, + { + "time": "16:10:28", + "speaker": "Alex Martemyanov", + "text": "So, yeah, last week. Last week after. All of that kind of got some toxication. Uh, which… Luckily gave me like a couple of days. To just get relaxed a little bit. Yeah, but meanwhile, yesterday, I got some… Oh, I… Got some time… like lazy white coding on the extra project projects. And I got some results you may have seen. So, basically, there is the tech design for the VS Code integration updated. Yeah, basically, I've posted the update. Thanks for all the input." + }, + { + "time": "16:11:14", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm." + }, + { + "time": "16:11:18", + "speaker": "Alex Martemyanov", + "text": "And, uh, having all of that, I actually found a way that will work and, uh, that doesn't touch the current." + }, + { + "time": "16:11:19", + "speaker": "Dominik Kapusta", + "text": "Yeah." + }, + { + "time": "16:11:28", + "speaker": "Alex Martemyanov", + "text": "I mean, current project structure, it's, uh… It's a little… it's a small wrapper over the Xcode language." + }, + { + "time": "16:11:38", + "speaker": "Dominik Kapusta", + "text": "Ahem." + }, + { + "time": "16:11:38", + "speaker": "Alex Martemyanov", + "text": "The server, which uses the same architecture. Uh, as Xcode does for…" + }, + { + "time": "16:11:45", + "speaker": "Dominik Kapusta", + "text": "Mmhm." + }, + { + "time": "16:11:46", + "speaker": "Alex Martemyanov", + "text": "sources indexing, and it used the same Swift build system. that Xcode27 is using under the hood now, so we should be pretty much aligned on this. Even though the repo or the project itself is pretty young, I think we could easily fork it since it's released." + }, + { + "time": "16:11:57", + "speaker": "Dominik Kapusta", + "text": "Mmhm." + }, + { + "time": "16:12:07", + "speaker": "Alex Martemyanov", + "text": "Really small rubber, and uh… And keep…" + }, + { + "time": "16:12:14", + "speaker": "Dominik Kapusta", + "text": "Okay." + }, + { + "time": "16:12:16", + "speaker": "Alex Martemyanov", + "text": "And coupons, that's… for me." + }, + { + "time": "16:12:20", + "speaker": "Dominik Kapusta", + "text": "Um…" + }, + { + "time": "16:12:20", + "speaker": "Alex Martemyanov", + "text": "Because of, kind of, security and privacy concerns, and uh…" + }, + { + "time": "16:12:24", + "speaker": "Dominik Kapusta", + "text": "Fine, yeah, yeah, I think it would require… Something like a vendor triage… dependency… Triage, or tool triage, whatever it's called, but it's essentially, like, a tool that we want to use, and… And because of that, we might want to perform some checks on it." + }, + { + "time": "16:12:50", + "speaker": "Alex Martemyanov", + "text": "Yeah, there is a related question in the tech design, so basically I've assigned it to you if you can. And you may leave the comments on it." + }, + { + "time": "16:12:58", + "speaker": "Dominik Kapusta", + "text": "Mmhm." + }, + { + "time": "16:13:03", + "speaker": "Alex Martemyanov", + "text": "Yeah, so basically that should work, and… Keeping things moving and finally resolve the project. Maybe maybe a good thing to the. Career review thing. Like, moving the team forward and finishing the effort. And with the following… With the following tests update. I actually got it locally, so basically it's a buildable folder and unlinking the AppDelegate dependency. it just waits for, uh, for the tech design to be approved. Yeah, basically, it only depends on the main… main branch, it's not related to VS Code. But it works, iOS works with simulator." + }, + { + "time": "16:13:52", + "speaker": "Dominik Kapusta", + "text": "Mmhm." + }, + { + "time": "16:13:53", + "speaker": "Alex Martemyanov", + "text": "macOS network, everything just works. Oh…" + }, + { + "time": "16:13:57", + "speaker": "Dominik Kapusta", + "text": "That's good, that's good." + }, + { + "time": "16:14:00", + "speaker": "Alex Martemyanov", + "text": "And yeah, there is only one issue about export build, and it's a package resolution thing that I was trying to get rid of, but maybe I'll get through it with some local fork. Just for myself or for anybody who's interested, if… if it would be the use case. Basically, I expect a couple of… team members to adopt it, or at least take a look, maybe it works for somebody. Especially having the next things, which are in my, uh… Stick in the artwork. So basically, I. Uh, pretty much completed the, uh, virtual machine manager thing that I mentioned, kind of, half a year ago. Started work on it, so it's migrated to… Another build system… It supports remote machines like old MacBook that just works. You can see it. Sorry. It just works directly from MCP, and even if I can crash machines, but I won't advertise on the team, but anyways, I have one. And be used for virtual machines testing as well. Uh, it just works. So, um, Claude and ChatGPT, when I ask to…" + }, + { + "time": "16:15:20", + "speaker": "Dominik Kapusta", + "text": "Okay." + }, + { + "time": "16:15:25", + "speaker": "Alex Martemyanov", + "text": "validate the tests on macOS 27 or macOS 12, it just says, okay, I will set up the virtual machine, I'm getting the lease, I've run the tests, the bug is reproduced, it's fixed. Uh… So that's another part of the… AR work and developers help, and there is integration for VS Code as well, so you could just run the virtual machine and run the build. from VS Code, and there is no hanging at launch, it just works natively, and you can run UI tests in it, not blocking your main working machine. So, basically, the project is moving really, really well." + }, + { + "time": "16:16:06", + "speaker": "Dominik Kapusta", + "text": "Mm, mm-hmm." + }, + { + "time": "16:16:07", + "speaker": "Alex Martemyanov", + "text": "And I expected to have some to make some contribution to the team when I when I finish. Approving this." + }, + { + "time": "16:16:18", + "speaker": "Dominik Kapusta", + "text": "Yeah, that's good. I mean, it's a lot. It is a lot. So allow me to digest it." + }, + { + "time": "16:16:20", + "speaker": "Alex Martemyanov", + "text": "Great, thank you." + }, + { + "time": "16:16:26", + "speaker": "Dominik Kapusta", + "text": "Piece by piece. But, uh… Um… Can maybe talk about the tech design later. VS Code and Xcode preferably server. Fine. The other thing you've just mentioned, it's what's on that diagram." + }, + { + "time": "16:16:55", + "speaker": "Alex Martemyanov", + "text": "Uh, the diagram, yeah, that's just another quick, uh, quick call of yesterday's date." + }, + { + "time": "16:16:56", + "speaker": "Dominik Kapusta", + "text": "In the agenda?" + }, + { + "time": "16:17:02", + "speaker": "Alex Martemyanov", + "text": "From my bed. Oh… It's, uh, basically… Agent setup analysis for automatic bug and crash fix workflow. I just… had its one short run, and asked to summarize everything we've had for a century, and what Android and Windows teams have. Uh, so this is kind of first one-shot diagram that it came with, analyzing the signals. So we have, uh… manual trigger from Asana, like tagging or mentioning a bot. Uh, we have a new crash events, or we have a CI failure, uh, that, uh, first runs. a cloud agent or Linux with Sentry and Asana access, analyzes the code, the task, and. everything, and then runs an isolated runner on Bitrise. that reproduces UI tests or unit tests, collects the evidence, tries to fix, iterates, and proceeds opening pull requests with a fix or no hope. With automated MetaMoose and Basana comment. Not sent by a bot because of the incident one, and, but, posted by by the automation." + }, + { + "time": "16:18:30", + "speaker": "Dominik Kapusta", + "text": "Hmm, yeah." + }, + { + "time": "16:18:35", + "speaker": "Alex Martemyanov", + "text": "And then the last step, yeah, the bottleneck of the human review, the approval. Which, if in case of the test runs, the test runs… By the way, I just got another test run that just passed, and I'm probably gonna use the Fernando proposal to just merge it. Um, there's one self-review." + }, + { + "time": "16:18:55", + "speaker": "Dominik Kapusta", + "text": "Amanda proposal." + }, + { + "time": "16:18:58", + "speaker": "Alex Martemyanov", + "text": "Uh, they self-review for test fixes." + }, + { + "time": "16:19:02", + "speaker": "Dominik Kapusta", + "text": "Ah, yeah, yeah, sure." + }, + { + "time": "16:19:04", + "speaker": "Alex Martemyanov", + "text": "Yeah, so yeah, it's basically an automated run. fixing the… my local automators around fixing the Discover, DUI tests issues. Uh… So… It should run the same thing, but online using agent runners. And, uh… So yeah, basically we have a first. First AI iteration of it, so I could… Choose from what to move next when I have some time." + }, + { + "time": "16:19:40", + "speaker": "Dominik Kapusta", + "text": "All right. What you're doing is… It's great in terms that… It's… These are great ideas for the team, for sure. Uh, the thing is, it is being worked on already in a few places, and it would be great to coordinate that work, or maybe join that work. Uh, we are currently… figuring out… Bitrise… well, not Bitrise, but, uh, essentially infrastructure for… Running Agentic workflows on… for Apple team. And… I said Bitrise because I'm involved in a Bitrise task, which is about Bitrise remote development environments, which is their new feature that they… where they just…" + }, + { + "time": "16:20:32", + "speaker": "Alex Martemyanov", + "text": "Okay." + }, + { + "time": "16:20:41", + "speaker": "Dominik Kapusta", + "text": "just provide macOS virtual machines that you can use for that. They come with Xcode and Claude pre-installed, and… Yeah. Okay. What I was doing is I was trying to get the build to pass on these machines, like, set everything up… as close to our CI setup as possible. And I think it worked in the end, I need to… Uh, leave for a moment today, but… Yeah, I think it works." + }, + { + "time": "16:21:17", + "speaker": "Alex Martemyanov", + "text": "Yeah, you mean the… the runner automation thing? Yeah, again, I, uh, haven't spent…" + }, + { + "time": "16:21:20", + "speaker": "Dominik Kapusta", + "text": "Yeah, we…" + }, + { + "time": "16:21:24", + "speaker": "Alex Martemyanov", + "text": "Actually, a minute on it. And just… it's just a one-shot research." + }, + { + "time": "16:21:30", + "speaker": "Dominik Kapusta", + "text": "Just the discussion topic. Okay, okay, fine. Yeah." + }, + { + "time": "16:21:33", + "speaker": "Alex Martemyanov", + "text": "Yeah, so basically a discussion topic to probably involve me into these flows and, yeah, start the coordination." + }, + { + "time": "16:21:37", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm, sure, sure, so I can tell you, I can tell you where we are, I can tell you where we are. We are considering… Actually, one thing that is happening is… Um, enabling… Simple Agentic workflows, like one shot. essentially workflows on GitHub Actions. And, uh, so the idea is you have a workflow where you… Or the prompt? is the input. And the. A workflow just runs, and whatever… whatever the output needs to be, it is. Is it, like, a pull request, or some artifact, whatever. But essentially, like, think of, I don't know, fix this crash, and then it ends up with a pull request. Yeah, um… There is a small problem. We aren't allowed to use… Anthropic. API keys in public repositories. So. To work around that, we are setting up a private repository that will be empty. And just have that token? And the workflows. And the workflow would clone the monorepo." + }, + { + "time": "16:23:04", + "speaker": "Alex Martemyanov", + "text": "Mmhm." + }, + { + "time": "16:23:04", + "speaker": "Dominik Kapusta", + "text": "But it would run in a private repository otherwise. But it would clone the monorepo, and work on the monorepo, and open the pull request in the monorepo. Uh, so the only… the only complication here is that it can't be the monorepo, can't live in the monorepo, but it lives in a private repository that essentially has write access to the monorepo, and that's it. So this is for a single… Like, single-shot, uh… tasks? Where you just… Essentially, you give a task to the agent, and… you don't want to talk to it in the meantime, you don't need to talk to it in the meantime, and then it comes with the result. For longer. Workflows, where you would like to… Intervene. In the meantime, or would you expect to be pinged by the agent? Uh, we can't do it in GitHub Actions, because you can't… stop the… stop the GitHub action workflow, or… essentially take over the control of it. So for that, we just need a remote machine. With… with a cloud session. And you could like SSH into that machine for instance or VNC into it and… And take over if needed. And that is being figured out. One possibility is AWS. The problem with AWS is it's $1400 per month per machine. So, we're also evaluating Bitrise on that, and Bitrise would be definitely cheaper, and it comes with… Well, the VM images are prepared for Apple development. They have Xcode, they have plenty of other tools. installed Ruby and so on and so on. So that's what we're… dealing with now, going through security triages and so on and so on. Um, oh." + }, + { + "time": "16:25:17", + "speaker": "Alex Martemyanov", + "text": "What's the problem with the… With it. Why do we have to SSH to another machine?" + }, + { + "time": "16:25:28", + "speaker": "Dominik Kapusta", + "text": "Well, we don't have to, but… If we want to… we wouldn't be able to in a GitHub Action workflow. I'm." + }, + { + "time": "16:25:40", + "speaker": "Alex Martemyanov", + "text": "Okay." + }, + { + "time": "16:25:41", + "speaker": "Dominik Kapusta", + "text": "And, yeah, well, whatever, you don't need to SSH into it, but you might want to… Connect to a cloud session on such machine. to see… what's going on there, and I don't know, to… to provide further instructions to the agent, and so on and so on. Uh, I also… to be completely fair, I don't… fully follow that use case yet. I'm… I clearly understand the need for, uh, simple workflows, like, please fix this, please do this, and so on and so on. Make no mistakes. But these interactive sessions, they are a bit… A bit strange to me, but… Yeah, people that have more experience than me suggested that we would need this. Uh, I guess it may… it may be about, um… Just doing work on a remote machine, rather than a local machine. Just like this, right? So you can do it locally, but you can also do it remotely. I'm not entirely sure how much it would, uh… we would benefit from it. Umm. Let's see." + }, + { + "time": "16:27:04", + "speaker": "Alex Martemyanov", + "text": "Yeah, like having a… remote testing machine with BNC, and uh… Agent runs, and even remote building from… from the VS Code. Uh, it may be a good option, since not everybody has, like, as new of machine as I… of machines as I do. And ability to run those. So probably we could." + }, + { + "time": "16:27:25", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm." + }, + { + "time": "16:27:29", + "speaker": "Alex Martemyanov", + "text": "Integrate. And that point as well, somehow. So just maybe ping me in the related tasks and." + }, + { + "time": "16:27:34", + "speaker": "Dominik Kapusta", + "text": "Yeah, yeah." + }, + { + "time": "16:27:38", + "speaker": "Alex Martemyanov", + "text": "I'll see where can we… Integrate. and distribute the work. Okay." + }, + { + "time": "16:27:55", + "speaker": "Dominik Kapusta", + "text": "Yeah, I can try to involve you here and there or just give you links. Because, because, because, because one of them is this one. This is one of them. That's for the simple workflows and the other one is… this. And this Bitrise thingy is a subtask of. of a full project called \"Find an alternative to Cursor Cloud Agents to safely run autonomous workflows\"." + }, + { + "time": "16:28:48", + "speaker": "Alex Martemyanov", + "text": "Mm-hmm." + }, + { + "time": "16:28:53", + "speaker": "Dominik Kapusta", + "text": "One other limitation of GitHub Actions is that. Any workflow can only run for 6 hours, so in case we have some long, long jobs… It would just stop after six hours. and be deleted and forgotten." + }, + { + "time": "16:29:12", + "speaker": "Alex Martemyanov", + "text": "Yeah, generally, the ramps should not… List for cigarette rollers." + }, + { + "time": "16:29:17", + "speaker": "Dominik Kapusta", + "text": "Yeah, they shouldn't. I agree. Oh, all right." + }, + { + "time": "16:29:29", + "speaker": "Alex Martemyanov", + "text": "Yeah." + }, + { + "time": "16:29:31", + "speaker": "Dominik Kapusta", + "text": "All right, so that's this. For the tech design. I will have a look later. I saw there are some comments already, and overall the reception is… is better. Probably because… It's opt-in, and it doesn't change anything that we have. Um… Yeah, some of the requirements of your previous design were… hard to… Hard to just, you know… agree on without, without, uh…" + }, + { + "time": "16:30:06", + "speaker": "Alex Martemyanov", + "text": "Accept." + }, + { + "time": "16:30:10", + "speaker": "Dominik Kapusta", + "text": "No. Like… It was just, essentially it was just refactoring, refactoring a lot of code in order to maybe have some benefits, but also there were, like, a significant part of these benefits would be achievable without all these changes, so… I'm glad that we're gonna be switching to buildable folders, which will simplify the project file drastically. And then there's this other thing. that I have forgotten in the meantime. Oh, yeah, uh, removing the host application from tests." + }, + { + "time": "16:30:48", + "speaker": "Alex Martemyanov", + "text": "Uh, I think it's not removing, but uh… Because since we run it in Xcode and not as a package, we cannot remove the host application." + }, + { + "time": "16:31:01", + "speaker": "Dominik Kapusta", + "text": "But you don't launch it in UI tests, in unit tests." + }, + { + "time": "16:31:04", + "speaker": "Alex Martemyanov", + "text": "Relaunch it." + }, + { + "time": "16:31:06", + "speaker": "Dominik Kapusta", + "text": "But if you set it to none, do you still launch it?" + }, + { + "time": "16:31:06", + "speaker": "Alex Martemyanov", + "text": "But, uh… You cannot launch it if you don't have it. Because it's run against the host application from Xcode. And if you want to run to remove the host application, you have to convert it to the library as it was in the initial design." + }, + { + "time": "16:31:26", + "speaker": "Dominik Kapusta", + "text": "So what happens? If I go here… and here and do this. What does this really change?" + }, + { + "time": "16:31:38", + "speaker": "Alex Martemyanov", + "text": "Mmhm. I suppose it won't. Build the tests." + }, + { + "time": "16:31:51", + "speaker": "Dominik Kapusta", + "text": "It works. It's what I wrote in the comment on your initial tech design. I set it to none, and it works. The only tests that are failing were the CBR…" + }, + { + "time": "16:31:52", + "speaker": "Alex Martemyanov", + "text": "Or maybe, uh… Excuse me." + }, + { + "time": "16:32:03", + "speaker": "Dominik Kapusta", + "text": "Tests. No." + }, + { + "time": "16:32:09", + "speaker": "Alex Martemyanov", + "text": "Okay, good. I'll reiterate about it." + }, + { + "time": "16:32:12", + "speaker": "Dominik Kapusta", + "text": "Okay." + }, + { + "time": "16:32:12", + "speaker": "Alex Martemyanov", + "text": "Anyways, uh… anyways, it's ready without… even without it. And, uh… The fix there was just to… To inject the… An empty app delegate." + }, + { + "time": "16:32:26", + "speaker": "Dominik Kapusta", + "text": "Yeah, yeah, that was… that was the thing that came to my mind initially. We can… we can have another app that I get, and then…" + }, + { + "time": "16:32:26", + "speaker": "Alex Martemyanov", + "text": "Instead of the apps that I'm gonna get." + }, + { + "time": "16:32:36", + "speaker": "Dominik Kapusta", + "text": "I think it's a build setting, the app delegate is also a build setting somewhere, or the… yeah." + }, + { + "time": "16:32:39", + "speaker": "Alex Martemyanov", + "text": "Yeah, so anyways, I'm getting to it, and it's independent from VS Code or anything else, and when I…" + }, + { + "time": "16:32:44", + "speaker": "Dominik Kapusta", + "text": "Yeah, yeah. Mm-hmm." + }, + { + "time": "16:32:47", + "speaker": "Alex Martemyanov", + "text": "Wipe, wipe out the current priority work." + }, + { + "time": "16:32:53", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm." + }, + { + "time": "16:32:53", + "speaker": "Alex Martemyanov", + "text": "On my table, and uh… I'll come back to it and. And, uh… and modularization items as well." + }, + { + "time": "16:33:05", + "speaker": "Dominik Kapusta", + "text": "Mmhm." + }, + { + "time": "16:33:05", + "speaker": "Alex Martemyanov", + "text": "So, maybe when, uh… when we have the browser modularized, like, finalized, we could reiterate over the SPM package, as it would be a logical next step, or maybe we didn't change. Uh, with the next, next code release. Uh, like, Apple providing several…" + }, + { + "time": "16:33:23", + "speaker": "Dominik Kapusta", + "text": "Hmm." + }, + { + "time": "16:33:25", + "speaker": "Alex Martemyanov", + "text": "Steps further." + }, + { + "time": "16:33:26", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm." + }, + { + "time": "16:33:27", + "speaker": "Alex Martemyanov", + "text": "to the SPM compilation, as it seems. Uh, so… yeah, we'll get there." + }, + { + "time": "16:33:35", + "speaker": "Dominik Kapusta", + "text": "Okay. Okay, nice. One other thing that we need to do today. which is slightly overdue, is the… Continuous development check-in. Which means we should talk about growth areas and shoutouts as well, actually, of course. They are here. Yeah, it's a private task, but you have access. um… So we… We talked about… uh, the communication overall. And… um… For this… Like then, what was the next steps was that you're moving again from ON to OE into a new… Environment, new people… And there was just this reminder to use your project advisor, to bring questions, to… to provide updates in the project and so on and so on. And… What do you think about… About this growth area, about the other growth area perhaps as well, because we can keep it, we can… Call it done. We can create a new one. My. Personal feeling is that. It still needs some work. But curious about your perspective." + }, + { + "time": "16:35:40", + "speaker": "Alex Martemyanov", + "text": "So, I don't know… Very good question. So generally, we… It's the last… iteration. We've had several projects, like. And… The most complicated one is probably the current one, and uh…" + }, + { + "time": "16:35:58", + "speaker": "Dominik Kapusta", + "text": "Mmhm." + }, + { + "time": "16:36:01", + "speaker": "Alex Martemyanov", + "text": "So general directions there were initial communications over the project structure. I will proceed and." + }, + { + "time": "16:36:11", + "speaker": "Dominik Kapusta", + "text": "Mmhm." + }, + { + "time": "16:36:12", + "speaker": "Alex Martemyanov", + "text": "Several need more time suggesting the roadmap. Oh. Otherwise, there were just regular project updates on the current state and expectations with some corrections as required. And… So about bringing question and doubts. I'm not sure here, because I think there were a couple of. question and doubts that I brought to the project advisor on what. What's better to do, or how to iterate over it, or should we apply this, or have a bigger iteration on the better solution?" + }, + { + "time": "16:36:49", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm. Mmhm." + }, + { + "time": "16:36:56", + "speaker": "Alex Martemyanov", + "text": "Or, uh… Aligning on the… on the roadmap, I mean, on schedule, like on reviews and… our release dates. So… Generally, from my perspective, I… Try to keep it. Up to date and keep people updated when it's… when something happens, or like, nothing happens if I…" + }, + { + "time": "16:37:25", + "speaker": "Dominik Kapusta", + "text": "Yeah, okay." + }, + { + "time": "16:37:28", + "speaker": "Alex Martemyanov", + "text": "Um, if there is… if there is a slowdown, for example, for some reason." + }, + { + "time": "16:37:29", + "speaker": "Dominik Kapusta", + "text": "Right. Yeah, yeah, and that's good. If you… So when you reach out to the project advisor, do you do it on Inasana or Mattermost?" + }, + { + "time": "16:37:48", + "speaker": "Alex Martemyanov", + "text": "Mmm…" + }, + { + "time": "16:37:48", + "speaker": "Dominik Kapusta", + "text": "Is it in the comms task or some other tasks?" + }, + { + "time": "16:37:53", + "speaker": "Alex Martemyanov", + "text": "I think it's mostly in MetaMOST, but sometimes there is some… So basically, project update iteration, if there was some…" + }, + { + "time": "16:37:56", + "speaker": "Dominik Kapusta", + "text": "Mmhm. Mmhm." + }, + { + "time": "16:38:02", + "speaker": "Alex Martemyanov", + "text": "If there was some decision." + }, + { + "time": "16:38:04", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm. Good. What I can… suggest, maybe, is… because, like, at least looking at, uh, at this task…" + }, + { + "time": "16:38:18", + "speaker": "Alex Martemyanov", + "text": "Yeah, there is not much of the communication happening on the top." + }, + { + "time": "16:38:18", + "speaker": "Dominik Kapusta", + "text": "for… You know, there is not much communication, but there are also two instances of, uh… career advisor asking… I mean, sorry, project advisor asking you for… for the status?" + }, + { + "time": "16:38:34", + "speaker": "Alex Martemyanov", + "text": "Uh, and actually, I was just writing the project update, and in the moment, he was asking." + }, + { + "time": "16:38:34", + "speaker": "Dominik Kapusta", + "text": "And." + }, + { + "time": "16:38:40", + "speaker": "Alex Martemyanov", + "text": "Uh, about the status…" + }, + { + "time": "16:38:41", + "speaker": "Dominik Kapusta", + "text": "Mmhm." + }, + { + "time": "16:38:43", + "speaker": "Alex Martemyanov", + "text": "And…" + }, + { + "time": "16:38:43", + "speaker": "Dominik Kapusta", + "text": "And." + }, + { + "time": "16:38:46", + "speaker": "Alex Martemyanov", + "text": "And yeah, you mean making the communication more visible and go through the communication tasks?" + }, + { + "time": "16:38:50", + "speaker": "Dominik Kapusta", + "text": "Making the… if the communication happens, making it visible would be great. what I noticed, uh… Diego did on a couple of occasions. We were on a Zoom call, and he would put a summary of a Zoom call in the communication task. Just, you know, just some bullet points, just to…" + }, + { + "time": "16:39:14", + "speaker": "Alex Martemyanov", + "text": "Mm-hmm." + }, + { + "time": "16:39:17", + "speaker": "Dominik Kapusta", + "text": "to make it clear that the communication happens. And it's also valuable… of course, it's valuable to everyone who reads the task, but it's also valuable to yourself and to the project advisor, because project advisor. I mean, more to the project advisor, of course, because you… this is your top priority, but this is not project advisor's top priority, and they may have more work, and they may be forgetting things, so it's great to… To just… Note down. Oh. whatever is happening, right? If you… even if you chat on Mattermost, and you have, like, a… some exchange of messages in Matrimos that is valuable, and where you learn something. It's a great… Um, great, uh, habit to… to just, you know… put it in Asana as well. Just as a documentation that things are happening. When it comes to project updates. It's… It's probably… I wanted to say that, well, I can see you're posting frequent updates when needed. There's an update from 7th of October and then the update from 9th of October. Because some people get fixed on that. rows weekly… I mean, write weekly updates, and then they put one update a week, and they're fine with that. But it's not… always enough to just write one update a week. So that's good. But… What I would like to see… And this CPM project is not looking… I mean, it's looking fine, right? People seem to be… okay with your communication there, but then there is… like, the communication does not end on your project, your top priorities. We had an example with this VS Code initiative where… Well, some comments started popping up on your project task. And you remember, like, I was pinging you to put a comment there, uh, like. Calm them down, because the situation was that some people wrote some comments and… The last one was from Juan. The last one was from Juan, and um… And he just… asked you explicitly, could you talk more about the benefits of the project structure, cleanup, and coding standards we'll get from these changes? And… I know that. you… your idea was to write a tech design, and that's also what we agreed on on Apple Weekly. Another weekly meeting, I think it went well overall, where you calmed people down, essentially. But not everyone was on the call. And then if you come back to that project, you see that project in Asana, and you still see Juan's comment there, which is unanswered. It would be great to respond to it. Could you talk more about the benefits of the project structure cleanup? I mean, yes… I'm about to write everything down in a tech design. So we'll see, and… yeah, I saw your comment, I read your comment, and I will address it. Sometimes this is… Fine. Um, there were actually some… some agreements on the Apple Weekly Call that you could put in writing over there, like, yeah, you'll write the tech design, and then we'll talk about it, and it's not… what was very important to me, I think, at least, was that… it's not strictly about VS Code integration, but also it's… It's a way of speeding up builds, cleaning up project structure, and so on and so on. So… This could have been put there in a comment. Otherwise, people were… a bit lost in all of this, and they were… Actually, I have to say they were afraid." + }, + { + "time": "16:44:17", + "speaker": "Dominik Kapusta", + "text": "about what's happening, because it's a lot of changes, and… Of course, we don't like changes, no one likes big changes, especially if they are not clearly backed by some proper reasoning. Um, so… So that was that. And then when I… then when I… kept pinging you for a couple of days, you told me, oh, I'm writing a tech design, I'll update later, I'll say, fine. And then you only wrote the comment that the tech design is ready, so please go read a tech design. Go and retake design. Which, yeah, it was a bit… a bit late as well, but uh… What I… what I suggested you on our Mattermost chat, it's essentially, you know, just put, like, two, three sentences there to calm people down, and you should be fine. Mmm. No. So… So that's something that… That would be great to see going forward. I think. Because… Let me… put it this way. It's clearer than when projects are going… The right way, or… Or not, but as long as it's… On the technical side, good or bad, whatever, you're handling it perfectly. You're just, okay, this is my project, this is the plan, these are the tasks I'm working on, when I'm done with this, I'm gonna do this, and so on and so on. And you're giving proper updates, you're keeping everyone… Well informed. And then… when sometimes something happens, and also, you're fine, like, calling me mid-mortems to decide on technical stuff, and so on, and so on. But if there is this… This, how to say, um, well, someone raising something, uh, having doubts. Then it gets tricky. Essentially it gets tricky and you may be. A bit lost, I don't know. I'm just still trying to…" + }, + { + "time": "16:47:08", + "speaker": "Alex Martemyanov", + "text": "Yeah, I just tried to go through the actual comment to reason about it and to." + }, + { + "time": "16:47:15", + "speaker": "Dominik Kapusta", + "text": "Yeah." + }, + { + "time": "16:47:16", + "speaker": "Alex Martemyanov", + "text": "Basically, to iterate over it so it gets to my… Incoming queue, and uh…" + }, + { + "time": "16:47:21", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm." + }, + { + "time": "16:47:23", + "speaker": "Alex Martemyanov", + "text": "When I reach to it, I, yeah, answer, basically." + }, + { + "time": "16:47:26", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm, mm-hmm, mm." + }, + { + "time": "16:47:30", + "speaker": "Alex Martemyanov", + "text": "And some comments do require some extra checks." + }, + { + "time": "16:47:34", + "speaker": "Dominik Kapusta", + "text": "Mmhm." + }, + { + "time": "16:47:35", + "speaker": "Alex Martemyanov", + "text": "Uh, switching contexts and, uh, especially having those run as a parallel project." + }, + { + "time": "16:47:37", + "speaker": "Dominik Kapusta", + "text": "No." + }, + { + "time": "16:47:42", + "speaker": "Alex Martemyanov", + "text": "or background projects to the priority. And it may be, yeah, it may require some extra efforts. To marry those." + }, + { + "time": "16:47:54", + "speaker": "Dominik Kapusta", + "text": "You know." + }, + { + "time": "16:47:56", + "speaker": "Alex Martemyanov", + "text": "There's really the incoming, um… Incoming backlog." + }, + { + "time": "16:48:05", + "speaker": "Dominik Kapusta", + "text": "I'm thinking how to… What to do? to also avoid… Being pinged. for updating your project status. I understand that there was a coincidence, like, Michal commented, okay, so how is it going, what are the next steps, and you were just writing an update. But. Yeah, maybe…" + }, + { + "time": "16:48:37", + "speaker": "Alex Martemyanov", + "text": "Yeah, so basically there is a milestone at the end of the week and my evening of Fridays and there is some events like mid-mortems or some plan changes or some re-evaluations." + }, + { + "time": "16:48:41", + "speaker": "Dominik Kapusta", + "text": "Mmhm. Mmhm." + }, + { + "time": "16:48:52", + "speaker": "Alex Martemyanov", + "text": "That I'll post midweek. And, uh…" + }, + { + "time": "16:48:54", + "speaker": "Dominik Kapusta", + "text": "Hmm." + }, + { + "time": "16:48:55", + "speaker": "Alex Martemyanov", + "text": "Generally, otherwise, when, uh… it feels natural for me to post an update, like, when I finish my work on Friday, just to hand over to the, uh…" + }, + { + "time": "16:49:02", + "speaker": "Dominik Kapusta", + "text": "No." + }, + { + "time": "16:49:06", + "speaker": "Alex Martemyanov", + "text": "Uh, to the ones from the US side that are usually running the objectives, and uh…" + }, + { + "time": "16:49:09", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm. Mmhm." + }, + { + "time": "16:49:11", + "speaker": "Alex Martemyanov", + "text": "it feels kinda fine, posting an update in the morning when I didn't finish, and I don't see the outcome yet, and… It's kind of. It may get tricky." + }, + { + "time": "16:49:25", + "speaker": "Dominik Kapusta", + "text": "Okay. Yeah, uh… Oh, okay, okay. All right. Fine, but I will… I would still keep that growth area here, because I think this is the most important thing for you right now. It's to… to be…" + }, + { + "time": "16:49:57", + "speaker": "Alex Martemyanov", + "text": "I'm trying to… To work with it from the different perspective and having some. Yeah, basically, I've also added to the agenda, like, the, uh, the personal OS setup that. And that keeps growing in parallel. I already had some. Local agents analyzing my past work and. current work and just prepare the workflow for the. current status analysis and comparing it to the local work that is being done and tracing the communication requiring my reactions. Just to keep things in focus and maybe post some notifications as… as is required. So to get myself like pinged that. Okay, you already like hyper focus to this task like for 6 h, you should stop for today. Post an update and answer for these 3 comments. So this is the." + }, + { + "time": "16:50:51", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm, mm-hmm. Yeah. Yes." + }, + { + "time": "16:51:03", + "speaker": "Alex Martemyanov", + "text": "should be the case and it's… It's already starts to show something. Building up from it." + }, + { + "time": "16:51:11", + "speaker": "Dominik Kapusta", + "text": "Did you say you put it in the agenda?" + }, + { + "time": "16:51:12", + "speaker": "Alex Martemyanov", + "text": "Oh. No, uh, yes. Uh, yes, I put it to the, uh… The agenda." + }, + { + "time": "16:51:24", + "speaker": "Dominik Kapusta", + "text": "Can't find it." + }, + { + "time": "16:51:24", + "speaker": "Alex Martemyanov", + "text": "Right. Hmm. Where is it?" + }, + { + "time": "16:51:33", + "speaker": "Dominik Kapusta", + "text": "I don't know." + }, + { + "time": "16:51:35", + "speaker": "Alex Martemyanov", + "text": "Sure, it was there. It was in the… Good. Not here. Okay, let's put it here. It was the update that was, uh… the old content, basically, I updated it. Maybe… maybe you just got something from it." + }, + { + "time": "16:51:56", + "speaker": "Dominik Kapusta", + "text": "Oh. Okay, in the old path. Mmhm." + }, + { + "time": "16:52:46", + "speaker": "Alex Martemyanov", + "text": "And… Yeah. So basically what's, it's done there, it's, monitors the activity watch, active window, of course, locally, related to the local work trees, to Asana tasks, loads, the Asana task." + }, + { + "time": "16:53:27", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm." + }, + { + "time": "16:53:29", + "speaker": "Alex Martemyanov", + "text": "full listing and summarizes it to the short project status and key decisions. And, uh, when the new events arrive, uh, they are updated. Um, so… In the perfect world, it should, like… Group up, analyze my current day workflow, analyze the…" + }, + { + "time": "16:53:49", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm." + }, + { + "time": "16:53:51", + "speaker": "Alex Martemyanov", + "text": "week, weekly, uh… weekly plans and career plans and mix it in a balanced set of. Oh. plans and nudges like notifications to react on something or to. Minish Lee. Focus on context switching. It starts getting some shape, so it's currently on the state of current local agent output. Of course, it should be gone through manually in my free time, and I should see the actual project status and what I got from it. And how it understands it, so there's no… Mmhm. Doubling source of truth. And yeah, after it, I'll build something on top of it. Meanwhile, it led some consequences with the token solar usage." + }, + { + "time": "16:54:58", + "speaker": "Dominik Kapusta", + "text": "Thank you." + }, + { + "time": "16:54:58", + "speaker": "Alex Martemyanov", + "text": "So I got commented from Kane. Uh, asking me to share the actual results I've got from spending. the quarters. the first week of October." + }, + { + "time": "16:55:13", + "speaker": "Dominik Kapusta", + "text": "Wow." + }, + { + "time": "16:55:15", + "speaker": "Alex Martemyanov", + "text": "Yeah, um… I'm gonna share it later. Probably." + }, + { + "time": "16:55:23", + "speaker": "Dominik Kapusta", + "text": "Interesting." + }, + { + "time": "16:55:25", + "speaker": "Alex Martemyanov", + "text": "And…" + }, + { + "time": "16:55:25", + "speaker": "Dominik Kapusta", + "text": "So, what was it? You exhausted the quota, or you have higher quota already?" + }, + { + "time": "16:55:29", + "speaker": "Alex Martemyanov", + "text": "Yeah, basically, I've adjusted the quota, and I've requested a quota raise for Claude, and I got raised the quota." + }, + { + "time": "16:55:35", + "speaker": "Dominik Kapusta", + "text": "Yeah, and then they are asking for what you've done with it." + }, + { + "time": "16:55:39", + "speaker": "Alex Martemyanov", + "text": "Yeah, unboxing what was happening and what was going wrong. So basically, it's just the default Opus that I have set here again. Let's just, especially on the high level." + }, + { + "time": "16:55:51", + "speaker": "Dominik Kapusta", + "text": "Was was it? Was it 5.5?" + }, + { + "time": "16:55:54", + "speaker": "Alex Martemyanov", + "text": "Yep. Yeah, Opus 5.5, the org default, set for high, it's uh…" + }, + { + "time": "16:55:56", + "speaker": "Dominik Kapusta", + "text": "Oh." + }, + { + "time": "16:56:01", + "speaker": "Alex Martemyanov", + "text": "It just burned another 200 of bucks yesterday for the test iteration work, because I…" + }, + { + "time": "16:56:04", + "speaker": "Dominik Kapusta", + "text": "Hmm. Mm-hmm." + }, + { + "time": "16:56:08", + "speaker": "Alex Martemyanov", + "text": "Started it that way and forgot to switch it back." + }, + { + "time": "16:56:11", + "speaker": "Dominik Kapusta", + "text": "Hmmm." + }, + { + "time": "16:56:11", + "speaker": "Alex Martemyanov", + "text": "So and it's really easy to to burn 200 there. So 5 days of work, and you have the 1,000 out." + }, + { + "time": "16:56:12", + "speaker": "Dominik Kapusta", + "text": "Okay. Yeah, sure." + }, + { + "time": "16:56:18", + "speaker": "Alex Martemyanov", + "text": "So nothing special, actually." + }, + { + "time": "16:56:21", + "speaker": "Dominik Kapusta", + "text": "Yeah. Okay." + }, + { + "time": "16:56:21", + "speaker": "Alex Martemyanov", + "text": "Um… So I'll probably try to mention it, that we should set the default model. to another one, because it says Opus by default, because it's set as ORG default. But yeah, otherwise there were some outputs from it." + }, + { + "time": "16:56:36", + "speaker": "Dominik Kapusta", + "text": "Hmm…" + }, + { + "time": "16:56:41", + "speaker": "Alex Martemyanov", + "text": "like the UI test, the CPM web extension. 3 pull requests, and… Countless iteration of a revolution with virtual machines and all this setup. Actually, run with it, and… So it got the job done, but… The burning is still…" + }, + { + "time": "16:57:04", + "speaker": "Dominik Kapusta", + "text": "Interesting, interesting. I just saw, I just checked and it looks like I'm on medium effort because I had the medium effort set for Fable. I was using Fable on medium effort." + }, + { + "time": "16:57:04", + "speaker": "Alex Martemyanov", + "text": "I've looked at my leggings." + }, + { + "time": "16:57:19", + "speaker": "Dominik Kapusta", + "text": "And I switched back to Opus 5.5, and I kept medium effort. I didn't mean to keep medium effort, but I have very, very, very, very low usage this month." + }, + { + "time": "16:57:30", + "speaker": "Alex Martemyanov", + "text": "Actually, Sonnet is using a reasonable amount of token, I say, and high effort, because I usually use high effort for some larger topics, especially." + }, + { + "time": "16:57:37", + "speaker": "Dominik Kapusta", + "text": "Okay." + }, + { + "time": "16:57:45", + "speaker": "Alex Martemyanov", + "text": "when I just run it, okay, evaluate this bug from Asana, run the test, fix it, and then come up with a PR, so I can check the final result and not iterate on every stage. And if I set medium effort, it just loses context, compacts it, and starts doing some…" + }, + { + "time": "16:57:50", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm. Mm-hmm." + }, + { + "time": "16:58:01", + "speaker": "Alex Martemyanov", + "text": "Some bullshit, usually." + }, + { + "time": "16:58:04", + "speaker": "Dominik Kapusta", + "text": "Right." + }, + { + "time": "16:58:06", + "speaker": "Alex Martemyanov", + "text": "But yeah, Sonnet is, uh, Sonnet or Fable is pretty good at it, and I just should not forget to switch it back from Opus." + }, + { + "time": "16:58:15", + "speaker": "Dominik Kapusta", + "text": "Yeah. Uh, alright…" + }, + { + "time": "16:58:22", + "speaker": "Alex Martemyanov", + "text": "So yeah, coming back to the updates." + }, + { + "time": "16:58:22", + "speaker": "Dominik Kapusta", + "text": "Override." + }, + { + "time": "16:58:28", + "speaker": "Alex Martemyanov", + "text": "I'm… I'm working on that." + }, + { + "time": "16:58:31", + "speaker": "Dominik Kapusta", + "text": "Mmhm." + }, + { + "time": "16:58:31", + "speaker": "Alex Martemyanov", + "text": "So I have that that points to. To provide some updates and try to. To catch it if it requires some more attention and post updates. Earlier, for example, I have one pending from Kirby and some pixel not being reported. Mmm… I'll probably just pause it. I have to manage my top priority and answer later this week. This weekend's tomorrow. Okay. Uh, yeah, I'm working on it. And, uh… And, uh, and, and… Anything else on the, uh… On the growth areas." + }, + { + "time": "16:59:23", + "speaker": "Dominik Kapusta", + "text": "Only growth areas… I think we should also keep the other one for… About. Essentially growing others. So that's for team leadership, which means reviewing stuff, which you… have done a nice job for Andre. I'll try to get feedback from him." + }, + { + "time": "16:59:50", + "speaker": "Alex Martemyanov", + "text": "And it was…" + }, + { + "time": "16:59:53", + "speaker": "Dominik Kapusta", + "text": "Umm." + }, + { + "time": "16:59:53", + "speaker": "Alex Martemyanov", + "text": "It was, uh… yeah, I tried… I mean, it was a lot of, uh… a lot of work, actually, spent on the reviews and back and forth and all of that, and…" + }, + { + "time": "17:00:03", + "speaker": "Dominik Kapusta", + "text": "Yeah, and it may be overwhelming, it may be annoying, but I also…" + }, + { + "time": "17:00:04", + "speaker": "Alex Martemyanov", + "text": "that… Goes like an." + }, + { + "time": "17:00:11", + "speaker": "Dominik Kapusta", + "text": "I also heard from Andre that. Does your good reviewer? I'm going to send him a feedback request for that." + }, + { + "time": "17:00:19", + "speaker": "Alex Martemyanov", + "text": "Yeah, training every day on Claude and Codex." + }, + { + "time": "17:00:22", + "speaker": "Dominik Kapusta", + "text": "Yeah, so that was fine. We got feedback. Have you seen feedback from Max?" + }, + { + "time": "17:00:32", + "speaker": "Alex Martemyanov", + "text": "No." + }, + { + "time": "17:00:33", + "speaker": "Dominik Kapusta", + "text": "It arrived yesterday. Uh, let me share… It's here." + }, + { + "time": "17:01:04", + "speaker": "Alex Martemyanov", + "text": "And… Thanks. And…" + }, + { + "time": "17:01:18", + "speaker": "Dominik Kapusta", + "text": "which also…" + }, + { + "time": "17:01:18", + "speaker": "Alex Martemyanov", + "text": "Okay, 100." + }, + { + "time": "17:01:21", + "speaker": "Dominik Kapusta", + "text": "What was that, sorry?" + }, + { + "time": "17:01:21", + "speaker": "Alex Martemyanov", + "text": "Yes, here we are. Oh, for months." + }, + { + "time": "17:01:25", + "speaker": "Dominik Kapusta", + "text": "Yes. Have you read it?" + }, + { + "time": "17:01:28", + "speaker": "Alex Martemyanov", + "text": "Hmm… Okay. Mm-hmm." + }, + { + "time": "17:01:50", + "speaker": "Dominik Kapusta", + "text": "Yeah, so, um…" + }, + { + "time": "17:01:53", + "speaker": "Alex Martemyanov", + "text": "Again, this is the career advisor task." + }, + { + "time": "17:01:54", + "speaker": "Dominik Kapusta", + "text": "This is… This is also… I, sorry, what was that?" + }, + { + "time": "17:01:58", + "speaker": "Alex Martemyanov", + "text": "It's a visibility question." + }, + { + "time": "17:02:00", + "speaker": "Dominik Kapusta", + "text": "I don't understand." + }, + { + "time": "17:02:00", + "speaker": "Alex Martemyanov", + "text": "The career advisor task communication thing that." + }, + { + "time": "17:02:04", + "speaker": "Dominik Kapusta", + "text": "The project advisor task." + }, + { + "time": "17:02:07", + "speaker": "Alex Martemyanov", + "text": "Project advisor cost, right?" + }, + { + "time": "17:02:07", + "speaker": "Dominik Kapusta", + "text": "Yes, yes, yes. Yeah, yeah, so that's that. I don't know what to say, just remember about that, because the previous feedback from Alessandro was really, really good. And I was like, ah, that's amazing." + }, + { + "time": "17:02:27", + "speaker": "Alex Martemyanov", + "text": "Yeah, generally we kept in touch with Alessandro, and probably he was the… Only one, and the, uh, ODRIs were updated during the meeting… during the meetings, the stand-ups." + }, + { + "time": "17:02:38", + "speaker": "Dominik Kapusta", + "text": "Uh-huh, yeah." + }, + { + "time": "17:02:38", + "speaker": "Alex Martemyanov", + "text": "Uh, so there was no… nobody else, uh, involved there. Here in the status, it may look like." + }, + { + "time": "17:02:44", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm." + }, + { + "time": "17:02:47", + "speaker": "Alex Martemyanov", + "text": "Because, uh, the project advisor communications in the summer look pretty much the same, actually, and I just…" + }, + { + "time": "17:02:53", + "speaker": "Dominik Kapusta", + "text": "Mmhm. Mmhm." + }, + { + "time": "17:02:56", + "speaker": "Alex Martemyanov", + "text": "reached out to him directly on Mattermost, most of the times, and posting the project update in the… in the main desk." + }, + { + "time": "17:02:59", + "speaker": "Dominik Kapusta", + "text": "Mm-mm. I see. Yeah, yeah." + }, + { + "time": "17:03:03", + "speaker": "Alex Martemyanov", + "text": "So having no real discussions happening in the project advisor tasks." + }, + { + "time": "17:03:08", + "speaker": "Dominik Kapusta", + "text": "Right, right." + }, + { + "time": "17:03:09", + "speaker": "Alex Martemyanov", + "text": "That probably should come up with some kind of discussions to be put in there." + }, + { + "time": "17:03:11", + "speaker": "Dominik Kapusta", + "text": "Oh. Yeah, probably, you know, don't do anything for the sake of doing it, but just… Documenting and the chats in that async task is a good habit to have. Yeah, um… We're also waiting for feedback from Michal. So we'll see. And I'll send one out to Andre. For now, I think let's keep your… let's keep your growth areas. So, yeah, focus on… I mean, keep communication in mind. And not only into priorities." + }, + { + "time": "17:04:03", + "speaker": "Alex Martemyanov", + "text": "Okay, I'll just post an update today, probably that we discussed today about the project, and we're not getting up with all the PRs today." + }, + { + "time": "17:04:14", + "speaker": "Dominik Kapusta", + "text": "Hmm, hmm. Fine. Uh, yeah, and the other one is leverage your functional skills to ensure that your peers keep a high quality bar. And I'm going to document the progress and the progresses that you've worked with Andra. Have you also commented on… Yeah, you have. You have commented on the ship review. So that's great." + }, + { + "time": "17:04:37", + "speaker": "Alex Martemyanov", + "text": "On the ship review, on tech design." + }, + { + "time": "17:04:39", + "speaker": "Dominik Kapusta", + "text": "Mmhm." + }, + { + "time": "17:04:41", + "speaker": "Alex Martemyanov", + "text": "There was and the. And the VS Code tech design discussion and iterations." + }, + { + "time": "17:04:46", + "speaker": "Dominik Kapusta", + "text": "Yeah, yeah, yeah, yeah, sure, sure. For tech designs here, for tech designs, we're looking for examples when you were the reviewer." + }, + { + "time": "17:04:48", + "speaker": "Alex Martemyanov", + "text": "I guess." + }, + { + "time": "17:04:56", + "speaker": "Dominik Kapusta", + "text": "So. Next time. Uh, and yeah, if there's something, uh, something, uh. that I spot that you could be a reviewer for, I will… I will arrange it. So that you could do it for a tech design. Good." + }, + { + "time": "17:05:18", + "speaker": "Alex Martemyanov", + "text": "Okay…" + }, + { + "time": "17:05:22", + "speaker": "Dominik Kapusta", + "text": "I'm going to update it soon. Not many updates, anyway, in the Grove Areas. The Grove Areas stay. I'm gonna add a new shoutout, and slightly rework the Grove Areas, and that's it. For the… for the… this VS Code work… I think we're done. Your last comment was really good, like acknowledging everything and closing it and opening a new one. The new one, it is a little bit of a surprise, it comes so quick, so fast. That, yeah, people may be wondering… what are you doing in your free time? Which is… I know what you're doing, but it may be strange." + }, + { + "time": "17:06:06", + "speaker": "Alex Martemyanov", + "text": "Yeah, basically it was… In my bed yesterday, just with clothes." + }, + { + "time": "17:06:10", + "speaker": "Dominik Kapusta", + "text": "Mmhm. No." + }, + { + "time": "17:06:12", + "speaker": "Alex Martemyanov", + "text": "Just to iterate over it." + }, + { + "time": "17:06:15", + "speaker": "Dominik Kapusta", + "text": "Mmhm." + }, + { + "time": "17:06:15", + "speaker": "Alex Martemyanov", + "text": "So…" + }, + { + "time": "17:06:19", + "speaker": "Dominik Kapusta", + "text": "Fine." + }, + { + "time": "17:06:21", + "speaker": "Alex Martemyanov", + "text": "Yes, that's in the technical leadership and the…" + }, + { + "time": "17:06:21", + "speaker": "Dominik Kapusta", + "text": "Good. I'll…" + }, + { + "time": "17:06:25", + "speaker": "Alex Martemyanov", + "text": "We integrate the agenda task. Uh, ship review, the comment on tech design…" + }, + { + "time": "17:06:32", + "speaker": "Dominik Kapusta", + "text": "Mmhm." + }, + { + "time": "17:06:35", + "speaker": "Alex Martemyanov", + "text": "And the VS Code tech design moving forward and giving Apple weekly updates about it. And… Bye." + }, + { + "time": "17:06:56", + "speaker": "Dominik Kapusta", + "text": "I will respond to the tech design later today, hopefully today." + }, + { + "time": "17:07:00", + "speaker": "Alex Martemyanov", + "text": "Okay, so I hope it makes sense, I'll just… Ah, that's true." + }, + { + "time": "17:07:06", + "speaker": "Dominik Kapusta", + "text": "There are some comments from Diego already and Federico. If this sounds like…" + }, + { + "time": "17:07:11", + "speaker": "Alex Martemyanov", + "text": "Thank you. I feel like I cannot finish it today." + }, + { + "time": "17:07:16", + "speaker": "Dominik Kapusta", + "text": "If this sounds like something that will need a few extra files in the repository, which is what I think…" + }, + { + "time": "17:07:23", + "speaker": "Alex Martemyanov", + "text": "Yeah, basically, there is one script, or six script files in Scripts, VS Code directory, and a code workspace file that loads it." + }, + { + "time": "17:07:30", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm." + }, + { + "time": "17:07:36", + "speaker": "Alex Martemyanov", + "text": "Other, uh, other stuff it does by itself." + }, + { + "time": "17:07:38", + "speaker": "Dominik Kapusta", + "text": "Oh, okay." + }, + { + "time": "17:07:40", + "speaker": "Alex Martemyanov", + "text": "So it basically loads, generates the build server, generates the tasks and launch JSON." + }, + { + "time": "17:07:44", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm." + }, + { + "time": "17:07:46", + "speaker": "Alex Martemyanov", + "text": "Uh, to keep it not in the repository, and everything happens in the script." + }, + { + "time": "17:07:49", + "speaker": "Dominik Kapusta", + "text": "Mmhm." + }, + { + "time": "17:07:54", + "speaker": "Alex Martemyanov", + "text": "And removed by removing those three files if needed." + }, + { + "time": "17:07:54", + "speaker": "Dominik Kapusta", + "text": "So overall, yeah, overall the ask of this tech design is… Just adding these files really, because nothing changes. Mm-Hmm." + }, + { + "time": "17:08:03", + "speaker": "Alex Martemyanov", + "text": "Yeah." + }, + { + "time": "17:08:05", + "speaker": "Dominik Kapusta", + "text": "with the rest. That sounds good. Yeah. Okay, okay, okay, um… Good. Great. Thanks for that, um… yeah, I think we're… I think we're good, I think we're… Clear. If we're not, we'll iterate next month, next Tuesday. Uh, good." + }, + { + "time": "17:08:26", + "speaker": "Alex Martemyanov", + "text": "Yeah, on that one, the PR is basically ready, and uh… Confirmed working with some. Extensive tests. And I think… Even the VS Code remote debugging should be up soon as well. But the bottleneck is my review. attention that I have. Still have to complete the top priority and just… Iterate over all the stuff happening, including the communications." + }, + { + "time": "17:08:59", + "speaker": "Dominik Kapusta", + "text": "Sure." + }, + { + "time": "17:09:02", + "speaker": "Alex Martemyanov", + "text": "Quickly." + }, + { + "time": "17:09:02", + "speaker": "Dominik Kapusta", + "text": "Right, yeah. If you have a pull request sort of ready, or a draft pull request up, you can just link it there." + }, + { + "time": "17:09:07", + "speaker": "Alex Martemyanov", + "text": "Yeah, I have one… I have one here in search. And that window, this window, it's the crash. I hope it makes sense. Should be pretty clear, but, uh, just touch as many places in the code, and use a swift linter to prevent the…" + }, + { + "time": "17:09:27", + "speaker": "Dominik Kapusta", + "text": "Whoa." + }, + { + "time": "17:09:35", + "speaker": "Alex Martemyanov", + "text": "failures… possible failures in the future. And has, uh, Swiss law for…" + }, + { + "time": "17:09:39", + "speaker": "Dominik Kapusta", + "text": "Okay." + }, + { + "time": "17:09:41", + "speaker": "Alex Martemyanov", + "text": "to wrap the errors that we got, that we may extract from other places." + }, + { + "time": "17:09:46", + "speaker": "Dominik Kapusta", + "text": "Mm-hmm, mm-hmm, m." + }, + { + "time": "17:09:47", + "speaker": "Alex Martemyanov", + "text": "Um… yeah, it has tests, and… validation steps to to prove the clauses happening on on Rosetta. 86 architectures and to prove it does not. Let me just get this fixed." + }, + { + "time": "17:10:03", + "speaker": "Dominik Kapusta", + "text": "Nice. Okay, fine." + }, + { + "time": "17:10:07", + "speaker": "Alex Martemyanov", + "text": "And after that, I could switch to… Give it to priority telemetry, and I'll give an update in the project advisor's task at the time. Not getting everything ready by today, and uh…" + }, + { + "time": "17:10:20", + "speaker": "Dominik Kapusta", + "text": "Uh-huh." + }, + { + "time": "17:10:21", + "speaker": "Alex Martemyanov", + "text": "Because… Because of this work and. The crash and the. And the amount of tasks to be filled, including the plans and attribution data analysis." + }, + { + "time": "17:10:38", + "speaker": "Dominik Kapusta", + "text": "Good, sounds good. Alright." + }, + { + "time": "17:10:38", + "speaker": "Alex Martemyanov", + "text": "Smooth." + }, + { + "time": "17:10:42", + "speaker": "Dominik Kapusta", + "text": "Fine. Thank you very much. Have." + }, + { + "time": "17:10:45", + "speaker": "Alex Martemyanov", + "text": "Yep. Thank you, Drew, for…" + }, + { + "time": "17:10:47", + "speaker": "Dominik Kapusta", + "text": "Have a great rest of the day. See ya. Bye bye." + }, + { + "time": "17:10:49", + "speaker": "Alex Martemyanov", + "text": "I'm sounding this loud and everything. Yep, I'll…" + }, + { + "time": "17:10:53", + "speaker": "Dominik Kapusta", + "text": "No, don't worry. That's great." + }, + { + "time": "17:10:54", + "speaker": "Alex Martemyanov", + "text": "I'll get back to you on the…" + } + ] +} diff --git a/work/zoom-transcripts/2026-10-15 Dominik Kapusta's Personal Meeting Room 2026-10-15 16 05(GMT+6 00) nzWOuhyzSdCjNqMRh6X13w/transcript.md b/work/zoom-transcripts/2026-10-15 Dominik Kapusta's Personal Meeting Room 2026-10-15 16 05(GMT+6 00) nzWOuhyzSdCjNqMRh6X13w/transcript.md new file mode 100644 index 00000000..9afeea92 --- /dev/null +++ b/work/zoom-transcripts/2026-10-15 Dominik Kapusta's Personal Meeting Room 2026-10-15 16 05(GMT+6 00) nzWOuhyzSdCjNqMRh6X13w/transcript.md @@ -0,0 +1,345 @@ +--- +title: "Dominik Kapusta's Personal Meeting Room 2026-10-15 16:05(GMT+6:00)" +date: 2026-10-15 +zoom_note_id: "nzWOuhyzSdCjNqMRh6X13w" +source: "https://us01mynotes.zoom.us/nzWOuhyzSdCjNqMRh6X13w" +--- + +# Dominik Kapusta's Personal Meeting Room 2026-10-15 16:05(GMT+6:00) + +[Zoom My Notes](https://us01mynotes.zoom.us/nzWOuhyzSdCjNqMRh6X13w) + +## Transcript + +- **16:05:14 · Dominik Kapusta:** Ай Горю? +- **16:05:15 · Alex Martemyanov:** Oh. Still commuting, yeah. Much better, I think. And yeah, reaching you. +- **16:05:25 · Dominik Kapusta:** Отгод. Гуд. Туф. Ера. +- **16:05:27 · Alex Martemyanov:** Eventful week. Let's see. A lot of things happening in parallel. And yeah, for today, I kinda… Already tired. Probably still not 100% recovered. But, yeah, anyways, I tried to update our agenda. +- **16:05:45 · Alex Martemyanov:** Бад. Я. Энивэйс? +- **16:05:46 · Dominik Kapusta:** Я? +- **16:05:53 · Alex Martemyanov:** And, uh… Yeah, so basically… From the last update, from the last Friday's update on my top priority, there is… Not much of actual update happened since I spent most of the Monday. And… with the… It abuse the incident thing. The other stuff, and just get to the… +- **16:06:21 · Dominik Kapusta:** Ням? +- **16:06:24 · Alex Martemyanov:** Do the actual priority thing, and uh… Today, I'm… trying to get through it, and first of all, it's blocked with this, uh, domain name called Crash. The time kinda keep iterating. Miss Claude. +- **16:06:40 · Dominik Kapusta:** Вот краш вот. Краш. Свои? +- **16:06:42 · Alex Martemyanov:** The domain and the domain and code, the WebKit proxy error thing. +- **16:06:46 · Dominik Kapusta:** А. Аа, Окей? +- **16:06:49 · Alex Martemyanov:** Yeah, I'm just, uh… I'm just about to open it, and just final validation of the bills passing. I'm just basically ready, and I'll ping you if you can. Uh, it goes to a normal… normal release, since it's not… Not high occurrences are normally on the 86 machines, but anyways, it's naturally preceding the telemetry fix and all the other stuff. Yeah, and on the top priority, I got several stages. I think there is, um… Three, four. Even… Yeah, at least three VRs. Stacked PRs pending. So first of all, we need adjusting the attribution because currently it misses some identified points. And, uh, we need some proofs of it, actually. of the events actually happening. So basically, I've identified it to… The background issue is lock screen or unloading browser and the network process crash that may also. I don't know. We affected the CPM error and basically those like 80% of the telemetry. +- **16:08:18 · Dominik Kapusta:** Окей? +- **16:08:25 · Alex Martemyanov:** It got reproduced in the. Best homeless setup. That was made for evaluating the theories. So, if it goes well, we should… We should probably cover like 80% of those and hopefully receive some extra data to cover the rest. Um, so… That's moving, although I'm kind of feeling a little… Bring the trade. and all of this. Uh, but yeah, I was hoping to open everything today so we could review it tomorrow, but realistically… It's probably gonna be only the attribution fix, so request for today and the crash fix. And for tomorrow, yeah. I'll try to… Uh, to discuss it with Michal, if we can… We can get it through. +- **16:09:30 · Dominik Kapusta:** All right. Uh, okay. +- **16:09:32 · Alex Martemyanov:** So, yeah, later today, I'll give an update on the project, uh, when I… when I have the request open. +- **16:09:35 · Dominik Kapusta:** Mm-hmm. Yeah, sure. +- **16:09:40 · Alex Martemyanov:** So, it may be… +- **16:09:43 · Dominik Kapusta:** Yeah, uh, I'm looking at these fixed CPM breakage issues. Breakage. WebKit issues, I guess. Uh, and there are four subtasks, which… +- **16:09:51 · Alex Martemyanov:** Yep. +- **16:09:56 · Dominik Kapusta:** So there will be four pull requests? +- **16:09:57 · Alex Martemyanov:** All of them have contacts. +- **16:10:00 · Dominik Kapusta:** Double. +- **16:10:00 · Alex Martemyanov:** Yes, I guess so. +- **16:10:01 · Dominik Kapusta:** Mmhm. Okay. +- **16:10:03 · Alex Martemyanov:** I'm planning to… to give it some… details in the research and in the tasks themselves. on, uh… kind of describing the approaches, but yeah, it comes a bit later. So, yeah, it's to be updated. They'll post in a project a bit later today. +- **16:10:27 · Dominik Kapusta:** Sounds good. +- **16:10:28 · Alex Martemyanov:** So, yeah, last week. Last week after. All of that kind of got some toxication. Uh, which… Luckily gave me like a couple of days. To just get relaxed a little bit. Yeah, but meanwhile, yesterday, I got some… Oh, I… Got some time… like lazy white coding on the extra project projects. And I got some results you may have seen. So, basically, there is the tech design for the VS Code integration updated. Yeah, basically, I've posted the update. Thanks for all the input. +- **16:11:14 · Dominik Kapusta:** Mm-hmm. +- **16:11:18 · Alex Martemyanov:** And, uh, having all of that, I actually found a way that will work and, uh, that doesn't touch the current. +- **16:11:19 · Dominik Kapusta:** Yeah. +- **16:11:28 · Alex Martemyanov:** I mean, current project structure, it's, uh… It's a little… it's a small wrapper over the Xcode language. +- **16:11:38 · Dominik Kapusta:** Ahem. +- **16:11:38 · Alex Martemyanov:** The server, which uses the same architecture. Uh, as Xcode does for… +- **16:11:45 · Dominik Kapusta:** Mmhm. +- **16:11:46 · Alex Martemyanov:** sources indexing, and it used the same Swift build system. that Xcode27 is using under the hood now, so we should be pretty much aligned on this. Even though the repo or the project itself is pretty young, I think we could easily fork it since it's released. +- **16:11:57 · Dominik Kapusta:** Mmhm. +- **16:12:07 · Alex Martemyanov:** Really small rubber, and uh… And keep… +- **16:12:14 · Dominik Kapusta:** Okay. +- **16:12:16 · Alex Martemyanov:** And coupons, that's… for me. +- **16:12:20 · Dominik Kapusta:** Um… +- **16:12:20 · Alex Martemyanov:** Because of, kind of, security and privacy concerns, and uh… +- **16:12:24 · Dominik Kapusta:** Fine, yeah, yeah, I think it would require… Something like a vendor triage… dependency… Triage, or tool triage, whatever it's called, but it's essentially, like, a tool that we want to use, and… And because of that, we might want to perform some checks on it. +- **16:12:50 · Alex Martemyanov:** Yeah, there is a related question in the tech design, so basically I've assigned it to you if you can. And you may leave the comments on it. +- **16:12:58 · Dominik Kapusta:** Mmhm. +- **16:13:03 · Alex Martemyanov:** Yeah, so basically that should work, and… Keeping things moving and finally resolve the project. Maybe maybe a good thing to the. Career review thing. Like, moving the team forward and finishing the effort. And with the following… With the following tests update. I actually got it locally, so basically it's a buildable folder and unlinking the AppDelegate dependency. it just waits for, uh, for the tech design to be approved. Yeah, basically, it only depends on the main… main branch, it's not related to VS Code. But it works, iOS works with simulator. +- **16:13:52 · Dominik Kapusta:** Mmhm. +- **16:13:53 · Alex Martemyanov:** macOS network, everything just works. Oh… +- **16:13:57 · Dominik Kapusta:** That's good, that's good. +- **16:14:00 · Alex Martemyanov:** And yeah, there is only one issue about export build, and it's a package resolution thing that I was trying to get rid of, but maybe I'll get through it with some local fork. Just for myself or for anybody who's interested, if… if it would be the use case. Basically, I expect a couple of… team members to adopt it, or at least take a look, maybe it works for somebody. Especially having the next things, which are in my, uh… Stick in the artwork. So basically, I. Uh, pretty much completed the, uh, virtual machine manager thing that I mentioned, kind of, half a year ago. Started work on it, so it's migrated to… Another build system… It supports remote machines like old MacBook that just works. You can see it. Sorry. It just works directly from MCP, and even if I can crash machines, but I won't advertise on the team, but anyways, I have one. And be used for virtual machines testing as well. Uh, it just works. So, um, Claude and ChatGPT, when I ask to… +- **16:15:20 · Dominik Kapusta:** Okay. +- **16:15:25 · Alex Martemyanov:** validate the tests on macOS 27 or macOS 12, it just says, okay, I will set up the virtual machine, I'm getting the lease, I've run the tests, the bug is reproduced, it's fixed. Uh… So that's another part of the… AR work and developers help, and there is integration for VS Code as well, so you could just run the virtual machine and run the build. from VS Code, and there is no hanging at launch, it just works natively, and you can run UI tests in it, not blocking your main working machine. So, basically, the project is moving really, really well. +- **16:16:06 · Dominik Kapusta:** Mm, mm-hmm. +- **16:16:07 · Alex Martemyanov:** And I expected to have some to make some contribution to the team when I when I finish. Approving this. +- **16:16:18 · Dominik Kapusta:** Yeah, that's good. I mean, it's a lot. It is a lot. So allow me to digest it. +- **16:16:20 · Alex Martemyanov:** Great, thank you. +- **16:16:26 · Dominik Kapusta:** Piece by piece. But, uh… Um… Can maybe talk about the tech design later. VS Code and Xcode preferably server. Fine. The other thing you've just mentioned, it's what's on that diagram. +- **16:16:55 · Alex Martemyanov:** Uh, the diagram, yeah, that's just another quick, uh, quick call of yesterday's date. +- **16:16:56 · Dominik Kapusta:** In the agenda? +- **16:17:02 · Alex Martemyanov:** From my bed. Oh… It's, uh, basically… Agent setup analysis for automatic bug and crash fix workflow. I just… had its one short run, and asked to summarize everything we've had for a century, and what Android and Windows teams have. Uh, so this is kind of first one-shot diagram that it came with, analyzing the signals. So we have, uh… manual trigger from Asana, like tagging or mentioning a bot. Uh, we have a new crash events, or we have a CI failure, uh, that, uh, first runs. a cloud agent or Linux with Sentry and Asana access, analyzes the code, the task, and. everything, and then runs an isolated runner on Bitrise. that reproduces UI tests or unit tests, collects the evidence, tries to fix, iterates, and proceeds opening pull requests with a fix or no hope. With automated MetaMoose and Basana comment. Not sent by a bot because of the incident one, and, but, posted by by the automation. +- **16:18:30 · Dominik Kapusta:** Hmm, yeah. +- **16:18:35 · Alex Martemyanov:** And then the last step, yeah, the bottleneck of the human review, the approval. Which, if in case of the test runs, the test runs… By the way, I just got another test run that just passed, and I'm probably gonna use the Fernando proposal to just merge it. Um, there's one self-review. +- **16:18:55 · Dominik Kapusta:** Amanda proposal. +- **16:18:58 · Alex Martemyanov:** Uh, they self-review for test fixes. +- **16:19:02 · Dominik Kapusta:** Ah, yeah, yeah, sure. +- **16:19:04 · Alex Martemyanov:** Yeah, so yeah, it's basically an automated run. fixing the… my local automators around fixing the Discover, DUI tests issues. Uh… So… It should run the same thing, but online using agent runners. And, uh… So yeah, basically we have a first. First AI iteration of it, so I could… Choose from what to move next when I have some time. +- **16:19:40 · Dominik Kapusta:** All right. What you're doing is… It's great in terms that… It's… These are great ideas for the team, for sure. Uh, the thing is, it is being worked on already in a few places, and it would be great to coordinate that work, or maybe join that work. Uh, we are currently… figuring out… Bitrise… well, not Bitrise, but, uh, essentially infrastructure for… Running Agentic workflows on… for Apple team. And… I said Bitrise because I'm involved in a Bitrise task, which is about Bitrise remote development environments, which is their new feature that they… where they just… +- **16:20:32 · Alex Martemyanov:** Okay. +- **16:20:41 · Dominik Kapusta:** just provide macOS virtual machines that you can use for that. They come with Xcode and Claude pre-installed, and… Yeah. Okay. What I was doing is I was trying to get the build to pass on these machines, like, set everything up… as close to our CI setup as possible. And I think it worked in the end, I need to… Uh, leave for a moment today, but… Yeah, I think it works. +- **16:21:17 · Alex Martemyanov:** Yeah, you mean the… the runner automation thing? Yeah, again, I, uh, haven't spent… +- **16:21:20 · Dominik Kapusta:** Yeah, we… +- **16:21:24 · Alex Martemyanov:** Actually, a minute on it. And just… it's just a one-shot research. +- **16:21:30 · Dominik Kapusta:** Just the discussion topic. Okay, okay, fine. Yeah. +- **16:21:33 · Alex Martemyanov:** Yeah, so basically a discussion topic to probably involve me into these flows and, yeah, start the coordination. +- **16:21:37 · Dominik Kapusta:** Mm-hmm, sure, sure, so I can tell you, I can tell you where we are, I can tell you where we are. We are considering… Actually, one thing that is happening is… Um, enabling… Simple Agentic workflows, like one shot. essentially workflows on GitHub Actions. And, uh, so the idea is you have a workflow where you… Or the prompt? is the input. And the. A workflow just runs, and whatever… whatever the output needs to be, it is. Is it, like, a pull request, or some artifact, whatever. But essentially, like, think of, I don't know, fix this crash, and then it ends up with a pull request. Yeah, um… There is a small problem. We aren't allowed to use… Anthropic. API keys in public repositories. So. To work around that, we are setting up a private repository that will be empty. And just have that token? And the workflows. And the workflow would clone the monorepo. +- **16:23:04 · Alex Martemyanov:** Mmhm. +- **16:23:04 · Dominik Kapusta:** But it would run in a private repository otherwise. But it would clone the monorepo, and work on the monorepo, and open the pull request in the monorepo. Uh, so the only… the only complication here is that it can't be the monorepo, can't live in the monorepo, but it lives in a private repository that essentially has write access to the monorepo, and that's it. So this is for a single… Like, single-shot, uh… tasks? Where you just… Essentially, you give a task to the agent, and… you don't want to talk to it in the meantime, you don't need to talk to it in the meantime, and then it comes with the result. For longer. Workflows, where you would like to… Intervene. In the meantime, or would you expect to be pinged by the agent? Uh, we can't do it in GitHub Actions, because you can't… stop the… stop the GitHub action workflow, or… essentially take over the control of it. So for that, we just need a remote machine. With… with a cloud session. And you could like SSH into that machine for instance or VNC into it and… And take over if needed. And that is being figured out. One possibility is AWS. The problem with AWS is it's $1400 per month per machine. So, we're also evaluating Bitrise on that, and Bitrise would be definitely cheaper, and it comes with… Well, the VM images are prepared for Apple development. They have Xcode, they have plenty of other tools. installed Ruby and so on and so on. So that's what we're… dealing with now, going through security triages and so on and so on. Um, oh. +- **16:25:17 · Alex Martemyanov:** What's the problem with the… With it. Why do we have to SSH to another machine? +- **16:25:28 · Dominik Kapusta:** Well, we don't have to, but… If we want to… we wouldn't be able to in a GitHub Action workflow. I'm. +- **16:25:40 · Alex Martemyanov:** Okay. +- **16:25:41 · Dominik Kapusta:** And, yeah, well, whatever, you don't need to SSH into it, but you might want to… Connect to a cloud session on such machine. to see… what's going on there, and I don't know, to… to provide further instructions to the agent, and so on and so on. Uh, I also… to be completely fair, I don't… fully follow that use case yet. I'm… I clearly understand the need for, uh, simple workflows, like, please fix this, please do this, and so on and so on. Make no mistakes. But these interactive sessions, they are a bit… A bit strange to me, but… Yeah, people that have more experience than me suggested that we would need this. Uh, I guess it may… it may be about, um… Just doing work on a remote machine, rather than a local machine. Just like this, right? So you can do it locally, but you can also do it remotely. I'm not entirely sure how much it would, uh… we would benefit from it. Umm. Let's see. +- **16:27:04 · Alex Martemyanov:** Yeah, like having a… remote testing machine with BNC, and uh… Agent runs, and even remote building from… from the VS Code. Uh, it may be a good option, since not everybody has, like, as new of machine as I… of machines as I do. And ability to run those. So probably we could. +- **16:27:25 · Dominik Kapusta:** Mm-hmm. +- **16:27:29 · Alex Martemyanov:** Integrate. And that point as well, somehow. So just maybe ping me in the related tasks and. +- **16:27:34 · Dominik Kapusta:** Yeah, yeah. +- **16:27:38 · Alex Martemyanov:** I'll see where can we… Integrate. and distribute the work. Okay. +- **16:27:55 · Dominik Kapusta:** Yeah, I can try to involve you here and there or just give you links. Because, because, because, because one of them is this one. This is one of them. That's for the simple workflows and the other one is… this. And this Bitrise thingy is a subtask of. of a full project called "Find an alternative to Cursor Cloud Agents to safely run autonomous workflows". +- **16:28:48 · Alex Martemyanov:** Mm-hmm. +- **16:28:53 · Dominik Kapusta:** One other limitation of GitHub Actions is that. Any workflow can only run for 6 hours, so in case we have some long, long jobs… It would just stop after six hours. and be deleted and forgotten. +- **16:29:12 · Alex Martemyanov:** Yeah, generally, the ramps should not… List for cigarette rollers. +- **16:29:17 · Dominik Kapusta:** Yeah, they shouldn't. I agree. Oh, all right. +- **16:29:29 · Alex Martemyanov:** Yeah. +- **16:29:31 · Dominik Kapusta:** All right, so that's this. For the tech design. I will have a look later. I saw there are some comments already, and overall the reception is… is better. Probably because… It's opt-in, and it doesn't change anything that we have. Um… Yeah, some of the requirements of your previous design were… hard to… Hard to just, you know… agree on without, without, uh… +- **16:30:06 · Alex Martemyanov:** Accept. +- **16:30:10 · Dominik Kapusta:** No. Like… It was just, essentially it was just refactoring, refactoring a lot of code in order to maybe have some benefits, but also there were, like, a significant part of these benefits would be achievable without all these changes, so… I'm glad that we're gonna be switching to buildable folders, which will simplify the project file drastically. And then there's this other thing. that I have forgotten in the meantime. Oh, yeah, uh, removing the host application from tests. +- **16:30:48 · Alex Martemyanov:** Uh, I think it's not removing, but uh… Because since we run it in Xcode and not as a package, we cannot remove the host application. +- **16:31:01 · Dominik Kapusta:** But you don't launch it in UI tests, in unit tests. +- **16:31:04 · Alex Martemyanov:** Relaunch it. +- **16:31:06 · Dominik Kapusta:** But if you set it to none, do you still launch it? +- **16:31:06 · Alex Martemyanov:** But, uh… You cannot launch it if you don't have it. Because it's run against the host application from Xcode. And if you want to run to remove the host application, you have to convert it to the library as it was in the initial design. +- **16:31:26 · Dominik Kapusta:** So what happens? If I go here… and here and do this. What does this really change? +- **16:31:38 · Alex Martemyanov:** Mmhm. I suppose it won't. Build the tests. +- **16:31:51 · Dominik Kapusta:** It works. It's what I wrote in the comment on your initial tech design. I set it to none, and it works. The only tests that are failing were the CBR… +- **16:31:52 · Alex Martemyanov:** Or maybe, uh… Excuse me. +- **16:32:03 · Dominik Kapusta:** Tests. No. +- **16:32:09 · Alex Martemyanov:** Okay, good. I'll reiterate about it. +- **16:32:12 · Dominik Kapusta:** Okay. +- **16:32:12 · Alex Martemyanov:** Anyways, uh… anyways, it's ready without… even without it. And, uh… The fix there was just to… To inject the… An empty app delegate. +- **16:32:26 · Dominik Kapusta:** Yeah, yeah, that was… that was the thing that came to my mind initially. We can… we can have another app that I get, and then… +- **16:32:26 · Alex Martemyanov:** Instead of the apps that I'm gonna get. +- **16:32:36 · Dominik Kapusta:** I think it's a build setting, the app delegate is also a build setting somewhere, or the… yeah. +- **16:32:39 · Alex Martemyanov:** Yeah, so anyways, I'm getting to it, and it's independent from VS Code or anything else, and when I… +- **16:32:44 · Dominik Kapusta:** Yeah, yeah. Mm-hmm. +- **16:32:47 · Alex Martemyanov:** Wipe, wipe out the current priority work. +- **16:32:53 · Dominik Kapusta:** Mm-hmm. +- **16:32:53 · Alex Martemyanov:** On my table, and uh… I'll come back to it and. And, uh… and modularization items as well. +- **16:33:05 · Dominik Kapusta:** Mmhm. +- **16:33:05 · Alex Martemyanov:** So, maybe when, uh… when we have the browser modularized, like, finalized, we could reiterate over the SPM package, as it would be a logical next step, or maybe we didn't change. Uh, with the next, next code release. Uh, like, Apple providing several… +- **16:33:23 · Dominik Kapusta:** Hmm. +- **16:33:25 · Alex Martemyanov:** Steps further. +- **16:33:26 · Dominik Kapusta:** Mm-hmm. +- **16:33:27 · Alex Martemyanov:** to the SPM compilation, as it seems. Uh, so… yeah, we'll get there. +- **16:33:35 · Dominik Kapusta:** Okay. Okay, nice. One other thing that we need to do today. which is slightly overdue, is the… Continuous development check-in. Which means we should talk about growth areas and shoutouts as well, actually, of course. They are here. Yeah, it's a private task, but you have access. um… So we… We talked about… uh, the communication overall. And… um… For this… Like then, what was the next steps was that you're moving again from ON to OE into a new… Environment, new people… And there was just this reminder to use your project advisor, to bring questions, to… to provide updates in the project and so on and so on. And… What do you think about… About this growth area, about the other growth area perhaps as well, because we can keep it, we can… Call it done. We can create a new one. My. Personal feeling is that. It still needs some work. But curious about your perspective. +- **16:35:40 · Alex Martemyanov:** So, I don't know… Very good question. So generally, we… It's the last… iteration. We've had several projects, like. And… The most complicated one is probably the current one, and uh… +- **16:35:58 · Dominik Kapusta:** Mmhm. +- **16:36:01 · Alex Martemyanov:** So general directions there were initial communications over the project structure. I will proceed and. +- **16:36:11 · Dominik Kapusta:** Mmhm. +- **16:36:12 · Alex Martemyanov:** Several need more time suggesting the roadmap. Oh. Otherwise, there were just regular project updates on the current state and expectations with some corrections as required. And… So about bringing question and doubts. I'm not sure here, because I think there were a couple of. question and doubts that I brought to the project advisor on what. What's better to do, or how to iterate over it, or should we apply this, or have a bigger iteration on the better solution? +- **16:36:49 · Dominik Kapusta:** Mm-hmm. Mmhm. +- **16:36:56 · Alex Martemyanov:** Or, uh… Aligning on the… on the roadmap, I mean, on schedule, like on reviews and… our release dates. So… Generally, from my perspective, I… Try to keep it. Up to date and keep people updated when it's… when something happens, or like, nothing happens if I… +- **16:37:25 · Dominik Kapusta:** Yeah, okay. +- **16:37:28 · Alex Martemyanov:** Um, if there is… if there is a slowdown, for example, for some reason. +- **16:37:29 · Dominik Kapusta:** Right. Yeah, yeah, and that's good. If you… So when you reach out to the project advisor, do you do it on Inasana or Mattermost? +- **16:37:48 · Alex Martemyanov:** Mmm… +- **16:37:48 · Dominik Kapusta:** Is it in the comms task or some other tasks? +- **16:37:53 · Alex Martemyanov:** I think it's mostly in MetaMOST, but sometimes there is some… So basically, project update iteration, if there was some… +- **16:37:56 · Dominik Kapusta:** Mmhm. Mmhm. +- **16:38:02 · Alex Martemyanov:** If there was some decision. +- **16:38:04 · Dominik Kapusta:** Mm-hmm. Good. What I can… suggest, maybe, is… because, like, at least looking at, uh, at this task… +- **16:38:18 · Alex Martemyanov:** Yeah, there is not much of the communication happening on the top. +- **16:38:18 · Dominik Kapusta:** for… You know, there is not much communication, but there are also two instances of, uh… career advisor asking… I mean, sorry, project advisor asking you for… for the status? +- **16:38:34 · Alex Martemyanov:** Uh, and actually, I was just writing the project update, and in the moment, he was asking. +- **16:38:34 · Dominik Kapusta:** And. +- **16:38:40 · Alex Martemyanov:** Uh, about the status… +- **16:38:41 · Dominik Kapusta:** Mmhm. +- **16:38:43 · Alex Martemyanov:** And… +- **16:38:43 · Dominik Kapusta:** And. +- **16:38:46 · Alex Martemyanov:** And yeah, you mean making the communication more visible and go through the communication tasks? +- **16:38:50 · Dominik Kapusta:** Making the… if the communication happens, making it visible would be great. what I noticed, uh… Diego did on a couple of occasions. We were on a Zoom call, and he would put a summary of a Zoom call in the communication task. Just, you know, just some bullet points, just to… +- **16:39:14 · Alex Martemyanov:** Mm-hmm. +- **16:39:17 · Dominik Kapusta:** to make it clear that the communication happens. And it's also valuable… of course, it's valuable to everyone who reads the task, but it's also valuable to yourself and to the project advisor, because project advisor. I mean, more to the project advisor, of course, because you… this is your top priority, but this is not project advisor's top priority, and they may have more work, and they may be forgetting things, so it's great to… To just… Note down. Oh. whatever is happening, right? If you… even if you chat on Mattermost, and you have, like, a… some exchange of messages in Matrimos that is valuable, and where you learn something. It's a great… Um, great, uh, habit to… to just, you know… put it in Asana as well. Just as a documentation that things are happening. When it comes to project updates. It's… It's probably… I wanted to say that, well, I can see you're posting frequent updates when needed. There's an update from 7th of October and then the update from 9th of October. Because some people get fixed on that. rows weekly… I mean, write weekly updates, and then they put one update a week, and they're fine with that. But it's not… always enough to just write one update a week. So that's good. But… What I would like to see… And this CPM project is not looking… I mean, it's looking fine, right? People seem to be… okay with your communication there, but then there is… like, the communication does not end on your project, your top priorities. We had an example with this VS Code initiative where… Well, some comments started popping up on your project task. And you remember, like, I was pinging you to put a comment there, uh, like. Calm them down, because the situation was that some people wrote some comments and… The last one was from Juan. The last one was from Juan, and um… And he just… asked you explicitly, could you talk more about the benefits of the project structure, cleanup, and coding standards we'll get from these changes? And… I know that. you… your idea was to write a tech design, and that's also what we agreed on on Apple Weekly. Another weekly meeting, I think it went well overall, where you calmed people down, essentially. But not everyone was on the call. And then if you come back to that project, you see that project in Asana, and you still see Juan's comment there, which is unanswered. It would be great to respond to it. Could you talk more about the benefits of the project structure cleanup? I mean, yes… I'm about to write everything down in a tech design. So we'll see, and… yeah, I saw your comment, I read your comment, and I will address it. Sometimes this is… Fine. Um, there were actually some… some agreements on the Apple Weekly Call that you could put in writing over there, like, yeah, you'll write the tech design, and then we'll talk about it, and it's not… what was very important to me, I think, at least, was that… it's not strictly about VS Code integration, but also it's… It's a way of speeding up builds, cleaning up project structure, and so on and so on. So… This could have been put there in a comment. Otherwise, people were… a bit lost in all of this, and they were… Actually, I have to say they were afraid. +- **16:44:17 · Dominik Kapusta:** about what's happening, because it's a lot of changes, and… Of course, we don't like changes, no one likes big changes, especially if they are not clearly backed by some proper reasoning. Um, so… So that was that. And then when I… then when I… kept pinging you for a couple of days, you told me, oh, I'm writing a tech design, I'll update later, I'll say, fine. And then you only wrote the comment that the tech design is ready, so please go read a tech design. Go and retake design. Which, yeah, it was a bit… a bit late as well, but uh… What I… what I suggested you on our Mattermost chat, it's essentially, you know, just put, like, two, three sentences there to calm people down, and you should be fine. Mmm. No. So… So that's something that… That would be great to see going forward. I think. Because… Let me… put it this way. It's clearer than when projects are going… The right way, or… Or not, but as long as it's… On the technical side, good or bad, whatever, you're handling it perfectly. You're just, okay, this is my project, this is the plan, these are the tasks I'm working on, when I'm done with this, I'm gonna do this, and so on and so on. And you're giving proper updates, you're keeping everyone… Well informed. And then… when sometimes something happens, and also, you're fine, like, calling me mid-mortems to decide on technical stuff, and so on, and so on. But if there is this… This, how to say, um, well, someone raising something, uh, having doubts. Then it gets tricky. Essentially it gets tricky and you may be. A bit lost, I don't know. I'm just still trying to… +- **16:47:08 · Alex Martemyanov:** Yeah, I just tried to go through the actual comment to reason about it and to. +- **16:47:15 · Dominik Kapusta:** Yeah. +- **16:47:16 · Alex Martemyanov:** Basically, to iterate over it so it gets to my… Incoming queue, and uh… +- **16:47:21 · Dominik Kapusta:** Mm-hmm. +- **16:47:23 · Alex Martemyanov:** When I reach to it, I, yeah, answer, basically. +- **16:47:26 · Dominik Kapusta:** Mm-hmm, mm-hmm, mm. +- **16:47:30 · Alex Martemyanov:** And some comments do require some extra checks. +- **16:47:34 · Dominik Kapusta:** Mmhm. +- **16:47:35 · Alex Martemyanov:** Uh, switching contexts and, uh, especially having those run as a parallel project. +- **16:47:37 · Dominik Kapusta:** No. +- **16:47:42 · Alex Martemyanov:** or background projects to the priority. And it may be, yeah, it may require some extra efforts. To marry those. +- **16:47:54 · Dominik Kapusta:** You know. +- **16:47:56 · Alex Martemyanov:** There's really the incoming, um… Incoming backlog. +- **16:48:05 · Dominik Kapusta:** I'm thinking how to… What to do? to also avoid… Being pinged. for updating your project status. I understand that there was a coincidence, like, Michal commented, okay, so how is it going, what are the next steps, and you were just writing an update. But. Yeah, maybe… +- **16:48:37 · Alex Martemyanov:** Yeah, so basically there is a milestone at the end of the week and my evening of Fridays and there is some events like mid-mortems or some plan changes or some re-evaluations. +- **16:48:41 · Dominik Kapusta:** Mmhm. Mmhm. +- **16:48:52 · Alex Martemyanov:** That I'll post midweek. And, uh… +- **16:48:54 · Dominik Kapusta:** Hmm. +- **16:48:55 · Alex Martemyanov:** Generally, otherwise, when, uh… it feels natural for me to post an update, like, when I finish my work on Friday, just to hand over to the, uh… +- **16:49:02 · Dominik Kapusta:** No. +- **16:49:06 · Alex Martemyanov:** Uh, to the ones from the US side that are usually running the objectives, and uh… +- **16:49:09 · Dominik Kapusta:** Mm-hmm. Mmhm. +- **16:49:11 · Alex Martemyanov:** it feels kinda fine, posting an update in the morning when I didn't finish, and I don't see the outcome yet, and… It's kind of. It may get tricky. +- **16:49:25 · Dominik Kapusta:** Okay. Yeah, uh… Oh, okay, okay. All right. Fine, but I will… I would still keep that growth area here, because I think this is the most important thing for you right now. It's to… to be… +- **16:49:57 · Alex Martemyanov:** I'm trying to… To work with it from the different perspective and having some. Yeah, basically, I've also added to the agenda, like, the, uh, the personal OS setup that. And that keeps growing in parallel. I already had some. Local agents analyzing my past work and. current work and just prepare the workflow for the. current status analysis and comparing it to the local work that is being done and tracing the communication requiring my reactions. Just to keep things in focus and maybe post some notifications as… as is required. So to get myself like pinged that. Okay, you already like hyper focus to this task like for 6 h, you should stop for today. Post an update and answer for these 3 comments. So this is the. +- **16:50:51 · Dominik Kapusta:** Mm-hmm, mm-hmm. Yeah. Yes. +- **16:51:03 · Alex Martemyanov:** should be the case and it's… It's already starts to show something. Building up from it. +- **16:51:11 · Dominik Kapusta:** Did you say you put it in the agenda? +- **16:51:12 · Alex Martemyanov:** Oh. No, uh, yes. Uh, yes, I put it to the, uh… The agenda. +- **16:51:24 · Dominik Kapusta:** Can't find it. +- **16:51:24 · Alex Martemyanov:** Right. Hmm. Where is it? +- **16:51:33 · Dominik Kapusta:** I don't know. +- **16:51:35 · Alex Martemyanov:** Sure, it was there. It was in the… Good. Not here. Okay, let's put it here. It was the update that was, uh… the old content, basically, I updated it. Maybe… maybe you just got something from it. +- **16:51:56 · Dominik Kapusta:** Oh. Okay, in the old path. Mmhm. +- **16:52:46 · Alex Martemyanov:** And… Yeah. So basically what's, it's done there, it's, monitors the activity watch, active window, of course, locally, related to the local work trees, to Asana tasks, loads, the Asana task. +- **16:53:27 · Dominik Kapusta:** Mm-hmm. +- **16:53:29 · Alex Martemyanov:** full listing and summarizes it to the short project status and key decisions. And, uh, when the new events arrive, uh, they are updated. Um, so… In the perfect world, it should, like… Group up, analyze my current day workflow, analyze the… +- **16:53:49 · Dominik Kapusta:** Mm-hmm. +- **16:53:51 · Alex Martemyanov:** week, weekly, uh… weekly plans and career plans and mix it in a balanced set of. Oh. plans and nudges like notifications to react on something or to. Minish Lee. Focus on context switching. It starts getting some shape, so it's currently on the state of current local agent output. Of course, it should be gone through manually in my free time, and I should see the actual project status and what I got from it. And how it understands it, so there's no… Mmhm. Doubling source of truth. And yeah, after it, I'll build something on top of it. Meanwhile, it led some consequences with the token solar usage. +- **16:54:58 · Dominik Kapusta:** Thank you. +- **16:54:58 · Alex Martemyanov:** So I got commented from Kane. Uh, asking me to share the actual results I've got from spending. the quarters. the first week of October. +- **16:55:13 · Dominik Kapusta:** Wow. +- **16:55:15 · Alex Martemyanov:** Yeah, um… I'm gonna share it later. Probably. +- **16:55:23 · Dominik Kapusta:** Interesting. +- **16:55:25 · Alex Martemyanov:** And… +- **16:55:25 · Dominik Kapusta:** So, what was it? You exhausted the quota, or you have higher quota already? +- **16:55:29 · Alex Martemyanov:** Yeah, basically, I've adjusted the quota, and I've requested a quota raise for Claude, and I got raised the quota. +- **16:55:35 · Dominik Kapusta:** Yeah, and then they are asking for what you've done with it. +- **16:55:39 · Alex Martemyanov:** Yeah, unboxing what was happening and what was going wrong. So basically, it's just the default Opus that I have set here again. Let's just, especially on the high level. +- **16:55:51 · Dominik Kapusta:** Was was it? Was it 5.5? +- **16:55:54 · Alex Martemyanov:** Yep. Yeah, Opus 5.5, the org default, set for high, it's uh… +- **16:55:56 · Dominik Kapusta:** Oh. +- **16:56:01 · Alex Martemyanov:** It just burned another 200 of bucks yesterday for the test iteration work, because I… +- **16:56:04 · Dominik Kapusta:** Hmm. Mm-hmm. +- **16:56:08 · Alex Martemyanov:** Started it that way and forgot to switch it back. +- **16:56:11 · Dominik Kapusta:** Hmmm. +- **16:56:11 · Alex Martemyanov:** So and it's really easy to to burn 200 there. So 5 days of work, and you have the 1,000 out. +- **16:56:12 · Dominik Kapusta:** Okay. Yeah, sure. +- **16:56:18 · Alex Martemyanov:** So nothing special, actually. +- **16:56:21 · Dominik Kapusta:** Yeah. Okay. +- **16:56:21 · Alex Martemyanov:** Um… So I'll probably try to mention it, that we should set the default model. to another one, because it says Opus by default, because it's set as ORG default. But yeah, otherwise there were some outputs from it. +- **16:56:36 · Dominik Kapusta:** Hmm… +- **16:56:41 · Alex Martemyanov:** like the UI test, the CPM web extension. 3 pull requests, and… Countless iteration of a revolution with virtual machines and all this setup. Actually, run with it, and… So it got the job done, but… The burning is still… +- **16:57:04 · Dominik Kapusta:** Interesting, interesting. I just saw, I just checked and it looks like I'm on medium effort because I had the medium effort set for Fable. I was using Fable on medium effort. +- **16:57:04 · Alex Martemyanov:** I've looked at my leggings. +- **16:57:19 · Dominik Kapusta:** And I switched back to Opus 5.5, and I kept medium effort. I didn't mean to keep medium effort, but I have very, very, very, very low usage this month. +- **16:57:30 · Alex Martemyanov:** Actually, Sonnet is using a reasonable amount of token, I say, and high effort, because I usually use high effort for some larger topics, especially. +- **16:57:37 · Dominik Kapusta:** Okay. +- **16:57:45 · Alex Martemyanov:** when I just run it, okay, evaluate this bug from Asana, run the test, fix it, and then come up with a PR, so I can check the final result and not iterate on every stage. And if I set medium effort, it just loses context, compacts it, and starts doing some… +- **16:57:50 · Dominik Kapusta:** Mm-hmm. Mm-hmm. +- **16:58:01 · Alex Martemyanov:** Some bullshit, usually. +- **16:58:04 · Dominik Kapusta:** Right. +- **16:58:06 · Alex Martemyanov:** But yeah, Sonnet is, uh, Sonnet or Fable is pretty good at it, and I just should not forget to switch it back from Opus. +- **16:58:15 · Dominik Kapusta:** Yeah. Uh, alright… +- **16:58:22 · Alex Martemyanov:** So yeah, coming back to the updates. +- **16:58:22 · Dominik Kapusta:** Override. +- **16:58:28 · Alex Martemyanov:** I'm… I'm working on that. +- **16:58:31 · Dominik Kapusta:** Mmhm. +- **16:58:31 · Alex Martemyanov:** So I have that that points to. To provide some updates and try to. To catch it if it requires some more attention and post updates. Earlier, for example, I have one pending from Kirby and some pixel not being reported. Mmm… I'll probably just pause it. I have to manage my top priority and answer later this week. This weekend's tomorrow. Okay. Uh, yeah, I'm working on it. And, uh… And, uh, and, and… Anything else on the, uh… On the growth areas. +- **16:59:23 · Dominik Kapusta:** Only growth areas… I think we should also keep the other one for… About. Essentially growing others. So that's for team leadership, which means reviewing stuff, which you… have done a nice job for Andre. I'll try to get feedback from him. +- **16:59:50 · Alex Martemyanov:** And it was… +- **16:59:53 · Dominik Kapusta:** Umm. +- **16:59:53 · Alex Martemyanov:** It was, uh… yeah, I tried… I mean, it was a lot of, uh… a lot of work, actually, spent on the reviews and back and forth and all of that, and… +- **17:00:03 · Dominik Kapusta:** Yeah, and it may be overwhelming, it may be annoying, but I also… +- **17:00:04 · Alex Martemyanov:** that… Goes like an. +- **17:00:11 · Dominik Kapusta:** I also heard from Andre that. Does your good reviewer? I'm going to send him a feedback request for that. +- **17:00:19 · Alex Martemyanov:** Yeah, training every day on Claude and Codex. +- **17:00:22 · Dominik Kapusta:** Yeah, so that was fine. We got feedback. Have you seen feedback from Max? +- **17:00:32 · Alex Martemyanov:** No. +- **17:00:33 · Dominik Kapusta:** It arrived yesterday. Uh, let me share… It's here. +- **17:01:04 · Alex Martemyanov:** And… Thanks. And… +- **17:01:18 · Dominik Kapusta:** which also… +- **17:01:18 · Alex Martemyanov:** Okay, 100. +- **17:01:21 · Dominik Kapusta:** What was that, sorry? +- **17:01:21 · Alex Martemyanov:** Yes, here we are. Oh, for months. +- **17:01:25 · Dominik Kapusta:** Yes. Have you read it? +- **17:01:28 · Alex Martemyanov:** Hmm… Okay. Mm-hmm. +- **17:01:50 · Dominik Kapusta:** Yeah, so, um… +- **17:01:53 · Alex Martemyanov:** Again, this is the career advisor task. +- **17:01:54 · Dominik Kapusta:** This is… This is also… I, sorry, what was that? +- **17:01:58 · Alex Martemyanov:** It's a visibility question. +- **17:02:00 · Dominik Kapusta:** I don't understand. +- **17:02:00 · Alex Martemyanov:** The career advisor task communication thing that. +- **17:02:04 · Dominik Kapusta:** The project advisor task. +- **17:02:07 · Alex Martemyanov:** Project advisor cost, right? +- **17:02:07 · Dominik Kapusta:** Yes, yes, yes. Yeah, yeah, so that's that. I don't know what to say, just remember about that, because the previous feedback from Alessandro was really, really good. And I was like, ah, that's amazing. +- **17:02:27 · Alex Martemyanov:** Yeah, generally we kept in touch with Alessandro, and probably he was the… Only one, and the, uh, ODRIs were updated during the meeting… during the meetings, the stand-ups. +- **17:02:38 · Dominik Kapusta:** Uh-huh, yeah. +- **17:02:38 · Alex Martemyanov:** Uh, so there was no… nobody else, uh, involved there. Here in the status, it may look like. +- **17:02:44 · Dominik Kapusta:** Mm-hmm. +- **17:02:47 · Alex Martemyanov:** Because, uh, the project advisor communications in the summer look pretty much the same, actually, and I just… +- **17:02:53 · Dominik Kapusta:** Mmhm. Mmhm. +- **17:02:56 · Alex Martemyanov:** reached out to him directly on Mattermost, most of the times, and posting the project update in the… in the main desk. +- **17:02:59 · Dominik Kapusta:** Mm-mm. I see. Yeah, yeah. +- **17:03:03 · Alex Martemyanov:** So having no real discussions happening in the project advisor tasks. +- **17:03:08 · Dominik Kapusta:** Right, right. +- **17:03:09 · Alex Martemyanov:** That probably should come up with some kind of discussions to be put in there. +- **17:03:11 · Dominik Kapusta:** Oh. Yeah, probably, you know, don't do anything for the sake of doing it, but just… Documenting and the chats in that async task is a good habit to have. Yeah, um… We're also waiting for feedback from Michal. So we'll see. And I'll send one out to Andre. For now, I think let's keep your… let's keep your growth areas. So, yeah, focus on… I mean, keep communication in mind. And not only into priorities. +- **17:04:03 · Alex Martemyanov:** Okay, I'll just post an update today, probably that we discussed today about the project, and we're not getting up with all the PRs today. +- **17:04:14 · Dominik Kapusta:** Hmm, hmm. Fine. Uh, yeah, and the other one is leverage your functional skills to ensure that your peers keep a high quality bar. And I'm going to document the progress and the progresses that you've worked with Andra. Have you also commented on… Yeah, you have. You have commented on the ship review. So that's great. +- **17:04:37 · Alex Martemyanov:** On the ship review, on tech design. +- **17:04:39 · Dominik Kapusta:** Mmhm. +- **17:04:41 · Alex Martemyanov:** There was and the. And the VS Code tech design discussion and iterations. +- **17:04:46 · Dominik Kapusta:** Yeah, yeah, yeah, yeah, sure, sure. For tech designs here, for tech designs, we're looking for examples when you were the reviewer. +- **17:04:48 · Alex Martemyanov:** I guess. +- **17:04:56 · Dominik Kapusta:** So. Next time. Uh, and yeah, if there's something, uh, something, uh. that I spot that you could be a reviewer for, I will… I will arrange it. So that you could do it for a tech design. Good. +- **17:05:18 · Alex Martemyanov:** Okay… +- **17:05:22 · Dominik Kapusta:** I'm going to update it soon. Not many updates, anyway, in the Grove Areas. The Grove Areas stay. I'm gonna add a new shoutout, and slightly rework the Grove Areas, and that's it. For the… for the… this VS Code work… I think we're done. Your last comment was really good, like acknowledging everything and closing it and opening a new one. The new one, it is a little bit of a surprise, it comes so quick, so fast. That, yeah, people may be wondering… what are you doing in your free time? Which is… I know what you're doing, but it may be strange. +- **17:06:06 · Alex Martemyanov:** Yeah, basically it was… In my bed yesterday, just with clothes. +- **17:06:10 · Dominik Kapusta:** Mmhm. No. +- **17:06:12 · Alex Martemyanov:** Just to iterate over it. +- **17:06:15 · Dominik Kapusta:** Mmhm. +- **17:06:15 · Alex Martemyanov:** So… +- **17:06:19 · Dominik Kapusta:** Fine. +- **17:06:21 · Alex Martemyanov:** Yes, that's in the technical leadership and the… +- **17:06:21 · Dominik Kapusta:** Good. I'll… +- **17:06:25 · Alex Martemyanov:** We integrate the agenda task. Uh, ship review, the comment on tech design… +- **17:06:32 · Dominik Kapusta:** Mmhm. +- **17:06:35 · Alex Martemyanov:** And the VS Code tech design moving forward and giving Apple weekly updates about it. And… Bye. +- **17:06:56 · Dominik Kapusta:** I will respond to the tech design later today, hopefully today. +- **17:07:00 · Alex Martemyanov:** Okay, so I hope it makes sense, I'll just… Ah, that's true. +- **17:07:06 · Dominik Kapusta:** There are some comments from Diego already and Federico. If this sounds like… +- **17:07:11 · Alex Martemyanov:** Thank you. I feel like I cannot finish it today. +- **17:07:16 · Dominik Kapusta:** If this sounds like something that will need a few extra files in the repository, which is what I think… +- **17:07:23 · Alex Martemyanov:** Yeah, basically, there is one script, or six script files in Scripts, VS Code directory, and a code workspace file that loads it. +- **17:07:30 · Dominik Kapusta:** Mm-hmm. +- **17:07:36 · Alex Martemyanov:** Other, uh, other stuff it does by itself. +- **17:07:38 · Dominik Kapusta:** Oh, okay. +- **17:07:40 · Alex Martemyanov:** So it basically loads, generates the build server, generates the tasks and launch JSON. +- **17:07:44 · Dominik Kapusta:** Mm-hmm. +- **17:07:46 · Alex Martemyanov:** Uh, to keep it not in the repository, and everything happens in the script. +- **17:07:49 · Dominik Kapusta:** Mmhm. +- **17:07:54 · Alex Martemyanov:** And removed by removing those three files if needed. +- **17:07:54 · Dominik Kapusta:** So overall, yeah, overall the ask of this tech design is… Just adding these files really, because nothing changes. Mm-Hmm. +- **17:08:03 · Alex Martemyanov:** Yeah. +- **17:08:05 · Dominik Kapusta:** with the rest. That sounds good. Yeah. Okay, okay, okay, um… Good. Great. Thanks for that, um… yeah, I think we're… I think we're good, I think we're… Clear. If we're not, we'll iterate next month, next Tuesday. Uh, good. +- **17:08:26 · Alex Martemyanov:** Yeah, on that one, the PR is basically ready, and uh… Confirmed working with some. Extensive tests. And I think… Even the VS Code remote debugging should be up soon as well. But the bottleneck is my review. attention that I have. Still have to complete the top priority and just… Iterate over all the stuff happening, including the communications. +- **17:08:59 · Dominik Kapusta:** Sure. +- **17:09:02 · Alex Martemyanov:** Quickly. +- **17:09:02 · Dominik Kapusta:** Right, yeah. If you have a pull request sort of ready, or a draft pull request up, you can just link it there. +- **17:09:07 · Alex Martemyanov:** Yeah, I have one… I have one here in search. And that window, this window, it's the crash. I hope it makes sense. Should be pretty clear, but, uh, just touch as many places in the code, and use a swift linter to prevent the… +- **17:09:27 · Dominik Kapusta:** Whoa. +- **17:09:35 · Alex Martemyanov:** failures… possible failures in the future. And has, uh, Swiss law for… +- **17:09:39 · Dominik Kapusta:** Okay. +- **17:09:41 · Alex Martemyanov:** to wrap the errors that we got, that we may extract from other places. +- **17:09:46 · Dominik Kapusta:** Mm-hmm, mm-hmm, m. +- **17:09:47 · Alex Martemyanov:** Um… yeah, it has tests, and… validation steps to to prove the clauses happening on on Rosetta. 86 architectures and to prove it does not. Let me just get this fixed. +- **17:10:03 · Dominik Kapusta:** Nice. Okay, fine. +- **17:10:07 · Alex Martemyanov:** And after that, I could switch to… Give it to priority telemetry, and I'll give an update in the project advisor's task at the time. Not getting everything ready by today, and uh… +- **17:10:20 · Dominik Kapusta:** Uh-huh. +- **17:10:21 · Alex Martemyanov:** Because… Because of this work and. The crash and the. And the amount of tasks to be filled, including the plans and attribution data analysis. +- **17:10:38 · Dominik Kapusta:** Good, sounds good. Alright. +- **17:10:38 · Alex Martemyanov:** Smooth. +- **17:10:42 · Dominik Kapusta:** Fine. Thank you very much. Have. +- **17:10:45 · Alex Martemyanov:** Yep. Thank you, Drew, for… +- **17:10:47 · Dominik Kapusta:** Have a great rest of the day. See ya. Bye bye. +- **17:10:49 · Alex Martemyanov:** I'm sounding this loud and everything. Yep, I'll… +- **17:10:53 · Dominik Kapusta:** No, don't worry. That's great. +- **17:10:54 · Alex Martemyanov:** I'll get back to you on the… diff --git a/work/zoom-transcripts/index.json b/work/zoom-transcripts/index.json old mode 100755 new mode 100644 index d64d9a47..85e8bb84 --- a/work/zoom-transcripts/index.json +++ b/work/zoom-transcripts/index.json @@ -72,6 +72,14 @@ "folder": "2026-10-09 Зал персональной конференции Alex Martemyanov 2026-10-09 18 51(GMT+6 00) AEmGnEdJQfCMmCjwLyGtGA", "sha256": "562d2af7fee22ee565cd6494dac717becd8bcd090b926b8fe9deea7099e8e2f2", "cues": 86 + }, + "nzWOuhyzSdCjNqMRh6X13w": { + "title": "Dominik Kapusta's Personal Meeting Room 2026-10-15 16:05(GMT+6:00)", + "meeting_date": "2026-10-15", + "source_url": "https://us01mynotes.zoom.us/nzWOuhyzSdCjNqMRh6X13w", + "folder": "2026-10-15 Dominik Kapusta's Personal Meeting Room 2026-10-15 16 05(GMT+6 00) nzWOuhyzSdCjNqMRh6X13w", + "sha256": "8e8e82f7d36e0910cb33039ff1c0ce633ae1b5d0680666379c69a5ce0d828533", + "cues": 332 } } }