Pic related is about the level I can code at no lie
In a year or less I want to be contributing to legitimate/important Github repos like JS frameworks, open source web apps with real user bases, etc
Teach me how to be an open source neckbeard Zig Forumsnessmen
People told me get really fucking good at JavaScript (with books and doing all their exercises) and read repos/docs until I know what's going, then open PRs for small shit
Would you guys do anything different?
learn at least ES6, read about the nodejs ecosystem, learn some react/vue and start with small pull requests
I don't understand, that pic is like level -1 of coding
Can you suggest whatever additions you like or does that make you look like an idiot? There's supposed to be a roadmap or something right? Or maybe not depending on what it is
Suppose you get one commit in, can you start reaching out to the members and ask for some directions or is that thirsty?
...
You're going to want to be comfortable with the command line and know git. Get these free books
Bro /g/ is slow as fuck and biz gets more of the legit working at big companies tech crowd
G is consoomer technology and web dev kiddies (I am one myself) central
HTML ISN'T CODING
Is JSX in React coding?
Is Github just self explanatory after learning git?
You will never contribute anything to open source user. You have to be a turbo autist to get any good at this shit. You don't have "it".
yes
github is just a site for hosting git repos, it has nothing to do with git itself
Get familiar with build tools, using node, webpack etc. Learn at least 1 SPA framework properly (I'd recommend Vue) & since Javascript itself is kinda shit & unsafe, I'd recommend Typescript or something else that's transpiled. Also really master SCSS - most devs are dogshit at design & making stuff look good, yet that's all VCs & businesses really care about when you're looking for funding or whatever. Apart from that, yeah - contribute to open source projects and just build a portfolio of work up.
Bro how hard could it be? I theorize it's about the same skill bar as working at big tech companies, and I've seen many midwits achieve that
The only difference is you don't have a manager and onboarding experience like you would if you started working for Facebook
What do you need webpack for?
Fix a bug first
Generally when you use these things you'll stumble upon some issue or annoyance that can be fixed
How did you learn to navigate github though? And how do people analyze the code usually, on their machine or via the web interface? Some of these projects are like several GB and change by the day, I suppose one would normally sync their local copy to the repo like it's a Dropbox folder or something right?
kek, nice bait fag.
>muh html code. how leet am I?
Gotta start somewhere
it's pretty simple, you just go to peoples account and you can see the source code for their projects. If you want to dive into a project yourself download (clone) the repository and view it in an IDE.
It's basically like navigating your file system on your computer. Except you can see the file history. I wouldn't try to grasp big projects until you get a sense of how small ones are laid out and you're familiar with commit history and branches
It builds and manages your assets.
Read this for context
medium.com
HTML isn’t programming. It’s a markup language. There a big difference.
I have starting working on a dapp as my first bug project my experience is mostly with python
I have learned some solidity and have decided to jump in at the deep end
is this retarded? I have a good idea and these devs are thirsty for dapps to be built on their network
Whatever you do OP don't accept any job offers in tech. I can't wait to be done with the following gay shit for the rest of my life.
>daily scrum
>sCrUM MaSteR
>emails that start with "Team,"
>Please re-organize your scrum tasks and follow the proper hierarchy. THE TASKS MUST BE BELOW THE EPICS. THANKS, John.
>Business requirements changed and we'll have to redo that feature you spent all month on. It needs to be done by tomorrow
>Automatic merge failed; fix conflicts then commit the result.
>Technical specification documents that are all text
>Design specs that only describe one scenario
>What's your estimate for this task user?
Html is a markup language, not a coding language. It marks various elements to be interpreted by code but in itself it contains no logic.
and then you have fags like this that argue semantics for the sake of semantics. be prepared to deal with that bullshit if you ever decide to wage as a dev
Sounds fucking gay man
I am going to work in tech eventually, I hope open source gets my resume look at by good companies so I don't have to pay my dues at local shitter companies that make point-of-sale software and pajeet stuff like that
No, it's a great idea. Lotta noob devs waste too much time just doing tutorials & obsessing about the details of code itself (including me when I was learning). Start doing projects ASAP, just literally Google shit & copy paste from stack overflow if you get stuck. If you understand the problem in enough detail, the code really will write itself. So go through the full life cycle of gathering requirements & planning, creating wire frames (so you don't waste time building something that looks dogshit), setting up CI/CD & your infrastructure etc. Yes, you're going to fuck the first project or 2 up - but that's fine. You'll quickly realise what you need to work on & can then learn more. Just get the fundamentals down & go nuts.