4 ms·
minor nits: 1/ For coding interviews, you should be solving 4-6 leetcode problems per day which should take about 5-6 hours). The remaining 3 hours of bandwidt
by itake 2y ago
minor nits:
1/ For coding interviews, you should be solving 4-6 leetcode problems per day which should take about 5-6 hours). The remaining 3 hours of bandwidth should be spent learning system design.
2/ If the jobs are you applying for learn Spring, go build a few apps on your own in Spring. Your github profile doesn't have much coding activity.
3/ your profile photos in github and your website aren't centered.
4/ I would remove the donate button on your website. it doesn't signal that you're a successful programmer. If you truly need to have a donation button, write more explaining why people should donate to you.
- MyFirstSass 2y ago"leetcoding" 6 hours and doing "systems design" for 3 hours, totalling 9 hours of heavy cognitive math like work each day while job hunting? Whev, i'd have an absolute mental breakdown over that. But maybe it's the kids and other responsibilities, how old are you? I don't even think i grinded that hard in university, i've always only been able to do that kind of work 3-5 hours even when maxing out for an exam, and only for a few days at a time.
- fewald_net 2y agoI found that the maximum number of hours I could do something productive was 6 hours while being in college. After this I was able to keep going but with diminishing returns. Nowadays it’s hard for me to find even a 6 hour block (while employed). The best advice I heard is to treat interviewing like a full time job with lunch break and a defined end.
- purple-leafy 2y ago1 is terrible advice. 9 hours of heavy thought work? Yeah right. Good way to mentally exhaust yourself and burn out
- itake 2y agoI’m just sharing what my friend did to get into FANGA. In China, they work 12 hours per day.