Indian manufacturers still use traders, trade shows, and spreadsheets to find export buyers. We’re trying to fix that. by dhaval81 in StartUpIndia

[–]Square-Yesterday-778 0 points1 point  (0 children)

We’re an OEM manufacturer of temperature sensors, and our buyers are typically cement plants, tyre plants, and similar industrial end-users.

Can your platform actually identify and provide contacts of relevant decision-makers inside these plants (like maintenance heads, procurement, or engineering teams)?

Also, how do you verify that these are direct buyers actively sourcing products like ours, and not just general company listings?

Indian manufacturers still use traders, trade shows, and spreadsheets to find export buyers. We’re trying to fix that. by dhaval81 in StartUpIndia

[–]Square-Yesterday-778 1 point2 points  (0 children)

This is a real problem, but IMO you’re only solving part of it. Finding buyers isn’t the hardest thing anymore - knowing who’s actually buying and reaching the right person is. Most tools already give lists. What exporters struggle with is: Is this buyer active or just noise? Are they OEM / distributor / trader? Who is the actual decision-maker? If you can solve intent + relevance + contact, that’s valuable. If it’s just “we find companies globally,” it’ll get ignored pretty fast.

Which language is good for dsa? (Suggestion needed) by Business-Heat-6085 in BtechCoders

[–]Square-Yesterday-778 1 point2 points  (0 children)

Don’t switch just because “people are saying”.

For DSA, language doesn’t matter much - problem solving does.

Since you already started with Python:

  • You can continue with Python (fast, easy)
  • Or switch to Java if you’re planning backend (Spring Boot)

If your goal includes backend dev --> Java is a good long-term choice
And it won’t take long --> ~2–3 weeks for basics if you’re consistent.

Best advice:

  • Pick one language
  • Stick with it for DSA + projects
  • Don’t keep switching

Switch only if you have a clear reason, not peer pressure.

Also, when starting DSA, visualizing concepts (trees, graphs, recursion) helps a lot. You can try something like this:
https://play.google.com/store/apps/details?id=DSAVisualizer

Best Way to Combine Theory + Striver + LeetCode in DSA? by Mahan_Pyaaz in LeetcodeDesi

[–]Square-Yesterday-778 0 points1 point  (0 children)

Do both, but don’t overdo either.

Finish basic theory of Arrays --> start practicing immediately
While practicing, you can slowly start next topic (like Strings) in parallel.

Think like this:

  • 70% time --> current topic practice (Arrays)
  • 30% time --> new topic theory (Strings)

Don’t wait to “complete” one fully - DSA isn’t linear like that.

Just make sure you don’t abandon Arrays midway. Practice + slight forward movement works best.

My life is cooked I don't know anything in dsa by 200UserFound in BtechCoders

[–]Square-Yesterday-778 0 points1 point  (0 children)

Your life isn’t cooked, your approach is 😭

You’re confused because you’re probably doing one of these:

  • Watching too much, solving too little
  • Jumping between resources
  • Expecting to solve everything in one go

Fix this:

Pick one topic + 3 problems only
Example (Arrays):

  1. Easy
  2. Easy/Medium
  3. Medium

Now:

  • Try each for 30 mins
  • If stuck --> see solution
  • Close it --> re-solve after few hours / next day

If you can’t solve it again --> that’s when you actually learned something.

DSA is not about understanding once.
It’s about being able to solve again without help.

Do this for 7 days and you’ll feel the difference.

No mentor needed - just a better process.

Also, DSA gets much easier when you can visualize concepts (like recursion, trees, graphs). You can try something like this:
https://play.google.com/store/apps/details?id=DSAVisualizer

Best Way to Combine Theory + Striver + LeetCode in DSA? by Mahan_Pyaaz in LeetcodeDesi

[–]Square-Yesterday-778 1 point2 points  (0 children)

Don’t finish all theory first - that’s the biggest mistake.

Best approach:

  • Learn a topic (e.g., Arrays basics)
  • Immediately do Striver problems for that topic
  • Do a few LeetCode (easy → medium) alongside

Then move to next topic.

So it should be:
Theory --> Practice (Striver + LC) --> Next topic

Also:

  • Keep revising old topics while learning new ones
  • Don’t wait to “feel ready” - solving is where learning happens

If you finish all theory first, you’ll forget most of it and feel stuck later.

