Well That Was Not In Test Cases

Content Junior dev who just did unit testing to get code coverage up Senior dev who is about to assign integration testing as part of sprint

When a dev tweets "the energy i bring to the team" and it's just someone commenting "i'm merging it. fuck the tests" - that's peak chaotic developer energy right there! 🔥 And then that reply about test cases being "a sign of weakness"? Pure madness! This is that 3 AM deploy energy when you're running on nothing but energy drinks and blind confidence. Ship it and pray nothing breaks! Who needs sleep when you have the adrenaline rush of potentially breaking production?

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);

Content TYPES OF RPROGRAMMERHUMOR POSTS CLIENTS ARE STUPID DOES NEEDING TO USE GOOGLE AND DOCUMENTATION MAKE YOU A BAD PROGRAMMER? COMPILERS ARE MOSTLY BAD AT EXPLAINING SYNTAX ERRORS IS IT OKAY TO USE INFINITE RAM? HOLD MY BEER WHILE I MAKE FUN OF JAVASCRIPT STACKOVERFLOW VOTED LEAST FRIENDLY SITE HERE'S HOW I CREATED A NEW TOOL AND STILL FAILED TO PASS A JOB INTERVIEW USING THAT SAME TOOL NUMBER OF PROGRAMMING LANGUAGES REQUIRED ON JOB OFFERS HAVE INCREASED 3000 IN THE LAST CENTURY PRINTING "HELLO. WORLD!" DOES NOT TEACH EVERYTHING ABOUT A LANGUAGE WHAT I'M DOING DOES NOT CORRESPOND TO WHAT I THINK SOCIETY THINKS I'M DOING: A CASE STUDY IN FIXING PRINTERS FOR FREE NEW RECORD: ONE USER TRAPPED IN VIM FOR 50 CONSECUTIVE YEARS RECURSI000ON: LOOK HOW META I AM! read the original version at https:kcd.com2456

Someone just learned the hard way why you always test your cleanup scripts with a dry-run flag first. Their "dry-run" turned out to be about as dry as the Titanic's maiden voyage—it executed real deletes and nuked the admin account (user id 3) because it had email_verified=0 in the database. The beautiful irony? They're now frantically checking for database backups while simultaneously realizing they should've excluded admin accounts AND done a SELECT-only test first. That's like realizing you should've brought a parachute after jumping out of the plane. The PowerShell suggestion at the bottom is basically the digital equivalent of "thoughts and prayers"—good luck recovering from that one, chief. Pro tip: When your cleanup script has the power to delete accounts, maybe don't trust a boolean flag to be the only thing standing between you and unemployment.

Content The 5 Stages of Debugging At some point in each of our lives, we must face errors in our code. Debugging is a natural healing process to help us through these times. It is important to recognize these common stages and realize that debugging will eventually come to an end. Denial This stage is often characterized by such phrases as "What? That's impossible," or "I know this is right." A strong sign of denial is recompiling without changing any code, "just in case.' BargainingSelf-Blame Several programming errors are uncovered and the programmer feels stupid and guilty for having made them. Bargaining is common: "If I fix this, will you please compile?" Also, "I only have 14 errors to go!" HOSt Anger Cryptic error messages send the programmer into a rage. This stage is accompanied by an hours-long and profanity-filled diatribe about the limitations of the language directed at whomever will listen. Depression Following the outburst, the programmer becomes aware that hours have gone by unproductively and there is still no solution in sight. The programmer becomes listless. Posture often deteriorates. Accentance The programmer finally accepts the situation, declares the bug a "feature", and goes to play some Quake.