2 ms·
I used to do some part-time (second job) lone web dev, this is why i don't anymore: >"Maintaining a deep knowledge of both front end tools, libraries, and tech
by pbhjpbhj 9y ago
I used to do some part-time (second job) lone web dev, this is why i don't anymore:
>"Maintaining a deep knowledge of both front end tools, libraries, and techniques (down to browser-specific quirks), as well as backend architecture […] requires years of experience dedicated to each in addition to the time to keep up to date with how those areas are changing." //
Basically the time to keep up to date with all the tech is increasing; like a growing snake, it's hard to keep track of both ends, and the middle. Also customers expectation increases as familiarity with the web increases.
My definition of full-stack web dev would be everything front-end including things like icon design and optimisation, handling hdpi, logo design, responsive page layout, SEO, font choice and optimisation, dom scripting, etc. through to in-flight issues such as browser caching, CDNs, DNS, security (certs, etc.); through to back-end reverse proxies, varnish, caching, failover, optimisation, actual production of the HTML (PHP in my case) [edit: not forgetting DB, and it's optimisation and management, I never got as far as sharding or anything tricky], and on to keeping servers updated and running securely (SSH key management, firewalls, backup, etc.).
(And in your spare time you do sales and marketing!)
I think it's near impossible to handle the full web stack now; I'd imagine splitting it in to at least 5 roles.
Their definition of full-stack web dev appears to be just LAMP (or similar). So then you've got at minimum a 3 person team: adding a graphic designer, server manager.
Full-stack elsewhere would be something like back-end, gui design, UX, _and_ packaging/installers for distribution?