Jump in the discussion.

No email address required.

404'd

:marseygiveup:

Jump in the discussion.

No email address required.

Jump in the discussion.

No email address required.

:marseykingcrown:

Jump in the discussion.

No email address required.

How do these tards imagine that having a bot write it and then a human go over it meticulously looking for bugs is the right way to go? It probably takes as much time.

Jump in the discussion.

No email address required.

Because the current method is to have a human write it then have a second human go through their code and the bot is cheaper than the first person.

Jump in the discussion.

No email address required.

well the bot's getting paid $2000 a day right now :marseylaugh:

Jump in the discussion.

No email address required.

Because people fall for things that start faster. The idea of 90% done to 100% done taking longer than 0% done to 100% done seems silly.

Jump in the discussion.

No email address required.

Prob buts if I had a choice between working on 90 to 100 vs 0 to 90 I'm picking the former option.

I use GPT to write templates and then go from there, makes the day easier.

Jump in the discussion.

No email address required.

5 days to fix? How do you not have a bunch of duplicate key errors in your logs?

Jump in the discussion.

No email address required.

ChatGPT didn't say to put UNIQUE constraints on their ID columns.

>UUIDs are inherently unique :marseyclueless:

Jump in the discussion.

No email address required.

I am a full stack developer and do not see the issue with this logic

Jump in the discussion.

No email address required.

The uuid was only being generated once per server deployment. The first subscription attempt was successful after every deployment, but the next time someone made a request, the exact same uuid was being used and caused a conflict.

Jump in the discussion.

No email address required.

Easy: they don't have logs.

Jump in the discussion.

No email address required.

:marseyl#:

Jump in the discussion.

No email address required.

All they needed was a single integration test that created two or more subscriptions to find this issue since that's a common scenario (or at least two integration tests that created subscriptions). I have a feeling none of these r-slurs created an integration test.

Jump in the discussion.

No email address required.

Did none of these r-slurs test their shitty app after they deployed it?

Jump in the discussion.

No email address required.

Clearly a skills issue

Jump in the discussion.

No email address required.

using a dynamically typed language smh

Jump in the discussion.

No email address required.

Link copied to clipboard
Action successful!
Error, please refresh the page and try again.