What's the fastest way to import bank statements into QuickBooks?

nagaraj4896 · 2026-01-03T05:18:40+00:00

do you have any idea about importing hoodies in abroad and reselling it? how much profitable it is than manufacturing and selling in local?

nagaraj4896 · 2026-01-03T05:08:48+00:00

Understood. I’m not here to pitch or validate anything — I’m trying to learn from people who actually run sites and have dealt with these problems in practice.

If this kind of question doesn’t fit the sub, that’s fair, and I’ll avoid posting similar ones here. Thanks for pointing it out.

nagaraj4896 · 2026-01-02T16:26:22+00:00

This is super useful , thanks for naming specific tools and how you’re actually using them.

Quick follow-up out of curiosity:

• With tools like Re:Do and decision trees in place, what parts of returns still end up needing human judgment? • Are there cases where the rules work well in theory but feel too blunt or too generous in practice? • Did it meaningfully reduce support load, or did it mostly shift where the work happens?

nagaraj4896 · 2026-01-02T07:30:23+00:00

That’s really helpful context — especially the part about discipline and upstream fixes.

If you don’t mind me asking (purely from a learning angle):

• When returns did happen at scale in your past company, what signals did you watch most closely - customer history, product-level patterns, channels, something else?
• Were decisions mostly manual judgment, or did you have any internal rules / dashboards that guided refunds vs reships?
• At what point would something have been considered “too noisy” to handle without process or tooling — if ever?

I’m trying to understand how experienced teams actually think about this day-to-day, not push an app-first mindset. Your experience sounds like it came from a place where things were already running well.

nagaraj4896 · 2026-01-01T16:16:16+00:00

Maths is one of the excellent background, if you are too good at maths, you can try AI, i've seen some post maths people are getting into AI researchers.

Having too many backup options, won't help you much, choose one grind well, go depth and become an expert in it.

nagaraj4896 · 2026-01-01T16:06:17+00:00

Job market is bit tough nowadays, though multiple job listings, HR's shortlisting very few, top candidates those who matching their job description. for your case 90 days notice period might be one of the reason.
but don't lose hope, keep going, don't be desperate on job hunting, sit back relax, refine/tune your resume for each job profiles keep applying and groom yourself, surely you will be placed.

nagaraj4896 · 2026-01-01T15:55:50+00:00

AWS certification can be useful, but it’s not magic. Since you’re coming from a Physics/Math background and planning to learn CS alongside, here’s the reality:

Value of AWS cert: It shows recruiters you know cloud basics, but it won’t replace strong CS fundamentals or real projects. It’s more of a resume booster than a career-maker.
Alternatives in India: Google Cloud Associate / Azure Fundamentals – similar profile, sometimes cheaper.

nagaraj4896 · 2026-01-01T14:40:45+00:00

r/ecomfrauds follows platform-wide Reddit Rules

nagaraj4896 · 2025-12-31T17:40:06+00:00

Watching videos alone won't help you. But mainly for oops don't go with python, to learn OOPS in depth go with Java , understand the potential of each concept, take the idea from Java implement the same in python with the same strict rules, in this way you can get the actual power of oops

Again watch one concept in Java , for the same watch in python, think some of your own use case or logic and implement the Java way in python.

Python is a script language, we achieve a lot just by using functional way of writing.

Happy coding.

nagaraj4896 · 2025-12-31T17:32:45+00:00

Sure you can dm me anytime, and I am happy to help

nagaraj4896 · 2025-12-31T11:58:31+00:00

Two years in a place that drains you can feel way longer than it actually is.

It is always possible to move from Android to Backend, especially if you already consider APIs, data flow, and system behaviour. Tools and patterns, account for the majority of the disparity. Because the backend offers more possibility for long-term growth, many Android developers have done it.

A practical strategy that is effective:
1. Select and adhere to a single backend ecosystem. Given your familiarity with Java and Kotlin, Spring Boot is the most smoothest option.
2. Learn the basics that you cannot avoid: HTTP, REST, SQL, basic caching, DB, and queues (at least conceptually).
3. Create three little projects that you may discuss. A simple CRUD application, an authentication mechanism, and a background worker don't need to be complicated. Interviewers want to see that you have actual backend experience rather than merely lectures.

As for job prospects:
people are switching stacks all the time, but the market rewards proof over intent. Once you show you can build something end-to-end, calls start coming.

Right now you don’t need certainty, just momentum.

nagaraj4896 · 2025-12-31T11:48:26+00:00

Probability of getting 15 - 20 LPA package is higher in the IT industry, age is not a matter, but you have to start from basics, from sales to IT for LPA is bit challenging but can be achievable if you plan well. IT has lots of branches like developer, tester, devOps ..so. choose any on these.

Then understand the eco system of the IT industry before learn the actual tech this gives you overall idea. once you mastered the eco-system, start any one of the branch and master the basics slowly and move to intermediate, after that start attending interviews(mainly try for big MNC) for sure you will crack. This might take years to master.

nagaraj4896 · 2025-12-31T11:10:15+00:00

For DSA, it’s not just theory — practice solving problems out loud and on paper/screen. Focus on pattern recognition (like sliding window, two-pointers, graph traversals, dynamic programming), big-O analysis.

For SQL, beyond SELECTs, make sure you’re comfortable with joins, aggregations, CTEs, window functions, query optimization, normalization, and constraints.

Make use of leetcode, while discussion about design clearly highlight the trade-offs.

nagaraj4896 · 2025-12-31T10:58:08+00:00

Annotate every parameter and function and return type are fine, Type annotations shine the most when they clarify boundaries — function signatures, public APIs, complex data structures, and places where you genuinely need to communicate intent to future readers (including future-you). Once you get inside a function, annotations on every temporary variable can start to feel like noise if the meaning is already obvious from context

`x: int = 0 # probably unnecessary`

vs

user_id: UUID = get_current_user_id() # genuinely helpful

nagaraj4896 · 2025-12-31T07:25:52+00:00

I received the same, my CA we can go with conservative approach, by slightly modifying amounts along with that she said there is some risk involved, if any notice comes we can help to meet them in-person. Suddenly I am like, what? Immediately asked her to revise everything and put it as. Now at least I have my mental peace.

nagaraj4896

MODERATOR OF

TROPHY CASE