email "protocol" is clunky and old AF. no need to build an email client for the 21st century when everything underneath it a donkey pulling a cart full of rotten fish. stmp/pop/imap and all the dkip.. is pure crap. we need to overhaul the entire email/messaging delivery system. not just the face of it.
the cloud is the golden cage. companies, and people, got sold on comfort and ease of use whilst trapping themselves into vendor lock-in environment that is the california hotel. when they realize the problem, they are too deep in the tech and rewriting their codebase would be too complex or expensive so they bite the expense and keep on doing what they are doing. constantly increasing their dependency and costs and never be able to leave.
as you pointed out, bare metal is the way to go. is works the opposite of cloud - a bit more work at the beginning but a way lot less of expenses at the end.
tl;dr you probably just work on projects you don't like, not that you don't like coding. Been there, done that. Nothing new under the sun. Those people who say that you will never work a day in your life if you do what you love are foll of crap because having an option to do something and having to do something are two very different things. And having to do something you like doing is the fastest way to hate it. My advice is switch company and look for work that interests you nowadays. Like instead of working for a company doing e-commerce, go work for a company doing IoT, banking, healthcare or anything like that. Just change the type of work you do.
starlink and covid were gamechangers for WfH. People can now move outside of big cities and enjoy better lives while still being able to make good money. less traffic, less pollution(if you are into that), less garbage, less waste in general. billions of hours saved on commuting. more time to spend with your family, to relax...
I was frantic code commenter in my youth because I wanted to give as much information to other people as possible but as I became SR developer I dropped them altogether. Especially after I moved into Go. Nowadays, I comment only in two situations:
1. if it is important to explain WHY something is done in a way it is done
2. if there is some related or directly connected code far away that the person might miss or cannot know about and how this code influences it. Writing self-explanatory code nowadays is a standard. An era of newbie spaghetti code is long gone so no need to explain the code itself.
i was wrong. my bank's documentation did not include this crucial detail so i had the impression that, at leas my bank, allows anyone with verified ssl certificate to access the api(which is quite basic anyway).
that is my current bank. but they do not have a concept of nonce. at least not in their "simple" api. am researching their open banking api at the moment but as far, as i know the bank quite well, i dobut it will work as needed because they are a MVP bank. bare minimum.
the rendering itself was easy. the problem i had was actually the style of the rendering. because you have to use the node/way tags to determine what is what and how to render it(style). not only that but also order of rendering. that in itself is not an issue, but the tag system is. which everything(logic) is built on. hence why i gave up on it. i still have the code, it works, it renders roads and whatnot but it is impossible to write some useful style for it beyond utter basics. the only thing i struggled with for a while was tile edges where renderer would close the paths, making continuous lines broken on every edge. once i figured out to render a but further beyond the edge(which won't be actually rendered on the image) i was fine. it is really not hard to do, couple of hours at most. but again, the tag system makes this useless. it can be done but i realized that life is way too short for this and moved on. also i found there are other project that handle this that you can self-host nowadays so it lost it's financial potential anyway. i just prefer to use my own code.
i tried to write my own map tile renderer, in go, for one airbnb-like project where using the google maps or any other provider would cost me an arm and a leg and after experiencing the tag system in OSM i'd rather cut said arm and said leg myself off...with a rusty saw.
there is nothing wrong with asking if provided object is more capable than it seems so we can perform more efficient logic on it. that has nothing to do with magic methods, numbers... no magic whatsoever. "magic" in code refers to usually hidden and/or fixed behavior. this is not even in the same ballpark.
When i was was apartment hunting in barcelona 7+ years ago and failed straight for weeks to get a single reply on idealista, and went to the real estate agencies and found they had siestas, still, in barcelona, i quit the country. good to visit, not to live.
ps: when i wanted a bank account, the people there acted like they didn't spoke english, until it was clear they won't give me an account, then suddenly english was not a problem.
i would because ** REST for API but i am already too used to write my APIs in protocol buffers so even though I have abandoned gRPC I still use PB and so I need rest-ish approach.