I don't want to be a full-fullstack developer
artur-martsinkovskyi.github.io
I don't want to be a full-fullstack developer
1–10 of 88 posts
Re: I don't want to be a full-fullstack developer
#2(1) There's a strong reason for this desire. Software systems are very interdependent.
We you can see from front to back and side to side, and you can recoginze the potential for improvement or optimization.
(2) "Full-stack software developer" is more specialized then you might think.
As a "full stack" web developer, I can count on one hand the number of times I've looked at a browser's source code. Same for databases. I understand the basics of DNS, IP, TCP, UDP, BGP, but not the details. And my knowledge of common ISAs is laughable. And I have essentially no knowledge of hardware: physical CPUs/GPUs, displays, fiber optics, etc.
Re: I don't want to be a full-fullstack developer
#3Re: I don't want to be a full-fullstack developer
#4Re: I don't want to be a full-fullstack developer
#5Re: I don't want to be a full-fullstack developer
#6I'm fine with all of those roles. I've been able to pick them up along the way and others (report writer use to be a separate role).
The one role I can't master is designer (not frontend developer). It isn't logical and it can't be learned through instructions alone. And the rules change.. what looks great today looked alien yesterday and boring tomorrow.
Re: I don't want to be a full-fullstack developer
#7Re: I don't want to be a full-fullstack developer
#8Agree with all your points, but in my experience, early-stage startups require full-stack competency due to rapidly changing priorities and a small team.
In a small place having a third of your team being full stack takes a lot of stress off the planning people.
Re: I don't want to be a full-fullstack developer
#9Allow me the exaggeration but I think that if everybody would be full stack, frameworks would be much simpler, there is a lot of gratuite complexity that grows because people have the time to dedicated just to one side.