یادآوری به خود

  • یوسف مهرداد بی‌بالان

خیلی کم، اما گاهی پیش میاد که مطلبی یا ویدیویی یا مقاله ای که مخلوق دیگری است رو به اشتراک بگذارم تا دیگران ببینن.

هر بار که این کار رو انجام میدم باید به خودم گوشزد کنم که، هِی رفیق، فراموش نکن که قرار نیست چیزی از اعتبار خالق اون اثر با این عملِ به اشتراک گذاشتن، به تو برسه و نمیرسه. بنابراین یه وقت ژست خاصی نگیری!!

 

منبع: از نوشته‌های دوست عزیزم، مهدی مری در لینکدین

بهار 1393: دوره متدهای چابک

  • یوسف مهرداد بی‌بالان

beautiful code

  • یوسف مهرداد بی‌بالان
function makeAdder(x) {
  return function(y) {
    return x + y;
  };
}

var add5 = makeAdder(5);
var add10 = makeAdder(10);

console.log(add5(2));  // ?
console.log(add10(2)); // ?

Understanding Coupling and Cohesion

  • یوسف مهرداد بی‌بالان

I invited some of my friends to discuss the nebulous concepts of coupling and cohesion in software design. How do we think about these topics? How do we understand the terms? How do we use that in our work as programmers? How do we teach it to others? How much does any of it even matter? Our invited guests: Corey Haines, Curtis Cooley, Dale Emery, J. B. Rainsberger, Jim Weirich, Kent Beck, Nat Pryce, Ron Jeffries.

Carry You

  • یوسف مهرداد بی‌بالان
I know it hurts
It’s hard to breathe sometimes
These nights are long
You’ve lost the will to fight
Is anybody out there?
Can you lead me to the light?
Is anybody out there?
Tell me it’ll all be alright
You are not alone
I’ve been here the whole time singing you a song
I will carry you
I will carry you
I know you can’t remember how to shine
Your heart’s a bird without the wings to fly
Is anybody out there?
Can you take this weight of mine?
Is anybody out there?
Can you lead me to the light?
You are not alone
I’ve been here the whole time singing you a song
I will carry you
I will carry you
You are not…
“Carry You” by Ruelle, Fleurie, on Youtube
What was the inspiration behind the song? => https://youtu.be/SJURFa1jlwo

Engineering Playbook

  • یوسف مهرداد بی‌بالان

CSE Code-With Customer/Partner Engineering Playbook

An engineer working for a CSE project…

  • Has responsibilities to their team – mentor, coach, and lead.
  • Knows their playbook. Follows their playbook. Fixes their playbook if it is broken. If they find a better playbook, they copy it. If somebody could use your playbook, give them yours.
  • Leads by example. Models the behaviors we desire both interpersonally and technically.
  • Strives to understand how their work fits into a broader context and ensures the outcome.

This is our playbook. All contributions welcome! Please feel free to submit a pull request to get involved.

Note: If you are reading this on github – head over to https://microsoft.github.io/code-with-engineering-playbook/ for a better reading experience

Why Have A Playbook

  • To increase overall efficiency for team members and the whole team in general.
  • Reduce the number of mistakes and avoid common pitfalls.
  • Strive to be a better engineer and learn from other people’s shared experience.

“The” Checklist

If you do nothing else follow the Engineering Fundamentals Checklist! It’s here to help follow the Engineering Fundamentals.

Structure of a Sprint

A breakdown of sections according to the structure of an Agile sprint.

General Guidance

  • Keep the code quality bar high.
  • Value quality and precision over ‘getting things done’.
  • Work diligently on the one important thing.
  • As a distributed team take time to share context via wiki, teams and backlog items.
  • Make the simple thing work now. Build fewer features today, but ensure they work amazingly. Then add more features tomorrow.
  • Avoid adding scope to a backlog item, instead add a new backlog item.
  • Our goal is to ship incremental customer value.
  • Keep backlog item details up to date to communicate the state of things with the rest of your team.
  • Report product issues found and provide clear and repeatable engineering feedback!
  • We all own our code and each one of us has an obligation to make all parts of the solution great.

Engineering Fundamentals

Fundamentals for Specific Technology Areas

Contributing

See CONTRIBUTING.md for contribution guidelines.

Awesome Agile

  • یوسف مهرداد بی‌بالان

Awesome Agile Awesome
Awesome List of resources on Agile Software Development.

Contents

The Fundamentals

Key Concepts

Agile Adoption

Team and Roles

Engineering

Product Development

User Stories and Estimation

Ceremonies

Metrics

Agile Leadership

Blogs and Podcasts


برای خروج از جستجو کلید ESC را بفشارید