Anit Shrestha anitsh

MySQL

Getting started:

Collections

Resources

Project Title

One Paragraph of project description goes here

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

Prerequisites

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

Clarify and agree on the scope of the system

User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

General rules

Follow standard conventions.
Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
Boy scout rule. Leave the campground cleaner than you found it.
Always find root cause. Always look for the root cause of a problem.

	import torch
	from torch import nn
	from torch.autograd import Variable
	import torch.nn.functional as F
	import torch.optim as optim


	# toy feed-forward net
	class Net(nn.Module):
	def __init__(self):

	FROM golang:1.9

	WORKDIR /go/src/github.com/purplebooth/example
	COPY . .
	RUN go build -ldflags "-linkmode external -extldflags -static" -a main.go

	FROM scratch
	COPY --from=0 /go/src/github.com/purplebooth/example/main /main
	CMD ["/main"]


	class Node():
	"""A node class for A* Pathfinding"""

	def __init__(self, parent=None, position=None):
	self.parent = parent
	self.position = position

	self.g = 0
	self.h = 0