Ever wondered how to get a real world experience on web development while we are in a learning phase. this article share some of the useful way to ...
For further actions, you may consider blocking this person and/or reporting abuse
What's going on with the line breaks in the middle of words in this article? Makes it really hard to read.
I always start a blog app whenever I need to learn some new rhing on frontend or backend. I covers almost all aspects of a web application like authentication, authorisation, profile/user types and model relationships.
What I find intresting the idea of
making clone appsEx: instagram clone, pintrest clone, dev.to clone, stack overflow clone, trello clone, etc.
May I suggest a different path? Disclaimer: super biased.
Build something that people will use - not to boost your portfolio, but to feel what it's like to have an app in production with real feature requests, and bugs, and deployment environments, and platform limitations, and libraries that work in a different way than you expect them to, and version control, and collaboration with other devs, and - you get my drift.
My suggestion, for a modern, full stack JS application? Build a Shopify app. Check my profile - I'm writing a tutorial series on it now. Did I mention I was super biased? ;)
And if you're up to it, I'd like to show you the ropes and be there for the build process. Just reach out to me at hey@redcaptom.com and we'll set it up.
Remember - you're building software that will be used by people. Train in the wild, not in your sandbox.
Exactly. this is what I want the developers to do. at the EOD, all it matters is what kind of problem we solve for users. I feel, if someone can understand a customer's needs and provide a solution to that. his confidence level will be enormous. Thank you for the feedback. let me know if I can help from my side.
Yes, exactly! I once interviewed for a FAANG company, and the interviewer mentioned the first project a developer puts out there as a "ramp". I really liked that analogy, because it implicitly states that until you've actually done it once - put yourself out there in the cold, that is - you will not get the view from the mountain. And once you're up there, it's very clear where your strengths, your weaknesses, your passions and your pet peeves lie. It's an excellent exercise in figuring out what type of developer you are.
Building something and throwing it on GitHub is like practicing on a punching bag - it's nice, it'll advance your technique, but it's not really the thing that will make you an outstanding fighter.
The real warriors spar (i.e. fight against other fighters) all the time. That's the only way you actually get good at what you do in the real world - you put yourself out there, get punched down, get back up, and repeat ad infinitum. As a former fighter myself, I can verify that the most hardcore folks I sparred with do this on the daily - and they are beasts.
To me, GitHub projects are the punching bag, and real-world problems are the sparring. I urge anyone who is starting to code to dive head first into a real world problem - even if it's fixing a WordPress plugin, which isn't "cool" nowadays - just get to work. See firsthand how software behaves out there, and you will see that a) it's just code and b) you can do it, and you can do it well.
And if you need a hand - talk to us! @ganeshmani and I are here for the assist.
Thanks for the ideas. I will follow those. 👍🙏
Awesome thanks for such amazing ideas!
Editor is a bad UX. sorry for that. i am trying my best to make it readable. don't know why it's like that.
Thank u very much for this valuable information, I will follow this.
Great tips. Thanks a lot