Media is too big
VIEW IN TELEGRAM
28. Team Metrics
Brian explains that metrics are crucial to product management because it's evidence and help define the success or failure of a given mission. An example of team metrics at Netflix is also discussed in this lesson.
#lesson
Brian explains that metrics are crucial to product management because it's evidence and help define the success or failure of a given mission. An example of team metrics at Netflix is also discussed in this lesson.
#lesson
Media is too big
VIEW IN TELEGRAM
29. Project Metrics
Brian explains why any project should affect team metrics. A PM should write down the problem the project is trying to solve and the metrics used to measure its success. The CSAT or customer satisfaction metric is also discussed in this lesson.
#lesson
Brian explains why any project should affect team metrics. A PM should write down the problem the project is trying to solve and the metrics used to measure its success. The CSAT or customer satisfaction metric is also discussed in this lesson.
#lesson
Media is too big
VIEW IN TELEGRAM
30. Metrics Exercise
Students are instructed to identify what metrics should be tracked for each project and the affected company-wide metrics.
- https://pm.holt.courses/lessons/metrics/exercise
#lesson
Students are instructed to identify what metrics should be tracked for each project and the affected company-wide metrics.
- https://pm.holt.courses/lessons/metrics/exercise
#lesson
Media is too big
VIEW IN TELEGRAM
31. User Stories
Brian recommends creating user stories by filling in the blanks: "As a [blank], I want to [blank]". This helps create a user story from the perspective of the end-user rather than the perspective of a product manager.
#lesson
Brian recommends creating user stories by filling in the blanks: "As a [blank], I want to [blank]". This helps create a user story from the perspective of the end-user rather than the perspective of a product manager.
#lesson
Media is too big
VIEW IN TELEGRAM
32. Product Spec
Brian introduces the product spec and shares a few variations used by different companies. Whether it's referred to as a ticket, statement of work, or proposal, a product specification is the most important document to a product manager. It describes a parcel of work and the steps required to accomplish it.
#lesson
Brian introduces the product spec and shares a few variations used by different companies. Whether it's referred to as a ticket, statement of work, or proposal, a product specification is the most important document to a product manager. It describes a parcel of work and the steps required to accomplish it.
#lesson
Media is too big
VIEW IN TELEGRAM
33. BLUF, Problem Statement, & Goals
Brian defines the BLUF (executive summary), problem statement, and how to define the goals of a project clearly. A product specification should include one of your team's metrics, or at the very least, company core metrics.
#lesson
Brian defines the BLUF (executive summary), problem statement, and how to define the goals of a project clearly. A product specification should include one of your team's metrics, or at the very least, company core metrics.
#lesson
Media is too big
VIEW IN TELEGRAM
34. Rollback Criteria, Timelines, & Mockups
Brian encourages project managers to define clear rollback criteria for when a team would stop working on a project and revert to a previous state. Tips for creating timelines and design mockups are also discussed in this lesson.
#lesson
Brian encourages project managers to define clear rollback criteria for when a team would stop working on a project and revert to a previous state. Tips for creating timelines and design mockups are also discussed in this lesson.
#lesson
Media is too big
VIEW IN TELEGRAM
35. Example Product Spec
Brian shares an example product spec. The sections of the product spec are organized by priority: BLUF, Problem Statement, Goals, Key Metrics, Rollback Criteria, Timelines, UI Mocks, Outstanding Questions, and Appendix.
#lesson
Brian shares an example product spec. The sections of the product spec are organized by priority: BLUF, Problem Statement, Goals, Key Metrics, Rollback Criteria, Timelines, UI Mocks, Outstanding Questions, and Appendix.
#lesson
Media is too big
VIEW IN TELEGRAM
36. Product Spec Exercise
Students are instructed to write a product spec for any product idea. Suggested product ideas can be found on in the course website linked below.
- https://pm.holt.courses/lessons/product/exercise
#lesson
Students are instructed to write a product spec for any product idea. Suggested product ideas can be found on in the course website linked below.
- https://pm.holt.courses/lessons/product/exercise
#lesson
Media is too big
VIEW IN TELEGRAM
37. Fit into the Organization
Brian recommends shaping a planning process to align with the existing culture and organization. It's challenging to gain a consensus if the process doesn't fit. In some cases this may mean product managers focus on strategy while engineering managers create the plan.
#lesson
Brian recommends shaping a planning process to align with the existing culture and organization. It's challenging to gain a consensus if the process doesn't fit. In some cases this may mean product managers focus on strategy while engineering managers create the plan.
#lesson
Media is too big
VIEW IN TELEGRAM
38. Starting the Planning Process
Brian shares tips for starting the planning process. Starting by getting ideas on paper helps with the writing process. Not all ideas need to come from a product manager. Projects should also be completable and have tangible milestones if there is a long timeline.
#lesson
Brian shares tips for starting the planning process. Starting by getting ideas on paper helps with the writing process. Not all ideas need to come from a product manager. Projects should also be completable and have tangible milestones if there is a long timeline.
#lesson
Media is too big
VIEW IN TELEGRAM
39. Cutlines & Roadmaps
Brian recommends defining a cutline that defines additional work that could be performed given more resources. Also, product features should not be added to a roadmap unless a product spec is created and it has been researched.
#lesson
Brian recommends defining a cutline that defines additional work that could be performed given more resources. Also, product features should not be added to a roadmap unless a product spec is created and it has been researched.
#lesson
Media is too big
VIEW IN TELEGRAM
40. Prioritizing
Brian provides two tools that are helpful when prioritizing projects. Comparing the complexity to business value splits the risk into effort and impact. The RICE method takes a more scientific approach, allowing product managers to associate a score with each task.
#lesson
Brian provides two tools that are helpful when prioritizing projects. Comparing the complexity to business value splits the risk into effort and impact. The RICE method takes a more scientific approach, allowing product managers to associate a score with each task.
#lesson
Media is too big
VIEW IN TELEGRAM
41. Planning Exercise
Students are instructed to create a prioritized roadmap for the proposed tasks along with a cutline for additional features.
- https://pm.holt.courses/lessons/planning/exercise
#lesson
Students are instructed to create a prioritized roadmap for the proposed tasks along with a cutline for additional features.
- https://pm.holt.courses/lessons/planning/exercise
#lesson
Media is too big
VIEW IN TELEGRAM
42. Wrapping Up
Brian wraps up the course with some tips for applying the product management skills learned throughout this course.
#lesson
Brian wraps up the course with some tips for applying the product management skills learned throughout this course.
#lesson
Title: Electron, v3
Description: Use Electron to build native, cross-platform desktop applications using web technologies (e.g. HTML, CSS, and JavaScript). Learn inter-process communication, UI customization, native features, and performance optimization.
Link: https://frontendmasters.com/courses/electron-v3/
Time: 3 hours, 53 minutes
Lessons: 25 / 25
Tags: #course #frontendmasters #720p
Description: Use Electron to build native, cross-platform desktop applications using web technologies (e.g. HTML, CSS, and JavaScript). Learn inter-process communication, UI customization, native features, and performance optimization.
Link: https://frontendmasters.com/courses/electron-v3/
Time: 3 hours, 53 minutes
Lessons: 25 / 25
Tags: #course #frontendmasters #720p
Frontendmasters
Build Cross-Platform Desktop Apps | Learn Electron Development
Use Electron to build native, cross-platform desktop applications using web technologies (e.g. HTML, CSS, and JavaScript). Learn inter-process communication, UI customization, native features, and performance optimization.
Media is too big
VIEW IN TELEGRAM
1. Introduction
Steve Kinney introduces the course by discussing Electron as a combination of a full Node.js and Chromium runtime. An overview of the course projects and material is also provided in this segment.
- Course setup: https://gist.github.com/stevekinney/46d6e96eb31ddb9db2b28af114d03679
- Course notes: https://gist.github.com/stevekinney/837ce9b2fa05ed88f6bc76d7d6e22efd
- Slides: https://static.frontendmasters.com/resources/2023-08-18-electron-v3/electron-v3.pdf
#lesson
Steve Kinney introduces the course by discussing Electron as a combination of a full Node.js and Chromium runtime. An overview of the course projects and material is also provided in this segment.
- Course setup: https://gist.github.com/stevekinney/46d6e96eb31ddb9db2b28af114d03679
- Course notes: https://gist.github.com/stevekinney/837ce9b2fa05ed88f6bc76d7d6e22efd
- Slides: https://static.frontendmasters.com/resources/2023-08-18-electron-v3/electron-v3.pdf
#lesson
Media is too big
VIEW IN TELEGRAM
2. Main Process & Renderer Overview
Steve discusses handling communication between the main and renderer processes. Newer versions of Node.js security differences and preload scripts are also covered in this segment.
#lesson
Steve discusses handling communication between the main and renderer processes. Newer versions of Node.js security differences and preload scripts are also covered in this segment.
#lesson
Media is too big
VIEW IN TELEGRAM
3. Electron Code Overview
Steve discusses the Electron Fiddle tool and walks through the contents of a simple app boilerplate. Multi-platform functionality should be kept in mind, as Electron is compatible with macOS, Windows, and Linux.
#lesson
Steve discusses the Electron Fiddle tool and walks through the contents of a simple app boilerplate. Multi-platform functionality should be kept in mind, as Electron is compatible with macOS, Windows, and Linux.
#lesson
Media is too big
VIEW IN TELEGRAM
4. Project Setup
Steve walks through the contents of the Firesale app's index.ts file. Updating the index.ts to not show the application window until it's fully loaded and where the dev tools should be shown is also demonstrated in this segment.
- https://gist.github.com/stevekinney/46d6e96eb31ddb9db2b28af114d03679
#lesson
Steve walks through the contents of the Firesale app's index.ts file. Updating the index.ts to not show the application window until it's fully loaded and where the dev tools should be shown is also demonstrated in this segment.
- https://gist.github.com/stevekinney/46d6e96eb31ddb9db2b28af114d03679
#lesson
Media is too big
VIEW IN TELEGRAM
5. File System Dialog & Reading Files
Steve demonstrates triggering a file system dialog by utilizing Electron's dialog module. How to restrict the allowed file types and reading files using fs/promises is also covered in this segment.
#lesson
Steve demonstrates triggering a file system dialog by utilizing Electron's dialog module. How to restrict the allowed file types and reading files using fs/promises is also covered in this segment.
#lesson