Posts
All the articles I've posted.
-
Real-Device Testing on App-in-Toss — Stuck on Direct Phone Connection, Solved with ait deploy
Starting the August vibe coding challenge, I tried real-device testing on App-in-Toss with my Galaxy Flip4 and only got 'A problem occurred while running the app.' I checked wifi, logs, and even TCP settings but couldn't fix it — turns out the whole approach was wrong. The answer was to build a bundle with `npx ait deploy` and send a test push.
-
Feature-by-Feature Study #2 — JWT Authentication: An Access Pass the Server Doesn't Remember
How JWT solves the weakness of the session approach (the server having to remember every session). Covers the structure that packs information into the token itself (header, payload, signature), the trap that the payload is just base64, not encryption, code for creating and verifying tokens with jjwt, and the new problem JWT introduces (no revocation).
-
Studying by Feature #1 — Session-Based Authentication: Why Doesn't HTTP Remember Me?
I decided to dig into features like login/auth, reservations, and payments one by one. The first topic is session-based authentication. Covers authN vs authZ, the fundamental problem caused by HTTP being stateless, how sessions work like a 'locker number tag,' Spring Security, why passwords are hashed with BCrypt, and the weaknesses of the session approach.
-
Learning by Building #1 — What I Missed in Designing an Ingredient-Filtered Recipe Feature
A feature where you input a recipe plus 'the ingredients I have', and it returns a cooking method that works with just those ingredients. Before implementing, I answered the design questions myself and got them evaluated. What I got right, 5 things I got wrong, 6 things I missed — name tags instead of indexes, revealing instead of blocking, combinatorial explosion, and the trap of AI-written tests.