Placeholder Image

字幕列表 影片播放

由 AI 自動生成
  • If it's like my family, I definitely have no subjects.

    如果像我的家庭一樣,我肯定沒有主題。

  • Hey Daniel, hey Eric, welcome back here.

    嘿,丹尼爾,嘿,埃裡克,歡迎回到這裡。

  • Thanks so much.

    非常感謝。

  • Yeah, it's great to be here.

    是啊,能來這裡真是太好了。

  • Hi Virginia.

    嗨,弗吉尼亞。

  • Hello.

    你好

  • All right, let's kick off.

    好了,我們開始吧。

  • I wanted to start out with some reminders.

    首先,我想提醒大家幾點。

  • First, we have a book club coming up on Inspired in four weeks on August 7th.

    首先,我們將在四周後的 8 月 7 日舉辦一個關於《靈感》的讀書會。

  • I just re-read it myself.

    我剛剛重讀了一遍。

  • It's a good read.

    這是一本好書。

  • It's highly aligned with how I think about product management and does a good job of explaining why some of these things are important that I also believe to be important.

    它與我對產品管理的看法高度一致,並很好地解釋了為什麼其中一些事情很重要,而我也認為這些事情很重要。

  • So it's nice to have another voice explaining all of that.

    是以,很高興能有另一種聲音來解釋這一切。

  • So please do read that.

    是以,請務必閱讀。

  • I think I'm going to update the new hire onboarding doc and ask all new hires to read this as well so that everybody in the team is on the same page with respect to this book.

    我想我會更新新員工入職文件,並要求所有新員工都閱讀這本書,這樣團隊中的每個人都會對這本書有相同的認識。

  • Let's see.

    讓我們看看

  • Reminder B, remember there's this interview spreadsheet, CS and sales have populated that with a number of customer contacts for meetings.

    提醒 B,請記住有這樣一張面談電子表格,CS 和銷售人員已經在上面填入了一些客戶聯繫人,以便進行面談。

  • Please do follow up on that.

    請繼續跟進。

  • I want to ensure goodwill with that team and follow up promptly with meetings with these customers so that that team can see that we're taking advantage of it.

    我要確保與該團隊的良好關係,並及時跟進與這些客戶的會面,讓該團隊看到我們正在利用它。

  • Third reminder, we've got a little engagement survey.

    第三個提醒,我們有一個小小的參與調查。

  • I'm going to run this once a month in Q3, just to take a pulse given all the change going on.

    我打算在第三季度每月運行一次,以便在發生這麼多變化的情況下把握脈搏。

  • Please do take a minute to fill it out.

    請花一分鐘填寫。

  • It's five quick questions and then one free form where you can share whatever feedback you have.

    這是五個快速問題,然後是一個自由表格,您可以在其中分享任何反饋意見。

  • Fabian didn't receive it.

    法比安沒有收到。

  • I'm pretty sure I went through my emails.

    我很確定我看過我的電子郵件。

  • Maybe it's on my end, but I'm happy to fill it out.

    也許是我的問題,但我很樂意填寫。

  • You didn't get it.

    你沒明白。

  • I need to get it to you.

    我得把它給你

  • All right.

    好吧

  • I will.

    我會的

  • I'll ask Jessica to resend that to you.

    我會讓傑西卡重新發給你。

  • Anybody else in the same condition where you did not receive it?

    還有人遇到同樣的情況嗎?

  • I don't recall, but is there a way to put the link to the survey in the agenda?

    我不記得了,但有沒有辦法把調查鏈接放到議程中?

  • Well, it's personal.

    嗯,這是個人問題。

  • It's tied back to your user ID so we can track which team you're on and that kind of thing.

    它與您的用戶 ID 綁定,這樣我們就能追蹤您所在的團隊等資訊。

  • I do believe it's anonymous, but nevertheless, everyone has their own custom ID.

    我相信它是匿名的,但儘管如此,每個人都有自己的自定義 ID。

  • So I'll ask Jessica to send it to Fabian and Karina.

    所以我會讓傑西卡把它發給費比安和卡琳娜。

  • Anybody else?

    還有其他人嗎?

  • I hadn't seen it, Scott, but I searched my email real quick and it looks like that's the title of the email.

    我沒看到,斯科特,但我很快搜索了我的電子郵件,看起來這就是郵件的標題。

  • So if you just search for that in your Gmail, you should be able to find it if you got it.

    是以,只要在 Gmail 中搜索一下,應該就能找到。

  • Pulse survey.

    脈搏調查。

  • Okay.

    好的

  • If anybody else didn't get it, please ping me.

    如果還有人沒有收到,請聯繫我。

  • All right.

    好吧

  • Next reminder, we have a goal of at least three customer interviews per PM.

    下一個提醒,我們的目標是每個 PM 至少採訪三次客戶。

  • There's an OKR issue out there.

    現在有一個 OKR 問題。

  • If you haven't updated it lately, please do so.

    如果您最近沒有更新,請進行更新。

  • And remember, we have three weeks until Q2 to hit our goal.

    請記住,在第二季度之前,我們還有三週的時間來實現我們的目標。

  • So please do invest the time to get those set up and get at least three done if you haven't already.

    是以,請投入時間來設置這些功能,如果還沒有的話,至少要設置三個。

  • Next one, category maturity page.

    下一個是類別成熟度頁面。

  • Last week, we talked about this.

    上週,我們談到了這一點。

  • Josh did a great job of creating some new views, one of which is sort of this flow chart showing how mature we're going to be at a given point in time, which raised questions about whether we were forecasting that accurately.

    喬希很好地創建了一些新的視圖,其中一個是流程圖,顯示了我們在特定時間點的成熟度,這讓人懷疑我們的預測是否準確。

  • If you haven't already, please go in and either confirm that it's accurate or update it.

    如果您還沒有這樣做,請登錄並確認其準確性或進行更新。

  • Thanks to Kenny for creating that issue.

    感謝 Kenny 創建了這個問題。

  • Somebody had a direction maturity page.

    有人有一個方向成熟度頁面。

  • You want to talk about that?

    你想談談嗎?

  • That was just me, just as you referenced it, so I was adding the link there.

    那只是我的想法,正如你提到的那樣,所以我在那裡添加了鏈接。

  • That's all.

    僅此而已。

  • Folks, if you haven't seen the updates there for the charts, just check it out.

    朋友們,如果你們還沒有看到圖表的更新,就去看看吧。

  • So it's a good way you can get a sense for like, you know, it's hard when it's in tabular form, but when it's charted, it's much easier to see like if it's achievable or not based on some of the trends.

    是以,這是一個很好的方法,你可以通過表格的形式來了解情況,你知道,這很難,但如果用圖表的形式,就更容易根據一些趨勢來判斷是否可以實現。

  • And there's also, if you scroll down, stage level trends as well.

    如果向下滾動,還可以看到階段性的趨勢。

  • So you can see how your stage in particular is trending or set to be trending.

    是以,您可以看到您所在舞臺的特定趨勢或即將出現的趨勢。

  • Great.

    好極了

  • Thank you, Josh.

    謝謝你,喬希。

  • All right.

    好吧

  • Some team updates.

    一些團隊更新

  • We hired a couple more PMs.

    我們又僱了幾個 PM。

  • We got a good rhythm going on hiring.

    我們的招聘節奏很好。

  • We hired Gabe Weaver.

    我們僱傭了加布-韋弗。

  • He originally came through the growth funnel, but we have a really strong candidate for that fourth slot.

    他最初是通過成長漏斗進來的,但我們有一個非常強有力的候選人來填補第四個名額。

  • So we're going to target Gabe for a third managed PM.

    所以,我們要把加布作為第三個受管總理的目標。

  • The charter of that team is to be defined, but bottom line, we're going to have a third group in the managed area and Gabe will lead that.

    該小組的章程有待確定,但最重要的是,我們將在管理區設立第三個小組,由 Gabe 上司。

  • And then Dov Hershkowitz, we just hired him as the APM monitoring.

    然後是多夫-赫什科維茨(Dov Hershkowitz),我們剛剛聘請他擔任 APM 監督員。

  • He's got a great background in monitoring and has most recently been at Elastic.

    他在監控領域有很好的背景,最近在 Elastic 工作。

  • So thank you to everyone who's been involved in the hiring loop.

    是以,感謝所有參與招聘工作的人。

  • I know it's taking a lot of energy from everybody, but I think our hiring processes continues to pick up speed.

    我知道這需要每個人投入大量精力,但我認為我們的招聘進程在不斷加快。

  • B2B worked with Christy and David Sakamoto to change some language around customer results.

    B2B 與 Christy 和 David Sakamoto 合作,修改了一些有關客戶結果的措辭。

  • Just wanted to make sure you all saw that.

    我只是想確認你們都看到了。

  • So there's the MR. Hey, Scott.

    這就是MR嘿,斯科特。

  • On that one, the diff highlights what is new content, I believe, and there's one section that is great.

    我認為,在這其中,差值突出了哪些是新內容,其中有一個部分非常棒。

  • I can totally understand why we would add that about prioritize ruthlessly.

    我完全理解我們為什麼要加上 "無情地確定優先次序 "這句話。

  • But then the rest is, I guess, a bunch of formatting changes.

    但剩下的,我想就是一些格式上的改動了。

  • And I don't know if there's new content in any of the dogfooding.

    我也不知道這些狗糧裡有沒有新內容。

  • I guess the TLDR, the addition of that prioritize ruthlessly, or is there some other point we were trying to make in this change?

    我想是 "TLDR",即增加了 "無情地確定優先次序",還是我們在這一改動中還想表達其他觀點?

  • Oh, it's been a little while.

    哦,好久不見。

  • I think there were a number of changes, but before the handbook basically read that internal feedback is worth 10 times more than external feedback.

    我認為有很多變化,但在手冊之前,基本上是這樣寫的:內部反饋的價值是外部反饋的 10 倍。

  • And I understand why we want internal feedback because of dogfooding and using our own product.

    我也明白為什麼我們需要內部反饋,因為我們在使用自己的產品。

  • It's a great channel for feedback, but I think it was sending the message that customers weren't nearly as important as internal opinion.

    這是一個很好的反饋管道,但我認為它傳遞的資訊是,客戶並沒有內部意見那麼重要。

  • And both Christy and I want to move off of that position.

    克里斯蒂和我都想離開這個位置。

  • Like we should be customer first and treat our own teams as a customer.

    比如我們應該客戶至上,把自己的團隊當作客戶。

  • But I don't want people to interpret that our own internal opinion is worth 10 times more than a customer's opinion, if that makes sense.

    但我不希望人們理解為,我們內部的意見比客戶的意見價值高出 10 倍,如果這能說得通的話。

  • So it was mostly language, wherever that showed up in the handbook.

    是以,無論手冊中出現了什麼,主要都是語言問題。

  • Gotcha.

    抓到你了

  • Okay.

    好的

  • The one comment that I had on this is that some of the text seems like we should focus on core competencies as opposed to new scope, as in we should focus first on what we're best at.

    我對此的一個評論是,有些文字似乎認為我們應該關注核心能力,而不是新的範圍,就像我們應該首先關注我們最擅長的東西。

  • So anyways, that's one thought I had on this.

    總之,這就是我的一個想法。

  • I don't remember that being the point of it.

    我不記得這是重點。

  • Maybe it reads that way.

    也許讀起來就是這樣。

  • I don't know.

    我不知道。

  • Feel free to continue to suggest tweaks.

    歡迎繼續提出調整建議。

  • The point was, let's prioritize and do what matters most first.

    問題是,讓我們分清主次,先做最重要的事情。

  • Just it's kind of what I've been preaching the whole time.

    這也是我一直以來所宣揚的。

  • Like let's, in your area, wherever that is, do what matters first.

    比如讓我們在你所在的地區,無論在哪裡,先做最重要的事情。

  • Don't try to do it all at once.

    不要試圖一次全部完成。

  • We're going to have to work our way through.

    我們必須努力克服困難。

  • That was the point.

    這才是重點。

  • Yeah.

    是啊

  • And I don't know if this is a follow-up issue in the way you described it.

    我不知道這是否是你所說的後續問題。

  • It doesn't seem controversial, but I will say there was a big discussion and a recent initiative from Sid and other leaders that we should heavily prioritize dogfooding because there are parts, there are teams within the company that were not utilizing our features.

    這似乎沒有爭議,但我要說的是,希德和其他上司最近發起了一場大討論和一項倡議,我們應該優先考慮狗糧,因為公司內部有一些部分、一些團隊沒有利用我們的功能。

  • And we wanted to make sure that the product team was responsive to requests from them.

    我們希望確保產品團隊能夠及時響應他們的要求。

  • It's a little bit different than saying it's about our internal opinion.

    這與我們的內部意見有點不同。

  • Like we had always said we should validate it.

    就像我們一直說的,我們應該驗證它。

  • So that clarification is good that we want to make sure it's about us saying this is in line with where we want to take the product and where we're hearing customers.

    是以,我們很高興能澄清這一點,我們希望確保這與我們的目標一致,也符合客戶的要求。

  • But if an internal customer wants it, we should, the original thinking was that we should emphasize it.

    但如果內部客戶需要,我們就應該這樣做,最初的想法是我們應該強調這一點。

  • I just want to like, if the intent was to make sure we were just clarifying that same position, but if we're saying actually we should kind of pull back from the push for more dogfooding.

    我只是想知道,如果我們的目的是要確保我們只是在澄清同樣的立場,但如果我們說實際上我們應該從推動更多的狗糧中抽身出來。

  • No, I would, please don't conflate the two.

    不,我會的,請不要把兩者混為一談。

  • We very much still want to dogfood.

    我們還是非常想吃狗糧。

  • I think the point is when you're thinking of customers for your thing, think of our internal teams early, like you can get great feedback from them.

    我認為,當你為自己的產品考慮客戶時,應儘早考慮我們的內部團隊,因為你可以從他們那裡獲得很好的反饋。

  • They have an incentive to work with you.

    他們有動力與你合作。

  • There's very little risk in rolling out things early to them.

    提前向他們推出產品的風險很小。

  • So treat them like a customer and think of our internal teams early as you're rolling something out.

    是以,要像對待客戶一樣對待他們,並在推出產品時儘早考慮到我們的內部團隊。

  • That's still very much the message.

    這仍然是非常重要的資訊。

  • But let's not over rotate on internal feedback or internal opinion.

    但我們也不要過分依賴內部反饋或內部意見。

  • Let's still seek external feedback too, because that's just one customer of many. Great.

    我們也要尋求外部反饋,因為這只是眾多客戶中的一個。 好極了

  • Make sense?

    明白嗎?

  • Yeah, it does.

    是的,確實如此。

  • All right. 2C, customer discovery training coming soon.

    好的2C,客戶發現培訓即將開始。

  • Sarah O'Donnell and her team are going to do a bunch of sort of quick videos on a variety of customer discovery topics.

    Sarah O'Donnell 和她的團隊將就各種客戶發現主題製作一系列快速視頻。

  • So super excited for that.

    太激動了

  • They should start dropping any day now, I think starting this week.

    我想從本週開始,它們隨時都會開始投放。

  • And so we'll release those to you as they come out.

    是以,我們會在這些資訊發佈後及時向大家公佈。

  • We'll embed them in the how we work description on our team page as well.

    我們還將在團隊頁面的 "我們如何工作 "描述中嵌入這些內容。

  • All right.

    好吧

  • Number three, 12.2, kickoff feedback.

    三號,12.2,開球反饋。

  • Josh, thanks for leading the charge.

    喬希,感謝你的上司。

  • I thought you did a good job of emceeing and sort of adding color commentary in between.

    我覺得你主持得很好,還在中間加入了彩色評論。

  • I thought the screenshots definitely helped.

    我覺得截圖絕對有幫助。

  • There were a bunch that did not have them.

    還有一些沒有。

  • I was wondering why.

    我想知道為什麼。

  • Is it just because we're not there yet on many of these?

    難道只是因為我們在很多方面還沒有做到位?

  • Yeah? Yeah.

    是嗎? - 是的 - Yeah? Yeah. - Yeah.

  • I mean, some of the commentary, I don't know, or Nicole added that, yeah, many of the issues were saying we're going to do UX front end and back end in the same iteration.

    我的意思是,有些評論,我不知道,或者妮可補充說,是的,很多問題是說我們要在同一個迭代中完成用戶體驗的前端和後端。

  • So it hasn't started.

    所以還沒開始。

  • And in some, they're like, I can think of a number where there just aren't appropriate screenshots, or at least there weren't screenshots or mock-ups created in advance for the purposes of front end working on it, because front end was going to work on it without a mock-up.

    在某些情況下,它們就像,我能想到很多沒有適當截圖的地方,或者至少沒有截圖,或者沒有為了前端工作而提前製作的模擬圖,因為前端要在沒有模擬圖的情況下工作。

  • Okay.

    好的

  • I'd love to get to where we're a bit ahead so that we'll have more of these earlier and hopefully the customer discovery flow will get us further ahead on that.

    我很希望我們能走在前面一點,這樣我們就能更早地擁有更多這樣的產品,希望客戶發現流程能讓我們在這方面走得更遠。

  • In my case, some of the features also just have no UX component, as in no UI component that could be screen-shotted.

    就我而言,有些功能沒有用戶體驗組件,也就是沒有可以截屏的用戶界面組件。

  • Understood.

    明白。

  • Yeah.

    是啊

  • I don't expect everyone.

    我不指望每個人都這樣。

  • I mean, use your judgment.

    我的意思是,你自己判斷吧。

  • If it doesn't need it, fine.

    如果不需要,沒關係。

  • But where we do need design, it'd be great to get at least a month ahead so as we roll into dev, we have that to offer them.

    但如果我們確實需要設計,最好能至少提前一個月,這樣當我們進入開發階段時,我們就能為他們提供設計。

  • Scott, just a quick question to you.

    斯科特,問你一個簡單的問題。

  • How do you feel about presenting like balsamic or super lo-fi mock-ups on the kickoff call?

    你對在開球呼叫中展示類似香醋或超低仿真模擬有什麼看法?

  • Fine with that.

    沒問題。

  • Okay.

    好的

  • Because that could be an option, too, for PMs that are waiting for UX to work in the same sprint.

    因為對於在同一衝刺階段等待用戶體驗工作的項目經理來說,這也是一種選擇。

  • And I know that plan's done a pretty good job, at least in the past, of kind of running ahead of UX and saying, like, hey, this is kind of what I think I want this to look like before spinning UX cycles on making a more hi-fi mock-up.

    我知道,至少在過去,計劃在用戶體驗方面做得很好,比如說,在用戶體驗循環制作更高保真的模型之前,我想我希望它是這個樣子的。

  • So just to- If you think it does a better job of describing it than the issue itself, then use it.

    如果你認為它比問題本身更能說明問題,那就用它。

  • I think in some cases, like a picture can be worth a thousand words.

    我認為在某些情況下,一張照片勝過千言萬語。

  • I mean, no matter how many words you throw at something, it's like, you know, for example, one of my things that I request or I reported on for the release, the kickoff meeting, was expanding the Epic view in the roadmap.

    我的意思是,無論你在某件事情上說了多少話,就好像,你知道,例如,我在發佈啟動會議上要求或報告的一件事,就是在路線圖中擴展 Epic 視圖。

  • And like, those are basically just a bunch of buzzwords put together that you're like, okay, what does that mean?

    就像,這些基本上只是一堆流行語,你會想,好吧,那是什麼意思?

  • Expand Epic.

    擴展史詩。

  • And I'm just- I literally thought on that one for like 20 minutes saying, how do I make this issue title like more descriptive for customer value?

    我想了大概 20 分鐘,說:"我怎樣才能讓這個問題的標題更能體現客戶價值?

  • And it just came down to like, that is the functionality we're adding.

    最後的結果就是,這就是我們要添加的功能。

  • What does that mean?

    這是什麼意思?

  • Oh, here's the screenshot.

    哦,這是截圖。

  • You can see that we're going to add a dropdown.

    你可以看到,我們要添加一個下拉菜單。

  • You can see the issues and children epics that are attached to that epic.

    你可以看到與史詩相關的問題和兒童史詩。

  • And in that case, I was like, I'm so thankful I have a screenshot, even though that one is actually not a hi-fi mock-up.

    在這種情況下,我就想,真感謝我有一張截圖,儘管那張截圖實際上並不是高保真模擬。

  • It's more lo-fi.

    它更低保真。

  • It was a little bit pieced together.

    這是一點點拼湊起來的。

  • So yeah, I think like in general, there's a lot more value if we can show something like that.

    所以是的,我認為一般來說,如果我們能展示這樣的東西,就會有更大的價值。

  • So product managers, you can consider that.

    所以,產品經理們,你們可以考慮一下。

  • You should feel free that, you know, you're empowered to take a tool that you're comfortable with.

    你應該感到自由,你知道,你有能力使用自己喜歡的工具。

  • Even if it might even be just like Google Slides and make something that gets you at least a part of the way there in terms of what you want the experience to look like.

    哪怕只是像谷歌幻燈片那樣,至少也要能讓你部分了解你想要的體驗是什麼樣的。

  • Yep.

    是的。

  • Perfect. 3C, I thought the talk track shifted.

    太好了。3C,我以為談話軌跡變了。

  • It was definitely more problem focused.

    這無疑更注重問題的解決。

  • I noticed a number of speakers really trying to zero in on that, which is perfect.

    我注意到許多發言者都在努力將注意力集中在這一點上,這很好。

  • Some of them could have been more problem focused, I thought.

    我認為,其中一些問題本可以更加集中。

  • So just keep considering that as you, you know, it's important to be able to pitch these things in ways that people that aren't close to it can understand.

    所以,你要繼續考慮這一點,你知道,重要的是能夠用不熟悉的人能夠理解的方式來推銷這些東西。

  • And so just think about that.

    你想想看

  • How do I explain this to someone who's cold, who doesn't know a darn thing about this?

    我怎樣才能向一個對這些一無所知的冷冰冰的人解釋清楚呢?

  • Why should they care?

    他們為什麼要關心?

  • Getting that crystal in your thinking is going to be important no matter what.

    無論如何,讓水晶融入你的思維都是非常重要的。

  • So it's time well spent.

    所以時間花得很值。

  • Hey, Scott, this is Karina, just to add to that, if you don't mind.

    嘿,斯科特,我是卡琳娜,如果你不介意的話,我再補充一下。

  • I think this has always been a challenge in product, even before I've joined GitLab, for many people is how to get there on some of this terminology when those of us have deep technical background.

    我認為這一直是產品方面的一個挑戰,甚至在我加入 GitLab 之前,對於很多人來說,當我們這些人擁有深厚的技術背景時,如何掌握其中的一些術語,一直是個難題。

  • So my thought would be, is there a way that you can start sharing, you know, or applauding good examples of this so that the product team can start to kind of ruminate on this and develop that skill if we're not there yet?

    是以,我的想法是,你們是否有辦法開始分享,你知道的,或者為這方面的好例子鼓掌,這樣產品團隊就可以開始反思這個問題,如果我們還沒有發展到那個階段,是否可以發展這種技能?

  • Yeah, I thought Luca's were very well framed up.

    是的,我覺得盧卡的作品構圖非常好。

  • Those those two popped out at me as, yeah, that's the problem we're trying to solve.

    這兩個問題讓我眼前一亮,是啊,這就是我們要解決的問題。

  • Check those out.

    看看這些。

  • I'll look through for some other examples.

    我再找找其他例子。

  • Thank you for the suggestion.

    謝謝您的建議。

  • All right. 3D, we went long.

    好的3D 我們做多了

  • We just have a ton of speakers, which I love that lots of people get a chance to speak.

    我們有很多發言人,我喜歡很多人都有機會發言。

  • So I'm good with that.

    所以,我對此很滿意。

  • But we're going to have to we're going to have to limit the number of items, probably.

    但我們必須限制項目的數量。

  • So it looks like there's some other ideas in here, perhaps.

    看來,這裡或許還有些其他想法。

  • Themes.

    主題

  • Yeah, I mean, if there are some that relate to each other, you could tell a story, hey, we're trying to improve this and then A, B and C tie back to it.

    是的,我的意思是,如果有一些是相互關聯的,你可以講一個故事,嘿,我們正在努力改進這一點,然後 A、B 和 C 與之相關聯。

  • I think it's OK to be pretty brief in your description as long as you're hitting what it is.

    我認為,只要你能說清楚它是什麼,描述得簡短些也沒關係。

  • And if somebody is really interested, they can dive deep.

    如果有人真的感興趣,他們可以深入研究。

  • Thematic is a good idea.

    主題是個好主意。

  • Recorded video, if you really want to go deep, maybe it's technically complex.

    錄製視頻,如果你真的想深入瞭解,也許技術上很複雜。

  • That's a great idea.

    這是個好主意。

  • And then you can just cover the customer value at a high level and leave the detail to the video.

    然後,你就可以從高層次上介紹客戶價值,把細節留給視頻。

  • Watch statistics.

    觀察統計數據。

  • I think Josh looked this up last time.

    我想喬希上次查過這個問題。

  • I think he said there were a thousand.

    我想他說有一千個。

  • Oh, there we go.

    哦,又來了。

  • Kenny's putting them in.

    肯尼把它們放進去了

  • So somewhere between 500 and a thousand.

    是以,大約在 500 到 1000 之間。

  • To kind of add to the time, just a feedback, I was timing myself this time and I had two features listed and I hit three minutes and 14 seconds.

    我這次給自己計時,列出了兩個功能,結果用時 3 分 14 秒。

  • Obviously, I can shorten that.

    顯然,我可以縮短這個時間。

  • So when we talk about, you know, I think somebody mentioned doing two or coupling it down.

    所以,當我們談到,你知道,我認為有人提到做兩個或耦合它下來。

  • It's interesting that I landed there with the two that I chose.

    有趣的是,我選擇了這兩個地方。

  • Yeah, that feels good.

    是的,感覺很好。

  • I mean, I don't know if that feels about average, but we've had how many speakers will probably have to be a couple minutes, Max, per person.

    我的意思是,我不知道這是否感覺平均水平,但我們已經有多少發言人將可能有一對夫婦分鐘,最大,每個人。

  • I mean, Eric pointed this out in the next line.

    我是說,埃裡克在下一行就指出了這一點。

  • I do think we are due for a rethink of how we're doing the kickoff, because we're going to have next month, we're going to have 25 people trying to give content.

    我確實認為我們應該重新思考如何開展啟動儀式,因為下個月我們將有 25 人試圖提供內容。

  • And even at two minutes, you're already gone.

    即使是兩分鐘,你也已經走了。

  • So, yeah, maybe we expand it.

    所以,是的,也許我們可以擴大它。

  • I will give a shout out for Jason.

    我要為傑森點贊。

  • I know because he's on paternity leave, created a video, but I think the original intent of the kickoff was actually just as a company.

    我知道,因為他在休陪產假,所以製作了一個視頻,但我認為啟動儀式的初衷其實只是作為一個公司。

  • We had a retrospective and a kickoff, a retrospective immediately followed by a kickoff.

    我們進行了回顧和開球,回顧之後立即開球。

  • And we just decided to post that on YouTube.

    我們決定把它發佈到 YouTube 上。

  • We now post a whole bunch of content on YouTube.

    現在,我們在 YouTube 上發佈了大量內容。

  • So, just having what you would normally do for your grooming or kickoff within your individual group posted to YouTube and us maybe having a specific channel for people who wanted to follow it.

    是以,只需將你通常會在個人小組內做的梳理或啟動工作發佈到 YouTube 上,我們也許會為想要關注它的人提供一個特定的頻道。

  • Anyway, we should discuss it in an issue and come up with something, I do think, prior to next release kickoff.

    總之,我們應該在一個問題中討論這個問題,並在下一個版本發佈前想出辦法。

  • Just to evaluate alternatives to the format?

    只是為了評估格式的替代品?

  • Yeah, I mean, I don't, even if we said every person has one minute, I feel like we're doing a disservice because we're now highlighting much less because we feel like we have a time constraint and need to keep it into one synchronous 30 minute block when there's a need to do that.

    是的,我的意思是,我不這麼認為,即使我們說每個人都有一分鐘的時間,我覺得我們也是在做無用功,因為我們現在強調的內容要少得多,因為我們覺得我們有時間限制,需要在有必要的情況下保持 30 分鐘的同步時間段。

  • Okay.

    好的

  • Yeah, plus one to revamping it.

    是啊,再加上一個改造。

  • I think, I think we're trying to, it's like, got so many jobs right now that we're not doing a good job at any particular one of them.

    我認為,我認為我們正在努力,就像現在有這麼多的工作,我們沒有做好其中任何一項。

  • But I think that feels the most important customers are internal.

    但我認為,最重要的客戶是內部客戶。

  • And it's just like communicating internally about because like, people attend that thing, man.

    這就像內部溝通一樣,因為人們都會參加這個活動。

  • We had like 50 people on the zoom call alone, not even considering YouTube, people were asking about what happened to YouTube link and things like that.

    光是放大電話就有 50 人参加,甚至還沒考慮到 YouTube,大家都在問 YouTube 鏈接怎麼了之類的問題。

  • So it's, it's well attended internally, I think, for alignment.

    是以,我認為,為了保持一致,它在內部受到了廣泛關注。

  • Let alone the, you know, marketing value of like, sort of like a release.

    更不用說,你知道,就像發佈一樣的營銷價值了。

  • I mean, for fictional customers, it kind of feels like you're better off having like a webinar or live stream on the release day.

    我的意思是,對於虛構客戶來說,在發佈當天舉辦網絡研討會或現場直播感覺會更好。

  • Right.

  • Yeah, maybe the externally focused one would be more about what we just shipped.

    是啊,也許對外的重點會更多地放在我們剛剛運送的東西上。

  • There was a webinar that used to happen called release radar.

    以前有一個網絡研討會,叫做 "釋放雷達"。

  • I think I participated in a couple of those three or three of them back to back, and they were pretty poorly attended from what my experience was.

    我想我參加了其中的幾次,有三次是背靠背的,根據我的經驗,參加的人很少。

  • And I think they actually got ended by the product marketing team for that reason.

    我認為產品營銷團隊是以而終止了他們的合作。

  • I'm sure someone from that team could actually give feedback.

    我相信該團隊中的某個人一定能提供反饋意見。

  • But I think one thing about the time limit is it's really hard to motivate problems, particularly like in a short amount of time, particularly when they're very technical, like as product categories grow in maturity and sophistication, like the problems become more and more specific that we're solving.

    但我認為,關於時間限制的一件事是,要在短時間內激發問題的積極性真的很難,尤其是當問題的技術性很強的時候,比如隨著產品類別的成熟和複雜程度的提高,我們要解決的問題也會變得越來越具體。

  • And so motivating those specific reasons and why we're going after like this specific tiny piece of a very mature category.

    是以,我們要說明這些具體原因,以及我們為什麼要在一個非常成熟的品類中尋找這一小塊。

  • It's hard to do in 30 seconds in a way that and so if we want to do that better, that's going to put more and more pressure on like communicating a reasonable number of items, I think.

    這很難在 30 秒內完成,是以,如果我們想做得更好,我認為,這將會給溝通合理數量的項目帶來越來越大的壓力。

  • Okay.

    好的

  • Thank you all for the feedback.

    感謝大家的反饋。

  • I like the idea of creating an issue and perhaps tweaking the format before next month.

    我喜歡創刊的想法,或許下個月之前可以調整一下形式。

  • I also like the idea of asking internal and external constituents what they like or don't like about the format.

    我還喜歡詢問內部和外部選民他們喜歡或不喜歡這種形式的想法。

  • Yeah, just one final thought on that.

    是的,關於這一點,我還有最後一個想法。

  • Like, I love that it's a half an hour.

    比如,我喜歡半小時的節目。

  • I'd almost even like take pick particular categories over, over, over lengthening the time as an example, just because I feel the feeling I had a feeling that if you want to watch it consistently, it's going to be in that block, but that's just me.

    我幾乎甚至想以延長時間為例,挑選一些特定的類別,因為我有一種感覺,我有一種感覺,如果你想持續觀看,它就會出現在那個區塊,但這只是我的感覺。

  • So if, you know, other customers are, you know, saying they would like the larger block, then that's the right way to go.

    是以,如果其他客戶說他們想要更大的區塊,那就是正確的選擇。

  • So that's, that's where I'd love to get feedback in some fashion to say, okay, you know, here's how we should change it.

    是以,我很希望能以某種方式得到反饋,說:好吧,你知道,我們應該怎麼改。

  • But we clearly have gone breath wise.

    但是,我們顯然已經失去了呼吸的智慧。

  • We've gone so much broader that it's going to be hard to cover all the topics in it.

    我們已經做了很多擴展,很難涵蓋其中的所有主題。

  • Okay.

    好的

  • Thanks, Kenny, for starting the issue.

    謝謝你,肯尼,謝謝你提出這個問題。

  • James over to you for number four.

    詹姆斯,第四個節目交給你了

  • Yeah, I just thought I'd share this for many, I think many on this call haven't heard Mark Cunspat speak about product discovery sprints, but he advocated for this quite a number of times previously, from his experience running these at a prior company.

    是的,我只是想和很多人分享一下,我想在座的很多人都沒聽過馬克-康斯帕特(Mark Cunspat)關於產品發現衝刺的演講,但他之前在一家公司營運產品發現衝刺的經驗中,曾多次倡導過這一點。

  • So the idea is kind of different to a, I guess, a UX discovery sprint, I think Fabian linked one of the books about that, where it's really focused on UX iteration and research.

    是以,這個想法與用戶體驗發現衝刺有點不同,我想Fabian在一本書中提到過,用戶體驗發現衝刺的重點是用戶體驗迭代和研究。

  • The product discovery sprint is more focused on kind of like actually building something iterating on something that's built and trying to get to some sort of MVC really quickly by trying to make the process more synchronous.

    產品發現衝刺更側重於實際構建一些東西,對已構建的東西進行迭代,並通過嘗試使流程更加同步,真正快速地實現某種 MVC。

  • So the source code group is going to try and do that around file by file diff navigation to solve performance and usability problems in 12.3 And I thought it'd be interesting to share that because internally, we've been wrestling with like how to make this work well in async slash remote environment.

    是以,源代碼小組將嘗試在 12.3 中實現逐個文件的差異導航,以解決性能和可用性問題。我認為分享這一點會很有趣,因為在內部,我們一直在糾結如何在異步斜線遠程環境中很好地實現這一點。

  • So we're looking at trying to confine the participants in a specific time zone, so that we can all be available with a significant amount of overlap.

    是以,我們正在嘗試將參與者限制在特定的時區,這樣我們就可以在有大量重疊的情況下都能參加。

  • But that's also difficult because we have, it kind of excludes automatically 50% of the team who are just geographically remote from any of their peers, we only have one UX designer that's only available in the European time zone.

    但這也很難,因為我們有 50%的團隊成員在地理位置上遠離他們的同行,我們只有一個用戶體驗設計師只能在歐洲時區工作。

  • So some interesting challenges there.

    是以,這裡存在一些有趣的挑戰。

  • If it goes well, we're going to try and replicate it A release or two later on a different problem that is also really complicated and hard.

    如果進展順利,我們將在一兩個版本後嘗試在另一個同樣非常複雜和困難的問題上覆制它。

  • We're going to make progress on quickly, but I'll share any findings we have.

    我們將很快取得進展,但我會與大家分享我們的任何發現。

  • And if anyone's interested in discussing that with me more Put a meeting my calendar or drop me a message.

    如果有人有興趣和我討論這個問題,請在我的日程表中安排會面,或者給我留言。

  • This is great, James.

    太棒了,詹姆斯。

  • By the way, I think the UX team is going to run.

    順便說一句,我覺得用戶體驗團隊要競選了。

  • Well, let me just say we have the option to run one with Google Ventures, who's one of our investors in that Sprint book that Fabian linked to was written by a guy from GV.

    好吧,我只想說,我們可以選擇與谷歌風險投資公司(Google Ventures)合作,他們也是我們的投資者之一,費比安鏈接的那本《Sprint》就是谷歌風險投資公司的人寫的。

  • They did hundreds of these things for our clients.

    他們為我們的客戶做了數百件這樣的事情。

  • They know what they're doing.

    他們知道自己在做什麼。

  • So if we get a chance to do one with them, we should We're going to have to figure out how to do it within our basic model, though.

    是以,如果我們有機會與他們合作,我們應該這樣做。

  • So whatever you learn from yours, James, please feed that back super interesting topic.

    詹姆斯,無論你從你的文章中學到了什麼,都請把它反饋到超級有趣的話題中去。

  • I think if we could get good at this asynchronously, that would be a breakthrough.

    我認為,如果我們能以異步方式做好這件事,那將是一個突破。

  • Yeah, I think one other interesting challenges that the sprint sort of terminology is kind of Challenging and like it's not sustainable to be doing design sprints or discovery sprints on a daily basis, whether or not we were in person or not.

    是的,我認為還有一個有趣的挑戰,那就是衝刺的術語有點像 "挑戰",就像每天都進行設計衝刺或發現衝刺是不可持續的,無論我們是否親自參加。

  • It's not scalable to actually sprint all the time.

    實際上,一直衝刺是無法擴展的。

  • So choosing the right tasks, choosing the right time is I think one of the other challenges.

    是以,選擇合適的任務、合適的時間是我認為的其他挑戰之一。

  • I agree.

    我同意。

  • Yeah, you don't want to do this for everything because, well, if you follow the to the letter.

    是的,你不希望每件事都這樣做,因為,如果你嚴格遵守的話。

  • It takes a whole week and you're totally dedicated to it, which is Amazing for focus sake, but you can't get anything else done.

    這需要整整一週的時間,你要全身心地投入其中,為了集中精力,這很了不起,但你卻無法完成其他任何事情。

  • So depending on how we structure this, it would need to be done for things that are Really big unknowns were dedicating a big chunk of time like that is worth it and not everything clears that bar.

    是以,根據我們的結構,需要為那些真正的重大未知事項投入大量時間,這才是值得的,而不是所有事情都能通過這一關。

  • And I think it's also most relevant for for stages that are very In various in the very beginning, kind of like a tyrant was like one of their biggest example for Google Ventures, when They obviously like solving clinical trials for the world is like super complex problems.

    我認為,這也是與那些在最開始階段非常複雜的階段最相關的,就像谷歌風投(Google Ventures)的一個最大的例子--當他們為世界解決臨床試驗這個超級複雜的問題時,他們就像一個暴君。

  • So they just figured out what is this thing that we can do so that we can start getting there.

    是以,他們就想出了我們可以做的事情,這樣我們就可以開始實現目標了。

  • And I think these are the problems that That is a Sprint is We used it pretty successfully at my last company around pricing and packaging stuff and ran a bunch of interviews with customers on that so I've seen it work.

    我認為這些都是 "衝刺 "計劃要解決的問題。我們在上一家公司圍繞定價和包裝問題使用得非常成功,並就此與客戶進行了大量訪談,是以我看到了它的效果。

  • All right.

    好吧

  • Okay, Christopher.

    好的 克里斯托弗

  • Number five.

    第五個

  • Yeah, just want to call out we've over the past month we've had a significant number of And that affected at least one customer revenue potential.

    是的,我只想說,在過去的一個月裡,我們遇到了大量的問題,至少影響了一位客戶的潛在收入。

  • And because of that, you know, we've had some some focus from an exec leadership perspective.

    正因為如此,從執行領導層的角度來看,我們已經有了一些關注點。

  • So I encourage everybody to look at that document, you kind of look through it, in particular, there's a couple things from an engineering perspective, make you aware of one is is we started an infrastructure.

    是以,我鼓勵每個人都看看這份文件,尤其是從工程學的角度來看,有幾件事值得注意,一是我們啟動了一項基礎設施建設。

  • To development board where we're going to start matching issues up and trying to make sure that if that those get prioritized highly where appropriate, particularly for anything that you know affects performance around these issues.

    在開發板上,我們將開始匹配問題,並努力確保這些問題在適當的情況下得到高度優先處理,特別是對於任何你知道會影響這些問題性能的問題。

  • The other issue that I put in there was one around that's listed specifically, which is around the fact of prioritizing P performance availability work.

    我提出的另一個問題是具體列出的一個問題,即優先考慮 P 性能可用性工作。

  • So one of the significant Features of this particular recent outage last week was is that the Redis server apparently Can't handle the load anymore.

    是以,上週發生的這次故障的一個重要原因是,Redis 服務器顯然無法再處理負載。

  • And we started digging into it.

    於是我們開始深入研究。

  • We found a bunch of stuff that we hadn't checked.

    我們發現了很多沒有檢查過的東西。

  • Like, for instance, It's an example RJ unit tests were basically going and getting cached and there was no limit on the number of unit tests that could actually be cash.

    舉個例子,RJ 單元測試基本上都會被緩存,而且單元測試的數量沒有限制。

  • So we're getting these like blocks of like several megabytes of data that had to basically be transferred around and read us That's really what's affecting its performance overall from a caching service perspective.

    是以,我們得到的這些數據塊都是幾兆字節的數據,基本上都需要傳輸和讀取,從緩存服務的角度來看,這才是影響其整體性能的真正原因。

  • So consequently, Scott, I send that to you.

    是以,斯科特,我把它送給你。

  • I hope that's okay.

    希望你不介意。

  • It feels like it was like you need to help out in regards to the fact that, you know, how do we best make sure that we get this this kind of systematically going And I just want to make sure that everybody was aware and just kind of open up for discussion.

    我只是想確保每個人都意識到這一點,並展開討論。

  • If there were any questions or or any feedback early feedback on it from that perspective.

    如果有任何問題或反饋,請儘早從這個角度提出反饋意見。

  • I added some comments to it, Christopher.

    我加了一些評論,克里斯托弗。

  • Okay, I haven't had a chance to look.

    好吧,我還沒來得及看。

  • I apologize about that.

    我對此深表歉意。

  • Can I ask, do we and maybe Mac.

    我可以問一下,我們也許還有 Mac。

  • This is a question for you.

    這是給你的一個問題。

  • Do we categorize performance issues as bugs.

    我們是否將性能問題歸類為錯誤。

  • We do have a performance label, but they should be under under books.

    我們確實有一個性能標籤,但它們應該在書籍下面。

  • Okay.

    好的

  • This is an example where oftentimes the way we would treat performances is a reactionary.

    在這個例子中,我們對待表演的方式往往是反動的。

  • This is trying to think about it more in a proactive way.

    這是一種更加積極主動的思考方式。

  • So like as an example.

    舉個例子

  • I'll give a horrible example, but I worked at Amazon tags.

    我舉一個可怕的例子,我曾在亞馬遜標籤公司工作過。

  • Originally, when Amazon was created tags were Were they were expecting just a label, you know, certain instances.

    最初,當亞馬遜創建標籤時,他們期待的只是一個標籤,你知道,某些情況下。

  • And that was it.

    就是這樣。

  • And it turns out that all customers started using like 20 and 30 or 50 tags and they're like, what the heck's going on and they realize Tags were being used to basically assure environmental information.

    結果發現,所有客戶都開始使用 20、30 或 50 個標籤,他們就想,這到底是怎麼回事,他們意識到標籤基本上是用來保證環境資訊的。

  • So the VMs could They could put the same drop of code on two different VMs and they could behave differently based on the tag.

    是以,虛擬機可以將相同的代碼放到兩個不同的虛擬機上,它們會根據標籤的不同而有不同的表現。

  • Which was a total novel way for customers to use it.

    對客戶來說,這完全是一種新穎的使用方式。

  • So then they had to basically limit the number of tags They could use because it wasn't scaling with the system effectively so like this is kind of another example where like I think we got to start thinking in terms of You know, like when we create something new a new feature of piece of functionality Like what's the cost associated with that?

    是以,他們不得不從根本上限制標籤的數量,因為這無法有效地與系統進行擴展,所以這是另一個例子,我認為我們必須開始思考,當我們創建新的功能時,與之相關的成本是多少?

  • Right?

    對不對?

  • Because like it does cost some something internal and I'm not asking Product managers to necessarily think in terms of the exact bytes But I am starting to think in terms of like, you know What are the expectations around because like as an example if we went back and looked at G unit tests and reporting, you know, if we said unlimited that's you know, that's a tough engineering call, right?

    因為這確實需要一些內部成本,我並不是要求產品經理一定要考慮精確的字節數,但我開始考慮的是,你知道周圍的期望是什麼,因為舉個例子,如果我們回頭看 G 單元測試和報告,你知道,如果我們說這是無限制的,你知道,這是一個艱難的工程決策,對嗎?

  • Particularly, I guess it's free right now For customers is my understanding.

    特別是,我想現在對客戶是免費的,這是我的理解。

  • We also don't have a number of repos mirroring.

    我們也沒有許多 repos 鏡像。

  • We don't have a limit on that and that that seems dangerous Yeah, so I guess I would comment, you know, I think the product team Is expected to prioritize all things and to understand them deeply whether they're a security issue or a performance concern I think what you're highlighting is In order to be proactive.

    我們沒有這方面的限制,這似乎很危險。 是的,所以我想我要評論一下,你知道,我認為產品團隊應該優先處理所有事情,並深入瞭解它們,無論它們是安全問題還是性能問題。

  • I don't know if the product team would immediately know the impact of a proposed change, but maybe that's an opportunity for our Calm infrastructure or sre stable counterparts to be involved in vetting and looking at issues early in the pipeline to decide whether or not they would Yeah, or Or let's say we're implementing a feature like let's say we were implementing mirroring from scratch like the first question we should be asking is is like how many How many mirrors does a customer expected to be able to support and what I want to start charging for?

    我不知道產品團隊是否會立即知道擬議變更的影響,但這也許是我們的 Calm 基礎架構或 sre 穩定版同行參與審查的一個機會,他們可以在管道的早期階段查看問題,以決定它們是否會產生影響,或者比方說,我們正在實施一項功能,比方說我們正在從頭開始實施鏡像功能,我們應該問的第一個問題是,客戶期望能夠支持多少個鏡像,以及我想開始收取多少費用?

  • if they get above a certain limit and you know, and right now we don't and you could argue that Scaling is just as much a reason for customers to start paying us as uh as feature sets That's that's that's kind of the argument I would be making Because those things cost money like whether we like to admit it or not Yeah, christopher, I would I would agree with you on what you're trying to sort of shape up and call out here um in the sense of you know going through pages, for example, um performance of getting those pages loaded, um Is not great and I don't know if we set out originally to track some of those performance things, um but I think that Performance and to your point kenny.

    如果它們超過了一定的限制,你知道,現在我們沒有,你可以說,擴展和功能集一樣,是客戶開始付錢給我們的原因,這就是我的論點,因為這些東西都是要花錢的,就像我們是否願意承認一樣、我同意你的觀點,比如說,你在瀏覽網頁的時候,加載這些網頁的性能並不是很好,我不知道我們最初的目的是否是為了追蹤一些性能方面的東西,但我認為性能和你說的 Kenny。

  • I think performance should be somewhere incorporated um As we move forward and something we should be thinking about for scalability across the board um Because uh, it's just as important as bringing forth that really cool thing to them Is that that really cool thing works and people will stay there to use it I I think just as a side note, I think we have Something the product handbook that I read like a couple days ago on performance something like fast applications are are like always, you know, like more usable and I think that's that's definitely important and I also think that Um github.com is massive.

    我認為性能應該是我們在前進過程中應該考慮的問題,也是我們應該全面考慮可擴展性的問題,因為這與向他們展示很酷的東西一樣重要,因為很酷的東西可以讓人們留下來使用它,我認為這只是題外話,我認為我們的產品手冊中有一些關於性能的內容,就像幾天前我讀到的那樣,快速的應用程序總是更可用,我認為這絕對很重要,我還認為 Github.com 非常龐大。

  • I think we have four million users and for example for geo.

    我想我們有 400 萬用戶,比如地理信息。

  • I know that Only by actually like interacting with the infrastructure We are getting feedback on some of the performance bottlenecks that we are just not seeing otherwise, right?

    我知道,只有通過與基礎架構的實際互動,我們才能獲得一些性能瓶頸方面的反饋,而這些反饋是我們無法以其他方式看到的,對嗎?

  • And so I think that's actually also um, really valuable and in that regard maybe also, uh Like again, you know dogfooding these things helps and I think with the combination of cd we may hit a lot of those things Yeah, and the dogfooding thing on that front is a little confusing to me.

    是以,我認為這實際上也是非常有價值的,從這個角度來說,或許也是,嗯,就像你知道的那樣,狗糧這些東西很有幫助,我認為結合 cd,我們可能會打中很多這些東西 是的,狗糧這方面的事情讓我有點困惑。

  • I met with um, um Maren to talk about that and you know, there's sort of this mentality of looking at dot-com first or leading with dot-com for scalability and I just It's not really chris to me where we're going um from making sure that we're um, you know how we approach making sure that we intact scalability for dot-com if we're starting the dot-com or restarting somewhere else, um, From a dogfooding perspective i'm pretty sure the handbook says that we're meant to well at least the guidelines used to be that for new features that were meant to be available on gitlab.com and self-posted at the same time and that There used to be a production ready checklist um That I think the engineering team was responsible for I know that for when he launched geo There was a production readiness process that we had to go through and certainly with giddily We can see these things on the source code front We're regularly considering scale like moving terabytes of data from the database into object storage and considering all these sorts of things performance is very much a feature and should be considered that and I think Particularly in categories where adoption is still growing and in early stages of maturity performance Like understandably is less of a concern because there's lower usage.

    我和瑪倫討論過這個問題,你知道,現在有一種心態,就是首先考慮網絡公司,或者以網絡公司的可擴展性為先導,但我不太清楚,我們該如何確保網絡公司的可擴展性?從狗糧的角度來看,我很確定手冊上說的是,我們應該至少在以前的指南中是這樣說的,新功能應該在 gitlab.com我們可以在源代碼方面看到這些東西,我們會定期考慮規模問題,比如將 TB 級的數據從 Gitlab.com 轉移到 Gitlab.com 上。將 TB 級的數據從數據庫轉移到對象存儲中,考慮到所有這些事情,性能在很大程度上是一個特徵,應該考慮到這一點

  • So Like solving Scale at like an enormous level doesn't make sense commercially like necessarily when usage is small so there is a bit of a juggling act here because we don't want to build a product for billions of users if there's only I don't know 20 000 users experimenting with our newest feature.

    是以,在使用率較低的情況下,要解決規模龐大的問題在商業上是沒有意義的,這就需要權衡利弊,因為如果只有兩萬名用戶在試用我們的最新功能,我們就不想為數十億用戶打造產品。

  • Um, so there's a There's an iterative approach that needs to be taken but I'd I would agree that particularly coming from a team That's digging out a lot of technical debt and solving a lot of performance problems all the time We've probably historically not been very good at picking the right moment To pay off technical debt and address performance problems until they become fires so yeah, so To that point just real quick james.

    嗯,所以有一個有一個迭代的方法,需要採取,但我會我會同意,尤其是來自一個團隊,挖出了大量的技術債務和解決了很多性能問題的所有時間,我們可能歷來不是很擅長選擇正確的時機來償還技術債務和解決性能問題,直到他們成為火災,所以是的,所以這一點只是真正的快詹姆斯。

  • Um, sorry scott.

    對不起,斯科特。

  • Um, I think some things are obvious like when we look at our progressive deliveries, um strategy I think that we like if you look at something like feature flags or something like that That's something that I think is going to be like I wouldn't imagine that that's not going to be a key feature that we're going to bring forward Um, so I feel like that that should be a gimme on whether adoption has yet struck or not Um, but the second thing that is not clear to me like again When I was interviewing maren about dog fooding is that I noticed that maren's like we don't this isn't We weren't they didn't come to us first.

    嗯,我認為有些事情是顯而易見的,比如當我們看我們的漸進式交付時,嗯,我認為我們的策略就像如果你看一些像功能標誌或類似的東西,我認為這將是像我不會想象,這不會是一個關鍵的功能,我們將帶來前進嗯、所以我覺得這應該是採用與否的關鍵 第二點我也不太清楚 當我採訪瑪倫關於狗糧的事時

  • And so this is not scalable or this is not usable for us internally And so it's like the the approach and process moving forward to dog food in the right spots is not clear to me Or you know what the best practice has been or if anybody's you know, crack that yeah I can give a concrete example because I did a call with maren a few months back around confidential merge requests Um, so we knew that customers wanted to resolve them We knew that we wanted to do that and that we're trying to get rid of dev.gitlab.org so I had a video call with him and a bunch of async conversations with like I've got these ideas for the first iteration looks like and then we did a few calls and worked through them and worked out Which were the things that needed to happen?

    我可以舉個具體的例子,幾個月前我和 maren 就機密合並請求進行了一次通話,我們知道客戶希望解決這些請求,我們也知道我們想這麼做,而且我們正試圖擺脫 dev.gitlab.org。gitlab.org 所以我和他進行了視頻通話,並進行了一些異步對話,比如我有了一些關於第一次迭代的想法,然後我們又進行了幾次通話,討論並確定了哪些事情是必須要做的?

  • And so we're shipping the first iteration of that in 12.1 But we coordinated with them and spoke I spoke with maren quite a lot to make sure whatever we were building was useful And would solve the security problems that they had as well as our own ones, so I yeah, I agree.

    我們在 12.1 版本中推出了第一個迭代版本,但我們與他們進行了協調,並與瑪倫進行了多次溝通,以確保我們構建的東西是有用的,並能解決他們的安全問題和我們自己的安全問題。

  • It needs to be proactive We're not going to ship something's useful or that the infrastructure team is going to want to opt into Unless we've had a conversation with them in advance All right 30 sec.

    除非我們事先與基礎架構團隊進行了溝通,否則我們不會向他們提供有用的資訊,也不會讓他們選擇使用。

  • Can I add one like last tiny point?

    我能像上一個小點那樣加一個嗎?

  • It's sometimes really important for customers as well that we're running it on gitlab.com Um before they adopt it.

    有時,在客戶採用之前,我們在 gitlab.com Um 上運行它對他們來說也非常重要。

  • So one example is we built ssl tls support in giddily.

    例如,我們在 giddily 中構建了 ssl tls 支持。

  • Um But it's not turned on in gitlab.com And so the customer that we built it for isn't using it because they're waiting for our production team to turn it on because they want to see Before they turn it on for their enormous instance Have we actually proven it at the world's largest gitlab instance scale, um, so I think that's one important reason why we always need to make sure that features are on and are getting used on gitlab.com Just again rip.

    嗯,但在 gitlab.com 上並沒有開啟,所以我們為其構建的客戶並沒有使用它,因為他們在等待我們的生產團隊開啟它,因為他們想看看在他們為其龐大的實例開啟它之前,我們實際上已經在世界上最大的 gitlab 實例規模上驗證了它,嗯,所以我認為這是我們為什麼總是需要確保功能在 gitlab.com 上開啟並得到使用的一個重要原因,只是再次撕裂。

  • Sorry.

    對不起。

  • I got a couple things.

    我有幾樣東西

  • I think we definitely need to To have a stronger definition of done as part of progressions delivery, right and so Part of commission done is it needs to run at scale and get that dot com successfully And not blow up the cost model not below performance.

    我認為,我們肯定需要對 "完成 "有一個更有力的定義,將其作為進展交付的一部分。

  • Um, and if it does it's just going to be reverted Frankly, um, and that should be the bar for getting features across the line.

    嗯,如果是這樣,它就會被還原,坦白說,嗯,這應該是讓功能跨線的標準。

  • Um, that doesn't mean for new features.

    嗯,這不是指新功能。

  • Um, You know that have low usage that you know, obviously they're impacted quite small But there's still it needs to be within reason.

    嗯,你知道,那些使用率低的地方,你知道,顯然它們受到的影響相當小,但還是需要在合理的範圍內。

  • Um, I totally agree that you don't want to overbuild On the first iteration for planning for millions of users because that's just doesn't make any sense Um, but um, yeah, I think that's one aspect I think their aspect is that on your comment Christopher on pricing and we can maybe have a follow-up here on like a handbook update, but um I think it's interesting that customers will absorb the cost on self-managed of of compute and so for them if they want to have a ridiculous number of you know, um, Uh mirrors then you know, then it's fine because they're paying for it's our use case.

    嗯,我完全同意,你不希望在規劃數百萬用戶的第一次迭代中過度建設,因為這沒有任何意義 嗯,但是,嗯,是的,我認為這是一個方面,我認為他們的方面是你對克里斯托弗定價的評論,我們也許可以在這裡有一個像手冊更新的後續行動、但我覺得有趣的是,客戶會自行承擔計算自我管理的成本,所以對他們來說,如果他們想擁有數量多到離譜的鏡像,那就沒問題,因為他們為我們的用例買單。

  • It's all on their dime Um, and so maybe a way to think about this is to have some level of control so you can set if you want to at the instance level to sort of I don't have have some way to control that.

    這一切都要靠他們自己,嗯,所以也許考慮這個問題的一個方法是有一定程度的控制,這樣你就可以在實例級別設置,如果你想的話,我沒有一些方法來控制。

  • Um in a manner of behavior for when we're covering the cost of those things Um, but uh, but yeah anyways Thank you all great topic Christopher.

    嗯,在我們支付這些東西的費用時的行為方式 嗯,但是,嗯,但是,是的,無論如何,謝謝大家 偉大的主題克里斯托弗。

  • Uh, Please pile on that issue with thoughts on how to how to handle this.

    請就如何處理這個問題發表看法。

  • I like your suggestion on definition of done josh All right, karina six and seven Yes.

    我喜歡你關於 "已完成 "的定義的建議,Josh 好的,Karina 6 和 7 是的。

  • Um, so I um submitted an mr for the product handbook yesterday um, and we're going through this process of uh Getting more self-organized in the release.

    嗯,我昨天提交了一份產品手冊,我們正在經歷這個過程。

  • Um, Area and with our engineering and user design, uh partners and you know, one of the things that we Recognize and it's documented in the issue below in number seven Is um, you know one our delivery percentage is has not been great, which you've heard me talk about.

    我們的工程和用戶設計、合作伙伴以及我們認識到的一個問題是,我們的交付率並不高,這一點你們已經聽我說過了。

  • Um, but Team has been on a ramp that we need to self-organize around some method and what we found and sort of the last prioritization for a release scope is that we have a lot of oversized issues and features, um that Uh, you know honestly need a need a beat or a release, um to go through user research Um, maybe look at the code if they've never seen the code, you know reviewed that piece of code before Or make some recommendations on the best way to solve Um, so I put some thinking around, you know That sort of you know that dual track mindset dual track agile kind of launching off of what user experience has recently updated for dual track agile So feedback on that and then the second piece is that this experiment we're running is we're leveraging a semi-dual track agile approach just to organize our conversation how we open issues, uh for areas that we need a discovery beat versus Presenting an issue that is actually ready for delivery.

    嗯,但團隊一直在斜坡上,我們需要圍繞一些方法進行自我組織,我們發現和排序的發佈範圍的最後一個優先級是,我們有很多過大的問題和功能,嗯,你知道誠實地需要一個需要一個節拍或釋放,嗯,通過用戶研究,嗯,也許看看代碼,如果他們從來沒有見過代碼,你知道之前審查的代碼,或提出一些建議的最佳方式來解決嗯、是以,我圍繞雙軌思維進行了一些思考,雙軌敏捷是根據用戶體驗最近對雙軌敏捷的更新而推出的,是以,我對雙軌敏捷進行了反饋,然後第二部分是,我們正在進行的實驗是利用半雙軌敏捷方法來組織我們的對話,我們如何打開問題,嗯,對於我

  • Um, one thing that was interesting scott.

    嗯,有一件事很有趣,斯科特。

  • Um, we were talking about You know just the um kickoff call and having some you know, you know images and and more to share um That's definitely where I think we'd like to be with release is getting ahead of that curve and really having Um some concrete understanding and prototypes of what we're trying to present and deliver um, but when we looked at sort of kind of going through that process, you know, this is really for complex things or um heavy lifting Because you know it is about a 20 to 30 day lead time, um to commit So just uh, and so we have some targets, um To improve.

    嗯,我們正在討論你知道的只是嗯啟動電話和有一些你知道的,你知道的影像和更多的分享嗯,這肯定是我認為我們想與釋放是領先於曲線,真正有嗯一些具體的理解和原型,我們試圖提出和交付嗯、但是,當我們審視這個過程時,你知道,這確實是一個複雜的過程,因為你知道它需要 20 到 30 天的準備時間,所以我們有一些目標,嗯,要改進。

  • Um, you know our hypothesis on leveraging this um, you can follow it there if you have input, but Um, it they kind of tie together, but I love input on the handbook piece Thank you.

    嗯,你知道我們關於利用這一點的假設,如果你有意見,可以在那裡提出,但嗯,它們有點像綁在一起的,但我喜歡關於手冊這一塊的意見 謝謝。

  • Karina for creating these and sharing these I think you're on the right track Um In parallel i've been working with like christopher and eric and christy to outline A high level description of our software development life cycle, which will have two tracks this is Sort of competing content there or maybe or maybe they could be merged.

    同時,我一直在與克里斯托弗、埃裡克和克里斯蒂等人合作,勾勒出我們軟件開發生命週期的高層次描述,其中將有兩條軌道,這也算是競爭內容吧,或許或許它們可以合併。

  • So thank you for doing this I may slow roll it a little bit to make sure that We have one way of describing the flow we'd like to go through but uh Thank you very much for getting it kicked off Any questions for karina If not josh over to you Yeah, just a risk announcement, I just went through renamed the promise label to planning priority, um General meaning is largely the same.

    謝謝你的工作,我可能會稍微慢一點,以確保我們有一種方法來描述我們想經歷的流程,但非常感謝你讓它啟動,有什麼問題要問卡琳娜嗎?

  • Although we shouldn't be promising features.

    雖然我們不應該承諾功能。

  • And so this is just a way to flag it um And uh, that way it's a reminder for pms that this issue had some important select conditional dependencies And so just be aware of it.

    是以,這只是一種標記它的方法,嗯,這樣可以提醒 PMS,這個問題有一些重要的選擇條件依賴性,是以要注意它。

  • Um, so you can feel free to use it Um, I did note in the label text that it should only be applied by product managers and in particular the responsible product manager for that section Um, so it shouldn't get applied by cams or anyone else so Awesome I like that terminology a lot better.

    嗯,所以你可以隨意使用它 嗯,我在標籤文本中指出,它只能由產品經理使用,尤其是負責該部分的產品經理 嗯,所以不應該由凸輪或其他任何人使用,真棒,我更喜歡這個術語。

  • Thank you.

    謝謝。

  • Josh All right, five minutes to spare anything else If not, have a great tuesday adios Thanks

    喬希 好了,還有五分鐘時間,如果沒有,祝你星期二愉快 再見 謝謝

If it's like my family, I definitely have no subjects.

如果像我的家庭一樣,我肯定沒有主題。

字幕與單字
由 AI 自動生成

單字即點即查 點擊單字可以查詢單字解釋