Comments by "Vincent Jenks" (@VincentJenks) on "Fireship"
channel.
-
22
-
4
-
This made me lololol. I've been building web apps since the late-90's and while the user experience has gotten better, the developer experience, especially if you insist on being fullstack, has become a world of hurt and misery. Looking for a job right now? Good luck, even if you have cutting-edge skills...but regardless - have you seen the skill requirements!? We're buried in frameworks, frameworks for frameworks, configuration, configuration for all of your configuration, cloud services, deployment, DevOps, DevSecOps, and every manner of trendy thing that requires you to sleep once every 3 days, so you can spend most of your life in front of a screen, trying to keep up. For what? CRUD. The internet is still just CRUD.
The conclusion was great, though I'd go with an AWS serverless stack, just due to it being better for your career. JS - React, Lambda, Dynamo, wrapped up with the CDK, in a single GitHub repo, will scale to most things you'll ever write and give you a skill set that best benefits your career. All the bits therein can be learned quickly and swapped in/out as needed.
2
-
2
-
2
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
It's unfortunate that the era of the WYSIWYG seems to have passed. Both of these frameworks would benefit greatly from it, IMO. It's ancient technology now, but both C#/.NET and Java worlds embraced rapid application development with visual layout tools, which were truly awesome. Before mobile, I did a lot of work with the .NET Compact Framework (yes, I'm old, you wacky code school kids ;) and desktop w/ WinForms and Swing in Java. You could drag/drop widgets into place, set styles and properties, and mostly concern yourself with building the application...quickly! Hell man, even Dreamweaver was a huge timesaver for mocking up web apps, at the outset of a project. Where my WYSIWYG gone? :(
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
While this is interesting, I'm always wary of these layers-upon-layers of magical abstractions. All cost concerns aside, which can easily be controlled and aren't the boogyman man of the comments might suggest; you're not learning enough about the underlying infrastructure you're maniuplating. All abstractions come with this cost. Even with CDK, which I've adopted and started using because you need some sort of IaC tool for automation, you've got to understand what's happening under your code. To me, if you're strictly AWS, CDK is the way to go, and adding another layer on top of that might be easier, but you learn and understand less of the consequences of what you're executing.
All that being said, we're mired in frameworks, built atop frameworks, embedded with endless layers of abstraction and configuration. There's a shiny new toy every-other-day. You can chase your tail around for years and never settle on "THE stack"...and all of these toys achieve the same thing, in the end. At what point do you select "the best" tools and stick to them for more than a few months, or even a few years?
As neat as this is, I prefer to stay as close to the "bare metal" as possible, while accepting that the market will push you into certain things that you have no choice in adopting. Keep it as simple as possible, even if it's more difficult and requires a little more code and understanding. These frameworks come and go, seemingly overnight. If you stick to strong fundamentals and as few abstractions as possible, you'll waste less time and build more stable environments.
1