-
Notifications
You must be signed in to change notification settings - Fork 16
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #17 from NHSDigital/SH_new_front_page
Merging after approval
- Loading branch information
Showing
15 changed files
with
75 additions
and
26 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
# Coding Best Practice | ||
This page is still under construction, however you can find guidance on this at these pages: | ||
- General Code Development | ||
- [Unit testing, back testing, tidy data and notebook vs IDE development](/development-approach) | ||
- Python | ||
- [Our general Python guidance incl. guidance on why to use functions!](/python) | ||
- [Pyspark style guide](/pyspark) | ||
- [Very comprehensive Python guidance here on almost every aspect of python (external link)](https://docs.python-guide.org/) | ||
- [google python style guide, which our Pyspark style guide is heavily based on](https://github.com/google/styleguide/blob/gh-pages/pyguide.md) | ||
|
||
- R | ||
- [R guidance - in progress](/R) |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
[RAP Champions]: ../README.md#support | ||
|
||
# Training your team | ||
This is just a stub page, but soon we intend to populate this with guidance on how to approach training your team in RAP. | ||
|
||
Some initial pointers to get you started: | ||
- **Get your team learning the basics of an open source language and Git**: confidence using version control, and a programming language of choice (at NHS Digital, this is usually Python), will make it easier for your team to engage with RAP training. | ||
- **Make time for RAP**: people need time to learn and use what they've learned - if they don't get time set aside specfically for RAP they won't develop these skills, and will potentially fall behind and lose motivation. | ||
- **Pragmatism is ok!:** You don't leap up to the level of full pyspark pipelines in one go. There is nothing wrong with starting very basic: wraping your existing SQL code in a bit of Python to orchestrate it, get that working, include some very simple tests to prove it works and then add it to Git and publish it. This is a great way to start and provides a solid foundation on which to build and learn more. | ||
- **Copy other people:** Look at your colleagues code, copy chunks of it, play around with it, try and break it - encourage others do the same. Re-use is at the heart of RAP and it's also a great way to teach and learn. | ||
- **Talk to the RAP champions:** The RAP champions (both your RAP trained colleagues and the Data Science RAP squad) have probably trained a number of people - ask them for advice. You can find out how to get in touch [here][RAP Champions]. | ||
- **The thin-slice approach is built with training in mind:** [See our pages on the the "thin slice" approach of doing RAP](/rollout-approach/thin-slice-strategy.md) - by doing a simple part of the publication from end to end, you create something people can learn from, and then with help expand. This can provide the structure around which you can train people. |