mirror of
https://github.com/kamranahmedse/developer-roadmap.git
synced 2026-10-24 01:08:07 +08:00
chore: sync content to repo (#10452)
Co-authored-by: nilbuild <4921183+nilbuild@users.noreply.github.com>
This commit is contained in:
co-authored by
nilbuild
parent
6e22fbd350
commit
f2dc3eaa71
+1
-1
@@ -7,4 +7,4 @@ AI engineering involves building software systems that use machine learning mode
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@What Is an AI Engineer? (And How to Become One)](https://www.coursera.org/articles/ai-engineer)
|
||||
- [@video@AI, Machine Learning, Deep Learning and Generative AI Explained](https://www.youtube.com/watch?v=qYNweeDHiyU)
|
||||
- [@video@AI, Machine Learning, Deep Learning and Generative AI Explained](https://www.youtube.com/watch?v=qYNweeDHiyU)
|
||||
@@ -0,0 +1,8 @@
|
||||
# DevOps Skills
|
||||
|
||||
DevOps is the practice of automating and streamlining how software is built, tested, and deployed. A forward-deployed engineer who knows DevOps can own the full deployment lifecycle, from spinning up infrastructure to shipping a containerized agent into a client's cloud environment, without depending on another team to get there.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@What Is DevOps? A Guide to the Basics](https://www.coursera.org/articles/what-is-devops)
|
||||
- [@video@DevOps In 5 Minutes](https://www.youtube.com/watch?v=Xrgk023l4lI)
|
||||
+8
@@ -0,0 +1,8 @@
|
||||
# Tradeoffs: Scope, Speed, Quality
|
||||
|
||||
Every project involves tradeoffs between scope (how much is built), speed (how fast it is delivered), and quality (how well it holds up over time). Reducing scope can speed things up without sacrificing quality. Cutting corners on quality can speed things up in the short term but creates problems later. FDEs need to understand and communicate these tradeoffs clearly, helping customers make informed decisions rather than just agreeing to everything and delivering less than expected.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Project management triangle: Triple constraint guide](https://asana.com/resources/project-management-triangle)
|
||||
- [@video@What is the Iron Triangle? Time, Cost, Quality, Scope?](https://www.youtube.com/watch?v=JHSHOAfV-uw)
|
||||
+8
@@ -0,0 +1,8 @@
|
||||
# Technical Scoping & Sequencing
|
||||
|
||||
Technical scoping involves breaking a project into discrete tasks, estimating their complexity, and identifying dependencies. Sequencing means ordering those tasks logically, starting with the highest-risk or most uncertain parts. A well-scoped and sequenced project is easier to track and deliver on time, and gives the customer visibility into what is being built and in what order.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@How to effectively scope your software projects](https://medium.com/free-code-camp/how-to-effectively-scope-your-software-projects-from-planning-to-execution-e96cbcac54b9)
|
||||
- [@video@Project Scope Statement \[IN 4 EASY STEPS\]](https://www.youtube.com/watch?v=QDLk2QIuJkg)
|
||||
Reference in New Issue
Block a user