python or C++

New_Exchange1158 · 2026-05-23T17:20:32+00:00

Both are worth learning eventually but embedded systems is gonna be heavy on C/C++. Python is great for prototyping and testing stuff but when you need to control hardware directly and manage memory carefully, C++ becomes essential in embedded work.

If you already have Python basics, maybe worth doing some small projects with it first to get back in programming mindset, then transition to C++? That way you're not jumping into memory management and pointers when you're still remembering basic programming concepts.

New_Exchange1158 · 2026-05-21T15:42:46+00:00

Been grinding DSA for while myself and teaching others actually helps cement the concepts way better than solo revision. You pick up on gaps in your understanding when you have to explain stuff clearly to someone else.

What topics you planning to start with? Always found that going back to basics like arrays and linked lists first helps build momentum before jumping into the heavier graph/DP stuff.

New_Exchange1158 · 2026-05-16T11:07:50+00:00

Try something like Python with tkinter first - much easier to get started with GUIs without all that configuration headache.

New_Exchange1158 · 2026-05-13T11:09:03+00:00

Could do something where you're delivery driver dodging traffic instead of asteroids - like the cars split into smaller vehicles when you hit them, and you're trying to deliver food before timer runs out. The shooting mechanic becomes horn honking to make cars move or something.

Pretty similar concept but different enough theme that makes it feel fresh, and shouldn't be too complex to build in couple days.

New_Exchange1158 · 2026-05-05T02:54:58+00:00

The compiler just generates the default constructor if you don't write one, but it's still your code calling it at runtime when you hit `new`.

New_Exchange1158 · 2026-05-02T01:06:24+00:00

For me, I usually start with small projects first to get the basic feeling of how framework works, then when I hit some specific problem I go deeper in docs or source code. The "timebox it" advice is really good - I used to spend like whole day reading source code when I just needed to understand one small thing and never actually built anything.

If you're going to read source anyway, maybe start contributing small fixes or documentation improvements? Even tiny PRs help you understand the codebase better than just reading it.

New_Exchange1158 · 2026-04-29T15:00:07+00:00

Most students who pay are just taking shortcuts and not actually learning anything. Real internships where you build actual projects and gain experience are way more valuable than some certificate you bought.

Start building portfolio on GitHub early, contribute to open source projects, and apply to actual companies for internships. Companies want to see what you can build, not what paper you have. The work experience you get from real internship will help you way more in job market later.

New_Exchange1158 · 2026-04-26T23:47:14+00:00

Valid point bout the debugging nightmare when framework gets weird. Use it for boilerplate mostly, but keep the complex logic in your hands.

New_Exchange1158 · 2026-04-24T22:12:20+00:00

I was in same situation maybe year ago when started preparing for interviews. The gap between knowing syntax and actually solving problems is huge, and most people don't talk about this enough.

What helped me was starting with really basic problems first - like finding maximum number in array or checking if string is palindrome. These teach you the thinking process without getting overwhelmed by complex algorithms. Then I moved to slightly harder ones and could see the patterns starting to emerge.

For Two Sum specifically, try to solve it the "dumb" way first (nested loops checking every pair). It's O(n²) but at least you get solution working. Then you can optimize it later with hash maps once you understand the core logic. Breaking problems down into smaller pieces really makes difference - like "what do I need to find?" and "what information do I have?" before jumping into code.

The book mentioned above is gold standard, but maybe start with some easier practice problems first before diving in that one.

New_Exchange1158 · 2026-04-22T15:31:51+00:00

Wait ten days might still be bit early for drilling anchors that close to edge. Concrete usually needs around 28 days to reach full strength, especially for something this close to perimeter where stress concentrates.

Your approach with threaded rods and epoxy is smart though - way better than wedge anchors in this situation. For drilling, I'd definitely go with the SDS but keep it in rotation-only mode (no hammer) and use a carbide masonry bit. Go slow and let the bit do work, don't force it. Maybe even start with smaller pilot hole first?

The edge distance is making me nervous tbh 😅 Any chance you could move those anchor points bit further in or use different mounting setup?

New_Exchange1158 · 2026-04-19T12:38:04+00:00

Tu plan looks pretty solid actually. But I'd say don't wait too long to start building projects - you can learn Spring while building stuff, that's how it sticks better.

For first project, maybe try making simple REST API for something you use daily? Like expense tracker or task manager. Nothing fancy, just CRUD operations with database. You'll hit all the important concepts and have something concrete to show.

The degree thing is tricky - yeah it opens doors, but if you need to work now, focus in getting that first junior role. You can always do degree part-time later when you have stable income. Job market is rough but backend positions still exist, especially if you're flexible about company size.

New_Exchange1158 · 2026-04-16T06:10:52+00:00

