Video

Genuinely nobody articulates how I feel, but cant out into words, like you do. My lack of binary thinking and belief that theres merit to multiple approaches has held me back career wise. I believe that not holding strong binary opinions can make you look unconfident.

Haha, the video length 😆

This advice is slightly misguided. What he's really saying is learn how to manage up with an inept manager. It's the most common manager, so it's good advice, but it's not actually the best way to operate if you have a competent manager with good leadership qualities.

“This is where I’ll probably get ripped in the comments” *proceeds to call procedural programming “method based” programming*. LOL. Seriously, though, great points! I don’t have a dog in the race, because I just love all the doggos! I see the attention to verifiable computing in the FP world, and I say, “That’s the part I’m in love with!” I don’t work in an FP shop, but I still bring those principles; I use short, focused chunks of logic that receive input and return some result, returning control to the caller - so what if they’re often namespaced to something that has some configuration constants and protected internal state? I don’t have the luxury of writing combinator chains in team code if that means I will be the only one on the team that understands what’s going on. I certainly don’t care what anyone calls it, so I simply write provable code.

It's a culture problem. It's a spiritual problem. People are full of pride and envy. Only leads to strife, contention, chaos, and destruction.

A video about how to think logically. Alright 🤷‍♂️

I was at a company where "fake agile" was the norm. I said as much, when I asked me to explain what I meant, I just told them "you use the name of agile as an excuse not to plan and not to think". They wanted you to "act agile" without the benefits of being agile...

When it comes to placing blame, it's fine to do it if your company is a contractor. Your project manager wants to know who to nag and will contact the people responsible to move the project along. The information is also important for when the customer comes around, and management needs to present themselves well or never get another contract again.

Context is key!

You need to be open-minded, but not so open-minded that your brain falls out. If we are unwilling or unable to say certain practices of the past (like OOP/Scrum) were a mistake, then we can never clear out conceptual baggage that could truly be holding us back. That's the problem with being overly soft and accepting in one's approach. There comes a time when one must confidently say, without reservation, "THIS IS BULLSHIT!" and you say it because all of the evidence points in that direction. True leaders have an instinct for doing that.

Sometimes its impossible to go further without refactoring.

Judging if you need to be a be a good developer and confidence inducer(usually ==trickster) is a binary choice is wrong, it is not indeed binary, Ex: Bill Gates(programmer and exceptional liar). The only problem I have with that is that being _also_ a confidence inducer makes me take ownership of business side and that doesn't belong to me, I am an employee. If I would have my own company, than yes, that would be true, but also the tariffs would at least triple or more.

Manipulative know it all.. … is very annoying

Why only in IT industry we have to talk about these topics? Do we developers are more fragile? Or IT so specific that we should reflect to these mistakes?

this applies to large firms. for startups productivity is priority.

Not a programmer but works mostly in automation testing and DevOps. Lot of you said applies as well. Trying to be open minded and just genuinely listening really well. Listening to others is a valuable but often overlooked skill that can either make or break your career. Technical skills are important but soft skills and communication as well.

YOU SHOULD DEFINITELY MAKE VIDEO OF DIFFERENT APPROUCHES IN DIFFERENT COMPANIES

Dont be a copilot for Copilot.

I have been wrong about the Tabs vs Spaces debate for a long time. It doesn't matter *most* of the time. If everybody is healthy and doing fine, use whatever you like. Modern editors can handle conversion. The moment you start working with someone who has a visual impairment or some reading problems, you want to switch to Tabs. The argument "But Tabs do not look the same on all devices" is exactly the point. You can tune your device to your needs. What do we learn from that? Sometimes there is a right answer (in this case Tabs), but it doesn't matter unless you meet someone who needs this to matter.

The more you know, the more you realize you don’t know. The irony is, being humble and acknowledging your gaps is often perceived as lack of confidence or lack of expertise

I have a strong anti-recency bias

Thinking about people's priorities is much better than just seeing that "both sides has a point". Everyone usually agrees on a list of important things, but rarely on how to prioritize them when they compete for resources. Take a example from the video, just saying "both 'being a good developer' and 'portraying confidence' are important" isn't enough. These two are often in conflict because a good developer should be documenting and reporting lack of confidence he has in the product. Anyway, it's a person's choice what they prioritize and who they want to be working with.

“Management is useless” is a belief usually stemming from work history where the results of bad management impact sometimes to the point of PTSD.

Business people often make unrealistic demands when they don't understand a subject. A healthy business has a technical project manager. It makes no sense for every single developer to have to persuade people who don't understand what they're asking for.

Someone show this to Theo ASAP

TDD + Clean Code will solve everything Interface for everything (why just 1 level deep) and 10 lines per function (why not just 3), always 100% test coverage and eliminate manual testing Don't mind the users or what they are saying, just treat them as dumb complainer, runs against the thinking you are better than everyone It is all about technologies, the newer or the complicated, the better 😅

