TWIL July 17th 2026
- After spending far too long wondering if things are safe to have in the URL I'm of the firm belief that every request type should allow a body
- Luckily the upcoming QUERY method has my back
- It's possible for a professional, senior web developer to not know how to use a native multi-select
- And of course he suggested a JS package which provides a dropdown select as an alternative
- The JS framework brainrot is real
- A commonly overlooked drawback of using LLMs is the effect it has on other people's productivity
- For example, you have an LLM generate a support ticket in English from the external Japanese ticket.
- The internal ticket is now about 8 paragraphs long and has 2 lines of useful information, but devs have to read all of it to find those two lines
- Being a nice helpful CS person you ask Claude what it thinks the problem might be
- Claude has no idea what it's talking about so it spits out a wall of nonsense, but because you're not a dev you don't know that
- You post your 'analysis' on the ticket as a comment
- Devs now have to respond to address the 'analysis' because a human posted it despite it being nonsense AI slop, taking time away from actual investigative work
- Your chat with Claude potentially caused you to respond slowly to actually important questions from the devs
- Get your feature in the hands of people who'll use it as soon as possible, they'll point out all sorts of things you wouldn't think of
- Just because other jobs using the same AWS context in CI can do stuff to staging, doesn't mean the same context lets you do different stuff
- I would've expected permissions issues for the specific thing I was trying to do, but that's not the case
- Seems I need to do something to opt into staging rather than prod creds?
- Will look at other projects which apparently switch between the two to figure it out
Links
- Data landscape guide for developers - OlegWock
Could be handy if I ever need to work closely with AI & DS or at a future job.