Bima (ngbima)

Stop Ignoring your HTTP Headers: Secure any Frontend App in 10 minutes. Sometime last year I interviewed with a bank, up to the last stage I was already feeling at home. Then a man said tell me about ‘X-Frame-option-, and so I dipped. Hence the force that made me write on the; 5 Essential Security Headers for Modern Frontend Devs Please read more here: https://dev.to/olabima_/5-essential-security-headers-for-modern-frontend-devs-nextjs-angular-vue-3icf Feel free to share your thoughts as well. Cheers!!

• 0 replies
• 1 recast
• 0 reactions

recast:farcaster://casts/0xc8b0ba3042738d43bf54471687e6a21a4f10221cf1305594657179360252487e

• 0 replies
• 0 recasts
• 0 reactions

Man, this Git workflow has been frustrating me lately. Team uses main for Prod and develop for UAT. Every feature I finish, I have to manually create two branches, switch back and forth, merge, push, then open separate PRs. Today I got tired of the nonsense and just automated the whole thing. Now I run one command yarn dual-pr and it handles pulling latest, branching, merging and pushing to both. Even drops the PR links straight in terminal.If there's conflict on the develop side it stops and tells me. Super simple.Script here if you need it: gist.github.com/boluwatifee4/f… Anyone else dealing with this annoying dual env flow? How do you handle it?

• 0 replies
• 0 recasts
• 0 reactions