|
Score ?
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
Bingo!
Your turn tomorrow...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
It's about 20 was a bit of a giveaway
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
I thought it has two faces...
For a native English it may help, but to the others it should be the opposite...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
"Notes"?
I ain't got no signature.
|
|
|
|
|
Does our work stand out here ? (11)
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
It's not "Outstanding", is it?
I ain't got no signature.
|
|
|
|
|
Nope
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
Ok, "CodeProject"?
-- EDIT: Reasoning
Our work -> code
stand out -> project
here -> the definition
I ain't got no signature.
|
|
|
|
|
You are up tomorrow - well done.
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
Tried this? Anybody?
The Camera vendor warns me , this might damage the lens mount (in the body). But a quick googling doesnt hint the same. Anything wrong with this hack folks? I think the vendor guy is saying these just to sell his expensive Macro lenses.
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy.
modified 28-Oct-15 4:14am.
|
|
|
|
|
This hack has been around for decades, I never actually used it but I've never heard of any problems being reported. Reversing rings are widely available.
|
|
|
|
|
The only miss is the lens detection by the body. It can't sync with the reversed lens, so the AF motor cannot be controlled. But that's fine, We'll switch to RN-AF* System. Eyes/fingers & with a bit of motor sound from the mouth, we can exactly make a it up.
*Red-Neck Auto-Focus.
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy.
|
|
|
|
|
I've only heard tales of it not working. But assuming for the moment that humans are rational (lol), it wouldn't be done so much if it really just didn't work at all. Perhaps it's just that there's no reason to talk about non-failure, that would be a non-story after all.
So, does it ever work? Are there success stories?
(I'll read your responses tomorrow)
|
|
|
|
|
|
We're currently doing quite a bit and so far we're faring well!
It's a mix of some offshoring, but also completely outsourced work.
It's not something I'm willing to divulge in a public forum, but in case you're interested just send me an email.
Cheers!
"I had the right to remain silent, but I didn't have the ability!"
Ron White, Comedian
|
|
|
|
|
To use the cliche; if you stay on top of it, it works. At my current company, we have an actual office in India, not just contractors from some company.
Also, if you outsource to the former Eastern block countries, you will likely get very good code.
|
|
|
|
|
What other options do you have?
Even if you contract with a local company they could simply sub-contract it out anywhere*. You might just as well go straight to the lowest bidder and cut out the middlemen.
* I've heard of that happening.
|
|
|
|
|
This looks quite a blunt question. Stats would sum up and give you a blurred data. But if you look closer, on case basis , for sure there are clear winners and clear losers. It depends on two things mainly.
1. Complexity of the work
2. To whom you are outsourcing
#2 is highly critical. As the complexity of the work & duration of the project increases, #2 gets super critical. & The other thing is, you shouldnt transfer the whole in one go. First the non-critical items should go and then gradually the critical ones follow suit.
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy.
|
|
|
|
|
While I only have experience with the disasters I can identify one of the main causes - ownership, as Joe said you need someone to keep on top of the service, you can't just throw money at them and then bitch when you get ripped off, you need to invest some resources and they had better be bloody good at what they do, not the office junior!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
What Joe and Mycroft said.
Outsourcing doesn't have anything to do with it actually.
If you have a competent owner, a proper specification and good communications, it will work no matter whether it's inhouse or outsourced.
If you do inhouse development you will normally have a lot better communications, compensating for the lack in the two other areas.
Also note how a proper specification clashes with agile development.
|
|
|
|
|
Depends on a lot of things:
1) quality of engineering (this can be shockingly bad depending where it is)
2) cultural issues and how negativity is handled
#2 is famously a big issue. Certain cultures dont like to own up to issues and say 'no, it cant be done' or 'we have a major blocking issue'. In the west we can, so while we expect such honesty, we don't always get it, which can make projects fail.
#1 varies a lot. Generally I see good code from eastern Europeans, but these days they just go to work in western Europe, so its not really outsourcing. As for India, well, I have see some monstrous stuff. Really appalling.
|
|
|
|
|
Munchies_Matt wrote: 2) cultural issues and how negativity is handled I have come across this where the word for "yes" and "no" is "yes" - the only difference being in the manner that "yes" is communicated
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
I've worked with offshoring before, the daily cost savings were cancelled out by the increased time take due to things such as language/cultural differences, the requirement for more meetings/travel and so on.
It wasn't a negative experience, it just didn't bring the cost saving gains that the management who implemented it expected.
Plus, everyone was doing it so the costs kept going up as staff kept jumping ship to the next company that did it that paid slightly more and so the wages went up etc.
|
|
|
|
|
As far as my limited experience concerns, I saw that the shorter is the circuit linking request-> design -> code -> test -> release -> adjust request ->... the faster and less costly is delivering a functional product.
Introducing obstacles such as two different chains of command, business agreement and payments ("you changed a so the cost is +50" - "but you misunderstood b so we won't pay those other 30" - "no wait we did not misunderstood let's block until we come to an agreement"...), language barriers, time zone delays and possible lack of domain knowledge on the outsourcing provider enlarges and slows down the circuit, converging to a proper solution slower.
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
"When you have eliminated the JavaScript, whatever remains must be an empty page." -- Mike Hankey
|
|
|
|