|
|
|
|
|
by o12v
2667 days ago
|
|
If you expect to be a generalist by somewhat half heartedly knowing how to use a number of technologies you're doing it wrong. What makes you a generalist is not just being able to use tools, but rather understanding how they work. That means for web frontend work you should rather step towards understanding how the dom and v8 works instead of jumping on the newest hyped framework or instead of just learning react's api maybe also understand how and why they are building their own virtual dom. If you do backend work you eventually want to look into compilers and understand the difference between interpreting, compiling and jit-ing code. If you do database things you may want to start thinking about how you would implement your own and touch on things like transactions, consistency, how a query optimizer works or what structures data is stored in. Not that you will ever be tasked with building your own frontend library, language, compiler or database; but all that helps you immensely to understand and evaluate the tradeoff space and also quickly jump on the newest hyped thing if it actually is a good idea. |
|