"Oh, he is asking that much money for this website? I will create that for only $250 with WordPress. He is just trying to use you"

You fucking wanker. What you don't understand is that you are pushing the companies to a fucking black hole that they won't be able to recover from.

He shows an example of a website which takes 30 sec to load. It's full of hundreds of dreadful plugins. He chose the shittiest stock pictures to make it look "pretty".

When I point out his fucking shite website takes this long to load, he says if the company wants to make the website fast, they will need buy the premium plan of CloudFlare. WHAT THE FUCK are you even talking about?

Not only that, the example website, doesn't even have any SSL. He is saying that the other company didn't want to pay for the SSL. Ever heard of fucking StartSSL or LetsEncrypt?

It's people like you who is responsible for making half of the web an insecure, slow, low-performance space which is prone to hacking.

WordPress was made for blogging. KEEP IT THAT WAY. Stop trying to make your high-performance CMS or eCommerce website with this shite.

I have this old lady that I help from time to time with her computer issues.

She is nice, so I feel compelled to help her.

Get a call one day.

Lady : "hello, my internet and email isn't working, I've tried everything, could you maybe help me?"

Me : "Sure, ill come over after work and check it out"

*arrive at her house*

Lady : "you see, none of the web pages load, and my email refuses to sync. Should I call (insert isp name), or can you fix it?"

Me : I'm sure I can get it, gimme a sec.

*find the issue in a sec or two, dunno how to tell her about it, she isn't totally stupid*

Me : "Uhh, I don't know if you checked, but the ether.. internet cable isn't plugged in"

Lady : *realizes the wtf moment I'm having, obviously feeling very stupid*

Me : "Don't worry, happens to the best of us"

Obviously I lied a little, most of us would probably check the damn cable. Sometimes is just better to make people not feel like its their fault. People learn better when they don't feel like something is making a fool of them.

I have helped this lady with so many things that are just straight out of this world.

The one time she tried emailing 37mb tiff files over her 315kbps network.

Another time she said her email was not syncing, so I went to her house and clicked the "sync" button.

She even once phoned me to get their wifi password.

I just like helping her, somehow it makes me feel as if we all have something to learn.

Worst dev team failure I've experienced?

One of several.

Around 2012, a team of devs were tasked to convert a ASPX service to WCF that had one responsibility, returning product data (description, price, availability, etc...simple stuff)
No complex searching, just pass the ID, you get the response.

I was the original developer of the ASPX service, which API was an XML request and returned an XML response. The 'powers-that-be' decided anything XML was evil and had to be purged from the planet. If this thought bubble popped up over your head "Wait a sec...doesn't WCF transmit everything via SOAP, which is XML?", yes, but in their minds SOAP wasn't XML. That's not the worst WTF of this story.

The team, 3 developers, 2 DBAs, network administrators, several web developers, worked on the conversion for about 9 months using the Waterfall method (3~5 months was mostly in meetings and very basic prototyping) and using a test-first approach (their own flavor of TDD). The 'go live' day was to occur at 3:00AM and mandatory that nearly the entire department be on-sight (including the department VP) and available to help troubleshoot any system issues.

3:00AM - Teams start their deployments
3:05AM - Thousands and thousands of errors from all kinds of sources (web exceptions, database exceptions, server exceptions, etc), site goes down, teams roll everything back.

3:30AM - The primary developer remembered he made a last minute change to a stored procedure parameter that hadn't been pushed to production, which caused a side-affect across several layers of their stack.

4:00AM - The developer found his bug, but the manager decided it would be better if everyone went home and get a fresh look at the problem at 8:00AM (yes, he expected everyone to be back in the office at 8:00AM).

About a month later, the team scheduled another 3:00AM deployment (VP was present again), confident that introducing mocking into their testing pipeline would fix any database related errors.

3:00AM - Team starts their deployments.
3:30AM - No major errors, things seem to be going well. High fives, cheers..manager tells everyone to head home.
3:35AM - Site crashes, like white page, no response from the servers kind of crash. Resetting IIS on the servers works, but only for around 10 minutes or so.
4:00AM - Team rolls back, manager is clearly pissed at this point, "Nobody is going fucking home until we figure this out!!"
6:00AM - Diagnostics found the WCF client was causing the server to run out of resources, with a mix of clogging up server bandwidth, and a sprinkle of N+1 scaling problem. Manager lets everyone go home, but be back in the office at 8:00AM to develop a plan so this *never* happens again.

