Content pfp
Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions

Justin Hunter pfp
Justin Hunter
@polluterofminds
Here’s my hot take for today. Frontend is harder and more time consuming than backend.
18 replies
1 recast
23 reactions

sourav currently at DevCon pfp
sourav currently at DevCon
@sourav
I feel that FE is very capricious. You're dealing with different environments, faster changing best practices, libraries, frameworks, & tooling, increasingly demanding audiences, and any imperfections will be quickly noticeable. While BE is declarative hence solid once put in place.
1 reply
0 recast
2 reactions

sourav currently at DevCon pfp
sourav currently at DevCon
@sourav
But I also feel that BE is riskier. If you mess up the frontend, revert and redeploy. If you mess up the backend (data corruption, data removal, data leaking, etc.) you are in hell.
1 reply
0 recast
2 reactions

sourav currently at DevCon pfp
sourav currently at DevCon
@sourav
The thing about FE is that by default, devs aren’t equipped with tools that will guide them down “happy paths” for most things. To be good at FE, one needs to care deeply and devote a ton of time and energy into framework and component choice and understanding what’s going on under the hood.
1 reply
0 recast
2 reactions