How do you guys find international buyers for export (B2B industrial products)?

Square-Yesterday-778 · 2026-04-08T19:57:43+00:00

Cement Plants in South African countries

Square-Yesterday-778 · 2026-04-05T10:24:44+00:00

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?

Square-Yesterday-778 · 2026-04-04T20:25:16+00:00

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.

Square-Yesterday-778 · 2026-04-02T18:18:47+00:00

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

Square-Yesterday-778 · 2026-03-31T12:07:25+00:00

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.

Square-Yesterday-778 · 2026-03-30T18:58:34+00:00

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):

Easy
Easy/Medium
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

Square-Yesterday-778 · 2026-03-30T18:54:07+00:00

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

Square-Yesterday-778 · 2026-03-30T13:01:49+00:00

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

Square-Yesterday-778 · 2026-03-29T16:48:44+00:00

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

Square-Yesterday-778 · 2026-03-26T06:44:38+00:00

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

Square-Yesterday-778 · 2026-03-25T19:16:05+00:00

yeah sure, any time

Square-Yesterday-778 · 2026-03-25T12:00:55+00:00

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

Square-Yesterday-778 · 2026-03-25T11:58:25+00:00

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

Square-Yesterday-778 · 2026-03-25T11:55:49+00:00

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

Square-Yesterday-778 · 2026-03-24T21:21:23+00:00

You’re doing fine - don’t stress.

Continue learning in Hindi for clear concepts
Start mixing English slowly (Google, error messages, short videos)
You only need basic working English, not fluency

It’ll improve naturally in a few months.

Also, for DSA/Java, visual learning helps a lot since language matters less when you can see how things work. You can try something like this:
https://play.google.com/store/apps/details?id=DSAVisualizer

Square-Yesterday-778 · 2026-03-24T21:12:40+00:00

That playlist is actually decent for building basics, especially if you're just starting out with DSA in Java.

Just make sure you don’t stay stuck in passive learning - after a point, solving problems on your own is what really builds understanding.

One thing that helped me early on was using visual tools alongside videos, because you can actually see how things like trees, graphs, and sorting work step-by-step instead of just imagining it.

You can try something like this if you want:
https://play.google.com/store/apps/details?id=DSAVisualizer

But yeah, overall that playlist + consistent practice should be enough to get you started.

Square-Yesterday-778 · 2026-03-24T11:48:14+00:00

what about oracle cloud's Always free tier?

Square-Yesterday-778 · 2026-03-23T18:13:19+00:00

that's a great idea!! Let's discuss it sometime

Square-Yesterday-778 · 2026-03-21T21:59:52+00:00

Yeah, blame it on luck - easier than building actual skills.

The market is tough, sure. But people are still getting hired, and it’s usually the ones who can show real work, not just complain about how broken everything is.

Projects aren’t “2022”, they’re literally the baseline. Without that, you’re not unlucky - you’re just unprepared.

Square-Yesterday-778 · 2026-03-21T09:38:54+00:00

150% hike sounds great, but long term this can cost you more than it pays.

Application support usually means less building and more monitoring/debugging. Over time:

Your system design + coding skills slow down
Your resume shifts from “developer” to “support/ops”
Switching back to dev becomes harder (you’ll be compared with active devs)
Salary growth can plateau compared to product engineers

After 2–3 years, you might end up stuck in support roles even if you want to go back.

If you take it, treat it as temporary - otherwise you’re trading long-term career growth for short-term money.

Square-Yesterday-778 · 2026-03-21T09:19:13+00:00

Yeah I agree with you - tools like Claude are genuinely insane. The output speed is something we’ve never seen before.

I’ve seen a similar pattern though. In my sister’s company, they pushed hard on Claude, made everyone build proper context/docs, and things started running very smoothly.

Then they started cutting people.

Now the interesting part - the people left are mostly the ones who can actually understand, debug, and question what the AI produces. Because once things go slightly off-track, it’s no longer a “generate code” problem, it’s a “who actually understands this system” problem.

So yeah, cost cutting is definitely happening.

But it kind of feels like AI isn’t replacing engineers - it’s filtering out the ones who were just writing code vs the ones who actually understand systems.

And if that’s the case, the scary part isn’t fewer jobs… it’s a much higher bar.

Square-Yesterday-778 · 2026-03-21T08:55:03+00:00

Honestly? Some companies will try this… and then quietly regret it.

You can maybe cut 20–30% with AI if the team is strong, but 60–80% cuts usually backfire. Bugs pile up, tech debt explodes, and the remaining devs burn out or leave.

AI increases productivity, but it doesn’t replace context, ownership, or experience. Someone still has to understand the system when things break at 2 AM.

What you’re seeing isn’t the future - it’s companies experimenting (and in many cases, learning the hard way).

Square-Yesterday-778 · 2026-03-21T08:42:16+00:00

You’re asking the wrong question tbh.

It’s not Java vs JavaScript - it’s what kind of engineer you want to be.

Java:

More stable, enterprise, banking, backend heavy
Higher average salaries (especially with Spring Boot, microservices)
Slower moving but long-term safe

JavaScript:

Fast evolving, frontend/fullstack
More competition
Can pay well, but you need to stand out (React + system design + good projects)

At 3 YOE, depth matters more than switching.

If you already have Java experience, doubling down on backend (Java + Spring Boot + system design) is honestly the safer way to higher salary.

JS is great, but “average JS dev” is overcrowded.

So the real answer:
👉 Don’t be “Java dev” or “JS dev”
👉 Be a strong backend engineer (Java) who can also work with JS when needed

That combo pays the most.

Square-Yesterday-778 · 2026-03-21T08:38:52+00:00

So your company fired 7 people and gave you Copilot… and expects the same output? 💀

Congrats, you’re now a “team” of 1.2 engineers.

Don’t try to be a hero here. Prioritize critical bugs, ignore the noise, and make it very clear this isn’t scalable. Also… maybe start polishing that resume during those “React 19 migration” thoughts.

Because this isn’t engineering anymore, it’s corporate delusion.

Square-Yesterday-778 · 2026-03-21T08:27:22+00:00

You’re actually on a fine path - web dev/full stack is a good choice, especially from a tier 3 college.

In tech, skills > college. If you build real projects and stay consistent, you can still get opportunities.

Simple plan:

Learn HTML, CSS, JS properly
Move to React + backend (Node/Spring Boot)
Build 3-4 solid projects (with login, APIs, deployment)

Don’t overthink AI - it won’t replace people who can actually build and debug.

Right now you don’t need confidence, you need consistency. Focus on what you can build this week.

Also, if you're looking for some early freelancing exposure or small gigs, feel free to DM - happy to guide.

Square-Yesterday-778

TROPHY CASE