Earlier quoted context omitted.
If your career can be significantly affected by devs fresh from bootcamp, you probably need to sort out your own issues than to complain here mate.
If your career can be significantly affected by devs fresh from bootcamp Well, there are certainly problems if that's the case. But it's not necessarily senior ICs that are the problem. I've experienced a few companies where "boot camp yahoos" wound up essentially running the show to ruinous effect. Why? They had numbers, essentially, and management was too hands-off to prevent it. To give a specific example: we had…
Things I wish I knew before moving 50K lines of code to React Server Components
511–520 of 540 posts
Re: Things I wish I knew before moving 50K lines of code to React Server Components
#512Stop a second before you go into RSCs. Whatever you want to achieve ultimately is much easier/quicker/scalable done in real fullstack (or classic web-) frameworks! Rails/Django/Laravel/… + Turbolinks/Htmx/… or even sprinkle some light clientside JS for fancyness. Or go best-of-all-worlds if you happen to know Elixir/Phoenix. But don’t continue the descent into RSCs, now matter how many people tweet about it. These fo…
Indeed, RSC reminds me of CORBA [1]. CORBA is a way to mix local components with remote components. CORBA is very mature and works in many languages. So why doesn't everyone use it? I would guess that most developers today have never even heard of it. Why is that? I would suggest that anyone who wants to invent another distributed component architecture should study CORBA and its descendants and why they have never r…
It's an over engineered overly complicated design that leaves a lot of crucial stuff undefined, which made interoperability impossible. From a performance perspective it was crap. And debugging an implementation was almost impossible.
It's a great example of how architects can destroy a good idea by layering ridiculous amounts of abstraction into an incomprehensible pile of software.
And it shows that architecture without implementation experience should never happen.
Re: Things I wish I knew before moving 50K lines of code to React Server Components
#513Earlier quoted context omitted.
This is why web development (and python, don't get me started on the pain that is python) is not for me.
What do you code in? For any language if you don't have the toolchain set up, obviously it'll seem laborious to install it, it's not a knock on the framework used on top of the toolchain.
Re: Things I wish I knew before moving 50K lines of code to React Server Components
#514Earlier quoted context omitted.
Or just don't even bundle if you can serve your users with ES6 modules.
Performance with native ESM isn't great since you get cascading requests, unless you have very shallow dependency trees.
For general performance you can cache the modules using a service worker.
In any case they are fine for most use cases.
Re: Things I wish I knew before moving 50K lines of code to React Server Components
#515I'm old enough to remember when servers rendered everything and you used CSS and Javascript to enhance the pages after they were rendered. The web is in such a dark and overengineered place. It's almost unbelievable. It's why my approach to building apps is server-rendered first and then enhanced after the fact.
As a different perspective, I'm also old enough to remember when CSS and Javascript were invented , and I've been making websites since that time. IMO web dev has never seen better tooling than today, and user experience has improved tremendously over the years. What we used to call AJAX has grown from a neat side toy to a basic part of everyday life in the form of client components and SPAs. The server is still as p…
Re: Things I wish I knew before moving 50K lines of code to React Server Components
#516Earlier quoted context omitted.
It's not React's fault but the ignorance of the average React dev never stops surprising me. From using divs for buttons or links to this.
Yeah modern JavaScript frameworks heavily discourage semantic markup, and I’m salty about it.
Re: Things I wish I knew before moving 50K lines of code to React Server Components
#517Earlier quoted context omitted.
Please help the guy before he gets too far along. Some of us might have to work with him. Seriously though, I saw someone described as a 22 yr old software engineer in an article. There is a better term: "Software Engineering Apprentice"
Unionize already. It's not just about wage, it's about assigning appropriate work to peoples level and having them progress through the most efficient steps to mastery while also completing billable hours
Re: Things I wish I knew before moving 50K lines of code to React Server Components
#518Earlier quoted context omitted.
It's not React's fault but the ignorance of the average React dev never stops surprising me. From using divs for buttons or links to this.
I think a big part of the problem is how online education and bootcamps/college degrees for web-dev are structured. Often times people are so overwhelmed with the stack they are supposed to learn that quite obvious and important stuff gets lost. People just try things out until it works without understanding the underlying structure. If you come from a simpler MVC framework like Rails or Laravel, it enables you to fo…
Re: Things I wish I knew before moving 50K lines of code to React Server Components
#519Earlier quoted context omitted.
yeah, i'm not google of facebook or ny times or whatever, i'm a lone dev in montana what other options did i have?
People don't realize that many of the dev tools they use they are using more because of the large marketing reach of those dev tools than any objective decision to use the tool. Entire companies have been built around the premise of good developer marketing, and if you're faang, you simply get to impose whatever developer trends you want to see in the market. I'll never forget how wildly popular Stripe became overnig…
Re: Things I wish I knew before moving 50K lines of code to React Server Components
#520Earlier quoted context omitted.
If your career can be significantly affected by devs fresh from bootcamp Well, there are certainly problems if that's the case. But it's not necessarily senior ICs that are the problem. I've experienced a few companies where "boot camp yahoos" wound up essentially running the show to ruinous effect. Why? They had numbers, essentially, and management was too hands-off to prevent it. To give a specific example: we had…
You describe the scenario I am complaining about. These boot camp developers do not have the background for large scale engineering, yet get cast into it side by side with real seasoned engineers. However, that real seasoned engineer is a small fraction of the "dev team" and gets overwhelmed by the boot camp developer's group thinking - their opinion is just as good as the guy with the CS degree they figure, after al…
However, that real seasoned engineer is a small
fraction of the "dev team" and gets overwhelmed
by the boot camp developer's group thinking -
their opinion is just as good as the guy with the
CS degree they figure, after all, their boot camp
crowd seems to win the debates!
Oh my god. So true. Heaven help us.