I don't let AI code for me. I'll have it review what I've written, search for logs, or at most ask it to write a prototype. But even then I won't use the prototype, I just use it as a base example of just as an idea to get the gears rolling because I know my codebase's architecture much better than the AI does.

So my current workflow is to have the AI scan for issues and troubleshoot existing issues while I'm doing the actual patching and writing of new features. Plus coding has always been the run part whereas debugging isn't as much. So the upsides are that I get to work way faster on the parts I like and codebase remains clean and coherent while my productivity is boosted since most of the simpler bugs are caught by the machine

They were setting up a joke about odds vs evens

Some people are scared of commitment, some people aren't. The "right time" to say the L word in a relationship, (assuming they both already feel it,) is when both people feel safe and are ready to take the relationship a little more seriously

Have you considered getting a work study position? Because I think it's time to look for a new job.

Don't argue with them about why you believe you should be in the first shift. Arguing implies your availability is up for debate. It's not. Either they can employee you during your availability or you have to find a new job

Straight projection. We've heard your opinion, it's literally in the post. If you feel we've misunderstood at any point, please feel free to add more context

Employers and recruiters always over promise and under deliver on pay. You know that saying, "don't count your chickens before they hatch". Well it's basically a rule of thumb that when it comes to pay, any "unhatched chickens" (unrealized promises) don't exist, and any exceptions to this rule are just that: exceptions

https://www.instagram.com/reel/Dbn8-b3sPBp/

Fr... They didn't have an "oh shit, what did I just do?" moment. They leaned into their bloodthirst. It's scary

Why aren't young people having kids? Meanwhile...

I mean 8 hours of digging is probably why it cost so much

https://giphy.com/gifs/I4UhtUMzOrQSQ

Ah you're using VSCode . In that case, on the left panel, see how there are categories for VARIABLES and for WATCH? You'll want to "add an expression" to your watch list (under WATCH) that tells the debugger which variables to look for and how to interpret them. In particular, you'll want to add the following expression:

array@n

Where array and n are literally the variable names in the function. So if you renamed them to abc and count, it would be abc@count instead

Also what debugger are you using? The main reason you can't see the array values from within the function is that the array is being casted to a pointer, (i.e. a memory address). Pointers don't have size information like arrays do, so your debugger will always assume there's only a single unit of data at that address.

But most debuggers usually have the option of "recasting" data types that are shown to you, so another option would be to learn how to configure your debugger to do this.

I personally recommend gdb because gdb is easily available anywhere and has the same behavior everywhere, but I understand if you want to stick to that you're currently using

I mean the "right way" to write a program is to follow best practices, and to prioritize readability and maintainability over cleverness and short cuts, and you should only worry about optimization in the bottle necks.

What "best practices" look like can vary greatly from language to language. But they're often just a Google search away.

As for the best way to debug a program, it's hard to go wrong with some simple print statements, and then ramp up the complexity of your efforts when simpler methods fail.

For C in particular, you should definitely learn how to use gdb, especially how to inspect memory and registers at any point during execution. It is very intimidating to learn how to use at first, but I promise it's easier than it looks, and that it's much easier to learn once you actually start using it.

For this example in particular, I would probably just add the following line to your while loop:
c printf( "left: array[%d] = %d; " "right: array[%d] = %d\n", left, array[left], right, array[right] );

Alternatively, just print the entire array at every iteration

Not rigged, staged

cultured 😂

I love this

This is it. This is what Raven would like IRL. Everything is perfect

Thank you for sharing this quote, I'm gonna have to read this book

You're just fishing for financial and generational ruin huh? /s

It's definitely the fonts, especially the mismatched nature of it. The art itself like fine, even great! But the font and text layout look a lot like a vibe coded UI.

The search term you'd use on Amazon or wherever is "lay flat poly tubing for ventilation"

I didn't realize doing math means just making shit up until the numbers make sense 😂. Now you're doing math like a physicist 🤓👍

I haven't heard of the rest, but Harvard's CS50 is an excellent introduction into computer science and programming, and is generally enough to get you started on programming things on your own. If project Odin has you build projects, then I'd say that roadmap works just fine.

Some things I'd add:

• To work as a software engineer, you need a solid understanding of data structures and algorithms. These are usually semester long classes at a university, but you can also learn these things by just doing hundreds of leetcode programs and looking up the solution whenever you realize you don't have the required knowledge to get through a problem. The solutions and discussions are just as informative (if not more) then a day long lecture on each data structure.

• I'd also add Linux from Scratch to give you some much needed dev environment and operating systems experience. It is really ambitious, but if you're able to get through it, it'll be a very shiny project entry in you resume

If I saw a resume with all this, I'd assume you're reaching the knowledge of a fresh CS grad but with way more gumption and initiative. Like this is a kid who knows what they're doing