Chad Rhonan Stewart chadstewart

Setup a Node.js project with Typescript, ESLint, Prettier, Husky

Starting a personal node project could be easy; starting a team node project could be challenging.

I am a developer currently working in SEEK Australia.

In my experience, common mistakes developer make when starting a projects are:

No Linting

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Run tsx in VSCode Debugger",
      "type": "node",
      "request": "launch",
      "runtimeExecutable": "node",
 "runtimeArgs": ["--loader", "tsx"],

What is the company vision?
What is your passion with/about the company/your role?
What is the company culture?
How did you get into this role?
What keeps you up at night about this role?
Are there plans to extend the team?
What is the ratio of front end to back end developers?
Walk me through the decision-making process.
What have you learned from people in roles beneath yours?
What have you learned form older/younger developers?

Speaker Rider

by Tatiana Mac

Last updated 14 April 2021

What is a speaker rider?

As speaking comes with immense privilege, I have crafted a speaker rider to set expectations and boundaries around my engagement. I am grateful to all the conference organisers who have brilliantly hosted me. I would love to continue to exercise this privilege to speak at conferences, and use this privilege to make the landscape more accessible and beneficial to tech's most historically excluded and marginalised communities.

Considerations

😫 I provide a lot of explanations for those of you who never had to consider these things. Most thoughtful conferences I've attended check most of these boxes intrinsically, particularly when conference runners are experienced speakers. They get it.

	def is_valid_state(state):
	# check if it is a valid solution
	return True

	def get_candidates(state):
	return []

	def search(state, solutions):
	if is_valid_state(state):
	solutions.append(state.copy())