
Re: Jenkins?
"This is a bit like saying you've never heard of git. Somewhat invalidates any subsequent claims of competence."
Not really. It mostly invalidates any claim of knowing EVERYTHING. You can survive your entire career without knowing a THING about git. It all depends on whether or not you've ever needed it, or something like it. Some of us just don't need to chase the bleeding edge all of the time, would rather just work with what we have and get stuff done [which makes bosses+clients happy and higher pay scale, usually].
I'd only heard 'Jenkins' mentioned before, and after reading the article, I'll probably look into it more closely. The truth is, I've never needed anything like it. I don't work in large teams [normally could do the work of a relatively large team on my own, heh, by approaching things efficiently and generally being left alone, no meetings, no pairing up, etc.].
Funniest (or saddest) example of this: at a used-to-company, developed initial prototype in 3 weeks for something that was worked on FOR A YEAR by one manager, one senior coder, and one junior coder, with daily closed door meetings, etc. at the frustration of the senior coder. They used my prototype [which I'd maybe spent a weeks' additional time patching and tweeking] to demonstrate the concept to potential customers SEVERAL times, while still working on the "real" version. At the end of that year-long period, they asked me to step in to help them finish up. The junior guy got laid off, and the senior guy and I finished it up and fixed it. Took about a month to fix it, though. Go fig. I think the design concepts being used in the "real" version were flawed and inefficient to code around and that became the biggest problem.
Anyway, "that" happens, too.
[I suspect that Jenkins would make "doing it the wrong way" more efficient?]