Why the Full Stack Engineer Is Problematic

But honestly, the BEST thing about this industry IS learning new things.
The pace of change is what it makes it so great.

I didn't like React. CRA is an abortion of a project. Redux is a horrible pattern/DX.

But I have been revisiting React, because it makes sense from a business and recruitment point of view, and the state of React in 2022 is amazing.
Next.js and hooks solve everything that I disliked about React.
And building a Next.js apps was trivial, as I have built many Nuxt.js apps.

Framework wars initiated: I do still think vue is better :X3:


I personally want to learn everything, touch everything.
Rust, OMG amazing - probably not going to make it a tech in my company though.
Jack of all trades/master of none is such a BS expression. Having knowledge of different patterns/implementations from different systems/technologies is what makes you a master of SOFTWARE DEVELOPMENT.


But again, it's down to your brain/personal capacity.
Some (most) people will just be average/fine at their job, and that is OK.
I'll continue investing in myself, knowing a lot about a lot, and a little about a lot.
 
_kabal_ said:
But honestly, the BEST thing about this industry IS learning new things.
The pace of change is what it makes it so great.

I didn't like React. CRA is an abortion of a project. Redux is a horrible pattern/DX.

But I have been revisiting React, because it makes sense from a business and recruitment point of view, and the state of React in 2022 is amazing.
Next.js and hooks solve everything that I disliked about React.
And building a Next.js apps was trivial, as I have built many Nuxt.js apps.

Framework wars initiated: I do still think vue is better :X3:


I personally want to learn everything, touch everything.
Rust, OMG amazing - probably not going to make it a tech in my company though.
Jack of all trades/master of none is such a BS expression. Having knowledge of different patterns/implementations from different systems/technologies is what makes you a master of SOFTWARE DEVELOPMENT.


But again, it's down to your brain/personal capacity.
Some (most) people will just be average/fine at their job, and that is OK.
I'll continue investing in myself, knowing a lot about a lot, and a little about a lot.
Click to expand...
Fair criticism. React before they switched to functional programming was an absolute dog to work with.

Redux is fine once you train yourself and others to handle application state correctly. Applying structure like the duck pattern to it really makes it quite nice to work with.
https://github.com/erikras/ducks-modular-redux
 
_kabal_ said:
But honestly, the BEST thing about this industry IS learning new things.
The pace of change is what it makes it so great.

I didn't like React. CRA is an abortion of a project. Redux is a horrible pattern/DX.

But I have been revisiting React, because it makes sense from a business and recruitment point of view, and the state of React in 2022 is amazing.
Next.js and hooks solve everything that I disliked about React.
And building a Next.js apps was trivial, as I have built many Nuxt.js apps.

Framework wars initiated: I do still think vue is better :X3:


I personally want to learn everything, touch everything.
Rust, OMG amazing - probably not going to make it a tech in my company though.
Jack of all trades/master of none is such a BS expression. Having knowledge of different patterns/implementations from different systems/technologies is what makes you a master of SOFTWARE DEVELOPMENT.


But again, it's down to your brain/personal capacity.
Some (most) people will just be average/fine at their job, and that is OK.
I'll continue investing in myself, knowing a lot about a lot, and a little about a lot.
Click to expand...
Jack of all trades master of none, is real. There is too much too learn and its increasing. Specialization is the way to go. Yes its good to know about a lot of tech, but being a specialist in a new in-demand tech is better than knowing a little bit about everything. Full stack is an old school concept, specialization and mastery is now the in thing.

All those JavaScript frameworks:sick:, Blazor:love:
 
Benedict A55h0le said:
Jack of all trades master of none, is real. There is too much too learn and its increasing. Specialization is the way to go. Yes its good to know about a lot of tech, but being a specialist in a new in-demand tech is better than knowing a little bit about everything. Full stack is an old school concept, specialization and mastery is now the in thing.

All those JavaScript frameworks:sick:, Blazor:love:
Click to expand...
depends on the person I guess.
any tech that I work on in production, I will be a master of it in a couple of months at most, in as much as I am able to be highly productive, and be able to support it.


Blazor really is nice (I have built 1x small, approaching medium .NET 6 Blazor WSAM project) but honestly the DX has a way to go to match HMR.
It might be slightly better if you use Windows with VS2022 (they have their special hot reload debugger), but I am not going to do that :p
Keen to see where it goes with .NET 7

What IS a great DX for Blazor WASM is using Nswag code generation to build HTTP clients from your OpenAPI file.
 
konfab said:
Fair criticism. React before they switched to functional programming was an absolute dog to work with.

Redux is fine once you train yourself and others to handle application state correctly. Applying structure like the duck pattern to it really makes it quite nice to work with.
https://github.com/erikras/ducks-modular-redux
Click to expand...
Yeah, I havent really got to the "how to solve application statement management" part yet.
I should probably move this to ZA-tech, but is there a currently accepted "best practice"/implementation?
Not talking about component level "data" aka "useState", but more global state/store. Is it just redux?
 
_kabal_ said:
depends on the person I guess.
any tech that I work on in production, I will be a master of it in a couple of months at most, in as much as I am able to be highly productive, and be able to support it.


Blazor really is nice (I have built 1x small, approaching medium .NET 6 Blazor WSAM project) but honestly the DX has a way to go to match HMR.
It might be slightly better if you use Windows with VS2022 (they have their special hot reload debugger), but I am not going to do that :p
Keen to see where it goes with .NET 7

What IS a great DX for Blazor WASM is using Nswag code generation to build HTTP clients from your OpenAPI file.
Click to expand...
You agree with your attitude but depending on the tech, a few months might not be enough to master it.
 
_kabal_ said:
Yeah, I havent really got to the "how to solve application statement management" part yet.
I should probably move this to ZA-tech, but is there a currently accepted "best practice"/implementation?
Not talking about component level "data" aka "useState", but more global state/store. Is it just redux?
Click to expand...
Redux is the most common, but people abuse the hell out of it.(Two of our applications suffer from this, because previous devs decided to use Redux and a package called API middleware to fetch stuff from the backend.)
You have to actively think to not put stuff in global state via redux, as Redux makes it very easy and safe to use global state.
 
noxibox said:
This in a nutshell is exactly what is wrong with that industry. You're expecting people to spend the little time they have available for not working on working.
Click to expand...

I don't think it's a problem in the industry at all. No one is forcing you to spend the hours to become specialized/outpace your peers. Also, there are definitely companies out there that do well to help with their engineers/developers upskilling, you just need to find them, which is your choice.

PS: There's no "expectation" that you must spend your personal time upskilling. But it's certainly advantageous.
If you don't want to get into that sort of thing, don't get into the profession or be content with what you have.
 
My problem with companies wanting full stack devs is that the combinations of technologies leads to an infinite number of "full stack dev" profiles. Front-end: Vue/Angular/React/Something Else, back-end nodejs/ python/ C#/Java/Scala/Kotlin, databases MySql/ Postgress/ MSSQL/ Mongo/DocumentDB and what have you.

And then the companies complain they can't find enough full-stack devs (with "experience") with their mix of technologies. If they want to mix-and-match technologies and insist on experience with their particular mix they shouldn't try and full stack devs -- they should rather just get specialists in their area.

I am much more comfortable on the data and back-end side and probably can do functional user interfaces but it would most probably be uninspired :-)
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X