How To Make An IMPACT As A Junior Developer

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

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

50% 1

What are the things you can do to really stand out from the crowd as a junior developer in a development team? Frank Yu, a leading engineer at Coinbase, offers his advice for junior developers in this clip from his appearance on the Engineering Room Podcast.
You can watch Frank's FULL episode HERE ➡️ • The Code Behind HUGE T...
___________________________________________________
🙏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
-------------------------------------------------------------------------------------
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
📧 AVOID THESE COMMON PITFALLS
In this compact pdf guide, I list the pitfalls developer often fall into over the course of their career, and offer advice on how to avoid/break those bad habits. Grab your FREE guide HERE ➡️ subscribepage.com/avoid-pitfa...

Наука

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

30 сен 2023

Ссылка:

Скачать:

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

Добавить в:

Мой плейлист

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

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

@grasshopper3085 8 месяцев назад

Hello Dave here's an idea for a video: explain what things a 1-year experience junior developer should know in 3 levels: 1. Things juniors absolutely MUST know. 2. Things juniors are reasonably expected to know. 3. Optional things that set juniors apart in interviews.

@user-mikesmith 8 месяцев назад

I think the best way for anyone at any level to maximize impact is: 0. Do a high quality job on your core work. People will often depend and rely on the core work you are doing. 1. Identify the most important problems the team needs to solve. If you don’t know what those are, ask leadership. 2. Filter #1 to the problems not already handled. Many of the top problems already have people working on them, but find the critical problems not getting any attention. 3. Filter #2 to the problems you can best attempt to solve with your personal strengths. Of course, communicate intentions with management as you go through 1-3. This process will provide potential for unlimited career growth as you solve bigger and bigger problems in your career. The test system suggestion from this video could appear as one of those problems but may not. It is important to continually adapt to the current situation.

@fennecbesixdouze1794 7 месяцев назад

Being a junior dev is awful. Any junior dev who actually moved as slowly and carefully as they should to keep their quality up and to optimize actual long-term value throughput would end up fired by the business people for not delivering enough story points. Best as I can do as a principal is constantly impress on the business the importance of quality and that junior devs need to learn how to produce quality to optimize their delivery of value, but the business people construct all kinds of perverse incentives to deliver crap things quickly that end up slowing down the business.

@blackjackjester 8 месяцев назад

When you say "build frameworks", what do you mean? This is a very common thing for people to say, but rarely is there examples of it. What ive usually noticed is when people build "test frameworks", they're typically just using a NIH mindset, reinventing the wheel, then causing maintenance problems in the future. I'd love a video on what a "test framework" actually is.

@ContinuousDelivery 8 месяцев назад

Checkout some of my videos on Acceptance Testing & BDD. It is a topic that is too big for a RU-vid video, so I have training courses that teach it, but they aren't free I am afraid. courses.cd.training/courses/atdd-from-stories-to-executable-specifications

@mecanuktutorials6476 5 месяцев назад

I’m doing this at my job and it really is that. A “NIH” mindset leads to proprietary code and integration that in turn needs custom test infrastructure.

@AnonymousAccount514 7 месяцев назад

As an sdet…I disagree….building test frameworks isn’t the same as building an application and definitely not the same as building a brand new feature from scratch Don’t waste your time building a test framework…it won’t prepare you for building apps