2d ago Β· 5 min read Β· If you've ever tried to write a Playwright test that covers a full sign-up β email verification β login flow, you've hit the same wall: how do you actually read the email your app sends during a test?
Join discussion
2d ago Β· 9 min read Β· Introduction When I started learning CI/CD as part of the Full Stack Open curriculum, I thought it was going to be complicated. It turned out to be one of the most satisfying things I've set up as a d
Join discussion
2d ago Β· 5 min read Β· Modern software development demands speed, consistency, and reliability. Manual deployments and ad hoc testing processes inevitably introduce risk. GitHub Actions emerged as one of the most widely ado
Join discussion
5d ago Β· 7 min read Β· error: failed to push some refs to 'https://github.com/...' Updates were rejected because the remote contains work that you do not have locally. The first time it happened I thought it was a simple g
Join discussion
Jun 3 Β· 8 min read Β· It was a Tuesday. The pull request was clean. Peer review: approved. Unit tests: green across the board. Staging smoke tests: passing. The deploy pipeline finished at 4:47 PM, and the whole engineerin
Join discussion
Jun 2 Β· 2 min read Β· ππΆπ²π ππ΅π² π½πΏπΌπ·π²π°π πΌπ» π π΄πΆππ΅ππ― When utilizing managed cloud providers (GKE, AKS, EKS), You've handed major part of the operational overhead to the cloud provider but engineering
Join discussionMay 31 Β· 4 min read Β· Stop Deploying Manually: A Friendly Guide to GitHub Actions for Web Developers Let's be honest β manually testing and building your app before every single deploy is a recipe for disaster. Here is ho
Join discussion
