text stringlengths 0 2.35k |
|---|
[3450.64 --> 3450.82] Yeah. |
[3451.02 --> 3472.14] I mean, I find that sad from the other side, you know, JavaScript and all the other parts of the web ecosystem have become so big that it is impossible for anyone to make a new JavaScript interpreter engine without the resources of a huge multinational corporation. |
[3472.56 --> 3473.60] That sucks. |
[3473.60 --> 3477.98] Well, I'm afraid that's all the time we have on that somber note. |
[3479.26 --> 3483.52] You can forget about your dreams of writing your own JavaScript engine. |
[3483.82 --> 3484.70] It's not going to happen. |
[3485.74 --> 3487.02] So just wake up. |
[3487.22 --> 3487.36] Sorry. |
[3487.72 --> 3488.72] No, it's, it's harsh. |
[3488.88 --> 3491.00] It's a harsh wake up call, Michael, but we needed it. |
[3491.12 --> 3491.86] Thank you very much. |
[3493.14 --> 3496.52] Thank you so much to our guests today. |
[3497.48 --> 3500.98] Michael Matloub joined us, as did Daniel Marti. |
[3501.32 --> 3502.80] It was a pleasure as always. |
[3502.80 --> 3503.76] Thank you very much. |
[3503.84 --> 3505.04] Thanks for joining us on GoTime. |
[3505.22 --> 3505.70] Thanks to me. |
[3505.90 --> 3506.72] We'll see you next time. |
[3507.46 --> 3512.48] All right. |
[3512.62 --> 3514.22] That is GoTime for this week. |
[3514.76 --> 3517.24] What are you most excited about in Go 1.18? |
[3517.62 --> 3518.26] Is it fuzzing? |
[3518.86 --> 3519.34] Generics? |
[3519.86 --> 3520.96] Something we talked about today? |
[3521.34 --> 3522.90] Let us know in the comments. |
[3523.40 --> 3524.76] Just pop open your show notes. |
[3525.04 --> 3528.48] Click the discuss on changelog news link and let your voice be heard. |
[3528.48 --> 3532.78] And if you're a long time listener, do us a solid and tell a friend about the show. |
[3532.98 --> 3534.90] It is the best way for you to support GoTime. |
[3535.22 --> 3539.34] Of course, we have our changelog++ membership, which is awesome and gets you closer to the metal. |
[3539.52 --> 3545.20] But if you want to pitch in, we would love a tweet, a blog post, a Reddit thread, however it is that you like to socialize. |
[3545.20 --> 3553.16] Thanks again to Fastly for being our CDN partner for all these years, to Brakemaster Cylinder for keeping our beats fresh, and to you for listening. |
[3553.38 --> 3554.24] We appreciate you. |
[3554.48 --> 3557.26] An episode on GraphQL is in the pipeline. |
[3557.60 --> 3560.34] In fact, it's coming up next time on GoTime. |
[3560.34 --> 3576.68] Game on. |
• Velocity in software development |
• Definition and measurement of velocity |
• Agile practice of velocity, including assigning abstract scores to work |
• Challenges with estimating time and assigning points |
• Consistency issues with pointing sessions and estimation |
• Potential solutions for improving velocity tracking, such as group estimation and card roulette |
• Discussion of inconsistent biases in allocation of points |
• Introduction to the concept of "noise" from Daniel Kahneman's book Noise |
• Explanation of external noise as unpredictable factors influencing decision-making |
• Comparison between bias and noise in planning meetings |
• Discussion of Fibonacci sequence and its limitations in scaling |
• Use of simplified three-bucket system (Easy, Medium, Hard) for prioritization |
• Critique of using large numbers (e.g. 13) to represent complex tasks |
• Discussion about velocity calculation in Agile and how it relates to time |
• Tool usage: ClickUp for task management and estimation |
• Relationship between complexity and time |
• Importance of avoiding fixed scope and time in Agile development |
• Definition and understanding of velocity vs speed in physics and software development |
• Shared direction as a key aspect of velocity in Agile development |
• Anecdote about getting lost while driving and the importance of feedback loops |
• Developing a visualization system to track progress across multiple aspects of a project |
• Applying concepts like velocity to non-numeric metrics (e.g., points per direction) |
• Potential gamification features for tracking progress and unlocking new tools or features |
• Copilot and AI tooling for development, including its cost and value proposition |
• Impact on productivity and "velocity" in software development |
• The benefits and limitations of using developer tools like Copilot |
• Managing scope versus sacrificing quality or speed in software development |
• Convincing stakeholders that prioritizing scope is key to delivering high-quality software on time |
• The importance of cultural alignment across an organization for successful agile practices |
• Negotiating trade-offs between cost, time, and scope with stakeholders, particularly when working in a startup environment |
• Measuring velocity and estimating task time |
• Challenges of measuring velocity accurately |
• Importance of trusting teams and not micromanaging |
• Defining scope and prioritizing tasks |
• Understanding that scope can change naturally during a project |
• The role of communication in managing expectations and scope changes |
• Using experience to inform estimates and scope planning |
• Negotiating around scope and priorities in client-developer relationships |
• The importance of balancing speed and quality in software development |
• The dangers of micromanaging and technical debt |
• Finding the right balance between future-proofing designs and over-engineering |
• The value of experience and instinctive decision-making in software development |
• Techniques for making decisions, such as categorizing them into reversible or non-reversible actions |
• The concept of "two-way doors" vs. "one-way doors" in decision-making, and the idea of investing time to get it right |
• Discussion on estimation sessions in software development and how they can be valuable despite being inaccurate |
• Idea of keeping estimation sessions but throwing away the estimations themselves |
• Importance of sharing knowledge and coming open-minded to different perspectives |
• Criticism of books that are too long-winded or repetitive in explaining new concepts |
• Suggestion that books should be shorter or more clearly structured |
• Mention of Blinkist, a service that summarizes key concepts from non-fiction books into 15-minute summaries |
• Discussion of book pricing on Blinkist |
• Mention of Audible as an alternative |
• Humorous exchange about "fit wall" or "pain wall" |
• Debate over terminology for software professionals (coder, programmer, developer, engineer) |
• Results of Changelog's Twitter poll on preferred title |
• Jerod Santo's unpopular opinion that coding is not equivalent to typing |
• The difference between coding and typing |
• Connotations associated with the term "coder" |
• Why the term "coder" may have fallen out of favor |
• Comparison of developer vs programmer vs engineer |
• Agile development principles and feedback loops |
• Challenges of estimating work in software development |
**Natalie Pistunovich:** Hello everyone, and welcome to the episode about velocity in developments. Today we have very special guests - Mat Ryer, and Jerod, who was either drafted, or opted in, or accepted, but was definitely not rejected, as we clarified just before we started. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.