I'm Doing My Part (Against AWS)

Content conspiracy theorists after finding out Amazon web services (AWS) terms, clause 42.10 jan 11 2022 version Com cRuise math gauckerbeng

The greatest marketing trick the cloud ever pulled was convincing developers that servers don't exist. Turns out "serverless" is just someone else's server with a fancy API and a premium price tag. It's like ordering food delivery and pretending your kitchen doesn't exist because you didn't cook. The shocked cat face is every developer the moment they realize they've been bamboozled by buzzwords. Next they'll try selling us "codeless programming" that's just code hidden behind a drag-and-drop interface.

Content Backend Software Develo... D-Orbit Lisboa, Portugal in Candidatura simplificada Salvar Qualifications and Requirements Strong experience in Python programming (at least 3 years): Knowledge of asynchronous programming: Strong knowledge about Pythons' unit testing frameworks (preferably pytest); Experience in the use of Cython library for generation of python extensions; Strong experience in Java programming (preferable experience in Kotlin): Experience in maintaining Java based web applications: Strong experience in C programming; Strong experience in the use and design of REST APIs; Strong experience on event-driven architectures (pubsub pattern); Strong familiarity with Git distributed version control system; Strong experience of the use of commandline of the Linux based operating systems; Strong experience in debugging distributed applications potentially running in remote environments: Experience in agile development methodologies (e.g.. Scrum, TDD); Experience with applications that handle large datasets: Experience in implementing caching mechanisms (i.e., using Redis); Experience in NoSQL databases such as Cassandra and Redis; Experience in relational databases, namely PostgreSQL: Experience using Kafka, MQTT and Redis as message brokers: Experience in cloud-based environments, namely AWS; Experience in the definition and use of Docker containers; Experience in orchestration of docker containerized microservices using Kubernetes; Some experience in working under DevOps oriented methodologies: Pipeline definition: Test execution automation; Some experience in web application development using the microservices architectural paradigm; Experience in designing web-based applications considering the need for scalability, reliability and security; Experience with Jira framework: Experience of bash shell scripting; Experience in JavaScriptTypescript: Experience in authentication and authorization mechanisms; Experience with event bus technologies (e.g., Kafka);

When your AI-powered deployment system is so advanced that it triggers company-wide panic meetings because someone "vibe coded" their changes. You know, that beautiful state where you write code based purely on vibes with zero documentation, testing, or regard for human life. And then there's the second part showing a trading interface with +277,897 gains and -567 losses. Translation: Amazon's stock probably went up because investors think "AI-driven mandatory meetings" sounds like innovation. Meanwhile, the devs who actually have to attend these meetings are definitely in the red zone. Nothing says "cutting-edge AI" quite like automated systems that detect code quality so poor it requires human intervention via PowerPoint presentations.

Content rAskReddit Posted by uworldtraveler100 10h What technology are you shocked has not advanced yet? 4 26.8k J 14.6k Share Award BEST COMMENTS RegulatoryCapture 4h 1 Award The legal code. Computer programmers have come up with beautiful collab- orative change tracking systems (like git) that let you easily make changes to a huge base of code, track who changed what, submit and resolve conflicting versions of updates, etc. But when we pass a new bill that replaces or modifies an old law, it is always some 300 page document with pages of "Subsection F Paragraph 3 will be modified to read 'XYZ' Why not put the laws into a git repository and make it easy for bills to just modify the existing history to say what you want it to say? And why not have the transparency to see exactly what changes and WHO implemented that change? Want to slip some pork for your district into an unrelated bill? Well, that edit is going to have your name on it. Of course it will never happen. Reply 928 J imtn 1h Who the heck wrote this ridiculous bill? git blame Ah, I did. 217

Cloud migration in a nutshell: Backend service owners clutching their precious code like a hairless cat hoarding gold coins, while completely ignoring those pesky validation steps scattered on the table. "But it works on my machine!" they hiss, as the DevOps team sighs for the 47th time today. The validation steps might as well be invisible—just like documentation and proper error handling. Who needs testing when you've got blind faith and a prayer to the server gods?