What Makes A GREAT Software Developer? | Martin Thompson On High Performance & TRUE Expertise

Подписаться 205 тыс.

Просмотров 14 тыс.

50% 1

Martin Thompson talks about his experience in high-performance development teams and offers his thoughts on some of the traits of GOOD software developers.
This is a clip from Martin's full Engineering Room episode which you can watch HERE ➡️ • How To Manage Software...
-------------------------------------------------------------------------------------
⭐ PATREON:
Join the Continuous Delivery community and access extra perks & content! If you join this month you will be entered into a book giveaway to get a free copy of Dave's latest book "Modern Software Engineering", or even a signed copy of one of Dave's books.
JOIN HERE ➡️ bit.ly/ContinuousDeliveryPatreon
_____________________________________________________
🙏The Engineering Room series is SPONSORED BY EQUAL EXPERTS
Equal Experts is a product software development consultancy with a network of over 1,000 experienced technology consultants globally. They increase the pace of innovation by using modern software engineering practices that embrace Continuous Delivery, Security, and Operability from the outset ➡️ bit.ly/3ASy8n0
-------------------------------------------------------------------------------------
📚 BOOKS:
📖 Dave’s NEW BOOK "Modern Software Engineering" is now available here ➡️ amzn.to/3DwdwT3
📖 "Continuous Delivery Pipelines" by Dave Farley paperback ➡️
amzn.to/3gIULlA
ebook version ➡️ leanpub.com/cd-pipelines
📖 The award-winning "Continuous Delivery" book by Dave Farley and Jez Humble ➡️ amzn.to/2WxRYmx
NOTE: If you click on one of these Amazon Affiliate links and buy the book, Continuous Delivery Ltd. will get a small fee for the recommendation with NO increase in cost to you.
-----------------------------------------------------------------------------
Also from Dave:
🎓 CD TRAINING COURSES
If you want to learn Continuous Delivery and DevOps skills, check out Dave Farley's courses ➡️ bit.ly/DFTraining
📧 Get a FREE guide "How to Organise Software Teams" by Dave Farley when you join our CD MAIL LIST 📧
The best way to keep in touch with the latest discussions, events and new training courses, get FREE guides and exclusive offers. ➡️ www.subscribepage.com/organis...

Наука

Опубликовано:

8 окт 2022

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 45

@eriklintsev Год назад

Curiosity eventually brings you to the point of humility and constant wonder

@trappedcat3615 Год назад

Sometime its good to be curious about not being curious and keep it simple.

@agumonkey Год назад

It's a state of mind we forget along the years, where you can just immerse your mind into a topic / domain / problem. Even better in team (extreme/pair programming). The only good days I have at work were days like that. Too rare.

@eriklintsev Год назад

@@agumonkey feel you, hope those days become less rare

@marflage Год назад

@@agumonkey I like pair programming too much. I somewhat did it with my uni friend for assignments and some side projects. We used to have a discussion and we would not realize we were discussing too deeply into the matter. I feel like we both grasped the concepts better after going on like that. It is also important to note that such types of discussions are not exclusive to software engineering; every concept/person can benefit from those.

@Lee14G Год назад

Dos 1. Be Curious 2. Adapt change 3. Learn fundamentals Don’ts 1. Learn syntax and know every corner of a language

@thomasking9573 Год назад

This has helped; we're looking for a new developer and I struggled to articulate what I think we needed. I thought about some things like ownership, interest in the craft, mentorship, etc. but the curiosity aspect I wasn't thinking about. But that's it, the things we need someone to help us improve on (as a team) are things that require exploration. Now I just need to think about how to find a curious developer.

@ContinuousDelivery Год назад

Great! I am pleased that you found this helpful. I did a video on interviews, it is mainly aimed at the interviewee, but also offers some advice for interviewers too, I hope this may help some more: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-osnOY5zgdMI.html

@cjp0605 Год назад

