grug, like all sane developer, fear concurrency
God willing the frontend complexity demon willl become generally imprisonable before I die. I like the conception of the frontend as a place where many more mistakes have yet to be made.
This is the common sense position held almost unanimously among all of the senior (ACTUALLY senior, not 4 years out of school senior that everyone seems to be now, I am talking hairy eared senior) software engineers I have ever worked with. Everyone is obsessed with the sexy new frameworks/etc, they think that all problems can be solved with new interpretations of what the problem "is". In reality, the problem is that a rotating team of 4 to 6 developers have to continuously fix one or two pieces of software over and over, and how to make that even remotely possible is such a massive challenge it is truly a wonder that anything ever works at all.
It used to be that I just never did concurrency. It was easy as an embedded guy. Learning Rust though has made me less fearful of concurrency until things don't work because of too many threads. 😕
I went from C threads, then confused by python async, to learning go and calling a function as a goroutine. I rather do C threads than figure out wtf is going on with async stuff.
I didn't really get async until I saw it done in Rust. I still like using thread pools and plain old threads though. If you like C threading then you'd probably like Rust.
good post, agree with all. Currently at one of my jobs the devs and devops people on my team have gone off the rails, deciding we need kubernetes and helm and terraform to deploy our simple little app to the web. We are on month 18 and still can't deploy automatically without an issue cropping up somewhere. Complexity should be avoided at all costs!
The computing scientist’s main challenge is not to get confused by the complexities of his own making.
:dijkstra-shining:
Stay grug-pilled. Use Plan 9. Club the next complexity demon you see!
