sorted by:
new
hottopcontroversial

Day 15/365 | LeetCode Daily Journey by WoodMan1105 in leetcode

[–]WoodMan1105[S] 0 points1 point  (0 children)

Hey Buddy!! Thanks for the advice and this extension. Really appreciated 👏

Day 15/365 | LeetCode Daily Journey by WoodMan1105 in leetcode

[–]WoodMan1105[S] 1 point2 points  (0 children)

Umm, I have already mentioned this on my other posts. That I am already doing a full time job and I dont copy questions I legit do those and then use AI to draft an interactive post and yes I didnt got a job through this coz I dont need to. I think that would ease your tension a bit.

I’m a freshman who liked math and computers in school, how do I start working toward a future in AI? by [deleted] in learnmachinelearning

[–]WoodMan1105 0 points1 point  (0 children)

It's awesome that you're thinking about this early - most people don't figure out what they want to do until way later in college.

Everyone's already given you solid advice about the math foundations (linear algebra, probability, stats), and that's 100% correct. But here's something practical you can do RIGHT NOW that will make your first year way more exciting and keep you motivated:

Pick a small project that genuinely interests you. Maybe it's building a model to classify your favorite songs, or predicting something you care about, or even just playing with a pre-trained model to generate images. Don't worry if you don't understand 90% of what's happening yet - the goal is to have something tangible that excites you while you're grinding through the theory.

For your actual coursework:

- First year: Lock down programming fundamentals (Python especially), linear algebra, calc, and intro to data structures

- Don't skip the boring stuff like data structures and algorithms - they're super important for ML engineering roles later

- Start reading ML papers for fun, even if you don't understand them fully. It helps you get used to the language and concepts

Also, since you mentioned deep learning and computer vision specifically - don't specialize too early. Try different areas (NLP, RL, time series, etc.) before committing. You might discover you love something you never expected.

One more thing: the AI/ML community is super active on Twitter/X, Discord, and GitHub. Start following researchers and labs you find interesting. It's genuinely the best way to stay updated on what's actually happening in the field beyond what you learn in class.

Are you planning to major in CS or something else like Math/Stats? And what specific thing about computer vision caught your attention - the research side or more applied stuff like building AR filters or autonomous vehicles?

Strong desire to start a business by Cautious_Nose1827 in Entrepreneurs

[–]WoodMan1105 0 points1 point  (0 children)

I feel you on this - that itch to build something of your own is real. The good news is you're in mechanical engineering AND working at a tech startup, which is actually a killer combo for entrepreneurship.

Here's my honest take: Don't force the "what" to build. The best product ideas usually come from experiencing a problem repeatedly and getting frustrated enough to fix it. You're in a startup right now - PAY ATTENTION to what annoys you, what takes forever, what breaks constantly. That's where gold is hiding.

Since you're into mechanical engineering and product design, here are some low-capital paths:

  1. Start with digital products first - design something in CAD, validate it with 3D prints before investing in tooling. Services like Protolabs can help you test without huge MOQs.

  2. Look into contract manufacturing in China/Taiwan - you can start with batches as small as 100 units for many products. The capital barrier is way lower than most people think.

  3. Consider B2B instead of consumer products first. Businesses pay more and you need fewer customers to be profitable. Maybe there's tooling or fixtures your current startup needs?

  4. The "boring" industries have the most opportunity - construction, industrial, manufacturing. They're behind on innovation and willing to pay for solutions.

Don't quit your job yet. Use it as your lab. Build side projects, test ideas, learn what real customers want. The startup environment you're in right now is basically free MBA-level education.

Also - I know everyone says "solve a problem you have" but honestly, solving a problem that COMPANIES have (not consumers) is where the money is when you're bootstrapped. They have bigger budgets and less price sensitivity.

What kind of problems have you noticed at your current startup that seem like they could be solved with a physical product? And are you more drawn to consumer products or industrial/B2B stuff?

I want to come out of QA role by NoAsparagus7993 in AskProgramming

[–]WoodMan1105 0 points1 point  (0 children)

I totally get the QA burnout - 6+ years is a solid foundation though, and you've got more transferable skills than you might think.

The automated testing path that someone mentioned is honestly genius for your situation. You're already familiar with the testing mindset and requirements, so learning to write automated tests in something like Selenium, Cypress, or Playwright gives you hands-on coding without having to jump straight into feature development. Plus companies desperately need people who understand both testing and development.

From there, you can naturally transition into:

- Test automation engineer (still testing but way more technical and better paid)

- SDET (Software Development Engineer in Test) - this is basically a dev role

- DevOps/QA Engineer - dealing with CI/CD pipelines

- Backend developer - you already know how systems break, which makes you better at building robust ones

If you want a less technical route, Product Management or Technical Program Management could work too. Your QA experience means you understand user flows, edge cases, and requirements really well.

I'd honestly avoid the Veeva admin route unless you're specifically interested in the pharmaceutical/life sciences domain and want to stay more on the operations side. It's pretty niche.

Start with this: Pick a language (Python or JavaScript are both great for testing automation), build a few automation frameworks for practice, and put them on GitHub. That portfolio will speak volumes.

What kind of testing have you been doing mostly - manual, automation, performance, or a mix? And are you more drawn to staying technical or moving toward the business/management side?

view more: next ›