Actively seeking to disprove what you believe is a superpower.

@ContinuousDelivery Год назад

Absolutely!

@Name260812 Год назад

Wow. Thankfully I stumbled on this channel. Nice to hear sensible mature people speaking .

@ContinuousDelivery Год назад

Welcome aboard!

@mutsukira Год назад

Thank you, that resonate so much with me.

@lordlucan529 Год назад

Spot on. When I interview I will ask what things the interviewee has developed, researched or learnt about in their own time, and ask them to talk about it. You quickly find out if they have an innate curiosity or they just got to 18 and picked a well paid career path.

@rothbardfreedom Год назад

Obviously the one that close more story points in Jira.

@davidravnsborg2565 Год назад

Unless there's a pattern of bidding up story points on stories they tend to take, if the team isn't good at estimating story points consistently, if the person helps write or accept bad stories with gaps between actual requirements and what's in the story, or especially if the person just takes shortcuts to getting stories written at the expense of good practices which improve maintainability. If any of those red flags exist, then the one with the highest points total is winning a losing game the fastest, and ultimately acting as more of an anchor on the team rather then resolving those issues first.

@Spiderboydk Год назад

Mike Acton, a prominent proponent of data-oriented design, has reached the same conclusion: when hiring, the only correlation he can find between a candidate characteristic and how good a hire they are, is strong, innate curiosity. Grades, schools, coding interview questions, nothing else correlates at all according to his experience.

@christophjahn6678 Год назад

Back in 1989 I took apart my Commodore 1571 floppy drive 🙂. And I really would have loved to have been on the LMAX project !!

@ContinuousDelivery Год назад

It was a lot of fun. 😎

@orange-vlcybpd2 Год назад

Not be afraid of doing something wrong. Be curious and try things out, to learn from it. We dont learn when we read books, we learn when it hurts. So go out and make your mistakes. Im not a developer, but a test automation guy. And for me experimenting with things is absolutely natural everyday business, and i learn a lot. Some of the developers in my working environment stick to what they know is working, and try to stick to the known path. I try to go the unknown path. Not trying, not experimenting, makes you live in the world of old assumptions. But the environment around moves forward and so should we. That is the agility. Adaptation is key. It is crucial for surival of the species. And in philosophical sense, i would like to quote Bruce Lee here: be water, my friend.

@andrewharpin6749 Год назад

Ironically I took my parents video recorder apart when I was about 6 or 7, my mum took the remains up to the TV repair shop (remember them! ;)) and we left it with them and they put it back together. I'd taken it apart perfectly, but was lacking enough knowledge to return it to function. "The knack" as they call it in Dilbert.

@lordlucan529 Год назад

It was radios and electronic toys in my day - by the time I hit my teens I'd learnt to leave the video recorder alone ;)

@ericpmoss Год назад

I would emphasize the ability to become an expert in the subject matter. In one job I had, I knew people who were much better programmers than I, but for whatever reason, they just didn't 'get' that subject. So they didn't write code that did the right thing *for the right reason*, and they couldn't see underlying simplifications that were possible.

@colinmaharaj Год назад

4:40 So I use a C++ dev environment for 25 years and won't change that, but I'm in a new dev role and I haven't been disappointed. I'm solving problems with those tools, and I find myself writing my own tools. 6:00 I use C++ Builder for 20 years plus now. When I was much younger, I used to develop stuff in dos using Turbo C++. I've always maintained the line of compilers that competed with Microsoft. and I don't do managed or scripted like C# or Java or python

@Flamechr Год назад

As a former section manager the things I Looked into was. 1: personality can you work well together with others ? 2: As you mention curiosity what are you working with in your spare time ? GIT data and so fourth 3: code quality do you have pride in your work. GIT "comments, unittest, ect's"

@mariuszjelen9101 Год назад

curiosity is something that you have to be born with, opposite to programming skills that you can learn on the job rather easily

@bigstones84 Год назад

