• Where to find the team documentation?
• Team practices documentation
• User definition, use cases, requirements
• Where is the documentation to build projects?
• One step build process
• Access to CI/CD
• Access to git central repository
• Access to slack
• Installation of development tools/languages
• Where to find the tasks being worked on?
• Where to find the team roadmap?
• Who prioritizes things?
• Determine where I can have the biggest impact
• Determine a timeline where I'll have reached my 80/20 at the company
• What is the maturity of existing projects?
• How fast can we iterate on certain aspects given the team/company composition?
• Who are the core/principal/staff contributors?
• What is the architecture of the system?
• What is the database architecture?
• Is it a monolith or micro-services?
• What (3rd party) tools are used?

Notice/Advisory: I am not an accountant nor a day trader. The following is not advice, only notes I've taken for myself. Content may be wrong or inaccurate. Use at your own risk.

The following is a list of items and things to think about if you would like to be a day trader. I wrote it with the intent of identifying what were the requirements to be a day trader and what would be the impacts of being considered as one vs being an investor.

• Basics
  • Computer or phone
  • Internet
  • Broker
  • Money
• Do not do day trading in your TFSA/RRSP/RESP accounts
• Your gains/losses will either be categorized as capital gains (50% taxable) or business income (100% taxable) based on how you trade. In any case, since this is a day trading article, you can assume this will be business income. Here are some properties taken into account
  • Volume and frequency of trading
  • Length of ownership of securities
  • Type of securities owned
  • Your profession and level of stock market knowledge
  • If trading is your main source of income or substantially supplements it
    • Here it is not clear what substantially represents. I would estimate that anything below 25% of your non-trading income isn't substantial.
• If you want to day trade, you will want to have access to level 2 data, which costs money depending on your broker
  • Some brokers will reimburse your data package fees if you spend a certain amount of money on commissions each month. For example, Questrade data package will cost you 90$/month, but if you spend over 400$ on commissions this fee will be rebated.
• You do not need to register with the government or any agency
• You do not need a minimal amount of money, although it is suggested to have a few thousands dollars otherwise you will not make a lot of profit daily and your commissions fees are likely to eat any profit you will make
  • Some brokers have minimum account balance
• You have a trading strategy
• Track your transactions
  • Time of entry/exit
  • Cost at entry/exit
  • Symbol/Ticker

References

• https://investingbasics.ca/guides/day-trading/#2--how-to-start-day-trading-
• https://www.wealthsimple.com/en-ca/learn/how-to-start-day-trading

• Decide what habit you want to have and record why you want this habit
• Start with the smallest amount of effort possible
• Increase the amount of effort regularly until you reach the desired amount of regular effort
• Track your habit in a habit recording system such as Loop Habit Tracker
• Review on a regular basis (monthly) whether you want to keep this habit or not
  • If you decide not to keep the habit, record why you decided to drop the habit such that if you decide to pick it up again, you can determine whether you might end up dropping it again.
• It's not a problem if you miss doing your habit, just make sure to do it when you're supposed to

• List all the features you would like to develop
• Define an appetite for the task (day, week, month, quarter)
• Identify the features where the appetite differs between individuals and discuss them to reach consensus
• Define the roles necessary to complete the task
• Identify dependencies between features
• Categorize the dependencies
  • Soft: somewhat depends on this other feature but isn't blocked by its absence from the codebase
  • Hard: depends on this other feature and is blocked by its absence from the codebase
• Prioritize the features
  • Use the RICE framework
  • Priority can also be skipped if using ROI as prioritization metric
• Estimate the value of a features in dollars
• Calculate a ROI (return on investment) as the estimated value of the feature divided by the defined appetite
• Order tasks according to dependencies and ROI

• Do you understand what is at stake?
• Do you know what already exists?
• Can you take an informed decision?
• What did you consider during your decision?
• What are your unknowns (things you'd need to know before your can make a decision)?

• Do you have experience with the problem which needs a decision?

• Indicate who has the most expertise to make the decision

• You should be allowed to cast a vote if the decision will impact you. If it doesn't (i.e., you're not a stakeholder), your vote will not be counted towards any option