bro it's funny cause everyone wants to work for FAANG, but it's just the grass is always greener.. you get $$ but you may get stuffed into a corner to work on a project that never makes it to production
Hey man - Your enthusiasm for coding is infectious and is helping me out. I have ADHD also and go through phases of imposter syndrome and the like with my career, despite making progress with my projects. But, yeah, your enthusiasm definitely picks me up to keep on keepin' on as a software engineer. The stress of this career can drag you down sometimes. So, just wanted to say thanks for the laughs and enthusiasm.
As an aspiring software engineer, somehow I relate to. He has changed the way I view it greatly. Not so long ago I was only just interested in, but now, I love it.
1:15 as it happens, I worked with someone some years ago (let's call him Bill) who also wouldn't stop talking about his dog... AAAAAAnd, he had an extra loud mechanical keyboard.
Loving these videos. I’ve worked with developers that just wait for me to figure out new stuff so they can just copy my code .. it’s really annoying. I enjoy learning new methods or practices outside of work or during a project if I feel it will make a difference or increase my knowledge. Other developers can just waste so much time or don’t take the time to learn how it works.
I remember having a 5-minute Stand Up once. Team management wasn't there to comment on anything, so someone said "lightning round?" and everyone just powered out the three questions and then went and sat down.
@@dejangegicMy stand-ups are 15 minutes, but you don't get anything out of them If you want to clarify your task (which you always do in my team, because the descriptions are so vague) or you want to discuss your idea before just jumping into the code, you need to spend a few days asking and then couple of hours on different calls to find out what do you event need to do. One time, I was assigned a bug, the description was literally just "fix this bug" and 100 lines of pasted stacktrace. It took me 2 weeks to find out what is even supposed to happen there and how the microservice works, and in the end it was just moving one line of code outside the if statement - the most frustrating part is, this would've been caught instantly in a code review, but we don't do them because "we don't have time" (but we do for doing 3-5 storypoint tasks for a whole sprint or longer xd) Before you say anything, yes I am getting the fuck out of there, already signed an offer and starting new position in a couple of months, now I just need to endure 2-3 more months before the new position starts
The Peter principle is a concept in management developed by Laurence J. Peter, which observes that people in a hierarchy tend to rise to "a level of respective incompetence": employees are promoted based on their success in previous jobs until they reach a level at which they are no longer competent, as skills in one job do not necessarily translate to another.
The thing is its all because the whole pay structure is messed up. The executives and owners get way too much money for not doing work that is any more difficult than those under them. This leads to shoving everyone towards a management and decision making role even though we know most people are probably not well suited to those positions.
Honestly I think it's also because people are highly promoted based on their ability to manage relationships and network, people promote people they like and not just based on how solid one is in their technical prowess (so similar to politicians moving into positions I guess).
"Peter Principle" is a book by Laurence Peter. The basic idea of the book is that an incompetent person can be forced to make lateral moves in organizations, which makes their overall resume look better, and gets them promotions in the long run. Edit: I guess I should have waited until the end of the video to comment. Edit #2: what I described was not the Peter Principle. It is the Dilbert Principle. Oops, my bad.
I have never read the original book so this description might actually be more correct but this usually isn't how the principle is described. Usually it's described that competent people will get promoted until they reach a job they are no longer competent at. This then leads to a lot of the people at a company being incompetent at their current position.
@@sinom I never read the book either. Just watch the video of somebody talking about it. So it is very possible that I am talking about an unrelated, but similar, phenomenon. Or what I said might be one of the paths that leads to the person making it to the position they're incompetent at.
that article is trash, it's, just trashing personalities at work and not talking about programming at all, if the article mentioned the second one, it could be helpful to people and they can learn if they fall on the bad programmer category, i work with a bad programmers : * they chew more that they can swallow, * always have an opinion about a subject, mostly it's always unrelated to the actual question or topic, they talk without saying nothing * most of their "work" is just copy-pasting your work and tweak it, or even leave it like that, and that breaks the application or cause unexpected bugs that of course you need to fix because they have no idea what they're doing * they ask for "help" when in reality they play victim so you do their job for them * they make the team fall behind due to their incompetence * they don't accept criticisms and they are not willing to accept they are wrong * they don't want to learn the craft, they hold to the bare mininum (if not worse) there you go, 7 real signs you suck as a programmer
I've always used the absolute crap out of whiteboards in my team work. It's a great way to free-form visualize, and collaboratively conceptualize. Even in a well-tuned team individuals often only assume they're on the same page mentally, when in reality, usually days/weeks down the line, they realize they weren't. Actually using whiteboards help a lot with that. "But everyone knows what it means" "I can hear you talking, but I can't hear you meaning" "Meaning isn't a verb" "Exactly" In my experience having a whiteboard standing around unused, doesn't mean whiteboards are a shitty tool, it usually indicates the team doesn't really want to collaborate.
I've used the whiteboard in different companies with different teams to design. Some people may not like it, but I feel it's an effective tool of comunication. I didn't use originally by myself, but because of my boss and acquiered the habit of using it as well. I wouldn't take the article very seriously, it's from medium....
1:45 I'm pretty happy that our stand-ups are not like what prime is describing. I'm a QA guy and they allow me to sit in on their meetings to hear what kind of features and bugs the devs are working on (they actually allowed me to come in to the meetings). Everyone bullshits for like, 40 seconds at the start of the meeting and then it's down to business. I appreciate that. When they ask me what I'm up to, I just tell them I'm working on breaking things, like always. I keep it down to about 10 seconds or less, unless something specific needs to be in their POV. I work with a solid team.
I have one in the office but everyone wears noise cancelling headphones anyways. Guess I could switch it for a "middle ground" gaming keyboard with some snap but quieter. Or maybe get an A/T to USB dongle access rock my Model M.
There are mechanical keyboards that are very silent. Maybe not as satisfying to use (depending on your personal preferences), but still way better than the rubber domes.
I used one in the office before we were all moved to remote, but only when I had my own office. Of course people complained about my typing before that because for some reason I type extremely loudly no matter the type of keyboard...
I bought a mechanical keyboard for work, but switched out the Cherry browns with Epomaker sea salt switches, they're quieter than most membrane keyboards.
07:55 my colleague is basically just copy pasting stack overflow or my code and is soon the proud owner of a masters degree in comp sci. A pleasure to work with that guy
I have similiar guy at my job: copies my Mermaid diagrams, removes half of it. Claims he wrote them himself in the "discovery process". When I ask merithorical questions about parts that he removed, he responds that he didn't discover that yet but he is working really hard to document whole process. Management is so blind that they can't see that he copied already existing documentation so he is getting praised and commended on his work. I hate this guy.
The point about being it in for the money from the article is really shallow, because there's no context of what kind of money we're talking about, and I fully agree with Prime on this (taking his example if Netflix would only pay him 1/10 of his current salary). I've been programming for more than a decade doing personal projects, and working 3 years professionally as an engineer, and while I like programming and what I do, the income is not fair in the slightest and it can demotivate you very quickly as I've been depressed often because of this. To further illustrate what I mean by shallow look from the article's point, taking the example of my income (17k€/year, thanks Portugal), you can absolutely say it's not enough for the skills such person brings, and while I love what I do on the job, since I always loved programming, the point about the income being so low starts to make you dislike it overtime so you don't really enjoy it anymore despite being your "passion".
I don't know if I can get behind the lack of curiosity one. There's been studies on motivation that've shown that interest in a task decreases once it is tied to monetary compensation. You can very much go into the industry with passion and have it entirely snuffed out over time and it's not unreasonable for that to occur; it might actually be the exception if it doesn't happen. It's also not always feasible to change careers as other industries might not pay enough or are locked behind college degrees you don't have
Every time i start watching like this i get worried that im considered a bad programmer by some random metric. When in fact im a bad programmer because i write buggy pieces of shit
I love when my client director asks for suggestions. I give the only suggestion, he says no not sure about that. then he suggests a solution that just rephrases what I said.
For XP, most companies only accept professional experience. In 2001, I was open-sourcing a shell to add tabs to Internet Explorer. Around the same time, Firefox came out. Before that, I was toying with Basic and made the usual suspects: snake, Tetris, and even a screen-by-screen 3D maze (which will be a raycasting engine in VB6 later on). In 2005, I did the most challenging track available (Industrial computing) because I already knew most of the material from my hobby. At that point, I already had more than 5 years of practical experience, including trying j2me. So, I was flying through the curriculum. So much so that I was helping students from later years. Got my first job without even looking. I just had to say yes. Then I got fired in the last batch of 300 people due to the crisis. When I wrote my resume, I listed languages I was comfortable with, and recruiters just binned my resume. So, I took a shitty job, regretted it, and quit. In all interviews, I was rejected. Good on the technical part, but a danger for the company. With my knowledge, I could decide to go at any moment, which was terrible. Also barred from most free training because I didn't sit well during test. Acing them is not the right thing to do. I cried to join a training because they promised that 95% would be hired. Got to join and ''follow" the movement, which mainly was providing support to classmates. I ended up in a company where I managed servers, repaired label printers, and developed. I did a burnout because I was doing a 5 man job. So, I explained it to my boss, who didn't believe me for months, telling him I was drifting away. One day, I just went to his desk and handed him my resignation letter. He tried to say that he understood, that he would change things. I said it was way too late. He hired 3 people to replace me and sunsetted multiple projects I was working on because the new people needed more time to maintain and improve them. In another company, I became critical. I warned my boss that the company would die if I got sick for too long or became unavailable. So, I needed a double. He ignored my request because he didn't want someone sitting on his ass all day. Then I discovered the abuse on colleagues as it became worse and worse. So, I told the boss that if the abuse did continue, I would quit. And the worse part was that I was also working for a company developing a database, and who... needed help understanding their implementation. So, I had to send them test reports and bug fixes (realm, which wasn't a good fit for the project, but the boss didn't want to let that go!). I faked some efforts, we had some discussions, and I quit. A few months later, the company was dead. Ultimately, I am aware that I am "not hirable" because I don't fit well in a team, not due to any skill issues but my mobility (easy to move on) and the technical gap with peers. The "Why don't you do that? It will take only 5 minutes"." your reply can only be ''Because I am doing more important things that would take you even more time." This is condescending...So, it creates dissent.
@@psvkushal7170 I work in a niche. I am doing tree-to-tree transformation driven by trees. Full remote and only four days a week. Still though due to my health, my expertise allows me to have those accommodations.
Its called The Peter principle based on a 1969 best selling book "The Peter Principle; why Things always go wrong" - Authors Dr Laurence J Peter and Raymond Hull. The main thesis of the book is - In a Hierarchy an employee tends to get promoted till he hits his level of incompetence.
"But why?" - this one is such a bummer. And usually, when you explain it - they don't really hear you anyway. This one is a fake out. It sounds like curiosity... but it's really just them letting you know they'd prefer if you rounded down and stopped thinking.
@@liquidmagma0 blue light doesn't affect your eyes in any special way. there's a slight psychological effect for the sleep-wake cycle, but even that has been very challenging to reproduce experimentally. the blue-light blocking industry is basically the same as the healing stones industry
6:22 I am in one of those and it's a nightmare because even if you have documentation you have such a broad array of types of documentations and depths of documentation that anyone else picking it up is a complete nightmare.
7:42 Well, I copy a lot of code from SO, but I mostly only use it when I understand it and I even often adapt it to be compatible with my own code. So I _do_ copy stuff, but I _don't_ do it unresponsibly.
I copy from SO all the fuckin time because there's always some trivial nonsense that I don't care to figure out from scratch, but I will learn how and why it works before I just shove it in and hope for the best.
4:55 - not true. In my previous company, there was a huge monorepo project in Angular 1. Since it was quite old and difficult to manage, they decided to port it to react. It seemed like a gargantuan task, but somehow they figured out a nice way to wire both frameworks together, so they could incrementally refactor angular components into react. The strategy was to write new components in react only, and port old components every time they were touched for any reason. Took some time, but the rewrite was successful
"The informed captain approach." This applies outside of coding as well. It is a dream when you have that boss that captains your team confidently and correctly.
The whiteboard thing is definitely a thing i was guilty of, not necessarily having it in the background but feeling having one made me a more serious engineer. In my experience writing things down is useful, but a whiteboard is not ergonomic at all a notebook is way more practical and less pretentious
Unless you were pretentious, then if your whiteboard makes you feel like a more serious engineer, then that just seems like it helps get you fired up about your work.
Don't see what's wrong with a whiteboard. More real estate for drawing out things and easily erasable and correctable.I didn't even know it was an ego thing.
@@drstalone i get that but the way i had it setup wasn’t ergonomic or practical had it on a wall i couldnt see from my desk comfortably. Decided to move over to old fashioned notebooks and a tablet
The guy who wrote the article only needs to look in a mirror if he wants to find a bad programmer. Feeling the need to shit on other people is usually a red flag in terms of competence.
From a code perspective I feel like readability is the best sign of bad or good programmer. A good programmer: 1. Indents in a consistent manner. 2. Uses if statements effectively without excessive nesting or abusing and/or operators. 3. Names variables and functions to something informative. 4. Groups similar lines in a function together to form sub-tasks. 5. Adds one and only one new line when a different task is is done in the function. 6. And most importantly knows when to write comments when certain code is required to be janky.
I love extra whitespace, not between every line, but between groups of lines where it makes sense to introduce some space. Or after an if block for example. Also, while I'm on the subject of if, people who dont use braces suck
1. I have a mechanical keyboard because I had RSI so bad I lost hand movement for months. I was in splints. I use one as it is a joy to type, it means I can still continue to type. Perhaps it is a form of inverse snobbery by the author against someone using a decent tool in their job. I like large monitors, too. Dual. One landscape one portrait (for code). Bite me. 2. So using Copilot is co-pi-pasta, right?
I specifically built my office mech keyboard to be *extra* quiet. And it is, it's more quiet than the standard-issue garbage logitech rubber-dome keyboards, so I am pleased with myself. But I'm also not a programmer, lul
I used to bring my clicky ALPS kb to the office and I'm sure it annoyed everyone. But, on the other hand, my coworker across the cube wall talking about the latest streamer he was watching for hours on end bothered me, so to each their own.
The peter principle is a reference to a book y the same name. It can be summarized as thus: If everyone is promoted based on their abilities in their current role (and not future role), then every role will eventually be filled with people not good enough to get promoted (but not bad enough to get fired). Put another way: everyone rises to their level of incompetence. With the corollary, that everyone is therefore incompetent if they aren't rising.
I do have a whiteboard, but it never shows in my background during stand-up. I use my whiteboard for algorithm, as standing and talking to myself while addressing the problem on a whiteboard is a lot more efficient than just sitting and writing on a piece of paper.
The worst part is i know the exact type of person that writes this....and theyre usually not the most creative or the best at problem solving....usually competent enough to just get by
Decisions are made by having the most experience person for that task make the call, indeed. Just let everybody put forth their ideas but in the end the most experience will pick a solution.
@@notquitehim Hahaha I think you will need to perform a heinous act of terrorism and leave that manifesto to be found :p Even then sane people don't care about Agile manifestos :D NICE ONE !
@@phillipanselmo8540 absolutely not true! First of there’s a thing for older technologies - they are stable, predictable and reliable, the pursuit of the new shiny thing makes IT so unreliable compared to say my field of education electronic engineering or civil engineering, healthcare systems (that I worked in for almost 6 years) and aerospace. They are more conservative in changing technologies. Those technologies have to have been tested to hell and back and proven to actually be better than what there is currently is before adoption is even a thing. And their success rate despite being infinitely more difficult than web projects or even most games (no lives depend on them) their success rate of IT projects is so much higher than IT projects. And prove and point take Ginger Bill a technical director, who knows fluid simulations better than most people and created a new language “Odin” to lift some of the burdens that the only other languages mature and fast enough C/C++ have. The most experience person knows how to weigh the pros and cons. They’ve done many projects and know what hidden challenges lay ahead. Inexperienced people know very little about anything because… well… inexperienced. And a senior always is open to good ideas and knows how to incorporate them in a proven workflow. So you listen to those who successfully did many projects because they successful managed to do them because they are doing things right and learning as they go along to even improve upon that and then onboard new tech that they know actually solves a problem and not just because it’s “easier” or “new and shiny”.
The worst programmers are the ones who make changes in common code, turn it into something that looks like it came out of a module bundler, and say "ohh I'll refactor it bro" and they never do.
I noticed high correlation between mechanical keyboard and being arrogant actually in my 20-years career as a software dev/eng/programmer/keyboard clicker.
I work with a senior developer which I by now multiple times have caught just copy pasting stuff from stack overflow... It is always answers which has at most 5 upvotes because they answer very specific questions... The code always looks horrible.
I don't think the person who wrote that article has actually worked in a professional environment... And if they have, I'm guessing as a manager, not dev.
5:09 LOL bro just read that there are only shades of gray no black or white, and went "EHHH IDK ABOUT THAT ONE" with his head WHICH IS A SHADE OF GRAY RESPONSE LOL
I’m a nursing home nurse and there was a time during Covid and a bit after they were trying to make nursing home nurses go to stand up meetings with management.. bro I have 35 patients who all need morning meds and insulin ya Mildred is still 96 and confused what do you want from me ugh 🤦♂️
A large part of my programming has been in areas if I screw up people die. I get how most software isn't that way I've worked across the field on about everything. But you learn real quick when people's lives are involved there is a right and a wrong way. There is no grey area. You tend to find that holds true in a few other areas large some of money and national security. Its the difference in I get fired because I messed up vs you can go to jail because you caused a death or they find your action culpable or negligent... Working at Netflix you won't go to jail for a screw up in most cases. Screw up on the software for a nuclear power plant and cause a melt down you very well can. You also have chemical industries, dams, various labs, military equipment, industrial systems many of which you can not only get one but multiple or many people killed. So why I here someone say there isn't just one way. I think the person is inexperienced and a bit of an idiot. Because clearly it does depend on what you are working on if there is or isn't just one way. Generally the practices I found working over in that area of development transfer well. They generally provide increased stability and performance. So I'm pretty much of the mind there is actually there is always a best way and then there are many wrong ways.
Im the boss and teddy gets fired immediately if he talks about his dog in any meeting And bill also gets fired immediately if he brings the dog to the office because "there's nobody to take care of him"
One sign of a bad programmer is me after having to work back to back 80 hour weeks. Six months later I am still fixing the bugs and scratching my head trying to figure what planet I was on when I decided to write that.
For me, stand ups go way past 5 minutes because our Software Architect goes on a 30 minute monologue about the tape drive system we are buying every damn day.
I don't get the "I'm a software engineer, not a programmer" one. That has nothing to do with arrogance. It's a better descriptor of your work. Programming/coding is somewhere between 0-30% of my actual worktime every day. I'd love for it to be 80%, but it's not. It's like calling a chef a "food cutter". At my workplace, nobody uses the word "programmers" or "coders" or even "software engineers". We use "developers". How is this now a contentious issue?
"Shades of gray" doesn't mean "no right or wrong," it means the black and white is very granular and requires closer inspection. It's nuanced. Gray is literally black pigment mixed with white pigment (or some white photons but not filled with white photons. There aren't any "black" photons.)
"I am not sure how you can be so arrogant with 3 years of experience." I'll tell you why, because it takes me about the same time to write a program as you doing the work manually. The difference is once I write a program it never has to be done manually again, it is functional forever (with slight tweaks as needed), even if I leave the company my work is *still* doing work, and clearly you can't do it. This was totally not written by a dev.
I don't know that people think they're cool for having a whiteboard. The fact that he disses the whiteboard person for having a bulleted list on it makes me think that the author actually thinks you need to be at least a certain level of cool to deserve a whiteboard. I'm guessing here but I think the author thinks whiteboards do make you cool and because of that it would be pretentious to show it off by having it be in the background. So he has one but it's not in his background. Same with the judgement about the mechanical keyboard. Some people just like having nice things. When I was in school, I carried an HHKB with me at all times and used it in the computer labs. I didn't do it to be cool, I did it because I like my keyboard and I trusted the people around me to not be like the author. I can imagine the author seeing me and thinking "Look at this guy with his keyboard, he's only a 2nd year student and he thinks he's the shit".
Yeah this is the kind of article that I'd expect from the general section of medium where it's usually coming from the ultra left rant lol. A lot of ad hominem and projecting, without any regards of reality. Haha.
@@edward8064 I mean I’ve read my fair share of medium articles, as well as this specific author’s, and most of this person’s stuff is this unhinged. Dramatically more so than other writers on that site. So idk what politics has to do with it. Only ad hominem (and projection?) I’m seeing right now though is your comment, bud.
@@Zer-ei4co There were times when my Medium's timeline is filled with a lot of SJW's article and that's why it's been a long time I didn't check the site. But I just checked it, and it looks much better than it used to. So yeah, probably I'm wrong and projecting, or probably we simply have different experience about it..
@@edward8064 It seems like a matter of experience. There is nothing wrong with making assumptions and avoiding a website based on that. Even if it is not entirely correct. @Zer-ei4co's accusation of projection is unbased.
I use a mechanical keyboard and I don't even believe there's such as thing as a "software engineer" or that it would be a good idea to have them. 40 years as a programmer.
As of making this comment, I haven't watched the whole video. But for the first point, "I'm a Software Engineer, not a Programmer" - I have NEVER heard anyone say anything like this. I personally refer to myself as a Software Engineer, because I like how that sounds over Programmer. Not sure why, it's just a me thing. But I have never thought of those two meaning different things. Furthermore, I would not "correct" someone if they called me a Programmer. Is there a stigma to using the term "Software Engineer"? Does it sound pretentious to others? I'm genuinely curious now 😮
About the rewriting thing, I think arrogant newcomers are indeed inclined to rewriting. Because it is always hard to learn a mature project: even if it is near perfectly designed and well maintained-it is a complex thing, it contains a lot of know-how that the company gained over time. It is a steep learning curve. On the other hand, rewriting always seems easy-you have a clean sheet of paper in front of you. There’s nothing to read and learn. The learning curve is gentle and flat. It is just a lot longer, and it leads you through the same mistakes that the mature project has already learnt. But it is an easy entry point.
The author of this article seems like someone who has their head up the assess of his previous teachers (at school) and his current managers / employer. People like him are the reason why I can do the same thing as an entire company.
I have a whiteboard right behind me in my office.. It's not my fault :) I don't even use it except for memes. Something like "I'm drunk" in russian, but it looks like a serious note and I hope that no one can read it
![BLACK BAG - Official Trailer [HD] - Only in Theaters March 14](http://i.ytimg.com/vi/Du0Xp8WX_7I/mqdefault.jpg)
I dont watch twitch, i watch twitch clips on youtubes
You watch twich. I watch twitch clips on youtube. We are not the same. :D
@@berkano_plays NGL, Prime is beginning to stir the Twitch FOMO
@@richardwelsh7901 frfr
Me too. I'm subbed to him there as well
Prime is peak twitch
8:36 aged well
"Im not saying Im going to quit netflix within the next 4 years"
*quits 8 months later*
Lol this aged like sour milk 😆
That's because this guy is a total ass hat. Don't listen to him.
Came down here to comment this exact thing lmao.
Came here to make same comment
bro it's funny cause everyone wants to work for FAANG, but it's just the grass is always greener.. you get $$ but you may get stuffed into a corner to work on a project that never makes it to production
The only thing I got from that is that bad programmers can't write good articles about bad programmers
When you have the snark of a "when I worked at NASA" programmer but none of the worth.
7 reasons why the author is the least liked person on his team while thinking the opposite.
🤣!
Hey man - Your enthusiasm for coding is infectious and is helping me out. I have ADHD also and go through phases of imposter syndrome and the like with my career, despite making progress with my projects. But, yeah, your enthusiasm definitely picks me up to keep on keepin' on as a software engineer. The stress of this career can drag you down sometimes. So, just wanted to say thanks for the laughs and enthusiasm.
As an aspiring software engineer, somehow I relate to.
He has changed the way I view it greatly. Not so long ago I was only just interested in, but now, I love it.
Don't worry, every dev has ADHD 🔥😵💫
are you even that good to have impostor syndrome?
@@DajuSar What type of comment is that?
im sure it's just a joke @@syno6412
1:15 as it happens, I worked with someone some years ago (let's call him Bill) who also wouldn't stop talking about his dog... AAAAAAnd, he had an extra loud mechanical keyboard.
hahaha
Lol did you write the article 👀
@ThePrimeTimeagen it's one of those shits that make you question whether you like things going in as much as you like the loaves going out!
Loving these videos.
I’ve worked with developers that just wait for me to figure out new stuff so they can just copy my code .. it’s really annoying. I enjoy learning new methods or practices outside of work or during a project if I feel it will make a difference or increase my knowledge. Other developers can just waste so much time or don’t take the time to learn how it works.
0:58 in my defence, everybody loves my mechanical keyboard in the office.
if its not the loudest blues there are, you are doing it wrong
@@CYXXYC I'm so sorry, they thock because I lubed them with care.
I'm a fool.
@@EnterpriseKnightwhat switches did you use for that thock action?
@@tongpoo8985 Gateron Milky Yellow Pro but I'm not sure which generation.
@@EnterpriseKnight thanks bro
I would have closed the article immediately upon reading about 5 minutes stand-up meetings. BRUH.
5 minutes is a dream
I remember having a 5-minute Stand Up once. Team management wasn't there to comment on anything, so someone said "lightning round?" and everyone just powered out the three questions and then went and sat down.
@@dejangegicMy stand-ups are 15 minutes, but you don't get anything out of them
If you want to clarify your task (which you always do in my team, because the descriptions are so vague) or you want to discuss your idea before just jumping into the code, you need to spend a few days asking and then couple of hours on different calls to find out what do you event need to do.
One time, I was assigned a bug, the description was literally just "fix this bug" and 100 lines of pasted stacktrace. It took me 2 weeks to find out what is even supposed to happen there and how the microservice works, and in the end it was just moving one line of code outside the if statement - the most frustrating part is, this would've been caught instantly in a code review, but we don't do them because "we don't have time" (but we do for doing 3-5 storypoint tasks for a whole sprint or longer xd)
Before you say anything, yes I am getting the fuck out of there, already signed an offer and starting new position in a couple of months, now I just need to endure 2-3 more months before the new position starts
This dude has only weird takes and seems to be a jerk. All of his medium and also his name are just one big res flag
@@dantenotavailable the only time we have sub-5 minute standup is when our scrum master isn't there to shit the place up
The Peter principle is a concept in management developed by Laurence J. Peter, which observes that people in a hierarchy tend to rise to "a level of respective incompetence": employees are promoted based on their success in previous jobs until they reach a level at which they are no longer competent, as skills in one job do not necessarily translate to another.
The thing is its all because the whole pay structure is messed up. The executives and owners get way too much money for not doing work that is any more difficult than those under them.
This leads to shoving everyone towards a management and decision making role even though we know most people are probably not well suited to those positions.
I was trying to relate it to Office Space.
thats very interesting but i will still called the Peter Griffin principle just becouse its funny
@@anon_y_mousse clasic family guy moment
Honestly I think it's also because people are highly promoted based on their ability to manage relationships and network, people promote people they like and not just based on how solid one is in their technical prowess (so similar to politicians moving into positions I guess).
If standup actually only 5 minutes (for everyone not for each) then I would be the most diligent people attending standup.
"Peter Principle" is a book by Laurence Peter. The basic idea of the book is that an incompetent person can be forced to make lateral moves in organizations, which makes their overall resume look better, and gets them promotions in the long run.
Edit: I guess I should have waited until the end of the video to comment.
Edit #2: what I described was not the Peter Principle. It is the Dilbert Principle. Oops, my bad.
great book I must say. highly recommend
I have never read the original book so this description might actually be more correct but this usually isn't how the principle is described. Usually it's described that competent people will get promoted until they reach a job they are no longer competent at.
This then leads to a lot of the people at a company being incompetent at their current position.
but hey, you actually explained what it was about
Bro really named the principle after himself 💀
@@sinom I never read the book either. Just watch the video of somebody talking about it. So it is very possible that I am talking about an unrelated, but similar, phenomenon. Or what I said might be one of the paths that leads to the person making it to the position they're incompetent at.
that article is trash, it's, just trashing personalities at work and not talking about programming at all, if the article mentioned the second one, it could be helpful to people and they can learn if they fall on the bad programmer category, i work with a bad programmers :
* they chew more that they can swallow,
* always have an opinion about a subject, mostly it's always unrelated to the actual question or topic, they talk without saying nothing
* most of their "work" is just copy-pasting your work and tweak it, or even leave it like that, and that breaks the application or cause unexpected bugs that of course you need to fix because they have no idea what they're doing
* they ask for "help" when in reality they play victim so you do their job for them
* they make the team fall behind due to their incompetence
* they don't accept criticisms and they are not willing to accept they are wrong
* they don't want to learn the craft, they hold to the bare mininum (if not worse)
there you go, 7 real signs you suck as a programmer
I've always used the absolute crap out of whiteboards in my team work. It's a great way to free-form visualize, and collaboratively conceptualize. Even in a well-tuned team individuals often only assume they're on the same page mentally, when in reality, usually days/weeks down the line, they realize they weren't. Actually using whiteboards help a lot with that.
"But everyone knows what it means"
"I can hear you talking, but I can't hear you meaning"
"Meaning isn't a verb"
"Exactly"
In my experience having a whiteboard standing around unused, doesn't mean whiteboards are a shitty tool, it usually indicates the team doesn't really want to collaborate.
But "meaning" is a totally valid present participle of the verb "to mean".
I've used the whiteboard in different companies with different teams to design. Some people may not like it, but I feel it's an effective tool of comunication. I didn't use originally by myself, but because of my boss and acquiered the habit of using it as well.
I wouldn't take the article very seriously, it's from medium....
Yeah, Im the type of person that writes when I think. And have a writeboard its superusefull and dosent wast paper.
Talking isn't a verb either. It's a gerund which is a type of noun.
@@Blue_Skies_Sunflower_FieldsI don't think it's a gerund in that sentence bro
1:45 I'm pretty happy that our stand-ups are not like what prime is describing.
I'm a QA guy and they allow me to sit in on their meetings to hear what kind of features and bugs the devs are working on (they actually allowed me to come in to the meetings). Everyone bullshits for like, 40 seconds at the start of the meeting and then it's down to business. I appreciate that. When they ask me what I'm up to, I just tell them I'm working on breaking things, like always. I keep it down to about 10 seconds or less, unless something specific needs to be in their POV. I work with a solid team.
I have a mechanical keyboard at home, not at the office. I don't want my co-workers to hate me _that_ much.
I have one in the office but everyone wears noise cancelling headphones anyways. Guess I could switch it for a "middle ground" gaming keyboard with some snap but quieter. Or maybe get an A/T to USB dongle access rock my Model M.
There are mechanical keyboards that are very silent. Maybe not as satisfying to use (depending on your personal preferences), but still way better than the rubber domes.
I used one in the office before we were all moved to remote, but only when I had my own office. Of course people complained about my typing before that because for some reason I type extremely loudly no matter the type of keyboard...
I bought a mechanical keyboard for work, but switched out the Cherry browns with Epomaker sea salt switches, they're quieter than most membrane keyboards.
@@shockthetoast was your loud typing the reason they put you in your own office?
ThePrimeAgen has reignited my passion for programming. Professional for the last 5 years, but my Burnout has turned into a motivation to grow!
Spoiler alert he quits Netflix within the next 9 months
07:55 my colleague is basically just copy pasting stack overflow or my code and is soon the proud owner of a masters degree in comp sci. A pleasure to work with that guy
I have similiar guy at my job: copies my Mermaid diagrams, removes half of it. Claims he wrote them himself in the "discovery process". When I ask merithorical questions about parts that he removed, he responds that he didn't discover that yet but he is working really hard to document whole process. Management is so blind that they can't see that he copied already existing documentation so he is getting praised and commended on his work. I hate this guy.
The point about being it in for the money from the article is really shallow, because there's no context of what kind of money we're talking about, and I fully agree with Prime on this (taking his example if Netflix would only pay him 1/10 of his current salary). I've been programming for more than a decade doing personal projects, and working 3 years professionally as an engineer, and while I like programming and what I do, the income is not fair in the slightest and it can demotivate you very quickly as I've been depressed often because of this.
To further illustrate what I mean by shallow look from the article's point, taking the example of my income (17k€/year, thanks Portugal), you can absolutely say it's not enough for the skills such person brings, and while I love what I do on the job, since I always loved programming, the point about the income being so low starts to make you dislike it overtime so you don't really enjoy it anymore despite being your "passion".
"Boss, if you're listening, I'm not trying to say I'm going to quit Netflix within the next 4 years". 9 months later resigned from Netflix
I don't know if I can get behind the lack of curiosity one. There's been studies on motivation that've shown that interest in a task decreases once it is tied to monetary compensation. You can very much go into the industry with passion and have it entirely snuffed out over time and it's not unreasonable for that to occur; it might actually be the exception if it doesn't happen. It's also not always feasible to change careers as other industries might not pay enough or are locked behind college degrees you don't have
Every time i start watching like this i get worried that im considered a bad programmer by some random metric.
When in fact im a bad programmer because i write buggy pieces of shit
Nah, writing buggy code is not bad. Not fixing buggy code is bad
@@darekmistrz4364 Yup, there's two types of people. Those that write buggy code, and those who don't write code.
@@shockthetoast Couldnt have said this better.
It’s not you it’s the process. They tell me they don’t have time for me to write tests so I tell them to expect buggy code
I love when my client director asks for suggestions. I give the only suggestion, he says no not sure about that. then he suggests a solution that just rephrases what I said.
At least he had the courtesy of rephrasing it, I’ve had people repeat my ideas verbatim and convincing themselves it was their idea
The irony in this article is deep.
yeah, i'm thinking the same
For XP, most companies only accept professional experience. In 2001, I was open-sourcing a shell to add tabs to Internet Explorer. Around the same time, Firefox came out.
Before that, I was toying with Basic and made the usual suspects: snake, Tetris, and even a screen-by-screen 3D maze (which will be a raycasting engine in VB6 later on).
In 2005, I did the most challenging track available (Industrial computing) because I already knew most of the material from my hobby. At that point, I already had more than 5 years of practical experience, including trying j2me.
So, I was flying through the curriculum. So much so that I was helping students from later years.
Got my first job without even looking. I just had to say yes.
Then I got fired in the last batch of 300 people due to the crisis.
When I wrote my resume, I listed languages I was comfortable with, and recruiters just binned my resume. So, I took a shitty job, regretted it, and quit.
In all interviews, I was rejected. Good on the technical part, but a danger for the company. With my knowledge, I could decide to go at any moment, which was terrible.
Also barred from most free training because I didn't sit well during test. Acing them is not the right thing to do.
I cried to join a training because they promised that 95% would be hired. Got to join and ''follow" the movement, which mainly was providing support to classmates.
I ended up in a company where I managed servers, repaired label printers, and developed.
I did a burnout because I was doing a 5 man job. So, I explained it to my boss, who didn't believe me for months, telling him I was drifting away.
One day, I just went to his desk and handed him my resignation letter. He tried to say that he understood, that he would change things. I said it was way too late.
He hired 3 people to replace me and sunsetted multiple projects I was working on because the new people needed more time to maintain and improve them.
In another company, I became critical. I warned my boss that the company would die if I got sick for too long or became unavailable. So, I needed a double.
He ignored my request because he didn't want someone sitting on his ass all day.
Then I discovered the abuse on colleagues as it became worse and worse. So, I told the boss that if the abuse did continue, I would quit.
And the worse part was that I was also working for a company developing a database, and who... needed help understanding their implementation. So, I had to send them test reports and bug fixes (realm, which wasn't a good fit for the project, but the boss didn't want to let that go!).
I faked some efforts, we had some discussions, and I quit. A few months later, the company was dead.
Ultimately, I am aware that I am "not hirable" because I don't fit well in a team, not due to any skill issues but my mobility (easy to move on) and the technical gap with peers. The "Why don't you do that? It will take only 5 minutes"." your reply can only be ''Because I am doing more important things that would take you even more time." This is condescending...So, it creates dissent.
how are you doing now?
@@psvkushal7170 I work in a niche. I am doing tree-to-tree transformation driven by trees. Full remote and only four days a week.
Still though due to my health, my expertise allows me to have those accommodations.
Actual ppl working :
Ok let’s go, another day
Its called The Peter principle based on a 1969 best selling book "The Peter Principle; why Things always go wrong" - Authors Dr Laurence J Peter and Raymond Hull. The main thesis of the book is - In a Hierarchy an employee tends to get promoted till he hits his level of incompetence.
"But why?" - this one is such a bummer. And usually, when you explain it - they don't really hear you anyway. This one is a fake out. It sounds like curiosity... but it's really just them letting you know they'd prefer if you rounded down and stopped thinking.
As someone who wears blue light glasses because I’m convinced it helps with eye strain, I…feel attacked.
Did you know that most monitors allow you to change the color channels independently in their OSD? You can just turn the blue light down at the source
also I remember hearing studies showing no benefit to blue light glasses / reducing blue light.
@@liquidmagma0 blue light doesn't affect your eyes in any special way. there's a slight psychological effect for the sleep-wake cycle, but even that has been very challenging to reproduce experimentally. the blue-light blocking industry is basically the same as the healing stones industry
Did you type this comment on your mechanical keyboard, in the office?
I use it too, works pretty good
6:22 I am in one of those and it's a nightmare because even if you have documentation you have such a broad array of types of documentations and depths of documentation that anyone else picking it up is a complete nightmare.
7:42 Well, I copy a lot of code from SO, but I mostly only use it when I understand it and I even often adapt it to be compatible with my own code. So I _do_ copy stuff, but I _don't_ do it unresponsibly.
I copy from SO all the fuckin time because there's always some trivial nonsense that I don't care to figure out from scratch, but I will learn how and why it works before I just shove it in and hope for the best.
4:55 - not true. In my previous company, there was a huge monorepo project in Angular 1. Since it was quite old and difficult to manage, they decided to port it to react. It seemed like a gargantuan task, but somehow they figured out a nice way to wire both frameworks together, so they could incrementally refactor angular components into react. The strategy was to write new components in react only, and port old components every time they were touched for any reason. Took some time, but the rewrite was successful
"The informed captain approach." This applies outside of coding as well. It is a dream when you have that boss that captains your team confidently and correctly.
The whiteboard thing is definitely a thing i was guilty of, not necessarily having it in the background but feeling having one made me a more serious engineer. In my experience writing things down is useful, but a whiteboard is not ergonomic at all a notebook is way more practical and less pretentious
Unless you were pretentious, then if your whiteboard makes you feel like a more serious engineer, then that just seems like it helps get you fired up about your work.
Don't see what's wrong with a whiteboard. More real estate for drawing out things and easily erasable and correctable.I didn't even know it was an ego thing.
@@drstalone i get that but the way i had it setup wasn’t ergonomic or practical had it on a wall i couldnt see from my desk comfortably. Decided to move over to old fashioned notebooks and a tablet
yeah that point in the article was stupid and just sounded like the dude was rubbed the wrong way by a whiteboard bro 💀
I mean just the act of standing while writing would help me think, but I don't own a whiteboard. I could see the validity of it though
Cries into my mechanical keyboard at work.
One of the most arrogant and empty articles i have ever seen
chad jipidee would be very upset !
For real - the author seems to have some sort of inferiority complex.
@@jasondoe2596 true
Peter Principle was first popularised by Laurence J. Peter in 1969, in a book titled "The Peter Principle"
The guy who wrote the article only needs to look in a mirror if he wants to find a bad programmer. Feeling the need to shit on other people is usually a red flag in terms of competence.
tom's a genius?!
yes, Tom is a freaking genius! Jay-diesel
Just found your channel and fucking love the content!
Those who can't, teach. Those who can't even teach write listicles :))
From a code perspective I feel like readability is the best sign of bad or good programmer.
A good programmer:
1. Indents in a consistent manner.
2. Uses if statements effectively without excessive nesting or abusing and/or operators.
3. Names variables and functions to something informative.
4. Groups similar lines in a function together to form sub-tasks.
5. Adds one and only one new line when a different task is is done in the function.
6. And most importantly knows when to write comments when certain code is required to be janky.
These are trivial
I love extra whitespace, not between every line, but between groups of lines where it makes sense to introduce some space. Or after an if block for example. Also, while I'm on the subject of if, people who dont use braces suck
1. I have a mechanical keyboard because I had RSI so bad I lost hand movement for months. I was in splints. I use one as it is a joy to type, it means I can still continue to type. Perhaps it is a form of inverse snobbery by the author against someone using a decent tool in their job. I like large monitors, too. Dual. One landscape one portrait (for code). Bite me.
2. So using Copilot is co-pi-pasta, right?
I specifically built my office mech keyboard to be *extra* quiet. And it is, it's more quiet than the standard-issue garbage logitech rubber-dome keyboards, so I am pleased with myself. But I'm also not a programmer, lul
That took a turn, also why do you watch programming content if your not a developer (not a dig just genuinely curious)
Still a twat
@@justgame5508 I'm a Sysadmin, so distantly related, and in my free time I contribute some C++ to open source projects
I used to bring my clicky ALPS kb to the office and I'm sure it annoyed everyone. But, on the other hand, my coworker across the cube wall talking about the latest streamer he was watching for hours on end bothered me, so to each their own.
The peter principle is a reference to a book y the same name. It can be summarized as thus:
If everyone is promoted based on their abilities in their current role (and not future role), then every role will eventually be filled with people not good enough to get promoted (but not bad enough to get fired).
Put another way: everyone rises to their level of incompetence. With the corollary, that everyone is therefore incompetent if they aren't rising.
I do have a whiteboard, but it never shows in my background during stand-up. I use my whiteboard for algorithm, as standing and talking to myself while addressing the problem on a whiteboard is a lot more efficient than just sitting and writing on a piece of paper.
The worst part is i know the exact type of person that writes this....and theyre usually not the most creative or the best at problem solving....usually competent enough to just get by
1 sign of a bad programmer, write an ad hominem article on 7 signs of a bad programmer.
What a terribly poor article.
Can I come work with you at netflix ?! So that I don't have attend another standup because they are draining the life out of me.
Love me a quality outro 😂
Article was obviously written to vent about one very specific person, lol. Author ain't fooling anybody.
Decisions are made by having the most experience person for that task make the call, indeed. Just let everybody put forth their ideas but in the end the most experience will pick a solution.
But muh agile manifesto
@@notquitehim Hahaha I think you will need to perform a heinous act of terrorism and leave that manifesto to be found :p Even then sane people don't care about Agile manifestos :D NICE ONE !
that's a bad idea, the most experienced person is biased towards using older technologies
@@phillipanselmo8540 absolutely not true! First of there’s a thing for older technologies - they are stable, predictable and reliable, the pursuit of the new shiny thing makes IT so unreliable compared to say my field of education electronic engineering or civil engineering, healthcare systems (that I worked in for almost 6 years) and aerospace.
They are more conservative in changing technologies. Those technologies have to have been tested to hell and back and proven to actually be better than what there is currently is before adoption is even a thing. And their success rate despite being infinitely more difficult than web projects or even most games (no lives depend on them) their success rate of IT projects is so much higher than IT projects.
And prove and point take Ginger Bill a technical director, who knows fluid simulations better than most people and created a new language “Odin” to lift some of the burdens that the only other languages mature and fast enough C/C++ have.
The most experience person knows how to weigh the pros and cons. They’ve done many projects and know what hidden challenges lay ahead.
Inexperienced people know very little about anything because… well… inexperienced.
And a senior always is open to good ideas and knows how to incorporate them in a proven workflow.
So you listen to those who successfully did many projects because they successful managed to do them because they are doing things right and learning as they go along to even improve upon that and then onboard new tech that they know actually solves a problem and not just because it’s “easier” or “new and shiny”.
The "my way or the highway" one was hilarious. 😂
The worst programmers are the ones who make changes in common code, turn it into something that looks like it came out of a module bundler, and say "ohh I'll refactor it bro" and they never do.
C level management people after watching an ABAP video be like:
I noticed high correlation between mechanical keyboard and being arrogant actually in my 20-years career as a software dev/eng/programmer/keyboard clicker.
8:31 aged really really well
I work with a senior developer which I by now multiple times have caught just copy pasting stuff from stack overflow...
It is always answers which has at most 5 upvotes because they answer very specific questions... The code always looks horrible.
I don't think the person who wrote that article has actually worked in a professional environment... And if they have, I'm guessing as a manager, not dev.
5:09 LOL bro just read that there are only shades of gray no black or white, and went "EHHH IDK ABOUT THAT ONE" with his head WHICH IS A SHADE OF GRAY RESPONSE LOL
I was casually listening to this vid and 1st "sign" of a bad programmer caught me😂
Well, that not-quitting-in-the-next-four-years meme didn't age well.
I like how I have yet to find a recent clip
I have a mechanical keyboard, the same since 1998. It's pretty good.
I havent had the chnace to copy and paste something from stack overflow yet. Only been working for a month though :o
Peter Griffith always come to mind when somebody says Peter Principle
Is just me, or the article was written by a project manager? to much hate to devs... lol
This article is seethe and cope
yep, its fun though :)
I’m a nursing home nurse and there was a time during Covid and a bit after they were trying to make nursing home nurses go to stand up meetings with management.. bro I have 35 patients who all need morning meds and insulin ya Mildred is still 96 and confused what do you want from me ugh 🤦♂️
the end of this video is just perfect
A large part of my programming has been in areas if I screw up people die. I get how most software isn't that way I've worked across the field on about everything. But you learn real quick when people's lives are involved there is a right and a wrong way. There is no grey area. You tend to find that holds true in a few other areas large some of money and national security. Its the difference in I get fired because I messed up vs you can go to jail because you caused a death or they find your action culpable or negligent...
Working at Netflix you won't go to jail for a screw up in most cases. Screw up on the software for a nuclear power plant and cause a melt down you very well can. You also have chemical industries, dams, various labs, military equipment, industrial systems many of which you can not only get one but multiple or many people killed.
So why I here someone say there isn't just one way. I think the person is inexperienced and a bit of an idiot.
Because clearly it does depend on what you are working on if there is or isn't just one way. Generally the practices I found working over in that area of development transfer well. They generally provide increased stability and performance. So I'm pretty much of the mind there is actually there is always a best way and then there are many wrong ways.
Im the boss and teddy gets fired immediately if he talks about his dog in any meeting
And bill also gets fired immediately if he brings the dog to the office because "there's nobody to take care of him"
One sign of a bad programmer is me after having to work back to back 80 hour weeks. Six months later I am still fixing the bugs and scratching my head trying to figure what planet I was on when I decided to write that.
nah that just means you are progressing
For me, stand ups go way past 5 minutes because our Software Architect goes on a 30 minute monologue about the tape drive system we are buying every damn day.
5:20 no Prime, he's just saying, "There are no absolutes, ABSOLUTELY." This sentiment is valid, and probably correct.
I do agree he's being a pedant tho
good takes, i definitely think curiosity is key
From the beginning, I feel personally attached
content aside, i think your videos are a bit low in volume, could you make it louder next time? that would be great :3
Just turn up the volume
@@tsunami870 i mean i could but it would make the other applications too loud because i tend to watch his videos and do something else on the side
I don't get the "I'm a software engineer, not a programmer" one. That has nothing to do with arrogance. It's a better descriptor of your work. Programming/coding is somewhere between 0-30% of my actual worktime every day. I'd love for it to be 80%, but it's not. It's like calling a chef a "food cutter". At my workplace, nobody uses the word "programmers" or "coders" or even "software engineers". We use "developers". How is this now a contentious issue?
The comment about quitting is twice as funny now
I am not a programmer. I just smash out code until the computer leaves beep mode.
"Shades of gray" doesn't mean "no right or wrong," it means the black and white is very granular and requires closer inspection. It's nuanced. Gray is literally black pigment mixed with white pigment (or some white photons but not filled with white photons. There aren't any "black" photons.)
The Peter principle sounds kinda like what Dilbert said about the pointy haired boss. Failing upwards and dumber as they got promoted higher
"You dont do this - RIGHT CHAT..? RIGHT CHAT?!?!?!?"
Standups can be short. We used to have 15min ones. First 5min used to be just chit chat
"I am not sure how you can be so arrogant with 3 years of experience."
I'll tell you why, because it takes me about the same time to write a program as you doing the work manually. The difference is once I write a program it never has to be done manually again, it is functional forever (with slight tweaks as needed), even if I leave the company my work is *still* doing work, and clearly you can't do it.
This was totally not written by a dev.
I don't know that people think they're cool for having a whiteboard. The fact that he disses the whiteboard person for having a bulleted list on it makes me think that the author actually thinks you need to be at least a certain level of cool to deserve a whiteboard. I'm guessing here but I think the author thinks whiteboards do make you cool and because of that it would be pretentious to show it off by having it be in the background. So he has one but it's not in his background.
Same with the judgement about the mechanical keyboard. Some people just like having nice things. When I was in school, I carried an HHKB with me at all times and used it in the computer labs. I didn't do it to be cool, I did it because I like my keyboard and I trusted the people around me to not be like the author. I can imagine the author seeing me and thinking "Look at this guy with his keyboard, he's only a 2nd year student and he thinks he's the shit".
I never met any programmer who fit into any of these descriptions...
Agreed. It's making me wonder about the author of that article.......
Yeah this is the kind of article that I'd expect from the general section of medium where it's usually coming from the ultra left rant lol. A lot of ad hominem and projecting, without any regards of reality. Haha.
@@edward8064 I mean I’ve read my fair share of medium articles, as well as this specific author’s, and most of this person’s stuff is this unhinged. Dramatically more so than other writers on that site. So idk what politics has to do with it. Only ad hominem (and projection?) I’m seeing right now though is your comment, bud.
@@Zer-ei4co There were times when my Medium's timeline is filled with a lot of SJW's article and that's why it's been a long time I didn't check the site. But I just checked it, and it looks much better than it used to. So yeah, probably I'm wrong and projecting, or probably we simply have different experience about it..
@@edward8064 It seems like a matter of experience. There is nothing wrong with making assumptions and avoiding a website based on that. Even if it is not entirely correct. @Zer-ei4co's accusation of projection is unbased.
haha i haha - is that a joker reference?
No standups at netflix? Someone got a quick rundown?
8:38 but you did…
I use a mechanical keyboard and I don't even believe there's such as thing as a "software engineer" or that it would be a good idea to have them. 40 years as a programmer.
Yo if im not hearing about atleast one dog im not going to stand ups.
As of making this comment, I haven't watched the whole video. But for the first point, "I'm a Software Engineer, not a Programmer" - I have NEVER heard anyone say anything like this.
I personally refer to myself as a Software Engineer, because I like how that sounds over Programmer. Not sure why, it's just a me thing. But I have never thought of those two meaning different things. Furthermore, I would not "correct" someone if they called me a Programmer.
Is there a stigma to using the term "Software Engineer"? Does it sound pretentious to others? I'm genuinely curious now 😮
About the rewriting thing, I think arrogant newcomers are indeed inclined to rewriting. Because it is always hard to learn a mature project: even if it is near perfectly designed and well maintained-it is a complex thing, it contains a lot of know-how that the company gained over time. It is a steep learning curve. On the other hand, rewriting always seems easy-you have a clean sheet of paper in front of you. There’s nothing to read and learn. The learning curve is gentle and flat. It is just a lot longer, and it leads you through the same mistakes that the mature project has already learnt. But it is an easy entry point.
The author of this article seems like someone who has their head up the assess of his previous teachers (at school) and his current managers / employer. People like him are the reason why I can do the same thing as an entire company.
I have a whiteboard right behind me in my office.. It's not my fault :)
I don't even use it except for memes. Something like "I'm drunk" in russian, but it looks like a serious note and I hope that no one can read it