SQL or Sequel

The classic "just one small change" that breaks your entire data model. You design a perfect database with a unique constraint ensuring each user belongs to exactly one organization. The requirements were crystal clear. You even got it in writing. Then suddenly, the user who SWORE the relationship would "always be N:1" comes back asking if users can belong to multiple organizations. That look of horror is every database architect who now has to create a junction table, update all the queries, and pretend they're not dying inside. Next time, just assume every relationship is many-to-many from the start and save yourself the trauma.

Content Twotypes of people in Standup Yesterday I fixed an issue that occurred when parsing the JSON object received from fronted, I added the missing keys and created unit tests that cover all scenarios. I enhanced the performance as well by adding some missing joins to the SQL query which reduced the overall loading time of the endpoint. I tested the code on staging and everything was working fine so by the end of the day I deployed to production. Fixedan issue nasser. junior

Content Python: What if everything was a dict? Java: What if everything was an object? JavaScript: What if everything was a dict and an object? C: What if everything was a pointer? APL: What if everything was an array? Tel: What if everything was a string? Prolog: What if everything was a term? LISP: What if everything was a pair? Scheme: What if everything was a function? Haskell: What if everything was a monad? Assembly: What if everything was a register? Cog: What if everything was a typeproposition? COBOL: WHAT IF EVERYTHING WAS UPPERCASE? C: What if everything was like Java, but different? Ruby: What if everything was monkey patched? Pascal: BEGIN What if everything was structured? END C: What if we added everything to the language? C11: What if we forgot to stop adding stuff? Rust: What if garbage collection didn't exist? Go: What if we tried designing C a second time? Perl: What if shell, sed, and awk were one language? Peri6: What if we took the joke too far? PHP: What if we wanted to make SQL injection easier? VB: What if we wanted to allow anyone to program? VB.NET: What if we wanted to stop them again? Forth: What if everything was a stack? ColorForth: What if the stack was green? PostScript: What if everything was printed at 600dpi? XSLT: What if everything was an XML element? Make: What if everything was a dependency? m4: What if everything was incomprehensibly quoted? Scala: What if Haskell ran on the JVM? Clojure: What if LISP ran on the JVM? Lua: What if game developers got tired of C? Mathematica: What if Stephen Wolfram invented everything? Malbolge: What if there is no god? nixcraft

Content Giulio Carrara 3rd Software Engineer 1d g Dear recruiters, if you are looking for: - Java, Python, PHP - React, Angular - PostgreSQL, Redis, MongoDB - AWS, S3, EC2, ECS, EKS - nix system administration - Git and CI with TDD - Docker, Kubernetes That's not a Full Stack Developer. That's an entire IT department. Yours truly 8,801 391 comments

That moment when you're peacefully asleep and your brain decides to remind you that you left a database transaction hanging somewhere in production. Nothing quite like the cold sweat of realizing thousands of users might be experiencing locked tables because you forgot a single COMMIT statement. The worst part? You're now wide awake, grabbing your laptop, and praying to the database gods that auto-commit was enabled. Spoiler alert: it wasn't. You know it wasn't. Because when does anything ever work in your favor at this hour? Fun fact: Uncommitted transactions can hold locks indefinitely, blocking other operations and potentially bringing your entire application to a grinding halt. Sleep is for people who don't work with databases.

Content danielmiessler SecLists Watch 952 Star 8.819 Fork 3.362 Code Issues 21 83 Pull requests 21 I Projects 0 Be Wiki alt Insights Remove my password from lists so hackers won't be able to hack me 155 it Open assafnativ wants to merge 1 commit into danielmiessler: master from assafnativ:remove my password Conversation 104 o- Commits 1 El Files changed 30 2-32 0000 assafnativ commented 4 days ago No description provided. 4 263 48 8 (g) 353 80 g 4 132 Remove my password from lists so hackers won't be able to hack me 3cb9418 View changes mitcom reviewed 4 days ago Passwords10millionpasswordlisttop1000.txt -344, 7 344,6 blue 344 344 Tiverpoo 345 345 theman 346 346 bandit 347 -dolphins Reviewers D3X masterrr lucianoqueiroz RossBille mitcom Treva Sm rugk ils phra romcheg songgao unsign3d liukai k k X