Twitter | Search | |
Emily Bache
Technical Agile Coach. Conference Speaker. Author of The Coding Dojo Handbook, (). Singing, mountainbiking, cross-country skiing
3,707
Tweets
810
Following
2,932
Followers
Tweets
Emily Bache retweeted
Per Hammer 21h
We did our first with 4 interns this week. and “fizzbuzz but only two sets of {} per method”[1]. 90 minutes after I knew two new keyboard shortcuts, taught some refactoring tips, and had a great conversation about readability. [1] you should try it
Reply Retweet Like
Emily Bache retweeted
EXPAND-conf 23h
Y E S, that's right! The early bird tickets are already SOLD OUT! Make sure you won't miss out on the regular tickets: We have awesome speakers for you: and many more!! :-)
Reply Retweet Like
Emily Bache retweeted
Gene Kim Jun 25
When you see here at , give her a big high five for winning the Shingo Publication Award! She’s amazing! (Here’s what I think the new cover will look like! :)
Reply Retweet Like
Emily Bache retweeted
Seb Rose Jun 25
Reply Retweet Like
Emily Bache retweeted
Daniel Kraus Jun 25
Characterisation tests for faster page object development: Very cool blog post by in a series about page objects for testing set-top boxes (!) with .
Reply Retweet Like
Emily Bache retweeted
Steve Smith Jun 24
Posted: Build The Right Thing and Build The Thing Right (part 2). Why an organisation in peril should co-evolve its product development and IT capabilities from the outset, not pick one over the other
Reply Retweet Like
Emily Bache retweeted
Steve Smith Jun 24
Reposted: IT As A Cost Centre. Updated to emphasise a functionally segregated IT department is a consequence of cost centre accounting, and how disparate incentives create adversarial relationships with product areas
Reply Retweet Like
Emily Bache retweeted
Angie Jones Jun 24
I just blogged about verifying entire API responses with h/t
Reply Retweet Like
Emily Bache retweeted
Brian Button Jun 23
I was amazed at how easy it was to get to 100% coverage with approval tests and IDE tooling. That was the big lesson I took from your talk, followed very closely by Lift Up Conditional.
Reply Retweet Like
Emily Bache retweeted
Emilien Pecoul Jun 19
is now by far my best teaching tool 👍
Reply Retweet Like
Emily Bache retweeted
João Proença Jun 20
Replying to @mirjanakolarov
And she’s speaking about how exploratory testing can be a preparation for automated regression tests, allowing you to better assess risk, which drives the decision for automation.
Reply Retweet Like
Emily Bache retweeted
Thomas Sundberg Jun 18
That moment in time when you get a bug report, see the mistake you have made, create two unit tests for it and deploy a new version to production. In 13 minutes.
Reply Retweet Like
Emily Bache retweeted
Gáspár Nagy Jun 18
Reply Retweet Like
Emily Bache Jun 18
I've been having fun playing with PowerMock. I'm working on a new refactoring kata, where the tests need refactoring as well as the code
Reply Retweet Like
Emily Bache retweeted
Jo Van Eyck Jun 17
Replying to @XDetant @emilybache
Justin has a great write-up about the concept here (and explains really well why not to over-use it):
Reply Retweet Like
Emily Bache retweeted
Jo Van Eyck Jun 17
Repeat after me kids: I shall not use partial mocking features of my unit testing powertool. I shall not use partial mocking features of my unit testing powertool. I shall not use partial mocking features of my unit testing powertool. I shall not use partial mocking features of
Reply Retweet Like
Emily Bache retweeted
Laurie Jun 15
If you are a lead in any capacity your primary job is no longer to be the best coder in the room. Your job is to invest in learning the skills you need to effectively communicate and grow those you lead. Your words have the potential to sit with people for years, act accordingly.
Reply Retweet Like
Emily Bache retweeted
Llewellyn Falco Jun 14
Today I calculated that in the last 10 years I have facilitated over 1,500 sessions
Reply Retweet Like
Emily Bache retweeted
Nik Sumeiko Jun 13
Replying to @KevlinHenney
I call this "writing code with empathy" – when writing every line of code always think of other people who are going to read, maintain and figure our what this code does after you. We miss this skill much. It matters, because programming is a social activity these days.
Reply Retweet Like
Emily Bache retweeted
Praqma Jun 13
During the breaks of this fantastic line-up at next week, come say hi to us at Booth 14!
Reply Retweet Like