I can’t unsee this now. It’s literally EVERY TIME

Yeah, it kills me. I got skill issues and fail not to do that, but I feel like he does it on purpose

maybe he never got a proper feedback or he did but is unwilling to grow and change...

No they don't, source: I'm a kitten

Oh no, not a kitten 🙄

gotem

goetm goemt geomt gemot emgot

@@adammurai1955excellent joke but please can you fix the last line the result should be "egmot"

@@almicc damn, I was off by one

exactly my thought lmao. Just tell me what it does and I'll put it into code, please don't tell me buzzwords. My brain has no space for them.

@@vonpitlord1783 Bubble sort is usually the very first sorting algorithm you get taught in CS classes when you learn about sorting

That's the point. After a while you kind of forget what the names mean.

@@flarebear5346 To be fair, bubble sort is really only taught as an intro to sorting and algorithm efficiency analysis and the lesson ends with explaining that we don't use bubble sort in production because it's so inefficient. So you might encounter it a couple times in CS classes and then never again afterwards unless you're teaching programming

Bubble sort is default sorting algorithm you do when you don’t know how to do any sorting algorithms When I was in uni in initial data structures class we had to code our own sorting algo and bubblesort was what I accidentally created

they will always get you

​@@ThePrimeTimeagenbest way to measure the size of that dict

Well, chat wasn't wrong.

It was the swap part numbers[j], numbers[j+1] = numbers[j+1], numbers[j] Very pythonic Also, lol at this dude doing the xor trick

@@loogabarooga2812 show!

Soulless HR speak and CEO "this is why i'm a good person" pandering distilled, bottled and served to perfection.

The corporative obligatory courses with souless music about beeing communicative kkkkkkk

why bring juice into this you anti semite!

ahahahha came for this comment. Thought exactly the same 😂

How was he even allowed to do such a mess in the first place?

Management tends to trust older hires more than new hires. Add in a culture that doesn't value good practices and you get a recipe for disaster.

And the money the company lost because of it ultimately comes out of your salary

​@@fdg-rt2rk there are many companies that do not have quality as a focus during development. They just want the feature done and shipped.

@@fdg-rt2rk They had all the confidence in the world but zero competence along with the director of engineering thinking they were good. They had no PR process or gated check-ins in place. There were many times he would write code, not compile, and push. When I started on the team branch policies were put in place which is how I knew he had been doing that the whole time. Multiple times the code review would be "this code doesn't compile" and he would resolve it without doing anything. I just don't understand why we live in an age where firing somebody is a year(s) long process.

yeah lol, he literally says in his 2nd point that not growing is something worth firing someone off.

@@googleforcedhandleyeah, not sure why Prime didn’t get that. Think he was too hung up regarding the skills part.

He was just giving himself fellatio.

@@googleforcedhandle OP contradicted himself.

You know, growth cannot be infinite. At early steps - yes, you constantly grow. But the knowledge and experience expires. Expectations ate also tend to grow. And the more experience you have and in more areas, the more efforts it takes to just keep it up-to-date. So at some point you can get close to the saturation when a speed of skills expiration almost equals the speed of learning new. In reality such people still continue the developing themselves but the pace of improvement doesn't meet the expectations of others. Especially when someone looks at a novice who progresses at a certain speed in a single area and expects, that a senior with experience in 7 fields will progress at the same speed at each of these 7 fields. Learning never stops. But amount of up-to-date knowledge doesn't grow linearly. At the beginning the growth pace may even increase with years as previous experience helps learning new faster. But on later stages the growth pace slows down and most of the learning efforts can be spent just on keeping at the same level where you was without degrading

Ive nerver had to use a search or sort algorithm in my life in a real world program, someone has already a library for it that you can just import.. same for data structures - the only time I had to use them was in interviews or promotion exams in big companies..

@@and_I_am_Life_the_fixer_of_all i feel like that's kind of missing the point of why you might want to learn these things. learning the implementation of certain data structures and algorithms helps gain an understanding of their characteristics and what they might be good for. a lot of people don't even know of these things in the first place, and don't even think to reach into the standard library for a particular data structure, because they never learned that this particular problem maps really well to that particular data structure.

@@luccaflower751 The interview: Implement quicksort. Implement djikstra/A*. Spin 4-dimensional matrixes atop each other. Answer "use a hash map instead" when asked how you would optimize something - ANYTHING. The job: Writing "FreeJsonLibraryYouGotFromGitHub.Serialize()" once a week, and knowing when something needs a Visitor instead of regular polymorphism.

Bubble sort has some nice properties that can make it faster for small datasets and partially sorted data. Its also generally more cache friendly than other sorting algorithms and better suited to vectorization.

Wrong.

