Get help on whatever you're working on while you're at RailsConf this week. Today's the last day to book time ahead with us during Hack Spaces on Wednesday. Reserve your spot at https://forms.gle/dyJ839XcQZtd3kQJ8
#RailsConf #PairProgramming
#PairProgramming
Meanwhile in DevOps No.35
Ellis bans ensemble programming
#DevOps #EnsembleProgramming #MobProgramming #PairProgramming
How does #PairProgramming power successful #ContinuousDelivery?
In this #InfoQ video, Asgaut Mjølne Söderbom & Ola Hast share how their team ditched:
❌ Excessive WIP
❌ Lengthy pull requests
❌ Multiple test environments
The result?
✅ Ultra-fast deployments
✅ Superior code quality
✅ A highly cohesive, efficient engineering team
🎥 Watch now: https://bit.ly/4eu88np
#transcript included
#Culture #SoftwareEngineering #Agile #TechLeadership #Teamwork #QConLondon
Going to the last RailsConf next week? We'll be there! 10 Double Agents will hold office hours at the Hack Spaces on Wednesday, July 9.
More on who will be there at https://railsconf.org/hack-spaces/ —and you can even book a time ahead through Monday, July 7.
“We use the word programming to include all phases of the development process (design, debugging, testing, ...), not just coding. So, pair programming would include pair design, pair debugging, pair testing, and so on. In fact, two studies have indicated that pairing is most important for analysis and design. We believe people should pair at any time during development, in particular when they are working on something that is complex.” - Laurie Williams & Robert Kessler
Why agents are bad pair programmers
https://justin.searls.co/posts/why-agents-are-bad-pair-programmers/
#HackerNews #agents #pairprogramming #programming #badpractices #softwaredevelopment
I'm a strong proponent of learning with others. Here are two examples from physics and coding of the advantages of cooperative learning.
I am a #laptop person. Every couple of years I try to get a desktop machine, but it never feels right. Same with attaching monitors to the laptop. Too much hassle, and too much switching back and forth when moving around. With a good MacBook, everything is always right there and always works.
But I set up an external monitor for #PairProgramming now, so that I can watch the shared screen and also look at other windows. And it helps a lot with #Slack, too, whose window management is very clumsy.
Do you know your way around the #JUnit4 API? I'd love to add support for it in Greencently, my tiny #JUnit extension. How you can help: https://github.com/schmonz/junit-greencently/issues/29
#PairProgramming (if you'd like to) #TDD #JUnit5 #Kotlin #Java
#PairProgramming (if you'd like to) #TDD #JUnit5 #Kotlin #Java
This guy, how do I explain? Cognitively and care-fully simpatico, so many shared people and experiences, my once and with luck also future daily #PairProgramming partner. That’s a bit of @msilpala@qoto.org Great to see and squeeze you today, my friend.
I'm a strong proponent of learning with others. Here are two examples from physics and coding of the advantages of cooperative learning.
A pleasant side-effect of #PairProgramming is that it automatically improves the quality of code review and the need to wait for merge request approvals.
Since every line of code in the merge request is the result of negotiation and discussion between two developers, the four-eyes-principle is already satisfied and the merge request can be approved directly.
Without, it would either be rubber-stamped not to cause delays or require quite a lot of time on the reviewer to dive into the details.
As a side-effect of this, I got to experience "AI" coding assistants.
I am staying away from that tech because it is a net-negative societally, environmentally, legally, ethically and all-around, but my coworker is using it (with encouragement from management who are in love with the idea).
So #Copilot pops up in our #PairProgramming sessions.
I have to admit the code and commit message suggestions it makes are surprisingly good. It helps. If you ignore the big picture, it would be tempting.
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst