I started in hardware, went to web dev, now moving to data science.
1522cd1e4182cc87fa0f69f6cb2248e83cd31c2d289da8fd6a9bb2b5b172fa3c
I'm sure this is not the first one of these in existence, so I'd love to hear any tips/tricks or recommendations/precautions (both for the "developing nation" side and general "public computer lab" side). My personal background is more EE/SWE than IT.
[1] https://www.facebook.com/groups/740055676147398/
One of my biggest struggles is "getting to know" a codebase when I first walk up to it. I'm trying my best to get better, but I have to balance that with actually producing deliverables. It would help radically if a teammate (or better yet, the author!) could spend a few hours with me answering questions, but who has that kind of time! So an LLM wading through a codebase and then being able to sufficiently answer my questions about how modules relate, "what's [thisFunction] for?" and "where's the file that [doesThing]?" and the like would be absolutely something I would pay for.
Anything out there already? Is this an unmet market need, now that we know the tech is up to the challenge?
Also, any ex-con-in-tech related advice is welcome.
It will be used with mostly vanilla JS, pulling data from an in-house (Rails?) API. My familiarity with dataviz is pretty extensive as far as years, but pretty sparse when it comes to JS. I have 2 degrees in Engineering, but <5 years in Web Dev (and <1 attempting data science). Right now the company/customers are super-impressed with just JQuery's datatables, so the bar isn't super high, but I just want to make sure I'm not "that guy" if I pick the worst thing by accident or something.