nugator

I think there's a difference here.

The AI end user is using the tool as intended by the manufacturer: "Book me a yoga class". If the tool does something illegal/harmful it is the manufacturer's fault.

If the power hammer user uses the tool as intended but it explodes, it is the manufacturer's fault.

If the AI end user says "Hack the yoga website" or the power hammer user uses the tool to destroy something it's the end user's fault.

Pair programming requires a lot from you and your relationship with your pair programming partner.

When it's working I think it's absolutely great. Together we find the best solution in the fastest time with less errors along the way. I'm also less sloppy and more focused when someone constantly sees my work and vice versa. At the end of the day you can celebrate what you've done, both feel responsible for the work and knows exactly how it works.

Works well if you're communicating while you're making changes in code.

At my work 20 people are changing the same wiki-page when we do heavy regression tests. Works like a charm (not everyone is writing at the same place in the document since we are testing different things and writing results at different sections).

I like it because we don't have to do the this dance all the time: * Commit * Push * Say: Now it's pushed * Pull

We can just work together, talking and writing code. Works great with people you work well with and are aligned with.

So how much would you say this have cost you so far? Just $200 for this month?

~3.86B * $5/M tokens ≈ $19.3k

Is that the cost you've payed for this or is my calculation completely wrong?

If it's like the commercials in the movie the Truman show I think this could be a nightmare.

I think it all boils down to how (if?) this will be transparent to the user.

If the response suggests a sponsored product/service to the user it could either be the specific product/service that ChatGPT is biased to suggest or the whole idea of using a product/service. As a user I would like to know both of these biases to understand that using any product/service for my need might not even be the best thing.

> Made it harder to be the "come on guys! we can win this" coach when we were down on points + bodies.

Would you say that paintball on that level is almost deterministic? Compared to, for example, (American) football where momentum and perseverance can turn games around completely.

I work at a Swedish state authority and we don't have architects deciding software architecture, the teams do that themselves. There's however an "architecture guild" composed of about 6-8 senior architects that happily help you out if you want to have help, suggestions or review of your current or future architecture. I think that's a nice way of having good support if you need it.

Citation please.

Don't write another line of code. Setup mob programming with your colleagues and stay away from the keyboard. Instruct them what to do and answer all their questions. It will be slow at first but highly deliberating when they've understood the task and they can be more or less autonomous.

What field is that and how do you achive that?

I'm willingly pigeonholing myself as a "software developer mostly working on the JVM" just to be honest about my (current) main strengths/experince. Throwing me into a Go/Python/whatever project would first need some time for me to get up to speed with the language.

Are you saying that everyone understanding science and basic statistics should be pro nuclear power plants as the best way of generating power?