3 ms·
The future of front end engineering
- llorenc 3y agoSo, I wrote an article and would love to know what people think about it. If you don't feel like clicking on the link, the tldr is: There will be a ratio of 2 designers per frontend engineer because frontend engineers will develop and maintain the software that designers and product managers will use to build the application. I am not an expert on AI, but, at least in the midterm, I don't think there that there will be an AI that will build all applications. Instead, an engineer will build / configure a project so that product managers and designers can add features easily with AI help. What do you think?
- proc0 3y agoI wish it worked this way but I have my doubts. Since I started working on frontends I looked for ways to automate feature development but it seems the priorities of software organizations does not include this. Having a custom Content Management System should be an easy win, but in practice it seems it is too complex for the liking of most orgs. It would require a large dedicated core team that is not directly adding value to the business, and so it is not prioritized. Instead teams are pushed in the direction of owning part of the product and every slice of the product lifecycle. I think if you build the app from the ground up to be a CMS, it would look like a custom WordPress/Drupal, and those requirements are engineering only. It would only add indirect value which is hard to measure and therefore, unfortunately, it is not something that software orgs will invest in, despite the potential efficiency gains in the long term.
- llorenc 3y agoThat's a good point and I agree totally with you. But I don't think that this software will be built from scratch by the engineers. In my head, it's more like a framework. Think Rails or NextJS already setup with some conventions on how to integrate components and AI together.