No posts by ElenChen

@ElenChen

Elen Chen

Cloud Architect & Systems nerd turning caffeine into scalable microservices. Cur...
Joined April 2026
516 Points14 Badges4 Connections4 Followers7 Following

Comments by ElenChen

3 days Articles 11 min read
I've seen this file in almost every frontend project I've ever touched. It's usually called api.js or utils.js or sometimes just helpers.ts. It starts small. One function. Two functions. Then, six months later, it's 800 lines long, nobody fully un...
post-cover-20049
3 days Articles 11 min read
I've seen this file in almost every frontend project I've ever touched. It's usually called api.js or utils.js or sometimes just helpers.ts. It starts small. One function. Two functions. Then, six months later, it's 800 lines long, nobody fully un...
post-cover-20049
Jun 3 Articles 10 min read
It was a Thursday afternoon when the Teams message came in. A bug in production. A date formatting issue causing checkout to fail for users in certain timezones. Small bug, real impact: the payment flow was broken for roughly 8% of users. The fix t...
post-cover-17843
May 28 Articles 10 min read
I was doing a code review for a colleague when I found it. The component had five useEffect hooks. No errors. No warnings in the console. The PM had signed off on it. It had been in production for three months. But there was a subtle bug that o...
post-cover-17844
May 28 Articles 10 min read
I was doing a code review for a colleague when I found it. The component had five useEffect hooks. No errors. No warnings in the console. The PM had signed off on it. It had been in production for three months. But there was a subtle bug that o...
post-cover-17844
May 28 Articles 10 min read
I was doing a code review for a colleague when I found it. The component had five useEffect hooks. No errors. No warnings in the console. The PM had signed off on it. It had been in production for three months. But there was a subtle bug that o...
post-cover-17844
May 28 Articles 10 min read
I was doing a code review for a colleague when I found it. The component had five useEffect hooks. No errors. No warnings in the console. The PM had signed off on it. It had been in production for three months. But there was a subtle bug that o...
post-cover-17844
May 28 Articles 10 min read
I was doing a code review for a colleague when I found it. The component had five useEffect hooks. No errors. No warnings in the console. The PM had signed off on it. It had been in production for three months. But there was a subtle bug that o...
post-cover-17844
May 28 Articles 10 min read
I was doing a code review for a colleague when I found it. The component had five useEffect hooks. No errors. No warnings in the console. The PM had signed off on it. It had been in production for three months. But there was a subtle bug that o...
post-cover-17844
May 28 Articles 10 min read
I was doing a code review for a colleague when I found it. The component had five useEffect hooks. No errors. No warnings in the console. The PM had signed off on it. It had been in production for three months. But there was a subtle bug that o...
post-cover-17844
May 14 Articles 5 min read
A few months ago, we had to change a small piece of logic. It sounded simple. A minor tweak. “Shouldn’t take more than a couple of hours.” Then someone asked: > “Do we know how this actually works?” Silence. No one on the team had written that p...
post-cover-17831
May 14 Articles 5 min read
A few months ago, we had to change a small piece of logic. It sounded simple. A minor tweak. “Shouldn’t take more than a couple of hours.” Then someone asked: > “Do we know how this actually works?” Silence. No one on the team had written that p...
post-cover-17831
May 14 Articles 5 min read
A few months ago, we had to change a small piece of logic. It sounded simple. A minor tweak. “Shouldn’t take more than a couple of hours.” Then someone asked: > “Do we know how this actually works?” Silence. No one on the team had written that p...
post-cover-17831
Apr 22 Articles 4 min read
A while ago, I opened a file and immediately knew something was off. Not because it was broken. Not because it was complex. But because it had that shape. You know the one: if ... { // something } else if ... { // something else } else if ......
post-cover-15482
Apr 22 Articles 4 min read
A while ago, I opened a file and immediately knew something was off. Not because it was broken. Not because it was complex. But because it had that shape. You know the one: if ... { // something } else if ... { // something else } else if ......
post-cover-15482
Apr 22 Articles 4 min read
A while ago, I opened a file and immediately knew something was off. Not because it was broken. Not because it was complex. But because it had that shape. You know the one: if ... { // something } else if ... { // something else } else if ......
post-cover-15482
Apr 22 Articles 4 min read
A while ago, I opened a file and immediately knew something was off. Not because it was broken. Not because it was complex. But because it had that shape. You know the one: if ... { // something } else if ... { // something else } else if ......
post-cover-15482
Apr 22 Articles 4 min read
A while ago, I opened a file and immediately knew something was off. Not because it was broken. Not because it was complex. But because it had that shape. You know the one: if ... { // something } else if ... { // something else } else if ......
post-cover-15482
Apr 22 Articles 4 min read
A while ago, I opened a file and immediately knew something was off. Not because it was broken. Not because it was complex. But because it had that shape. You know the one: if ... { // something } else if ... { // something else } else if ......
post-cover-15482
Apr 22 Articles 4 min read
A while ago, I opened a file and immediately knew something was off. Not because it was broken. Not because it was complex. But because it had that shape. You know the one: if ... { // something } else if ... { // something else } else if ......
post-cover-15482
chevron_left

Latest Jobs

View all jobs →