But sometimes it can be _very_ hard to tell when someone "communicates poorly" until a huge mess has been made. Communicating poorly doesn't only mean messing up the repo or being an asshole in meetings. I'm in a small team and had a REALLY good programmer who, when the team grew a little, I promoted to handle 2 junior programmers. After that, he just took in all of their work and burned himself to the ground. If they went "Hey boss, can you help me with this?" he would sigh and just say "I'll have a look at it later", and then he'd do it all himself, instead of gently helping them out in their specific issue. He stopped testing thoroughly, the codebase became worse, and he became irritated. His 2 juniors became code monkeys who would fill in Visitor methods, create business classes, prototype the UI, and little else. Eventually he got extremely burned out and left the company. The 2 juniors and I took over his work, and we had to work many months to straighten out his mess. And guess what? Those 2 juniors were pretty smart guys, they just needed a chance. Turns out this guy was just completely inept at handling people, or delegating. And it wasn't just "you communicate poorly", but more like "you think others are stupid and won't be able to do what you do".

@@JellyMyst lol

Yeah this is a good point. Granted when i get feedback like that I ask for what specifically they dont like or would change. However its also true the person giving the feedback should have provided the specifics from the beginning. This problem can be solved from both sides, so whenever im on either I try to ensure i solve, I dont expect that from other people (even though you rightly could) I try to be twice as good rather than expecting other people to have these things dialed in. Unless its one of your higher engineers giving crappy feedback to a lower engineer, then you gotta tell them to improve, but since in my mind i always place myself at the top (lol) that i always try to solve these things.

WTF, youtube deleted my response here but I'm still getting notifications when people talk.

Eh, good attitude takes you further.

@@scahsaint6249 absolutely agree, attitute is also important

Should have written "Attitude is no substitute for aptitude", more rhetorically effective.

This had to be malicious I refuse to believe it 😭

that's actually crazy

Obviously a plant working for Intel or AMD to boost CPU sales.

@@asdasddas100 Could easily be a child raised by wild immutability advocates and now trying to adapt to civilization.

​@@asdasddas100"never attribute to malice that which is adequately explained by stupidity"

It would bother me less if someone took a long time but their solution was good. Seemingly the people who take forever produce code that doesn't even work

In chess it's said that if a player takes way too much time on a move, that move won't be good.

I hope I will never have to deal with that damn. I know these people exist though.

You said it. Most code in the world sucks, it's OK to not be an amazing coder. To be human is to have skill issues.

Just sort by distance squared

That's not really true. Being shit on from a person of authority will never train you to accept being shit on by a peer. One has the privilege to do it, while the other doesn't. I got shit on all the time by teachers and my parents growing up in the 90's, and all these anti-millennial sentiments of people growing up soft because of upbringing are so myopic. I guarantee you engineers in the 70's and 80's were just as ready to throw down over some colleague coming up and saying their code is trash to their face. I still remember in university, the older professors were the absolute prickliest sons of bitches I ever met, even those who had been in the industry. They had enormous egos and pride. Although my time in the industry has mostly involved people in my generation or younger, my few encounters with the previous generation in the wild only reinforced this perception. The generation before simply loves to make themselves out to be heroes, but they're just human. They aggroed each other constantly and can be huge manbabies. I remember a 55-year-old just hanging up on a call because he felt challenged and didn't like it. Fired 2 months later, good riddance.

@@Blaisem That's interesting. It feels like the very perception of authority figures has shifted, and the very notion of the "privilege to criticize" is often rejected these days. A lot of people 30 and younger dismiss the "I'm more experienced/knowledgeable" argument right out of hand. In 90s-early 00s, trashtalking someone's work felt like the norm. That last decade there's an ever-increasing need to sugarcoat everything, essentially "be nice or I won't listen". It is a shift in responsibilities also: we used to have "it's your responsibility to learn", now it's more "it's your responsibility to teach so that I'd understand". Most of the time, it turns out just fine, but the edge cases are pretty noticeable on both sides.

​@@Lodinn It's possible things have changed in the last decade, although if I recall correctly, people were already saying 10-15 years ago that the new generation was back then was already going soft. I can't tell if it's just a perennial perception every 10 years that people want to announce the new generation is soft, and then that new generation 10 years later turns around says the same thing about the next generation. As for missing a privilege to criticize, I don't have any facts to argue against it. I can only say in my personal sphere it hasn't been the case. Bosses are free to offer negative feedback, and people mostly take it when it happens. I mean, they can leave in a huff, but I can't recall it happening. I guess we could have a discussion on what that negative feedback looks like. As a boss, you are responsible for morale, so there's a proper way to deliver the negative feedback. A good boss in a private developmental meeting say your code writing is leading to bugs in production and needs to improve; they shouldn't call you out in the daily and say "hey, Timmy your code lately has been garbage, fix it." On the other hand, I've seen a boss get pissed over a bug(s) and yell at the team, and the person named Timmy knows it's their fault from their commit, and quietly so does everyone else. Timmy then fairly expects punishment through other means like bonus or missed promotions. But hey, maybe what's deemed proper has changed over time. Finally, I will say this interaction has often been unnecessary. Most people around me who haven't left for personal reasons have left due to layoffs, so for all I know the boss doesn't have to give negative feedback, just select the people he doesn't like when it's time for layoffs. Or shuffle them to another team.

