Wojtek Olearczyk retweeted
It is a key challenge in AI, at least within the Reinforcement Learning framework, to learn to make decisions under uncertainty. Our #engineering team demystifies how they approach the Experiment-as-Code concept from start to finish: hubs.ly/Q019CHz40
🔥 We would like to share what we've learned when modularising our #Ruby application and how tools like #CQRS help us.
That is the strong beginning of the Engineering Blog at Global App Testing 🚀
#ruby #rubyonrails #cqrs #remoteteams
hubs.ly/H0QRnWV0
Our new white paper, 'The Reason Tech Leaders are Turning to Exploratory Testing in 2020' is available now. lnkd.in/ebeq_vt
Have you ever face challenges to scale Engineering teams?
I'll be speaking tomorrow on a webinar with some insights.
You can still register at hubs.ly/H0p2Rrl0 # #digitaltransformation #scalingup lnkd.in/eQ7-v3Z
Wojtek Olearczyk retweeted
Read our Simple Programmer guest blog to discover 10 best practices you can use to avoid pesky bugs when developing software 🐛 hubs.ly/H0m36X80
Wojtek Olearczyk retweeted
Order your FREE copy of the #LeadingQuality book and join the #SoftwareTesting industry revolution today! 📚⚡ hubs.ly/H0k5l6B0
Wojtek Olearczyk retweeted
"The easiest, high-impact change you can make, to be more productive, is taking control of your interruptions. Interruptions are terrible for your productivity." by Devon Peroutky
hubs.ly/H0gBd-h0
Wojtek Olearczyk retweeted
KRUG season finale aka KRK.rb lineup is getting more and more interesting thanks to @hasumikin @_solnic_ @jonatasdp @mpapis @_m_b_j_ @jac33k @anton_davydov #ruby #programming #omgkrk #rubyonrails
Are you doing OKRs right? - A conversation with OKR-expert Ken Norton from Google Ventures via @RangeLabs range.co/blog/are-you-doing-…
Wojtek Olearczyk retweeted
Rather Than a Micromanager or Absentee Manager, Be a Thought Partner: buff.ly/2TRsjle
Wojtek Olearczyk retweeted
"One of the most important competencies of a principal engineer is to become a force multiplier [...] by advocating for best practices, gently reminding people of why the processes we have exist, and helping [other] engineers find ways to ‘level up’." buff.ly/2RWI4KG
Wojtek Olearczyk retweeted
Wonder what exceptional #engineering #leaders look like? Tune in to listen to @Intercom's podcast with @reddit’s VP of Engineering, Nick Caldwell on the differences between management and leadership, fostering diversity in tech, building trust and more 🎧 hubs.ly/H0dRd830
Wojtek Olearczyk retweeted
And it's a wrap! Thank you again to all our team, speakers and the 100+ delegates who've made this event a success! We had a fantastic time meeting so many inspiring people! 🇵🇱🚀😍
I have a pleasure to be invited to the #PMI #Kraków Seminar. Please join me to listen more about #learning on 6th September in Kraków. lnkd.in/gUhJ-3v
The story about #EventStorming in Global App Testing. A technique is great, we've already done at least 5 sessions. Thanks for the intro from @wjptak and @mariuszgil globalapptesting.com/blog/ev…
Wojtek Olearczyk retweeted
Timelapse recording from our yesterday #EventStorming practice session. And it’s just a starting point to something more…
Wojtek Olearczyk retweeted
Lean & agile... Observations On Scaling Engineering And Product Teams | @MyMonese @TomBarbour1 bit.ly/2FztvlR
Wojtek Olearczyk retweeted
Output = what you build. Outcome = what happens after it comes out. Use output-centric metrics to measure the rate you build, number of defects, if you’re on time. Outcome-centric metrics measure if people use, keep using, and like what you built. OKRs are ideally outcome-centric xitter.cf/cglambdin/status/97285…
Replying to @jeffpatton @meetfelipe
Are outcomes and OKRs different ways of talking about the same idea? Would an outcome be akin to an OKRs' objective, and it's target metrics the KRs? Or maybe a goal would be akin to the objective, and the outcomes the KRs? Or are they different ideas?















