Every Damntime

Content ooo verizon 9:10 AM ooo Verizon 9:10 AM 1 1 ooo verizon What do you know about material design? Oct 19. 2016. 10:22 PM Enough to know that Blue 600 is 1885 hex codes are hot Damn bov let me GIT some of that So is lava wouldn't mind giving you a unit test Oh don't tease me like that hope you're agile, be this just became a standup meeting Onlv if I can call vou CSS cause I like vour style I hope we can merge without any conflicts Let's do a pull request so we can commit and make it official call me scrum master cause I'II find all vour use cases Do you approach your sprints in waterfalls because you're making me wet the time and cost don't matter as long as I can scope out that ass Oct 19. 2016. 11:12 PM Are vou enterprise architecture because I like vour structure and how you operate girl let me gather your requirements 9:10 AM 6 11 00 Oct 20, 2016, 7:52 AM fyi I'm sharing this convo with my coworkers Oh I'm 100 doing the same 20 87 AM hope you're ready to deploy this package Oct 20, 2016, 9:37 AM Wanna come over later because I got a few things I want to demo from mv local AM as long as you can debug my performance Cont Oct 20. 2016. 12:11 PM hopefully my user experience leaves vou satisfied GIF Tune a Message. GIF Tune a Messade GIF

OH. MY. GOD. The absolute TRAGEDY of spending TWO WHOLE HOURS debugging an image upload issue only to discover you've been uploading a SCREENSHOT OF AN ERROR PAGE! 💀 It's like searching the entire house for your glasses when they're on your head the ENTIRE TIME! The universe really said "here's your sign" and slapped this poor soul with the most ironic debugging loop imaginable. The digital equivalent of trying to figure out why your car won't start while holding the keys in your hand!

BEHOLD! The magnificent Salt Bae of programming! Sprinkling his code with a flamboyant flourish of HTTP status codes and questionable life choices! 💅✨ This coding maestro isn't just writing code - he's PERFORMING ART, darling! Seasoning production environments with 400 Bad Requests, 401 Unauthorized drama, 402 Payment Required (because who doesn't love surprise billing?), and the classic 404 Not Found when everything inevitably crashes and burns! And the pièce de résistance? Those STUPID VARIABLE NAMES that future developers will absolutely SCREAM about during code reviews. "Why is this variable called 'chonkyBoi'? WHY IS THE DATABASE CONNECTION STRING STORED IN 'juicySecret'?!" This is what happens when you code purely on vibes and caffeine, sweetie. The production server never stood a chance! 💔

Content 3 Building the image using docker run build . --networkhost fixed the issue for me. The error I was getting was caused by Docker not being able to access the Internet, so spoonfeeding it "hey, just use host" seems to have fixed the problem. Share Follow answered Jan 27 at 18:35 walnut salami 2,790 0 1 11 33 3 It's ... kind of surreal googling an error, opening a stackoverflow answer and finding out that both the question and the answer are mine but several months later - walnutsalami May 24 at 9:24

Content When your client ask to fix the defect in operating system... fb.mevuva.krishna.memes New Scientist newscientist 5h Scentist Ghost crabs use teeth in their stomach to growl at their enemies bit.ly210pSO t7.35 123 James Colley JamColley - 5h Could you ask them to freakin not!?!?! 17 05 New Scientist New Scientist newscientist Replying to JamColley We'll see what we can do ProdrammerHumor.io

This is what happens when you let someone who learned architecture from YouTube tutorials and Stack Overflow answers design your house. The building looks like it was refactored 17 times by different junior devs who all said "it works on my machine." Windows positioned like UI elements dragged randomly in a Visual Studio form designer. That balcony clearly started as a simple feature request before scope creep turned it into whatever monstrosity we're looking at now. The structural integrity is probably maintained by hopes, prayers, and something equivalent to jQuery patches. This is the physical manifestation of "we'll fix it in production" and "ship now, refactor later." Bet the architect submitted this with a commit message that just said "final_house_ACTUALLY_FINAL_v3.2_USE_THIS_ONE.blueprint"