Sam Morgan sjmog

Misconception: "Parameter names and Argument names must be the same"

True or false: "parameter names and argument names must be the same"?

Play with the following examples: changing the names of the parameters and the arguments.

As always, try to have a hypothesis for what will happen before you make a change.

Link in

Explanation

New terminology

	/notes.txt
	# DevOps Notes – if you find this, I've gone feral

	---

	🟢 Day 1: Vision

	Clean setup. One instance. Node backend.
	"Firehose" service captures ride events and pushes them to Postgres.
	Event types: 'pickup', 'dropoff', 'cancelled', 'requested', maybe more.

	```python annotate
	# Import the PyTorch neural network module, which provides base classes and building blocks for neural network architectures.
	import torch.nn as nn

	# `torch` is needed for tensor operations, such as matmul and tensor reshaping, used later in the code.
	import torch

	# `F` is used for functional operations like softmax.
	import torch.nn.functional as F

	// An implementation of https://css-tricks.com/the-cleanest-trick-for-autogrowing-textareas/ in React

	import React, { useRef } from 'react'

	const AutoGrowingTextArea = props => {
	const grower = useRef(null);

	return(
	<div className="AutoGrowingTextArea" ref={grower}>
	<textarea

	# why do we do this?
	# (demonstrate working with the object and how nice it is)
	# (then talk about the idea of different "layers" in software and how we want each "layer" to be self-contained: Ruby in the MVC!)

	def self.create(url:, title:)
	return false unless is_url?(url)
	if ENV['ENVIRONMENT'] == 'test'
	connection = PG.connect(dbname: 'bookmark_manager_test')
	else
	connection = PG.connect(dbname: 'bookmark_manager')