Well first I thought horse is abstraction that you can't be good at both things so "full-stack" means you're going to show some real disadvantages of yours in one or both fields when projects get tough, which does not even have to be true. You could be great at both design and programming but I think there's really small number of people who actually do it good.
A quick intro in my current status and why I may be relevant. Worked with too much technologies and some jobs were back only some were full-stack. This is the first company where I think I might be best at backend because other folks don't care about architecture nor patterns nor anything and I don't think it's always necessary to do so but... When I talk to some old colleagues they know so much about backend development that I always feel like I'm dumb. Now I got into backend because we worked as a team of 4 on project and we split at the beaning on front and back teams. Main thing was that front, were guys did amazing job, left clients amazed so other colleague and I had to do whatever just to make the thing work fast and comply with front. Reason of success was that we collaborated all the time. Reason for me being on backend was that I suck at CSS and know too little about Angular. Next project frontend guys asked to stay split in terms of having front and back tasks separated because we got USED TO and warmed up with tools we used and thus it was faster and easier. And we COMMUNICATE A LOT to keep things going. I admire what these people do at front as it's too hard for me.
Now having experience from before, you make everyone full-stack, some mess up the back because they're not good at it and some even don't care about it but it's in their job description, and some mess up frontend because they hate it or think it's writing scripts, or it's works like backend.
Then I guess it's either my experience were full-stack means full-mess because people cannot organise well in those situations or it's only fit for certain projects were front is simple or back is just simple CRUD and team excels at one. Or maybe people have luck working in teams where there's actually great developers who know both ends reeeeeeeally good.
Just for the reference on how stuck I am and think devs should focuse on one thing here's a list of technologies that I can remember working with in _6 years in __11 companies so far: Java,Spring,Seam,Hibernate,Oracle 11g, C#,.NET Framework,.NET Core,EF,EF Core,SQL Server, ColdFusion, PHP,CodeIgniter,Laravel,Wordpress,MySQL,MariaDB NodeJS,express, MongoDB, Scala, AngularJs,Angular5/6/7,React and at least 20 testing frameworks and tools.
Believe me you should keep at one thing at least for 2 years before the switch to be good at something and to keep your mental health stable :D
Thank you for the interesting and detailed perspective. Yes, it’s much harder to be a full stack team when the technology is painfully diverse. Maybe I’m spoiled from doing NodeJS where it’s all javascript everywhere (well TypeScript actually because I work at a large enterprise (and also I think TypeScript is great)).
So yes, it clearly depends on the situation, the team makeup, and the willingness of each member. I’m happy that you’re focusing on conversation. :)
Of course NodeJS you can be there full stack. It's JS and TS but still it's only JS with addons :D. Toyota some time ago replaced robots with humans. Why? Because PEOPLE learn not robots(took this from Jim Coplien) and key to success is HUMAN resource. And to work on something we need to COMMUNICATE.
Please watch this to understand what's happening to people and why they step on others: youtube.com/watch?v=jobYTQTgeUE . It's about too much ego guys working around you and it's frustrating if you focuse on that. Or you could go well they have issues with themselfs God help them.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Well first I thought horse is abstraction that you can't be good at both things so "full-stack" means you're going to show some real disadvantages of yours in one or both fields when projects get tough, which does not even have to be true. You could be great at both design and programming but I think there's really small number of people who actually do it good.
A quick intro in my current status and why I may be relevant. Worked with too much technologies and some jobs were back only some were full-stack. This is the first company where I think I might be best at backend because other folks don't care about architecture nor patterns nor anything and I don't think it's always necessary to do so but... When I talk to some old colleagues they know so much about backend development that I always feel like I'm dumb. Now I got into backend because we worked as a team of 4 on project and we split at the beaning on front and back teams. Main thing was that front, were guys did amazing job, left clients amazed so other colleague and I had to do whatever just to make the thing work fast and comply with front. Reason of success was that we collaborated all the time. Reason for me being on backend was that I suck at CSS and know too little about Angular. Next project frontend guys asked to stay split in terms of having front and back tasks separated because we got USED TO and warmed up with tools we used and thus it was faster and easier. And we COMMUNICATE A LOT to keep things going. I admire what these people do at front as it's too hard for me.
Now having experience from before, you make everyone full-stack, some mess up the back because they're not good at it and some even don't care about it but it's in their job description, and some mess up frontend because they hate it or think it's writing scripts, or it's works like backend.
Then I guess it's either my experience were full-stack means full-mess because people cannot organise well in those situations or it's only fit for certain projects were front is simple or back is just simple CRUD and team excels at one. Or maybe people have luck working in teams where there's actually great developers who know both ends reeeeeeeally good.
Just for the reference on how stuck I am and think devs should focuse on one thing here's a list of technologies that I can remember working with in _6 years in __11 companies so far: Java,Spring,Seam,Hibernate,Oracle 11g, C#,.NET Framework,.NET Core,EF,EF Core,SQL Server, ColdFusion, PHP,CodeIgniter,Laravel,Wordpress,MySQL,MariaDB NodeJS,express, MongoDB, Scala, AngularJs,Angular5/6/7,React and at least 20 testing frameworks and tools.
Believe me you should keep at one thing at least for 2 years before the switch to be good at something and to keep your mental health stable :D
Thank you for the interesting and detailed perspective. Yes, it’s much harder to be a full stack team when the technology is painfully diverse. Maybe I’m spoiled from doing NodeJS where it’s all javascript everywhere (well TypeScript actually because I work at a large enterprise (and also I think TypeScript is great)).
So yes, it clearly depends on the situation, the team makeup, and the willingness of each member. I’m happy that you’re focusing on conversation. :)
Of course NodeJS you can be there full stack. It's JS and TS but still it's only JS with addons :D. Toyota some time ago replaced robots with humans. Why? Because PEOPLE learn not robots(took this from Jim Coplien) and key to success is HUMAN resource. And to work on something we need to COMMUNICATE.
Please watch this to understand what's happening to people and why they step on others: youtube.com/watch?v=jobYTQTgeUE . It's about too much ego guys working around you and it's frustrating if you focuse on that. Or you could go well they have issues with themselfs God help them.