Dividing front end from back end is an antipattern
As a fullstack dev, this article resonates with me. I was worried that being Fullstack dev is a career killer (what I heard), but I found out its not true. In my current company (one of the tech giants&#x2F;unicorns), there are many small independent teams that maintain stuffs themselves. In my team we maintain everything, from frontend to backend to devops. Python, JS&#x2F;TS, Go.<p>Not impossible to achieve, since frameworks&#x2F;methodologies are transferable. I.e., I use React, but I learned Angular2 in just a day or two and was able to be productive right away for maintaining&#x2F;building feature in some apps that use Angular2. Backend we use Express, Flask, plain Go. ES, SQL, MongoDB, DynamoDB. Doesn&#x27;t matter. Granted, everyone in my team are senior devs, more than 5+ years exp.<p>Besides, after a while doing just frontend or doing just backend you&#x27;ll get tired and sick of it and want some change. It is nice to just flip back and forth, do database today, do css tomorrow, do API the day after tomorrow, do buttons and forms next week.<p>We don&#x27;t do Kubernetes etc though, too complex. Just plain old Ansible Jenkins on real machines. And when we can, just use managed services.