Always wise, thx ❤

We estimate task la in our backlog in a weekly refinement meeting but if a task needs to be reestimated in the middle of a sprint, the engineer just says so at our standup and gives their input. It’s then usually what that engineer says but sometimes it’s voted on by all.

There are 10 type of programmers - those stuck in binary thinking and everyone else.

Really great video. I’ve encountered the Overconfidence in anecdotal evidence so many times along with the absolutist stance I’ve started calling it Rutters law. That whatever well established principle or concept you know in software development there will always be a small but growing group who describe it as an anti pattern. 😂 it works for everything. I have a slide with everything from Agile to Angular and links to ‘x is dead’ CZcams video.

I've been guilty of all of these at some point in my career. Recency bias is definitely a thing - OOP and functional programming have their place. Same with Scrum/Agile - it's how it gets implemented. The context is crucial. Vanity metrics are awful, especially when considering work/life balance as you mentioned.

I'd point a few more: - Being a good programmer makes you a good teacher. - Self-documenting code/Auto-generated documentation substitutes appropriate documentation. - Backwards compatibility is not an issue because you have access to the source code. - Optimization is not necessary because users/companies can always upgrade. - User Interfaces are just a beauty tack on top of functionality.

The most important thing is not told in the whole video. Lies: We don't need to give appropriate justification (rewards or punishments) on someone's work. If you can't get rid of this bias, your 1 to 5 doesn't matter, technically almost everything doesn't matter. Because what you'll be doing is just making a facade (or someone's else)

After years of experienced I realized that every tool I use has to be re-evaluated every 4 years - either it vastly improves and now is a great tool that was previously insufficient, or it hasn't been maintained and now other tools are exceeding it. Just saying, "Postman is great" or "Postman sucks" might only be true for a certain time period.

There are 10 kinds of programmers. Those who engage in binary thinking and those who don't.

Never follow the trend, do your homework about the project and select the right tools for it, not for you.

Perhaps if we take away ego, then being right will diminish and be seen as temporary insecurity. Nothing wrong with bruised ego, in fact, the more it's bruised, the better human you just might be. At the moment, my conviction

Great video. For people who want to dive real deep into this rabbit hole I recommend Iain McGilchrist's books on the two hemispheres of the brain (not the pop psychology, but the real research). Lots of insight about black and white thinking vs gray zone, understanding context and the need to be right on a topic. The titles are "The Master and his Emissary" and "The Matter with Things".

Try to do it right lose your job I am afraid that what years of development has taught me. Doing it right takes longer initially and the gains are invisible but the extra time is extremely visible.

thanks for sharing, all developers should see this video.

14:31 they key point in this video is to keep your biases in check. We all have biases and they often lead us astray. Biases and absolutism will sabotage your career. Also, try not to carry your past baggage everywhere you go. You shouldn't judge new people you haven't worked with before the same way as your past experiences. Give people the benefit of the doubt and maintain a positive mentality. That will lead to success in your career.

I enjoy watching your videos on my lunch break

I wish more online tech discussions would include details. Sometimes they are nuanced but without those details, people will interpret the nuance in different ways. People use vague terms like "scale" and "large" and "small". These words mean different things to someone working at Google, a high frequency trading firm, or a 2 person startup being led by people with no professional software development experience.

I love these videos, because they are general information that can be applied to any career. I work in desktop support, and have no work experience yet in programming, but these videos are preparing me for that next role.

I think you can have whatever opinion you want as long as you can logically explain it.

The point on anecdotal overconfidence is spot on and it really helped to hear someone who feels the same way. I am really frustrated when people see a different form, paradigm or method and their kneejerk reaction is to say "Thats bad" or "thats dumb", "just use xyz lol" or "thats wrong", instead of saying "why is it like this? Why have they implemented it like that? Is there something preventing them from doing it the way I believe is better? Is my way actually even better?" How can you look at the topmost tip of the iceberg of a software related decision, and then immediatly become, smug, condescending, assertive or dismissive about something that you know nothing about? Maybe there are reasons the project is like that, or why a certain tool or paradigm is used? If there are, then you need to take time to learn and explore the decision, codebase, developers and the project to learn why, instead of being an ass about it, or being dismissive. We as developers need to do better on the emotional maturity front as a whole.

Funny enough, programming has taught me that I am wrong ALL THE TIME XD

One that gets me is the cherry picking, "I read a blog post that said that X tech is dead and Y tech is the next thing that's going to take over the world. Nobody uses tech X anymore." How many times have I had someone say that when it isn't even close to true? They read some click-bait article and assume that it's gospel.

No worries, AI is going to take all of your jobs anyway. You have maybe 3 years left.....maybe. Want to do something productive? Then be an advocate for UBI. Otherwise, I'll see ya on the street.