@@Blaisem Shitting on people has nothing to do with giving feedback, it's simply an attempt to establish dominance. And of course, when such power games are played using feedback as a cover then feedback itself becomes perceived as an attack which needs to be defended against. The behaviour you described is the end result.

Not exactly. My brother works in Brazil for a Swiss company but they did lower his income to reflect his costs of living.

​@@CheeseOfMasterswait what the fuck isnt it, like, heavy discrimination and just very greedy stuff?

​@@ohno1052 Honestly, I don't know what else to expect. Why else would a company from Switzerland hire someone from Brazil? If they were gonna pay someone a Swiss paycheck then they would find someone in Switzerland. I'm in Eastern Europe and many EU and USA companies come here to outsource work because of cheap labour. When covid hit and the cost of living increased our companies increased how much dev cost and the companies went to a different East Europe country where IT isn't in a huge boom and programmers cost less. That's how big companies protect the bottom line. And to be fair their paychecks are still better than any local company and they 100% pay up every month.

​@@ohno1052 welcome to outsourcing

Cybersecurity is the better option.

thats a different version of the algo which is probs more optimised but could run into a problem if you made a mistake. In this version you know that the maximum number of swaps is at most the number of items in the array so you can just make the outer loop for let i = 0; i < array.length. If you used while (!swap) {} on the outer loop and the inner for loop you used if (left

@@abz4852 I see alright, comp sci class got me fucked up

You are right, he didn't implement actual bubblesort but a worse version of it.

In this context, "pixel perfect" usually refers more to getting all the alignments and edges right. If you have multiple content boxes that are supposed too align to the same edges, but one of your boxes is a pixel or two wider, that looks sloppy. Using different padding in each box looks sloppy. Randomly changing font sizes / font families looks sloppy. I've had engineers whine about "who cares if it's off by 1 pixel?!?" As if quality work is not something to be strived for. I get that they don't see it when they're just getting started. But if you've been working on the same product with the same theme for months and you continue to be sloppy with your implementation, we're going to have problems. Of course, your code is probably just as sloppy, soooo....

it means they are shitty designers.

That is still bubble sort. It doesn't really matter in this case, and if it does his solution is more efficient in the worst cases. He probably could have added a check though to prevent further iterations if already sorted. The goal is not to work from memory but to be able to implement basic sorting.

In python every for loop is actually a while loop

many things

it means making a screenshot of your UI match exactly what the designer threw together on their powerpoint slide

ic tnx@@Quantris

This comment should be pinned to the top. I'd love to see the staff turnover for this Tyke guy! People who claim others can't take feedback can never take feedback themselves. When given the brutal truth back, you are therefore labelled difficult! This video(not Prime's take on the video) is about a guy on a power rush, and with a narrow set of beliefs. Worst kind of person and manager.

Wtf are you talking about? A sorting algorithm being correct is dependent on the implementation not the end result. You can write a sorting algorithm incorrectly and still have it sort the array.

@@NihongoWakannai Well, you can also try to implement it and have it *not* actually sort it correctly. So you need to ensure you are getting a sorted result! Otherwise it is wrong. Note, it might not be optimal, or you followed the wrong algorithm, but getting it sorted is kind of crucial to a sorting function

@@NihongoWakannai You could also add some tests to ensure it is fast enough. Like if you are testing a quick sort, you can give it increasing input and measure the timing to see if it is behaving as it should. If you wanted to test bubble sort, you would have to add a parameter which would be the number of iterations it is allowed to run for, and then inspect the data to verify it is working as a bubble sort should.

It's cool, but nothing to do with TDD. TDD would start with a test that empty returns empty, then minimal code to make that pass. Then 2 elements sort, then code that can swap 2 elements. Then test with a normal array, then the loops in the code. That's more like TDD. I don't see how it's useful here though

That's fine as long as feedback is accepted both ways. If the code does not suck, and the manager is on a power rush or nitpicking, that leads to a toxic environment.

yes

I mean I heard Netflix pays their Hiring Engineers pretty good lol

Careful. That sort of intelligent reply might get you fired as you cannot accept feedback.

And companies will prefer the charismatic douchebags and fake people that average or less than people who are less good with people but are very technical.

@@AnonYmous-yu6hv I would put a fat asterisk on that. I've been a part of several companies that are biased toward highly technical folks that can't talk their way out of a paper bag, or are actively incredibly rude/arrogant, because they view the only purpose of an engineer being producing code, not working within the broader context of a company.

True, bubblesort has best case O(n) but his algo has O(n^2).

and that's why it's called bubble sort instead of bonkers sort