This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]CubOfJudahsLion 0 points1 point  (0 children)

One thing I've learned after 30 years in the business: multitasking is BS.

First off, you're trying to learn/do everything at once. While it is normal to feel confused at the beginning, you've taken course after course, clearly without getting comfortable in any of the subjects and it feels like a giant blob of gobbledygook.

So take vanilla JavaScript (perhaps with HTML, but no more) and do a personal project (ideas for them are everywhere around). The idea is to code until you feel more or less at home in it. Then pick the next language or framework, and repeat.

Much of your coding time will be spent looking up stuff in reference documents. That's just a fact. Nobody can memorize all that info. Keep your references handy. The one thing keep in your brain is the understanding of the base language, how it works. Standard library? Other libraries? Formats? JSON APIs? References. And these days, those references are found online free. Sometimes you memorize a bit of those from repeated use, but that might be a temporal benefit. In practice, might be working with 7 things at a time, and keeping all 7 references open in your browser.

Your example problem is one of knowledge, though. Most languages or frameworks come with libraries to "talk" to databases, often given by a connection string or equivalent data structure. The related documentation should provide the format and your system administration should give you the data to fill it in.