Front End Development Is Too Complicated

It becomes more and more complicated. Single Page Applications (SPA) are a great thing. I’m pretty sure that all users like it. I don’t know if many developers like it or not. Personally, I think that its development is too complicated.

Maybe it’s not so complicated as I think if you are Front-end Engineer or even full-stack JavaScript Developer. But it becomes extremely hard if you need to integrate your SPA with Python-based API with is working behind Nginx in Docker or Kubernetes. In such case, you have to be able to configure all this stuff. Of course, you may say that there are special guys in your team called DevOps or Deployment Engineers to do all configurations in a correct way but it doesn’t allow you to not understand how it works.

It’s not bad. It’s not good. It’s how things are going forward. If you grow your skills only in front-end, back-end or sysops area nothing will change. You need to be an expert only in your subject area. But if you want to be a T-shaped person you have to know about all of these tools:

Webpack to configure your front-end builds and dev area. uwsgi/gunicorn/etc to run your API Nginx to make everything work together Docker/K8S to deploy your application into containers (OK, you may not use Nginx in this case)

I do not say anything specific about JavaScript, Python, deployment tools and so on. I just mentioned all areas you should know to become a full-stack engineer.

I would like to have some unified environment configuration to run my projects with front-end, API, DB, key-value storage, etc in some unified way. Maybe it will be some yaml, maybe not. I just do not want to have dozens of config with different formats in one project.

P.S. I just tired a bit configuring nginx, webpack and getting everything work with docker-compose today.


.net .net-framework .net-framework-3.5 agile ajax ajax-control-toolkit ampq ansible apache automation axum babel bash benchmark blog blog-engine bootstrap buildout c# cache centos chrome ci cinder ckan cli cloud code-review codeplex community config debugger deface dependencies development-environment devices devstack devtime disks django dlr dns docker dockerimage dos easy_install elmah encoding environment-variables error event events everything-as-a-code exception exceptions fabrik firefox flask foreach forms fstab gae gcc gerrit git github go google google-app-engine grep hack hacked hardware headless horizon hound html hugo iaas ienumerable iis internet iptables iron-python ironic iscsi java-script javascript jenkins jquery js jsx k8s kharkivpy kiss kombu kubernetes kvm kyiv lettuce libvirt linux lio loci logging loopback losetup lvm mac-os macos mercurial microsoft microsoft-sync-framework mobile mono ms-office msbuild networking news nginx npm npx offtopic oop open-source open-xml opensource openstack openvswitch os packages paraller-development patterns-practices performance php pika pip plugins pnp podcast popup postgresql profiler project protocols proxy pycamp pycharm pycon pykyiv pylint pypi python python-3 qcow quantum qumy rabbitmq rar react reactjs refactoring rfc rhel search-engine security selenium server shell silverlight socket software-engineering source-control sourcegear-vault sources sql sql-server sql-server-express sqlalchemy ssh static-site sublimetext svg tests tgt tipfy todo tornado typescript uapycon ui uneta unit-tests upgrades usability vim virtualenv visual-studio vitrage vm vue.js vuejs web-development web-server web-service web_root webpack webroot windows windows-live word-press x32 x64 xcode xml xss xvfb интернет-магазин книги

Recent posts

Go 1.18: new features

Всё будет Kubernetes

2022 Relaunch

Everyday Blogging

I don't want this CI


2022 (3)
2019 (73)
2018 (2)
2017 (3)
2016 (2)
2015 (3)
2014 (5)
2013 (17)
2012 (22)
2011 (36)
2010 (25)
2009 (35)
2008 (32)
2007 (2)