-
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: added links to my website, and existing blog posts
- Loading branch information
1 parent
c89eed3
commit 3f6e71c
Showing
24 changed files
with
22,418 additions
and
13,199 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,7 @@ | ||
{ | ||
"typescript.tsdk": "node_modules/typescript/lib", | ||
"typescript.enablePromptUseWorkspaceTsdk": true | ||
"typescript.enablePromptUseWorkspaceTsdk": true, | ||
"workbench.colorCustomizations": { | ||
"titleBar.inactiveBackground": "#4e0380" | ||
} | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
<html> | ||
<head><title>404 Not Found</title></head> | ||
<body> | ||
<center><h1>404 Not Found</h1></center> | ||
<hr><center>nginx</center> | ||
</body> | ||
</html> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
{"markdown":3,"code":3,"features":3,"next-js":5,"math":1,"ols":1,"github":1,"guide":4,"tailwind":2,"holiday":1,"canada":1,"images":1,"writings":1,"book":1,"reflection":1,"multi-author":1,"feature":1} | ||
{"multi-author":2,"next-js":2,"feature":2} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,16 +1,12 @@ | ||
--- | ||
name: Tails Azimuth | ||
avatar: /static/images/avatar.png | ||
occupation: Professor of Atmospheric Science | ||
company: Stanford University | ||
email: address@yoursite.com | ||
twitter: https://twitter.com/Twitter | ||
linkedin: https://www.linkedin.com | ||
github: https://github.com | ||
name: Tanner Hallman | ||
avatar: /static/images/avatar.jpg | ||
occupation: Cofounder & CTO | ||
company: Coworks | ||
email: tanner.hallman@gmail.com | ||
twitter: https://twitter.com/tannerhallman | ||
linkedin: https://www.linkedin.com/in/tannerhallman | ||
github: https://github.com/tannerhallmab | ||
--- | ||
|
||
Tails Azimuth is a professor of atmospheric sciences at the Stanford AI Lab. His research interests includes complexity modelling of tailwinds, headwinds and crosswinds. | ||
|
||
He leads the clean energy group which develops 3D air pollution-climate models, writes differential equation solvers, and manufactures titanium plated air ballons. In his free time he bakes raspberry pi. | ||
|
||
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed neque elit, tristique placerat feugiat ac, facilisis vitae arcu. Proin eget egestas augue. Praesent ut sem nec arcu pellentesque aliquet. Duis dapibus diam vel metus tempus vulputate. | ||
Tanner is the CTO of Coworks, a startup that helps coworking spaces manage and automate their spaces. |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
--- | ||
title: The Art of Code Review | ||
date: 2021-05-02T13:50:52.438Z | ||
tags: ['multi-author', 'next-js', 'feature'] | ||
draft: false | ||
summary: 'Explore the importance of code reviews, best practices, and tools to ensure code quality in your projects.' | ||
--- | ||
|
||
Code review is the process of looking at the code that was written by someone else and offering feedback on it. It's a critical part of the software development process, and it's something that every software developer should take seriously. | ||
|
||
The goal of code review is to ensure that the code is as efficient and bug-free as possible. It's also a great way to learn from other developers and help each other improve our skills. | ||
|
||
When it comes to code review, there is an art to it. It's not just about finding bugs and suggesting improvements; it's also about helping the other person understand their code better. A good code reviewer can help the author understand why something isn’t working the way it should, or why a certain approach might be better. It’s a way of teaching and learning. | ||
|
||
So, what makes a good code reviewer? Here are some tips: | ||
|
||
1. Read the code. Take your time and read through the code thoroughly. Don’t just look for bugs; try to understand the logic and structure of the code. | ||
2. Ask questions. Asking questions is a great way to get a better understanding of the code. It also helps to ensure that your feedback is accurate and relevant. | ||
3. Be constructive. When giving feedback, focus on offering constructive criticism. Try to explain why something might not be the best approach and offer alternatives. | ||
4. Don’t be afraid to make mistakes. Recognize that mistakes will be made and that’s okay. The goal isn’t to be perfect. | ||
5. Help the author learn. Code review is a great opportunity to help the other person learn. Offer suggestions and explain why certain approaches might be better. | ||
|
||
Code review is an important part of the software development process. It takes time and effort, but it can be a great way to learn and help each other improve. With the right approach and attitude, code review can be an invaluable part of the process. |
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.