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.
... remember to keep the licensing registrations up to date!
Being the Sinaloa cartel’s tech guru was not an easy job. Prosecutors played the jury excerpts of a taped phone call where Cristián complains about being scolded for the encrypted network being down.
The irony was that authorities were only able to obtain the call because the men were forced to use conventional cellphones while their secure network was down. Cifuentes called Cristián "an irresponsible person," and said the engineer screwed up by forgetting to renew the license on the software they had purchased.
While the cartel was experiencing technical difficulties, law enforcement was watching — and listening.
Ya know, when I saw that article a week or two ago, I wondered how long it would take someone here to bring it up.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
Where I am working now we are using GIT, like many company before.
But, and this is a first for me, everyone is working on their own branch and, every now and then people make a pull request to develop to be approved by the lead developer.
Of course one should make sure the pull request has no conflict. But since 2 weeks of work from an other developer can drop anytime... despite me merging my branch from develop every morning I am having lots of painful merge conflicts... every few days....
What I wonder:
is it common practice to have every developer working on its own branch instead of the whole team working on a common branch?
Sure, but "private ownership" of the branch doesn't exist -- if the dev moves on to a different feature/product, he'll work on the branch for that, and someone else will take over the branch he'd been working on.
I wanna be a eunuchs developer! Pass me a bread knife!