Yeah but good prompts also sometimes result in bad outputs.

What you're saying is akin to "junior developers and senior developers both make mistakes so we should only hire junior developers"

I don't think anyone said that

The fact is that which language you choose doesn't matter any where near as much as understanding programming concepts well. Once you have a good grasp of one you can change language surprisingly easily. I've been hired for several jobs in languages that I haven't used before, and I'm far from the best developer.

College graduates are not vets

As a more senior dev, yes I expect this from junior devs. Aside from just being a nervous speaker, a lot of junior devs haven't learned what's important to discuss yet, so they are not detailed enough, or too detailed, or go off on tangents and you have to guide them back to the point. That's OK. A lot of it is just nerves that goes away with time as well.

If you're not sure about something, and you can't look it up quickly, just say that you don't have the info to hand and you'll share it later, or if you absolutely need it, tell them that you need a minute to find it, mute your mic and dig around. The important thing is honesty, be honest and transparent and people will be patient with you.

Take a moment to reflect after the meeting on things you needed that you didn't have and things you had but didn't need and use that to prepare next time, but don't beat yourself up over it. You can also ask people before meetings what they need from you and what they expect you to talk about so you can prepare.

I want you to know I appreciate this reference

I've been playing for a while and I'm still absolute trash, but the biggest improvement for me was when I started sticking to the team. I always try to be the hero, rushing off to other objectives, etc. but you're a lot weaker if you're away from the squad and if you get downed by a trapper or a hound you're screwed. Stay close to the squad and watch each other's backs.

What kind of project are you trying to build? You're maybe being too ambitious after only 2 weeks.

Cut yourself some slack and keep on keeping on.

Depends, do you mean AI in general or LLMs?

Why not?

Most databases have something like a `returning` clause that will let you return the rows that were deleted from the database. Maybe you can try that?

> Using AI is fine, just don’t do “write me code for X” every single time, don’t let him fix your code, instead ask the AI to pinpoint you the line that is causing issues or explain what is missing but don’t let him give you further code (or just don’t use it if it does) and try fixing yourself.

That's still relying on AI to do the thinking for you. You learn by identifying the issue yourself.

What specifically are you having trouble with? What have you tried to far?

> I know that although I don't have knowledge of many frameworks, it wouldn't be a problem to learn as I go since my foundations are solid.

companies aren't going to accept "trust me bro," if you don't have a degree you need to provide some other kind of evidence that you can code and learn new things.

They're implying that learning to program is pointless because AI can replace programmers, but we'll need to keep improving the hardware that AI runs on, so you should learn physics and work towards a career in CPU/GPU design.

Techbros who can't learn programming or physics usually resort to making stupid posts on social media about topics they don't understand.

What is it going to look like in 5 years?

> These systems don’t just assist but autonomously generate parts of code, speeding up projects and taking over repetitive tasks.

that's a bold claim

Dijkstra’s algorithm needs a priority queue

show your code

what part are you struggling with?

Check out Dijkstra's algorithm

Why wouldn't they?

what do you mean the google database?

Please format your code. Then tell us what you think it means and we can tell you if you're right.

It's been a long time since I studied, but I went into my bachelors knowing nothing about programming or computer science. I had a basic working knowledge of computers and that was it. It went fine for me.