Clients
Services
Blog
Contact
How we work
Guidelines on our approach to working
Search Book
⌘K
to navigate
Enter
to select
Esc
to close
1.
Introduction
2.
Be in Thought Zone
Where should I go to get work done
Maker's time vs Manager's time
Being in thought zone
Asynchronous communication is key to getting work done
3.
Working Remotely
4.
Thank you for reading!
5.
Write blog using ventilated prose style
6.
Use we
7.
Do not use foo, bar & baz
8.
Configure Command Prompt
Custom Command Prompt for bash users
9.
Use autosetuprebase
10.
How We Use Services & Carriers
11.
Trust data
12.
Do not use "or" & "and" in Ruby
13.
Use underscore prefix for memoization
14.
Do not leave action implementation blank
15.
Fully spell out variable names
16.
Variable names should match with domain
17.
FIXME and TODO
18.
Use self to declare class methods
19.
Prefer do end while creating blocks in ruby
20.
Prefer no trailing if for multiline code
21.
Oliver & Eve
22.
Organizing controllers
23.
Prefer using attr_readers, attr_writers
24.
Empty line after the import statements
25.
Empty line at the end of the file is not needed
26.
Have meaningful name in tests
27.
Running tests
28.
External services
CircleCI for React Native testing
Semaphore CI for running minitest
Heroku
S3
Honeybadger
DNSMadeEasy
Cross Browser Testing
UptimeRobot for monitoring
29.
Creating an issue in github
30.
How to find all issues assigned to me
31.
Prefer github over slack for communicating
32.
Create branch starting with issue number
33.
Do not mention issue number in the title of PR
34.
PR should mention fixes or closes issue number
35.
How to Rebase a pull request
36.
Pull requests are merged in master
37.
Hit y before copying url from github
38.
Take screenshot with the URL
39.
Epic Tag
What is an epic issue?
How to work with an epic issue?
40.
Copy production data to staging
41.
Download staging data to local machine