I found your channel a handful of months back and basically took all your vim talk as "What's the worst that could happen?" and gave it a serious try. My guy, I am now using it full time, have moved fully over to linux, have installed vim key shortcuts on firefox and everything else, am using sway tiling window manager instead of gnome, tmux, the whole show. It is madness how much everything changes just by learning to navigate one application by keyboard alone. My wife calls me silly when I express disdain at having to use a mouse on her computer. You have damaged me irreparably.
regarding the first tiktok, this exactly what happen to me in Sep this year. For over 2y I heard that everything is fine I am doing ok, and suddenly they call me and say, bye bye.
When this happens, how should one react? Can you bring this to a lawyer or something? I imagine that fighting to stay at the company isn't the best move, your career will pretty much be stunted. How do you explain this to your next employer?
@@hotgoosezion547if you're in the US you are probably in at-will employment which means that you can leave at any time and they can fire you at any time, no cause needed.
The moment you add prints and your code starts working is when you realize you're in serious trouble. At least you know a race condition is more likely than memory corruption. When you switch from optimized to debug and it starts working, though... that's where the fun begins.
A friend friend once asked me help to debug a piece of c++. The code behaved differently if we changed the order of declaration of the variables or if we used a different compiler. Turns there was an off-by-one error while reading inside an array
wait, does c++ just let you access out of bounds stuff without giving you an error? And the out of bounds thing you reached was whatever you declared earlier..?
@@anima94 It is undefined behavior, it could crash or it could just read whatever chunk of memory is after it. That's how a lot of vulnerabilities are created
I remember writing some audio processing code for the browser. It was one of the most basic algorithms to make music play slower/faster while maintaining the same tone. I spent hours, at the end of the day, arbitrarily changing coeficients for the algorithm. After some time, it started to sound without almost no audio artifacts/distortions. And after some more time, i came to my senses and thought "why is this working so well? The papers and all the other implementations have a bunch of audio artifacts...bruh wtf lol". The code is still up and i remember the faces of the biggest experts in the field when i presented it at a conference and said "I have absolutely no idea why this sounds so good, it shouldnt but it does".
Tiktok is like watching AI generated videos: it takes all the content it's seen and it has no idea how comedy is made, but it puts the necessary stuff in. It's not like a human who has intuition about what's funny and who's able to plan, then reflect on the plan, then execute and review it. It just shoots out the components of all the other stuff. Or like a baby that tries things out by trying to copy what it sees with no ability to parse what the real meaning of it is. The greatest common denominator or something.
The reason you don't get any feedback based on performance before they layoff is that the layoff is broad across many people, it's not based on your performance. So your direct manager didn't let you down. They had no feedback to give that could help this situation.
I love the machines they have, it looks so much like they are actually have their live in order. My machine is a 20 year old big tower which I upgraded to somewhat new hardware, my desk is full of papers and stuff and a soldering iron and the keyboards. And the screens are used ones I got for cheap and they are different sizes
Inserting a print and having it work is like, almost always pointing directly to some sort of race condition, which I find to be an incredibly helpful clue for debugging. It's only really soul-crushing when the race condition exists in some other code you're relying on and it's structured in such a way that there's no way to *fix* the race condition and so you just have to fall back on hacky process waits and finger-crossing.
When print statements "fix" your code it could be an indicator for concurrent problems under the hood. The stdout is synchronized and when you start to print while stuff happens, atuff will be synchronized. The moment you remove the little cheeky print, order collapses and its fudged again.
Small talk is one thing, but having 2 daily meetings is fucking hilarious (in the morning internal one with ppl from europe, and in the afternoon meeting with american clients). I literally say the same thing but with just different tense. In the morning "I will work on XD-123" and later in the day "I worked on XD-123" AND IT TAKES 1H every single day.
The "why is this working" thing is to me one of the major differences between a new and an experienced programmer. The new programmer's reaction can be seen in that TikTok; the experienced one (incl Mr Prime) first feels their pain) and then realises that that is one of the biggest red flags in the business: if something works and you don't know why, Ctrl-A, Delete
True, even if you figure out it after some time, it's probably too complicated to begin with. It's like a plumber saying - if you need to connect 5 pipes together, you screwed up hour ago so start over
I don't really get the whole "its working but I don't know why" thing. If im writing a piece of code, I have a goal in mind so if it works it's because that goal is being accomplished
@@sa1t938 you probably take hours to build things then. Most people (after some experience) can usually write some code that does the thing, only from the unknown instinct and only then understand what it does properly. It's kind of like writing a novel when you are drunk, and thinking "how did I write this?? it's so genious, I can't even continue it now" next morning when you are in your normal senses. Well I have this experience a lot. Simply said it's just the difference between people who write their code by their instinct (like drawing art, singing etc.) vs people who write their code fully rationally. Usually first type of people is rare because code itself is more math-y and concrete, but people who write a whole lot of code and who are very creative sometimes become that "instinct" type. It's neither good nor bad imo.
@@sa1t938 Thing is, if you don't know Why something is working, it may, no, will, break the moment you change anything. If you have that sort of code you are not in control. And if you're not in control, chances are something or -- worse -- someone else is, and that usually doesn't end well
Even with a bunch of experience, you can still occasionally hit "why does this work?", it's just that you're a lot better at figuring it out, so it's not as notable. "Why doesn't this work", in the other hand, is eternal. For me, the closer example for the difference experience makes is the "No, there's no way this code is broken. All the tests pass, I have 100% coverage, it hasn't been changed in a year, the bug is definitely somewhere else." Narrator: it was not.
Friendly reminder that we were all onboarded on social media to keep up with what our friends are doing. We are so far past that. It’s just random noise now.
tiktok programming is a bunch of failed wannabe programmers trying to become content creators by remaking every coding "funny" trend and it's just not cool anymore...
When he said 2 print statements to fix a bug. Reminded me when I saved 2 times to db in hibernate to make sure it got flushed. That fixes a random bug where few are not properly saved to db.
6:22 5 PM, you feel bad that you couldn't focus during the day and you fell like you did nothing, so you stay trying to code something until 8 PM, take a break, go back to it at 11 PM because you still feel like shit and you need to have something to tell about on the standup meeting in the morning.
Possibly hot take: if she wants to have a streamboard to open apps let her have it. If the speed you open your emails is something you need to optimise (outside of optimising for personal enjoyment), something went terribly wrong
Yup -- it was 30 of January 2023, I had an appointment with my head of department. Little did I know that HR was also invited.... Boom! My team was gone
my standup calls consists of 6 developers + project lead and its 15 minutes long, my speech there lasts a maximum of 15 seconds.... some people even take 3 minutes, its hell on earth.
i commented on one of the videos back when i wasnt that good at programming and now its engraved into history thanks to this video gosh i hate myself for this why why why why
4:00, UB. The bug use to start before. That's 1 of the reasons I like to have several conditional compilation: I start switching those switches, and may get rid of the UB. So I know in which section it started. About her code: didn't she run into an infinite recursive loop? 6:15, it's over, time to go!
"the thing that mostly gets me is not when something does or does not work like that, but when i put in a print statement and it starts working" this right here, this is when i start doubting my abilities the most
I have been teaching myself Python and have been using VSC.... I couldn't count how many times I've had a program I've written not work, not be able to run it, have everything look fine, walk away for an hour or two out of frustration, just to come back and have it run no issue when I come back....
lmao this actually changed my life. installed wsl2 because of that viewer, and now im using screen and neovim to do some basic stuff from windows. being able to just dos tuff from command line without dealing with windows shenanigans is amazing. i just follow along python tutorials without hating life. maybe ill get that wubuntu
6:22 - false. what we do is go do not disturb or appear offline, alt+tab to something we'd rather be doing and do that. What is this "get up out of the chair when its quitting time because we want to do something other than computer stuff" stuff?
I might be different here - I am all about working 100% remote, but I am ok of having tons of chitchat in standup meetings, I don't mind. That's the "socialization" that satisfies me, but no more than that, I don't even want to exist in the office anymore.
I think what makes Tiktok most successful, above all other factors, is its global availability and ease of access to those that obsess over social media attention and followings. Personally, it looks like spyware.
Looks like? You are too kind with your soft words. Tiktok is an infectious plague that primarily affects intelligence. Its like CIP but instead of pain its SHAME they can no longer feel
I mean, even if it is directly feeding information on its users to the CCP, which it definitely is, that revelation won't stop little Timmantha from chasing likes
Translation for people who do debugging using debuggers: When he says "I put in a print statement", imagine he said "I add a breakpoint" (+ "I recompile")
I love it when "I still don't even get - I don't even get TikTok yet, okay? I don't get it. I didn't get it before, i still don't get it today. Okay? I'm too old, or too young. I'm one of the two. And i don't know which one it is. But I'm not the correct age, for whatever this is. Whatever just happened on my screen ... I'm either a boomer or a zoomer. One of the two"-agen uploads a new video
Lowkey code written by overconfident senior engineers that thing everyone knows things as well as they do is way harder to read then a junior who is taking his time because he doesn’t know what’s going on.
The thing only a Junior dev would say. I would rather read 5 lines of code that elegantly does the thing, one by one, by understandable chunks, than 20 lines written by a junior who used a for loop, a bunch of clunky if elses, 2 disconnected arrays and god knows what else weird techniques they think the problem can be solved with, potentially filled with bugs. I really dislike that people are degradating their code for no reason. If you don't understand someone's code, learn it and it's done. Drop that loser mindset. You should improve your understanding and your code quality, not degradate.
@@twothreeoneoneseventwoonefour5 The senior engineers I know are the ones that write the second one, commit without comments (svn is brand new technology) and if anything needs to be fixed, they copy-paste, wrap it in if-else and pass in feature flag from somewhere. And god forbid you do foreach anywhere, don't you know it's sloooooow?
@@BlazingMagpie are they senior engineers then?.. I'd say not really. I am (almost) a senior engineer and I always try to write efficient, eloquent and (at the same time) practical code when possible. It is not simple by any standard, but it is succinct and clear once you understand it. Like a poem?.. Well maybe I am just an abnormal engineer in current age lol. I will not go out of my way to oversimplify, or overengineer something, but I will certainly use some new language features added recently(that will be compiled away by the bundler anyway so no worry there), or less known features like ?? or ??= operators when they are applicable, or an optimization hack that can only be explained with a three line long comment, because it is actually valuable.
@@BlazingMagpie Those sr developers suck. Sr doesn't just mean you've been doing it a long time. It implies some level of skill. Those are just juniors that never grew.
I used to have that issue where I added a print statement and then my code started working. Then I stopped using eclipse. Now my ide builds the current code every time.
There are small pockets of actual meaningful programming and tech discussion happening on tiktok, but the jokes and zoomer humour is what appeals to the masses.
4:10 i avoid using print statements, unless i know shit's unfixably fucked and need to know what the exact value of some fucked shit is. You never know what fuckery your code/print implementation might be up to.
I don't think adding volatile is something you want to do except perhaps a part of a debugging effort. If the optimizer is being too aggressive and optimizing your code so you have incorrect semantics, you almost certainly have a case of undefined/unspecified behavior on your hands and the better solution would be specify the semantics correctly.
Can also be various forms of undefined or unspecified behavior: memory corruption, indeterminate expression evaluation order, overflow, that sort of thing.
I had that happen to me before at a really small company. For 1 year they said everything was good and everyone liked me. Then I asked for a pay raise review and the review went awful and they said I was terrible. Like, couldn't you tell me that during the year? And then a month later I was laid off because they didn't "have the money." Which I think was true, but it was a bit weird after I got a really bad review.
Prime I totally feel u man. I don't get it either. Tiktok is just this enigmatic black whole that absorbs every last one of your brain cells if you dare to scroll for more than 2 minutes. I am 21 y/o, almost all of my friends use it. I really don't understand the purpose of it but still I am weird to not know what the name of this one dancing toilet head thingy is. Sure, Andy.
Prime forgets to turn off alerts as frequently as there is a new js framework developed
about 2 x a week?
@@ThePrimeTimeagen FIVE DOLLARS A MONTH!!!
Check out our new blazingly fast framework alertdisablr.js!
2x per day
He needs an ElGato stream deck to turn off it
I found your channel a handful of months back and basically took all your vim talk as "What's the worst that could happen?" and gave it a serious try. My guy, I am now using it full time, have moved fully over to linux, have installed vim key shortcuts on firefox and everything else, am using sway tiling window manager instead of gnome, tmux, the whole show. It is madness how much everything changes just by learning to navigate one application by keyboard alone. My wife calls me silly when I express disdain at having to use a mouse on her computer. You have damaged me irreparably.
I absolutely love that you shared this, thank you very much. Another life ruined
loooooooooooooooool
@@ThePrimeTimeagen
@@ThePrimeTimeagencan we smash
@@ThePrimeTimeagen 😂😂
The one with the guy working at his desk and “deep focus” sessions is me 100% 😂 And when it hits 5 I close every window and peace out.
regarding the first tiktok, this exactly what happen to me in Sep this year. For over 2y I heard that everything is fine I am doing ok, and suddenly they call me and say, bye bye.
yeah, it happens, i am a bit shocked it does, but i have heard of this
I wonder if they said "gottem" after
When this happens, how should one react? Can you bring this to a lawyer or something? I imagine that fighting to stay at the company isn't the best move, your career will pretty much be stunted. How do you explain this to your next employer?
@@hotgoosezion547if you're in the US you are probably in at-will employment which means that you can leave at any time and they can fire you at any time, no cause needed.
You can see his braincells fly away watching these.
The moment you add prints and your code starts working is when you realize you're in serious trouble. At least you know a race condition is more likely than memory corruption. When you switch from optimized to debug and it starts working, though... that's where the fun begins.
Bro the pain. The code is gaslighting you
A friend friend once asked me help to debug a piece of c++. The code behaved differently if we changed the order of declaration of the variables or if we used a different compiler. Turns there was an off-by-one error while reading inside an array
typical undefined behavior stuff 😱
wait, does c++ just let you access out of bounds stuff without giving you an error? And the out of bounds thing you reached was whatever you declared earlier..?
@@anima94 It is undefined behavior, it could crash or it could just read whatever chunk of memory is after it. That's how a lot of vulnerabilities are created
@@iron7956wow I didn't know that, kinda makes sense that it gives you the freedom to do so but I expected the compiler to at least mention something
There are access methods that use bounds checking for containers (.at()) but many programs opt not to use it for performance reasons.
"Yesterday I did what suppose to do yesterday and today I'll do what I am suppose to do today" was a good onw.
I remember writing some audio processing code for the browser. It was one of the most basic algorithms to make music play slower/faster while maintaining the same tone. I spent hours, at the end of the day, arbitrarily changing coeficients for the algorithm. After some time, it started to sound without almost no audio artifacts/distortions. And after some more time, i came to my senses and thought "why is this working so well? The papers and all the other implementations have a bunch of audio artifacts...bruh wtf lol". The code is still up and i remember the faces of the biggest experts in the field when i presented it at a conference and said "I have absolutely no idea why this sounds so good, it shouldnt but it does".
FFT coming in clutch
Where can I find it?
Tiktok is like watching AI generated videos: it takes all the content it's seen and it has no idea how comedy is made, but it puts the necessary stuff in. It's not like a human who has intuition about what's funny and who's able to plan, then reflect on the plan, then execute and review it. It just shoots out the components of all the other stuff. Or like a baby that tries things out by trying to copy what it sees with no ability to parse what the real meaning of it is. The greatest common denominator or something.
This sums it up perfectly. These all have the form of skits but there's no jokes. It's so bizarre
That "-agen" at the end of the long rant was perfect 🤣 the longer it went I got more worried that you would forget
The reason you don't get any feedback based on performance before they layoff is that the layoff is broad across many people, it's not based on your performance. So your direct manager didn't let you down. They had no feedback to give that could help this situation.
I love the machines they have, it looks so much like they are actually have their live in order.
My machine is a 20 year old big tower which I upgraded to somewhat new hardware, my desk is full of papers and stuff and a soldering iron and the keyboards. And the screens are used ones I got for cheap and they are different sizes
Sounds like a chad hardware setup
sounds practical babyyy, you get work done!
I have so much stuff on my dask, I have to use my whole arm to sweep some room for the laptop :D. And there's like 5 miles of cables in here.
That last one tho was honestly relatable. The other ones are clearly from script kiddies that do TikTok more than coding
Yup. Especially the two breakdowns a day. 😂
4:40 From my experience this always happens when you have something which is lazily evaluated but shouldn't be.
3:58 The inserting a print statement and it working thing is so on point it actually hurts my soul.
Now that I think about it....
Inserting a print and having it work is like, almost always pointing directly to some sort of race condition, which I find to be an incredibly helpful clue for debugging. It's only really soul-crushing when the race condition exists in some other code you're relying on and it's structured in such a way that there's no way to *fix* the race condition and so you just have to fall back on hacky process waits and finger-crossing.
Sometimes, it really is the children that are wrong.
When print statements "fix" your code it could be an indicator for concurrent problems under the hood. The stdout is synchronized and when you start to print while stuff happens, atuff will be synchronized. The moment you remove the little cheeky print, order collapses and its fudged again.
Small talk is one thing, but having 2 daily meetings is fucking hilarious (in the morning internal one with ppl from europe, and in the afternoon meeting with american clients). I literally say the same thing but with just different tense.
In the morning "I will work on XD-123" and later in the day "I worked on XD-123"
AND IT TAKES 1H every single day.
I had to watch this video muted because I knew tiktok programming is going to be cringe af
careful, once you catch the cringe....
if you gaze into the cringe, the cringe gazes also into you. (c)
@@ThePrimeTimeagenPerhaps i am cringe, but that makes me free.
The "why is this working" thing is to me one of the major differences between a new and an experienced programmer. The new programmer's reaction can be seen in that TikTok; the experienced one (incl Mr Prime) first feels their pain) and then realises that that is one of the biggest red flags in the business: if something works and you don't know why, Ctrl-A, Delete
True, even if you figure out it after some time, it's probably too complicated to begin with. It's like a plumber saying - if you need to connect 5 pipes together, you screwed up hour ago so start over
I don't really get the whole "its working but I don't know why" thing. If im writing a piece of code, I have a goal in mind so if it works it's because that goal is being accomplished
@@sa1t938 you probably take hours to build things then. Most people (after some experience) can usually write some code that does the thing, only from the unknown instinct and only then understand what it does properly. It's kind of like writing a novel when you are drunk, and thinking "how did I write this?? it's so genious, I can't even continue it now" next morning when you are in your normal senses. Well I have this experience a lot. Simply said it's just the difference between people who write their code by their instinct (like drawing art, singing etc.) vs people who write their code fully rationally. Usually first type of people is rare because code itself is more math-y and concrete, but people who write a whole lot of code and who are very creative sometimes become that "instinct" type. It's neither good nor bad imo.
@@sa1t938 Thing is, if you don't know Why something is working, it may, no, will, break the moment you change anything. If you have that sort of code you are not in control. And if you're not in control, chances are something or -- worse -- someone else is, and that usually doesn't end well
Even with a bunch of experience, you can still occasionally hit "why does this work?", it's just that you're a lot better at figuring it out, so it's not as notable.
"Why doesn't this work", in the other hand, is eternal.
For me, the closer example for the difference experience makes is the "No, there's no way this code is broken. All the tests pass, I have 100% coverage, it hasn't been changed in a year, the bug is definitely somewhere else."
Narrator: it was not.
Friendly reminder that we were all onboarded on social media to keep up with what our friends are doing. We are so far past that. It’s just random noise now.
tiktok programming is a bunch of failed wannabe programmers trying to become content creators by remaking every coding "funny" trend and it's just not cool anymore...
When he said 2 print statements to fix a bug.
Reminded me when I saved 2 times to db in hibernate to make sure it got flushed. That fixes a random bug where few are not properly saved to db.
6:22
5 PM, you feel bad that you couldn't focus during the day and you fell like you did nothing, so you stay trying to code something until 8 PM, take a break, go back to it at 11 PM because you still feel like shit and you need to have something to tell about on the standup meeting in the morning.
The manic bastard at 2:36 uses Title_Snake case. What in the hell even is that?!
"Why does it look so thick" while looking at a girl is wild 💀(joke ofc)
i thought the context was clear, but my editor made fun of me the exact same way
lmao yea i laughed so hard about that too :D
@@ThePrimeTimeagen the context was clear, but the switch-up mid-sentence is still funny nonetheless
😶 he said "so creamy as well"
Possibly hot take: if she wants to have a streamboard to open apps let her have it. If the speed you open your emails is something you need to optimise (outside of optimising for personal enjoyment), something went terribly wrong
There’s times where I look at my old code and it takes me a good hour to figure out what I was even doing 😂
Yup -- it was 30 of January 2023, I had an appointment with my head of department. Little did I know that HR was also invited.... Boom! My team was gone
my standup calls consists of 6 developers + project lead and its 15 minutes long, my speech there lasts a maximum of 15 seconds.... some people even take 3 minutes, its hell on earth.
I haven't seen any TikTok programming before and was excited to see some good memes.
As you may guess, my day is utterly ruined.
same, it hurts my soul
6:23 The most unrealistic part of this is the logging off at 5:00pm part, more like 11:00pm
i commented on one of the videos back when i wasnt that good at programming and now its engraved into history thanks to this video gosh i hate myself for this why why why why
Even as someone who enjoys watching tiktok reacts, this was particularly painful.
Programming tiktoks should be a new circle of hell.
Oh god why did you remind me about logging making the bug go away, that hurt me emotionally, I had forgotten about JS doing this.
4:00, UB. The bug use to start before. That's 1 of the reasons I like to have several conditional compilation: I start switching those switches, and may get rid of the UB. So I know in which section it started.
About her code: didn't she run into an infinite recursive loop?
6:15, it's over, time to go!
When print/logging out to console magically makes things work.
You're not "experienced" until that has happened to you at least once.
WT-actual-F!
95% of the time it's going to be a memory issue UB or a race condition. In fact that's true in general for non deterministic bugs.
"the thing that mostly gets me is not when something does or does not work like that, but when i put in a print statement and it starts working"
this right here, this is when i start doubting my abilities the most
I have been teaching myself Python and have been using VSC.... I couldn't count how many times I've had a program I've written not work, not be able to run it, have everything look fine, walk away for an hour or two out of frustration, just to come back and have it run no issue when I come back....
lmao this actually changed my life. installed wsl2 because of that viewer, and now im using screen and neovim to do some basic stuff from windows. being able to just dos tuff from command line without dealing with windows shenanigans is amazing. i just follow along python tutorials without hating life. maybe ill get that wubuntu
6:22 - false. what we do is go do not disturb or appear offline, alt+tab to something we'd rather be doing and do that. What is this "get up out of the chair when its quitting time because we want to do something other than computer stuff" stuff?
0:25 song: My Live Mine All Mine
I might be different here - I am all about working 100% remote, but I am ok of having tons of chitchat in standup meetings, I don't mind. That's the "socialization" that satisfies me, but no more than that, I don't even want to exist in the office anymore.
I think what makes Tiktok most successful, above all other factors, is its global availability and ease of access to those that obsess over social media attention and followings. Personally, it looks like spyware.
Looks like? You are too kind with your soft words. Tiktok is an infectious plague that primarily affects intelligence. Its like CIP but instead of pain its SHAME they can no longer feel
Like Instagram
Well, it *_is_* spyware. (Lookin' at you, Winnie the Pooh.)
I mean, even if it is directly feeding information on its users to the CCP, which it definitely is, that revelation won't stop little Timmantha from chasing likes
Can’t believe it took almost 5 minutes for someone to ask Prime to stop…
skip to 8:10
Translation for people who do debugging using debuggers: When he says "I put in a print statement", imagine he said "I add a breakpoint" (+ "I recompile")
Printagen
People who use debuggers still know what a print statement is bro 😂
It still amazed me that Americans can just be fired like that. No protection whatsoever. We don’t need you anymore, bye. It’s crazy.
3:05 You're wrong, it was the netcode, that shit will suck the life out of you. - A network eng.
I love it when "I still don't even get - I don't even get TikTok yet, okay? I don't get it. I didn't get it before, i still don't get it today. Okay? I'm too old, or too young. I'm one of the two. And i don't know which one it is. But I'm not the correct age, for whatever this is. Whatever just happened on my screen ... I'm either a boomer or a zoomer. One of the two"-agen uploads a new video
5:56 to 6:25 is the most relatable 30secs I’ve ever seen in my career😂😂
Lowkey code written by overconfident senior engineers that thing everyone knows things as well as they do is way harder to read then a junior who is taking his time because he doesn’t know what’s going on.
The thing only a Junior dev would say.
I would rather read 5 lines of code that elegantly does the thing, one by one, by understandable chunks, than 20 lines written by a junior who used a for loop, a bunch of clunky if elses, 2 disconnected arrays and god knows what else weird techniques they think the problem can be solved with, potentially filled with bugs.
I really dislike that people are degradating their code for no reason. If you don't understand someone's code, learn it and it's done. Drop that loser mindset. You should improve your understanding and your code quality, not degradate.
@@twothreeoneoneseventwoonefour5 The senior engineers I know are the ones that write the second one, commit without comments (svn is brand new technology) and if anything needs to be fixed, they copy-paste, wrap it in if-else and pass in feature flag from somewhere. And god forbid you do foreach anywhere, don't you know it's sloooooow?
@@twothreeoneoneseventwoonefour5simple and more explicit code is always better.
@@BlazingMagpie are they senior engineers then?.. I'd say not really. I am (almost) a senior engineer and I always try to write efficient, eloquent and (at the same time) practical code when possible. It is not simple by any standard, but it is succinct and clear once you understand it. Like a poem?.. Well maybe I am just an abnormal engineer in current age lol. I will not go out of my way to oversimplify, or overengineer something, but I will certainly use some new language features added recently(that will be compiled away by the bundler anyway so no worry there), or less known features like ?? or ??= operators when they are applicable, or an optimization hack that can only be explained with a three line long comment, because it is actually valuable.
@@BlazingMagpie Those sr developers suck. Sr doesn't just mean you've been doing it a long time. It implies some level of skill. Those are just juniors that never grew.
skill issues all around, yet somehow it's never their own fault lol
I cringe so hard, I can't look at it anymore, but I gave it a like because you sacrificed to go through this!
5:35 Brother, she on Windows, what window manager 💀
Stumbled about this just today. I'm glad not being the only one who doesn't get tiktok.
That surprise HR pop-in happened to me a year ago. Yeah, it sucks.
Tik tok tik tok = the sound of the time you have left to live while stuck watching ADHD inducing short clips.
I used to have that issue where I added a print statement and then my code started working. Then I stopped using eclipse. Now my ide builds the current code every time.
0:59 Usually I appear in HR Meetings.... To fix their stuff :/
In my experience if a code passes test even though I know for sure it shouldn't then something MAJOR is wrong with the code
"Why is it working?" is one of the most cursed questions ever.
that streamdeck thing killed me
Last one, very relatable haha
I was hoping that you will end your speech in the end with “…agen”
I’m kinda happy that you really did it
my wtf moment on embedded: I removed debug mode and it stopped working, after printing on the LCD screen horizontally mirrored. wtf ???
I definitely wanna hear about Rufus... wtf happened to Rufus???
The printstatement and then working is the worst possible outcome
Loved the "Do we have to keep doing this" comment....
Did anybody notice on 5:40 she has a workout going on her watch while she is coding?
If there is one thing I can count on in life it's you forgetting to turn of alerts.
Most painful thing when in debug code works fine but during normal run its going down in flames.
There are small pockets of actual meaningful programming and tech discussion happening on tiktok, but the jokes and zoomer humour is what appeals to the masses.
PG is constant, no improvisation. Alert scenario.
if(alert) then out("I forgot to turn off alerts!")
4:10 i avoid using print statements, unless i know shit's unfixably fucked and need to know what the exact value of some fucked shit is.
You never know what fuckery your code/print implementation might be up to.
5:40
Form over function.
💀
TikTok is the place you go to find a pity party. I am banking on these people, I know they won’t put in more effort than me.
prime, not getting tiktok is a good thing, your brain has not been fried
Goodbye PrimeAgen, We lost our best legend. :sob:
yeah, that's when "volatile" helps. Sometimes compiler wrongly over optimize code, and adding print prevent it from doing it :D
I don't think adding volatile is something you want to do except perhaps a part of a debugging effort. If the optimizer is being too aggressive and optimizing your code so you have incorrect semantics, you almost certainly have a case of undefined/unspecified behavior on your hands and the better solution would be specify the semantics correctly.
I've heard horror stories of printf both fixing and breaking code...
Usually when inserting print statements makes things work, it's a race condition somewhere.
Can also be various forms of undefined or unspecified behavior: memory corruption, indeterminate expression evaluation order, overflow, that sort of thing.
I had that happen to me before at a really small company. For 1 year they said everything was good and everyone liked me. Then I asked for a pay raise review and the review went awful and they said I was terrible. Like, couldn't you tell me that during the year? And then a month later I was laid off because they didn't "have the money." Which I think was true, but it was a bit weird after I got a really bad review.
TBH, I don't mind hearing about a dog named Rufus.
hr is a god of death coming for humans when their time is done
The first one was just straight up depressing.
"TikTok hates him, he used this one simple trick"
0:40 literally happend like this to me with my last job..
In Java, sometimes, things only work when there is a breakpoint. WTF.
I got a mental breakdown over those tiktoks.
"Why does it look so creamy? Why does it look so thick?" 😳
Prime I totally feel u man. I don't get it either. Tiktok is just this enigmatic black whole that absorbs every last one of your brain cells if you dare to scroll for more than 2 minutes. I am 21 y/o, almost all of my friends use it. I really don't understand the purpose of it but still I am weird to not know what the name of this one dancing toilet head thingy is. Sure, Andy.
My ears!!!!!!!
I was using a headphone. With 70% volume and BGM. The cringe came through all this noise.
Normal Tik Tok videos are already cringe, programming Tik Tok videos is the next fricking level.
Print synchronizes thread registers.
once again prime gave us brain rot
I actually liked the tiktoks. I thought I would be too old for it.
Oh no. It is happening.
After watchi´g this video, I will never open a tiktok account.