3 ms·
It’s frustrating to try to be helpful for someone with a degree that says “Documentation are hard to follow”. Maybe you chose the wrong field? Start with a sin
by inphovore 4y ago
It’s frustrating to try to be helpful for someone with a degree that says “Documentation are hard to follow”. Maybe you chose the wrong field?
Start with a single isolated component, say a simple static react single page web page.
Make your own website that shares some very basic interests you have.
Get that up on a service (maybe an AWS free tier or something.)
Then do something a little more complex, like create a fake/demo store front that sells pictures of goats or something.
Keep doing new isolated projects for yourself one piece at a time until you have at least enough experience to be helpful to someone else (like a relative who wants help putting together their own website, or a Craigslist gig project, etc.)
The secret to being a successful developer isn’t writing everything from scratch. It is finding an open source project that mostly does what you need and adapting it for your purposes.
And btw, I would avoid mongoDB unless that is something you know you will need. MySQL is more common and versatile, though everyone will say that about their go-to datastore.
- shivajikobardan 4y agoI don't see why it's wrong to accept documentation are tough to read for beginners. Maybe degrees from USA are so good you can read docs easily after getting them. They're not that good out here. I used to read books instead of RFCs to learn. But later I'd use RFCs to solve my confusions while learning networking concepts. That's the way. I'm stuck at the first phase. I'm just copying pasting code(typing), not learning anything. I fix an error I learn sth but getting the big picture is tough. A resourceful resource that covers theory behind what's happening could be of great help in this case but I'm not finding one. Books get outdated fast.