engineerkit / engineerkit Goto Github PK

It appears the author of the "Why Scrum: Defined Process vs Empirical Process" article that is included in the Product Lifecycle module has been suspended from Medium. Link to original article

Location in Module:

I'm not sure if it'd be best to simply remove the link to the article or to try to find a comparable one. The module has a plethora of resources and a replacement may not be needed.

Archive.org has a cached copy of the article (minus the graphics) for content comparison:
Why Scrum: Defined Process vs Empirical Process | Archive.org

• Create a LICENSE file

• Add more resources
• Add more clarity around the spectrum of data types

Once v1 topics are complete, create a map of all the modules and topics.

Thanks to @ThorntonMatthewD for finding this: https://github.com/gaurav-nelson/github-action-markdown-link-check

In response to #18, we should consider adding this to our pipeline to run on some sort of schedule, or on every push to the main branch.

There is numbering for files exercises and modules. So what happens is its listed in alphabetical order. I would expect that there be numbers in front of the MD file names so I know what order i'm supposed to go through it without needing to think. I don't feel like thinking more that I have to.

• Add more resources about publishing packages / dependencies

• Clarity on managing full stack state

Consider adding in more computer science topics?

Here are some example resources:

• MIT 6.006 Introduction to Algorithms, Fall 2011
• https://leetcode.com/discuss/career/450215/How-to-use-LeetCode-to-help-yourself-efficiently-and-effectively-(for-beginners)
• LeetCode - The World’s Leading Online Programming Learning Platform
• Favorite - LeetCode
• CS 97SI: Introduction to Programming Contests
• Why Learn Data Structures and Algorithms?
• Time Complexity and Space Complexity - GeeksforGeeks

There are a lot of false positives with the broken link checker. We either need to remove it entirely or improve its reliability.

Description: Some of the assignments in the "Securities" section in Engineer Kit are missing the repos to the assignments.

Expected Behavior: There should be a working link to a repo for the securities exercises that the mentee can clone down to their machine, complete , and then send to their mentors for feedback and critiquing.

Actual Behavior: Instructions for the assignment are present and added to the markdown file. However, the accompanying repo for the exercise that is mentioned in the file does not exist. The Markdown does mention a specific repo to clone, but this is not an existing repo. Even if you search for the repo on GitHub, it doesn't exist.

Relevant Information: Attached is a screenshot that highlights the exact repo for reference. This may provide more context on which assignments need to be linked. Below is the link to the specific repo that brought this to attention. This may not be the only missing assignment in EK. A thorough investigation of the assignment repos is recommended.

➡️ https://github.com/engineerkit/engineerkit/blob/main/exercises/security/broken-access-control.md

Attachments: Please see the attached screenshot.

Steps to Reproduce:

1. (Replicate via linked repo) Navigate to the aforementioned link above. Scroll down until you see the
   "link" to the assignment repo. Try to navigate to the repo that is linked. The link is not clickable and will not redirect to an assignment.

2. (Replicate via search) Copy and paste the repo into the search bar at the top right hand side of the page on GitHub. Hit "Enter". Note that the repo is not found.

Environment: Found via Safari: Version 17.2.1 (19617.1.17.11.12)

• Breakable toys
• Pairing
• Capstone project
• Module-specific projects

We need to figure out a way to collect data about how long it took someone to complete an exercise (perhaps an EngineerKit app feature?), so we can create a more accurate estimate range on how long it will take.

link of esimato in Module Tooling - Chpater Productivity doesn't land a webpage successfully.