13 ms·

I've been working as a full stack web developer for the last 15 years during this transformation and this couldn't be further from the truth. No full stack dev

I've been working as a full stack web developer for the last 15 years during this transformation and this couldn't be further from the truth. No full stack developer feels they aren't a real developer. But I think more than anything the full stack's have been the drive of a lot of this complications because all these complications make everything way easier for us. Web development today is easy (compared to 15 years ago) once you know this toolchain. And for professionals, tools that take a long time to learn but increase productivity tremendously are much better than tools that are easy to learn but slow to use. Of course we'll figure out how to simplify this toolchain over time. But things have been improving across the board for professionals. It is unfortunate that the barrier to entry seems to be raising even higher. But a trade-off we seem to be fine making.

acemarke 7y ago
Chris Coyier did a fantastic talk recently that covers how "front-end" development has ended up subsuming a lot of functionality that was traditionally "back-end". Highly worth reading the slides: https://full-stack.netlify.com/ https://full-stack.netlify.com/
GeorgeTirebiter 7y ago
I would greatly appreciate, given your 15 years as a full stack developer, that you explain what you are using today, and (hopefully) why. I'm also curious if you might have some vision for the future?
- the-pigeon 7y ago
  It really depends on the problem you are solving. Like internal tools, consumer facing tools, content site, social site, etc. Is it an MVP? Rebuilding an old system? Is this a build it, ship it and move on? Or build, enhance and maintain for foreseeable future? What's required lifetime of it? What's the desired lifetime? As well as resources. You want to use different setups if you are a single person compared to a team of 15. Generally speaking the smaller the team the simpler the architecture needs to be. And the larger, the more isolation you want between pieces. Personally I currently like Rails and React best. Both are fairly mature frameworks and work well together. Not to say there aren't better alternatives just those are the two that have worked best for me. There's so many good options that no one knows them all well enough to make a fair comparison. I think Rust is very promising as a much faster alternative to Ruby and expect to switch over to it sometime in the next decade. But I don't feel the web frameworks for it are mature enough yet that I can justify a switch to it to my employer.
Supermancho 7y ago
> Web development today is easy (compared to 15 years ago) once you know this toolchain Web development is harder for the simpler tasks that were common 15 years ago. It's harder so the harder (or impossible) tasks of yesterday, today and beyond, are easier for some values of harder and easier related to time and custom coding.
- ng12 7y ago
  Uh, it's not like PHP and jQuery don't exist anymore. Use the right tools for the job.

acemarke 7y ago

Chris Coyier did a fantastic talk recently that covers how "front-end" development has ended up subsuming a lot of functionality that was traditionally "back-end". Highly worth reading the slides: https://full-stack.netlify.com/ https://full-stack.netlify.com/

GeorgeTirebiter 7y ago

I would greatly appreciate, given your 15 years as a full stack developer, that you explain what you are using today, and (hopefully) why. I'm also curious if you might have some vision for the future?

the-pigeon 7y ago
It really depends on the problem you are solving. Like internal tools, consumer facing tools, content site, social site, etc. Is it an MVP? Rebuilding an old system? Is this a build it, ship it and move on? Or build, enhance and maintain for foreseeable future? What's required lifetime of it? What's the desired lifetime? As well as resources. You want to use different setups if you are a single person compared to a team of 15. Generally speaking the smaller the team the simpler the architecture needs to be. And the larger, the more isolation you want between pieces. Personally I currently like Rails and React best. Both are fairly mature frameworks and work well together. Not to say there aren't better alternatives just those are the two that have worked best for me. There's so many good options that no one knows them all well enough to make a fair comparison. I think Rust is very promising as a much faster alternative to Ruby and expect to switch over to it sometime in the next decade. But I don't feel the web frameworks for it are mature enough yet that I can justify a switch to it to my employer.

Supermancho 7y ago

> Web development today is easy (compared to 15 years ago) once you know this toolchain Web development is harder for the simpler tasks that were common 15 years ago. It's harder so the harder (or impossible) tasks of yesterday, today and beyond, are easier for some values of harder and easier related to time and custom coding.

ng12 7y ago
Uh, it's not like PHP and jQuery don't exist anymore. Use the right tools for the job.