We agree that some Internet access is better than none, and if that is what Internet.org actually provided—for example, through a uniformly rate-limited or data-capped free service—then it would have our full support. But it doesn’t. Instead, it continues to impose conditions and restraints that not only make it something less than a true Internet service, but also endanger people’s privacy and security.
While we applaud Facebook’s efforts to encourage more websites to provide support for low-end feature phones by stripping out “heavy” content, we would like to see Internet.org try harder to achieve its very worthy objective of connecting the remaining two thirds of the world to the Internet. We have confidence that it would be possible to provide a limited free Internet access service that is secure, and that doesn’t rely on Facebook and its partners to maintain a central list of approved sites. Until then, Internet.org will not be living up to its promise, or its name.
TL;DR key recommendations:
– Once a project is completed, the team must ensure that the “What” and “Why” of each software item are properly documented.
– In the cases of parallel development of inter-dependent software modules set up a negotiation table to solve conflict between the development teams.
– Make sure that the development team is aware of the CMMI-ACQ or ISO12207 processes for negotiating with third parties.
– Make sure that testers are involved when negotiating with a third party for a potentially vulnerable software component. ￼
– Plan organization-wide process reviews to detect isolated processes and to promote information flows between processes.
– Planned special budget items to support long lasting corrections or corrections that are likely to benefit many modules. ￼
– Projects with strict deadlines are risky, and should be carefully monitored to avoid last minute unplanned activities.
– Team members should maintain a careful balance between the flows of information within formal development processes and informal human interactions.
– Team members should make sure that knowledge is appropriately distributed amongst them. For example, pair programming is a practice which can promote knowledge sharing.
– Any intrusion into the team dynamics by outsiders should be done very carefully.
I had to write bad code because sales and management usually dictate the timeline of the project.
As an example: sales promises new customer feature X in one month and we will lose money unless it’s implemented.
My choice is to either: 1) Complete it the right way in double the time or 2) use hacks and cut corners to get it done on time. Since non-technical people just see the output and not what’s going on underneath, they often times don’t see the difference and when they explain to the boss that they might lose money, it’s almost always option #2.
Being kind isn’t the same as being nice. It isn’t about superficial praise. It doesn’t mean dulling your opinions. And it shouldn’t diminish the passion with which you present them.
Being kind is fundamentally about taking responsibility for your impact on the people around you. It requires you be mindful of their feelings and considerate of the way your presence affects them.
Um estudo do MIT compilou dados a partir de milhares de chamadas de vendas B2B. (…) Aqui está o que eles encontraram: o melhor horário para fazer contato com seus prospects é das 16h às 18h. (…) e ainda é 114% melhor do que o pior período do dia (ente às 11h e às 12h). (…) A pesquisa constatou que, as quartas e quintas-feiras são os melhores dias para a prospecção, quase 50% melhor do que o pior dia, a terça-feira.
1. Shut off alerts on your phone.
2. Get organized.
3 .Add estimated times to your to-do list.
4. Implement the 2-minute rule.
5. Make bad habits harder.
6. Work in bursts; take your breaks outside.
7. Designate yourself morale officer.
8. Upgrade your personal presentation.
9. Focus on your long-term goals.