[CAREER ADVICE]
Looking for career advice from people who are currently earning 15+ / 20+ LPA in software engineering.
If you were in my position, what would you do?
I have almost 2 years of experience, and my target is to reach 12+ LPA.
Hereโs what Iโm currently doing:
Solving DSA regularly in Java. Graphs are the only major topic left. Iโm able to solve most problems, although I still struggle with some.
Building one end-to-end project โ PostSyncs, which Iโm also trying to acquire users for.
Building smaller backend projects to improve my backend fundamentals:
Notification Service โ
URL Shortener โ
Currently building a custom job scheduler similar to BullMQ.
My main goal is to become stronger in backend engineering and system design, not just build projects for the sake of having them on my resume.
My question is:
What would you focus on if you were in my position?
Should I:
Go deeper into backend + system design?
Focus more on DSA and interview preparation?
Learn another OOP-oriented language like Go?
Or focus on something else that can realistically help me reach 12+ LPA?
Would really appreciate advice from people who have already made this transition.
[CAREER ADVICE]
Looking for career advice from people who are currently earning 15+ / 20+ LPA in software engineering.
If you were in my position, what would you do?
I have almost 2 years of experience, and my target is to reach 12+ LPA.
Hereโs what Iโm currently doing:
Solving DSA regularly in Java. Graphs are the only major topic left. Iโm able to solve most problems, although I still struggle with some.
Building one end-to-end project โ PostSyncs, which Iโm also trying to acquire users for.
Building smaller backend projects to improve my backend fundamentals:
Notification Service โ
URL Shortener โ
Currently building a custom job scheduler similar to BullMQ.
My main goal is to become stronger in backend engineering and system design, not just build projects for the sake of having them on my resume.
My question is:
What would you focus on if you were in my position?
Should I:
Go deeper into backend + system design?
Focus more on DSA and interview preparation?
Learn another OOP-oriented language like Go?
Or focus on something else that can realistically help me reach 12+ LPA?
Would really appreciate advice from people who have already made this transition.
[CAREER ADVICE]
Looking for career advice from people who are currently earning 15+ / 20+ LPA in software engineering.
If you were in my position, what would you do?
I have almost 2 years of experience, and my target is to reach 12+ LPA.
Hereโs what Iโm currently doing:
Solving DSA regularly in Java. Graphs are the only major topic left. Iโm able to solve most problems, although I still struggle with some.
Building one end-to-end project โ PostSyncs, which Iโm also trying to acquire users for.
Building smaller backend projects to improve my backend fundamentals:
Notification Service โ
URL Shortener โ
Currently building a custom job scheduler similar to BullMQ.
My main goal is to become stronger in backend engineering and system design, not just build projects for the sake of having them on my resume.
My question is:
What would you focus on if you were in my position?
Should I:
Go deeper into backend + system design?
Focus more on DSA and interview preparation?
Learn another OOP-oriented language like Go?
Or focus on something else that can realistically help me reach 12+ LPA?
Would really appreciate advice from people who have already made this transition.
Things I am working on
- Building Voicely
- Learning system design concepts by actually doing the code
- Improving SEO of my 2 websites
- Starting to practice graphs
Things I am working on
- Building Voicely
- Learning system design concepts by actually doing the code
- Improving SEO of my 2 websites
- Starting to practice graphs
Hey, I am looking for a freelance project. I am free for 2-3 weeks and want to spend my time building.
If you have any full-stack work, I can do it. Money is not an issue; I want to explore my free time.
Portfolio: https://t.co/OvHsLPh3TJ
i try to implement it using a lock mechanism as we do in the DB, but at lock ttl expire i stuck there.
For now, I stopped this and first learned Lua, and later i apply it.
Maybe in the next project i apply rate limiting using lua script.
Today I built ๐ฅ๐ฎ๐๐ฒ ๐๐ถ๐บ๐ถ๐๐ฒ๐ฟ as a standalone backend project.
While implementing it, I came across an important problem โ ๐ฅ๐ฎ๐ฐ๐ฒ ๐๐ผ๐ป๐ฑ๐ถ๐๐ถ๐ผ๐ป๐.
In databases, we can handle critical sections using ๐ง๐ฟ๐ฎ๐ป๐๐ฎ๐ฐ๐๐ถ๐ผ๐ป๐ + ๐๐ผ๐ฐ๐ธ๐. Redis also supports distributed locks, but for this use case, ๐๐๐ฎ ๐ฆ๐ฐ๐ฟ๐ถ๐ฝ๐๐ provide a cleaner approach.
๐๐๐ฎ ๐๐ฐ๐ฟ๐ถ๐ฝ๐๐ ๐ฐ๐ผ๐บ๐ฏ๐ถ๐ป๐ฒ ๐บ๐๐น๐๐ถ๐ฝ๐น๐ฒ ๐ฅ๐ฒ๐ฑ๐ถ๐ ๐ผ๐ฝ๐ฒ๐ฟ๐ฎ๐๐ถ๐ผ๐ป๐ ๐ถ๐ป๐๐ผ ๐ผ๐ป๐ฒ ๏ฟฝ๏ฟฝ๐๐ผ๐บ๐ถ๐ฐ ๐ผ๐ฝ๐ฒ๐ฟ๐ฎ๐๐ถ๐ผ๐ป.
Implement rate limiting for the URL Shortener Read API:
- Use the user's IP address for identification.
- Allow a maximum of 60 requests per user within a 60-second sliding window.
Implement rate limiting for the URL Shortener Read API:
- Use the user's IP address for identification.
- Allow a maximum of 60 requests per user within a 60-second sliding window.
Implement rate limiting for the URL Shortener Read API:
- Use the user's IP address for identification.
- Allow a maximum of 60 requests per user within a 60-second sliding window.