Skip to content

Commit 75e3d52

Browse files
committed
adding these files to version control
1 parent 227971b commit 75e3d52

File tree

6 files changed

+206
-0
lines changed

6 files changed

+206
-0
lines changed

.gitignore

+118
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,118 @@
1+
# Custom
2+
.idea
3+
4+
# Created by .ignore support plugin (hsz.mobi)
5+
### macOS template
6+
# General
7+
*.DS_Store
8+
.AppleDouble
9+
.LSOverride
10+
11+
# Icon must end with two \r
12+
Icon
13+
14+
# Thumbnails
15+
._*
16+
17+
# Files that might appear in the root of a volume
18+
.DocumentRevisions-V100
19+
.fseventsd
20+
.Spotlight-V100
21+
.TemporaryItems
22+
.Trashes
23+
.VolumeIcon.icns
24+
.com.apple.timemachine.donotpresent
25+
26+
# Directories potentially created on remote AFP share
27+
.AppleDB
28+
.AppleDesktop
29+
Network Trash Folder
30+
Temporary Items
31+
.apdisk
32+
### JetBrains template
33+
# Covers JetBrains IDEs: IntelliJ, RubyMine, PhpStorm, AppCode, PyCharm, CLion, Android Studio and Webstorm
34+
# Reference: https://intellij-support.jetbrains.com/hc/en-us/articles/206544839
35+
36+
# User-specific stuff:
37+
.idea/**/workspace.xml
38+
.idea/**/tasks.xml
39+
.idea/dictionaries
40+
41+
# Sensitive or high-churn files:
42+
.idea/**/dataSources/
43+
.idea/**/dataSources.ids
44+
.idea/**/dataSources.xml
45+
.idea/**/dataSources.local.xml
46+
.idea/**/sqlDataSources.xml
47+
.idea/**/dynamic.xml
48+
.idea/**/uiDesigner.xml
49+
50+
# Gradle:
51+
.idea/**/gradle.xml
52+
.idea/**/libraries
53+
54+
# CMake
55+
cmake-build-debug/
56+
57+
# Mongo Explorer plugin:
58+
.idea/**/mongoSettings.xml
59+
60+
## File-based project format:
61+
*.iws
62+
63+
## Plugin-specific files:
64+
65+
# IntelliJ
66+
out/
67+
68+
# mpeltonen/sbt-idea plugin
69+
.idea_modules/
70+
71+
# JIRA plugin
72+
atlassian-ide-plugin.xml
73+
74+
# Cursive Clojure plugin
75+
.idea/replstate.xml
76+
77+
# Crashlytics plugin (for Android Studio and IntelliJ)
78+
com_crashlytics_export_strings.xml
79+
crashlytics.properties
80+
crashlytics-build.properties
81+
fabric.properties
82+
### Linux template
83+
*~
84+
85+
# temporary files which can be created if a process still has a handle open of a deleted file
86+
.fuse_hidden*
87+
88+
# KDE directory preferences
89+
.directory
90+
91+
# Linux trash folder which might appear on any partition or disk
92+
.Trash-*
93+
94+
# .nfs files are created when an open file is removed but is still being accessed
95+
.nfs*
96+
### Windows template
97+
# Windows thumbnail cache files
98+
Thumbs.db
99+
ehthumbs.db
100+
ehthumbs_vista.db
101+
102+
# Dump file
103+
*.stackdump
104+
105+
# Folder config file
106+
Desktop.ini
107+
108+
# Recycle Bin used on file shares
109+
$RECYCLE.BIN/
110+
111+
# Windows Installer files
112+
*.cab
113+
*.msi
114+
*.msm
115+
*.msp
116+
117+
# Windows shortcuts
118+
*.lnk

LICENSE.md

+21
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
MIT License
2+
3+
Copyright (c) 2008-2017 NoahLE
4+
5+
Permission is hereby granted, free of charge, to any person obtaining a copy
6+
of this software and associated documentation files (the "Software"), to deal
7+
in the Software without restriction, including without limitation the rights
8+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9+
copies of the Software, and to permit persons to whom the Software is
10+
furnished to do so, subject to the following conditions:
11+
12+
The above copyright notice and this permission notice shall be included in all
13+
copies or substantial portions of the Software.
14+
15+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21+
SOFTWARE.

