The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Have you seen a lot different teams, and team sizes?
I have actually.
I once sat in a cold server room -- part of the punishment -- to do pair-programming under the tutelage of a far superior contractor dev. This was very early on with C# 2001 or so and I did learn some things. But mine was simply to nod my little head and listen to Master-Pair-Programmer so it was easy.
There were over 100 devs at that location -- attempting and failing to rewrite a LOS (Loan Origination System) at a large mortgage bank -- well they only spent $75 million before giving up.
I've also worked with contractors who've written "XML parsers that are faster than microsoft's".
That was the contractor's reasoning when I asked him why he wrote his own when there were perfectly good libraries in .NET.
He had no concept of DOM parsing. His was parsing everything into a string and yes that is faster than DOM parsing. In that case he would've been the Master-Pair-Programmer had I ever had to be paired with him.
I've been part of teams of one and large teams and small teams over the years.
Most of the time in larger corps it is the one with the most political pull who makes the design/code decisions. The other nods his little head.
Small(er)(ish) teams/companies give a bit more autonomy -- and if done properly has oversight and input / code reviews etc. We even work quite closely but pairing would drive me crazy.
Pairing feels more like a short-circuit attempt to fast communication more than anything, because *no one in companies really know how to communicate what they are actually doing with their code.
*an extreme statement that no one knows but basically right.
If this was the demo where one dev pretended to ask for help from his manager then I thought it could be useful on large teams/projects. It wasn't pair programming, but a way to get assistance without sharing a desktop
This one (example) was collaborative (another bingo buzzword) where two devs worked together (aka paired programming).
I'm being a bit jaded about it all because I can see how this could be neat with an experienced dev lending a hand, etc. but it just seems like these dog and pony shows try to push that old "paired-programming" paradigm a lot. Which never seemed to work out like someone hoped it might (Beck).
The days when I could stay up all night and still go to work the next day are long past me.
You'd have to travel 50km to find a corner shop wouldn't you? Let alone a pub or night life.
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004
I think I'm blessed/cursed with the late night thing. I've always been a night bird (since I was a little kid) and still work until 2-3am. But getting up in time for the 11am standup is hard. I need my beauty sleep.
The first sentences were a train wreck. Didn't even take two minutes.
He mentioned Bill Gates and Apple stock. What!?! It didn't even make sense.
Maybe if he had mentioned something about Linux. Maybe that would've been funny/ironic.
«... thank the gods that they have made you superior to those events which they have not placed within your own control, rendered you accountable for that only which is within you own control For what, then, have they made you responsible? For that which is alone in your own power—a right use of things as they appear.» Discourses of Epictetus Book I:12
Last Visit: 31-May-20 22:11 Last Update: 31-May-20 22:11