Often the most important part of the news is what they didn't tell.
That isn't a trivial mistake then. How did such mistakes show themselves? Compilation failure? Crashes at runtime? Or incorrect results? That last is of course the most serious.Tim Holloway wrote:. . . days chasing a misplaced comma than . . .
Often the most important part of the news is what they didn't tell.
Are you looking at serious mistakes or trivial mistakes? Is there such a thing as a trivial mistake at all?
Frank Carver wrote:This is where code reviews and pair programming come in.
I've been in academia for a while where, unfortunately, such things are frowned upon as somehow "cheating", but multiple pairs eyes on the code has saved my bacon many times in "the real world" ;)
Often the most important part of the news is what they didn't tell.
They should be teaching that you are taught to program individually, but in the real world most people program in pairs.Frank Carver wrote:. . . I've been in academia . . . such things are frowned upon . . .
Campbell Ritchie wrote:
They should be teaching that you are taught to program individually, but in the real world most people program in pairs.Frank Carver wrote:. . . I've been in academia . . . such things are frowned upon . . .
Often the most important part of the news is what they didn't tell.
...program in pairs.
Tomasz Lelek wrote:
...program in pairs.
It also depends if you are working in a remote-first company or on-site at the office. I am also not a fan of pair programming.
Often the most important part of the news is what they didn't tell.
What made you not a fan? Any specific experience(s) that soured you against it?
Junilu Lacar wrote:The opportunity to teach less experienced or newer developers
Frank Carver wrote:
I have spent most of my career as a contract developer, typically brought in to work on codebases which have grown horrible through years of suboptimal fixes and "improvements". The story is almost always the same. A single hero developer (occasionally a small team) who was always too busy or too secretive to explain why and how. Then the hero moved on to a new project, beginning the decline into a ball of mud.
Often the most important part of the news is what they didn't tell.
Tomasz Lelek wrote:I feel there is a high probability that the person with stronger opinions and character may dominate the pair programming.
Also, I think that everyone learns and processes things at different speed. It's hard to pair two engineers that are processing and coding at a similar rate.
Always look on the bright side of life. At least this ad is really tiny:
Smokeless wood heat with a rocket mass heater
https://woodheat.net
|