> Development (full stack), server admin, data center management, DevOps, project management, managing teams, VoIP, routing/switching, training, sales... the list goes on.
I was a 'generalist' for most of my career. I had started, run and sold a successful business that required me to touch all parts of the business.
Until a Sales Director absolutely schooled me in the theory that underpinned his work. He seemed insulted that I claimed to be proficient in sales. It was an insult to his specialism.
I would suggest you really test yourself in one of these areas before claiming you're proficient. I've never met a single person who was proficient in all the above. I've met plenty of people who could trudge along in those areas.
It's technically feasible.. but in my opinion, if it's happened with you then it's very likely to be happening with others.
There's no one single way to setup telco infrastructure, so it would be educated-guesswork in the case of Google Fi.
Worth noting VoIP is real time, it either works or it doesnt. And if a call is being setup between two parties and it's otherwise a good quality call, then monitoring is unlikely to mark it as a bad call.
Personally, I would recommend logging this as a bug (if Google Fi allow it?) as I suspect it will be near impossible for them to spot these scenarios, even with clever monitoring tools.
I'll be keeping an eye on the news for follow ups on this one!
"In India, VoIP is allowed, but only for computer-to-computer communications. India deregulated IP Telephony on 1 April 2002 following the ITUís World Telecommunication Policy Forum held in 2001 on the topic of ì IP Telephonyî. Indiaís proposed unified licence regime, however, would impose no restriction on VoIP telephony or other IP-enabled services, provided they are offered by operators with a unified licence that have duly paid all required registration charges."
..In practice, this means Twilio can terminate a call into India, as long as the route the call takes is via a licensed operator. This is Twilio's problem, not yours. (unless it says otherwise in their terms).
It also means if an individual, physically within India, chooses to make an outbound call, over the Twilio service, then the endpoint has to be another IP-endpoint. Or if to a 'copper cable endpoint', then at least traverse over an appropriate Indian carrier at some point. Probably using some kind of PSTN-IP gateway. Again, Twilio's problem and not yours (unless it says otherwise in their terms).
These complications were introduced to prevent people in India setting up copper cable-IP gateways, taking advantage of cheaper retail call bundles, and selling them cheap on the wholesale market. Naughty!
Personally, I would contact Twilio. They won't be able to give legal advice, but they will at least tell you if they can legally facilitate the requirement.
> as long as the route the call takes is via a licensed operator. This is Twilio's problem, not yours.
I surmised as much. Have not been able to speak to Twilio. But Plivo's reps assure me that compliance is not an issue. But we want to be doubly sure. Do not want to be railroaded by legality somewhere down the line
Something on the back of your car, that using a combination of your speed, the distance between you and the car behind you, an understanding of the weight of both cars (using a lookup on the Reg), and the stopping distance, taking into account weather.. is able to calculate the likelihood that the car will crash into you if you slammed on your breaks
And then display that figure in a big lcd panel in your back window.
Haven’t done it, because every time I remember it, I’m driving my car and forget by time I’m home.
Imagine being challenged at work... in a sales team, for example. Make a sale, get to do a lucky dip. Say two people make an equivalent sale, one wins and the other doesn't. I would personally feel less motivated if I lost.
I wonder if you did it to kids, they would learn to weigh up whether doing any given task was worth some arbitrarily set lost/win.
It's the difference between learning that "washing a car is worth $10 of my time because it will takes x hours and the cost of soap is y and so on" vs "washing a car is 50/50 worth nothing or $10".
Just some food for thought based on some recent experiences.
Sometimes, you'll be taking a job that someone in the team thinks they should have been offered - but didn't for whatever reason (perhaps current management weren't aware... or they simply aren't appropriate skilled...)
These people can also be well respected by others in the team. And winning their respect is therefore particularly important, as they may be the ones to validate you on behalf of others.
You can normally spot them, as they will lean back, fold their arms and keep to themselves (out of frustration). Or act the opposite and be completely outspoken over the top of others.
I would consider that these people do exist, and need to be wooed in a slightly different way. Instead of asking 'what do you want?' perhaps it'd be better to ask 'where do you think the problems are?'.
UUDDLRLRBA
It pops up a cute little rainbow