The STUPID MYTH Of Genius Software Developers

[@ContinuousDelivery]

You can get Dave Farley's FREE Guide "How to Organise SW Teams" here ➡www.subscribepage.com/organise-teams-guide

[@MisFakapek]

When could we see some good open source example of the whole CI/CD process with some good git history? That would be a good series to explain by example, not by just words and concepts. Don't get me wrong - I did enjoy your books but they are not as tangible as I would like to see.

[@jimhumelsine9187]

"I'm not a great programmer. I'm just a good programmer with great habits." - Kent Beck

[@kayakMike1000]

I need some of this Kent Beck in my attitude.

[@Flamechr]

Start off by writing the test

[@luxPacificus]

In my extensive experience as a software developer, I've experienced the issues presented here first hand. Continuous delivery using agile methods can result in lower performance due to excessive management interference. It's really tempting, by those in management, to pervert agile methods into simple micromanagement. I believe that these managers who do this actually believe they are doing agile. They are excited about using agile. They actually believe they are managing in an agile way. But, in reality, they are lying to themselves. They are fulfilling their dream of having direct control over the project. To properly do agile, people in the management role have to be brave enough to let go of the reins and let the team essentially self-manage. For a manager, it's scary and it kind of cuts them out of the process. Very rarely have I experienced agile done correctly. That's a sad state of affairs.

[@invalidaccount2315]

i agree, ive been programming for ~25 yrs, multiple languages, networking engineering, i have worked with 1 company that did scrum correctly, everything else was idealism, it is such an immature thinking pattern, im looking out for long running stable production code, which is essentially different from what we have today, ship as fast as possible well address design bugs later. praise glory to the white paper.

[@luciojb]

I hate that some times i did improvements by myself for a better performance or programming environment, there were unnecessary discussions and cut offs, there was always some kind of "shut down" or silencing.

[@BryonLape]

Looking at senior level positions on LinkedIn, many companies believe there is an endless supply of unicorns.

[@raffaeleloi]

Thank you so much for the videos Dave. You have a big influence in the concepts and habits that I learned and still learn. About the video I liked about the concept of changing habits in order to change thinking, this also apply to our lives, the habits that we have shapes our thinking. That also remindes me about the Kent Back phrase “I'm not a great programmer; I'm just a good programmer with great habits”.

[@Juzzyjuzzy]

Thanks for the presentation. This channel is one of the pearls of Tech KZbin. I particularly connect with the point regarding changing our thinking and behavior. Open-mindedness to change and newer ways of doing things is a great attitude for any team that wants to advance.

[@wstdonwiteout]

I agree that the idea of the "genius" developer is effectively a myth. However the notion of the 10x or 100x developer is not. This is the person who brings a process and way of working that uplevels everyone else in their orbit. In doing so they ensure that effort is invested in the highest leverage tasks with minimal waste.

[@T33K3SS3LCH3N]

Way too many companies pay junior dev salaries while expecting senior level performance... some others may not openly EXPECT it, but they NEED it to fulfil the goals they set out. And then everything inevitably goes to sht because the problems just keep piling up.

[@JedesonAlviso]

14:55 Our organization tried adding gatekeeping, and this truly impacted throughput and confidence. It also tends to foster a toxic environment

[@Juzzyjuzzy]

Gate keeping? Would you like to elaborate?

[@jesseogburn1175]

It's amazing to me how closely software development and manufacturing managment are related. I think it's mostly because both diciplines are working toward the same goal...good products. The way to that good product is correctly managing the resources available whether that is people sitting at a computer or people operating machinery.

[@ContinuousDelivery]

Understand the benefits of different pair partnerships, learn how to introduce pairing as an option for your team, and identify anti-patterns and how to avoid them. Get these tips FOR FREE direct to your inbox here ➡ www.subscribepage.com/cd-pair-guide

[@madmanX1314]

Before even watching the video: This must be a response to a lot of people in the comment section of the last video. Many of them said they wouldn‘t trust their bad junior developers ending up pushing bad code to production all the time, therefore pull requests. I can‘t wait to watch this video :-)

[@luciojb]

the market is awful. lot's of senior roles open, but only a very few developers have senior capabilities and correct skills and responsabilities

[@barneylaurance1865]

There's a great episode of the This American Life podcast about Nummi. It would be good to have a bit more acknowledgement in these videos though that a lot of us will already know about things like Nummi - a lot of us have read Accelerate.

[@brownhorsesoftware3605]

It all about having a culture of trust, respect, and honesty. That is my life experience. Success is a product of cooperation through practice.

[@logiciananimal]

I regard process steps as trail markers. Having the *will* to take that attitude on seems very difficult for some people. The gatekeeping mindset is so unfortunate. (And I say that as a security person!)

[@mrpocock]

I think there are different phases of any software project. In prototyping, you start with an empty folder and have to build up into some MVP - anything that works for some value of works. The next phase is building the real thing, ideally through continual maintenance and revision. Then it tends to go into some kind of long-term maintenance. IMHO, the only way to maintain the code long-term is to continuously rewrite it. As soon as you stop editing, even if only to improve the documentation or formatting or variable naming, it begins to rot.

