Weare Sorry

Content Company: our projects are well structured so errors are easy to find. Their projects: Languages Makefile 18.7 C 11.9 Rust 9.3 C 14.3 C 10.8 Java 9.3 Other 25.7

Content Samsung's trade secrets have reportedly leaked because employees shared a bit too much info with ChatGPT Microsoft Written by Priya Pathak April? 20231707 1ST SAMSUNG What did the employees do? As per the report, one employee asked ChatOPT to look for errors in a confidential source code. A second employee requested code optimisation with ChatGPT and shared code. The report notes a third employee shared a recording of a company meeting as it wanted ChatGPT to make notes for a presentation.

Content Interview process 1. Your application will be reviewed by our team 2. You will be sent a set of written interview questions which will be reviewed anonymously 3. You will be asked to take a standardised personality test 4. A short interview with a team member 5. An HR interview 6. You will be asked to complete a small coding test 7. A series of four more detailed technical interviews 8. Hiring manager interview 9. Offer

Content CODE RED: THE WEBSITE IS DOWN !! UMM... I... I... I ACCIDENTALLY PUSHED SOME CODE TO PRODUCTION INSTEAD OF TESTING. YOU WHAT? FINALLY! WELCOME TO THE CLUB! I'M SORRY... I.. I'M NEW TO THISI WON'T DO IT AGAIN... I.. workchronicles twitter and instagram workchronicles.com

The eternal dance between testers and developers captured in its purest form! When bugs mysteriously appear in production, testers immediately go into detective mode, crawling on the ground trying to catch these elusive creatures. Meanwhile, the default response? "I bet the developers did this." Because obviously, the code was perfect until someone breathed on it wrong. Never mind that it passed all the tests with flying colors yesterday. Production environments are just developers' favorite place to release their collection of exotic bugs into the wild. It's not a deployment, it's a safari.

The classic "it works on my machine" defense, followed by the inevitable bloodbath when QA gets their hands on it. That moment when your perfectly functioning code suddenly develops sentience and chooses violence the second it touches a tester's machine. No amount of unit tests can prepare you for the mysterious environmental variables on Dave from QA's laptop that somehow still runs Windows Vista "because it's stable."