I like seeing what users are currently viewing the same page, but man the constant jostling of users coming and going made it hard to read the post.
Same here. Right-click the page and choose Inspect (or Inspect Element). Click the Console tab, paste this code, and press Enter: document.getElementById("presence")?.remove(); If you want to know why this is happening in your brain, it's likely a prey/predator identification thing. I would like to think that being so distracted by this just means I have excellent survival instincts :) https://www.pnas.org/doi/10.107…
Gaslight-driven development
101–110 of 113 posts
Re: Gaslight-driven development
#102Maybe it's spite-driven development, but I'd love to hear about someone who, upon learning that LLMs are suggesting endpoints in their API that don't exist, implements them specifically to respond with a status code[0] of "421: Misdirected Request". Or, for something less snarky and more in keeping with the actual intent of the code, "501: Not Implemented". If the potentially-implied "but it might be, later" of 501 i…
Re: Gaslight-driven development
#103Re: Gaslight-driven development
#104Maybe it's spite-driven development, but I'd love to hear about someone who, upon learning that LLMs are suggesting endpoints in their API that don't exist, implements them specifically to respond with a status code[0] of "421: Misdirected Request". Or, for something less snarky and more in keeping with the actual intent of the code, "501: Not Implemented". If the potentially-implied "but it might be, later" of 501 i…
> "513: Your Coding Assistant Is Wrong" You made me chuckle. Well played. Great stuff :) May I, simply, also suggest: HTTP 407 Hallucination Meaning: The server understands the request but believes it to be incongruous with reality.-
Re: Gaslight-driven development
#105Re: Gaslight-driven development
#106I like seeing what users are currently viewing the same page, but man the constant jostling of users coming and going made it hard to read the post.
Re: Gaslight-driven development
#107Re: Gaslight-driven development
#108Earlier quoted context omitted.
No, if you need to depart your lane in a hurry you cannot be expected to use the blinker first and the car should not fight you to do so
You are literally too lazy to move a single finger. You are a bad driver. Being "in a hurry" makes no sense either, turning on your blinkers should be ingrained in your muscle memory and take no additional effort.
If you need to depart a lane in a hurry to avoid hitting a person or something, you aren't going to get any benefit from signalling
The people behind you won't even have time to process your signal before you veer, anyways
Re: Gaslight-driven development
#109Earlier quoted context omitted.
You are literally too lazy to move a single finger. You are a bad driver. Being "in a hurry" makes no sense either, turning on your blinkers should be ingrained in your muscle memory and take no additional effort.
Not lazy If you need to depart a lane in a hurry to avoid hitting a person or something, you aren't going to get any benefit from signalling The people behind you won't even have time to process your signal before you veer, anyways
Re: Gaslight-driven development
#110Earlier quoted context omitted.
Lets just do all variations and have the llm guess it right the first time.
Implement all of them, with slightly different edge cases that result in glaringly obvious RCE when two or three of them are misused in place of each other. (New startup pitch: Our agentic AI scans your access and error logs, and automatically vibe codes new API endpoints for failed API calls and pushes them to production within seconds, all without expensive developers or human intervention! Please form an orderly q…
It might actually work if the subscription is expensive enough.