├── .all-contributorsrc
├── .editorconfig
├── .github
├── CONTRIBUTING.md
├── ISSUE_TEMPLATE
│ ├── bug_report.yml
│ ├── config.yml
│ └── wiki-proposal.yml
├── PULL_REQUEST_TEMPLATE
│ └── pull_request_template.md
├── dependabot.yml
├── styles
│ ├── Vocab
│ │ └── word_list
│ │ │ └── accept.txt
│ └── style_guide
│ │ ├── Condescending.yml
│ │ ├── FirstPerson.yml
│ │ ├── Headings.yml
│ │ ├── Passive.yml
│ │ ├── SentenceLength.yml
│ │ ├── Slang.yml
│ │ ├── Spacing.yml
│ │ ├── Spelling.yml
│ │ └── Wordliness.yml
└── workflows
│ ├── build.yml
│ └── wiki_lint.yml
├── .pre-commit-config.yaml
├── .prettierignore
├── .prettierrc.json
├── .vale.ini
├── CONTRIBUTING.md
├── LICENSE
├── README.md
├── book.toml
├── index.html
├── netlify.toml
├── src
├── 404.md
├── SUMMARY.md
├── community-guides
│ ├── hackathons-101-a-step-by-step-guide-to-success.md
│ ├── how-to-constantly-upskill-yourself-as-a-developer.md
│ ├── how-to-create-an-ideal-software-engineering-resume.md
│ ├── resources-to-get-started-in-cybersecurity.md
│ ├── understanding-software-licenses.md
│ └── where-to-find-tech-jobs.md
└── faqs
│ ├── advice-for-freshers.md
│ ├── advice-for-professionals.md
│ ├── approaching-a-DSA-problem.md
│ ├── assets
│ └── github-small-foss-criteria.png
│ ├── campus-placements
│ ├── README.md
│ ├── effect-college-backlog.md
│ ├── effect-college-tier.md
│ ├── effect-of-cgpa-getting-job.md
│ └── effect-of-high-school-grades.md
│ ├── career-transitions
│ ├── README.md
│ ├── dev-to-devops.md
│ ├── game-dev.md
│ └── qa-sdet-to-dev.md
│ ├── contract-work.md
│ ├── effect-of-gap-year-on-getting-a-job.md
│ ├── finding-small-foss-projects-on-github.md
│ ├── freelancing.md
│ ├── health
│ ├── managing-eye-strain.md
│ └── managing-mental-health.md
│ ├── how-to-start-dsa.md
│ ├── performance-reviews.md
│ ├── switching-jobs
│ ├── README.md
│ ├── asking-for-referrals.md
│ ├── choosing-your-new-workplace.md
│ ├── negotiating-notice-periods.md
│ ├── negotiating-salaries.md
│ ├── planning-for-resignation.md
│ ├── rejecting-an-offer.md
│ ├── service-based-to-product-based.md
│ └── sharing-offer-letters-and-past-salaries.md
│ ├── tech-interviews.md
│ └── workplace-conundrums
│ ├── README.md
│ ├── dealing-with-background-verification.md
│ ├── dealing-with-colleagues-who-steal-credit.md
│ ├── dealing-with-micromanagement.md
│ └── dealing-with-toxic-workplaces.md
└── theme
├── book.js
├── css
├── chrome.css
├── general.css
├── print.css
└── variables.css
├── favicon.svg
├── highlight.css
├── highlight.js
└── index.hbs
/.all-contributorsrc:
--------------------------------------------------------------------------------
1 | {
2 | "files": [
3 | "README.md"
4 | ],
5 | "imageSize": 100,
6 | "commit": false,
7 | "contributors": [
8 | {
9 | "login": "Bhupesh-V",
10 | "name": "Bhupesh Varshney",
11 | "avatar_url": "https://avatars.githubusercontent.com/u/34342551?v=4",
12 | "profile": "http://bhupesh.me",
13 | "contributions": [
14 | "review",
15 | "content",
16 | "ideas",
17 | "projectManagement"
18 | ]
19 | },
20 | {
21 | "login": "Jarmos-san",
22 | "name": "Somraj Saha",
23 | "avatar_url": "https://avatars.githubusercontent.com/u/31373860?v=4",
24 | "profile": "https://jarmos.vercel.app",
25 | "contributions": [
26 | "review",
27 | "content",
28 | "ideas",
29 | "projectManagement",
30 | "infra",
31 | "tool",
32 | "code"
33 | ]
34 | },
35 | {
36 | "login": "sggts04",
37 | "name": "Shreyas Gupta",
38 | "avatar_url": "https://avatars.githubusercontent.com/u/20678047?v=4",
39 | "profile": "https://shreyasgupta.in",
40 | "contributions": [
41 | "content",
42 | "ideas"
43 | ]
44 | },
45 | {
46 | "login": "g0v1ndN",
47 | "name": "Govind S Nair",
48 | "avatar_url": "https://avatars.githubusercontent.com/u/115881229?v=4",
49 | "profile": "http://govindsnair.netlify.app",
50 | "contributions": [
51 | "content"
52 | ]
53 | },
54 | {
55 | "login": "triach-rold",
56 | "name": "Triach Rold",
57 | "avatar_url": "https://avatars.githubusercontent.com/u/156170660?v=4",
58 | "profile": "https://github.com/triach-rold",
59 | "contributions": [
60 | "content"
61 | ]
62 | },
63 | {
64 | "login": "asce-21",
65 | "name": "Sanam Dhar",
66 | "avatar_url": "https://avatars.githubusercontent.com/u/39599300?v=4",
67 | "profile": "https://asce-21.github.io/",
68 | "contributions": [
69 | "content"
70 | ]
71 | },
72 | {
73 | "login": "ryukaizen",
74 | "name": "Akash",
75 | "avatar_url": "https://avatars.githubusercontent.com/u/55140313?v=4",
76 | "profile": "https://github.com/ryukaizen",
77 | "contributions": [
78 | "content"
79 | ]
80 | }
81 | ],
82 | "contributorsPerLine": 7,
83 | "projectName": "wiki",
84 | "projectOwner": "developersIndia",
85 | "repoType": "github",
86 | "repoHost": "https://github.com",
87 | "skipCi": true,
88 | "commitType": "docs",
89 | "commitConvention": "angular"
90 | }
91 |
--------------------------------------------------------------------------------
/.editorconfig:
--------------------------------------------------------------------------------
1 | root = true
2 |
3 | [*]
4 | end_of_line = lf
5 | insert_final_newline = true
6 | # Indentation override for all JS under lib directory
7 | [*.{js,md}]
8 | indent_style = space
9 | indent_size = 2
10 |
11 | # Matches the exact files either package.json or .travis.yml
12 | [*.{json,yml}]
13 | indent_style = space
14 | indent_size = 2
15 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/bug_report.yml:
--------------------------------------------------------------------------------
1 | name: Bug Report 🐛
2 |
3 | description: File a bug report for broken URLs, grammatical errors, inconsistent site aesthetics & such.
4 | labels: ["bug"]
5 |
6 | assignees:
7 | - "Jarmos-san"
8 | - "Bhupesh-V"
9 |
10 | body:
11 | - type: markdown
12 | attributes:
13 | value: |
14 | "Thanks for taking the time to fill this report! It helps us understand the nature of the concern you've with the project."
15 |
16 | - type: textarea
17 | id: what-happened
18 | attributes:
19 | label: What Happened?
20 | description: Also tell us, what did you expect to happen? Found broken links? Include the new link & the link to the place where you found the broken links.
21 | placeholder: Please explain in detail the bug that you see & what did you expect. Include a screenshot (in GIF formats preferably) if possible.
22 | value: "Please explain in detail the bug that you see & what did you expect. Include a screenshot (in GIF formats preferably) if possible."
23 | validations:
24 | required: true
25 |
26 | - type: dropdown
27 | id: browsers
28 | attributes:
29 | label: What Browsers Are You Seeing the Problem On?
30 | multiple: true
31 | options:
32 | - Firefox
33 | - Chrome
34 | - Safari
35 | - Microsoft Edge
36 |
37 | - type: textarea
38 | id: logs
39 | attributes:
40 | label: Relevant Log Output
41 | description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
42 | render: shell
43 |
44 | - type: checkboxes
45 | id: terms
46 | attributes:
47 | label: Code of Conduct
48 | description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/developersIndia/.github/blob/main/CODE_OF_CONDUCT.md)
49 | options:
50 | - label: I agree to follow this project's Code of Conduct
51 | required: true
52 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/config.yml:
--------------------------------------------------------------------------------
1 | blank_issues_enabled: false
2 |
3 | contact_links:
4 | - name: developersIndia Community Support
5 | url: https://www.reddit.com/r/developersIndia
6 | about: Please ask & answer questions over here.
7 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/wiki-proposal.yml:
--------------------------------------------------------------------------------
1 | name: Wiki Proposal 📑
2 | description: Suggest an idea for the developersIndia wiki
3 | labels: ["proposal"]
4 | assignees:
5 | - Bhupesh-V
6 | body:
7 | - type: markdown
8 | attributes:
9 | value: |
10 | Thanks for taking the time to suggest an idea for a wiki proposal 🧡. If you have any questions, join us on Discord
11 | Make sure to enter a descriptive issue title above. E.g. "How to navigate interivews in product based companies"
12 |
13 | - type: checkboxes
14 | id: read-contrib
15 | attributes:
16 | label: Have you read the contributing guidelines for proposing a wiki?
17 | description: Please go through them once if you haven't [CONTRIBUTING.md](https://github.com/developersIndia/wiki/blob/main/CONTRIBUTING.md)
18 | options:
19 | - label: I have read the contributing guidelines.
20 | required: true
21 | - type: textarea
22 | id: description
23 | attributes:
24 | label: What's this proposal about? What should this wiki cover? Who's the audience?
25 | placeholder: The wiki should talk about ...
26 | validations:
27 | required: true
28 | - type: dropdown
29 | id: is-faq
30 | attributes:
31 | label: Choose the category for this wiki
32 | description: We encourage wikis that answer frequently asked questions on the developersIndia subreddit.
33 | options:
34 | - "Community Guide"
35 | - "FAQ"
36 | validations:
37 | required: true
38 | - type: textarea
39 | id: faq-list
40 | attributes:
41 | label: If this is a FAQ on the sub, please include links of similar posts from the subreddit
42 | validations:
43 | required: false
44 | - type: dropdown
45 | id: your-role
46 | attributes:
47 | label: Are you interested in authoring this wiki guide?
48 | description: Being an author makes you responsible for researching every little detail when writing a wiki. Once its written you have to also keep it updated timely.
49 | options:
50 | - "Yes"
51 | - "No"
52 | validations:
53 | required: true
54 | - type: checkboxes
55 | id: terms
56 | attributes:
57 | label: Code of Conduct
58 | description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/developersIndia/.github/blob/main/CODE_OF_CONDUCT.md)
59 | options:
60 | - label: I agree to follow the community's Code of Conduct
61 | required: true
62 |
--------------------------------------------------------------------------------
/.github/PULL_REQUEST_TEMPLATE/pull_request_template.md:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/developersIndia/wiki/dcc00de23521b55b0d788ce3e8eb1a6aa0b6583f/.github/PULL_REQUEST_TEMPLATE/pull_request_template.md
--------------------------------------------------------------------------------
/.github/dependabot.yml:
--------------------------------------------------------------------------------
1 | version: 2
2 | updates:
3 | - package-ecosystem: "github-actions"
4 | directory: "/"
5 | schedule:
6 | interval: "daily"
7 | time: "06:00"
8 | timezone: "Asia/Kolkata"
9 | commit-message:
10 | prefix: "🔀"
11 | labels: ["github-actions"]
12 | target-branch: "main"
13 | reviewers:
14 | - "Jarmos-san"
15 | - "bhupesh-V"
16 |
--------------------------------------------------------------------------------
/.github/styles/Vocab/word_list/accept.txt:
--------------------------------------------------------------------------------
1 | developersIndia
2 | Angelist
3 | Hirect
4 | remotists
5 | YouTube
6 | Upskill
7 | cfpland
8 | subreddits
9 | subreddit
10 | Canva
11 | Algos
12 | Hinglish
13 | Roadmaps
14 | pseudocode
15 | Leetcode
16 | Codeforces
17 | bruteforce
18 | Codechef
19 | [Ss]ubroute
20 | [Ss]ubstring
21 | uid
22 | jq
23 | Vue
24 | [Gg]eosearch
25 | Nginx
26 | Docxtemplater
27 | [Cc]onfig
28 | Algolia
29 | Typesense
30 | Symfony
31 | Laravel
32 | Strapi
33 | [Rr]eindexed
34 | chatbox
35 | Lucene
36 | Levenshtein
37 | Swiftype
38 | [Tt]okenizer
39 | [Tt]okenization
40 | [Aa]sync
41 | [Ee]nqueued
42 | [Ff]ilepath
43 | [Ww]ebshop
44 | boolean
45 | Taj
46 | Mahal
47 | [Cc]ertbot
48 | [Tt]oolchain
49 | Jieba
50 | Lindera
51 | Netlify
52 | [Oo]verconsumption
53 | [Gg]eopositioning
54 | hanzi
55 | [Aa]utobatching
56 | [Ii]mpactful
57 | [Ll]owercased
58 | [Mm]ultitenancy
59 | [Rr]ulesets
60 | [Pp]repended
61 | [Aa]nonymized
62 | [Ss]erverless
63 | [Aa]utoscaling
64 | [Hh]ostname
65 | cron
66 | mkcert
67 | [Uu]pvote
68 | Docsearch
69 | [Oo]rderable
70 | [Pp]erformant
71 | [Ss]ubproject
72 | '/\(\B(.*?)\)'
73 | [Ss]harding
74 | jsonlines
75 | SDKs
76 | SSDs
77 | HDDs
78 | UIs
79 | JWTs
80 | APIs
81 | AMIs
82 |
83 | linkedin
84 | lakh
85 | github
86 | txt
87 | Ctrl
88 | colorscheme
89 | vimrc
90 | netrw
91 | devfolio
92 | Nondeterministic
93 | NFA
94 | dotfiles
95 | Esc
96 | xmodmap
97 | CapsLock
98 | yyyy
99 | Tuxy
100 | rsync
101 | OSS
102 | NeoVim
103 | NERDTree
104 | vimmers
105 | AST
106 | ext4
107 | debugfs
108 | filesystem
109 | ext2
110 | ext3
111 | Btrfs
112 | CleanCode
113 | WebDev
114 | utf
115 | api
116 | json
117 | env
118 | ffmpeg
119 | GIFs
120 | cheatsheet
121 | Kewl
122 | disqus
123 | linux
124 | Merkel
125 | url
126 | nnoremap
127 | ascii
128 | javascript
129 | css
130 | ctrl
131 | foldmethod
132 | Ok
133 | ok
134 | bitrate
135 | neovim
136 | Youtube
137 | freeCodeCamp
138 | HackerNews
139 | StackOverflow
140 | gif
141 | CLIs
142 | struct
143 | config
144 | amd64
145 | golang
146 | Postgres
147 | stackoverflow
148 | ide
149 | emacs
150 | Ultisnips
151 | ultisnips
152 | docstring
153 | ffprobe
154 | Sharding
155 | sharded
156 | unsharded
157 | Goroutines
158 | Argparse
159 | searx
160 | DuckDuckGo
161 | fzf
162 | brainer
163 | FastAPI
164 | microservices
165 | worktrees
166 | SDK
167 | https
168 | io
169 | opencv
170 | OpenCV
171 | PIL
172 | Jupyter
173 | ipynb
174 | Codebases
175 | codebase
176 | ctags
177 | LSP
178 | lsc
179 | vim
180 | repo
181 | changelog
182 | diff
183 | blog
184 | Blogs
185 | emoji
186 | TIL
187 | printf
188 | RSS
189 | TOML
190 | YAML
191 | plugins
192 | Ubuntu
193 | jpg
194 | homebrew
195 | NumPy
196 | CDN
197 | ifconfig
198 | png
199 | README's
200 | offline
201 | memes
202 | blogging
203 | freecodecamp
204 | blogs
205 | dev
206 | GitHub
207 | bloggers
208 | meetup
209 | CLI
210 | zsh
211 | dotman
212 | OpenVPN
213 | PostgreSQL
214 | WriteTheDocs
215 | Thoughtbot
216 | BASHing
217 | vim
218 | vim
219 | LinkedIn
220 | gopls
221 | vimscript
222 | heredoc
223 | lua
224 | lsp
225 | nvim
226 | lspsaga
227 | btw
228 | pipefail
229 | lspconfig
230 | unpushed
231 | IITs
232 | JEE
233 | Btech
234 | cyberciti
235 | gocron
236 | xclip
237 | terminfo
238 | truecolor
239 | COLORTERM
240 | python3
241 | virtualenv
242 | pynvim
243 | health
244 | ofc
245 | jpeg
246 | csv
247 | defaultdict
248 | spammy
249 | Jira
250 | Gitlab
251 | httpbin
252 | Microsystems
253 | OpenTelemetry
254 | OpenCensus
255 | OpenTracing
256 | SDKs
257 | OpenMetrics
258 | Uber
259 | prometheus
260 | openmetrics
261 | CNCF
262 | opentelemetry
263 | backend
264 | linter
265 | RedHat
266 | VSCode
267 | linters
268 | Jina
269 | OTLP
270 | POC
271 | Timestamp
272 | WIP
273 | HackerNoon
274 | Hashnode
275 | Hotstar
276 | devtool
277 | VSCodium
278 | utils
279 | meetups
280 | protobuf
281 | pprof
282 | SQLite
283 | pyright
284 | timestamp
285 | operationalize
286 | OLAP
287 | ETL
288 | Elasticsearch
289 | MySQL
290 | Airbyte
291 | Redshift
292 | BigQuery
293 | Mutex
294 | mutexes
295 | malloc
296 | GC
297 | barebones
298 | goroutines
299 | DevOps
300 | DevAdvocate
301 | Kotlin
302 | SFTP
303 | AWS
304 | OpenSSH
305 | IAM
306 | S3
307 | VPC
308 | hostname
309 | asyncio
310 | callstack
311 | StackExchange
312 | Structs
313 | init
314 | Memoization
315 | RwMutex
316 |
--------------------------------------------------------------------------------
/.github/styles/style_guide/Condescending.yml:
--------------------------------------------------------------------------------
1 | ---
2 | # Error: style_guide.Spacing.yml
3 |
4 | extends: existence
5 | message: Using '%s' may come across as condescending.
6 | link: https://css-tricks.com/words-avoid-educational-writing/
7 | level: error
8 | ignorecase: true
9 | tokens:
10 | - obvious
11 | - obviously
12 | - simple
13 | - simply
14 | - easy
15 | - easily
16 | - of course
17 | - clearly
18 | - everyone knows
19 |
--------------------------------------------------------------------------------
/.github/styles/style_guide/FirstPerson.yml:
--------------------------------------------------------------------------------
1 | ---
2 | # Suggestion: style_guide.FirstPerson.yml
3 |
4 | # We want to avoid using singular first person pronouns
5 | extends: existence
6 | message: "Avoid first-person pronouns such as '%s' unless writing FAQs"
7 | link: 'https://developers.google.com/style/pronouns#personal-pronouns'
8 | ignorecase: true
9 | level: suggestion
10 | nonword: true
11 | tokens:
12 | - (?:^|\s)I\s
13 | - (?:^|\s)I,\s
14 | - \bI'm\b
15 | - \bme\b
16 | - \bmy\b
17 | - \bmine\b
18 |
19 |
--------------------------------------------------------------------------------
/.github/styles/style_guide/Headings.yml:
--------------------------------------------------------------------------------
1 | ---
2 | # Suggestion: style_guide.Headings.yml
3 |
4 | # Our headings should use sentence-style capitalization. The exceptions include any headings that maybe a list, start with "Step 1: Do this", and the list of words below
5 | extends: capitalization
6 | message: "'%s' should use sentence-style capitalization."
7 | link: 'https://developers.google.com/style/capitalization#capitalization-in-titles-and-headings'
8 | level: suggestion
9 | scope: heading
10 | match: $sentence
11 | indicators:
12 | - ':'
13 | - '.'
14 | exceptions:
15 | - Azure
16 | - CLI
17 | - Code
18 | - Docker
19 | - SDK
20 | - SDKs
21 | - Kubernetes
22 | - Linux
23 | - macOS
24 | - Marketplace
25 | - MongoDB
26 | - TypeScript
27 | - URLs
28 | - Visual
29 | - VS
30 | - Windows
31 | - Meilisearch
32 | - AWS
33 | - Amazon Web Services
34 | - DigitalOcean
35 | - GCP
36 | - Qovery
37 | - GCP
38 | - Google Cloud Platform
39 | - Compute Engine
40 | - GitHub
41 | - JSON
42 | - API
43 | - VuePress
44 | - OpenAPI
45 | - Elasticsearch
46 | - Algolia
47 | - DevOps
48 | - Lucene-Solr
49 | - App Service Auto-Scale
50 | - Certbot
51 | - Bleve & Tantivy
52 | - Google Cloud Console
53 | - AMIs
54 | - '\b\s[0-9]:\s[A-Z]' # Step 1: Do this
55 | - '[0-9]\.\s[A-Z]' # 1. Do this
56 | #- '"(.*?)"' #Ignore text in ""
57 |
--------------------------------------------------------------------------------
/.github/styles/style_guide/Passive.yml:
--------------------------------------------------------------------------------
1 | ---
2 | # Suggestion: style_guide.Passive.yml
3 |
4 | extends: existence
5 | link: 'https://developers.google.com/style/voice'
6 | message: "In general, use active voice instead of passive voice ('%s')."
7 | ignorecase: true
8 | level: suggestion
9 | raw:
10 | - \b(am|are|were|being|is|been|was|be)\b\s*
11 | tokens:
12 | - '[\w]+ed'
13 | - awoken
14 | - beat
15 | - become
16 | - been
17 | - begun
18 | - bent
19 | - beset
20 | - bet
21 | - bid
22 | - bidden
23 | - bitten
24 | - bled
25 | - blown
26 | - born
27 | - bought
28 | - bound
29 | - bred
30 | - broadcast
31 | - broken
32 | - brought
33 | - built
34 | - burnt
35 | - burst
36 | - cast
37 | - caught
38 | - chosen
39 | - clung
40 | - come
41 | - cost
42 | - crept
43 | - cut
44 | - dealt
45 | - dived
46 | - done
47 | - drawn
48 | - dreamt
49 | - driven
50 | - drunk
51 | - dug
52 | - eaten
53 | - fallen
54 | - fed
55 | - felt
56 | - fit
57 | - fled
58 | - flown
59 | - flung
60 | - forbidden
61 | - foregone
62 | - forgiven
63 | - forgotten
64 | - forsaken
65 | - fought
66 | - found
67 | - frozen
68 | - given
69 | - gone
70 | - gotten
71 | - ground
72 | - grown
73 | - heard
74 | - held
75 | - hidden
76 | - hit
77 | - hung
78 | - hurt
79 | - kept
80 | - knelt
81 | - knit
82 | - known
83 | - laid
84 | - lain
85 | - leapt
86 | - learnt
87 | - led
88 | - left
89 | - lent
90 | - let
91 | - lighted
92 | - lost
93 | - made
94 | - meant
95 | - met
96 | - misspelt
97 | - mistaken
98 | - mown
99 | - overcome
100 | - overdone
101 | - overtaken
102 | - overthrown
103 | - paid
104 | - pled
105 | - proven
106 | - put
107 | - quit
108 | - read
109 | - rid
110 | - ridden
111 | - risen
112 | - run
113 | - rung
114 | - said
115 | - sat
116 | - sawn
117 | - seen
118 | - sent
119 | - set
120 | - sewn
121 | - shaken
122 | - shaven
123 | - shed
124 | - shod
125 | - shone
126 | - shorn
127 | - shot
128 | - shown
129 | - shrunk
130 | - shut
131 | - slain
132 | - slept
133 | - slid
134 | - slit
135 | - slung
136 | - smitten
137 | - sold
138 | - sought
139 | - sown
140 | - sped
141 | - spent
142 | - spilt
143 | - spit
144 | - split
145 | - spoken
146 | - spread
147 | - sprung
148 | - spun
149 | - stolen
150 | - stood
151 | - stridden
152 | - striven
153 | - struck
154 | - strung
155 | - stuck
156 | - stung
157 | - stunk
158 | - sung
159 | - sunk
160 | - swept
161 | - swollen
162 | - sworn
163 | - swum
164 | - swung
165 | - taken
166 | - taught
167 | - thought
168 | - thrived
169 | - thrown
170 | - thrust
171 | - told
172 | - torn
173 | - trodden
174 | - understood
175 | - upheld
176 | - upset
177 | - wed
178 | - wept
179 | - withheld
180 | - withstood
181 | - woken
182 | - won
183 | - worn
184 | - wound
185 | - woven
186 | - written
187 | - wrung
188 |
--------------------------------------------------------------------------------
/.github/styles/style_guide/SentenceLength.yml:
--------------------------------------------------------------------------------
1 | ---
2 | # Warning: style_guide.SentenceLength.yml
3 |
4 | # Counts words in a sentence and alerts if a sentence exceeds 42 words.
5 | extends: occurrence
6 | message: 'Shorter sentences improve readability (max 40 words).'
7 | scope: sentence
8 | link: https://docs.gitlab.com/ee/development/documentation/styleguide/index.html#language
9 | level: warning
10 | max: 40
11 | token: \b(\w+)\b
12 |
13 |
14 |
--------------------------------------------------------------------------------
/.github/styles/style_guide/Slang.yml:
--------------------------------------------------------------------------------
1 | ---
2 | # Warning: style_guide.Slang.yml
3 |
4 | extends: existence
5 | message: "Don't use internet slang abbreviations such as '%s'."
6 | link: 'https://developers.google.com/style/abbreviations'
7 | ignorecase: true
8 | level: error
9 | tokens:
10 | - 'tl;dr'
11 | - ymmv
12 | - rtfm
13 | - imo
14 | - fwiw
15 |
--------------------------------------------------------------------------------
/.github/styles/style_guide/Spacing.yml:
--------------------------------------------------------------------------------
1 | ---
2 | # Error: style_guide.Condescending.yml
3 |
4 | # Use a space between words, sentences, and punctuation marks
5 | extends: existence
6 | message: "'%s' should have one space."
7 | link: https://docs.microsoft.com/en-us/style-guide/punctuation/periods
8 | level: error
9 | nonword: true
10 | tokens:
11 | - '[a-z]\s{2,}[a-z]' # ensure only one space between words
12 | - '[a-z][.?!:;",] {2,}[A-Z]' # one space between sentences (end. new)
13 | - '[a-z][.?!:;",][A-Z]' #(end.new)
14 | - '[\w.?!,\(\)\-":] {2,}[\w.?!,\(\)\-":]' #only one space after ,.?
15 |
16 |
--------------------------------------------------------------------------------
/.github/styles/style_guide/Spelling.yml:
--------------------------------------------------------------------------------
1 | ---
2 | # Warning: style_guide.Spelling.yml
3 |
4 | # Checks if your words exist in the dictionary. Any exceptions (including developersIndia) should be defined in `styles/Vocab/word_list/accept.txt`
5 | extends: spelling
6 | message: "Did you really mean '%s'?"
7 | level: warning
8 | filters:
9 | - 'Vale.*\b'
10 |
--------------------------------------------------------------------------------
/.github/styles/style_guide/Wordliness.yml:
--------------------------------------------------------------------------------
1 | extends: substitution
2 | message: "Consider using '%s' instead of '%s'."
3 | link: https://docs.microsoft.com/en-us/style-guide/word-choice/use-simple-words-concise-sentences
4 | ignorecase: true
5 | level: warning
6 | action:
7 | name: replace
8 | swap:
9 | (?:give|gave) rise to: lead to
10 | (?:previous|prior) to: before
11 | a (?:large)? majority of: most
12 | a (?:large)? number of: many
13 | a myriad of: myriad
14 | adversely impact: hurt
15 | all across: across
16 | all of a sudden: suddenly
17 | all of these: these
18 | all of: all
19 | all-time record: record
20 | almost all: most
21 | almost never: seldom
22 | along the lines of: similar to
23 | an adequate number of: enough
24 | an appreciable number of: many
25 | an estimated: about
26 | any and all: all
27 | are in agreement: agree
28 | as a matter of fact: in fact
29 | as a means of: to
30 | as a result of: because of
31 | as of yet: yet
32 | as per: per
33 | at a later date: later
34 | at all times: always
35 | at the present time: now
36 | at this point in time: at this point
37 | based in large part on: based on
38 | based on the fact that: because
39 | basic necessity: necessity
40 | because of the fact that: because
41 | came to a realization: realized
42 | came to an abrupt end: ended abruptly
43 | carry out an evaluation of: evaluate
44 | close down: close
45 | closed down: closed
46 | complete stranger: stranger
47 | completely separate: separate
48 | concerning the matter of: regarding
49 | conduct a review of: review
50 | conduct an investigation: investigate
51 | conduct experiments: experiment
52 | continue on: continue
53 | despite the fact that: although
54 | disappear from sight: disappear
55 | drag and drop: drag
56 | drag-and-drop: drag
57 | doomed to fail: doomed
58 | due to the fact that: because
59 | during the period of: during
60 | during the time that: while
61 | emergency situation: emergency
62 | except when: unless
63 | excessive number: too many
64 | extend an invitation: invite
65 | fall down: fall
66 | fell down: fell
67 | for the duration of: during
68 | gather together: gather
69 | has the ability to: can
70 | has the capacity to: can
71 | has the opportunity to: could
72 | hold a meeting: meet
73 | if this is not the case: if not
74 | in a careful manner: carefully
75 | in a thoughtful manner: thoughtfully
76 | in a timely manner: timely
77 | in an effort to: to
78 | in between: between
79 | in lieu of: instead of
80 | in many cases: often
81 | in most cases: usually
82 | in order to: to
83 | in some cases: sometimes
84 | in spite of the fact that: although
85 | in spite of: despite
86 | in the (?:very)? near future: soon
87 | in the event that: if
88 | in the neighborhood of: roughly
89 | in the vicinity of: close to
90 | it would appear that: apparently
91 | lift up: lift
92 | made reference to: referred to
93 | make reference to: refer to
94 | mix together: mix
95 | none at all: none
96 | not in a position to: unable
97 | not possible: impossible
98 | of major importance: important
99 | perform an assessment of: assess
100 | pertaining to: about
101 | place an order: order
102 | plays a key role in: is essential to
103 | present time: now
104 | readily apparent: apparent
105 | some of the: some
106 | span across: span
107 | subsequent to: after
108 | successfully complete: complete
109 | sufficient number (?:of)?: enough
110 | take action: act
111 | take into account: consider
112 | the question as to whether: whether
113 | there is no doubt but that: doubtless
114 | this day and age: this age
115 | this is a subject that: this subject
116 | time (?:frame|period): time
117 | under the provisions of: under
118 | until such time as: until
119 | used for fuel purposes: used for fuel
120 | whether or not: whether
121 | with regard to: regarding
122 | with the exception of: except for
123 |
--------------------------------------------------------------------------------
/.github/workflows/build.yml:
--------------------------------------------------------------------------------
1 | name: Netlify Deploy
2 |
3 | on:
4 | # push:
5 | # branches:
6 | # - 'main'
7 | workflow_dispatch:
8 |
9 | jobs:
10 | deploy:
11 | runs-on: ubuntu-latest
12 |
13 | permissions:
14 | contents: write
15 |
16 | steps:
17 | - name: Checkout Repository
18 | uses: 'actions/checkout@v4'
19 |
20 | - name: Install static-sitemap-cli
21 | run: npm install static-sitemap-cli
22 |
23 | - name: Setup mdBook
24 | uses: extractions/setup-crate@v1
25 | with:
26 | owner: rust-lang
27 | name: mdbook
28 |
29 | - name: Generate the Wiki
30 | run: mdbook build
31 |
32 | # TODOL fix the issue when the sitemap doesn't get generated when a commit is directly pushed to the main branch
33 | - name: Generate sitemap
34 | run: |
35 | cd book
36 | npx sscli --no-clean --base https://wiki.developersindia.in
37 |
38 | - name: Deploy to Netlify
39 | uses: nwtgck/actions-netlify@v3.0
40 | with:
41 | publish-dir: 'book'
42 | production-branch: main
43 | production-deploy: true
44 | netlify-config-path: netlify.toml
45 | github-token: ${{ secrets.GITHUB_TOKEN }}
46 | deploy-message: "Deploy from GitHub Actions"
47 | enable-pull-request-comment: false
48 | enable-commit-comment: false
49 | overwrites-pull-request-comment: false
50 | github-deployment-environment: "Netlify Deployment"
51 | github-deployment-description: "The production deployment environment on Netlify."
52 | fails-without-credentials: true
53 | env:
54 | NETLIFY_AUTH_TOKEN: ${{ secrets.NETLIFY_AUTH_TOKEN }}
55 | NETLIFY_SITE_ID: ${{ secrets.NETLIFY_SITE_ID }}
56 | timeout-minutes: 1
57 |
--------------------------------------------------------------------------------
/.github/workflows/wiki_lint.yml:
--------------------------------------------------------------------------------
1 | name: Wiki Style Guide Lint
2 | on:
3 | workflow_dispatch:
4 |
5 | jobs:
6 | vale:
7 | name: runner / vale
8 | runs-on: ubuntu-latest
9 | steps:
10 | - uses: actions/checkout@v4
11 | - uses: errata-ai/vale-action@reviewdog
12 | with:
13 | fail_on_error: true
14 | debug: true
15 | env:
16 | # Required, set by GitHub actions automatically:
17 | # https://docs.github.com/en/actions/security-guides/automatic-token-authentication#about-the-github_token-secret
18 | GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
--------------------------------------------------------------------------------
/.pre-commit-config.yaml:
--------------------------------------------------------------------------------
1 | # See https://pre-commit.com for more information
2 | # See https://pre-commit.com/hooks.html for more hooks
3 | repos:
4 | - repo: https://github.com/pre-commit/pre-commit-hooks
5 | rev: v3.2.0
6 | hooks:
7 | - id: trailing-whitespace
8 | - id: end-of-file-fixer
9 | - id: check-yaml
10 | - id: check-added-large-files
11 |
12 | - repo: https://github.com/pre-commit/mirrors-prettier
13 | rev: v2.7.1
14 | hooks:
15 | - id: prettier
16 |
--------------------------------------------------------------------------------
/.prettierignore:
--------------------------------------------------------------------------------
1 | book
2 | .github
3 | **/SUMMARY.md
4 |
--------------------------------------------------------------------------------
/.prettierrc.json:
--------------------------------------------------------------------------------
1 | {
2 | "proseWrap": "always"
3 | }
4 |
--------------------------------------------------------------------------------
/.vale.ini:
--------------------------------------------------------------------------------
1 | StylesPath = .github/styles
2 | MinAlertLevel = suggestion
3 |
4 | Vocab = word_list
5 |
6 | [*.md]
7 | BasedOnStyles = style_guide
8 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | # Contributing to developersIndia wiki
2 |
3 | First off, thanks for taking the time to contribute! 🎉 Make sure you follow
4 | below guidelines before contributing.
5 |
6 | ## Setup
7 |
8 | ### Prerequisites
9 |
10 | You need to have the follow tools installed:
11 |
12 | - [`mdbook`](https://github.com/rust-lang/mdBook/releases)
13 |
14 |
15 |
16 | Once installed you can verify if the software are working properly or not by
17 | invoking the following commands;
18 |
19 | ```shell
20 | # Verify the mdbook CLI tool is installed on your system
21 | mdbook --version
22 | # Example output: mdbook v0.4.21
23 | ```
24 |
25 | ### Getting Started
26 |
27 | 1. Fork the repository & clone it on your local machine:
28 |
29 | ```shell
30 | git clone github.com/developersIndia/wiki
31 | ```
32 |
33 | 2. Run the development server to see the changes live:
34 |
35 | ```shell
36 | mdbook serve
37 | ```
38 |
39 |
52 |
53 |
81 |
82 | ## What qualifies as a "wiki"?
83 |
84 | ### FAQs
85 |
86 | 1. Questions that are repeatedly asked on our subreddit (or discord). E.g _"How
87 | to prepare yourself for a product job"_ or _"How to switch from service based
88 | to a product-based job"_.
89 | 2. FAQs are highly valuable to the community & we expect you to constantly
90 | update them as time changes.
91 | 3. While adding insightful posts & comments from the community, make sure you
92 | follow below guidelines:
93 | - Follow the pattern of the existing FAQs.
94 | - Always make sure the content is relevant to the topic. If a category for
95 | FAQs doesn't exist, create a proposal with the necessary posts/comments
96 | that can belong to it.
97 | - Always make sure the content is not offensive. If moderators have removed a
98 | post, avoid linking any content from it.
99 | - Avoid linking any comments that are "reactions" to the post (E.g. _congrats
100 | OP_, _I'm in same situation_, etc).
101 | - Avoid linking any comments that are "follow-up" questions to a post. Only
102 | link direct answers to the post.
103 | - Add comments that are are insightful, these usually have a lot of upvotes
104 | or 1-2 paragraphs or points of detailed advice.
105 |
106 | ### Community Guides
107 |
108 | 1. Long text guides which will help developersIndia (or the tech community) in
109 | general. You can suggest ideas by creating a proposal. A nice example would
110 | be _"How to improve your productivity as a developer"_. Go very niche with
111 | the topic.
112 | 2. Basically these are guides that are not FAQs but are still very helpful to
113 | the community. Avoid proposing tutorials, like how to create a HTMX app.
114 | 3. Try to make you wiki as detailed as possible. We don't expect you to know
115 | everything.
116 | 4. Your intention while writing a wiki should be to think of the community as a
117 | whole.
118 | 5. Try to avoid any personal opinions. Try to be as close as possible towards
119 | facts.
120 |
121 | ## Process of contributing a wiki
122 |
123 | 1. You create a
124 | [wiki proposal](https://github.com/developersIndia/wiki/issues/new/choose)
125 | with an intention to work on it.
126 | 2. Community Members review your proposal & ask/suggest any follow ups.
127 | 3. You take your time to write this wiki. We use markdown for writing and vale
128 | for prose linting.
129 | 4. You create a PR mentioning the issue no.
130 | 5. One (or more) community members from our team reviews your Wiki. You fix any
131 | issues (grammar etc)
132 | 6. Once the PR is merged. We announce the new wiki addition on our subreddit
133 | (and discord).
134 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | Creative Commons Legal Code
2 |
3 | CC0 1.0 Universal
4 |
5 | CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE
6 | LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN
7 | ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS
8 | INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES
9 | REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS
10 | PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM
11 | THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED
12 | HEREUNDER.
13 |
14 | Statement of Purpose
15 |
16 | The laws of most jurisdictions throughout the world automatically confer
17 | exclusive Copyright and Related Rights (defined below) upon the creator
18 | and subsequent owner(s) (each and all, an "owner") of an original work of
19 | authorship and/or a database (each, a "Work").
20 |
21 | Certain owners wish to permanently relinquish those rights to a Work for
22 | the purpose of contributing to a commons of creative, cultural and
23 | scientific works ("Commons") that the public can reliably and without fear
24 | of later claims of infringement build upon, modify, incorporate in other
25 | works, reuse and redistribute as freely as possible in any form whatsoever
26 | and for any purposes, including without limitation commercial purposes.
27 | These owners may contribute to the Commons to promote the ideal of a free
28 | culture and the further production of creative, cultural and scientific
29 | works, or to gain reputation or greater distribution for their Work in
30 | part through the use and efforts of others.
31 |
32 | For these and/or other purposes and motivations, and without any
33 | expectation of additional consideration or compensation, the person
34 | associating CC0 with a Work (the "Affirmer"), to the extent that he or she
35 | is an owner of Copyright and Related Rights in the Work, voluntarily
36 | elects to apply CC0 to the Work and publicly distribute the Work under its
37 | terms, with knowledge of his or her Copyright and Related Rights in the
38 | Work and the meaning and intended legal effect of CC0 on those rights.
39 |
40 | 1. Copyright and Related Rights. A Work made available under CC0 may be
41 | protected by copyright and related or neighboring rights ("Copyright and
42 | Related Rights"). Copyright and Related Rights include, but are not
43 | limited to, the following:
44 |
45 | i. the right to reproduce, adapt, distribute, perform, display,
46 | communicate, and translate a Work;
47 | ii. moral rights retained by the original author(s) and/or performer(s);
48 | iii. publicity and privacy rights pertaining to a person's image or
49 | likeness depicted in a Work;
50 | iv. rights protecting against unfair competition in regards to a Work,
51 | subject to the limitations in paragraph 4(a), below;
52 | v. rights protecting the extraction, dissemination, use and reuse of data
53 | in a Work;
54 | vi. database rights (such as those arising under Directive 96/9/EC of the
55 | European Parliament and of the Council of 11 March 1996 on the legal
56 | protection of databases, and under any national implementation
57 | thereof, including any amended or successor version of such
58 | directive); and
59 | vii. other similar, equivalent or corresponding rights throughout the
60 | world based on applicable law or treaty, and any national
61 | implementations thereof.
62 |
63 | 2. Waiver. To the greatest extent permitted by, but not in contravention
64 | of, applicable law, Affirmer hereby overtly, fully, permanently,
65 | irrevocably and unconditionally waives, abandons, and surrenders all of
66 | Affirmer's Copyright and Related Rights and associated claims and causes
67 | of action, whether now known or unknown (including existing as well as
68 | future claims and causes of action), in the Work (i) in all territories
69 | worldwide, (ii) for the maximum duration provided by applicable law or
70 | treaty (including future time extensions), (iii) in any current or future
71 | medium and for any number of copies, and (iv) for any purpose whatsoever,
72 | including without limitation commercial, advertising or promotional
73 | purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each
74 | member of the public at large and to the detriment of Affirmer's heirs and
75 | successors, fully intending that such Waiver shall not be subject to
76 | revocation, rescission, cancellation, termination, or any other legal or
77 | equitable action to disrupt the quiet enjoyment of the Work by the public
78 | as contemplated by Affirmer's express Statement of Purpose.
79 |
80 | 3. Public License Fallback. Should any part of the Waiver for any reason
81 | be judged legally invalid or ineffective under applicable law, then the
82 | Waiver shall be preserved to the maximum extent permitted taking into
83 | account Affirmer's express Statement of Purpose. In addition, to the
84 | extent the Waiver is so judged Affirmer hereby grants to each affected
85 | person a royalty-free, non transferable, non sublicensable, non exclusive,
86 | irrevocable and unconditional license to exercise Affirmer's Copyright and
87 | Related Rights in the Work (i) in all territories worldwide, (ii) for the
88 | maximum duration provided by applicable law or treaty (including future
89 | time extensions), (iii) in any current or future medium and for any number
90 | of copies, and (iv) for any purpose whatsoever, including without
91 | limitation commercial, advertising or promotional purposes (the
92 | "License"). The License shall be deemed effective as of the date CC0 was
93 | applied by Affirmer to the Work. Should any part of the License for any
94 | reason be judged legally invalid or ineffective under applicable law, such
95 | partial invalidity or ineffectiveness shall not invalidate the remainder
96 | of the License, and in such case Affirmer hereby affirms that he or she
97 | will not (i) exercise any of his or her remaining Copyright and Related
98 | Rights in the Work or (ii) assert any associated claims and causes of
99 | action with respect to the Work, in either case contrary to Affirmer's
100 | express Statement of Purpose.
101 |
102 | 4. Limitations and Disclaimers.
103 |
104 | a. No trademark or patent rights held by Affirmer are waived, abandoned,
105 | surrendered, licensed or otherwise affected by this document.
106 | b. Affirmer offers the Work as-is and makes no representations or
107 | warranties of any kind concerning the Work, express, implied,
108 | statutory or otherwise, including without limitation warranties of
109 | title, merchantability, fitness for a particular purpose, non
110 | infringement, or the absence of latent or other defects, accuracy, or
111 | the present or absence of errors, whether or not discoverable, all to
112 | the greatest extent permissible under applicable law.
113 | c. Affirmer disclaims responsibility for clearing rights of other persons
114 | that may apply to the Work or any use thereof, including without
115 | limitation any person's Copyright and Related Rights in the Work.
116 | Further, Affirmer disclaims responsibility for obtaining any necessary
117 | consents, permissions or other rights required for any use of the
118 | Work.
119 | d. Affirmer understands and acknowledges that Creative Commons is not a
120 | party to this document and has no duty or obligation with respect to
121 | this CC0 or use of the Work.
122 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # The r/developersIndia Community Wiki
2 |
3 | [](#contributors-)
4 | [](https://discordapp.com/invite/MKXMSNC)
5 | [](https://www.reddit.com/r/developersIndia/)
6 |
7 | Welcome to the developersIndia Community Wiki! This repository is home to our
8 | face-lifted community wiki which you'll find across all the platforms our
9 | community is active on.
10 |
11 | ## How to use (read) the wiki?
12 |
13 | 1. Use the search function to find the topic you're looking for.
14 | 2. It's possible that a query you are looking for is not yet covered in the
15 | wiki. In that case, add the keyword `YOUR QUERY site:reddit.com/r/developersindia` to your search query on google.
16 | 3. Some of the topics may be grayed out. This means that the topic is still under construction and will be available soon. We encourage you to contribute in that case or [open a discussion on the same topic](https://github.com/developersIndia/wiki/discussions).
17 | 4. If a wiki is not helpful, **consider contributing to it**.
18 | 5. Each perspective/advice has a dedicated `Source` attached to it which is a comment on the forum. Consider visiting the source for more contextual information.
19 |
20 | ## How to contribute?
21 |
22 | The first and foremost goal of a wiki is that it helps the community, and
23 | becomes an official standing on the topic. We have a
24 | [bunch of topics](https://github.com/developersIndia/wiki/discussions/21) being
25 | requested over time. We request any author to have a look over them before
26 | creating a new proposal.
27 |
28 | We welcome community contributions! If you would like to share a word or two
29 | that you believe will help the community achieve something good, please read
30 | this section for instructions.
31 |
32 | First off, we use the [`mdbook`][1] project to maintain, create & generate the
33 | static version of our [wiki][2]. So, if you would like to get your hands dirty
34 | with this project, make sure you've read the official `mdbook`
35 | [documentations][3]. Besides the CLI tool, we also write our wiki content in
36 | [GitHub Flavoured Markdown][4]. So if you need a rundown on how to write in
37 | Markdown, the [Markdown Guide][5] will be helpful for that cause.
38 |
39 | That said, before contributing to the project make sure you've read & understood
40 | the [contributing guidelines][6] of our community. Once you have read through
41 | it, please keep the following points in mind to create a wiki entry:
42 |
43 | 1. Ensure your wiki is comprehensive enough & benefits the community in some
44 | ways.
45 | 2. Ensure your wiki entry is thoroughly reviewed for correctness & quality by
46 | one of the moderators (_you can reach out to us over Discord_).
47 | 3. Follow the [issue][7] & [pull request][8] templates to create a wiki entry
48 | for one of the moderators to review it. Expect the review process to take a
49 | while before it can be merged.
50 |
51 |
52 | ## License & Usage Terms & Conditions
53 |
54 | The community wiki is licensed under the terms & conditions (T&Cs) of the
55 | Creative Commons license. If you're interested in reading more about it, please
56 | take a look at the [LICENSE][9] document.
57 |
58 |
59 |
60 | [1]: https://github.com/rust-lang/mdbook
61 | [2]: https://wiki.developersindia.in
62 | [3]: https://rust-lang.github.io/mdBook
63 | [4]: https://github.github.com/gfm
64 | [5]: https://www.markdownguide.org
65 | [6]: https://github.com/developersIndia/wiki/blob/main/CONTRIBUTING.md
66 | [7]: https://github.com/developersIndia/wiki/issues/new/choose
67 | [8]: https://github.com/developersIndia/wiki/compare
68 | [9]: https://github.com/developersIndia/wiki/blob/main/LICENSE
69 |
70 | ## Contributors ✨
71 |
72 | Thanks go to these wonderful people
73 | ([emoji key](https://allcontributors.org/docs/en/emoji-key)):
74 |
75 |
76 |
77 |
78 |
2 |
3 | # Woah buddy, you're lost
4 | (aren't we all?)
5 |
6 | The page you're looking for isn't here. It's possible it has been moved to a different URL, use the search bar or the navigation menu in that case.
7 |
8 |
9 |
--------------------------------------------------------------------------------
/src/SUMMARY.md:
--------------------------------------------------------------------------------
1 | # Summary
2 |
3 | [Introduction](../README.md)
4 |
5 | # Frequently Asked Questions (FAQs)
6 |
7 | - [How to Start DSA](faqs/how-to-start-dsa.md)
8 | - [Approaching a DSA problem](./faqs/approaching-a-DSA-problem.md)
9 | - [Discovering small FOSS projects for contributing on github](faqs/finding-small-foss-projects-on-github.md)
10 | - [Advice for Freshers](./faqs/advice-for-freshers.md)
11 | - [Advice for Professionals](./faqs/advice-for-professionals.md)
12 | - [Switching Jobs](./faqs/switching-jobs/README.md)
13 | - [Planning for Resignation](./faqs/switching-jobs/planning-for-resignation.md)
14 | - [Negotiating Notice Periods](./faqs/switching-jobs/negotiating-notice-periods.md)
15 | - [Asking for Referrals](./faqs/switching-jobs/asking-for-referrals.md)
16 | - [Choosing your new workplace](./faqs/switching-jobs/choosing-your-new-workplace.md)
17 | - [Negotiating Salaries](./faqs/switching-jobs/negotiating-salaries.md)
18 | - [Rejecting a Job Offer](./faqs/switching-jobs/rejecting-an-offer.md)
19 | - [Sharing offer letters & past salaries with recruiters](./faqs/switching-jobs/sharing-offer-letters-and-past-salaries.md)
20 | - [Service Based to Product Based Organizations](./faqs/switching-jobs/service-based-to-product-based.md)
21 | - [Career Transitions](./faqs/career-transitions/README.md)
22 | - [From QA/SDET to Developer](./faqs/career-transitions/qa-sdet-to-dev.md)
23 | - [From Dev to DevOps](./faqs/career-transitions/dev-to-devops.md)
24 | - [To Game Dev](./faqs/career-transitions/game-dev.md)
25 | - [Preparing for tech interviews](./faqs/tech-interviews.md)
26 | - [Campus Placements](./faqs/campus-placements/README.md)
27 | - [Effect of CGPA on getting a job](./faqs/campus-placements/effect-of-cgpa-getting-job.md)
28 | - [Effect of college tier on getting a job](./faqs/campus-placements/effect-college-tier.md)
29 | - [Effect of High School grades on getting a job](./faqs/campus-placements/effect-of-high-school-grades.md)
30 | - [Effect of backlogs on getting a job](./faqs/campus-placements/effect-college-backlog.md)
31 | - [Workplace Conundrums](./faqs/workplace-conundrums/README.md)
32 | - [Dealing with micro management](./faqs/workplace-conundrums/dealing-with-micromanagement.md)
33 | - [Dealing with toxic workplaces](./faqs/workplace-conundrums/dealing-with-toxic-workplaces.md)
34 | - [Dealing with background verification (BGV)](./faqs/workplace-conundrums/dealing-with-background-verification.md)
35 | - [Dealing with colleagues who steal credit for work](./faqs/workplace-conundrums/dealing-with-colleagues-who-steal-credit.md)
36 | - [Effect of gap years on getting a job](./faqs/effect-of-gap-year-on-getting-a-job.md)
37 | - [Freelancing](./faqs/freelancing.md)
38 | - [Contract Work](./faqs/contract-work.md)
39 | - [Health]()
40 | - [Managing mental health](./faqs/health/managing-mental-health.md)
41 | - [Managing eye strain]()
42 | - [Preparing for Performance Reviews](./faqs/performance-reviews.md)
43 |
44 | # Community Guides
45 |
46 | - [How to constantly upskill yourself as a developer](community-guides/how-to-constantly-upskill-yourself-as-a-developer.md)
47 | - [How to Create an Ideal Software Engineering Resume](./community-guides/how-to-create-an-ideal-software-engineering-resume.md)
48 | - [Where to find tech jobs?](./community-guides/where-to-find-tech-jobs.md)
49 | - [Understanding Software Licenses](./community-guides/understanding-software-licenses.md)
50 | - [Getting Started in Cybersecurity](./community-guides/resources-to-get-started-in-cybersecurity.md)
51 | - [Hackathons 101: A Step-by-Step Guide to Success](./community-guides/hackathons-101-a-step-by-step-guide-to-success.md)
52 |
--------------------------------------------------------------------------------
/src/community-guides/hackathons-101-a-step-by-step-guide-to-success.md:
--------------------------------------------------------------------------------
1 |
2 | # Hackathons 101: A Step-by-Step Guide to Success
3 |
4 |
5 | ## Table of Contents
6 |
7 | - [Building the Dream Team](#building-the-dream-team)
8 | - [The Art of Problem Selection](#the-art-of-problem-selection)
9 | - [From Idea to Innovation](#from-idea-to-innovation)
10 | - [Handling Stress and Burnout](#handling-stress-and-burnout)
11 | - [Building Connections Beyond the Code](#building-connections-beyond-the-code)
12 | - [Technical Preparation](#technical-preparation)
13 | - [Useful Tools and Resources](#useful-tools-and-resources)
14 | - [Time Management](#time-management)
15 | - [Selling Your Solution](#selling-your-solution)
16 | - [Remote Hackathon Strategies](#remote-hackathon-strategies)
17 | - [Beyond the Prize](#beyond-the-prize)
18 | - [Dealing with Failure](#dealing-with-failure)
19 | - [Post-Hackathon Actions](#post-hackathon-actions)
20 | - [Case Study: From Hackathon to Startup](#case-study-from-hackathon-to-startup)
21 | - [Conclusion](#conclusion)
22 |
23 |
24 |
25 | Have you ever wondered why certain teams excel in hackathons?
26 | Is it only about code, or is there more to the story?
27 | Let's dig into the world of hackathons and learn how to construct a successful team, select the correct challenges, and create solutions that leave an impact on the judges.
28 |
29 | ## Building the Dream Team
30 | Imagine you're constructing a superhero team. Would you pick five Iron Men? Probably not. The same principle is applicable to hackathons. A varied staff is a tremendous resource. So, how do you discover the correct mix?
31 | First, strive for a combination of skills. Developers are essential, but don't forget about visionaries—designers and subject matter specialists who can give that special spark to your project. Consider your team to be a mini-startup that operates 24 hours a day. Wouldn't you want to cover all the bases?
32 | Speaking of coverage, what is the ideal team size? While there is no uniform solution, 4-5 members often reach the perfect spot. This size helps you to split work efficiently while avoiding confusion. Remember, even in a digital kitchen, too many cooks may ruin the soup!
33 |
34 | ## The Art of Problem Selection
35 | So, you've assembled your perfect squad. What happens next? It's time to choose your problem statement. But is every problem worth solving?
36 | The idea is to select the proper challenge—one that is neither too simple nor too difficult. How do you know when you've discovered it? Look for real-world applications. Will fixing this problem have an impact beyond the hackathon?
37 | Before you dive in, take a step back. What solutions already exist? Where are the gaps? This is your opportunity to create, not simply reinvent the wheel. In the hackathon world, the individual with a new, unique idea reigns supreme!
38 |
39 | ## From Idea to Innovation
40 | Now comes the enjoyable part: bringing your concept to reality. But how can you make your answer stand out amid an ocean of creativity?
41 | Begin with good research. Knowledge drives innovation in hackathons. Once you've figured out the landscape, let your imagination go wild. What twist can you apply to properly differentiate your solution?
42 | Choosing the right technological stack is analogous to picking the best tool for the job. It should be simple to use yet strong enough to wow. Pro tip: Do not waste time reinventing the wheel. Reusing code from past projects is not cheating; it is good time management!
43 | Before making your professional move, be sure you read the hackathon guidelines.
44 |
45 | ## Handling Stress and Burnout
46 | Given the intensity of hackathons, it is critical to handle stress appropriately. Take regular, brief breaks to keep focused and energized. Stay hydrated, eat well, and get some fresh air. Simple breathing techniques or brief meditation can also help keep stress levels under control. And if you get stuck, don't be afraid to ask for help—collaboration is essential in hackathons.
47 |
48 | ## Building Connections Beyond the Code
49 | Hackathons are more than simply coding marathons; they provide excellent networking opportunities. Here's how to make use of them:
50 | - During breaks, introduce yourself to members of the other teams.
51 | - Participate in social activities or seminars planned during the hackathon.
52 | - Connect with sponsors and judges; they might be potential employers or mentors.
53 | - After the event, follow up with your connections via LinkedIn or other professional sites.
54 | - Ethical Considerations in Hackathons
55 | Consider ethics when developing your answer. If your project includes data, make sure it is acquired ethically, used appropriately, and properly cited. Consider the potential negative effects of your approach and devise measures to reduce them. Strive for inclusive solutions that do not exclude or discriminate against any group. Be open about your solution's capabilities and limits.
56 |
57 | ## Technical Preparation
58 | Before the hackathon starts, make sure your development environment is ready to go. Prepare any code samples or templates you may require. Improve skills like API integration and data visualization. Consider assembling a "hackathon toolkit" from your favorite libraries and tools.
59 |
60 | ## Useful Tools and Resources
61 | The correct tools and resources may mean all the difference. Version control services like **[GitHub](https://github.com/)** and **[GitLab](https://about.gitlab.com/)** are essential tools for collaboration. Tools like **[Slack](https://slack.com/intl/en-in/)** or **[Discord](https://discord.com/)** may help your team communicate, especially during virtual hackathons. When it comes to design, prototyping tools like **[Figma](https://www.figma.com/)** and **[Sketch](https://www.sketch.com/)** may help you visualize your concepts. Backend development technologies like **[Firebase](https://firebase.google.com/)** and **[AWS Amplify](https://aws.amazon.com/amplify/)** can help speed up the process. Don't forget to include AI or machine learning frameworks like **[TensorFlow](https://www.tensorflow.org/)** or **[PyTorch](https://pytorch.org/)**, which can provide your project with a competitive advantage.
62 |
63 | ## Time Management
64 | Effective time management is essential at a hackathon. To make the best use of your limited time, create a basic schedule. Spend the first 2-3 hours **thinking and planning**, studying relevant material, and locating current solutions. Dedicate the next 12–14 hours to** core development**, with a focus on creating the features listed in your issue description. Reserve the last 2-3 hours of this time for integration. After that, devote 4-6 hours to **testing and tweaking** your product to guarantee it is polished and ready for the judges. Finally, in the final 2-3 hours, **prepare your presentation**, compose a fascinating speech, and harness your inner Steve Jobs to make a lasting impact. Remember to take pauses, eat properly, and keep hydrated—free food and beverages are great advantages during hackathons!
65 |
66 | ## Selling Your Solution
67 | You've created something fantastic. Now, how can you ensure that everyone else perceives it this way?
68 | Consider your presentation as a tale. What is the problem? Why should anybody care? How does your solution help rescue the day? Remember that judges are human, too. They prefer intriguing storytelling over dull facts.
69 | Here's an unexpected tip: concentrate more on the problem than the solution. Why? Because a well-defined problem is already halfway resolved. It demonstrates that you have done your study and fully grasp the task at hand.
70 |
71 | ## Remote Hackathon Strategies
72 | As more events go online, participating in remote hackathons necessitates a few adaptations. Make sure you have a reliable internet connection. Create a pleasant, distraction-free workstation. Maintain team connection using video calls. Use online collaboration tools like **Miro** or **Trello** to brainstorm and organize tasks. Regular check-ins with your team can help keep everyone on target.
73 |
74 | ## Beyond the Prize
75 | Let's be honest: you may not win your first hackathon. Or your second. Or even a third. But does this imply you've failed? Definitely not!
76 | Every hackathon is a learning opportunity. Participating in hackathons helps you improve your abilities, broaden your network, and push your limits. The actual prize is not only the trophy but also the development and improvement you make along the way.
77 |
78 | ## Dealing with Failure
79 | Even if you don't win, you can still benefit greatly. Start by soliciting comments from judges and peers. Reflect on what went well and where you can improve. Consider working on your project after the hackathon; many great businesses started this way. Keep in contact with your team about potential partnerships. Remember that not winning doesn't imply your concept isn't viable; it might be the basis for something enormous.
80 |
81 | ## Post-Hackathon Actions
82 | Completing the hackathon signals the beginning of a new phase. Refine your project based on comments. Consider open-sourcing your code to solicit more feedback from the community. If your solution has potential, consider developing it into a company or product. Writing a blog post about your experience might help you reinforce your knowledge and share your findings with others. And, of course, start organizing your next hackathon—there's always another chance to create and advance.
83 |
84 | ## Case Study: From Hackathon to Startup
85 | Consider the tale of GroupMe, a group messaging service that began as a hackathon project at the TechCrunch Disrupt Hackathon in 2010. Jared Hecht and Steve Martocci, the creators, created the prototype in 24 hours. They did not win the hackathon, but they saw the potential in their proposal. They continued to build the software and gathered funds, and within a year, GroupMe was bought by Skype for more than $40 million. This example demonstrates how, with perseverance and hard work, a hackathon project may become a profitable enterprise.
86 |
87 | ## Conclusion
88 | In the realm of hackathons, the journey is equally crucial as the outcome. You might not win your first hackathon—or even get accepted into the first ones you apply to. But keep going, be resilient, and embrace every chance. Every line of code, brainstorming session, and presentation contributes to your development as a developer, creator, and individual.
89 |
90 | So, are you ready to solve difficulties creatively and pave the route for success? The next hackathon might be your opportunity to demonstrate your abilities and create an impression. Will you seize it?
91 |
92 |
93 | ---
94 | Compiling all the data into a single page is not easy. If you feel I missed out on some advice and/or you could add additional insights, please feel free to make a pull request or ping me!
95 | Additionally, you can find more personal contact details about me on my [personal website](https://www.sujal.xyz/) if you want to reach to me privately for guidance.
96 |
--------------------------------------------------------------------------------
/src/community-guides/how-to-constantly-upskill-yourself-as-a-developer.md:
--------------------------------------------------------------------------------
1 |
2 | # How to constantly upskill yourself as a developer
3 |
4 | - [Hangout in Forums \& Communities](#hangout-in-forums--communities)
5 | - [Write Code \& Create Software Projects](#write-code--create-software-projects)
6 | - [Write about what you learn](#write-about-what-you-learn)
7 | - [Where to find interesting stuff?](#where-to-find-interesting-stuff)
8 | - [Read Newsletters](#read-newsletters)
9 | - [Listen to Podcasts](#listen-to-podcasts)
10 | - [Attend/Watch Conferences](#attendwatch-conferences)
11 |
12 | ## Hangout in Forums & Communities
13 |
14 | - Choose a community with which you can resonate. By community, we mean a collection of self-motivated developers/engineers/programmers. You are already in the right place 😉.
15 | - Read and watch what people are asking and discussing.
16 | - A good example is reading questions on [stackoverflow](http://stackoverflow.com) or [Software Engineering - StackExchange](https://softwareengineering.stackexchange.com/?tab=month).
17 | - Join programming-related subreddits (Reddit is the best place for software folks after Stack Overflow). If you like JavaScript, [find subreddits related to JavaScript](https://anvaka.github.io/sayit/?query=javascript) and join them.
18 |
19 | ## Write Code & Create Software Projects
20 |
21 | - This has been asked and repeated thousands of times by everyone on the internet: Just build stuff!
22 | - Learn how to contribute to FOSS if you don't have your own ideas to build.
23 | - Constantly learning new stuff is useless if you can't apply those new techniques.
24 |
25 | ## Write about what you learn
26 |
27 | - No matter how small things are, if they are forgettable (and most things in software are), then log them somewhere.
28 | - Build a notes site just for yourself; it doesn't need to be fancy. Open a text file, write about what you learned, and store it in a git repo or in Google Docs.
29 | - Optionally, you can choose to share your knowledge with the rest of the world via blogs.
30 |
31 | ## Where to find interesting stuff?
32 |
33 | ### Read Newsletters
34 |
35 | - Find newsletters on [zudochkin/awesome-newsletters](https://github.com/zudochkin/awesome-newsletters)
36 |
37 | ### Listen to Podcasts
38 |
39 | - Find podcasts on [rShetty/awesome-podcasts](https://github.com/rShetty/awesome-podcasts)
40 |
41 | ### Attend/Watch Conferences
42 |
43 | - Conferences tend to offer a lot of quality information from folks around the world.
44 | - If you can't travel, then watch them online. Most conferences have their YouTube channels.
45 | - Here are some places you can look for conferences and some amazing talks:
46 | 1. [dev.events](https://dev.events/)
47 | 2. [programming talks](https://www.programmingtalks.org/)
48 | 3. [confs.tech](https://confs.tech/#)
49 | 4. [papercall.io](https://www.papercall.io/events/)
50 | 5. [DevTube](https://dev.tube/)
51 | 6. [developers.events](https://developers.events)
52 |
53 |
54 |
55 |
56 | This wiki is maintained by [u/BhupeshV](https://www.reddit.com/user/BhupeshV)
57 |
--------------------------------------------------------------------------------
/src/community-guides/how-to-create-an-ideal-software-engineering-resume.md:
--------------------------------------------------------------------------------
1 | # How to Create an Appealing Software Engineering Resume
2 |
3 | Job search (especially in the competitive Software Engineering field) is a
4 | time-consuming and often stressful task. Hence it is important to optimise and
5 | streamline each step of this task as much as possible to better the chances of
6 | landing a good job offer.
7 |
8 | Part of the job search procedure is to draft an appealing resume according to
9 | certain standard protocols and format. This guideline therefore attempts to
10 | share with your some of those protocols (along with a few tips and tricks) to
11 | draft a resume to improve your chances of landing your ideal job offer.
12 |
13 | ## Understanding the Hiring Pipeline
14 |
15 | Over the years as I reviewed and screened a lot of resumes, one thing is always
16 | apparent - the applicant lacks insight of the hiring process. Hence I would like
17 | to start this guideline by attempting to educate you about it first.
18 |
19 | The hiring process is usually divided into multiple stages. Now the exact
20 | pipeline is never the same and it varies depending on the size and financial
21 | capabilities of the organisation but the core concept is pretty much very
22 | similar.
23 |
24 | The first stage of the hiring pipeline is when a _Hiring Manager_ (who is
25 | usually a senior technical member of the organisation/team) requires additional
26 | resources and prompts the HR team about the same. The HR team is provided a list
27 | of requirements the candidate is supposed to have to fulfill the Hiring
28 | Manager's needs. The HR then proceeds to put up a job advert on various
29 | platforms like LinkedIn or some other platform. As soon as you apply to a job
30 | advert through the said portal, your application (and your resume) is stored in
31 | an _Application Tracking System (ATS)_ for further screening.
32 |
33 | Now a common misunderstanding is about drafting resumes are that "_it should
34 | ATS-friendly_". I do not understand where this common misconception arose but
35 | you should be aware that the ATS is just a software to store and track
36 | applicants to a job position. Most commonly used ATSes do not have intelligent
37 | OCR capabilities to parse through your resume (if its in a PDF format). The
38 | organisations which can afford to utilise ATSes with more feature-rich and OCR
39 | capabilities are rare and not very common. To give you a heads up, the inbuilt
40 | LinkedIn ATS does not provide any such feature and you need not worry whether
41 | your resume will "_pass the ATS test_".
42 |
43 | With your application (and resume) tracked on the ATS, it is the HR's call to
44 | screen through the thousands and thousands of resume they receive each day! A
45 | vast majority of the resumes are often spam and unrelated to the job advert.
46 | Hence HRs are incentivised to scan a bunch of resumes/applications for not more
47 | than a few seconds "_looking for certain keywords_". The said keywords are
48 | chosen based on the requirements list provided to them by the Hiring Manager.
49 | All resumes which pass this initial HR screening are forwarded to the Hiring
50 | Manager for further review. The Hiring Manager approves a select few of those
51 | screened resumes for an interview call (or sometimes even a quick phone
52 | interview as is the case in smaller seed startups).
53 |
54 |
55 |
56 | The key takeaway here is, your resume should be optimised to showcase the best
57 | version of you at a quick glance! Keep it in mind, the HR screening your resume
58 | will not be spending more than 3-5 seconds of a glance reading through the
59 | resume. You can discuss more details of yourself during the phone call or
60 | face-to-face interview with the Hiring Manager!
61 |
62 | ## Using the Right Structure/Format for the Resume
63 |
64 | To ensure the resume is optimised for the HR screening stage, it is important to
65 | use a correct format for the resume. This section of the guide will walk you
66 | through the steps to draft a resume with a correct structure. Now do note, the
67 | structure shared here is applicable to the industries of most parts of Asia,
68 | Western Europe and the US. If you are looking to apply elsewhere you will
69 | probably have to perform your due research on what the accepted structure of the
70 | resume for that particular industry is.
71 |
72 | That said, the structure of the resume you should be working with is as follows:
73 |
74 | 1. Always start the resume with your name (in bold and prominent font size),
75 | contact information like email, GitHub profile, current location and your a
76 | phone number to reach out to you.
77 |
78 | 2. Divide the entire resume into multiple sections and each should be structured
79 | exactly like this:
80 |
81 | - Technical Skills, where you list all the skills you want to showcase.
82 | - Work Experience, where you share detailed description of your previous work
83 | experience.
84 | - (Optional) Projects, achievements, certifications and such where you want
85 | to showcase extra-curricular activities relevant to the job advert.
86 | - Education, where you share information about your academics.
87 |
88 | 3. Ensure your resume is read top-down like a normal book or a professional
89 | document. Resist the temptation to draft a resume in a column style, such
90 | resumes are often outright rejected!
91 |
92 | 4. Ensure chronological order of pretty much any/all relevant sections like your
93 | latest work experience should be on top of the previous ones. Or your latest
94 | education should be before the older previous one.
95 |
96 | 5. Resist the urge to prettify the resume with unnecessary details. Remember it
97 | is a professional document and you will not want to read such documents
98 | written by an amateur.
99 |
100 | ## Some Tips & Tricks to Write Professionally
101 |
102 | As discussed in the previous section, drafting the resume professionally is very
103 | important. This section will share some tips and tricks to create one such
104 | professionally drafted resume.
105 |
106 | #### Tip 1: Use the Right Font Family & Size
107 |
108 | Please for the love of God, stick with either of this font families - Times New
109 | Roman, Arial or any Serif-type font. Anything else and especially if it is not a
110 | [serif-type font](https://www.myfonts.com/pages/serif-fonts) is extremely
111 | unappealing to read!
112 |
113 | A good font size of the general description section of the document is 10-11
114 | points. Exception applies to the heading sections and the top of the document
115 | where you share your personal contact details and name.
116 |
117 | #### Tip 2: Refrain from Adding Unnecessary Fluff
118 |
119 | Professional documents do not require to look fancy with loads of colours and an
120 | oomph. Keep it simple and stupid (KISS) like the engineer in me would like it
121 | as!
122 |
123 | The most beautification you should worry about is:
124 |
125 | 1. Making sections of your resume bold and if you want to direct extra attention
126 | to it.
127 | 2. Using italics style on lesser prominent sections of the document.
128 | 3. Adding an underline and a blue font colour to hyperlinks to clearly
129 | distinguish them from the rest of the document as something of a
130 | point-of-interest.
131 |
132 | #### Tip 3: Use Your Best Judgement to Add Projects/Achievements
133 |
134 | Now adding a projects/achievements section to the resume can be quite
135 | subjective. While you might be super proud and confident about a certain project
136 | or achievement, others might not feel the same way about it!
137 |
138 | I personally recommend adding such a section to the document only and only if
139 | you feel confident you have a chance at discussing some interesting points about
140 | it during the interview process. If you do not have something to boast about
141 | during the interview, the space might be better utilised to describe more about
142 | your work experience instead.
143 |
144 | #### Tip 4: Update the Resume Very Often
145 |
146 | Most people I know only remember about updating the resume during their job
147 | search phase which I strongly advice against. Instead I usually recommend
148 | maintaining a [Bragdoc](https://www.bragdocs.com) which is updated every other
149 | day (should not take you more than a minute or two post work hours). And then
150 | every three or so months should you pick your personal best achievement from the
151 | Bragdoc and add it to your resume.
152 |
153 | This way not only are you **ALWAYS** ready with a resume but you will also never
154 | forget about an achievement you made at your workplace which could have made
155 | your resume look quite appealing.
156 |
157 | #### Tip 5: Perform a Customary Grammar Check
158 |
159 | It is a major turn off and a red flag to find a resume with **loads** of
160 | grammatical errors (keyword being loads). A professional document with
161 | grammatical errors make it looks amateurish and the candidate as someone to be
162 | slacking.
163 |
164 | Take my word on it and do not make yourself a target to be joked on and just use
165 | tools like [Grammarly](https://www.grammarly.com) &
166 | [Hemingway Editor](https://hemingwayapp.com) or some LLM-based chat bots like
167 | [ChatGPT](https://www.chat.openai.com) or [Claude](https://claude.ai) to review
168 | your resume for grammatical mistakes.
169 |
170 | ## Additional Recommended Reference Materials
171 |
172 | While the suggestions I have shared above will help you a long way ahead in
173 | securing your next job offer by enabling you write a very professional document,
174 | I want to share some additional resources which will provide additional marginal
175 | benefits.
176 |
177 | 1. Use this resume template I created in Google Docs -
178 | [Anonymous Resume](https://docs.google.com/document/d/12jBHnaiQXpIVH91lHf3OvNA5hPdFpmi5PBK5wUE5C_0/edit?usp=sharing).
179 |
180 | 2. Get your resume reviewed from your peers. A second opinion will always polish
181 | out the remaining intricate mistakes here and there which you might've
182 | missed. Join [our Discord community](https://discord.gg/kRMQSZGzkt) & ping me
183 | whenever you want to for a resume review (my Discord ID - `Jarmos#8937`).
184 |
185 | 3. **ALWAYS** remember, job hunting is a numbers game! Don't lose patience and
186 | keep applying to jobs on all platforms you can think of. And don't hesitate
187 | to reach out to prospects & network with people. Be mindful though, asking
188 | for a job straight away might appear rude to some. See this article -
189 | [How to Break Into the Tech Industry—a Guide to Job Hunting and Tech Interviews](https://haseebq.com/how-to-break-into-tech-job-hunting-and-interviews)
190 | to find some insights & lessons.
191 | 4. The
192 | [r/EngineeringResumes Wiki](https://www.reddit.com/r/EngineeringResumes/wiki/index/)
193 | .
194 |
195 | If you feel I missed out on some advice and/or you could add additional
196 | insights, please feel free to make a pull request or ping me on Discord!
197 | Additionally, you can find more personal contact details about me on
198 | [my personal website](https://jarmos.dev) if you want to reach to me privately.
199 |
--------------------------------------------------------------------------------
/src/community-guides/resources-to-get-started-in-cybersecurity.md:
--------------------------------------------------------------------------------
1 |
2 | # Resources To Get Started in Cybersecurity
3 |
4 | - [What is cybersecurity?](#what-is-cybersecurity)
5 | - [Basics](#basics)
6 | - [Learn about vulnerabilities and tools](#learn-about-vulnerabilities-and-tools)
7 | - [Practice](#practice)
8 | - [Test your skills in the real world](#test-your-skills-in-the-real-world)
9 | - [References](#references)
10 | - [Perspective \& advice from the community](#perspective--advice-from-the-community)
11 |
12 |
13 | ## What is cybersecurity?
14 |
15 | Cybersecurity is the protection of computer systems or networks from malicious actors that may result in the theft of data or disruption to any services these systems provide. It has many fields such as web hacking, mobile hacking, reverse engineering, etc. To get started, you have to pick the field which interests you. It can be web hacking if you like to tinker around with web applications to see how they behave or maybe reverse engineering if you like to see how the applications work.
16 |
17 | ## Basics
18 |
19 | To get started with cybersecurity, it is recommended to have a basic understanding of computer networking, operating system fundamentals, as you have to know how it communicates to hack something. Check out the following resources to get a head start:
20 |
21 | - [Network Fundamentals](https://www.youtube.com/watch?v=9uebakqWlB0)
22 | - [TCP IP Model](https://www.youtube.com/watch?v=e5DEVa9eSN0)
23 | - [How SSL Works](https://howhttps.works/)
24 | - [Basics of HTTP](https://developer.mozilla.org/en-US/docs/Web/HTTP/Overview)
25 | - If you want a university-like course with a deeper understanding of basics, you can follow [PWN College](https://pwn.college/intro-to-cybersecurity/)
26 |
27 | ## Learn about vulnerabilities and tools
28 |
29 | After understanding the basics, it is time to learn some hacking skills.
30 |
31 | [OWASP Top 10 for Web](https://owasp.org/Top10/)
32 |
33 | The very first step is to understand what vulnerabilities to look for in a system. OWASP Top 10 is a standard awareness document for developers and web application security. It represents a broad consensus about the most critical security risks to web applications.
34 |
35 | [Web Testing Guide](https://owasp.org/www-project-web-security-testing-guide/latest/)
36 |
37 | After learning about the OWASP TOP 10 vulnerabilities in web applications, you can use these comprehensive guides to learn step by step how to look for these vulnerabilities, along with the impact they have when exploited and how to remediate or fix those vulnerabilities.
38 |
39 | [Burp Suite](https://portswigger.net/burp/communitydownload)
40 |
41 | Burp Suite is a software security application used for penetration testing of web applications. It is an HTTP proxy tool that is used to intercept and manipulate the HTTP traffic of the application you are testing. To practice looking for vulnerabilities, it is necessary to learn how to use this tool to intercept and edit the HTTP request. It has both paid and free versions, but you can use the community edition, which is more than enough.
42 |
43 | - [How to use Burp Suite](https://www.youtube.com/watch?v=LSqC9qgEMi0&list=PLxhvVyxYRviajtnHaICLg_ZcY47TpgGjR)
44 | - [To practice Burp Suite lab](https://tryhackme.com/room/burpsuitebasics)
45 |
46 | ## Practice
47 |
48 | After you have some knowledge about the vulnerabilities in theory, it is time to practice them.
49 |
50 | - [Portswigger Web Security Academy](https://portswigger.net/web-security/getting-started) is a free online academy to learn about web security from the creators of Burp Suite. They have detailed information about different vulnerability topics along with real-world scenarios. Highly recommended for anyone who wants to learn the basics of how to look for web vulnerabilities.
51 | - [Tryhackme](https://tryhackme.com/) is an online platform for learning cybersecurity, using hands-on exercises and labs, all through your browser. It has both paid and free rooms that cover all topics about security through a series of CTF.
52 | - [Kontra](https://application.security/free/owasp-top-10) is a free platform to learn about application security through their series of interactive exercises on vulnerabilities in real-world scenarios.
53 | - [OWASP Juice Shop](https://github.com/juice-shop/juice-shop) is a modern insecure application that has vulnerabilities from OWASP Top 10 and other security issues found in real-world applications.
54 |
55 | ## Test your skills in the real world
56 |
57 | Now, after gaining knowledge about vulnerabilities and practicing how to find them, it is time to use your skills in the real world. You can try to test for vulnerabilities in Bug Bounty programs.
58 |
59 | Bug bounty programs offer monetary rewards to ethical hackers for successfully discovering and reporting a vulnerability or bug to the application's developer.
60 |
61 | 1. [HackerOne](https://hackerone.com/bug-bounty-programs)
62 | 2. [Bugcrowd](https://bugcrowd.com/engagements?category=bug_bounty&page=1&sort_by=promoted&sort_direction=desc)
63 | 3. [Intigriti](https://www.intigriti.com/programs)
64 | 4. [Bugbase](https://bugbase.in/programs): Bugbase is an India-based bug bounty platform that hosts bug bounty programs for various Indian companies.
65 |
66 | You can use these platforms to hunt on various programs, or you can search for independent vulnerability disclosure programs that are self-hosted by various companies by searching for 'Company Name' vulnerability disclosure program or 'Company Name' bug bounty program on Google.
67 |
68 |
69 | ## References
70 |
71 | - [OWASP](https://owasp.org/www-project-top-ten/)
72 | - [Portswigger](https://portswigger.net/web-security/)
73 | - [How to be a hacker](https://github.com/s0md3v/be-a-hacker)
74 |
75 | ## Perspective & advice from the community
76 |
77 | - [Career path for cybersecurity in India?](https://www.reddit.com/r/developersIndia/comments/ydxj5j/career_path_for_cybersecurity_in_india/).
78 | - [Cybersecurity vs Developer salary and career growth.](https://www.reddit.com/r/developersIndia/comments/12w45c1/cybersecurity_vs_developer_salary_and_career/).
79 | - [Is cyber security worth it?](https://www.reddit.com/r/developersIndia/comments/1930411/is_cyber_security_worth_it/).
80 | - [How is the CyberSecurity job market for freshers in India?](https://www.reddit.com/r/developersIndia/comments/1dsmrwo/how_is_the_cybersecurity_job_market_for_freshers/).
81 | - [How do i get into Cyber Security / A Cyber Security Job?](https://www.reddit.com/r/developersIndia/comments/ynmf8h/how_do_i_get_into_cyber_security_a_cyber_security/).
82 | - [**I’m Subho Halder, Co-founder & CEO of Appknox — AMA**](https://www.reddit.com/r/developersIndia/comments/1g75a7o/im_subho_halder_cofounder_ceo_of_appknox_ama/).
83 |
84 |
85 | ## Acknowledgements
86 |
87 | This wiki was initially written by [u/Sanamdhar](https://www.reddit.com/user/Sanamdhar/).
88 |
--------------------------------------------------------------------------------
/src/community-guides/understanding-software-licenses.md:
--------------------------------------------------------------------------------
1 | # Understanding Software Licenses
2 |
3 | ## What is a software license?
4 | A software license is a legal instrument that gives you the right to install, use or otherwise interact with a specific computer program under given circumstances.
5 |
6 | In simple terms, a software license defines a set of responsibilities for those who use the code and those who produce the code.
7 |
8 | A software license is a requirement when releasing code to the public, as without one, the code is copyrighted to the developer by default.
9 |
10 |
11 | ## Why are software licenses important?
12 | Here are the reasons why software licenses are indispensable:
13 |
14 | - They define the usage rights (T&C) and prevent unauthorized usage of the software.
15 |
16 | - Software licenses are essential for establishing legal boundaries and preventing legal troubles such as fines and lawsuits.
17 |
18 | - Licenses are crucial for defining distribution permissions and limitations.
19 |
20 | - They allow developers to control how their software is used to prevent misuse and unapproved modifications.
21 |
22 | - Open-source licenses facilitate collaboration by providing a legal framework for a transparent development environment.
23 |
24 |
25 | ## What are the types of Software Licenses?
26 | There are mainly 4 main categories of Software Licenses based on the rights and restrictions they impose.
27 |
28 | ### 1. Public Domain
29 | Public Domain software refers to software deliberately placed in the public domain, no longer protected by copyright, trademark or patent laws. As a result, it can be freely used without the permission of or payment to the developer.
30 |
31 | Direct licensing for the public domain is not universally recognized. Here are two tools that you could use as alternatives.
32 |
33 | - **[Creative Commons Zero (CC0)](https://creativecommons.org/public-domain/cc0/):** CC0, provided by Creative Commons, is used for waving copyright interest in a work you've created and serves as a fallback as a public domain equivalent license.
34 | - **[The Unlicense](https://unlicense.org/):** The Unlicense is similar to CC0 but offers a simpler, more direct statement of public domain dedication.
35 |
36 | ### 2. Permissive
37 | Permissive licenses, often referred to as “BSD-style licenses”, contain minimal restrictions on how the software can be modified or redistributed.
38 |
39 | [The Open Source Initiative](https://opensource.org/) defines a permissive software license as a “non-copyleft license that guarantees the freedom to use, modify and redistribute”.
40 |
41 | Some commonly used permissive licenses are:
42 |
43 | - **[MIT License](https://opensource.org/license/mit/):** The MIT License is one of the most permissive licenses that allow you to use, copy, modify, distribute, sublicense and sell copies of the software as long as you add a copy of the original MIT License and copyright to it.
44 | - **[Apache License 2.0](https://opensource.org/license/apache-2-0/):** Apache License is similar to MIT License but it explicitly addresses patents by providing the recipient with a license to any patents held by the contributor related to the project.
45 | - **[BSD-2-Clause](https://opensource.org/license/bsd-2-clause/):** Much like the MIT License, the 2-Clause BSD License also allows you to use, modify, distribute and sublicense the software. However, it includes an additional requirement for attribution in advertising materials.
46 |
47 | ### 3. Copyleft
48 | Copyleft licenses are more restrictive and less commercial-friendly.
49 | These require that anyone who modifies or distributes the software share their changes under the same or a compatible license.
50 |
51 | Some commonly used copyleft licenses are:
52 |
53 | - **[GNU General Public License (GPL) 2.0](https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html):** To utilise GPLv2 rights (copying, distribution & modifying), you must track changes and dates in the source file and share any changes under GPL terms.
54 | - **[GNU General Public License (GPL) 3.0](https://www.gnu.org/licenses/gpl-3.0.en.html):** GPLv3 follows GPLv2 but also includes provisions for patents, allows adding extra permissions, improved internationalization and termination processes, etc.
55 | - **[GNU Affero General Public License (AGPL) 3.0](https://www.gnu.org/licenses/agpl-3.0.en.html):** AGPLv3 and GPLv3 share core principles of copyleft, but AGPLv3 includes additional provisions to address the distribution of modified software over a network.
56 |
57 | ### 4. Proprietary
58 | Also called closed-sourced, this license is used by developers or vendors to claim ownership of their work and software. Proprietary licenses restrict the user’s right to modify, distribute or access the underlying source code of the software.
59 | An example of a proprietary license is:
60 |
61 | - **[MS Reference Source License](https://referencesource.microsoft.com/license.html):** The MS-RSL is a proprietary license that allows you to review the code and make copies of it, but you can’t use the code or change it in any way.
62 |
63 |
64 | ## Comparison of Software Licenses
65 | Here’s a table summarizing the software licenses we talked about earlier, including their types, key features and examples of projects corresponding to each license.
66 |
67 | | License | Type | Key Features | Example Projects |
68 | |--------------------------|---------------------|------------------------------------------------------------|----------------------------------|
69 | | **GNU General Public License (GPL)** | Copyleft | Requires derivative works to be distributed under the GPL. | Linux, Git, GNU tools |
70 | | **MIT License** | Permissive | Allows almost unrestricted use, modification, and distribution. | Node.js, jQuery, Rails |
71 | | **Apache License** | Permissive | Allows usage of the software for any purpose, with limited conditions. | Apache HTTP Server, Hadoop |
72 | | **BSD Licenses** | Permissive | Simple and permissive, allows use in proprietary projects. | FreeBSD, NetBSD, Nginx |
73 | | **Creative Commons** | Various | Used for creative works, it provides different levels of sharing and usage permissions. | Wikimedia Commons, Flickr |
74 | | **Mozilla Public License (MPL)** | Copyleft | Requires modifications to be open-sourced under the MPL. | Mozilla Firefox, Thunderbird |
75 | | **Eclipse Public License (EPL)** | Weak Copyleft | Similar to the MPL, but contains specific patent grant provisions. | Eclipse IDE, Jetty |
76 | | **ISC License** | Permissive | Short and simple permissive license. | OpenBSD, PostCSS |
77 | | **GNU Lesser General Public License (LGPL)** | Weak Copyleft | Allows linking with non-GPL software. | GTK+, GStreamer |
78 | | **Unlicense** | Public Domain | Places the work in the public domain with no restrictions. | Bitcoin.php, CPython (prior to v3.5) |
79 |
80 |
81 | ## Which software license should I use?
82 |
83 | When choosing an open-source license for your project, it’s crucial to ensure that your selection aligns with your ideological values and objectives. Additionally, consider the level of control you wish to maintain over your project, ensuring compatibility and compliance with the licenses of any software incorporated into it.
84 |
85 | If you prefer a copyleft approach, where derivative work must also be open source, the GNU General Public License (GPL) is a strong candidate. This license ensures that modifications and improvements to your project also contribute to the open-source community.
86 |
87 | If you prioritize making your software widely accessible with minimal restrictions, the MIT License is a popular choice. It allows for almost unrestricted use, modification and distribution.
88 |
89 | There are also open-source software licenses for non-software works ranging from documentation to fonts.
90 |
91 | Ultimately, the right license depends on your specific project requirements and how you envision collaboration within the open-source community. Take time to understand the terms and conditions of each license to make an informed decision that best suits your objectives.
92 |
93 |
94 | ## Resources
95 | Not sure which license to pick? Here are a few tools to help you out.
96 |
97 | - [Choosealicense.com](https://choosealicense.com/) by Github offers comprehensive information on licensing options beyond those discussed here.
98 | - [Public License Selector](https://ufal.github.io/public-license-selector/) by ÚFAL is a tool that can help you choose the right open-source license for data and software.
99 | - Also, check out [OSI's extensive FAQs](https://opensource.org/faq/) which may offer solutions to your queries.
100 | ---
101 |
102 | This wiki is maintained by [u/govind_s_nair](https://www.reddit.com/user/govind_s_nair).
103 |
--------------------------------------------------------------------------------
/src/community-guides/where-to-find-tech-jobs.md:
--------------------------------------------------------------------------------
1 |
2 | # Where to find tech jobs?
3 |
4 |
5 |
6 | > **Checkout r/developerIndia's official [Job Board](https://developersindia.in/job-board/) for job listings**.
7 |
8 |
9 |
10 | - [Traditional Mediums](#traditional-mediums)
11 | - [Remote job boards](#remote-job-boards)
12 | - [Job Boards for jobs on Hackernews](#job-boards-for-jobs-on-hackernews)
13 | - [Newsletter based job Boards](#newsletter-based-job-boards)
14 | - [Miscellaneous job boards](#miscellaneous-job-boards)
15 |
16 | ## Traditional Mediums
17 |
18 | 1. [LinkedIn](https://www.linkedin.com/jobs/)
19 | 2. [InstaHyre](https://www.instahyre.com/)
20 | 3. [Wellfound (formerly AngelList Talent)](https://wellfound.com/)
21 | 4. [CutShort](https://cutshort.io/)
22 | 5. [Hirect](https://www.hirect.in/)
23 |
24 | Not to mention job portals like Shine and Indeed.
25 |
26 | ## Remote job boards
27 |
28 | 1. [We Work Remotely](https://weworkremotely.com/)
29 | 2. [Entry Level Remote Job](https://entrylevelremotejob.com/)
30 | 3. [Remote OK](https://remoteok.com/)
31 | 4. [Remotive.io](https://remotive.io/)
32 | 5. [Remotists](https://remotists.com/)
33 | 6. [remote-developer-jobs.com](https://www.remote-developer-jobs.com/)
34 | 7. [Findwork.dev](https://findwork.dev)
35 | 8. [EchoJobs](https://echojobs.io/search?q=&locations=Remote%2BIndia&page=1)
36 |
37 | ## Job Boards for jobs on Hackernews
38 |
39 | 1. [kennytilton.github.io](https://kennytilton.github.io/whoishiring/)
40 | 2. [hnjobs.emilburzo.com](https://hnjobs.emilburzo.com)
41 |
42 | ## Newsletter based job Boards
43 |
44 | - [NoCommute - Remote jobs delivered to your inbox](https://www.nocommutejob.com/).
45 | - [Remote Leaf](https://remoteleaf.com/)
46 |
47 | ## Miscellaneous job boards
48 |
49 | - [No CS Degree - Job Board for Self-taught Developers](https://www.nocsdegree.com/jobs/)
50 | - [Hasgeek Job Board](https://hasjob.co/?c=programming).
51 |
--------------------------------------------------------------------------------
/src/faqs/advice-for-professionals.md:
--------------------------------------------------------------------------------
1 |
2 | # Advice for Professionals
3 |
4 | - [Perspectives \& advice from the community](#perspectives--advice-from-the-community)
5 | - [Related Discussions](#related-discussions)
6 |
7 | ## Perspectives & advice from the community
8 |
9 | `u/impossible__dude` on a post titled
10 | [What is the future of people in the tech sector?](https://www.reddit.com/r/developersIndia/comments/18ma6fw/what_is_the_future_of_people_in_the_tech_sector/)
11 | shared the following advice:
12 |
13 |
14 |
15 | I am 45, working as a CXO in a mid sized firm (1000+ staff).
16 |
17 | Here are a few things that worked for me:
18 |
19 | Planning about the future makes no sense, we dunno if we will be alive next
20 | week. Why think of 30 years ahead and bug yourself.
21 |
22 | Have money goals. Say how much do you think you need to run a family? If your
23 | household expenses are 1 lac pm, then a good first target is 2.4cr (annual
24 | expenses x 20). Work on it
25 |
26 | Acquire skills. Whatever be your area acquire skills that speak for you. Build
27 | something useful for others, have a strong github presence. Contribute to open
28 | source, that's a very strong skill there
29 |
30 | Don't look around and see who is doing what and compare. Then you are trying to
31 | be another rat in the rat race, and except for stress never gives anything back
32 | this approach
33 |
34 | Strongly refrain from using social media. If you must, use it for brand building
35 | but please use it judiciously. Much of social media is fake, toxic and always
36 | ready to weave a conflicting narrative. Very bad for the brain. If you want a
37 | long career you need to be healthy and relaxed above anything
38 |
39 | ---
40 |
41 | [`Source`](https://www.reddit.com/r/developersIndia/comments/18ma6fw/comment/ke4fl3a/)
42 |
43 |
44 |
45 | `u/Longjumping-Egg-3925` on a post titled [Professionals with 15+ years experience](https://www.reddit.com/r/developersIndia/comments/190l8ap/professionals_with_15_years_experience/), shared the following perspective:
46 |
47 |
48 |
49 | Closing 20 years in 2025.
50 |
51 | Service Desk Engineer - Sys Admin - Windows Admin - Design Engineer - Cloud Engineer - Cloud Architect - Cloud Tech Sales/Pre-Sales - Cloud Programme Leadership (Tech & Non Tech).
52 |
53 | Career spans two countries India/New Zealand.
54 |
55 | Learnt that you can learn anything given enough effort and time is out against it. Also learnt that grass is always greener on the other side.
56 |
57 | Learnt WLB is important - and work cannot come at the cost of health/wealth.
58 |
59 | If I was to tell my younger self something - passive income pursuits and also investing early.
60 |
61 | Also learnt that if you invest in yourself - you can reap bigger than life benefits.
62 |
63 | Now - give back to migrant communities where I am, return to work folk, students and such.
64 |
65 | Now chasing passive income pursuits. And building that retirement portfolio - read up about FIRE if you are interested.
66 |
67 | Looking to coast after 45 - and then look for consulting only opportunities at the end. Depending on what my kid wants to end up doing.
68 |
69 | Lots more! Let the discussion begin.
70 |
71 | ---
72 |
73 | [`Source`](https://www.reddit.com/r/developersIndia/comments/190l8ap/comment/kgp5ki4/)
74 |
75 |
76 |
77 | `u/impossible__dude` on a post titled, [Professionals with 15+ years experience](https://www.reddit.com/r/developersIndia/comments/190l8ap/professionals_with_15_years_experience/), shared the following advice:
78 |
79 |
80 |
81 | 22+ YOE. CXO.
82 |
83 | Very important to still be sufficiently hands on and not be dependent on someone else (another staff member) for everything.
84 |
85 | At this level, picking up what will keep you ahead of the competition is everything. Could be reading up on some specific tech like Rust and seeing if it makes sense to write a few modules with it. Could be reading up on how to analyze your AWS and GCP bills and understand if the teams are effectively utilizing the resources or overprovisioning. Could be checking out the latest release notes of React Native and trying to understand if upgrading makes sense.
86 |
87 | Overall, being independent and reading up a lot is crucial so that you can bring your own perspective to the team meetings.
88 |
89 | And, of course, learning new ways to convince people never goes out of fashion. Some board member will always bat for AI and LLMs even if the firm doesn't remotely need it. Learning to focus and deploy the available research dollars to the right projects is v crucial.
90 |
91 | ---
92 |
93 | [`Source`](https://www.reddit.com/r/developersIndia/comments/190l8ap/comment/kgpvfe3/)
94 |
95 |
96 |
97 | `u/Plastic-Kiwi-1063/` shared the following advice on a post titled [Professionals with 15+ years experience](https://www.reddit.com/r/developersIndia/comments/190l8ap/professionals_with_15_years_experience/):
98 |
99 |
100 |
101 | Establish clear boundaries, especially where long hours and shifting priorities are common. I’ve worked in a startup for the past two years and faced similar challenges. Here are some strategies that might help:
102 |
103 | - Do the Minimum Required: The more you work, the more work you'll receive. Aim to meet expectations without overextending yourself.
104 | - Gradually Reduce Extra Hours: Start by cutting back on the extra time you work. Do this incrementally to avoid abrupt changes.
105 | - Understand Managerial Behavior: Learn how to navigate your manager’s expectations and behavior effectively.
106 | - Redirect Attention: Use complex, relevant questions about tasks to shift your manager’s focus away from your workload. This can give you some breathing room.
107 | - Estimate and Communicate Timelines: At the start of each task, estimate the time required and stick to it. If additional tasks are assigned, extend your timeline accordingly and attribute delays to these tasks.
108 | - Have Ready Explanations: Be prepared with concise explanations for delays, focusing on task complexity rather than detailed justifications.
109 | - Manage Expectations: If you’re not seeking a promotion or long-term commitment, gradually reduce the quality of your work. By the time any action is taken, you might have another offer.
110 |
111 | Ultimately, you’ll need to adapt these strategies depending on your situation and company dynamics. Play around to see what works best for you.
112 |
113 | ---
114 |
115 | [`Source`](https://www.reddit.com/r/developersIndia/comments/1eze3b8/comment/ljnt8d2)
116 |
117 |
118 |
119 | ## Related Discussions
120 |
121 | - [Your career span in IT sector would be more like 20 years rather than 40 years, so plan accordingly](https://www.reddit.com/r/developersIndia/comments/1bx1yx4/your_career_span_in_it_sector_would_be_more_like/).
122 | - [What is the "endgame" for people in IT?](https://www.reddit.com/r/developersIndia/comments/1ak1l1j/what_is_the_endgame_for_people_in_it/).
123 | - [How have you changed with years of experience? What are the things you did as a fresher that you no longer do?](https://www.reddit.com/r/developersIndia/comments/1bo7sre/how_have_you_changed_with_years_of_experience/).
124 | - [Let's talk performance reviews!](https://www.reddit.com/r/developersIndia/comments/siqswv/lets_talk_performance_reviews/).
125 | - [As a senior dev, how do you work (or mentor) junior folks around you, what have you learned from them?](https://www.reddit.com/r/developersIndia/comments/15jf4o8/as_a_senior_dev_how_do_you_work_or_mentor_junior/).
126 | - [How to deal with being unemployed in the IT sector in your 40s and beyond?](https://www.reddit.com/r/developersIndia/comments/15iopcr/how_to_deal_with_being_unemployed_in_the_it/).
127 | - [How do Indian devs keep up with ageism in the industry?](https://www.reddit.com/r/developersIndia/comments/r9mog3/how_do_indian_devs_keep_up_with_ageism_in_the/).
128 | - [Let's talk performance reviews!](https://www.reddit.com/r/developersIndia/comments/siqswv/lets_talk_performance_reviews/).
129 | - [Thoughts from an Old Timer](https://www.reddit.com/r/developersIndia/comments/xgy8s2/thoughts_from_an_old_timer/).
130 | - [Experienced developers of India, How to be not incompetent at work?](https://www.reddit.com/r/developersIndia/comments/17n1gv5/experienced_developers_of_india_how_to_be_not/).
131 | - [Who is senior software engineer? The question i ask myself.](https://www.reddit.com/r/developersIndia/comments/1bzxktd/who_is_senior_software_engineer_the_question_i/).
132 | - [What do IT employees do after 40? Do you wish you had taken a different career?](https://www.reddit.com/r/developersIndia/comments/1c7lv2t/what_do_it_employees_do_after_40_do_you_wish_you/).
133 |
--------------------------------------------------------------------------------
/src/faqs/approaching-a-DSA-problem.md:
--------------------------------------------------------------------------------
1 | # How to approach a DSA problem?
2 |
3 | ## Understanding the problem
4 |
5 | - The first step in approaching a DSA problem is to understand the essence of
6 | the problem itself. We must try to figure out what the problem demands.
7 | - Not understanding the basic needs of the problem asked is a big mistake. If
8 | the wording of the question is unclear, look at the test cases given for the
9 | particular problem and try to reverse-engineer the demands of the question.
10 |
11 | ## Clearing out a logical path
12 |
13 | - The second step involves building a clear picture of the answer's logic in our
14 | head. If the logic of your answer statement is fairly complicated, consider
15 | writing down comments while implementing the logic in your code.
16 | - Once the logic is thought of, try to think of alternate ways to approach the
17 | problem if it doesn't meet the complexity constraints. Repeat this step until
18 | you're happy with your desired logic for the answer. Using pseudocode or
19 | diagrammatic representations to refine the algorithm before coding can help to
20 | understand the logic and essence of the program well.
21 |
22 | ## Effective Implementation
23 |
24 | - Implement the logic in your code. As said before, consider adding comments to
25 | your code to make the logic "flow" better while solving it. Eventually, with
26 | enough problem-solving, you won't require the comments to implement logic(s)
27 | anymore, though it is a good habit to do so.
28 | - Another "cosmetic" tip is to name your variables well. Try to use as few
29 | variables as possible to minimize the storage space required for your code.
30 | Try to include various problem-solving paradigms such as greedy, dynamic
31 | programming, divide and conquer paradigms to guide the design of your
32 | algorithms.
33 |
34 | ## Testing and submission
35 |
36 | - Once implemented, test your code. Your code should be tested on an exhaustive
37 | set of inputs and outputs. This exhaustive testing will allow you to find and
38 | fix any edge cases that slipped under the radar the first time.
39 | - Try to think about why your code breaks at that edge case and see if it's a
40 | basic logical fallacy in your code or simply a case that could have slipped
41 | between the cracks during the implementation.
42 | - Try using systematic debugging techniques such as print statements, debugging
43 | tools, or test case generators to identify and resolve errors more
44 | efficiently. This would allow you to pinpoint the source of all the errors and
45 | allow you to fix them surgically.
46 |
47 | ## Dealing with fallacies
48 |
49 | - If all else has failed, try a brute force method to meet all the constraints
50 | of the problem and work your way from there. Try to look at your logic and
51 | think about ways it can be optimized, even at the cost of storage space. Try
52 | to think of any way to make your code run faster.
53 | - Try to think of more "elegant" ways that would not require recursion in any
54 | form. Thinking about creative ways to solve problems will allow you to level
55 | up your skills as well as make you think about the logic of your program more
56 | deeply.
57 |
58 | ## Effective debugging
59 |
60 | - Breaking your code down into smaller parts would allow you to approach the
61 | problem in a more appealing way, allowing you to debug and test it easily.
62 | Identify patterns between logic(s) of various problems and think about why
63 | they resemble each other.
64 | - Try thinking about possible trade-offs between **speed** and **memory usage**.
65 | Balancing both is key in real-world situations.
66 |
67 | ## Patience is key
68 |
69 | - Most importantly, you must be patient throughout the whole process. Getting
70 | stuck is a part of the journey. Apart from that, solving more DSA problems
71 | will make you better at it. That is pretty much true for every replicable
72 | activity. Solving more problems, especially harder questions, would allow you
73 | to step out of your comfort zone by a lot.
74 | - Learning new algorithms, mathematical formulas, etc. are all things that would
75 | make you a better programmer in the long run.
76 |
77 | ## Attribution
78 |
79 | This wiki was maintained/written by
80 | Triach Rold.
81 |
--------------------------------------------------------------------------------
/src/faqs/assets/github-small-foss-criteria.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/developersIndia/wiki/dcc00de23521b55b0d788ce3e8eb1a6aa0b6583f/src/faqs/assets/github-small-foss-criteria.png
--------------------------------------------------------------------------------
/src/faqs/campus-placements/README.md:
--------------------------------------------------------------------------------
1 | # Campus Placements
2 |
3 | - [Effect of CGPA on getting a job](./effect-of-cgpa-getting-job.md)
4 | - [Effect of college tier on getting a job](./effect-college-tier.md)
5 | - [Effect of High School grades on getting a job](./effect-of-high-school-grades.md)
6 | - [Effect of backlogs on getting a job](./effect-college-backlog.md)
--------------------------------------------------------------------------------
/src/faqs/campus-placements/effect-college-backlog.md:
--------------------------------------------------------------------------------
1 |
2 | # Effect of backlogs on getting a job
3 |
4 | - [Perspectives \& advice from the community](#perspectives--advice-from-the-community)
5 | - [Related Discussions](#related-discussions)
6 | - [Stories from the community](#stories-from-the-community)
7 |
8 | ## Perspectives & advice from the community
9 |
10 | `u/Adventurous_Top_4993` shared the following advice on a post titled [What will be the impact of having a backlog on my career as a fresher?](https://www.reddit.com/r/developersIndia/comments/1cj0bsn/what_will_be_the_impact_of_having_a_backlog_on_my/):
11 |
12 |
13 |
14 | Some companies in placement have a criteria where u should never have any arrears (Be it cleared or not).
15 | Its called "History of arrears". Some companies want history of arrears to be 0 to even attend their first round.
16 | An arrear gives a black mark in ur placement journey. so try not to get arrears and questions ur consistency so try to complete ur degree without any backlogs. A backlog will always stay in ur profile even if u clear them.
17 |
18 | what is the difference between standing arrears and history of arrears in engineering? Standing arrears means current backlog or in simple words do you have any backlog at present where as history of arrears means during your entire course period the number of backlog you have.
19 |
20 | Do well! Cheers!
21 |
22 | ---
23 |
24 | [`Source`](https://www.reddit.com/r/developersIndia/comments/1cj0bsn/comment/l2d2vu4/)
25 |
26 |
27 |
28 | ## Related Discussions
29 |
30 | - [f'ed up big time. Got a back in 6th sem and I also resigned the internship I had.](https://www.reddit.com/r/developersIndia/comments/1edamie/fed_up_big_time_got_a_back_in_6th_sem_and_i_also/).
31 | - [Are there firms that hire employees with backlogs/no degree](https://www.reddit.com/r/developersIndia/comments/1175hcq/are_there_firms_that_hire_employees_with/).
32 | - [Should I complete my bachelor's?](https://www.reddit.com/r/developersIndia/comments/18zaqlr/should_i_complete_my_bachelors/).
33 | - [What if you can't complete your btech degree in 4 years?](https://www.reddit.com/r/developersIndia/comments/y60bfp/what_if_you_cant_complete_your_btech_degree_in_4/).
34 | - [Feeling Desperate and Scared After Getting a Semester Backlog](https://www.reddit.com/r/developersIndia/comments/1eb9bjm/feeling_desperate_and_scared_after_getting_a/).
35 | - [Am I fucked for jobs?](https://www.reddit.com/r/developersIndia/comments/145ofug/am_i_fucked_for_jobs/).
36 |
37 | ## Stories from the community
38 |
39 | - [Anyone here got a 8lpa job out of college despite having multiple backlogs? If yes, can you please share your story?](https://www.reddit.com/r/developersIndia/comments/so76oo/anyone_here_got_a_8lpa_job_out_of_college_despite/).
40 |
--------------------------------------------------------------------------------
/src/faqs/campus-placements/effect-college-tier.md:
--------------------------------------------------------------------------------
1 | # Effect of college tier on getting a job
2 |
3 | ## Related Discussions
4 |
5 | - [DOES COLLEGE REALLY MATTER](https://www.reddit.com/r/developersIndia/comments/1al5c4x/does_college_really_matter/).
6 | - [Does a college's tier really matter in the end?](https://www.reddit.com/r/developersIndia/comments/19949l9/does_a_colleges_tier_really_matter_in_the_end/).
7 | - [What are tier1, tier2, and tier3 colleges.](https://www.reddit.com/r/developersIndia/comments/18q1mhf/what_are_tier1_tier2_and_tier3_colleges/).
8 | - [How much does a college tag really matter for the first job?[Tier 3 college here]](https://www.reddit.com/r/developersIndia/comments/q9x4qs/how_much_does_a_college_tag_really_matter_for_the/).
9 | - [How much does you college matter in IT?](https://www.reddit.com/r/developersIndia/comments/14k127i/how_much_does_you_college_matter_in_it/).
10 | - [What mistakes did u do in ur college that cost u later ? ( For cse )](https://www.reddit.com/r/developersIndia/comments/1d12ptu/what_mistakes_did_u_do_in_ur_college_that_cost_u/).
11 | - [Take your college more seriously kids](https://www.reddit.com/r/developersIndia/comments/16gmr4x/take_your_college_more_seriously_kids/).
12 |
--------------------------------------------------------------------------------
/src/faqs/campus-placements/effect-of-cgpa-getting-job.md:
--------------------------------------------------------------------------------
1 | # Effect of CGPA on getting a job
2 |
3 | ## Related Discussions
4 |
5 | - [My low CGPA constantly keeping me depressed and demotivated. Can I even get placed?](https://www.reddit.com/r/developersIndia/comments/1abdso5/my_low_cgpa_constantly_keeping_me_depressed_and/).
6 | - [Are there people who succeeded in getting good jobs with low cgpa and tier 3 college?](https://www.reddit.com/r/developersIndia/comments/1c3uwn5/are_there_people_who_succeeded_in_getting_good/).
7 | - [How important is CGPA for placements?](https://www.reddit.com/r/developersIndia/comments/11a0aii/how_important_is_cgpa_for_placements/).
8 | - [What is the minimum CGPA required so as to be eligible to sit in maximum placements?](https://www.reddit.com/r/developersIndia/comments/p07cd7/what_is_the_minimum_cgpa_required_so_as_to_be/).
9 | - [Will low cgpa affect off campus placements?](https://www.reddit.com/r/developersIndia/comments/kow1do/will_low_cgpa_affect_off_campus_placements/).
10 |
--------------------------------------------------------------------------------
/src/faqs/campus-placements/effect-of-high-school-grades.md:
--------------------------------------------------------------------------------
1 | # Effect of High School grades on getting a job
2 |
3 | ## Related Discussions
4 |
5 | - [56 percent in class 12th will I never get a job ?](https://www.reddit.com/r/developersIndia/comments/1dtpxis/56_percent_in_class_12th_will_i_never_get_a_job/).
6 | - [I got 65.83% in 12th Boards. I'm in 2nd Year. Should I be worried?](https://www.reddit.com/r/developersIndia/comments/1e773h3/i_got_6583_in_12th_boards_im_in_2nd_year_should_i/).
7 | - [Developers with low 12th scores did you face any difficulty in interviews?](https://www.reddit.com/r/developersIndia/comments/1gcrtms/developers_with_low_12th_scores_did_you_face_any/).
8 | - [Do 12th marks really matter in IT sectors?? Will I have less opportunities as compared to others?](https://www.reddit.com/r/developersIndia/comments/1cv1jjs/do_12th_marks_really_matter_in_it_sectors_will_i/).
9 | - [I am 12th pass with 58 percentage can get a job in CS](https://www.reddit.com/r/developersIndia/comments/x4y6rl/i_am_12th_pass_with_58_percentage_can_get_a_job/).
10 | - [Do 12th boards marks matter in cse field?](https://www.reddit.com/r/developersIndia/comments/1299r2n/do_12th_boards_marks_matter_in_cse_field/).
11 | - [HOW DO 12TH MARKS AFFECT TECH PLACEMENTS](https://www.reddit.com/r/developersIndia/comments/15v8iqc/how_do_12th_marks_affect_tech_placements/).
12 |
--------------------------------------------------------------------------------
/src/faqs/career-transitions/README.md:
--------------------------------------------------------------------------------
1 | # Career Transitions
2 |
3 | - [From QA/SDET to Developer](./qa-sdet-to-dev.md).
4 | - [From Dev to DevOps](./dev-to-devops.md).
5 | - [To Game Dev](./game-dev.md).
6 |
--------------------------------------------------------------------------------
/src/faqs/career-transitions/game-dev.md:
--------------------------------------------------------------------------------
1 | # To Game Dev
2 |
3 | ## Related Discussions
4 |
5 | - [Is Game dev a good future in India??](https://www.reddit.com/r/developersIndia/comments/16kr4yy/is_game_dev_a_good_future_in_india/)
6 | - [Why less people are interested in game dev in India? Anyone of you interested?](https://www.reddit.com/r/developersIndia/comments/1e0onq0/why_less_people_are_interested_in_game_dev_in/).
--------------------------------------------------------------------------------
/src/faqs/career-transitions/qa-sdet-to-dev.md:
--------------------------------------------------------------------------------
1 |
2 | # QA/SDET to Developer
3 |
4 | - [Perspectives \& advice from the community](#perspectives--advice-from-the-community)
5 | - [Stories from the community](#stories-from-the-community)
6 |
7 | ## Perspectives & advice from the community
8 |
9 | `u/Effective_Spite6462` on a post titled, [Need guidance on switching from testing to development](https://www.reddit.com/r/developersIndia/comments/twol6c/need_guidance_on_switching_from_testing_to/)
10 | shared the following advice:
11 |
12 |
13 |
14 | Learn about your current project/product. Update your CV showing experience in
15 | creating automation framework and working with dev team in debugging the code.
16 |
17 | Learn a framework in any programming language and start making your own project
18 | using that. You are already good with DSA you will be able to solve algorithm
19 | questions in interviews if asked.
20 |
21 | You can explain about your current project and your personal project in
22 | interviews. Since you don't have much experience and you joined this company as
23 | a fresher, present yourself in interview such that when you were given a role
24 | that you didn't like you still didn't give up the chance on learning. Like you
25 | spent your free time on learning technology and understanding the working of
26 | current product.
27 |
28 | At this level interviewers won't think much about what you did before but rather
29 | how good you are. If your ultimate goal is developer then you should switch for
30 | a development profile as soon as possible. If you spend much time in automation
31 | then it Wil get harder to switch to Development.
32 |
33 | Having said that, Automation itself is a good career choice, yes it involves
34 | manual testing and automating the regression testing. You can also learn about
35 | API testing and performance testing. It's a very bright career in itself and
36 | most product based companies hire people as SDET (software development engineer
37 | in test) for Automation.
38 |
39 | According to my research SDET in some companies get higher pay than SDE but
40 | these companies are less in number. SDET can grow very quickly but they reach
41 | peak salary very soon because peak salary of a SDET is less than that of a SDE.
42 | At that point you will come across many companies that will say they cannot pay
43 | you much because it's only testing profile.
44 |
45 | While being a SDET you can switch your lines as Automation developer in
46 | different lines like robotics.
47 |
48 | That's all I know from my research. I might be wrong about certain points but it
49 | is all available on internet.
50 |
51 | TL'DR If you want to switch to Development do it now after learning a tech stack
52 | with which you are comfortable. Show them that you are eager to learn and being
53 | in unfavorable environment doesn't stop you from learning.
54 |
55 | ---
56 |
57 | [`Source`](https://www.reddit.com/r/developersIndia/comments/twol6c/comment/i3gpwlg/)
58 |
59 |
60 |
61 | ## Stories from the community
62 |
63 | - [My journey from test engineer to software developer](https://www.reddit.com/r/developersIndia/comments/16wy6es/my_journey_from_test_engineer_to_software/).
64 |
--------------------------------------------------------------------------------
/src/faqs/contract-work.md:
--------------------------------------------------------------------------------
1 | # Contract work
2 |
3 | ## Perspectives & advice from the community
4 |
5 | `u/arjinium` shared the following advice on a post titled, [Should i switch to contractual full time remote job?](https://www.reddit.com/r/developersIndia/comments/1gajorx/should_i_switch_to_contractual_full_time_remote/).
6 |
7 |
8 |
9 | Purely comparing a Contractual role and a regular Vanilla Employee setup in India - especially when the Contractual role pays better - I would advise you to go for the Contract.
10 |
11 | However, the caveat is - please make sure that there is a decent job security where you are going. In your case you said that they have 1 year's runway, what after that? Remember if it's know that you may have to let go of the job after a year, that means you will have to start looking 3-4 months prior. Try to address this and talk to them.
12 |
13 | Advantages:
14 | On a pure monetary level, a Contract role is better off than a standard Employment:
15 |
16 | 1. You essentially become a sole person business, and can get some taxation advantages based on that (you will need to get a GST number)
17 | 2. You can take advantage of the 44ADA Taxation law and save a huge chunk of your income from falling prey to the taxman. Your effective %age of income that goes towards tax is usually 10% in Contractual roles vs 25% in standard roles above 15LPA - huge savings.
18 | 3. You said the role is remote and with a non Indian organisation - both mean that you now save even more money and have relatively better work culture than an Indian organisation.
19 | 4. You will directly work with the US org - which hopefully should give you better opportunities to work on actually good tech and infra. Whereas Indian dev centres usually get outdated projects or sub par projects to work on in India.
20 |
21 | Cons:
22 |
23 | 1. A contractor is never an employee - and that distinction may be prominent if there are more employees than contractors.
24 | 2. You have to get used to a lot of procedures - getting GST number, Filing GST returns regularly, Keeping track of time and filling in timesheets at the company etc
25 | 3. Contractors are basically mercenaries - hired-with-pay for work - and there may be a general difference in attitude, what I mean is, there is a possibility that one may be used to cushy employee treatment, while that may not be the case here.
26 | 4. No ESOPs or RSUs for you in contract roles
27 | 5. Job security and finding your next client - you will have to build a freelancer/mercenary mindset where you are always looking for your next client, are building your portfolio, marketing your skills etc.
28 | 6. You can definitely include this on your rsume - but be aware that in the US they do not give out appointment and experience letters to contractors, plus being a contractor you don't have the usual paper trail that is expected from employees in India when an Indian HR recruits - so no payslips etc. - I do not have personal experience, but this could make it more difficult than usual to get recruited as an employee again (mind you your experience will be counted).
29 |
30 | Your question:
31 |
32 | ```
33 | •If I don’t quit and continue as a full-time contractor with the startup, could this cause issues? Would my employer find out, given the time zone difference?•If I don’t quit and continue as a full-time contractor with the startup, could this cause issues? Would my employer find out, given the time zone difference?
34 | ```
35 |
36 | Why would you want to work full time at two places especially when one overworks you for 15 hrs a day - that is recipe for disaster.
37 |
38 | ---
39 |
40 | [`Source`](https://www.reddit.com/r/developersIndia/comments/1gajorx/comment/ltgtmkc/)
41 |
42 |
43 |
44 | `u/user501230` on a post titled [Does anyone use Deel for payroll management?](https://www.reddit.com/r/developersIndia/comments/osk5u1/does_anyone_use_deel_for_payroll_management/) shared the following advice on **working with overseas clients**:
45 |
46 |
47 |
48 | Hi folks, so I am using Deel for last 4 months now so this is going to be the long post as I will cover every important thing which is needed for one to be employed by overseas companies. I went through lots of hassle to understand how this entire system works. Here are some points from me:
49 |
50 | 1. **Deel**: The Deel Inc is an US based company and it helps companies in hiring/contracting people overseas. In India, Deel is registered as Deel EOR PVT LTD.
51 | Read here to know more about EOR. Deel platform is intuitive and easy to use. My employer uses it to for my payroll management. It helps employer to share the contract with employee/contractor. Once you and employer agree on the employment terms you can sign the contract. The Deel will auto-generate an invoice for you based on the terms in your contract and share it with employee and transfer the money to your Deel wallet. Deel wallet(it's free) is nothing but a place where it shows how much money you have earned. Having money parked in your Deel account does not mean money has reached to you. One has to withdraw the money in his/her bank account. You select a payment method to withdraw the amount from the different payment options that are provided by Deel. I will come back to you on why you should add your bank account and in payment method later. For India, Deel does not handle tax compliance so you are on your own. As of today, there are two health insurance options available on Deel platform for Indians but both are useless.
52 | 2. **Taxation**: When you are working for an overseas company you are providing them your services and billing them(remember auto-generated invoices on Deel in above sections) and that's where taxation gets complicated. Now you will be entitled to pay GST(Goods and Services Tax) along with income tax. Yes, both GST and income tax. Before you get disappointed by the taxes let me tell you as of now, export of Goods and Services are taxed at 0% i.e. you will pay ZERO GST. Although you don't have to pay GST, you will have file GST every month. Sounds funny but that leads us to next part i.e. Compliance.
53 | 3. **Compliance**: So far you know you have to file GST even though you will be exporting your services and are entitled for zero GST. As you have to pay GST, you will need a good CA who does GST registration and files it on your behalf. CA will be responsible for your entire taxation and compliance work. Find a CA you know or people recommend. I personally feel if your CA asks for more 40k/year, consider a different CA.
54 | Your CA will handle everything from taxation to compliance but it's good to understand the taxation and compliance relevant for you. It will help you make wise decisions as it's your money. Let's begin certain important points:
55 | 4. You will have to register for GST which takes around two weeks of all the documents are fine. Sometimes more documents and clarity is asked from GST team and that will make the GST registration process longer, good thing is without GST you can take 20 lakhs INR in your account. in respect to Deel, you will keep working for your company and raise invoice bi-weekly/monthly and get paid in your Deel wallet. After you have pulled(withdrawn) 20 lakh INR from your Deel wallet to your bank account you ave to stop and sort out your GST registration.
56 | 5. FIRC(Foreign Inward Remittance Certificate) this is one of the most important compliance documents. As you will receive money from foreign hence it is important for authorities to know the purpose of receiving foreign fund. FIRC document is provided by banks when you receive foreign fund(your salary in this case), this document contains all the relevant details like sender and it's address, receiver and it's address, amount, currency exchange rate, purpose code, etc. Each time you receive foreign fund you will have to get an FIRC for the same from your bank.
57 |
58 | FIRC can be issued by banks only thus it is important to add your bank account on the Deel for withdrawing money from your Deel wallet.
59 | Most of the banks do not provide FIRC so choose some correct bank which does it. For example , SBI has very good exchange rate(dollar to rupees) but they told me they would provide only one FIRC per Financial year but I needed FIRC everytime I received money so I went ahead with HDFC bank. I opened a current account in HDFC and they provide me FIRC every time I receive money their currency exchange rate is almost 80p less than SBI but I negotiated well and got +50p on current day's exchange rate.
60 |
61 | 6. If your annual salary is less than 50 lakh rupees you will be entitled to claim presumptive tax. For annual income more than 50 lakh you will have to get your income audited by CA. Either ways you will have a CA to take care of it. I recommend reading presumptive tax.
62 | 7. You will have to pay Advance Income Tax every quarter.
63 |
64 | ---
65 |
66 | [`Source`](https://www.reddit.com/r/developersIndia/comments/osk5u1/comment/ht0jg08/)
67 |
68 |
69 |
70 | `u/mobihack` shared the following advice on a post titled, [Work for US company as Independent Contractor.](https://www.reddit.com/r/developersIndia/comments/1akjwv9/work_for_us_company_as_independent_contractor/).
71 |
72 |
73 |
74 | 1. Yeah. My employer uses wise. (Make sure to have KYC complaint bank account else the money may be put on hold until completed)
75 | 2. You can make use of the Presumptive Taxation Scheme under Section 44ADA of the Income Tax Act, and pay tax on freelance income on only half of their gross annual income, provided the total income for the year is less than Rs. 50 lakhs. For example if you had 18 lakhs rupees deposited as earnings, you will have 9 lakh rupees taxable income. And you can have further deductions based on which tax regime you are selecting.
76 | 3. I did my tax filing last year by myself and I intend to do the same this year too. It's fairly straightforward but I would suggest you have a list of deposits related to your earnings in a spreadsheet. Contrary to Indian salaried people, none of our details are prefilled in the application. (Because there is no AIS data for our kind of transactions)
77 |
78 | An issue you may run into is that your company may give some money for remote setup or equipments deposited this way. But from tax point of view, this amount is also taxable and don't remove it from the calculation.
79 |
80 | Just assume you are a freelancer and most questions will be answered easily.
81 |
82 | ---
83 |
84 | [`Source`](https://www.reddit.com/r/developersIndia/comments/1akjwv9/comment/kp8giu8/)
85 |
86 |
87 |
--------------------------------------------------------------------------------
/src/faqs/effect-of-gap-year-on-getting-a-job.md:
--------------------------------------------------------------------------------
1 |
2 | # Effect of gap years on getting a job
3 |
4 | - [Perspectives \& advice from the community](#perspectives--advice-from-the-community)
5 | - [Related Discussions](#related-discussions)
6 | - [Stories from the community](#stories-from-the-community)
7 |
8 | ## Perspectives & advice from the community
9 |
10 | `u/DistributionSad2038` shared the following advice on a post titled, [Is gap of 1 year is really bad?](https://www.reddit.com/r/developersIndia/comments/189wro2/is_gap_of_1_year_is_really_bad/):
11 |
12 |
13 |
14 | What will happen is you won't be the most desirable candidate. Now you have to explain the reason of your gap to the hr there are three replies that I saw work the best:
15 |
16 | 1. I was intentionally looking for a job in my field however I did keep myself abreast with (put recent technical advancements) and I did do some (add courses) to help contribute more in the professional world
17 | 2. I had to fight against personal battles and hence that took a priority but now that I am back I am ready to give my hundred percent towards my career
18 | 3. I was having another course of plans specifically masters planned in my pocket but after my research I did see that experience and skills matter more and hence Im trying to get hands on experience to get a job.
19 |
20 | Secondly, I will suggest you to message the hrs of companies (small bigstartps ) on LinkedIn
21 |
22 | And thirdly, I would suggest you to find some internships or projects on wellfound, indeed, etc
23 |
24 | You ca do this
25 |
26 | ---
27 |
28 | [`Source`](https://www.reddit.com/r/developersIndia/comments/189wro2/comment/kbuf07p)
29 |
30 |
31 |
32 | ## Related Discussions
33 |
34 | - [How crazy is taking 2 years gap for gate? Help please!!](https://www.reddit.com/r/developersIndia/comments/1em8vsd/how_crazy_is_taking_2_years_gap_for_gate_help/).
35 | - [Need Help How do you justify a career gap of 3-6 months](https://www.reddit.com/r/developersIndia/comments/1bouvak/need_help_how_do_you_justify_a_career_gap_of_36/).
36 | - [I have 6 years of gap after graduating in computer engineering in 2018. I need some serious help!](https://www.reddit.com/r/developersIndia/comments/1bxv316/i_have_6_years_of_gap_after_graduating_in/).
37 | - [People, there is nothing wrong with having a gap.](https://www.reddit.com/r/developersIndia/comments/12eytvo/people_there_is_nothing_wrong_with_having_a_gap/).
38 |
39 | ## Stories from the community
40 |
41 | - [4 YEARS of career gap, from a different field, landed a software developer role at a start up in 2024 job market](https://www.reddit.com/r/developersIndia/comments/1fr9ugm/4_years_of_career_gap_from_a_different_field/).
42 | - [Finally, Got a 6 LPA remote Data Analyst job after 1.5 yrs of Gap year.](https://www.reddit.com/r/developersIndia/comments/1bweia3/finally_got_a_6_lpa_remote_data_analyst_job_after/).
43 | - [Do you have any Career Gap ? Have you lied about it ?](https://www.reddit.com/r/developersIndia/comments/1bx6rj4/do_you_have_any_career_gap_have_you_lied_about_it/).
44 | - [People with gap in their Resume, Where are you now?](https://www.reddit.com/r/developersIndia/comments/1dhvw9f/people_with_gap_in_their_resume_where_are_you_now/).
45 |
--------------------------------------------------------------------------------
/src/faqs/freelancing.md:
--------------------------------------------------------------------------------
1 |
2 | # Freelancing
3 |
4 | - [How do I find clients?](#how-do-i-find-clients)
5 | - [How do I decide how much to charge?](#how-do-i-decide-how-much-to-charge)
6 | - [Related Discussions](#related-discussions)
7 | - [Stories from the community](#stories-from-the-community)
8 |
9 | ## How do I find clients?
10 |
11 | `@jarmos.rs` on developersIndia discord shared the following advice:
12 |
13 |
14 |
15 | I've come across a lot of people lately asking questions about freelancing. Among all the question one is very common: "How do I find clients?". So, I thought I should attempt to answer this question as much as I can.
16 |
17 | But before that, a couple of gotchas & business 101:
18 |
19 | - It's cheaper & less time consuming to keep working with an older client than look for a new client.
20 | - Second, client interactions are pretty much like dating. Just as how you wouldn't date based on the other person's bank balance or ... you shouldn't do business based on the clients's budget either. Strive to deliver the best quality of service & products, the _$$$_ will flow in eventually.
21 | - And finally identify what kind of clients you would like to work with based on how you want to freelance.
22 |
23 | With that said, let's try to identify who an ideal client is:
24 |
25 | - If you want to pursue a full-time job yet keep freelancing on the side to augment your income. Then your ideal clients are those who doesn't bat an eye about code quality, tests & standard practices. All they need is for their deliverables to work as they require it to be. Where do you find these clients? Fiverr, PeoplePerHour & so on. You could try Reddit too on that matter.
26 | - If you plan on making freelancing a full-time career some day, this is where you start dipping your feet before diving straight in. These clients are startup founders & MSME owners who either just got funded or don't have the budget to hire FT employees yet. Do note, these are clients with whom you can expect to create a long-term relationship & hence start earning more $$$ over time. Most of the time these clients aren't dumb & do care about quality checks & standard practices.
27 | - Third list of clients are those with the highest budget & those who're willing to hire you in the long-term (think 3+ months) for a project. You'll not find them right of the bat. It takes time, often years to build a relationship & find such clients. But these are also the clients who'll pay you the biggest $$$ & support your finances enough to obligate you to go full-time freelancing.
28 |
29 | So, I hope it answered the question on "How to find clients?". Obviously, there's much to talk about & individual mileage will vary but I believe this is how anyone, regardless of experience can get started freelancing. Got more questions, ask here for others to learn something or as always my DMs are open.
30 |
31 | ---
32 | [`Source`](https://discord.com/channels/669880381649977354/670198758343966740/855819850815111179)
33 |
34 |
35 |
36 | `u/catrovacer16` shared the following advice on a post titled, [Do freelancing actually works. Show Proof](https://www.reddit.com/r/developersIndia/comments/17v0m4j/do_freelancing_actually_works_show_proof/).
37 |
38 |
39 |
40 | - Search for freelancers on upwork that are doing similar work as you say front end developer etc. and learn how they are pitching their skills.
41 | - Make a good profile and set a good profile picture. Add relevant details about your experience in the field and how you are the best man for the job
42 | - Add as many visuals as you can in both profile as well as proposals. Like previously built websites with photos and links. A good catalogue easily catches attention.
43 | - Offer lower rates early on and mention why you are offering lower rates.
44 | - Pick a more niche problem statement, if possible draw them a plan how you would solve their problem efficiently.
45 | - Make sure your proposals are precise, to the point and curated to the client's needs.
46 |
47 | ---
48 |
49 | [`Source`](https://www.reddit.com/r/developersIndia/comments/17v0m4j/comment/k9br2bx/)
50 |
51 |
52 |
53 | ## How do I decide how much to charge?
54 |
55 | `@jarmos.rs` on developersIndia discord shared the following advice:
56 |
57 |
58 |
59 | A while ago I shared a very brief write-up on how to get started freelancing . And since then I was asked a couple more questions like "How do I decide how much to charge?" & so on. So, today I thought it would be nice to share how I calculate my fees.
60 |
61 | But before we dig into the main course, some starters first.
62 |
63 | Remember;
64 |
65 | - You're your own boss when freelancing, so you decide how much annual income you should be earning.
66 | - The eventual profits that you earn is directly proportional to the quality of service you provide to the client.
67 | - Your earning potential is also decided based on where you procure your clients from. Clients from upwork & related marketplaces pay shit for more work. Clients from Angel.co & such who're more professional might pay you what's worth.
68 |
69 | That said here's how I calculated my fees when I started some 6 years ago in college. I created an UpWork profile & started bidding only to realise I was getting ghosted. And if you feel the same don't be surprised. Marketplaces are a battle-royale to the bottom of the barrel. So, if you charge the lowest & you also get have good rating you can make a living off of marketplaces. Suffice to say, I didn't survive there & don't recommend to start out there either.
70 |
71 | I went full-time on 2019 after quitting my job & was fortunate enough to land a client soon after who I was working with earlier. And as such this is how calculated my hourly rate: Expected Annual Income divided by # of Working hours in a year.
72 |
73 | With that in mind, assume you want to earn ₹600,000/yr & work ~1920hrs/yr (8hrs for 5-working days a week). So, that would mean your hourly rate should be ~₹300/hr. Now obviously this is a rough estimation but remember my intention was to get your started somehow. And as you keep perfecting your craft you'll eventually learn the other nitty-gritty details as well.
74 |
75 | Some ending notes, always prioritise providing the best service over your income. Don't regret increasing your hourly rate by some
76 |
77 | ---
78 | [`Source`](https://discord.com/channels/669880381649977354/670198758343966740/861203010382200862)
79 |
80 |
81 |
82 | `u/the4thkillermachine` shared the following advice on a post titled, [Do you freelance? How do you charge?](https://www.reddit.com/r/developersIndia/comments/ljh9cb/do_you_freelance_how_do_you_charge/).
83 |
84 |
85 |
86 | I freelance full-time as an ML Engineer, so I guess I can help you with my two cents.
87 |
88 | Setting a minimum base rate for yourself helps. Then charge them like this: base rate x (time to complete the task in hours x 4). So, assuming your rate is, say $75/hr & a client asks you to create a SPA landing page for them. You would charge them 75 x (8 x 4) = $2400 for one single landing page. Of course you can increase your base rate as you gain more experience.
89 |
90 | Now if you're wondering why multiply the time to complete the task by 4? That's to account for the idea of unpromising & over-delivering. In other words, even if creating a single landing page takes you 8 hours to complete. Tell your client it would take you at least 24 hours to complete.
91 |
92 | This way not only do you've a happy client who might come back to you again, but you pocketed 4x the profits as well!
93 |
94 | I don't use the formulae any more as I've experience dealing with a wide range of clients & business problems. So, I quote a different rate for each client and/or the projects, depending on the complexity & other variables.
95 |
96 | EDIT: I realized OP asked the question in context to Indian clients. Although I don't deal with many Indian clients, but I've hired Indian freelancers earlier. Their base rate used to be anything between ₹125-1200 depending on their experience.
97 |
98 | The last freelancer, I hired was a college kid who charged me ₹125/hr.
99 |
100 | Also, just so you know, charging Indian clients in $ might not work out, I guess. Although I'm not sure of it.
101 |
102 | ---
103 |
104 | [`Source`](https://www.reddit.com/r/developersIndia/comments/ljh9cb/comment/gngfx8f/)
105 |
106 |
107 |
108 | ## Related Discussions
109 |
110 | - [A lot of people in this sub are budding freelancers. So, here is how to apply for GST registration(and how much time it takes)](https://www.reddit.com/r/developersIndia/comments/15xcvg2/a_lot_of_people_in_this_sub_are_budding/).
111 | - [Scope of freelance development work in India](https://www.reddit.com/r/developersIndia/comments/13nrq86/scope_of_freelance_development_work_in_india/).
112 | - [Legal formalities for developers who wish to start freelancing](https://www.reddit.com/r/developersIndia/comments/x6csij/legal_formalities_for_developers_who_wish_to/).
113 | - [Freelancing for the first time. Please help!](https://www.reddit.com/r/developersIndia/comments/wju8s4/freelancing_for_the_first_time_please_help/).
114 | - [Use the "Productized Service' technique to increase your freelance earnings.](https://www.reddit.com/r/developersIndia/comments/1cawuuy/use_the_productized_service_technique_to_increase/).
115 | - [Freelancers reading this post, how do you decide on the pricing?](https://www.reddit.com/r/developersIndia/comments/1fb3ggz/freelancers_reading_this_post_how_do_you_decide/).
116 |
117 | ## Stories from the community
118 |
119 | - [How I started Freelancing right after joining college](https://www.reddit.com/r/developersIndia/comments/153yymh/how_i_started_freelancing_right_after_joining/).
120 | - [This scene from The Dark Knight Rises actually inspired me to finally quit my job 11 years ago and dive into full-time freelancing.](https://www.reddit.com/r/developersIndia/comments/1d65oi1/this_scene_from_the_dark_knight_rises_actually/).
121 | - [I could not make it as a freelancer, And I had everything dependent on it!](https://www.reddit.com/r/developersIndia/comments/wy775h/i_could_not_make_it_as_a_freelancer_and_i_had/).
122 |
--------------------------------------------------------------------------------
/src/faqs/health/managing-eye-strain.md:
--------------------------------------------------------------------------------
1 | # Managing Eye Strain
2 |
--------------------------------------------------------------------------------
/src/faqs/how-to-start-dsa.md:
--------------------------------------------------------------------------------
1 | # How to Start DSA
2 |
3 | Every company is having Competitive Programming-based OA rounds and is asking DSA in tech rounds these days. If you're not doing DSA, the number of companies you can apply to gets drastically reduced. So here's a guide on how you can get started with DSA to ace those OAs and interviews.
4 |
5 | ## Pick a Language
6 |
7 | The most popular languages for doing DSA are C++, Java, and Python (in decreasing order). You *can* do DSA in any language you desire; however, picking one of the popular options is better since you will have access to many more resources and help online. If you have no language bias, I would recommend C++.
8 |
9 | When doing competitive programming, it's generally preferred to use C++ or Java over Python since you're working with a time limit, and Python, being an interpreted language, is a bit slower than the other two options.
10 |
11 | ## Get Started
12 |
13 | ### Syllabus
14 |
15 | Here is a *rough* syllabus of topics that you'll need to cover:
16 |
17 | - Programming Basics
18 | - Data types
19 | - I/O
20 | - etc.
21 | - Time Complexity and Space Complexity
22 | - Searching
23 | - Linear Search
24 | - Binary Search
25 | - Sorting
26 | - Selection Sort
27 | - Bubble Sort
28 | - Merge Sort
29 | - Quick Sort
30 | - Data Structures
31 | - Sets
32 | - Maps
33 | - Stacks
34 | - Queues
35 | - Linked Lists
36 | - Number Theory
37 | - Bit Manipulation
38 | - Recursion
39 | - Greedy Algorithms
40 | - Graph Theory
41 | - DFS
42 | - BFS
43 | - Dijkstra
44 | - Binary Search Trees
45 | - Dynamic Programming
46 | - Other Specific Algorithms:
47 | - Hashing
48 | - Sliding Window
49 | - Divide and Conquer
50 |
51 | ### Learning Resources
52 |
53 | Okay, I know the syllabus, where do I learn from?
54 |
55 | #### Books
56 |
57 | If you prefer the book learning approach, you are covered:
58 |
59 | - [Competitive Programmer’s Handbook](https://cses.fi/book/book.pdf) - This book is an amazing resource that covers everything, even up to advanced CP concepts. However, for just cracking DSA interviews, you can cover up to chapter 13, which should cover all the basic concepts and introduce you to some medium-level Graph concepts. It is mostly language agnostic but has code in C++.
60 | - [Introduction to Algorithms](https://mitpress.mit.edu/books/introduction-algorithms-third-edition)
61 | - [A Common-Sense Guide to Data Structures and Algorithms](https://www.amazon.com/Common-Sense-Guide-Data-Structures-Algorithms/dp/1680507222)
62 | - [Saadhan - developersIndia Resource Collection](https://saadhan.developersindia.in/resources?category=dsa)
63 |
64 | #### Video Lectures
65 |
66 | If you prefer the video lecture approach:
67 |
68 | - [Luv CP/DSA Playlist](https://www.youtube.com/playlist?list=PLauivoElc3ggagradg8MfOZreCMmXMmJ-) - Not to be confused with Luv Babbar, this is a different guy. The playlist is great, and he's a great teacher. The playlist is C++-focused, but the explanation of concepts will be language agnostic. Warning: This playlist is in Hinglish.
69 | - [Aditya Verma](https://www.youtube.com/c/AdityaVermaTheProgrammingLord/playlists) - Very popular for his Dynamic Programming playlist but also has playlists on other concepts like Binary Search, Recursion, Stacks, Sliding Window, etc.
70 | - [Striver](https://www.youtube.com/c/takeUforward/playlists) - Very popular for his problem set but has nice playlists explaining some topics like Recursion, DP, Greedy Algos, Binary Search, Trees
71 | - [LuvBabbar](https://www.youtube.com/playlist?list=PLDzeHZWIZsTryvtXdMr6rPh4IDexB5NIA) - Not a big fan of the guy personally, but this is a well-compiled playlist to study all the topics.
72 |
73 | #### Roadmaps
74 |
75 | If you want to follow a laid-out roadmap:
76 |
77 | - [Roadmap to CP](https://docs.google.com/document/d/1N4--AK1rC45rjY-o0JFUwz1jRRc56w_QLurYCimH2Mc/edit#) - Has question links and lecture links for the entire syllabus relevant to you. You can leave the extra “Advanced” concepts at the end.
78 | - [roadmap.sh - Data Structures & Algorithms Roadmap](https://roadmap.sh/datastructures-and-algorithms) - Step-by-step guide to learn Data Structures and Algorithms.
79 |
80 | #### Other Helpful Websites
81 |
82 | To quickly brush up on any algorithm:
83 | - [CP-Algorithms](https://cp-algorithms.com/) - An absolutely brilliant resource website. You can look up any algorithm, and this website will give you a great theory explanation along with pseudocode, if not full C++ code. It also provides relevant questions from CP websites. No BS, to-the-point website.
84 |
85 | ### Questions
86 |
87 | I know the syllabus, I have understood the concepts, where and which questions do I solve?
88 |
89 | If you're starting off with the absolute basics, before jumping onto the problem sets, consider doing some practice on the easy questions. For that, you can jump onto [Leetcode Easy](https://leetcode.com/problemset/all/?difficulty=EASY&page=1) and keep solving until you feel comfortable solving any Easy question insight. Then you can move on to the problem sets and start solving topic-wise questions.
90 |
91 | #### Compiled Problem Sets
92 |
93 | Here are some compiled problem sets that are considered enough to conquer any interview you want:
94 |
95 | - [InterviewBit Question Set](https://www.interviewbit.com/courses/programming/) - Topic-wise questions that are asked many times by top companies, ranging from easy to hard. Personally, I used this site during my placement season. Major recommendation.
96 | - [450 DSA Cracker](https://450dsa.com/) - Luv Babbar's 450 question list. Very popular list among students.
97 | - [Blind 75 LC](https://leetcode.com/discuss/general-discussion/460599/blind-75-leetcode-questions) - Popular list of 75 questions that, if you can solve, you can confidently crack any interview.
98 |
99 | #### For OA Practice
100 |
101 | A big factor in interviews for DSA questions as well as in OA Rounds is **time**. You have to be able to solve the questions within a certain time limit. Thus, it's good to give a few contests on CP websites so that you can get used to constraints. Here are some beginner-friendly ones:
102 |
103 | - [Codeforces Contests](https://codeforces.com/contests?complete=true) - To start off, give only the Division 3 contests and solve the A and B questions, and slowly aim to solve C. You can start to give Div 2 contests as well once you feel comfortable.
104 | - [LeetCode Contests](https://leetcode.com/contest/) - To start off, aim to solve at least 2 questions in all the weekly and biweekly contests.
105 | - [Atcoder Contests](https://atcoder.jp/contests/) - To start off, just give the 'Beginner Contests'.
106 | - [Codechef Contests](https://www.codechef.com/contests?itm_medium=navmenu&itm_campaign=allcontests) - Codechef has fallen off the throne for a while because of its degrading quality and user base, but it's still a decent site for beginners. To start off, I wouldn't recommend the Long contests because it has unnecessary brute force questions. Instead, just do the timed contests like Cook-off, Lunchtime, and Starters.
107 |
108 | #### Other Practice Platforms
109 |
110 | |Name|Link|
111 | |:-|:-|
112 | |HackerRank|[hackerrank.com](https://www.hackerrank.com/)|
113 | |CodeSignal|[codesignal.com](https://codesignal.com/)|
114 | |TopCoder|[topcoder.com](https://www.topcoder.com/)|
115 | |InterviewBit|[interviewbit.com](https://www.interviewbit.com/)|
116 | |Codewars|[codewars.com](https://www.codewars.com/)|
117 | |Project Euler|[projecteuler.net](https://projecteuler.net/)|
118 | |Spoj|[spoj.com](https://www.spoj.com/)|
119 | |GeeksforGeeks|[geeksforgeeks.org](https://www.geeksforgeeks.org/)|
120 |
121 |
122 |
123 | ---
124 |
125 | This wiki was originally written by [u/sggts04](https://reddit.com/u/sggts04).
126 |
127 | Later revisions done by:
128 | - [u/LinearArray](https://reddit.com/u/lineararray)
129 |
--------------------------------------------------------------------------------
/src/faqs/performance-reviews.md:
--------------------------------------------------------------------------------
1 |
2 | # Preparing for Performance Reviews
3 |
4 | - [Perspectives \& advice from the community](#perspectives--advice-from-the-community)
5 | - [Related Discussions](#related-discussions)
6 |
7 |
8 | ## Perspectives & advice from the community
9 |
10 | `u/mango_admi` shared the following advice on a post titled, [Got told keeping me in the project is very difficult because I am very inefficient and irresponsible.](https://www.reddit.com/r/developersIndia/comments/1ijp2e3/got_told_keeping_me_in_the_project_is_very/)
11 |
12 |
13 |
14 | My friend you need to work on your communication skills and make sure that you are documenting things that you do. Try doing this for a start-
15 |
16 | 1. Create a excel file with details of what you do on a daily basis. Have the following details in it- Date, Task name, status report, who to report to, reported today?
17 | 2. Whatever happens, update this before you log off for the day.
18 | 3. When you are updating then check if you have reported to the concerned person, if not then send mail or ping with the current status.
19 | 4. Keep your lead updated about your daily work.
20 | 5. Start paying attention in meetings and reading mails thoroughly. Use GPT to summarize meeing minutes and mails so that you can get easy language to understand what is being asked of you. Also ask questions in meetings if you have any. Dont keep quiet.
21 |
22 | Once you create a habit of reporting your work and speaking up, you wont need to manage this excel as the trust in you will increase and even if you dont report daily, it will be seen as a sign that everything is okay on your end.
23 |
24 | ---
25 |
26 | [`Source`](https://www.reddit.com/r/developersIndia/comments/1ijp2e3/comment/mbfx2x9)
27 |
28 |
29 |
30 |
31 | `u/ReverseDebugger` shared the following advice on a post titled, [Managers & Devs: Year End review 101, how tos & what tos.](https://www.reddit.com/r/developersIndia/comments/1irp36p/managers_devs_year_end_review_101_how_tos_what_tos/)
32 |
33 |
34 |
35 | Ratings are pre-decided regardless of how much work you put in. Learn and read about how Bell Curve works.
36 |
37 | As far as your experience goes, my personal experience stands at 13y. I would highly recommend you at this point to not to take up the lead role and in-fact, try to be hands-on as much as possible. If you are leading here, I would personally recommend you to look for a job where you are not the best. Since you are early in your career, your focus should be on coding and of course learning other software skills like communication, problem solving, and execution/planning as you mentioned but refrain from taking up team responsibilities. It’s more of a hassle than you think it is.
38 |
39 | Lastly, I would suggest you to discuss on the following:
40 |
41 | 1. How’s your company doing and what are their plans for the new FY and see if they align with your goals.
42 | 2. How or what you could change or improve and why?
43 | 3. What’s new in terms of tech improvements and in what areas you would learn.
44 | 4. Any plans of scaling the team further or what kind of projects is your team anticipating.
45 | 5. Lastly, if possible, ask them to allow you to work on open-ended and complex problems where you may struggle.
46 |
47 | In terms of rating, right question to ask is, what it takes to achieve 4-5/5 rating? What areas you could improve upon.
48 |
49 | As far as your feedback goes, you could share it in a constructive manner around:
50 |
51 | 1. What went well
52 | 2. What didn’t go well (for you and for your team)
53 | 3. What can be done better
54 | 4. Any other feedback
55 |
56 | Fine tune the above as you think your manager is open for a candid feedback or refrain from being too direct and craft it as per your experience. Hope this helps.
57 |
58 | ---
59 |
60 | [`Source`](https://www.reddit.com/r/developersIndia/comments/1irp36p/comment/mdaa4nz)
61 |
62 |
63 |
64 | `u/Inside_Dimension5308` shared the following advice on a post titled, [Managers & Devs: Year End review 101, how tos & what tos.](https://www.reddit.com/r/developersIndia/comments/1irp36p/managers_devs_year_end_review_101_how_tos_what_tos/)
65 |
66 |
67 |
68 | You should already know your performance rating based on how your manager is behaving with you. If he mostly sounds pissed and tries to point out your mistakes, you are in the below average rating(2). If your manager is encouraging you to take more responsibility. You are mostly in average(3) rating.
69 |
70 | If your manager is mostly happy and praising you, you are in the above expectation(4) rating. However, the behaviour can be deceptive. So, don't quote my words. It is better to rely on regular feedback to understand your performance rather than waiting for year end.
71 |
72 | What you shouldn't say? Don't get aggressive with whatever you say. Don't start pointing mistakes of your manager. Don't get personal. Don't start recalling your specific contributions. Your performance is not based on micro-contributions.
73 |
74 | What you should say? You can present your dissatisfaction providing a macro-view of where you have excelled which justifies your better rating(based on your expectations).
75 |
76 | ---
77 |
78 | [`Source`](https://www.reddit.com/r/developersIndia/comments/1irp36p/comment/mdb1sj0)
79 |
80 |
81 |
82 | ## Related Discussions
83 |
84 | - [Let's talk performance reviews!](https://www.reddit.com/r/developersIndia/comments/siqswv/lets_talk_performance_reviews/)
--------------------------------------------------------------------------------
/src/faqs/switching-jobs/README.md:
--------------------------------------------------------------------------------
1 |
2 | # Switching Jobs
3 |
4 | - [Planning for Resignation](./planning-for-resignation.md)
5 | - [Negotiating Notice Periods](./negotiating-notice-periods.md)
6 | - [Asking for Referrals](./asking-for-referrals.md)
7 | - [Choosing your new workplace](./choosing-your-new-workplace.md)
8 | - [Negotiating Salaries](./negotiating-salaries.md)
9 | - [Rejecting a Job Offer](./rejecting-an-offer.md)
10 | - [Sharing offer letters & past salaries with recruiters](./sharing-offer-letters-and-past-salaries.md)
11 | - [Switching from a Service Based to a Product Based Organisation](./service-based-to-product-based.md)
12 |
--------------------------------------------------------------------------------
/src/faqs/switching-jobs/asking-for-referrals.md:
--------------------------------------------------------------------------------
1 | # Asking for job referrals
2 |
3 | ## Perspectives & advice from the community
4 |
5 | `u/Enforcerboy` on a post titled
6 | [Getting ghosted after asking for referrals is frustrating](https://www.reddit.com/r/developersIndia/comments/vclqru/getting_ghosted_after_asking_for_referrals_is/)
7 | shared the following advice:
8 |
9 |
10 |
11 | Here's the thing with referrals.
12 |
13 | Employees have the incentive to refer you, because they will get referral bonus,
14 | if you get hired.
15 |
16 | But given that most referrals aren't going to get hired, and that many people
17 | getting the offer, might not join, they don't have much incentive to spend time
18 | on you out of their busy day.
19 |
20 | So, unless the person who you are approaching is a close friend, make their job
21 | of referring you as easy as possible.
22 |
23 | Always send the link to a job from their company's career page, along with your
24 | resume:
25 |
26 | Not "refer me for an appropriate role based on my resume".
27 |
28 | Not Linkedin job link. They mostly don't match 1:1 with the internal job
29 | posting. And if you are too lazy to look for it, expect them be even more lazy.
30 |
31 | And certainly not the screenshot of the job opening.
32 |
33 | It's not just height of being lazy, but really rude.
34 |
35 | You are essentially telling them that while you don't even have enough time to
36 | share a link, they are supposed to type out the title from the screenshot in
37 | their company's portal, find the relevant job by reading each description, and
38 | then confirm with your highness, if they find 2-3 similar ones, that they aren't
39 | sure of. This is something that I wouldn't even do for a close friend. If a
40 | stranger sends this, I will just block them. If a friend does this, I will kick
41 | their butt, and will make them send me a link.
42 |
43 | Always ... always ... always ... Share the exact job link from their company's
44 | career page, and your resume. Most of these links, take them directly to the
45 | page, where they can refer you.
46 |
47 | To further your chances, add your name, location, email and phone-number to the
48 | message that you send to them. They need to fill these details on the referral
49 | page, and it's a pain looking for it in weirdly formatted resumes.
50 |
51 | Go with:
52 |
53 | ```
54 | Hi XXX,
55 |
56 | I am looking for a job/job change, and I was wondering will you be able to refer me to the following job opening in your company?https://careers..com/
57 |
58 | Further details:
59 |
60 | Name: string
61 |
62 | YOE: int
63 |
64 | Phone number: string
65 |
66 | Email address: string
67 |
68 | Current location: string
69 |
70 | Preferred locations: csv, or array of string (if applicable)
71 |
72 | I am attaching my resume with this message. Please inform me once you have referred, so that I can fill any additional details, or give my confirmation on the referral email, if needed.
73 |
74 |
75 | ```
76 |
77 | Some people insist on adding some personalized message, but I don't think it's
78 | really important, unless you are sending the message to a senior person. Most
79 | SWEs won't care, as far as they have enough information to refer you, within a
80 | few clicks.
81 |
82 | Also, use more standard, ATS-friendly resume templates. In most cases, HRs are
83 | even lazier, and they don't even go through weird looking fancy resumes, and
84 | rather pick someone else. Within 5-10 seconds of looking at your resume, one
85 | should be able to understand the following 2 things:
86 |
87 | Who you are?(Senior SWE @ , working on /,
88 | experienced in development/design/architecture), or some variant of it,
89 | that applies to you
90 |
91 | What kind of job you want to go for? Individual contributor / Managerial , etc
92 |
93 | They should only have to spend more than 5-10 seconds, if they want to know more
94 | about your projects, your graduation/school marks, or your hobbies. Most
95 | recruiters won't care.
96 |
97 | ---
98 |
99 | [`Source`](https://www.reddit.com/r/developersIndia/comments/vclqru/comment/icffcq0/)
100 |
101 |
102 |
103 | `u/fonderupp` shared the following advice on a now deleted post titled, [How do you properly ask for referrals?](https://www.reddit.com/r/developersIndia/comments/15w4bh8/how_do_you_properly_ask_for_referrals/)
104 |
105 |
106 |
107 | Here's my template:
108 |
109 | Hi {person name}.
110 |
111 | Hope you're doing great.
112 |
113 | I'm {my name}. I graduated from {college name since it is a good college, don't mention here if it's not that good} this year and I'm looking for Software Engineer opportunities. There's an opening at {company name} that I'm interested in. I would be grateful if you can refer me for the same. Here's the job: {job link}
114 |
115 | A little more about me: {point wise highlight your skills and notable achievements. this section is to show why you're a good fit aka why you should be considered}
116 |
117 | I am attaching my resume for your reference: {resume drive link so that people don't have to download}
118 |
119 | Thanks and warm regards
120 |
121 | **Results**
122 |
123 | Ofc there are people who just ignore messages, but overall I get a pretty good response rate. At least people go through my profile or say that they will check with HR and get back. Now it's also a factor that I'm from a good clg with huge alumni network so I mostly reach out to alums, if no alums then alums from sister colleges or similar level colleges.
124 |
125 | My template has a very clear format:
126 |
127 | 1. salutation
128 | 2. short introduction and what I'm asking for. if the reader is not interested, they will simply stop at this point, but at least they know what I was hoping to get from them
129 | 3. now if the reader did not leave, that means they want to know whether you're really good enough to be considered for the role. so here goes more descriptive section with skills and achievement.
130 | 4. again, if they are impressed by section 3, provide them the next step by sharing your resume
131 | 5. end with humble greetings
132 |
133 | ---
134 |
135 | [`Source`](https://www.reddit.com/r/developersIndia/comments/15w4bh8/comment/jwz128f)
136 |
137 |
138 |
139 | ## Related Discussions
140 |
141 | - [Why getting a referral is so hard?](https://www.reddit.com/r/developersIndia/comments/18tca0w/why_getting_a_referral_is_so_hard/).
142 | - [Why you should not refer anyone from Linkedin without knowing them!](https://www.reddit.com/r/developersIndia/comments/1av8rqt/why_you_should_not_refer_anyone_from_linkedin/).
143 |
--------------------------------------------------------------------------------
/src/faqs/switching-jobs/choosing-your-new-workplace.md:
--------------------------------------------------------------------------------
1 | # Choosing your new workplace
2 |
3 | ## Perspectives & advice from the community
4 |
5 | `@someguyguy.` on developersIndia discord shared the following advice on **How
6 | to evaluate if a good company is _good_**?
7 |
8 |
9 |
10 | 1. Check the product they are building, is it good enough? Do you feel it could
11 | be successful?
12 | 2. Checkout linked in profiles of co founders, senior tech and junior tech
13 | people as well? Also of other senior members. Are they good?
14 | 3. Check their funding? Which stage of funding are they in? Who are their
15 | investors? Check out their profile on crunchbase.
16 | 4. Are you interested in the industry they are working in? Is it
17 | exciting/interesting/innvoative/etc.?
18 | 5. What is their tech stack? What is the level of their backend infra? Are they
19 | using a custom built framework/library?
20 | 6. What is their interview process like? Too easy?
21 | 7. Check out their profile on glassdoor, how many bad reviews there are?
22 | 8. Try to connect on Linkedin with an ex employee and ask about their
23 | experience.
24 | 9. What are their coding practices? Do they write unit tests? Do they follow
25 | TDD? Do they have an in-depth code review process?
26 | 10. How many techies are there in the company relative to
27 | business/marketing/etc. people? Is the company focusing on creating an
28 | interesting tech product or just selling a subpar product?
29 | 11. Do their co founders have experience in starting companies? Where are those
30 | companies now? How long did they last?
31 | 12. Ask about their roadmap. What are they focusing on?
32 | 13. How much are they paying? How much are they paying senior tech
33 | people(checkout angel or job postings on other websites)? How much ESOPS do
34 | they give to junior/senior people?
35 | 14. Ask about their focus on work life balance.
36 | 15. What is their team size right now and how much would it be 6 months/1 year
37 | from now?
38 |
39 | Also be careful asking questions. I have seen some people who would not like
40 | someone joining their team asking about funding etc. The reality is that you
41 | would not be able to find answers to all of these questions but try to find as
42 | many as possible.
43 |
44 | No company would have positive answers on all of these. Find the ones which have
45 | good/great answers on most of these questions.
46 |
47 | ---
48 |
49 | [`Source`](https://discord.com/channels/669880381649977354/670198758343966740/813748050001788978)
50 |
51 |
52 |
--------------------------------------------------------------------------------
/src/faqs/switching-jobs/negotiating-notice-periods.md:
--------------------------------------------------------------------------------
1 | # Negotiating notice periods
2 |
3 | ## Perspectives & advice from the community
4 |
5 | `u/dedxtreme` on a post titled
6 | [Lied about my Notice period before interview now f\*\*ked](https://www.reddit.com/r/developersIndia/comments/1b875sd/lied_about_my_notice_period_before_interview_now/)
7 | shared the following advice:
8 |
9 |
10 |
11 | Tell the recruiter that you have a good working relationship with your current
12 | manager and that he’s requesting for 45-60 days to ensure smooth transition.
13 | Tell that he wanted to retain you with salary revision but you refused as you’ve
14 | decided to move on. So, out of kindness for his gesture you’d like to complete
15 | the transition the way he has requested.
16 |
17 | This shows that you’re definitely going to leave the current org and not stay
18 | back, you’re a nice person work with even when parting ways, and that you have a
19 | good work ethic that you put ppl first. The recruiter and more so the new hiring
20 | manager would appreciate this.
21 |
22 | This has helped me in the past when I wanted a couple of weeks of breathing time
23 | before I switch to a new org.
24 |
25 | ---
26 |
27 | [`Source`](https://www.reddit.com/r/developersIndia/comments/1b875sd/comment/ktpodj4/)
28 |
29 |
30 |
31 | `u/rajath_naik` on a post titled [People with 90 days notice period and no buyout how do you switch?](https://www.reddit.com/r/developersIndia/comments/1gccqao/people_with_90_days_notice_period_and_no_buyout/), shared the following advice:
32 |
33 |
34 |
35 | This usually works for me. First, Start applying to companies/responding to reschouts that you are okay to loose the offer from, sort of like test ground companies. This should be done from day one of interview prep. They'll usually help prepare you for the interviews and build some confidence. These companies should be easy to crack and won't take much effort. While doing so, tell them you have less than a month of notice and you are an immediate joiner. This will help with offer confirmation sooner.
36 |
37 | Second, the moment you get an offer from these companies, even if it's just one offer, you can drop papers. The reason to wait for this offer is sort of psychological and it's a huge confidence boost. Once you win one, you'll feel good and it'll act as a backup in the worst case possible. But you'll have to resist the urge to settle and always remind yourself to go back to preparation.
38 |
39 | Third, you keep giving interviews until you reach the list of companies that you actually want to join, sort of in a tier list of companies, going towards the top. This list can be personal based on WFH, Package, city etc.. Here, you don't want to lie. You put your 100%. Usually you would have reduced your notice period significantly by then, along with a few backup offers towards the end, where the notice you mentioned is not too drastic, than your actual notice. You don't have a chance to negotiate with your old company because they are in a lose position anyway. But you can definitely negotiate a week or 2 extension on your joining date with new company .
40 |
41 | Tldr: use the gap between joining dates of bad companies you don't want to join as a filler till your notice is close. Then apply to good companies.
42 |
43 | Note: this is not a hack towards your preparation. Nothing can discount preparation. This is just a hedge towards a rigged game of hiring.
44 |
45 | ---
46 |
47 | [`Source`](https://www.reddit.com/r/developersIndia/comments/1gccqao/comment/ltt9o2z/)
48 |
49 |
50 |
--------------------------------------------------------------------------------
/src/faqs/switching-jobs/negotiating-salaries.md:
--------------------------------------------------------------------------------
1 |
2 | # Negotiating Salaries
3 |
4 | - [Perspectives \& advice from the community](#perspectives--advice-from-the-community)
5 | - [Related Discussions](#related-discussions)
6 |
7 | ## Perspectives & advice from the community
8 |
9 | `@thecatclubpresident` on developersindia discord shared the following advice:
10 |
11 |
12 |
13 | I'll summarize for the people who don't want to go through 6k-7k words:
14 |
15 | 1. Don't think you're being immoral or your chances go down when you negotiate.
16 | The person hiring you cares very little compared to how much you care. He has
17 | a budget and an option to make a good choice. His job doesn't depend on
18 | making a good decision. Yours does so don't let him know that.
19 | 2. Hiring is a business and every good business means negotiation. ALWAYS
20 | negotiate. Ask yourself if being shy is worth losing out on lacs of money.
21 | It's closed as well: that interviewer isn't going to put up a video of you
22 | negotiating on youtube. NEVER SHY AWAY FROM NEGOTIATING
23 | 3. Always make sure the interviewer is interested in hiring you. If the job
24 | depends on you being cheap w.r.t. your salary, it is not a job worth having.
25 | If the job depends on your expertise mostly and not on your salary (as long
26 | as you're not adding or removing another zero), it is almost certainly a job
27 | worth having.
28 | 4. The usual process of job-hunting (go through some websites, apply on some
29 | then send the companies that look promising) is highly ineffective. Unless
30 | you are 10x better in some respect than all other potential candidates, you
31 | will almost certainly lose to nepotism. Use this fact for yourself. Pay
32 | someone to job hunt for you. Brokers aren't evil. Talk to them instead of
33 | talking to a thousand employers over a thousand mails. Brokers have more
34 | experience in this job than you ever will.
35 | 5. Resumes exist for the very reason that nobody needs to see them. While this
36 | might not always be true, the person hiring you will not see how well you
37 | present your resume or that abacus training program you took in 9th class.
38 | Send resumes without shame and to everyone.
39 | 6. MOST IMPORTANT POINT: Don't start with a number. It's a rookie mistake. If an
40 | employer asks for a previous number, give them a ballpark if you don't know
41 | how to make excuses. They are asking how low you were paid in your last job
42 | so that they can pay you less in the future. Talk about salary only after
43 | you've discussed all the other points of employment.
44 | 7. This ties back to point 6: once all the other points are decided and you've
45 | gone through all the necessary interviews WITHOUT NEGOTIATING SALARY, the
46 | employer will lose money if he doesn't hire you. He has spent weeks if not
47 | months trimming down on potential candidates. If he doesn't choose now, he'll
48 | have to spend that time and money again. Use this to negotiate a higher
49 | salary.
50 |
51 | ---
52 |
53 | [`Source`](https://discord.com/channels/669880381649977354/670198758343966740/681394827337662476)
54 |
55 |
56 |
57 | ## Related Discussions
58 |
59 | - [What Negotiation tactics you use for salary discussion with HR](https://www.reddit.com/r/developersIndia/comments/1f716gq/what_negotiation_tactics_you_use_for_salary/).
60 | - [Salary negotiation frameworks to keep in mind. (Credits to OPs in comments)](https://www.reddit.com/r/developersIndia/comments/yahbss/salary_negotiation_frameworks_to_keep_in_mind/).
61 | - [IT Professionals: How to Demand the Salary You Deserve](https://www.reddit.com/r/developersIndia/comments/1eh7t8p/it_professionals_how_to_demand_the_salary_you/).
62 |
--------------------------------------------------------------------------------
/src/faqs/switching-jobs/planning-for-resignation.md:
--------------------------------------------------------------------------------
1 | # Planning for resignation
2 |
3 | ## Perspectives & advice from the community
4 |
5 | `u/magnet_24` on a post titled
6 | [Resignation Reason Backfired](https://www.reddit.com/r/developersIndia/comments/15gwfph/resignation_reason_backfired/)
7 | shared the following advice:
8 |
9 |
10 |
11 | OP, just vomit out the below phrase word for word :
12 |
13 | "Unfortunately upon further introspection i have come to the conclusion that
14 | resigning would be the better trajectory for my career path."
15 |
16 | And, whatever they say after this, keep mum, answer in only "hmmms" and "i see"
17 | and stick to your decision. They may try to provocate, do not engage.
18 |
19 | And as a general rule of thumb, it rarely benefits to accept a counter offer.
20 |
21 | ---
22 |
23 | [`Source`](https://www.reddit.com/r/developersIndia/comments/15gwfph/comment/jul7so8/)
24 |
25 |
26 |
--------------------------------------------------------------------------------
/src/faqs/switching-jobs/rejecting-an-offer.md:
--------------------------------------------------------------------------------
1 | # Rejecting an offer
2 |
3 | ## Perspectives & advice from the community
4 |
5 | `u/Mindless-Pilot-Chef` on a post titled, [I accepted an offer but don't want to join](https://www.reddit.com/r/developersIndia/comments/taw6k8/i_accepted_an_offer_but_dont_want_to_join/)
6 | shared the following advice:
7 |
8 |
9 |
10 | Just drop a formal email/talk to the HR, something along these lines: Hey, thank
11 | you so much for offering me the job for the position X, but recently I have been
12 | made another offer which, after careful consideration, is what I will be going
13 | forward with. Therefore, I would like to forfeit the offer from your
14 | organization. This is purely because I feel that the other offer is more aligned
15 | with my short and long term career aspirations. I deeply regret any
16 | inconveniences my decision might cause.
17 |
18 | ---
19 |
20 | [`Source`](https://www.reddit.com/r/developersIndia/comments/taw6k8/comment/i03f5tu/)
21 |
22 |
23 |
24 | `u/simplehudga` on a post titled, [Best way to turndown the job offer after accepting it](https://www.reddit.com/r/developersIndia/comments/1atp7cg/best_way_to_turndown_the_job_offer_after/), shared the following advice:
25 |
26 |
27 |
28 | As someone who did this once many years ago. If I could go back, I won't do it again. It's a small world and even smaller industry. You don't want to be seen as unprofessional.
29 |
30 | If I had to do it again:
31 |
32 | - Accept that it's your mistake. I negotiated in bad faith knowing that I was going to get multiple offers. I didn't have to accept any of them but I didn't want to miss an opportunity. But that's the wrong way of looking at it.
33 | - Let them know as soon as possible. The more you delay it, the more painful it'll be. Do not wait until your joining date. Give them enough time to find someone else for the role.
34 | - Have an honest 1:1 conversation with the hiring manager before sending an email rejecting their offer. Convey it over a phone call at least if you can't say it in person. Then send them an email (cc recruiter, etc.) and reject the offer. Don't give any justification here. It should be short and simple. Don't go into any detail of where you're joining or reasons for rejecting.
35 | - Be thankful to them for the offer. They probably rejected other candidates to write you an offer. It'll probably take them many months to years to find another suitable candidate for the position.
36 | - Do not break any bridges. If they gave you an offer today, there's a high chance they'll give you an offer in the future, if you don't break the bridge.
37 | - Be ready to listen to a small lecture (depends on the hiring manager). But you can keep it short and end it on good terms.
38 |
39 | Finally, it's not the end of the world. It's not an ideal situation for any party involved. They'll find someone else, eventually. You might regret it in the long run. But everybody moves on.
40 |
41 | ---
42 |
43 | [`Source`](https://www.reddit.com/r/developersIndia/comments/1atp7cg/comment/kqzqisk/)
44 |
45 |
46 |
47 | `u/imaburneracc` on a now deleted post titled [What is the best way to reject offer after accepting?](https://www.reddit.com/r/developersIndia/comments/1d4yt3c/what_is_the_best_way_to_reject_offer_after/), shared the following advice:
48 |
49 |
50 |
51 | Be straight and direct. Be polite but firm. If you received some onboarding kit or materials, ask them how you can return them, document your messages and whatever the HR does. It could be that they'll be pissed since they are losing a candidate and make threats like blacklisting and stuff but don't bother and document it (in case they do something to jeapordize your new job) or they'd be understanding and you can part ways normally.
52 |
53 | In any case, don't feel guilty because a company won't think twice before removing you for their selfish reasons, and so don't succumb to the dilemma or any of HR's threats if they resort to that. Act in good faith, document their actions so if things go bad, you have ammo.
54 |
55 | ---
56 |
57 | [`Source`](https://www.reddit.com/r/developersIndia/comments/1d4yt3c/comment/l6hr9po/)
58 |
59 |
60 |
--------------------------------------------------------------------------------
/src/faqs/switching-jobs/service-based-to-product-based.md:
--------------------------------------------------------------------------------
1 |
2 | # Switch from Service based to product based organizations
3 |
4 | - [Perspectives \& advice from the community](#perspectives--advice-from-the-community)
5 | - [Stories from the community](#stories-from-the-community)
6 | - [Related Discussions](#related-discussions)
7 |
8 | ## Perspectives & advice from the community
9 |
10 | `u/funnythrone` on a post titled
11 | [How to switch from service to product based companies for non cs background people?](https://www.reddit.com/r/developersIndia/comments/mmxk4m/how_to_switch_from_service_to_product_based/)
12 | shared the following advice:
13 |
14 |
15 |
16 | Switching to a product company is possible, but definitely not an easy task as
17 | there are lot of people trying to get into product companies. I have listed
18 | below the things I did. Do take it with a lot of salt as what worked for me may
19 | not work for you. Also, an interview is dependent on a bit of luck, as most
20 | companies do not have an objective way of interviewing, so it is subjective to
21 | the interviewer.
22 |
23 | 1. Start with the basics, of data structures and algorithms. You should be able
24 | to implement the most basic data structures using nothing but arrays/Lists in
25 | your preferred programming language. And then you should be able to identify
26 | the time and space complexity of any algorithm/program using the big O
27 | notation. You should be familiar with the runtime complexities of well known
28 | algorithms, and why one algorithm might be better than another in certain
29 | situations despite big O complexity saying otherwise.
30 | 2. Practice writing code. Studying the basics without a practical implementation
31 | of it counts for nothing. I spent a lot of time on hackerrank and
32 | hackerearth. Participating in any programming challenge, especially the
33 | hiring challenges on hackerearth. Initially I wasn't even able to finish 1
34 | out of the 2 or 3 questions, but I soon reached a stage where I was being
35 | called for interviews.
36 | 3. Build something on your own from scratch to end. The finished product might
37 | be trivial, but if you do the work yourself, it will help you understand how
38 | to do it. It's okay to use libraries and frameworks, because let's face it,
39 | no one will ask you to build an application at work without using any
40 | library/framework.
41 | 4. Learn to communicate with others effectively. What this means is that you
42 | should be able to convey your thoughts to the opposite person using the least
43 | possible time. Like it or not, unless you are in the top 0.01% of engineers,
44 | you will have to work in a team and it involves communicating with your
45 | peers, juniors and seniors. A person with above average skill and excellent
46 | communication skill will be more preferable than a person with great tech
47 | skill but poor communication skill.
48 |
49 | ---
50 |
51 | [`Source`](https://www.reddit.com/r/developersIndia/comments/mmxk4m/comment/gtwf996/)
52 |
53 |
54 |
55 | ## Stories from the community
56 |
57 | - [Switched from Service Based to Product Based](https://www.reddit.com/r/developersIndia/comments/y4h2b0/switched_from_service_based_to_product_based/).
58 | - [My Journey From Service-Based To Product-Based Company](https://www.reddit.com/r/developersIndia/comments/1afb25r/my_journey_from_servicebased_to_productbased/).
59 | - [I cracked multiple product interviews after being unemployed for more than 3 years. Just elated and wanted to share the journey. Open to questions.](https://www.reddit.com/r/developersIndia/comments/swidtc/i_cracked_multiple_product_interviews_after_being/).
60 | - [Any of you who switched from service companies to product companies?](https://www.reddit.com/r/developersIndia/comments/106fctt/any_of_you_who_switched_from_service_companies_to/).
61 | - [WITCH to the product company with 1 year of exp.](https://www.reddit.com/r/developersIndia/comments/tugy3k/witch_to_the_product_company_with_1_year_of_exp/).
62 |
63 | ## Related Discussions
64 |
65 | - [Service-Based Companies Can Be Career Killers—Here’s My Experience](https://www.reddit.com/r/developersIndia/comments/1f1ukb2/servicebased_companies_can_be_career_killersheres/).
66 | - [Are Service Based Companies Really that Bad?](https://www.reddit.com/r/developersIndia/comments/srj01q/are_service_based_companies_really_that_bad/).
67 | - [Understanding the Position of Service Based Companies](https://www.reddit.com/r/developersIndia/comments/1bihx5e/understanding_the_position_of_service_based/).
68 |
--------------------------------------------------------------------------------
/src/faqs/switching-jobs/sharing-offer-letters-and-past-salaries.md:
--------------------------------------------------------------------------------
1 |
2 | # Sharing offer letters & past salaries with recruiters
3 |
4 | - [Perspectives \& advice from the community](#perspectives--advice-from-the-community)
5 | - [Related Discussions](#related-discussions)
6 |
7 | ## Perspectives & advice from the community
8 |
9 | `u/Lord_TrainBacker7000` on a post titled, [Is it okay for me to share my offer letter with a recruiter?](https://www.reddit.com/r/developersIndia/comments/v32lvo/is_it_okay_for_me_to_share_my_offer_letter_with_a/)
10 | shared the following advice:
11 |
12 |
13 |
14 | Hi Recruiter,
15 |
16 | The offer letter I have signed has a confidentiality clause and I would not be
17 | comfortable in sharing the same. I would be able to share the compensation
18 | breakup if that solves the purpose. (Or any other similar variation)
19 |
20 | Best regards,
21 |
22 | Your awesome self
23 |
24 | ---
25 |
26 | [`Source`](https://www.reddit.com/r/developersIndia/comments/v32lvo/comment/iaw284y/)
27 |
28 |
29 |
30 | `u/Infinitrix02` on a post titled, [I'm tired of being asked about my current and expected CTC](https://www.reddit.com/r/developersIndia/comments/qnvk1d/im_tired_of_being_asked_about_my_current_and/) shared the following advice:
31 |
32 |
33 |
34 | If a recruiter ever asks for your expected salary in the first call, say these
35 | lines:
36 |
37 | "Would it be alright if I told you my expected salary at the end stage of the
38 | interview?"
39 |
40 | Most the times the recruiters will comply with this. But in certain cases the
41 | recruiter will ask why. In that case, you should say this:
42 |
43 | "I believe that once I complete the interviews and ask some questions regarding
44 | the role as well, I will have a more accurate range to provide you with. Without
45 | proper knowledge of this role, I don't think it's fair for me to give a number
46 | that doesn't justify the role."
47 |
48 | Which is all bullshit. We already have a number in our mind. But still say these
49 | lines because by the time the salary negotiation stage arrives, the recruiters
50 | are in too deep to let you go (if you have performed well on the interviews).
51 | However, this doesn't mean that the company will give you any salary that you
52 | desire. There will be some negotiation for sure. Therefore make sure that you
53 | give a realistic number too.
54 |
55 | Finally, if the recruiters are still persistent and say something like:
56 | "Actually in order for me to present your profile to the management, I need some
57 | range or number." In these cases, give them a wide (and I mean extremely wide)
58 | range.
59 |
60 | Say you're earning 5 LPA right now, say something like 7 - 14 LPA.
61 |
62 | I don't earn 5LPA (yet) so I haven't tried out the last solution, but the first
63 | two have worked beautifully for me over the past year.
64 |
65 | ---
66 |
67 | [`Source`](https://www.reddit.com/r/developersIndia/comments/qnvk1d/comment/hjj0ybp/)
68 |
69 |
70 |
71 | `u/pablolit69` on a post titled, [Recruiter: What's your current CTC? How to respond?](https://www.reddit.com/r/developersIndia/comments/xhiz2b/recruiter_whats_your_current_ctc_how_to/)
72 | shared the following advice:
73 |
74 |
75 |
76 | Don't try to avoid them.
77 |
78 | Tell that you earn 5 LPA, and that you are expecting 10-12 LPA. It's not as rare
79 | as they will make it sound like.
80 |
81 | Let them stick to their script, you stick to yours.
82 |
83 | But yes, you can always decline to tell your expected CTC before the interviews.
84 | For that, you can say that you don't know their pay range, and your expectations
85 | will be according to that. If they can tell you the range, you can tell the
86 | expectation now. Else, it will take time for you to get an idea about how much
87 | their company pays
88 |
89 | At least that's what I do. If they insist, I always tell them that I do not have
90 | any fixed number in mind, and if they keep insisting, I get done with saying
91 | "industry standard hike". Later, after the interview, if they insist that the
92 | industry standard is 25%, I insist that for the role that I am applying to and
93 | based on the company, it's 100%. (Don't just say it, unless it's true)
94 |
95 | It's not that there's some official resource that they can quote, and tell me
96 | that I am wrong.
97 |
98 | Do tell them your current CTC, as it saves everyone some time. But keep the
99 | "expected CTC" part for later.
100 |
101 | ---
102 |
103 | [`Source`](https://www.reddit.com/r/developersIndia/comments/xhiz2b/comment/ioy1xia/)
104 |
105 |
106 |
107 | ## Related Discussions
108 |
109 | - [Is it fine to share the offer letter to another company?](https://www.reddit.com/r/developersIndia/comments/raudjn/is_it_fine_to_share_the_offer_letter_to_another/).
110 | - [Is it safe to share offer letter of one company to another?](https://www.reddit.com/r/developersIndia/comments/1g9c0dh/is_it_safe_to_share_offer_letter_of_one_company/).
111 | - [Never tell your current employer whom you are joining next](https://www.reddit.com/r/developersIndia/comments/1bto4f8/never_tell_your_current_employer_whom_you_are/).
112 |
--------------------------------------------------------------------------------
/src/faqs/tech-interviews.md:
--------------------------------------------------------------------------------
1 |
2 | # Preparing for tech interviews
3 |
4 | - [Prespectives \& advice from the community](#prespectives--advice-from-the-community)
5 | - [Related Discussions](#related-discussions)
6 |
7 | ## Prespectives & advice from the community
8 |
9 | `u/knucklehead_whizkid` on a post titled [What are untold tricks / folk knowledge about campus placements (apart from "practice Leetcode" and "read Cracking the Coding Interview")](https://www.reddit.com/r/developersIndia/comments/qiupil/what_are_untold_tricks_folk_knowledge_about/) shared the following advice:
10 |
11 |
12 |
13 | Lot of people here have given some great technical advice, let me offer a slightly non-technical component in addition.
14 |
15 | Disclaimer: these are based on my personal interview experiences (not a whole lot, I've only interviewed 3-4 times and have been working with the same company for ~7yrs now) and based on the candidates I've selected from campus interview myself.
16 |
17 | Confidence and intellectual honesty are key. Sure, you need to have a good technical knowledge base and coding skills, but communication is key and people who say it isn't haven't interviewed other people perhaps. You might have all the answers but if you aren't going to be able to convey your thoughts easily, having those answers isn't very useful.
18 |
19 | And by intellectual honesty, I mean that it's okay to bluff a bit on your resume n all but make sure you let your interviewer know if something isn't your cup of tea, don't go bootlicking and say you know xyz when you've just done a hello-world level thing in it. Eg: If you think that you don't know the exact solution for a problem, but an unoptimized one, start with it; and mention that hey this isn't the most optimum thingy but I'll start with this to build something that works and then optimize later on.
20 |
21 | I've seen a lot of candidates who are really smart but if they aren't going to communicate confidently (what they know and don't know) then they're hard to integrate in a team. On the other hand, a lot of candidates because they were more open to have engaging conversations, discuss different approaches and tangents to a problem have gotten selected despite not having exposure to some technology just because they were able to demonstrate their ability to learn.
22 |
23 | PS: This is essentially a verbose version of the "have an open conversation" tip below.
24 |
25 | ---
26 |
27 | [`Source`](https://www.reddit.com/r/developersIndia/comments/qiupil/comment/himagga/)
28 |
29 |
30 |
31 | `u/vaibhav-kaushal` shared following advice on how **open source development can help in cracking interviews**:
32 |
33 |
34 |
35 | TL;DR: Open Source development kick started my career despite being a college dropout and I think it is a great way to impress your interviewer.
36 |
37 | Hi everyone. I have been watching the posts at r/developersindia since at least two years. I do comment and partake in discussions as well using another ID. Before I proceed, let me first introduce myself.
38 |
39 | I am Vaibhav, a middle-aged (35+ yrs old) man working in the IT industry since 10+ years (but doing software development since more than 14 years now). I have been a FullStack (Web+Backend) + DevOps guy since the beginning but am mostly backend-heavy these days. In the past I have written for a few Tech Magazines which includes Digit, CHIP and Linux for You. I started the journey with the security domain so I do have some basic knowledge around that too. I have been one of the core developers of a PHP framework in the past (named QCubed) which has been used at NASA, Stanford School of Medicine and was the framework in which the world’s largest Chess community site (Chess.com) was originally written.
40 |
41 | Now, back to the point. One of the most (if not THE most) frequently asked questions on this sub is about how to get into a job (aka "how to crack the interview"). I have been taking interviews since the start of career (10+ years) and have been on both sides of the table. So I believe I am qualified to offer some insight into the process and offer help on this topic.
42 |
43 | Most people think Leetcode is THE DEFINITIVE ANSWER. Sorry to state but that's NOT TRUE. I have worked with a couple of guys who were champions in competitive coding and honestly they were bad with everything else and that's a huge problem. Now Leetcode (or similar sites) are useful in training your mind to think in better ways. They teach you to think in innovative ways and make you proficient in basics of DSA. But honestly, in my career so far I never had to write a merge sort or invert a tree; never.
44 |
45 | So what do people look for in candidates? Unless you are trying for MMAANG, where DSA skills is mostly a filtering mechanism, you don't need the god level expertise with DSA. What impresses me (and a lot of other guys taking interviews) is "experience".
46 |
47 | So now you must be thinking "but I need a job or at least a meaningful internship to get experience". And that's where most people, at least in my observation on this sub, are wrong.
48 |
49 | When we look for candidates, we look for people who can solve problems in innovative ways; people who have the ability to go deep into a subject and find out why a bug exists; someone who already knows how to handle git; a guy who knows that part of the job of writing the software is to read other people's code and understand why something was done in a certain way; someone who understands that documentation is pretty important. I expect him to know the basics of the environment where his code will work (browsers for FE, Kubernetes/Cloud/VM for BE) and so on, what it will interact with (REST APIs, gRPC, GraphQL, Auth mechanisms for FE and DB, Cache, Logging frameworks etc. for BE).
50 |
51 | NONE of that needs you to have an internship or job. If someone has put up a profile with some experience with an existing Open Source project or has built something cool that solves a real problem, it catches my eye. Regardless of other factors, the desire of me wanting to talk to him is pretty high.
52 |
53 | Now, if you built a Library management system (or something similar) using 10 files in Python, I am sure no one is using that and such software are already there. You have zero visibility into how many use-cases are lacking, what the real-world bugs are in the code and so on. It probably cannot handle enough traffic and is organised poorly. So basically I am looking for "meaningful work" - whether you contributed a small feature or fixed a bug in Kubernetes or made a Logging library which is super easy to integrate and use, you are experienced with the domain in a meaningful way. You
54 |
55 | - must have some insight into code organisation
56 | - must be knowing fundamentals of git
57 | - must be knowing how to structure to your code
58 | - must have decent communication skills
59 | - must have read through and understood basic documentation related to the subject
60 | - must be (very important) passionate about solving an existing problem
61 |
62 | All of this is "experience" that makes my life easy as a senior/lead developer. It tells me that you, as a junior/colleague, would not need hand holding on basic stuff and that I can count on you to understand the dozens of dependencies on existing codebase and its functionality. Of course it does not mean that you should skip on DSA or that DSA is useless! DSA is still very much required, although being a DSA god is not required for most things we do in the software world!
63 |
64 | ---
65 |
66 | [`Source`](https://www.reddit.com/r/developersIndia/comments/16cgfy7/the_nonleetcode_answer_to_how_do_i_crack_the/)
67 |
68 |
69 |
70 | ## Related Discussions
71 |
72 | - [My tips for interview in product companies in current environment.](https://www.reddit.com/r/developersIndia/comments/1ao43zj/my_tips_for_interview_in_product_companies_in/).
73 | - [Questions to ask in an interview as an interviewee](https://www.reddit.com/r/developersIndia/comments/v97dbf/questions_to_ask_in_an_interview_as_an_interviewee/).
74 | - [Why I think interviews are often flawed?](https://www.reddit.com/r/developersIndia/comments/197xupt/why_i_think_interviews_are_often_flawed/).
75 |
--------------------------------------------------------------------------------
/src/faqs/workplace-conundrums/README.md:
--------------------------------------------------------------------------------
1 | # Workplace Conundrums
2 |
3 | - [Dealing with micro management](./dealing-with-micromanagement.md)
4 | - [Dealing with toxic workplaces](./dealing-with-toxic-workplaces.md)
5 | - [Dealing with background verification (BGV)](./dealing-with-background-verification.md)
6 | - [Dealing with colleagues who steal credit for work](./dealing-with-colleagues-who-steal-credit.md)
7 |
--------------------------------------------------------------------------------
/src/faqs/workplace-conundrums/dealing-with-background-verification.md:
--------------------------------------------------------------------------------
1 |
2 | # Dealing with background verification (BGV)
3 |
4 | - [Perspectives \& advice from the community](#perspectives--advice-from-the-community)
5 | - [Related Discussions](#related-discussions)
6 | - [Stories from the community](#stories-from-the-community)
7 |
8 | ## Perspectives & advice from the community
9 |
10 | `u/_undefined_null_` shared the following advice on a post titled, [just another day at office. Toxic culture at its peak](https://www.reddit.com/r/developersIndia/comments/1cory3t/just_another_day_at_office_toxic_culture_at_its/).
11 |
12 |
13 |
14 | To all the people talking about BGV.
15 |
16 | Whenever I have left an org for toxicity reasons, I have always informed my next org, the reason for my leaving in detail, before joining the org. I have also told them, not to expect much good review in BGV or referral review, as things were not good in that org. I had even given few referral of my colleague whom they can connect to confirm the toxicity level.
17 |
18 | The only thing is, you need to be crystal clear with your next org about all this, before actually joining. IF they are ok with it, they will ask you to sign the offer letter. IF not, they will give some reason as to why the can't continue. IT's ok, there are lots of companies out there, who don't really care about your previous companies reviews as long as you are able to work efficiently and help them complete their projects. So meh. IT world is small, but not that small.
19 |
20 | Kudos to the person standing up and making the upper management know about the toxicity of the manager.
21 |
22 | ---
23 |
24 | [`Source`](https://www.reddit.com/r/developersIndia/comments/1cory3t/comment/l3jlzru/)
25 |
26 |
27 |
28 | `u/agathver` shared the following advice on a post titled, [Background Verification No Rehire Status- ( 3 years )](https://www.reddit.com/r/developersIndia/comments/1f29ota/background_verification_no_rehire_status_3_years/).
29 |
30 |
31 |
32 | Scare tactic. They can't do anything.
33 |
34 | BGV is mostly for compliance and employment record verifications. No one cares about internal statuses.
35 |
36 | BGV is like, "did this person with employment ID 123 work here from xyz date to abc date?", Yes/No
37 |
38 | Also, with good BGV providers, they also have an option to confirm employment details with alternate means if you do not want to provide them with a reference for verification, using a combination of PF account details, payslips and ITR.
39 |
40 | ---
41 |
42 | [`Source`](https://www.reddit.com/r/developersIndia/comments/1f29ota/comment/lk52acg/)
43 |
44 |
45 |
46 | ## Related Discussions
47 |
48 | - [If you are working in a startup, then be warned. Get the follow clearances as soon as possible.](https://www.reddit.com/r/developersIndia/comments/1d2ow0l/if_you_are_working_in_a_startup_then_be_warned/).
49 | - [How strict is BGV? I resigned before clearing the BGV and am scared](https://www.reddit.com/r/developersIndia/comments/13swt1f/how_strict_is_bgv_i_resigned_before_clearing_the/).
50 | - [BGV Address Verification Agent Asking Money. Will he be able to cause any issue?](https://www.reddit.com/r/developersIndia/comments/1cjyq8m/bgv_address_verification_agent_asking_money_will/).
51 | - [Never fake your experience certificate. Never lie. If caught, your IT life is lost.](https://www.reddit.com/r/developersIndia/comments/18gk54z/never_fake_your_experience_certificate_never_lie/).
52 | - [Does the third party bgv vendors verify your skill sets?](https://www.reddit.com/r/developersIndia/comments/1bflmi2/does_the_third_party_bgv_vendors_verify_your/).
53 | - [Absconded in 2021 due to health. Now BGV asks for docs](https://www.reddit.com/r/developersIndia/comments/1fw6car/absconded_in_2021_due_to_health_now_bgv_asks_for/).
54 | - [How can I prove my employment without a salary slip?](https://www.reddit.com/r/developersIndia/comments/15rj52s/how_can_i_prove_my_employment_without_a_salary/).
55 |
56 | ## Stories from the community
57 |
58 | - [Previous company messed up my BGV process. Now, my career is hanging in balance](https://www.reddit.com/r/developersIndia/comments/1d2n800/previous_company_messed_up_my_bgv_process_now_my/).
59 |
--------------------------------------------------------------------------------
/src/faqs/workplace-conundrums/dealing-with-toxic-workplaces.md:
--------------------------------------------------------------------------------
1 |
2 | # Dealing with toxic workplaces
3 |
4 | - [Perspectives \& advice from the community](#perspectives--advice-from-the-community)
5 | - [Related Discussions](#related-discussions)
6 |
7 | ## Perspectives & advice from the community
8 |
9 | `u/ForeverIntoTheLight` shared the following advice on a post titled, [Feeling Stuck in a Toxic Work Environment ! Scrum master always highlights us when some useless or extra task comes up!](https://www.reddit.com/r/developersIndia/comments/1f0w357/feeling_stuck_in_a_toxic_work_environment_scrum/).
10 |
11 |
12 |
13 | Your assessment that this is toxic is fully accurate.
14 |
15 | I have been in this position years ago, in a previous job. Multiple people dragging down the team as deadweight, yet paid more than me. Still, somehow it was my responsibility to ensure everything was done on time. Suffice to say, I suffered multiple health issues, and finally quit the company.
16 |
17 | So don't be an idiot like me. First ask yourself what you really want. Can you handle the extra work, without burning out, in return for more compensation? In that case, reach out to your manager and politely state that if you are to be a dedicated troubleshooter in addition to your regular duties, then you would like to be compensated proportionally to your new duties, during your next performance review.
18 |
19 | If you can't handle it? Well, your options are limited:
20 |
21 | 1. Talk to your manager, and explain that perhaps the team should have a round-robin system to handle extra / unforeseen / delayed work. This will spread the workload evenly across remaining devs, nobody will be pushed too hard continuously.
22 | 2. You're smart, seeing as how you've managed so far. Quietly slow down your progress, so as to complete just a little ahead of time. Alternatively, continue with your current pace of work, but keep your latest stuff in a private branch on your own machine (don't push to the central repo), and again adjust the commit date and push it just before the end, taking into account time needed for code reviews. If people ask why you're not finishing so much ahead of time, give them a nicely dressed explanation of all the complexities involved in your task (which you can understand and probably embellish far better than anyone else). Such an explanation will probably cause a short-circuit in the mind of this 'scrum master', and he'll shut up.
23 | 3. Look for a job elsewhere. Yes, I know, market's bad right now, but what do you have left to lose? No need to set OpenToWork on LinkedIn, just start quietly applying for various jobs.
24 |
25 | If your company does agree to reward you and then fails to live upto it, then again the last two options should come into play.
26 |
27 | As for the 'scrum master', just ignore his words. You are doing your work, and that of others. What exactly is he even contributing to the company? Let stray dogs bark - that's all they can do.
28 |
29 | ---
30 |
31 | [`Source`](https://www.reddit.com/r/developersIndia/comments/1f0w357/comment/ljuzc6v/)
32 |
33 |
34 | `u/MerakiPigeon` shared the following advice on a post titled, [Feeling Stuck in a Toxic Work Environment ! Scrum master always highlights us when some useless or extra task comes up!](https://www.reddit.com/r/developersIndia/comments/1f0w357/feeling_stuck_in_a_toxic_work_environment_scrum/).
35 |
36 |
37 |
38 | Firstly, welcome to the corporate world! I know it sucks, but more often than not, projects have large undocumented code bases, especially if it's an older project worked on by many developers over time. It's completely natural to feel overwhelmed and clueless when you are new to something, and more so because you are an intern. So you definitely shouldn't be doubting yourself, rather realign your approach.
39 |
40 | The best way is to take it one step at a time. Break the code base apart and understand one section at a time. When you get stuck, approach your team for help. In a healthy work culture, questions are always welcomed, even the (so called) silly ones. Don't hesitate to ask for help when needed, but only after you've tried your best.
41 |
42 | For the future, I would advise you to take a decision based on the following considerations
43 |
44 | 1. Talk to your manager about work pressure and see how they respond. If they continue to be unsupportive to your workload, you might be better off leaving a toxic work culture.
45 | 2. Does the technology you're working on interest you? Would the experience benefit your profile in the future, and would the T&Cs (bonds, etc.) be worth it?
46 |
47 | Hope these suggestions help! Good luck
48 |
49 | ---
50 |
51 | [`Source`](https://www.reddit.com/r/developersIndia/comments/14wyqa2/comment/jrkkv8u/)
52 |
53 |
54 |
55 | `u/headshot_to_liver` shared the following advice on a post titled, [How to become resilient to toxic work culture?](https://www.reddit.com/r/developersIndia/comments/1altowr/how_to_become_resilient_to_toxic_work_culture/).
56 |
57 |
58 |
59 | Not a veteran but have considerable experience so here are my 2 cents
60 |
61 | 1. Lay low, don't get into useless fights with seniors. Last thing you want is a reason to get fired.
62 | 2. Keep an eye out for any openings and networking is your best friend here. Just realise that people like you
63 | 3. Can't stress is enough, keep upskilling. Gramophone repairmen are not in demand today.
64 | 4. Don't go overboard with anything, be it work or delivery. Do what you're asked and that's it.
65 |
66 | ---
67 |
68 | [`Source`](https://www.reddit.com/r/developersIndia/comments/1altowr/comment/kph8ifn/)
69 |
70 |
71 |
72 | `u/Life-Appointment-877` shared the following advice on a post titled, [That's it I cried at my workplace! Need help and advice🙂](https://www.reddit.com/r/developersIndia/comments/1eiv9pe/thats_it_i_cried_at_my_workplace_need_help_and/).
73 |
74 |
75 |
76 | I have seen someone in a similar situation when I was interning somewhere. That guy is now a senior dev at a very good startup and earning a lot.
77 |
78 | I don't see your fault in it. A fresher will definitely follow what his tech lead says. I can help you with some tips you can follow:
79 |
80 | - whenever a task is given, and as you said the tech lead is very busy, you shouldn't rely only on him for guidance. Try to have connections with other dev in the team. At least junior devs who know the codebase and understand the issues in standup. You can always take help from them.
81 | - try to set up a regular meet with your tech lead. If he is very busy, try asking him if you will schedule a 15 min meet every alternate day.
82 | - make some friends other than your lead in the team( QAs, dev, PMs etc.). Initially never hesitate to ask for help from these people. People who know the ecosystem always help you. Try having lunch with them. Somehow be a corporate friend. They also understand you are fresher. They will help only if you ask them.
83 | - Don't be too stressed. Trust me once you understand the codebase and architecture, it will be very easy for you. It is not that difficult except in the beginning of a few months. Being good in a database is not that difficult. Only if someone understands his task, he can deliver it well. A surgeon cannot do a good surgery if he is not told the patient's body characteristics or disease. It's not the doctor's fault, it's the hospital's fault which didn't manage the patient's information well.
84 |
85 | Also, PMs are the dumbest people (no offense for PMs) in the team. Don't let their judgement affect you.
86 |
87 | ---
88 |
89 | [`Source`](https://www.reddit.com/r/developersIndia/comments/1eiv9pe/comment/lg9l9n1/)
90 |
91 |
