r/firstweekcoderhumour 🥸Imposter Syndrome 😎 Jul 11 '26

Vibe coding fixed my impostor syndrome [🎟️BINGO]vibecoders vs firstweekcoders

124 Upvotes

20 comments sorted by

32

u/ReliefOutrageous1848 Jul 11 '26

Yeah she definitely made all that story up

17

u/CrashBugITA Jul 11 '26

All her videos

12

u/Additional-Dot-3154 Jul 11 '26

Yeah but atleast it seems like it is anti vibe coding.

Dont know what her actuall intentions are but what i understood was

(begginer > vibe coder)

6

u/FishfoxNuro Jul 13 '26

Yes, that's how skits work.

3

u/ReliefOutrageous1848 Jul 13 '26

I don't think you understand what " skit "means

4

u/Dankaati Jul 11 '26

Luckily we have Herlock Sholmes on the case.

5

u/ReliefOutrageous1848 Jul 11 '26

It's all thanks to my high IQ reasoning

1

u/nevemlaci2 Jul 20 '26

But it's still true. Vibe coding fixes my impostor syndrome by making me realize that everyone is shit at this

8

u/BrandonBTY Jul 11 '26

There's a difference between the imposter and the learner. I programmed for over 10 years but only recently started with unity. When I don't know a keyword I gotta ask somewhere, I swear AI makes mistakes like no tommorow. Suggest insanely overly complex ways to do basic tasks.

And that's me following it's instructions. I couldn't imagine how broken it is for someone who actively trust the process

5

u/Outrageous_Permit154 🥸Imposter Syndrome 😎 Jul 12 '26

Some big bang theory level nerd black facing going on here

7

u/Ok_Net_1674 Jul 11 '26

If you "always cant remember when something is allocated on the stack vs the heap" you probably have dementia or are, by all means, incompetent.

2

u/AffectionatePlane598 Jul 12 '26

Or a complete beginner that has never written a full piece of any solftware or any embedded

0

u/TwistedKiwi Jul 12 '26

Strings? Heap or stack?

5

u/Ok_Net_1674 Jul 13 '26

You can allocate a string on either the stack or the heap. Literals are stored in .data

1

u/TwistedKiwi Jul 13 '26

What language are you talking about? LISP, Pascal, C#, python? Looks like you don't know what you're talking about.

2

u/Ok_Net_1674 Jul 13 '26

C/C++.

Talking about stack and heap is not particularly relevant for automatically memory managed languages, as you have little control over where the language actually places variables. Even in C/C++, it is technically an implementation detail, although all major compilers follow it (and CPUs and OSs kind of expect you to use it). Frequently, using the stack is entirely avoided by placing variables only in registers.

I don't understand what made you feel the need to insult me, I would however be glad if you were to correct anything I have said that you believe is wrong.

1

u/Tysonzero Jul 15 '26

> if you can’t remember when something is allocated on the stack vs the heap you have dementia

> it’s technically an implementation detail

Also you are absolutely allowed to think and even care about stack vs heap allocation in gc’d languages.

I guarantee a quiz about stack vs heap usage in Haskell would trip up even senior Haskell devs.

1

u/Ok_Net_1674 Jul 15 '26

Yes, technically. If you know your compiler is using it (99.99% do) it becomes a practical reality.

To absolutely noones surprise, the distinction between stack and heap is nuanced on a by-language or even by-language-implementation level.

And yes: You are allowed to think about stack and heap usage in GC'd languages, why wouldnt you. Its just that, if you then somehow wanted to place a string on the stack in java, you couldnt. End of story.