Skip to content

Commit 4e7e4eb

Browse files
committed
content complete, time to edit
1 parent b830a23 commit 4e7e4eb

File tree

3 files changed

+46
-1
lines changed

3 files changed

+46
-1
lines changed

lessons/01-the-first-section/B-my-setup.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,14 @@ I _think_ this course would work with recent versions of [bun][bun] but it's unt
2727
- [Starship Prompt][starship] – Very cool prompt that's just pretty. Also shows you what sort of project you're in which is occasionally useful
2828
- [CaskaydiaCove Nerd Font][nerd] – This works with Starship prompt to give you the JS logos and all those extra glyphs. It's based on Cascadia Code.
2929

30+
## A note on the use of AI in this course
31+
32+
This course was written by me. I used AI in a few places for assistance, but every piece of code and every line of text on this site was written by me. The only places that it's actually AI written directly are the example rows of the database and the sample markdown - just filler content that I prompted Claude for. I do let OpenAI write all the SEO for these webpages (like all the OpenGraph keywords and descriptions.)
33+
34+
My stance on AI is two-fold. In the hands of an experieced wielder AI is incredibly powerful. When I say experienced, I mean it in two ways: 1. experienced in writing the sort of code they're prompting for and 2. experienced in the usage of how to prompt and use AI well. In our case, AI will allow you to amplify the rate you can write React code, but that's only possible if you understand React. Sure, you can "vibe" code React with a very shallow understanding, but you're going to build tall houses of cards. You'll be better served by turning off the AI and handwriting code, understanding each precept, and then using that knowledge to co-write solid React with your AI toolkit.
35+
36+
Do I use AI? Yes, it helps me work faster. But like a manager reviewing their interns' code, I am responsible for what I decide to ship, and so I keep a tight rein on it.
37+
3038
[ligatures]: https://worldofzero.com/posts/enable-font-ligatures-vscode/
3139
[monolisa]: https://www.monolisa.dev/
3240
[vscode-icons]: https://marketplace.visualstudio.com/items?itemName=vscode-icons-team.vscode-icons
Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,13 @@
1-
Hi React 19.
1+
Let's talk about [React 19][19].
2+
3+
It came out at the tail end of 2024 officially but really had publicly been worked on [since late 2022][rfc]. So it's been worked nearly 3 years and been stable and in production (via Next.js as well as internally at Facebook) since [late 2023][next].
4+
5+
All of this to say: it's fairly new to _stable_ React but it's been worked on and shipped via "unstable" channels for nearly 2+ years. We've had a lot of time to learn some good and bad patterns, and it's going to be fun to learn them together with you.
6+
7+
Primarily we are going to concern ourselves with React Server Components. This is a new way of writing React components that allows your React components to render partially on the server and then to be served in a client side app in React. It's very cool; it allows you to do things like safely directly query your database from within React, something we couldn't (or at least shouldn't) do previously.
8+
9+
The Complete Intro course does some minor cover of version 19 features and the good news is nothing changed in what I taught - everything I taught stayed stable so no corrections since version was released after v9 of my intro course!
10+
11+
[19]: https://react.dev/blog/2024/12/05/react-19
12+
[rfc]: https://github.com/reactjs/rfcs/pull/188
13+
[next]: https://nextjs.org/blog/next-14

lessons/09-wrap-up/A-congrats.md

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,28 @@
11
---
22
title: "Congrats!"
33
---
4+
5+
🎉 You did it! 🎉
6+
7+
Congrats, this is a lot of info all at once, but you can call yourself well equipped to take on any problem with React, server-side or not!
8+
9+
So where do you go from here? Well, here's some fun ideas:
10+
11+
- Take your favorite app here (maybe the Next.js one) and deploy it to a service. [Vercel][vercel] is particularly well equipped for Next.js apps
12+
- Take your database to the cloud! I'm obviously biased towards [Neon][neon] but any cloud database will work. I actually manage the integration between Vercel and Neon!
13+
- Add more features to your note passing app.
14+
- Add real auth. [Neon Auth][auth] or [Clerk][clerk] would be two great options so you can actually have real users.
15+
- Make it into more of a Twitter feed so you can follow people and post general notes, not just direct messages.
16+
- Add an admin feature that allows the teacher to remove or edit notes.
17+
- Use something like Llama locally or Claude/ChatGPT to add a summary ability so you feed in all of a user's notes and get back a summary of the notes they've received
18+
19+
Let me know what you build! Tweet/post at me on [𝕏][x] or [Bluesky][bs]!
20+
21+
Thank you and go build cool shit!
22+
23+
[vercel]: https://www.vercel.com
24+
[neon]: https://neon.tech
25+
[clerk]: https://www.clerk.com
26+
[auth]: https://neon.tech/docs/guides/neon-auth
27+
[x]: https://twitter.com/holtbt
28+
[bs]: https://bsky.app/profile/brianholt.me

0 commit comments

Comments
 (0)