I make web apps. This means that I have to know about Docker and Kubernetes (because our deployment is complex), protocol buffers (because our services talk to one another), Kafka (because they talk asynchronously), parsing abstract syntax trees (because apps that I do are IDEs), git and its internals and filesystems (not only to work on our source code, but because our apps actually launch some git commands behind the scenes), SQL and quirks of different OLTP and OLAP databases, Rust, Python, Go and other programming languages, WebGL and other 3d rendering topics like writing shaders and projection matrices, processing RTL texts, emojis and all other wonderful aspects of unicode (including utf16 surrogate pairs), HTTP protocol, TCP, UDP and websockets...
You know what I would do without? Keeping up to date with Photoshop, Illustrator and color circles. I'm still doing a lot of UX decisions, of course. But for the love of god, just give me sensible defaults and component library.
I make web apps. This means that I have to know about Docker and Kubernetes (because our deployment is complex), protocol buffers (because our services talk to one another), Kafka (because they talk asynchronously), parsing abstract syntax trees (because apps that I do are IDEs), git and its internals and filesystems (not only to work on our source code, but because our apps actually launch some git commands behind the scenes), SQL and quirks of different OLTP and OLAP databases, Rust, Python, Go and other programming languages, WebGL and other 3d rendering topics like writing shaders and projection matrices, processing RTL texts, emojis and all other wonderful aspects of unicode (including utf16 surrogate pairs), HTTP protocol, TCP, UDP and websockets...
You know what I would do without? Keeping up to date with Photoshop, Illustrator and color circles. I'm still doing a lot of UX decisions, of course. But for the love of god, just give me sensible defaults and component library.