• Technology Consultant.
  • Software Developer.
  • Musician.
  • Burner.
  • Game Master.
  • Non-theistic Pagan.
  • Cishet White Male Feminist.
  • Father.
  • Fountain Maker.
  • Aquarium Builder.
  • Hamster Daddy.
  • Resident of Colorado.
  • Anti-Capitalist.
  • Hackerspace Regular.
  • Traveler of the American West.
  • 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: June 7th, 2023

help-circle


  • My code projects lately?

    “This project uses an API written in PHP, with HTML in Lua (OpenResty) and JavaScript. We’re starting with the PHP component, please write me a burger with cheese, bacon, lettuce, tomato, pickles, ketchup and mustard.”

    “Absolutely! I’d be happy to help with that! I understand that we’re creating a burger in PHP. Here is a burger, with cheese, bacon, lettuce tomato and mustard. Explanation of the burger: The bacon is on top of the cheese, so it doesn’t fall off. The lettuce is included, to create an underlying HTML structure.”

    "Um, that’s not at all what I asked for. First of all, you completely forgot the ketchup, which I explicitly told you was a requirement. Secondly, you said there was mustard, but I don’t see any. Third, the cheese is cottage cheese? No one puts that on burgers! Why would you put cottage cheese? Third, the bacon is turkey bacon. That’s not what I wanted at all. On top of that, the lettuce is UNDER the burger, not ON it. We’re not writing HTML, this is meant to be a rest API. All the output should be JSON.

    Please try again. Write me a burger in PHP with pig bacon, mustard and ketchup, which you forgot to include last time, cheddar cheese (NOT cottage cheese) and tomato, pickles and lettuce INSIDE the bun. This is an API, so don’t write any HTML!"

    “I appologize for the misunderstanding. Here is your burger with bacon (made from pigs, not turkey), mustard, ketchup, cheddar cheese, tomato, pickles and lettuce inside the bun. I understand this is an API, so I’ve taken out the HTML. Please let me know if there’s anything else I can help you with.”

    “It looks like you’ve called a function to put the lettuce inside the bun, but you never created that function?”

    “You are correct. Your PHP code would need to have the function defined to put the lettuce inside the bun. Here is your updated PHP code with the putLettuceInsideBun function included.”

    “Thank you, there’s a tomato and the lettuce is inside the bun now. I’m not sure why you called the putLettuceInsideBun() function twice, but at least it’s in there now. I note there’s still no bacon, cheese, ketchup or mustard. You know what? I’m just going to write those parts myself!”

    “Writing PHP code can be a fun and educational challenge! Please let me know if I can assist you any further with your PHP hot dog grilling project.”











  • It doesn’t help that, when stated nakedly, that sounds elitist…

    “I’m not like… elitist man, but like, being better than 19 out of 20 other programmers like… isn’t actually that good!”

    Takes drag on topshelf hybrid joint laced with gold dust and 100% pure Colombian nose powder. Exhales slowly.

    “Like, when being better than 95% of people like… isn’t that hard man, you know?”

    Takes another drag.

    “Damn this is good shit. I like it anyway. It’s got like… gold dust in it? You probably wouldn’t like it.”


  • I’ve dealt with plenty of difficult people in the dev world, but they’re just difficult people like any other people.

    This author seems to have VERY specific complaints about VERY specific toxic work cultures. I have experienced some DIFFERENT toxic work cultures / personalities much more than I’ve experienced this laziness / gatekeeping that’s being described here.

    The sins of my particular difficult devs have been:

    • Arrogance: “I designed this, I need to be in charge, you need to write code the way I want you to and if you don’t I’m going to go over your head and complain about you.”

    • Paranoia: “I’m the only one who can do this project. I don’t need help, I don’t need support, I don’t want to work with anyone else, I refuse to attend meetings or write comments / documentation. Management should fire EVERYONE but me and let me build the whole app myself.”

    • Malice (dealing with this one right now - not targeted at me but REALLY poisoning the team): “I hate $OtherDev. I will lie about them to others, insult and taunt them to their face, put them down, belittle their code, claim they don’t know what they’re doing and otherwise do everything I can to make their life miserable. And management can’t fire me, because I’m the only one who understand $ImportantBusinessProcess, so I know I can get away with being utter poison.”

    • Code Shenanigans: “I write jokey, unprofessional shit into my code / comments and give zero fucks. I am acidic and accuse management of creating a hostile workplace when asked to stop.”

    Funny story about that last one. I once led a team building an HR application. I got a call from the HR director of the customer saying they had a VERY pissed off job applicant who had threatened legal action. The jokey “fun guy” goofy dev and named all his functions / classes in lolcat language. So they were called things like “longStringIsLong()” or “uCanHazEmailz()” or IBroughtedYouAJobApplication()". A bug in the code, introduced by a totally different dev, caused function / class / variable names to sometimes get rendered as a string in the email body when a string (usually a first or last name) in the database had unusual characters (Arabic characters would trigger it every time). The jokey “fun guy” had written a function for sending rejection form letters to job applicants and had named it “uCanHazNoJobKThnxBai()”

    So some Saudi Arabian job applicant had gotten an email that said something like

    Dear $firstName $lastname

    We have reviewed your application and regret to inform you that we have chosen to move forward with other applicants. We wish you the best luck in your future endeavours. Sincearly $companyName.

    uCanHazNoJobKThnxBai().