3 ms·
That's basically the life story of the life of frontend engineer nowadays isn't it? The lower I went to the ground, e.g. backend, then native code, then C... t
by keyle 2y ago
That's basically the life story of the life of frontend engineer nowadays isn't it?
The lower I went to the ground, e.g. backend, then native code, then C... the happier I am. It's like the ocean, the lower you go, the more stable and calm things are. On the surface, you get the crashing waves.
I used to be a Web expert, from the early days, DHTML and flash, to the median years, jquery, backbone etc. to then writing my own libraries. Vue 2 was the last I really used as front-end heavy.
Since then I've been secluded more towards the backend, I leave the front end to the young. I do like systems like Laravel Livewire though, it's mildly sane.
When I write websites now, I do it all by hand and focus on really fast page loading times rather than a monstrosity of generated code and async over the wire. I have such a better time doing it.
Today's web should be considered harmful to the health. It's a high blood pressure job.
- mystified5016 2y agoI really love firmware for this reason. Each instruction you send to the CPU means something. If you want, you can rip back all the abstraction and just run raw assembly. Sometimes the compiler can be very wrong and you get to embed the correct assembly in your C and suddenly the program is 10x faster. True story! Trying to fit my application in 1kB of flash and one hundred twenty-eight entire bytes of RAM taught me a lot as a young programmer. It really makes you confront the physicality of the machine your code represents. I don't think nearly enough programmers have that experience