JavaScript enthusiast, web developer.
Joined August 2010
- Tweets 3,243
- Following 1,335
- Followers 657
- Likes 191
21 Photos and videos
Pinned Tweet
23 Aug 2019
#javascriptchallenge #javascript 18th and counting, crafted by me. Embrace the language much more confidently :-)
github.com/yeungon/In-JavaSc…
1
Vuong Nguyen retweeted
May 15
49
132
1,037
7,722,138
Mar 8
Lesson learnt
1
129
Vuong Nguyen retweeted
31 Dec 2025
For people asking what to build to really learn Go, here’s a progression that maps well to how Go actually teaches you pragmatic systems thinking, concurrency, and production discipline.
---
Simple (start here, learn fundamentals & clarity)
1. Build a CLI tool (flag parsing, file I/O, error handling)
2. Build a log processor (bufio, streaming, memory efficiency)
3. Build a small HTTP client (net/http, retries, timeouts)
4. Build a basic HTTP server (handlers, middleware, context)
5. Build an in-memory cache (maps, mutexes, TTL)
6. Build a file watcher (fsnotify, goroutines, channels)
7. Build a config loader (env vars, YAML/JSON, validation)
8. Build a worker pool (goroutines, channels, backpressure)
---
Medium (where Go’s concurrency model clicks)
9. Build a REST API service (routing, middleware, graceful shutdown)
10. Build a job queue (channels vs persistent queues, retries)
11. Build a rate limiter (token bucket, leaky bucket)
12. Build a reverse proxy (net/http, connection reuse)
13. Build a metrics exporter (Prometheus client, counters, histograms)
14. Build a scheduler (cron-style, timers, cancellation)
15. Build a simple key-value store (files, WAL concepts)
16. Build an auth service (JWT, middleware, context propagation)
17. Build a search service (inverted index, concurrency-safe reads)
---
Hard (production-grade Go & systems depth)
18. Build a high-throughput TCP server (epoll-style patterns, pooling)
19. Build a distributed worker system (leader election, coordination)
20. Build a sharded cache (hashing, consistency trade-offs)
21. Build a Raft-based service (state machines, persistence)
22. Build a storage engine (indexes, compaction, snapshots)
23. Build a streaming pipeline (fan-in, fan-out, backpressure)
24. Build a custom protocol (binary framing, versioning)
25. Build a service mesh sidecar (proxies, retries, observability)
26. Build a full backend platform (API, async jobs, caching, metrics)
---
You learn Go by:
- Designing simple APIs
- Handling failure explicitly
- Respecting concurrency costs
- Writing code others can read at 3am
If your code feels boring, obvious, and stable then believe me, you’re doing it right.
31 Dec 2025
For people asking what to build to really learn Rust, here’s a progression that maps well to how Rust actually teaches you systems thinking.
Simple (start here, learn ownership & basics)
1. Build a CLI tool (argument parsing, file I/O, error handling)
2. Build a log parser (iterators, lifetimes, zero-copy parsing)
3. Build a small HTTP client (reqwest async basics)
4. Build a basic TCP server (std::net, threading)
5. Build an LRU cache (HashMap linked list, ownership pain included)
6. Build a file watcher (inotify-style logic, channels)
7. Build a config loader (serde, enums, validation)
8. Build a simple thread pool (Mutex, Arc, Condvar)
---
Medium (where Rust really clicks better)
9. Build an async web server (tokio, hyper, backpressure)
10. Build a key-value store (LSM-style, WAL, file layouts)
11. Build a job scheduler (work queues, cancellation, timeouts)
12. Build a reverse proxy (async I/O, connection pooling)
13. Build a mini database index (B-tree or skip list)
14. Build a parser AST (nom or handwritten parser)
15. Build a WASM runtime toy (wasmtime concepts)
16. Build an auth service (JWT, crypto crates, zero-copy serialization)
17. Build a search engine (inverted index, mmap, ranking)
---
Hard (deep Rust systems mastery)
18. Build a memory allocator (unsafe, layout, alignment)
19. Build a container runtime (namespaces, cgroups concepts)
20. Build a distributed cache (networking, consistency trade-offs)
21. Build a Raft implementation (ownership state machines)
22. Build a storage engine (MVCC, snapshots, compaction)
23. Build a network protocol (custom framing, async streams)
24. Build a compiler backend (IR, borrow checker inspiration)
25. Build an OS kernel module or toy kernel (no_std, bare metal)
26. Build a database from scratch (query planner execution engine)
---
Rust rewards building, not watching tutorials. So keep building too.
Each project forces you to confront ownership, lifetimes, concurrency, and performance head-on.
If it hurts a little(especially those borrow checkers errors), you’re doing it right.
10
55
490
50,330
11 Sep 2025
New toy to replace sluggish n8n.
10 Sep 2025
Announcing Genkit Go 1.0 ✨
The SDK is now stable and production-ready. This release introduces the genkit init:ai-tools command for seamless integration with AI coding tools, plus built-in support for tool calling, RAG, and more.
Read the blog →goo.gle/3Kep4D6
ALT An announcement graphic that reads "Genkit Go is ready for production use (with Gopher)" with the Go mascot, the Gopher, in the corner.
ALT An infographic on a dark background with green text boxes. The top box describes "Type-safe AI flows with Go structs and JSON schema validation." The bottom box highlights a "Unified model interface supporting Google AI, Vertex AI, OpenAI, Ollama, and more." A large green opening curly brace { is on the left side of the graphic.
ALT An infographic with a dark background and orange text boxes. The top box says "Tool calling, RAG, and multimodal support." The bottom box says "Rich local development tools with a standalone CLI binary and Developer UI." Between them are icons of a laptop, an oval, and a puzzle piece.
ALT A dark background graphic with a red text box at the top stating, "Try our AI coding assistant integration in Gemini CLI by entering." Below it is a pink box with the command genkit init:ai-tools. To the left is a large pink semicolon icon, and to the right is the light blue Go Gopher mascot looking at the command.
338
17 Sep 2023
Bun 1.0 means it is stable and production ready.
8 Sep 2023
Introducing Bun v1.0 - a fast, all-in-one toolkit for running, building, and testing JavaScript and TypeScript
bun.sh/blog/bun-v1.0
887
10 Mar 2023
Good stuff comes late :)
8 Mar 2023
✍️ Announcing writeout.ai – transcribe and translate any audio files!
10 languages available (including Klingon 🤓)
It's entirely free AND open source.
writeout.ai
936
7 Jan 2023
Show your largest number of tabs opened on a browser and tell your friends you are a programmer :)). Mine, currently is 489 :))
490
2 Jan 2023
It happens again. Idea comes and I then buy a domain without any hesitation. Can believe some other domains in the dashboard are gonna expire pretty soon. Idea comes and goes. Anyway, cannot stop building stuff or at least thinking about them, once you are a developer.
301
30 Dec 2022
You might not care but FYI Promise is eager and Observable is lazy. You might write console.log inside promise object. #javascript
211
23 Dec 2022
Is everything object in JavaScript ? I made this video to answer this question. #javascript
youtube.com/watch?v=8PIvrHL4…
296
21 Dec 2022
I make a new video about the ways (5 ones!) to create object in #javascript
youtube.com/watch?v=eZH8aIbH…
2
245
19 Dec 2022
Back to basic, I record video about JavaScript after 2 years youtube.com/watch?v=WNr5Vfeq…
191
18 Dec 2022
Goodye useEffect. Must watch video for React dev.
18 Dec 2022
I'd argue that this @DavidKPiano presentation is a must-watch for React devs.
Realistically, I think all React devs struggle with the useEffect hook, and as @dan_abramov reminds us, the mental model is synchronization, not lifecycle.
youtube.com/watch?v=bGzanfKV…
1
180
17 Dec 2022
Feel like much better/deeper than reading some random tutorials elsewhere.
142
12 Dec 2022
pseudo code pretended as a normal gate of
authentication. so if someone can read the code and "activate" it, then they can build the application by them-self.
1
12 Dec 2022
the code is tedious to read but not really hard to understand for a seasoned dev.