RISC vs CISC mindset! I've often though like that. I tend to be RISC too, and I like simple languages, simple to learn and read (eg. see the number of reserved keywords in Java or Go vs C# or Kotlin). It's the programming and design concepts that I want to learn, so that I can apply them in whatever language as a tool for thought. Saving a few keystrokes won't make much difference if I don't know how to represent a problem, and having to learn a new syntax is just cognitive load. However, I still question my approach when I gradually learn new language features and end up using them daily. What's the difference between these two mindsets?

@gustavoandrade58 Год назад

You only need one month experience with a language to get used to the reserved words. Anything other than that is just lazyness.

@engineeringvision9507 Год назад

@@gustavoandrade58 You're missing the point though. Excessive features offering minimal benefit while potentially obscuring the key concepts.

@gustavoandrade58 Год назад

@@engineeringvision9507 Well, ive been working with kotlin for some time and all reserved keywords are understandable and great for code flexibility. Who is defining "Excessive features"? Who is defining minimal benefit? If you want to be opinionated about something, you need to have experience with it. I am not missing the point, most languages go throw heavy discussions by a lot of smart people. Nothing is perfect, everything has tradeoffs, and there will never be a "right way" approach to build a language. My point is, dont criticize languages by its number of reserved keywords if you are too lazy or biased to not learn them. If you want a simple and easy to read representation of a problem, just do pseudocode and some diagrams. Languages need to be resourceful, and that not always comes with a small price.

@brownhorsesoftware3605 Год назад

I was advised to abandon my first attempt at a career as a harp major at a music conservatory by my top tier teacher (and first female member of The Cleveland Orchestra) not for lack of ability but because I "was interested in too many things".

@RicardoSilvaTripcall Год назад

I think the problem in this case is, trying to go deep in a variaty of subjects ... you can be curious and learn how new things works, build something in it and add it to your toolbox ...

@brownhorsesoftware3605 Год назад

@@RicardoSilvaTripcall I think it is an illustration of one difference between what is required for success as a harpist vs what is required for success as a programmer.

@MohamedSamyAlRabbani 11 месяцев назад

In my opinion, be productive, be humble and accept that you are wrong sometimes, learn to have a scientific technical discussion or accept that your ideas won't be accepted, prove it with code, and don't require other people to have to dance around your ego

@brunofunnie Год назад

Why this logo reminds a LOT Captain Disillusion logo?

@ContinuousDelivery Год назад

Maybe because "Captain Dissillusion" and "Continuous Delivery" both start with "C" and "D" 😉 We made our company logo long before I became aware of the captain, so this was a matter of convergent evolution, not plagiarism.

@j.j.9538 Год назад

What makes a great software developer? Connections

@gronkymug2590 Год назад

Dave, please try Rust and let me know where/when using it would be very efficient 🙂

@Sergio_Loureiro Год назад

As you usually have great t-shirts, why not one about: "You should ignore what this man says because he's old, grumpy and ugly" or whatever that person said. Then appear with it on a future video of yours. And after put a comment hash tagging the person and linking to to his/her original comment. And BTW, even agreeing with you on the irrelevance of your beauty for a SW Developer job, I doubt very much the person who said this is some kind of supermodel, or even one who could be consider beautiful.

@MohamedSamyAlRabbani 11 месяцев назад

Evidence, just because there is a lot of buzz doesn't mean that something is true with no proof.

@nexovec Год назад

If he says what I think he says I will seriously unsubscribe from this channel.

@nexovec Год назад

Okay I was completely wrong in thinking he's going to talk about how CI is so important for 10 minutes, I'm glad to be wrong :D

@davidravnsborg2565 Год назад

@@nexovec CI is only really important if you're frequently working on the same code as other people, or an established codebase with good tests. It's ultimately about testing yours and everyone else's features without introducing bugs, and minimizing code conflicts.

@Name260812 Год назад

Only English people should speak English. Is a treat to listen.