Youtube comments of Vincent Jenks (@VincentJenks).
-
156
-
132
-
42
-
30
-
22
-
19
-
19
-
14
-
Russia was doing exceedingly well economically, and developing strong ties w/ the west through gas and oil markets. There's no reason that they could not have continued in prosperity and peace, in this manner, and positively influenced Ukraine with investments and other economic stimulus. They didn't need to invade, kill, rape, and destroy everything in their way to achieve regional dominance. If they had only used the power of the market to achieve their goals, they would have won the hearts and minds of their neighbors, and created the kind of buffer they seek. Instead, paranoid of the west and NATO, which has never invaded or even directly threatened Russia, they took the the path of brutality and death...once again. It's as if they can't evolve socially past their violent imperial past, when the rest of the world has. The west would have welcomed, and WAS welcoming an open and economically cooperative Russia, and now they have ensured at least a generation of distrust, and has lost access to the world's biggest markets. This brutal and senseless war will have only cost them a great deal of lives, and their economic future. Such a tragic, pointless waste.
9
-
5
-
5
-
4
-
4
-
4
-
4
-
4
-
4
-
3
-
3
-
3
-
3
-
3
-
3
-
2
-
2
-
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
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
1
-
1
-
1
-
1
-
I've been a developer for 26 years now and in leadership, in one form or another, for the past 15 or so - never fully becoming a "manager who doesn't code". I love to write code and I love the creativity I'm able to express with this profession, but you hit the nail on the head - the industry has all but ruined the profession, starting with Google. Between every job I find myself spending countless hours re-learning all the things I had to memorize last time on the treadmill, which rarely get used in everyday software engineering to solve real-world problems. Algos, obscure data structures, 0(n) notation, mega-enterprise systems design, and a whole host of other things that only serve to get through interviews. This is why most of this stuff is useless in finding a great engineer! Add to that; as the market heads into another recession and layoffs have injected far more supply than demand, getting hired today is a truly painful, harrowing experience. I don't want to be a pure manager but the fantasy that I could, while also keeping my chops up while working on personal projects, is creeping into my consciousness more and more. The industry seems broken and I love people, love being in leadership, and am confident that I can definitely do the job well - I'm just not sure I'd be content. At that crossroads, for sure!
1
-
1
-
1
-
1
-
Great reminder that engineers are gonna over-engineer. Even senior professionals are often too quick too chase the shiny new hotness, and do whatâs trendy. Monoliths are fine for far more than they get credit for, and usually a good way to start a project, at the very least. Keep design and tooling simple, and minimalistic, with the idea that you might break the monolith up, later on.
Weâre drowning in trends, tooling, configuration, overly-complex architecture, and general over-engineering. Very few of us are building anything that requires all this stuff. Weâre not all Google and Amazon!
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
Another thought: One of your points is burnout from learning new tech. One thing I've avoided in my career, and always advise younger or aspiring devs to do, is to carefully consider how you invest your learning time. Time is money, and time, like money, should be wisely spent. You wouldn't willy-nilly invest a few pennies of every dollar into a bunch of assets of highly questionable or unknown value - at least I hope you wouldn't. So, like material investments or substantial new purchases, you'd do some research into what the market is doing before investing your hard-earned money. Usually, I hope. I've been careful to only invest my time into technologies that I know are valuable on the market and will have staying power. Too many devs I've met will hop around from one stack to the next, framework to framework, and so on. Every other day they're touting the new JS framework, or a new ORM, and converting entire codebases. All this tech does essentially the same thing. We're mostly just creating CRUD that we publish to other computers. I think it's a sure recipe for learning burnout if you're trying to learn it all, and you'll end up frustrated and only lightly skilled in any one thing. A jack of all trades and master of none. Focus and depth is better, IMO.
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
Call me old school, but Iâm struggling to see the advantages of a monorepo. Less tooling and flexibility is a good thing, and microrepos scale better, IMO. For most projects, shared code, like utility modules, can simply be referenced via npm, or whatever package manager youâre using. Regardless of approach, good documentation, management, and communication cannot be optional. I feel like we devs are drowning in configuration and tooling these days, and itâs wise to avoid any complexity that you can.
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
-
1
-
1
-
1
-
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
-
1
-
1