For example, "Chart.js" makes it really easy to create beautiful charts in a web app. Because of tools like that it's much easier to learn how to build a feature rich app now than 20 years ago.
Still, the guy who can create "Chart.js" (an artist) should be getting paid a lot more than a guy who can only use it (a craftsmen).
Why? One without the other is pretty pointless. I can accept the roles are different but not that either is particularly harder.
It's one thing to code what you see in front of you, another to think about problems and solve them thoughtfully, research, debug, and etc. Troubleshooting(debugging) in particular is a hard thing to learn.
As coding difficulty drops, and supply increases, the net effect will be a much higher demand for jobs than supply. And that's exactly where big tech wants it to be.
edit: here comes the javascript developer downvotes.
I actually love it when a developer says something like this, because it tells me way more than even 2 full days of pairing or interviewing could: They know absolutely nothing about software at scale, and are probably extremely arrogant to boot.
It informs me that you're probably a JQuery developer, personally offended because you believe that your work is incredibly advanced and challenging. In reality, what you do is probably some of the easiest "coding" to have ever come to fruition. Yet, you toss out the "at scale" comment ad nauseam because you think it'll make you sound important.
Just by the fact that you denounce anyone who recognizes the simplicity of it modern development tools shows me you probably fail to recognize the simplicity yourself. Or you don't want to admit the simple fact that programming has gotten much easier. That's been intent of so many modern languages, yet we're always going to have someone like you who claims we all don't know what we're talking about because we've never built anything "at scale".
Your 10,000 hits / day blog isn't "scale" buddy.
Edit: Also, I'm not your buddy, pal.
Jokes aside - the biggest error this software developer makes is not realizing that software is not the crtitcal part of AirBNB success. It is the thousand manyears of boots in streets promoting the app and getting people onboard.
It's classic expert talk, "oh, that's easy." Perhaps to you :)
Sorry is this a joke? Because I'm missing it.
- crashes under load,
- cannot scale to even 5% the traffic,
- doesnt have all the myriad required compliance and transnational side systems
- has underinvested in accounting and all support systems
- is un-maintainable, etc. etc.
And that is when serious businesses realize you get what you pay for and that you need to pay for real experience to real systems.
Yeah, that could definitely happen. /s
1. Enzyme, the current top used React testing library 2. NVM, kind of the only game in town for managing node versions 3. qs, a tool for converting search to json objects and back 4. tc39 proposals, the committee that determines new JS features
This is all in addition to his developer work at Airbnb. I would like to see a high schooler have that kind of maturity, drive, and focus.
You've drawn attention to an Airbnb engineer with a bunch of other interests that don't seem directly related to the infrastructure behind the company. I'm sure they use these things, but they aren't going to be critical to the success or failure of the site. That suggests the technical challenges of Airbnb aren't enough to keep someone with a large amount of maturity, drive and focus busy and interested.
Anyway it's important to note that coming up with the business idea and then executing it well is kinda where the money comes from, not from the app itself per se. A business may have a website; it might even use a web app to deliver its core business value; but having a website or web app doesn't necessarily mean you have a business.