Emily Bache

@emilybache

Technical Agile Coach, Conference Speaker, Author. (). she/her

Göteborg, Sweden
sammancoaching.org
Bergabung Maret 2009
32 Foto dan video Foto dan video

Tweet

Anda memblokir @emilybache

Yakin ingin melihat Tweet ini? Melihat Tweet tidak akan membuka blokir @emilybache

  1. me-Retweet
    17 jam yang lalu

    The ticket application for is now open: Please make sure to use the diversity checkbox, in case you are a member of an underindexed group! The SoCraTes conferences are non-profit and my favourite event of the year!

    1 balasan 13 retweet 12 suka
    Tampilkan utas ini
    Tampilkan utas ini
    Batalkan
  2. me-Retweet
    6 Mei

    Last year I learnt about two software crafting approaches which both keep me captivated. Cont.

    10 balasan 4 retweet 5 suka
    Tampilkan utas ini
    Tampilkan utas ini
    Batalkan
  3. 5 Mei

    I still can't quite believe it - my name up there as a keynote speaker on the Craft conference website. I'm really looking forward to this!

    1 balasan 1 retweet 17 suka
    Batalkan
  4. 5 Mei

    Glad you enjoyed watching these!

    I just discovered, and enjoyed watching, these three videos made by detailing some really interesting Gilded Rose refactoring: Part 1: Using CombinedApproval, code coverage and mutation testing to create tests before refactoring: ) >>>
    Tampilkan utas ini
    1 retweet 10 suka
    Batalkan
  5. me-Retweet
    4 Mei

    There is no statistically significant correlation between programming language and defect injection rate.

    5 balasan 86 retweet 209 suka
    Tampilkan utas ini
    Tampilkan utas ini
    Batalkan
  6. me-Retweet
    4 Mei

    "What C4 model tooling do you recommend?" - The Structurizr DSL in conjunction with whatever diagram renderer you like best. "And what about free tooling?" - Most of the Structurizr tooling *is* free. 🤦‍♂️

    2 balasan 10 retweet 52 suka
    Tampilkan utas ini
    Tampilkan utas ini
    Batalkan
  7. me-Retweet
    2 Mei

    Software engineering, 1966. Via Bob Rauf.

    32 balasan 46 retweet 423 suka
    Batalkan
  8. me-Retweet
    30 Apr

    "TDD only works if the requirements are clearly defined." Let's flip that on its head: TDD clearly defines the requirements.

    28 balasan 55 retweet 278 suka
    Batalkan
  9. me-Retweet
    30 Apr

    Help! A need a word for "Anything we do in our code, purposefully or not, that makes our code harder to extend and maintain." A term that includes the idea of "Technical Debt", but is broader and includes everything that makes tomorrows code harder to work with than it was today.

    198 balasan 26 retweet 149 suka
    Tampilkan utas ini
    Tampilkan utas ini
    Batalkan
  10. me-Retweet
    28 Apr

    Today was a very cool being-a-freelance day. I'm buzzing. I delivered a learning hr to some lovely peops, I met all the wonderful folk at to talk about not making each other feel stupid, and I delivered my first training course!

    3 balasan 1 retweet 23 suka
    Batalkan
  11. me-Retweet
    27 Apr

    Very much looking forward to joining part 1 of 's Learning Hour course this afternoon!

    2 retweet 6 suka
    Batalkan
  12. me-Retweet
    27 Apr

    The "head & tail" thing in python still impresses me. It's a simple bit of lispishness: head, *tail = collection If there is only one item, tail is empty. ValueError is raised if collection is empty. It's handy with split, re.split, etc.

    3 balasan 3 retweet 20 suka
    Batalkan
  13. me-Retweet
    26 Apr

    At every we have an external speaker to give a keynote presentation. This time, our speaker was the fantastic , talking about a way to spread skills and build culture across our Engineering teams using the method. Thank you Emily! 😀

    4 retweet 6 suka
    Batalkan
  14. me-Retweet
    25 Apr

    Metrics from GitHub and JIRA can't tell you how productive an engineering team is.

    25 balasan 168 retweet 794 suka
    Tampilkan utas ini
    Tampilkan utas ini
    Batalkan
  15. me-Retweet
    25 Apr

    We started to spend our Thursdays working with the part-time , working the ins and outs of our material. At the time, this meant going through code katas.

    2 retweet 4 suka
    Batalkan
  16. me-Retweet
    22 Apr

    We've won the Learning Solution Excellence award with the online , initially created by as a card game. A quick and fun way to explore alternatives for a pipeline. Play Pipeline online:

    2 retweet 5 suka
    Batalkan
  17. me-Retweet
    21 Apr

    The most important practice for continuous integration to work properly is frequent check-ins to trunk or mainline. You should be checking in your code at least a couple of times a day.

    5 balasan 43 retweet 124 suka
    Batalkan
  18. 22 Apr

    Great writeup, interesting to hear about another approach to technical coaching

    Here are some notes on a technical training experiment we did at my client Worldline. It was inspired by techniques from and , so if you like it, check their stuff out. ;-)
    3 suka
    Batalkan
  19. me-Retweet
    20 Apr

    I really enjoyed chatting with the Mob Mentality hosts and about how we use the (aka mob) as a teaching technique on our academy programme. Give it a listen!

    Join us as we discuss "Learning through the Ensemble" with We not only talk about pairs & ensembles at Academy but we also share experiences about troubleshooting issues in new ensembles
    Tampilkan utas ini
    1 balasan 6 retweet 6 suka
    Batalkan
  20. 20 Apr

    Thankyou for the summary!

    A small recap on ensemble programming after reading the very recommendable "Technical Agile Coaching with the Samman method" by
    1 balasan 4 suka
    Batalkan

@emilybache masih belum menge-Tweet.

Pemuatan tampaknya berlangsung agak lama.

Twitter sedang kelebihan beban atau mengalami sedikit masalah. Coba lagi atau kunjungi Status Twitter untuk informasi lebih lanjut.

    Mungkin Anda juga suka

    ·