Pascal (@paschals_robert) header
Pascal (@paschals_robert) profile picture

Full-stack engineer building https://teapawt.org/t.co/Nsd77USNDo Substack publication: https://teapawt.org/t.co/GTqCQdQBYw Drop a follow

/etc/init.d
Joined March 2022
Photo by Pascal (@paschals_robert)Photo by Pascal (@paschals_robert)Photo by Pascal (@paschals_robert)Photo by Pascal (@paschals_robert)Photo by Pascal (@paschals_robert)Photo by Pascal (@paschals_robert)Photo by Pascal (@paschals_robert)Photo by Pascal (@paschals_robert)Photo by Pascal (@paschals_robert)
heypascal.me is LIVE. My home on the internet. Months of building, rewriting, second-guessing every pixel. Full-stack engineer, founder, writer — one site, whole picture. If you've got something to build — an API, an AWS setup, a document workflow — the work-with-me section has real prices and a direct way to start. No pitch deck required. Here's what I built and what it cost me 🧵
2
3
19
1,306
A rate limit is not a punishment for using the API too much. It is the part of the design that says how much the system can honestly do, and it says it before the system falls over instead of after.
1
15
The limit protects both sides. It protects my system from one client taking everything, and it protects the client from building on a throughput I cannot keep. Say the number out loud before launch, not after the first outage.
1
14
Follow along if you build APIs other people depend on. I write about the backend decisions that only show up when real traffic arrives.
1
1
14
A test that passes on your machine and fails in CI is not a flaky test, it is a test that depends on something you did not write down. The timezone on your laptop. The order the tests ran in. A file that exists in your folder and not in the repo.
1
14
The suite is only as honest as its worst test. One test that passes by accident teaches the team to ignore failures, and a team that ignores failures has no test suite at all, just a green badge.
1
6
Follow along if your tests pass locally and fail everywhere else. I write about building backends that behave the same wherever they run.
7
1/ Every codebase has a flag that was supposed to be temporary. It shipped the new checkout, or the new pricing page, and the flag stayed on because removing it felt like extra work nobody had time for.
2
1
15
6/ If a flag cannot be removed, that is the real bug, and the fix is removing the branch, not guarding it forever.
1
8
7/ Follow along if your codebase has flags nobody remembers adding. I write about the backend habits that keep small systems understandable.
7
A project moves to its next phase when the question it has to answer changes. Phase one asks: does it work? Phase two asks: does it hold up when someone else touches it?
1
11
The phase change is a decision, not a date. What question is your project answering right now: does it work, or does it hold up? Next: Seeking clarity.
1
6