[@BryonLape]

I thought prototyping died 30 years ago.

[@mrpocock]

@@BryonLape every new project I've ever been on started with zero lines of code.

[@mihaiungureanu3370]

Well, where is the genius statement coming from? In my experience I have heard it repeatedly and it came from organizations hiring testers that are not even able to edit a JSON. The criteria is if you are able to edit a JSON in vscode, then you are a genius. And those organisations will consider you too expensive to be hired as a tester.

[@matthewtrow5698]

I think the myth of "genius software devs" is more aligned to those devs who put the work in to learn more, vs those who "rest on their laurels" A developer who is passionate about their craft will spend time outside of work enriching their knowledge. That makes them better developers - clearly it does. I totally get the CD side of things - that has a HUGE amount of merit, when practised correctly. However, a team is only as good as the individuals within it. The way I see it, we absolutely have individuals who have an incredible ability - a genius level - but they are few and far between. What makes up the real performance is the passion, the desire, the striving to improve - and CD doesn't touch on _that_ particular ability. If you have a bunch of average developers - those who are only "on the day job" and never learn anything new, it doesn't matter WHAT they do with CD and best practices, a team of passionate developers will kick their asses every day of the week, regardless of whether they practice CD or not. I know this, I've seen it, I've experienced it - not everything is about Continuous Delivery.

[@techsuvara]

Lifelong learning… 😊

[@skyhappy]

In what ways are passionate developers better over their counterparts?

[@maxlutz3674]

@@skyhappy They are not. Passion leads to a negative attitude towards people who criticize their work, let alone find a bug. Passion is for people batting their wife to death with a golf trophy. Professionals have standards. Be polite, be efficient, have a plan to fix every bug you find. I adopted the habit to thank my testers for every bug they find. I want them to be happy and actually look for them. On my part I try to keep the "thank you" opportunities to a minimum. After all they are meant to be a treat not a staple.

We do CI and most of our team is new devs with almost no prior experience and is working wonders.

[@skyhappy]

Could you explain how it is working?

@@skyhappy We do a lot of pair programming for onboarding, several months of it and even after the new hire is fully integrated with the team pair programming continues to be a rather common occurrence.

[@Colochoide]

Great shirt!

[@sneibarg]

IBM focused on LEAN, and then missed the public cloud bus to Amazon.

[@skyhappy]

Could you elaborate

[@sneibarg]

@@skyhappy IBM is a small player in the public cloud market. They bought SoftLayer to compete and never caught up.

[@deanschulze3129]

Good points here, but the title is pretty misleading. This is really about gatekeeping and how management sometimes prevents improvement.

[@silmelumenn]

Is it possible to use benefits of CI/CD for ETL processes, and Data Warehousing?

[@ContinuousDelivery]

Yes with some adaption. The fundamental principles are all correct, and there are lots of data orgs that operate good deployment pipelines. I don't have a video directly on that topic, butt you could try these: "CD for Data" kzbin.info/www/bejne/gIHJk52BoZ6dmNk and "Engineering for Data" kzbin.info/www/bejne/oJawgp-aYpt1qrM

[@scvnthorpe__]

Some of us may be geniuses, but we're all idiots too. Gotta work around the ability to be wrong...

[@kamertonaudiophileplayer847]

I use a simple approach having only one reasonably good developer and around 5 developers very average and even below. It is a very stable and highly performing team. Talented developers are bad because they compete with each other and do not deliver.

[@Flash136]

Tom is a genius.

[@piotrd.4850]

Depends on the job, really. 90% of this is maintenance, stupid bau work nobody has balls to automate or drop and CRUDs. And then you have 5% of software that requires to dig into subject matter that is beyond reach of most population before first line of code is written.

[@xephael3485]

Lets set a bunch of small goals so we can micromanage our development. All of this is trying to push it on to the workers

[@luciojb]

this was a great video, bad management and bureaucracy kill software development

[@xephael3485]

What a bunch of bollocks as the British like to say... The GM example basically shows that "culture" has to be driven by management it's not something you can create with a team. There are also genius developers. And horrible teams of people that can't be redeemed.

[@MohamedSamyAlRabbani]

Myth of genius? We're already nerds with no social life! Leave us something!

[@BryonLape]

Software development is not a manufacturing process.

[@AdamJorgensen]

If all the developers at Google, etc are geniuses then I'm a monkeys uncle

[@maxlutz3674]

I think that the claim that some things only work with geniuses is just an excuse for keeping bad habbits. It´s frequently easy to predict the quality of software by looking at the habits of the developers - often before the first line of code is written.

[@captainnoyaux]

Oh boys. I've been working with valve and Google engineer and I saw terrible pieces of softwares

[@skyhappy]

Could you elaborate

[@captainnoyaux]

@@skyhappy pieces of softwares that are filled with bugs, untested etc.

[@a544jh]

Taylorism has no place in the modern software industry.

[@ContinuousDelivery]

Indeed!