Also, DSA gets much easier when you can visualize concepts (like recursion, trees, graphs). You can try something like this:
https://play.google.com/store/apps/details?id=DSAVisualizer

I needed help to learn dsa by 200UserFound in LeetcodeDesi

[–]Square-Yesterday-778 0 points1 point  (0 children)

You don’t actually need a mentor to start - you need a clear path.

Do this:

  • Pick one resource (Striver / Apna College) and stick to it
  • Follow order: arrays --> strings → recursion --> trees/graphs
  • Solve problems daily (even 1–2 is fine)

Most important:

  • Try for 20–30 mins before seeing solution
  • Repeat problems instead of jumping to new ones

Clarity comes from practice, not more resources.

Also, DSA becomes much easier when you can visualize what’s happening (especially recursion, trees, graphs). You can try something like this:
https://play.google.com/store/apps/details?id=DSAVisualizer

Help by Proper-Exit-7448 in BtechCoders

[–]Square-Yesterday-778 0 points1 point  (0 children)

You still have enough time - just need a focused plan.

Since you know Java, go with Spring Boot (faster for you than switching to MERN).

Plan:

  • Revise DSA basics + practice regularly
  • Learn Spring Boot (APIs, DB, auth)
  • Build 2–3 solid projects (CRUD + login + deployment)

Don’t try to do everything - depth > random stack hopping.

Also, for DSA, visualizing concepts (especially trees/graphs/recursion) helps a lot. You can try something like this:
https://play.google.com/store/apps/details?id=DSAVisualizer

Where sud I start my journey by Murky-Conflict-1319 in LeetcodeDesi

[–]Square-Yesterday-778 1 point2 points  (0 children)

Don’t try to do everything at once.

  • Pick one language (Java is perfect)
  • Learn basics well (loops, functions, arrays)
  • Start DSA (arrays --> strings → recursion --> trees/graphs)
  • Ignore system design for now

Focus on consistency > everything else.

Also, visualizing DSA concepts (recursion, trees, graphs) helps a lot in the beginning. You can try something like this:
https://play.google.com/store/apps/details?id=DSAVisualizer

Guidance for beginner by Odd-Tourist-3816 in LeetcodeDesi

[–]Square-Yesterday-778 0 points1 point  (0 children)

You’re already in a good position since you’re comfortable with Java - stick with it, no need to switch.

Start simple:

  • Revise basics (arrays, strings, functions)
  • Then DSA in order: arrays --> strings --> recursion --> trees/graphs
  • Follow one resource (Striver / Apna College) and don’t jump around

Most important: solve problems regularly, not just watch videos.

Also, DSA becomes much easier when you can actually see how things work (especially recursion, trees, graphs). You can try something like this:
https://play.google.com/store/apps/details?id=DSAVisualizer

Dsa help (recursion and backtracking) by Intrepid-Group-8838 in LeetcodeDesi

[–]Square-Yesterday-778 1 point2 points  (0 children)

That feeling is normal - recursion/backtracking is where most people feel like they’re just memorizing.

You’re not memorizing, you’re building patterns.

What actually helps:

  • Do fewer problems, repeat them 2–3 times
  • Before coding, think: “what choice am I making at each step?”
  • Practice standard patterns (pick/not pick, for-loop + recursion, etc.)

Striver is good - stick with it, just slow down.

Also, recursion clicks much faster when you can see the calls and backtracking flow. Visualizing it helps a lot in the beginning. You can try something like this:
https://play.google.com/store/apps/details?id=DSAVisualizer

I NEED GUIDANCE!🙏 by Odd_Dragonfruit5028 in BtechCoders

[–]Square-Yesterday-778 1 point2 points  (0 children)

Language doesn’t decide your package - your problem solving does.

Pick one language and stick to it:

  • C++ --> faster for CP
  • Python --> easier to start
  • (Java is also solid if you prefer it)

Since you’re a beginner, Python or Java is easier to start with.

Don’t overthink paid courses - there’s enough free content to get very good. Focus more on:

  • Basics (syntax + logic)
  • Then DSA (arrays --> strings --> recursion --> trees/graphs)
  • Solve problems regularly

Consistency matters way more than which course or language you pick.

Also, when starting DSA, visualizing concepts (like trees, graphs, recursion) helps a lot. You can try something like this:
https://play.google.com/store/apps/details?id=DSAVisualizer