README.md

+3
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
# Programming notes
2+
3+
A disorganized set of programming notes

django.md

+4
Original file line numberDiff line numberDiff line change
@@ -137,6 +137,10 @@ class ClassName(models.Model):
137137
<target_model>,
138138
through='Intermediate table', # can make your own if you would like to add extra data
139139
)
140+
#extending the user model
141+
from django.contrib.auth.models import User
142+
user = models.OneToOneField(User, on_delete=models.CASCADE)
143+
140144
141145
class Meta:
142146
ordering = ['-var']

jira.md

+60
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
# JIRA Notes
2+
3+
Iron triange - scope, schedule, quality
4+
5+
We don't have the time, but have to make the time
6+
7+
Agile - good estimation, effective branching strategies for managing code, automated testing to protect quality, and continuous deployment to get fast feedback from users.
8+
9+
Estimate via time (x hours) or story points (0.5 - 20 points)
10+
11+
Time has emotional connection and can be iffy, story points are simply the amount of work and can be a collaborative process in deciding which points will be the most time consuming
12+
13+
If story points are taking too much time, they must be broken into smaller tasks
14+
15+
Estimate tasks in story points, track tasks in hours
16+
17+
Faster / shorter release cycles is ideal (keep deployed green)
18+
19+
## Scrum
20+
21+
Series of fixed length iterations (sprints)
22+
23+
Milestone - end of each sprint, proof of progress
24+
25+
Usually use task board and burnout chart for measuring
26+
27+
Three roles | description
28+
--- | ---
29+
Product owner | Build and manage the product backlog
30+
Closely partner with the business and the team to ensure everyone understands the work items in the product backlog
31+
Give the team clear guidance on which features to deliver next
32+
Decide when to ship the product with the predisposition towards more frequent delivery
33+
Keep in mind that a product owner is not a project manager. Product owners are not managing the status of the program. They focus on ensuring the development team delivers the most value to the business. Also, it's important that the product owner be an individual.
34+
35+
Scrum master | They coach the team, the product owner, and the business on the scrum process and look for ways to fine-tune their practice of it. An effective scrum master deeply understands the work being done by the team and can help the team optimize their delivery flow. As the facilitator-in-chief, they schedule the needed resources (both human and logistical) for sprint planning, stand-up, sprint review, and the sprint retrospective. Scrum masters also look to resolve impediments and distractions for the development team, insulating them from external disruptions whenever possible.
36+
Scrum team | Strong scrum teams approach their project with a clear "we" attitude. All members of the team help one another to ensure a successful sprint completion.
37+
38+
Four milestones spring planning:
39+
Ceremony | Description
40+
--- | ---
41+
Sprint planning | A team planning meeting that determines what to complete in the coming sprint.
42+
Daily stand-up | Also known as a daily scrum, a 15-minute mini-meeting for the software team to sync. What did I complete yesterday? What will I work on today? Am I blocked by anything?
43+
Sprint demo | A sharing meeting where the team shows what they've shipped in that sprint.
44+
Sprint retrospective | A review of what did and didn't go well with actions to make the next sprint better.
45+
46+
47+
48+
## The three ways of devops
49+
50+
Way | System name | Explanation
51+
--- | --- | ---
52+
The first way | System Thinking | emphasizes the performance of the entire system, as opposed to the performance of a specific silo of work or department — this can be as large a division or as small as an individual contributor.
53+
The second way | Amplify Feedback Loops | creating the right to left feedback loops. The goal of almost any process improvement initiative is to shorten and amplify feedback loops so necessary corrections can be continually made.
54+
The third way | Culture of Continual Experimentation and Learning | creating a culture that fosters two things: continual experimentation, taking risks and learning from failure; and understanding that repetition and practice is the prerequisite to mastery.
55+
56+
57+
#### Useful links
58+
59+
* [Agile](https://www.atlassian.com/agile/teams)
60+
* [Tracking tasks](https://confluence.atlassian.com/jirasoftwarecloud/configuring-estimation-and-tracking-764478030.html)

ubuntu-server.md

Whitespace-only changes.

0 commit comments

Comments
 (0)