How to a become a Full Stack developer? I'm studying for a course at Udemy, The Web Developer Bootcamp. Also, I'm learning Python from a book (back end). I know a lot of things really are missing, but is that a good start? What to do before??
Python book: souravsengupta.com
Other urls found in this thread:
eloquentjavascript.net
netmarketshare.com
twitter.com
Listen to all the trendiest podcasts and hook into to hottest communities of like minded creatives.
Bump.
Man, I sure hope this is ironicposting.
...
Castrate yourself.
Anyways, friend, you don't EVER want to work in IT-- trust me. At my last job the noxious stench of Indian BO WOULD HANG IN THE AIR EVEN IF NOBODY WAS AROUND. Only get an IT job if you're going to be around white people. (In all seriousness though-- the real reason to avoid IT is that everything you know will be useless in 5 years, perpetually. It's very frustrating.)
Kill me and then kill yourself
Learn HTML, Javascript, PHP, Python
If he wants full blown aids, he should just stick to javascript. MongoDB, JS backend, and JS client side rendering framework.
Yes, those technologies are the toolsets used for "full stack development". Try as he might, I have a sneaking suspicion that he'll never complete a course that covers all this by himself.
If they wanted people to sign up, why would they choose an ugly nigger face?
Convenience
They don't want people to sign up by looking at that.
They know normalfaggots will sign up and thus use the space available for social engineering.
Learn Rails and React
Probably why the nigger has glasses. Oh he so smart!
Full fag*, you already met the requirements
Why would you want to do that? That's usually some place people end up, not as a forethought. Just finish your courses and get a job doing backend if you can. Frontend work is something everybody dabbles in, so you'll get experience in that over time almost regardless of what you're doing.
Javascript dev is is growing much faster than jquery is. The number goes up, but the proportion goes down. This is case for a bunch of libs/frameworks. There are some blogs on npmjs about this if you are interested.
Reminder that Cash, Zepto, Umbrella, Underscore etc. are doing the same job as jQuery, not to mention ES6 is making these obsolete.
I only use twitter to view Trump's tweets and I'm seeing that shit now. I hate silicon valley so fucking much.
The bare minimum you need to get a job anywhere you can work on the full Stack.
Seriously, companies are absolutely THRISTY for anyone halfway competent and absolutely GIDDY when they hire someone who actually excels at their job to the level were they can work full-stack.
Most new developers today, even graduates, will swear under their breath and struggle when asked to write simple things in a web app. You really just need to be above par to excel.
In terms of specific technologies to learn, it doesn't matter so long as your learning the WHY of what your doing.
Just pick whatever, start writing full-stack toy apps, swap out shit you don't like, be conscious of what technologies solve what problems and their approach, and get to work.
Also goes without saying, but go beyond crappy Medium articles when your look for resources. Look at the docs and work done by actual developers first.
This is cringe
I don't know about that, but either way, if you had to learn just one JS library, it would still be jQuery. JS frameworks are still in a high state of flux; it's good to pick a technology you can be functional in and wait for the dust to settle. I'm sure as fuck glad I didn't invest mindshare in Angular 1 when that was the flavor of the day.
I'm personally waiting for the whole WASM thing to obsolete TypeScript et al.
learn zero. eloquentjavascript.net
document.querySelector() has been in the language for a good while now. jQuery is ogre.
I would prefer to write this:
// works with all browsers, btw$.getJSON('/my/url', function(data) {});
Instead of this:
// doesn't work with IE < 10, btwvar request = new XMLHttpRequest();request.open('GET', '/my/url', true);request.onload = function() { if (this.status >= 200 && this.status < 400) { // Success! var data = JSON.parse(this.response); } else { // We reached our target server, but it returned an error }};request.onerror = function() { // There was a connection error of some sort};request.send();
The API is just nicer, and it still provides a nice normalization layer on top of browsers. It's not just about DOM queries. There's also a rich plugin ecosystem, especially jQueryUI. It's a rather small dependency as well, so I don't see the drawback of using it.
This you won't learn shit at uni and you'll just waste your time. Teach yourself.
Are you brain dead retarded? The fetch API has been standard in the language for several years now.
The question is: why wouldn't I use jQuery as a full-stack developer?
1. use a real language and compile it to javascript (Elm, ReasonML, Nim)
2. use JavaScript and, if you pull in a framework, pull in one that punches above its weight and doesn't suck (Mithril)
Have you ever actually used e.g. JavaScript-compiled Nim? Go ahead and write "Hello, World!" in Nim, compile it to JavaScript, and post back with the results.
It literally doesn't work for any version of IE, and only partially words for Edge. Hell, it can't even deal with blob objects on all browsers. That's the quintessential file abstraction used in the browser, and it only works for 3/8 of the browsers listed! That's pathetic. Guess what? Works with jQuery!
No thanks. Being a full-stack developer means you have a lot of languages and frameworks competing for space in your mind. Learning the trendy framework of the day for the browser is a waste of mental real estate. Proper OOP in JavaScript, combined with jQuery is fast and efficient, and works across browsers.
nope. Nor Elm, nor ReasonML. I've looked at ATS compiled to JS though, and the runtime was a lot smaller than jQuery.
What I've done in my projects is still #2, of the options I gave.
>any version of IE
so yeah, 0.0.0, and 0% of your customers. I'll grant that it's nice to be able to tell your boss that you definitely haven't excluded anyone.
crossing the dom/javascript boundary as frequently as jQuery must do will always be more expensive than working with a vDOM and rendering it with it a diffing algorithm.
Of course, because it doesn't provide any of the benefits of jQuery.
Also,
3+% of that is IE, and it's IE 11, not exactly IE 6.
netmarketshare.com
I'm seeing estimates between 10-13% marketshare for IE+Edge. Even best case scenario, Edge, you're talking about a failure of the Fetch API to work with blob objects, which is unacceptable.
Top tier b8 thread, bumping for how perfect this is.