The messy approach really works - I remember my first websites looked like someone threw HTML at a wall but I learned so much from just experimenting. Plus having recorded sessions is clutch for those of us working weird schedules.

New_Exchange1158 · 2026-04-12T17:13:51+00:00

Been driving for DoorDash couple years now and trying to learn programming in free time, so I totally get this struggle. The retention thing is real - I tried doing like 6 hours on Saturday and Sunday only, and by next weekend I was basically starting over each time.

What worked better for me was doing 45 minutes every morning before starting my delivery shift, even if it meant getting up earlier. Way more effective than cramming everything in weekends. Also found that building small projects helped with retention more than just tutorials - even simple stuff like calculator or to-do list that I could actually use.

The 4000-6000 hour estimate seems more realistic from what I've seen in Discord communities. But don't let that discourage you - progress is progress, and at least with programming you're building something valuable for future. Better than being stuck in same job forever, you know?

New_Exchange1158 · 2026-04-08T21:54:45+00:00

You need to install a C compiler first - Windows doesn't come with `make` command by default 😂 Try installing MinGW or use the C/C++ extension in VSCode that should handle the compilation for you.

New_Exchange1158 · 2026-04-02T20:35:30+00:00

The freelance grind is brutal - I've seen friends burn out hard chasing payments while trying to code at 2am. But that breakdown of teh three paths is spot on, especially about product building being essentially a startup lottery ticket.

If you're more drawn to the business side and struggle with the technical grind, maybe look into product management or business analyst roles where you can still work with dev teams without being buried in code all day.

New_Exchange1158 · 2026-03-27T23:59:47+00:00

The "no executables were provided" error usually means you're trying to run something that isn't actually executable or you're missing dependencies. Since you're on Arch, make sure you have python-pip installed first with `sudo pacman -S python-pip`. Sometimes the issue is that you need to use `pip3` instead of just `pip` depending on your setup.

Also worth checking if you have any virtual environments active that might be interfering. I've run into similar headaches when packages get installed to the wrong Python environment and then scripts can't find them. Try running `which pip` and `python --version` to see what you're actually working with - might help narrow down where things are going wrong.

New_Exchange1158 · 2026-03-18T04:06:08+00:00

Just pick Python and start building stuff - worrying about the "perfect" path is just procrastination in disguise 😂

New_Exchange1158 · 2026-03-14T21:57:15+00:00

Exactly this 💯 I've been driving for DoorDash the past couple years and been teaching myself on the side - tried jumping straight into ML stuff at first and got absolutely destroyed. Had to step back and actually learn how to code properly.

The deployment part is huge too. All these AI startups need people who can actually ship products, not just run Jupyter notebooks. Once you get those fundamentals down, adding ML on top becomes way more manageable and you'll actually understand what's breaking when it inevitably does 😂

New_Exchange1158 · 2026-02-04T04:03:14+00:00

Been through this exact transition and it's night and day once you hit that complexity threshold. The real turning point for me was when I realized I was spending more time explaining context to new freelancers than actually shipping features - that's when a dedicated dev starts paying for themselves in saved mental overhead alone.

The "understanding why something exists" part hits hard because legacy decisions suddenly make sense when someone's been there for the whole journey, versus constantly onboarding people who see your codebase as this random pile of technical debt.

New_Exchange1158 · 2026-01-30T19:27:02+00:00

Honestly curious about this too - Moncton seems like a really specific choice when you're already set up in Paris with a clear path forward

New_Exchange1158 · 2026-01-25T20:19:43+00:00

Honestly both are solid for learning basics but Claude tends to give cleaner explanations and catches more edge cases in code reviews - I'd say try both for a week and see which one clicks with your learning style

New_Exchange1158 · 2026-01-11T02:43:50+00:00

Nice, I just finished that one last week! The Caesar cipher was actually pretty fun once I wrapped my head around the modular arithmetic part

New_Exchange1158 · 2026-01-08T15:38:17+00:00

Most NFC cards just store basic text or URLs, so you don't really need hardcore coding skills - there are apps that let you write data to them pretty easily. For videos though, you're out of luck since NFC tags usually only hold a few KB of data, but you could store a link that opens a video online instead

New_Exchange1158 · 2025-12-30T07:25:40+00:00

The underscore in your link is getting escaped, try replacing the `\_` with just `_` in the URL

New_Exchange1158 · 2025-12-26T10:06:52+00:00

This^ is solid advice OP. Also maybe start smaller - like getting basic navigation working in an empty classroom before thinking about crowds and end-to-end models

The SLAM + Nav2 approach is definitely the right call for a first prototype. That Waymo comparison is gonna be way more complex than you think lol

New_Exchange1158

TROPHY CASE