About 2 months later, a 'real' development+integration environment (previously, any+all integration tests were on the developer's machine) and the team scheduled a 6:00AM deployment, but at a much, much smaller scale with just the 3 development team members.

Why? Because the manager 'froze' changes to the ASPX service, the web team still needed various enhancements, so they bypassed the service (not using the ASPX service at all) and wrote their own SQL scripts that hit the database directly and utilized AppFabric/Velocity caching to allow the site to scale. There were only a couple client application using the ASPX service that needed to be converted, so deploying at 6:00AM gave everyone a couple of hours before users got into the office. Service deployed, worked like a champ.

A week later the VP schedules a celebration for the successful migration to WCF. Pizza, cake, the works. The 3 team members received awards (and a envelope, which probably equaled some $$$) and the entire team received a custom Benchmade pocket knife to remember this project's success. Myself and several others just stared at each other, not knowing what to say.

Later, my manager pulls several of us into a conference room
Me: "What the hell? This is one of the biggest failures I've been apart of. We got rewarded for thousands and thousands of dollars of wasted time."
<others expressed the same and expletive sediments>
Mgr: "I know..I know...but that's the story we have to stick with. If the company realizes what a fucking mess this is, we could all be fired."
Me: "What?!! All of us?!"
Mgr: "Well, shit rolls downhill. Dept-Mgr-John is ready to fire anyone he felt could make him look bad, which is why I pulled you guys in here. The other sheep out there will go along with anything he says and more than happy to throw you under the bus. Keep your head down until this blows over. Say nothing."

Dev checked in code (I suspect purposely not inviting me on the code review invite) saying he "fixed" the authentication bug in the web service.

Um no, like I told you last week, the authentication error is because the load balancer wasn't passing the user's authentication to IIS.

If I didn't overhear him telling a user "Still getting the error? I don't know, we might have to re-write that service", he might have gotten away with it.

Me: "Wait, that doesn't sound right. If I hit the server directly, authentication works. Its an issue with the load balancer, not the service"
Dev: "Admin said the load balancer is fine and it has to be the service."
Me: "I don't buy it. IIS is returning the authentication error, not the service."
Dev: "I added exception handling and nothing is being logged. Must be something in the service configuration."
Me: "No, IIS performs the authentication, not the service. I explained that last week, remember?"
Dev: "Oh yea. What changes do we need to make to the service?"
<my blood pressure starts to spike>
Me: "None. Give me a sec.."
<we have other apps on the same server farm that work just fine, so I re-configure the service pool settings to match theirs>
Me: "See, now going through the load balancer, the service works fine. For some reason, the admin had our service set up differently."
Dev: "OK, I'll let the users know the service is fixed."
Me: "Service was never broke and I'm not leaving it in its current state. In the morning I'll talk to the admin and see what he can do to fix."

Client: "Something is missing, like a type of BOOM or some fancy stuff, but I can't pinpoint what exactly. Do you know what I mean?"

Me: "Sure, give me one sec."
Changes font of a single word on a Web page to italic.

Client: "Perfect!"

My face: Priceless and trying not to laugh out loud.

Currently i have a small web dev project and i set up a live preview website so he cant see it developing and This literally Just happened

Client : hey, are you currently working on my website?
Me : Yes on my computer and working on it, can i help you with something?
C: yeah just a little bit, that logo on the top left are just a bit squeezed in size and stay like that since 5 days ago and it's bothering me, can you fix it?
Me : nah, its just a simple thing. give me a sec and try reload--
C: why is your voice echoing? Don't tell me you are coding in the bathroom
Me: ummm.. No... I guess...? (I Am)
C: 🤣
Me: sorry 😅

This new intern chose to write CSS instead of LESS/SASS even though I showed him how much time/lines of code were saved using LESS because he was "so used to it". Go ahead.. Enjoy writing 1 million lines of css to accomplish the same task.

While I was browsing the server through a ftp client, it froze for a sec and the next thing i notice is that a folder is missing. It was then when i found out the "drag'n'drop" feature.. Ofcourse it took me a few minutes to figure it out and ofcourse everything crashed. Btw, it was an asp.net web application I fucked up..on public..with more than 100 clients...o.o