3 ms·
Building a webapp being difficult for a junior is the exact problem he's pointing out, although pointing it out as a problem is probably not very fair. It's jus
by flakiness 2y ago
Building a webapp being difficult for a junior is the exact problem he's pointing out, although pointing it out as a problem is probably not very fair. It's just the maturity of the technology.
The expectation has changed, and people expect webapps to be relatively sophisticated, but building a sophisticated webapp isn't easy. There are a lot of them just because there are a lot of reasonably competent webdevs. Joining that club is not impossible at all, but it's not like building a Rails app 10+ years ago (which did solve a lot of problems at the standard of that time, because of the different expectation level).
- kaoD 2y agoIt's not even related to tech or field maturity. Web apps are complex beasts. A junior architect cannot design a safe and maintainable skyscraper (hell, they probably can't even design a proper two-story home without making mistakes) and architecture as a discipline has been with us for centuries. A modern, new product is even harder because it's often uncharted territory (it's almost a miracle we can build them) not because of the maturity of the field but rather because if you're building an app instead of deploying an off-the-shelf solution it's because you need to explore the trail... If you want tried and tested just deploy WooCommerce or whatevs in a plain-old web hosting! Designing something completely new is, by definition, off-limits for a junior in any field. This guy's been building bunkers and dams for years and somehow expects to transfer his knowledge to design a skyscraper? Would he expect a webdev to be able to design and build a brand-new LLM and deploy it in a scalable fashion from scratch? I understand the desire, but it's unrealistic, especially considering the ever-growing affordances that an app is expected to have in 2025.