tag:blogger.com,1999:blog-58433592718102299772024-03-14T06:14:43.975+00:00TecnicicesCuriosidades técnicas e tecnicices em geral... :)Unknownnoreply@blogger.comBlogger45125tag:blogger.com,1999:blog-5843359271810229977.post-5404594552202397772013-07-29T10:29:00.001+00:002013-07-29T10:29:11.922+00:00Código é poesia?? :)<div dir="ltr" style="text-align: left;" trbidi="on">
Pode escrever código fazer de nós poetas?? :)<br />
<br />
Aqui fica um artigo interessante, que transcrevo, não vá o link ir-se....<br />
<br />
Daqui: <a href="http://www1.folha.uol.com.br/colunas/luliradfahrer/2013/07/1317458-codigo-e-poesia.shtml">http://www1.folha.uol.com.br/colunas/luliradfahrer/2013/07/1317458-codigo-e-poesia.shtml</a><br />
<br />
<b>Código é poesia</b><br />
<br />
A expressão, usada como slogan pela plataforma Wordpress, é controversa. Comparar a nobre arte poética com a técnica da programação parece sacrilégio.<br />
<br />
Código é frio e calculado, precisa ser objetivo, não pode dar margem a interpretações. O que isso tem em comum com a artesania de palavras que compõe um verso?<br />
<br />
A relação entre as duas áreas tem origens medievais. Até o século 12 não se calculava com números na Europa. Para isso existiam os ábacos. Derivados do sistema romano, números eram apenas um tipo de letra usada para registrar quantias.<br />
<br />
A invasão árabe trouxe com ela as descobertas aritméticas dos hindus e persas, entre eles os escritos de Al-Khwarismi. De seu nome vêm os conceitos de algarismo, algoritmo e logaritmo.<br />
<br />
Entre suas invenções está a Álgebra, uma língua composta de pequenas frases e sinais que registra e calcula operações matemáticas. Em frases curtas, sequenciais e de gramática rígida buscava-se descobrir a incógnita, chamada por ele de xay (coisa), que não tardou a se transformar no "x" de tantas questões.<br />
<br />
Algoritmos, como equações algébricas, usam expressões para realizar operações. Sintéticas, essas frases em línguas estranhas (SQL, JavaScript, HTML) têm sintaxe, ortografia e métricas precisas.<br />
<br />
A semelhança entre código e poesia vai além de sintaxe e frases curtas. Ambas têm propósito, sentido e estrutura. Por motivos diferentes, precisam ser elegantes e concisas.<br />
<br />
Bom código, como boa poesia, não "acontece" naturalmente, nem pode ser gerado a partir de dicionários de rimas. Demanda disciplina, talento e trabalho duro.<br />
<br />
Algoritmos bem desenvolvidos, como poesias bem escritas, seguem fluxos naturais de ideias. Tudo neles parece estar no lugar correto, nada pode ser removido, cada linha emenda naturalmente na próxima.<br />
<br />
O fluxo de operações não é determinado pela estrutura gramatical mas pela forma com que cada ideia se conecta à seguinte, complementando a anterior. Linhas de código, como versos, fazem referências cruzadas, em que cada parte amplifica e sintetiza o que a antecedeu.<br />
<br />
Como bem sabe quem já tentou escrever poemas ou algoritmos, a tarefa não é fácil. Licenças poéticas, exceções e desvios acabam sendo usados para contornar problemas, criando emendas que geram trabalhos de péssima qualidade.<br />
<br />
Muitos preguiçosos autointitulados poetas apenas por serem capazes de rimar as palavras no fim de duas linhas se espantam porque ninguém suporta lê-los ou ouvi-los. Dodecassílabos, alexandrinos, heroicos ou redondilhas, poemas precisam de estrutura. Como eles, os haikus e sonetos algorítmicos demandam estruturas e métodos para serem devidamente apreciados.<br />
<br />
Programar websites e aplicativos é complexo, mas não é impossível, nem restrito a mentes brilhantes especiais. Da mesma forma que todos podem escrever, todos podem programar. Com engenho e arte, novos talentos podem fazer o que Chico, Caetano e Gil fizeram com os versos da nossa música.<br />
<br />
Mas só se poderá cultivá-los quando o preconceito que se tem com relação aos desenvolvedores for substituído pela admiração que temos por quem garimpa a beleza oculta na última flor do Lácio.</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5843359271810229977.post-50260864830228875292013-05-24T16:39:00.002+00:002013-05-24T16:39:50.645+00:00SAFs - Scaled Agile Framework<div dir="ltr" style="text-align: left;" trbidi="on">
<span style="background-color: white; color: #666666; font-family: 'helvetica neue', Helvetica, Arial, Verdana, sans-serif; font-size: 14px; line-height: 19px;">The Scaled Agile Framework (pronounced “SAFe”) is an interactive knowledge base for implementing agile practices at enterprise scale. The “Big Picture” graphic highlights the individual roles, teams, activities and artifacts necessary to scale agile from the team to program to the enterprise level. Clicking on each icon takes the user to an Abstract and a Detail page which elaborates on that element. Some elements (like DBT and Metrics) bring up additional sub-domains with navigation to further depth and description.</span><br />
<br />
Interessante...<br />
Tema a explorar:<br />
<a href="http://scaledagileframework.com/">http://scaledagileframework.com/</a></div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5843359271810229977.post-53943140017948190902013-05-24T16:38:00.001+00:002013-05-24T16:38:37.446+00:00HotHousing in Agile<div dir="ltr" style="text-align: left;" trbidi="on">
<span style="background-color: white; color: #4c4c4c; font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 17px;">The term originally came out of England at </span><a href="http://www.methodsandtools.com/archive/archive.php?id=43p2" style="background-color: white; color: #082855; font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 17px; outline: none;">British Telcom</a><span style="background-color: white; color: #4c4c4c; font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 17px;"> as a way to plan out the backlog for a given product. The entire project team and several different disciplines come together with business partners to creatively solve problems and launch into a 90-day development cycle.</span><br />
<br />
Interessante...<br />
<br />
Mais neste artigo:<br />
<a href="http://blogs.captechconsulting.com/blog/margaret-thomas/hothousing-new-concept-or-new-word?goback=%2Egde_81065_member_241843457">http://blogs.captechconsulting.com/blog/margaret-thomas/hothousing-new-concept-or-new-word?goback=%2Egde_81065_member_241843457</a><br />
<br />
<br /></div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5843359271810229977.post-10124172565140189082013-05-24T12:32:00.000+00:002013-05-24T12:32:47.875+00:00AGILE - Reuniões de retrospective<div dir="ltr" style="text-align: left;" trbidi="on">
Muitas vezes entramos em debates intermináveis nas reuniões de retrospectiva, no final do Sprint, sobre temas que não são importantes para a equipa.<br />
Embora seja fundamental haver abertura para as pessoas falarem do que acham importante, do que pode ser melhorado, até da sua visão sobre as questões abordadas, não é útil perder de vista o objectivo da reunião, que é identificar o que correu bem e reforçá-lo, e identificar o que correu mal e melhorá-lo.<br />
E nao nos perdermos em discussoes subjectivas sobre se a opinião do outro é mais certa ou errada do que a minha.<br />
É importante identificar pontos de melhoria e pensar em acções concretas e práticas para as mitigar.<br />
<br />
Deixo uma frase interessante e bastante ilustrativa :)<br />
Five frogs are sitting on a log. Four decide to jump off. How many are left?
Five, because deciding is different than doing.” Decisions are worthless …
unless you turn them into commitments.<br />
<br />
<a href="http://www.linkedin.com/today/post/article/20130520005409-36052017-are-you-making-this-mistake-at-the-end-of-your-meetings?goback=%2Egde_81065_member_242848818">http://www.linkedin.com/today/post/article/20130520005409-36052017-are-you-making-this-mistake-at-the-end-of-your-meetings?goback=%2Egde_81065_member_242848818</a><br />
<br /></div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5843359271810229977.post-5942515553436223712013-05-24T10:25:00.003+00:002013-05-27T08:55:55.708+00:00AGILE - Partir User Stories<div dir="ltr" style="text-align: left;" trbidi="on">
Pequena dica para partir User Stories demasiado grandes, num Road Map elucidativo e ilustrativo :)<br />
<br />
<span class="comment-body" data-li-comment-text=""><a href="http://www.linkedin.com/redirect?url=http%3A%2F%2Frslawrence%2Ewpengine%2Ecom%2Fwp-content%2Fuploads%2F2012%2F01%2FStory-Splitting-Flowchart%2Epdf&urlhash=F6r0&_t=tracking_disc" target="_blank">http://rslawrence.wpengine.com/wp-content/uploads/2012/01/Story-Splitting-Flowchart.pdf</a>
</span><br />
<br />
Mais alguns artigos sore como partir User Stories:<br />
<a href="http://blog.gdinwiddie.com/2011/05/01/splitting-user-stories/">http://blog.gdinwiddie.com/2011/05/01/splitting-user-stories/</a><br />
<a href="http://www.richardlawrence.info/2009/10/28/patterns-for-splitting-user-stories/">http://www.richardlawrence.info/2009/10/28/patterns-for-splitting-user-stories/</a><br />
<a href="http://www.infoq.com/news/2011/04/how-to-split-user-stories">http://www.infoq.com/news/2011/04/how-to-split-user-stories</a></div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5843359271810229977.post-62709249237040405312010-01-04T15:25:00.002+00:002010-01-04T15:26:47.383+00:00Agile, Scrum - A Christmas Retrospective :))))<div style="text-align: center;font-family:verdana;"><span style="font-size:85%;"><span style="color: rgb(0, 102, 0); font-style: italic;">‘Twas the night before Christmas</span><br /><span style="color: rgb(0, 102, 0); font-style: italic;">And Santa was busy</span><br /><span style="color: rgb(0, 102, 0); font-style: italic;">Trying to understand</span><br /><span style="color: rgb(0, 102, 0); font-style: italic;">Why things got so crazy</span><br /><br /><span style="color: rgb(0, 102, 0); font-style: italic;">But the plan was perfect</span><br /><span style="color: rgb(0, 102, 0); font-style: italic;">Created by experts</span><br /><span style="color: rgb(0, 102, 0); font-style: italic;">But the elves on the floor</span><br /><span style="color: rgb(0, 102, 0); font-style: italic;">Knew so much more</span><br /><br /><span style="color: rgb(0, 102, 0); font-style: italic;">What if they’d Scrumed it</span><br /><span style="color: rgb(0, 102, 0); font-style: italic;">Santa as P.O.</span><br /><span style="color: rgb(0, 102, 0); font-style: italic;">Maybe a burndown</span><br /><span style="color: rgb(0, 102, 0); font-style: italic;">And of course a retro</span><br /><br /><span style="color: rgb(0, 102, 0); font-style: italic;">Sprint 0 in March</span><br /><span style="color: rgb(0, 102, 0); font-style: italic;">And a start in April</span><br /><span style="color: rgb(0, 102, 0); font-style: italic;">A review every month</span><br /><span style="color: rgb(0, 102, 0); font-style: italic;">And see if we’re able</span><br /><br /><span style="color: rgb(0, 102, 0); font-style: italic;">But Agile it wasn’t</span><br /><span style="color: rgb(0, 102, 0); font-style: italic;">And waterfall it was</span><br /><span style="color: rgb(0, 102, 0); font-style: italic;">Santa found out too late</span><br /><span style="color: rgb(0, 102, 0); font-style: italic;">That he wouldn’t make the date</span><br /><br /><span style="color: rgb(0, 102, 0); font-style: italic;">Next Christmas will be different</span><br /><span style="color: rgb(0, 102, 0); font-style: italic;">It will be in December</span><br /><span style="color: rgb(0, 102, 0); font-style: italic;">And we won’t have to wait</span><br /><span style="color: rgb(0, 102, 0); font-style: italic;">For our toys in September</span><br /><br /><span style="color: rgb(0, 102, 0); font-style: italic;">Merry Christmas! ;)</span><br /><br /><span style="font-weight: bold;">Source: </span>don't remember :S but comes from a LinkedIn Group...</span></div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5843359271810229977.post-73372867647636496892009-12-04T15:11:00.002+00:002010-01-05T16:15:15.744+00:00Scrum Poker (ou Poker Planning)<span style="font-size:85%;"><span style="font-family:verdana;">Artigo bastante elucidativo, de uma forma divertida :), sobre Poker Planning, metodologia proposta por Mike Cohn, para calcular estimativas para a duração das stories.</span><br /><br /><a style="font-family: verdana;" href="http://www.crisp.se/planningpoker">http://www.crisp.se/planningpoker</a><br /><br /><span style="font-family:verdana;">Have fun :o)</span></span>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5843359271810229977.post-87287915578541407002009-11-26T11:54:00.003+00:002009-11-26T11:59:11.975+00:00What Do Actors and Programmers Have in Common?<span style=";font-family:trebuchet ms;font-size:85%;" >Artigo interessante sobre metodologias (estrategias?) partilhadas por estes dois grupos, aparentemente tão distintos :)<br /><br /><span style="color: rgb(102, 0, 0);">[…]</span><br /><span style="color: rgb(102, 0, 0);">So, what do actors and programmers have in common?</span><br /><span style="color: rgb(102, 0, 0);">Well, some amazingly fundamental things as it turns out:</span><br /><br /><span style="color: rgb(102, 0, 0);"> * Iterative work</span><br /><span style="color: rgb(102, 0, 0);"> * Collaboration</span><br /><span style="color: rgb(102, 0, 0);"> * Innovation</span><br /><br /><span style="color: rgb(102, 0, 0);">Theatre work and product development both thrive on iteration and collaboration. Lee described this in terms of rehearsal and the emergent look of a play leading up to and even after opening night. Rob affirmed the value of a collaborative and iterative approach in product development[…]</span><br /><br />Mais aqui:<a href="http://www.rallydev.com/agileblog/2009/11/what-do-actors-and-programmers-have-in-common/"> http://www.rallydev.com/agileblog/2009/11/what-do-actors-and-programmers-have-in-common/</a></span>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5843359271810229977.post-27163875111029596132009-11-17T18:54:00.001+00:002009-11-17T18:56:23.904+00:00How to implement Scrum in 10 easy steps :)<span style="font-size:85%;"><span style="font-family: trebuchet ms;">Artigo que propõe uma metodologia para aplicar a metodologia :)</span><br /><span style="font-family: trebuchet ms;">Scrum, entenda-se :))</span><br /><br /><span style="font-family: trebuchet ms;">Daqui: </span><a style="font-family: trebuchet ms;" href="http://www.agile-software-development.com/2007/09/how-to-implement-scrum-in-10-easy-steps.html">http://www.agile-software-development.com/2007/09/how-to-implement-scrum-in-10-easy-steps.html</a><br /><br /><span style="font-family: trebuchet ms;">- Step #1: Get your backlog in order!</span><br /><span style="font-family: trebuchet ms;">- Step #2: How to estimate your product backlog</span><br /><span style="font-family: trebuchet ms;">- Step #3: Sprint Planning/clarify requirements</span><br /><span style="font-family: trebuchet ms;">- Step #4: Sprint Planning/estimate tasks</span><br /><span style="font-family: trebuchet ms;">- Step #5: Create a collaborative workspace</span><br /><span style="font-family: trebuchet ms;">- Step #6: Sprint!</span><br /><span style="font-family: trebuchet ms;">- Step #7: Stand up and be counted!</span><br /><span style="font-family: trebuchet ms;">- Step #8: Track progress with a daily burndown chart</span><br /><span style="font-family: trebuchet ms;">- Step #9: Finish when you said you would</span><br /><span style="font-family: trebuchet ms;">- Step #10: Review, reflect, repeat...</span><br /><br /></span>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5843359271810229977.post-42388628894394814932009-11-17T18:36:00.003+00:002009-11-17T18:49:19.509+00:00Pragmatic Agile Development (PAD)<span style="font-size:85%;"><span style="font-family:trebuchet ms;">Interessante.</span><br /><span style="font-family:trebuchet ms;">Uma abordagem a metodologias ageis, baseada em Scrum, mas com algumas alterações.</span><br /><br /><span style="font-family:trebuchet ms;">Aqui fica um pequeno resumo.</span><br /><br /><span style="color: rgb(0, 0, 153); font-style: italic;"><span style="font-family:trebuchet ms;">Pragmatic Agile Development (PAD) and Agile Scrum</span><br /><br /><span style="font-family:trebuchet ms;">It is important to note that the way we use Agile Scrum varies from a purist version of Scrum as we have made modifications to Agile Scrum to work well for our development environment. Our version of Scrum is called Pragmatic Agile Development (PAD) and differs from a more purist Scrum implementation in these ways:</span><br /><br /><span style="font-family:trebuchet ms;"> 1. Scrum Planning - In Scrum, planning for an upcoming sprint is accomplished in 1 day, in PAD the planning spans 1 week. This is because we write more detailed specifications than a purist Scrum does (see next bullet item).</span><br /><span style="font-family:trebuchet ms;"> 2. User Stories vs. Specifications - In Scrum, requirements are written on index cards (called User Stories) and does not contain prototypes or detailed explanations of the feature set. In PAD, we spend time detailing the requirement specifications with prototypes to ensure that time is well spent on the feature, reducing rework.</span><br /><span style="font-family:trebuchet ms;"> 3. 30 Day Sprints - In Scrum, development is done in 30 calendar days. In PAD, development is done in 30 working days, skipping holidays. This provides us with more evenly distributed sprints.</span><br /><span style="font-family:trebuchet ms;"> 4. Team Composition - In Scrum, developers are expected to perform all duties (analysis, design, coding, test case development, execution, and documentation). In PAD, developers help with analysis and design and perform all the coding. We have specialized team members (Software Quality Engineers) for test case development and specialized team members for documentation. We do this because our experience has shown that we need specialists in these areas.</span></span><br /><br /><span style="font-family:trebuchet ms;">E o link: </span><a style="font-family: trebuchet ms;" href="http://softwareplanner.com/Newsletters/newsletter_2008_05_SP.htm">http://softwareplanner.com/Newsletters/newsletter_2008_05_SP.htm</a><br /></span>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5843359271810229977.post-26093690073212682102009-11-12T16:21:00.007+00:002009-11-12T16:41:03.495+00:00KISS! :)<div style="text-align: left;font-family:trebuchet ms;"><span style="font-size:85%;"><span style="font-weight: bold;font-size:130%;" >KISS. Keep IT Simple Stupid.</span><br /><br /></span><span style="font-size:85%;"><span style="font-weight: bold;">Manter o SCRUM simples, nao complicar.</span><br /><span style="font-weight: bold;">O que quer dizer isto??</span><br /><br /><span style="font-weight: bold;">Manter as stories simples.</span><br /><span style="font-weight: bold;">Manter a Review/Planning Meetings simples.</span><br /><span style="font-weight: bold;">Etc, etc, etc...</span><br /></span><span style="font-weight: bold;font-size:85%;" >Simplicidade. </span><span style="font-weight: bold;font-size:85%;" >Simplicidade. </span><span style="font-size:85%;"><span style="font-weight: bold;">Simplicidade.</span><br /><br /><span style="font-weight: bold;">A NAO ESQUECER!! :))</span><br /><br /><span style="font-weight: bold;">Artigos interessantes sobre KISS e SCRUM :)</span><br /><br /><a style="font-weight: bold;" href="http://pt.wikipedia.org/wiki/Keep_It_Simple">http://pt.wikipedia.org/wiki/Keep_It_Simple</a><br /><a style="font-weight: bold;" href="http://diego-pacheco.blogspot.com/2009/04/o-melhor-do-xp.html">http://diego-pacheco.blogspot.com/2009/04/o-melhor-do-xp.html</a><br /><a style="font-weight: bold;" href="http://www.techcrunch.com/2009/04/28/keep-it-simple-stupid/">http://www.techcrunch.com/2009/04/28/keep-it-simple-stupid/</a><br /><a style="font-weight: bold;" href="http://rafaelspereira.wordpress.com/2008/04/13/keep-it-simple/">http://rafaelspereira.wordpress.com/2008/04/13/keep-it-simple/</a><br /><a style="font-weight: bold;" href="http://blog.lppjunior.com/planejamento-de-software-keep-it-simple-stupid/">http://blog.lppjunior.com/planejamento-de-software-keep-it-simple-stupid/</a><br /><br /><a style="font-weight: bold;" href="http://pt.wikipedia.org/wiki/YAGNI">E ainda, YAGNI :)</a><br /><br /></span><span style="font-size:85%;"><span style="font-style: italic; color: rgb(0, 102, 0);">Tudo deve ser feito da forma mais simples possível, mas não mais simples que isso.</span><br /><span style="color: rgb(0, 102, 0);">Albert Einstein</span><br /><br /><span style="font-style: italic; color: rgb(0, 102, 0);">A perfeição é alcançada não quando não há mais nada para adicionar,</span><br /><span style="font-style: italic; color: rgb(0, 102, 0);">mas quando não há mais nada que se possa retirar.</span><br /><span style="color: rgb(0, 102, 0);">Antoine de Saint-Exupéry</span><br /><br /><span style="font-style: italic; color: rgb(0, 102, 0);">A simplicidade é a ultima sofisticação.</span><br /></span><span style="color: rgb(0, 102, 0);font-size:85%;" >Leonardo Da Vinci</span><br /><span style="font-size:85%;"><br />:)</span><br /></div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5843359271810229977.post-52570045860233478122009-10-22T10:40:00.002+00:002009-12-04T15:17:09.560+00:00SCRUM User Stories<span style="font-size:85%;"><span style="font-family:verdana;">In Scrum, work is expressed in the </span><a style="font-family: verdana;" href="http://scrummethodology.com/the-scrum-backlog/" target="_self">backlog</a><span style="font-family:verdana;"> as user stories. A team may write its user stories in a number of ways as long as they are written from the perspective of the end user. Put another way, team members are encouraged to think of their work from the perspective of who will use it (hence “user” story). A team can express a story as a noun (i.e. “text message” on a cell phone project) or a sentence or phrase (i.e. “debug GPS tracking system”).</span></span> <p style="font-family:verdana;"><span style="font-size:85%;">Many <a href="http://scrummethodology.com/the-scrum-team-role/" target="_self">Scrum teams</a> have adopted the user story template developed by Mike Cohn, which identifies who the end user is, what the end user wants, and why in a single sentence. This model of the user story is most often written like this: <span style="font-weight: bold; color: rgb(153, 0, 0);">“As a [end user role], I want [the desire] so that [the rationale]."</span></span></p> <p style="color: rgb(153, 0, 0);font-family:verdana;"><span style="font-size:85%;">To illustrate, consider how a developer working on a calculator application for a PC might express his work. First, the developer would want to identify who will benefit from this appication: a PC user. Second, he would want to decide what the PC user will want to get out of it: a convenient, prepackaged calculator application. Third, he would want to be able to explain why it’s important for the PC user to have this application. This piece of information is the most open to interpretation, but one can safely assume that the PC user would want to use it to add, subtract, multiply, and divide. Thus the developer’s user story could read something like the following: “As a PC user, I want a calculator with basic functionality on my PC so that I can conveniently perform basic mathematic operations.”</span></p> <p style="font-family:verdana;"><span style="font-size:85%;">In summary, user stories document requirements with particular attention to the end user’s point of view. Stories can be written in myriad ways, but Cohn’s model really works in Scrum because it provides so much information about the story. Because user stories are oriented to reflect the desires of the end user, they help developers remain focused on the customer.</span></p><span style="font-size:85%;"><span style="font-family:verdana;">Daqui: </span><a style="font-family: verdana;" href="http://scrummethodology.com/scrum-user-stories/">http://scrummethodology.com/scrum-user-stories/</a><br /><br /></span>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5843359271810229977.post-92224892859615254392009-10-22T10:32:00.003+00:002009-10-22T10:33:46.829+00:00SCRUM Ceremonies - Detalhes<p style="font-family:verdana;"><span style="font-size:85%;"> Scrum has three ceremonies: Sprint Planning, Sprint Review, and the Daily Scrum Meeting. </span></p> <h2 style="font-family:verdana;"><span style="font-size:85%;">Sprint Planning Meeting</span></h2> <p style="font-family:verdana;"><span style="font-size:85%;"> Preparation for a Scrum sprint begins when the Product Owner develops a plan for a product or a project. The Product Owner can be a customer representative or a customer proxy. For product companies, the customer is a market, and the Product Owner serves as a proxy for the market. A Product Owner needs a vision for the product that frames its ultimate purpose, a business plan that shows what revenue streams can be anticipated from the product in which timeframes, and a road map that plans out several releases, with features ordered by contribution to return on investment (ROI). S/he prepares a list of customer requirements prioritized by business value. This list is the <a href="http://www.scrumalliance.org/view/scrum_artifacts">Product Backlog</a> , a single list of features prioritized by value delivered to the customer. </span></p> <p style="font-family:verdana;"><span style="font-size:85%;"> The Scrum begins when enough of the Product Backlog is defined and prioritized to launch the first thirty-day sprint. A Sprint Planning Meeting is used to develop a detailed plan for the iteration. It begins with the Product Owner reviewing the vision, the roadmap, the release plan, and the Product Backlog with the Scrum team. The team reviews the estimates for features on the Product Backlog and confirms that they are as accurate as possible. The team decides how much work it can successfully take into the sprint based on team size, available hours, and level of team productivity. It is important that the team "pull" items from the top of the Product Backlog that they can commit to deliver in a thirty-day sprint. Pull systems have been show to deliver significant productivity gains in lean product development. </span></p> <p style="font-family:verdana;"><span style="font-size:85%;"> When the Scrum team has selected and committed to deliver a set of top priority features from the Product Backlog, the ScrumMaster leads the team in a planning session to break down Product Backlogs features into sprint tasks. These are the specific development activities required to implement a feature and form the Sprint Backlog. This phase of the Sprint Planning Meeting is time-boxed to a maximum of four hours. </span></p> <h2 style="font-family:verdana;"><span style="font-size:85%;">Daily Scrum Meeting</span></h2> <p style="font-family:verdana;"><span style="font-size:85%;"> Once planning is complete, the Sprint begins its thirty-day cycle. Each day the ScrumMaster leads the team in the Daily Scrum Meeting. This is a fifteen-minute meeting designed to clarify the state of the Scrum. Each team member speaks to three questions: what did I do yesterday, what did I do today, and what impediments got in my way? While anyone can attend this meeting, only team members who have committed to deliver work to the Scrum are allowed to speak. The goal is to get a global snapshot of the project, discover any new dependencies, address any personal needs of committed individuals, and adjust the work plan in real time to the needs of the day. </span></p> <h2 style="font-family:verdana;"><span style="font-size:85%;">Sprint Review Meeting</span></h2> <p style="font-family:verdana;"><span style="font-size:85%;"> At the end of a sprint, a Sprint Review Meeting is held. This meeting is time-boxed to a maximum of four hours. The first half of the meeting is set aside to demonstrate to the Product Owner the potentially shippable code that has been developed during the sprint. The Product Owner leads this part of the meeting and invites all interested stakeholders to attend. The state of the business, the market, and the technology are reviewed. The Product Owner determines which items on the Product Backlog have been completed in the Sprint, and discusses with the Scrum team and stakeholders how best to reprioritize the Product Backlog for the next sprint. The goal for the next sprint is defined. </span></p> <p style="font-family:verdana;"><span style="font-size:85%;"> The second half of the Sprint Review Meeting is a retrospective for the Scrum team that is led by the ScrumMaster. The team assesses the way they worked together in the sprint and identifies positive ways of working together that can be encouraged as future practice. the team also identifies the things that could work better and develops strategies for improvement. </span></p> <p style="font-family:verdana;"><span style="font-size:85%;"> After the Scrum Review Meeting, the process begins again. Iterations proceed until enough features have been done to complete or release a product. </span></p><span style="font-size:85%;"><span style="font-family:verdana;">Daqui: <a href="http://www.scrumalliance.org/pages/scrum_ceremonies"><span style="text-decoration: underline;">http://www.scrumalliance.org/pages/scrum_ceremonies</span></a></span><a style="font-family: verdana;" href="http://www.scrumalliance.org/pages/scrum_roles"></a><br /></span>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5843359271810229977.post-2261896163397272052009-10-22T10:32:00.002+00:002009-10-22T10:33:21.782+00:00SCRM Artifacts - Detalhes<p style="font-family: verdana;"><span style="font-size:85%;"> Scrum has three artifacts: the Product Backlog, the Sprint Backlog, and a Burndown Chart. </span></p> <h2 style="font-family: verdana;"><span style="font-size:85%;">Product Backlog</span></h2> <p style="font-family: verdana;"><span style="font-size:85%;"> At the beginning of the project, the product owner prepares a list of customer requirements prioritized by business value. This list is the Product Backlog, a single list of features prioritized by value delivered to the customer. The Scrum Team contributes to the product backlog by estimating the cost of developing features. </span></p> <p style="font-family: verdana;"><span style="font-size:85%;"> The Product Backlog should include all features visible to the customer, as well as the technical requirements needed to build the product. The highest priority items in the Product Backlog need to be broken down into small enough chunks to be estimable and testable. About ten developer-days of work is a good size for a Product Backlog item that can be ready for implementation in the next iteration. Features that will be implemented further out in time can be less detailed. </span></p> <h2 style="font-family: verdana;"><span style="font-size:85%;">Sprint Backlog</span></h2> <p style="font-family: verdana;"><span style="font-size:85%;"> The Sprint Backlog is an artifact of the Sprint Planning Meeting. When the Scrum Team has selected and committed to deliver a set of top priority features from the Product Backlog, the Product Backlog's features are broken down into a Sprint Backlog: a list of the specific development tasks required to implement a feature. These tasks are broken down into pieces that will require less than two days (or sixteen developer-hours) of work. When the Sprint Backlog is complete, the total work estimated is compared with original estimates from the Product Backlog. If there is a significant difference, the team negotiates with the Product Owner to get the right amount of work to take into the Sprint with a high probability of success. </span></p> <h2 style="font-family: verdana;"><span style="font-size:85%;">Burndown Chart</span></h2> <p style="font-family: verdana;"><span style="font-size:85%;"> The Burndown Chart shows the cumulative work remaining in a Sprint, day-by-day. </span></p> <p style="font-family: verdana;"><span style="font-size:85%;"> At the Sprint Planning Meeting the Scrum Team identifies and estimates specific tasks that must be completed for the Sprint to be successful. The total of all Sprint Backlog estimates of work remaining to be completed is the cumulative backlog. When tasks are completed as the Sprint proceeds, the ScrumMaster recalculates the remaining work to be done and the Sprint Backlog decreases, or burns down over time. If the cumulative Sprint Backlog is zero at the end of the Sprint, the Sprint is successful. </span></p> <p style="font-family: verdana;"><span style="font-size:85%;"> The Product Backlog items brought into the Sprint are fixed for the duration of the Sprint. However, the Sprint Backlog may change for several reasons: </span></p> <ul style="font-family: verdana;"><li><span style="font-size:85%;">The development team gains a better understanding of work to be done as time progresses and may find that they need to add new tasks to the Sprint Backlog to complete the Product Backlog items selected. </span></li><li><span style="font-size:85%;">Defects may be identified and logged as additional tasks. While these are viewed primarily as unfinished work on committed tasks, it may be necessary to keep track of them separately. </span></li><li><span style="font-size:85%;">The Product Owner may work with the team during the Sprint to help refine team understanding of the Sprint goal. The ScrumMaster and Team may decide that minor adjustments that do not lengthen the Sprint are appropriate to optimize customer value. </span></li></ul> <p style="font-family: verdana;"><span style="font-size:85%;"> The Burndown Chart is used as a tool to guide the development team to successful completion of a Sprint on time with working code that is potentially shippable as a product.<br /></span></p><p style="font-family: verdana;"><span style="font-size:85%;">Daqui: <a href="http://www.scrumalliance.org/pages/scrum_artifacts">http://www.scrumalliance.org/pages/scrum_artifacts</a><br /></span></p>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5843359271810229977.post-1917893910493862922009-10-22T10:31:00.001+00:002009-10-22T10:31:58.993+00:00SCRUM Roles - Detalhes<p style="font-family: verdana;"><span style="font-size:85%;"> Scrum has three roles: Product Owner, ScrumMaster, and Team. </span></p> <p style="font-family: verdana;"><span style="font-size:85%;"> The <strong>Product Owner</strong> has the following responsibilities. </span></p> <ul style="font-family: verdana;"><li><span style="font-size:85%;">Define the features of the product; </span></li><li><span style="font-size:85%;">Decide on release date and content; </span></li><li><span style="font-size:85%;">Be responsible for the profitability of the product (ROI); </span></li><li><span style="font-size:85%;">Prioritize features according to market value; </span></li><li><span style="font-size:85%;">Adjust features and priority every 30 days, as needed; and </span></li><li><span style="font-size:85%;">Accept or reject work results.</span></li></ul> <p style="font-family: verdana;"><span style="font-size:85%;"> The product owner is responsible for the first of the three Scrum <a href="http://www.scrumalliance.org/view/scrum_ceremonies">ceremonies</a> : Scrum Planning. </span></p> <p style="font-family: verdana;"><span style="font-size:85%;"> The <strong>ScrumMaster</strong> is a facilitative team leader working closing with the Product Owner. He must: </span></p> <ul style="font-family: verdana;"><li><span style="font-size:85%;">Ensure that the team is fully functional and productive; </span></li><li><span style="font-size:85%;">Enable close cooperation across all roles and functions; </span></li><li><span style="font-size:85%;">Remove barriers; </span></li><li><span style="font-size:85%;">Shield the team from external interferences; and </span></li><li><span style="font-size:85%;">Ensure that the process is followed, including issuing invitations to Daily Scrum, Sprint Review and Sprint Planning meetings.</span></li></ul> <p style="font-family: verdana;"><span style="font-size:85%;"> The ScrumMaster has three primary responsibilities in addition to leading the Daily Scrum meeting: </span></p> <ol style="font-family: verdana;"><li><span style="font-size:85%;">The ScrumMaster needs to know what tasks have been completed, what tasks have started, any new tasks that have been discovered, and any estimates that may have changed. This makes it possible to update the Burndown Chart which shows the cumulative work remaining day by day. The ScrumMaster must also look carefully at the number of open tasks in progress. Work in progress needs to be minimized to achieve lean productivity gains. </span></li><li><span style="font-size:85%;">The ScrumMaster needs to surface dependencies and blocks which are impediments to the Scrum. They need to be prioritized and tracked. A remediation plan needs to be implemented for impediments in priority order. Some can be resolved with the team, some can be resolved across teams, and others will need management involvement as they may be company issues that block all teams from achieving their production capacity. For example, a telecom company recently implemented Scrum and found eighteen items on their impediment list, only two of which were directly related to Scrum teams. The others were company issues that needed management attention. </span></li><li><span style="font-size:85%;">Last but not least, the ScrumMaster may notice personal problems or conflicts within the Scrum that need resolution. These need to be clarified by the ScrumMaster and be resolved by dialogue within the team, or the ScrumMaster may need help from management or the Human Resources. Certified ScrumMaster James Coplien developed over 200 case studies of notable projects while working at ATT Bell Labs. He reports that over 50% of productivity losses were caused by personnel issues. The ScrumMaster must pay attention to them to ensure the team is fully functional and productive.</span></li></ol> <p style="font-family: verdana;"><span style="font-size:85%;"> The <strong>Team</strong>: </span></p> <ul style="font-family: verdana;"><li><span style="font-size:85%;">Is cross-functional, with seven (plus/minus two) members; </span></li><li><span style="font-size:85%;">Selects the Sprint goal and specifies work results; </span></li><li><span style="font-size:85%;">Has the right to do everything within the boundaries of the project guidelines to reach the Sprint goal; </span></li><li><span style="font-size:85%;">Organizes itself and its work; and </span></li><li><span style="font-size:85%;">Demos work results to the Product Owner.</span></li></ul><span style="font-size:85%;"><span style="font-family: verdana;">Daqui: </span><a style="font-family: verdana;" href="http://www.scrumalliance.org/pages/scrum_roles">http://www.scrumalliance.org/pages/scrum_roles</a><br /></span>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5843359271810229977.post-62431624403347560612009-10-22T10:28:00.003+00:002009-10-22T10:31:17.683+00:00SCRUM!! (Let's go agile... ;))<span style="font-family: verdana;font-size:85%;" >Aqui ficam alguns conceitos gerais sobre SCRUM, à laia de nota...<br /><br /></span><span style="font-size:85%;"><span style="font-family: verdana;">Scrum is a "lean" approach to software development. The term Scrum comes from a 1986 study [1] by Takeuchi and Nonaka that was published in the </span><em style="font-family: verdana;">Harvard Business Review.</em><span style="font-family: verdana;"> In that study, Takeuchi and Nonaka note that projects using small, cross-functional teams historically produce the best results.</span><br /></span><p style="font-family: verdana;"><span style="font-size:85%;"> Scrum is a simple "inspect and adapt" framework that has three roles, three ceremonies, and three artifacts [1] designed to deliver working software in Sprints, usually 30-day iterations. </span></p> <ul style="font-family: verdana;"><li> <span style="font-size:85%;"><span style="font-weight: bold;">Roles:</span> Product Owner, ScrumMaster, Team; </span></li><li><span style="font-size:85%;"><strong> <a href="http://www.scrumalliance.org/view/scrum_ceremonies"></a></strong><span style="font-weight: bold;">Ceremonies:</span> Sprint Planning, Sprint Review, and Daily Scrum Meeting; </span></li><li><span style="font-size:85%;"><strong> <a href="http://www.scrumalliance.org/view/scrum_artifacts"></a></strong><span style="font-weight: bold;">Artifacts:</span> Product Backlog, Sprint Backlog, and Burndown Chart</span></li></ul><span style="font-size:85%;"><span style="font-family: verdana;">Daqui: </span><a style="font-family: verdana;" href="http://www.scrumalliance.org/">http://www.scrumalliance.org/</a><br /></span>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5843359271810229977.post-50142676712169464072009-09-18T15:32:00.001+00:002009-09-18T15:32:53.712+00:00InteroperabilidadeArtigo interessante sobre a Interoperabilidade em geral....<br /><br /><a href="http://imasters.uol.com.br/artigo/14307/webservices/interoperabilidade_na_pratica/">http://imasters.uol.com.br/artigo/14307/webservices/interoperabilidade_na_pratica/</a>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5843359271810229977.post-61295314184906367762009-07-01T13:20:00.008+00:002009-07-02T15:50:24.553+00:00GIS Data Integration Articles<a href="http://www.directionsmag.com/article.php?article_id=2298">http://www.directionsmag.com/article.php?article_id=2298</a><br /><a href="http://www.amerisurv.com/content/view/6269/153/">http://www.amerisurv.com/content/view/6269/153/</a><br /><a href="http://www.amerisurv.com/PDF/TheAmericanSurveyor_Zimmer-PLSSandGCDB_June2009.pdf">http://www.amerisurv.com/PDF/TheAmericanSurveyor_Zimmer-PLSSandGCDB_June2009.pdf</a><br /><br /><a href="http://free-gis-data.blogspot.com/">http://free-gis-data.blogspot.com/</a> --> interessante, com muita informação a explorar!!!!!!<br /><br /><a href="http://www.opengeospatial.org/">http://www.opengeospatial.org/</a> --> ESSENCIAL!!! Ver normas / standards!!<br /><br /><a href="http://gisweek.wordpress.com/">http://gisweek.wordpress.com/</a> --> Para publicar um artigo (pode ser um draft do artigo cientifico)<br /><br /><a href="http://tinyurl.com/284v2m">http://tinyurl.com/284v2m</a> --> NORMALIZAÇÃO ISO!!!!!!Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5843359271810229977.post-46573215638702318582009-02-06T12:28:00.006+00:002009-02-20T11:56:16.974+00:00Sharding??<span style=";font-family:verdana;font-size:78%;" >Deparei-me com o termo <span style="font-style: italic;">Sharding </span>recentemente...<br /><br /></span><span style=";font-family:verdana;font-size:78%;" >O termo foi designado e difundido pela equipa do Google.</span><span style=";font-family:verdana;font-size:78%;" > É um termo </span><span style=";font-family:verdana;font-size:78%;" >vistoso :), mas quando percebi o que era confesso que a surpresa e uma pequenita risada se apoderou de mim... :o)<br /><br />Trata-de de um novo nome para o particionamento de Bases de Dados, conceito que já existe há uns bons anos...<br />Confesso que achei piada!! :))<br /><br />Há no entanto quem defenda que não são exactamente a mesma coisa:<br /><br />"</span><span style="color: rgb(153, 153, 153);font-family:verdana;font-size:78%;" >The difference between partitioning and sharding is that sharding applies specifically to the technique of horizontal partitioning, whereas partitioning itself could be either horizontal or vertical. The term sharding is slightly more specific. The tech industry is full of nomenclature like this. It's important that we define it as doing so helps us to communicate better, even if we just decide that two terms are in fact the same.</span><span style=";font-family:verdana;font-size:78%;" >" {[2] - Comments}<br /><br />Fica a discutibilidade da coisa ao critério do leitor, e aqui ficam também dois artigos interessantes sobre o conceito de <span style="font-style: italic;">Sharding</span>, um sobre as vantagens, desvantagens e aspectos a ter em conta,<br /><br /><a target="_new" href="http://www.codefutures.com/database-sharding/">[1] http://www.codefutures.com/database-sharding/</a><br /><br />e um sobre o nome do conceito :),<br /><br /><a target="_new" href="http://lethargy.org/%7Ejesus/archives/95-Partitioning-vs.-Federation-vs.-Sharding.html">[2] http://lethargy.org/~jesus/archives/95-Partitioning-vs.-Federation-vs.-Sharding.html</a><br />(os comentários também são interessantes!)<br /><br />Have fun! :)<br /><br /></span>Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-5843359271810229977.post-73920150464588017452009-01-30T19:08:00.005+00:002009-01-30T19:13:07.383+00:00Porque nem só de tecnicices é feita a informática... :)<span style="font-size:78%;"><span style="font-family:verdana;">Um artigo bastante interessante e elucidativo!</span><br /><br /><span style="font-family:verdana;">P'ra malta mai'miuda :) mas não só :)</span><br /><br /><span style="font-family:verdana;">Daqui: <a href="http://clix.expresso.pt/gen.pl?p=stories&op=view&fokey=ex.stories/494027">http://clix.expresso.pt/gen.pl?p=stories&op=view&fokey=ex.stories/494027</a></span><br /><br /><span style="font-size:85%;"><span style="font-weight: bold;font-family:verdana;" >Pais e filhos de mãos dadas na Net </span></span><br /><span style="font-family:verdana;">O mundo virtual é a porta de entrada para muitas oportunidades. O risco também está sempre lá, mas há que saber enfrentá-lo. pais portugueses são dos mais controladores </span><br /><span style="font-family:verdana;">A forma como os pais europeus acompanham a utilização que os filhos fazem da Net será o tema do debate que se realiza em Lisboa a 10 de Fevereiro, quando se celebra o Dia Europeu para a Internet Segura.</span><br /><span style="font-family:verdana;">Os dados mais recentes do Eurobarómetro revelam que os pais portugueses são dos mais controladores, mas, contraditoriamente, serão aqueles que se mexem com menor à-vontade no universo dos computadores. Certo é que há muito a fazer para acabar com os mitos e ajudar as crianças e os jovens a escapar dos riscos da Rede. E que depende sempre do diálogo.</span><br /><br /><span style="font-style: italic;font-family:verdana;" >Hélder Oliveira / WHO </span><br /><br /><span style="font-weight: bold;font-family:verdana;" >--> Jovens: riscos a não correr…</span><br /></span><ul><li><span style="font-size:78%;"><span style="font-family:verdana;">Evitar colocar na Net informações pessoais ou imagens reveladoras: desconhece-se onde podem parar e não podem ser apagadas se copiadas.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Desconfiar se alguém que não se conhece fizer demasiadas perguntas pessoais e de identificação.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Evitar marcar encontros com pessoas que só se conhece online.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Não alimentar discussões online</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Recordar sempre que a Net pode parecer anónima mas não é.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Usar as linhas de apoio e denúncias de conteúdos ofensivos linhaalerta.internetsegura.pt para casos de pornografia infantil, apologia do racismo e da violência ou www.inhope.org que agrega as hotlines de denúncia de conteúdos ilegais).</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Sair do computador sempre que se encontrar conteúdos ou imagens perturbantes e falar com alguém.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Não abrir e-mails que possam ter assuntos ou textos estranhos, nem carregar em links ou anexos que não pareçam de confiança.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Não instalar programas desconhecidos e ter sempre o sistema operativo e o antivírus actualizados.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Lembrar que o mundo virtual não está separado do mundo físico e muitas regras, sobretudo de boa educação, são válidas em ambos.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Quando alguém que não se conhece falar online, procurar saber mais sobre a pessoa e tentar confirmar a sua identidade.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Pensar bem antes de enviar uma mensagem que possa ser considerada agressiva ou ofensiva. Insultos verbais ou por escrito não são diferentes.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Se se deparar com alguma imagem ou conteúdo perturbantes, sair do computador e falar com alguém.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Se achar que algo de estranho se está a passar no computador ou se alguém o(a) estiver a incomodar, falar com os pais, professores ou amigos.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Não seguir links dados pelo Messenger a menos que a pessoa com quem se está a falar confirme que que o site é seguro.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Quando um programa faz aparecer uma janela de informação ou aviso, ler sempre o que lá está e tentar perceber o que se passou antes de clicar em alguma coisa.</span></span></li></ul><span style="font-size:78%;"><br /><span style="font-weight: bold;font-family:verdana;" >--> ...e oportunidades a aproveitar</span><br /></span><ul><li><span style="font-size:78%;"><span style="font-family:verdana;">Através da Rede podemos conhecer novas influências musicais, filmes, tendências da literatura. Um universo mais vasto e muito para além do que a rádio e a televisão mostram.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Instantâneo é a palavra-chave. Quase imediatamente acede-se a informação especializada sobre um assunto qualquer, comum ou incomum.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Poder conhecer novas pessoas e influências, com atitudes e ideias diferentes - ou semelhantes - às nossas, alargando horizontes. Estejam estas pessoas onde estiverem.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Conseguir mostrar e disponibilizar aos outros aquilo que se cria: músicas, filmes, fotografias, textos.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Poder ultrapassar barreiras ou dificuldades físicas, nossas e dos outros, trabalhar e estudar à distância, mesmo sem sair de casa.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">É possível explorar as nossas ideias, e as dos outros, exprimir aquilo que pensamos e dialogar com outros.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">O Instante Messenging é uma das ferramentas de contacto mais populares entre os jovens. Podem ser usadas como uma forma de contactar com novos amigos, embora seja também das áreas onde o acompanhamento e o diálogo com os pais é mais importante e útil para evitar problemas ou enganos.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">A grande oportunidade é poder usar a Internet para aprender a usar a própria Internet: desde fóruns, a sites e a pessoas dispostas a ajudar, muita coisa pode ser aprendida.</span></span></li></ul><span style="font-size:78%;"><br /><span style="font-style: italic;font-family:verdana;" >Conselhos e listagem realizados em colaboração com Daniel Cardoso, 22 anos, participante do projecto EU-kids</span><br /><br /><span style="font-weight: bold;font-family:verdana;" >Pais: há que acompanhar e não controlar</span><br /></span><ul><li><span style="font-size:78%;"><span style="font-family:verdana;">Assuma a responsabilidade. A segurança online de crianças e jovens é responsabilidade de todos, mas cabe aos pais e à família estabelecer os princípios fundamentais.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Promova a sua literacia digital. Um dos problemas que está na base das situações de risco e insegurança vividas por crianças e jovens na Internet resulta do pouco à-vontade que pais e educadores têm do funcionamento do universo das tecnologias de informação em geral e computadores e Net em particular. Não é preciso saber tanto quanto eles, mas um mínimo ajuda sempre.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Promova o diálogo e aprenda com os seus filhos a utilizar as ferramentas online. Procure também os recursos informativos disponíveis online.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Dialogue com os seus filhos sobre a utilização que eles fazem dos computadores e deixe claras as suas expectativas e quais os valores que devem presidir à utilização. Deixe claro o que é e o que não é aceitável. Fale-lhe também do que há de bom e alerte para os riscos existentes.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Coloque o computador em uma zona comum da casa. Não dê livre acesso ao computador e à Internet, a qualquer dia e hora, sem qualquer supervisão. Procure colocar o computador com o ecrã virado para o interior do espaço e não para a parede.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Defina regras de utilização em conversa com os seus filhos.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Garanta o cumprimento destas regras. A forma de utilização pode ficar plasmada numa listagem afixada em local visível, perto do computador.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Conheça novas ferramentas para além dos básicos antivírus. A classificação de conteúdos, monitorização da utilização e controlo de tempo poderão ser úteis. Por si só, não são soluções definitivas, mas podem ajudar, sobretudo com crianças mais novas.</span></span></li><li><span style="font-size:78%;"><span style="font-family:verdana;">Regule os encontros offline. Um dos grandes perigos para uma criança ou para um jovem são os encontros reais com pessoas que se conhece apenas do universo da Internet.</span></span></li></ul><span style="font-size:78%;"><br /><span style="font-style: italic;font-family:verdana;" >Conselhos dados por Tito de Morais do projecto muidossegurosna.net </span><br /><br /></span>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5843359271810229977.post-1262519070393264982009-01-26T11:32:00.002+00:002009-01-26T11:35:18.676+00:00Academia Microsoft em Castelo Branco<span style="font-size:78%;"><span style="font-family:verdana;">Olha a minha escolinha do bacharelato :):)</span><br /><br /><span style="font-family:verdana;">Daqui: <a href="http://diario.iol.pt/tecnologia/microsoft-castelo-branco-academia-microsoft-escola-superior-de-tecnologia-tecnologia-ultimas-noticias/1036334-4069.html" target="_new">http://diario.iol.pt/tecnologia/microsoft-castelo-branco-academia-microsoft-escola-superior-de-tecnologia-tecnologia-ultimas-noticias/1036334-4069.html</a></span><br /><br /></span><h1 style="font-family:verdana;"><span style="font-size:78%;">Academia Microsoft em Castelo Branco</span></h1><h1 style="font-family:verdana;"><span style="font-size:78%;">Espaço vai ficar na Escola Superior de Tecnologia do Instituto Politécnico</span></h1> <span style="font-size:78%;"><span style="font-family:verdana;">Uma Academia Microsoft vai instalar-se na Escola Superior de Tecnologia do Instituto Politécnico de Castelo Branco a partir de quarta-feira, anunciou esta segunda-feira a instituição, escreve a Lusa. </span></span> <p style="font-family:verdana;"><span style="font-size:78%;">A iniciativa surge no âmbito do projecto Academias da Agência para a Sociedade do Conhecimento e visa a criação de espaços para formação em Tecnologias de Informação e Comunicação, tanto profissionalizante como na óptica do utilizador.<br /></span></p><p style="font-family:verdana;"><span style="font-size:78%;">Para o efeito, são integradas iniciativas já existentes no terreno da responsabilidade de empresas ligadas ao ramo, como é o caso da Microsoft - sendo que na Escola Superior de Tecnologia funciona já a Academia Cisco, especializada em redes. </span></p> <p style="font-family:verdana;"><span style="font-size:78%;">Os formadores da academia serão docentes da Escola Superior de Tecnologia certificados pela Microsoft. </span></p> <p style="font-family:verdana;"><span style="font-size:78%;">Para além das vantagens para os estudantes, a escola ganha acesso «a currículos, recursos, ferramentas e suporte que permitem fornecer formação e certificação de alta qualidade», destaca a instituição de ensino superior. </span></p> <p style="font-family:verdana;"><span style="font-size:78%;">A academia possibilita ainda «aos empregadores locais o acesso a recursos humanos mais competentes nas áreas das tecnologias da informação», acrescenta. </span></p> <p style="font-family:verdana;"><span style="font-size:78%;">Segundo a direcção da escola «a adesão EST ao programa IT Academy da Microsoft assume uma grande relevância na estratégia da escola, na medida em que contribuirá para a qualificação e requalificação profissional de activos, numa área que necessita de grande desenvolvimento em Portugal, das Tecnologias da Informação e Comunicação».</span></p>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5843359271810229977.post-44138927853568015592009-01-22T12:54:00.002+00:002009-01-22T12:58:00.531+00:00Protocolo HTTP - Reminders... :)<span style="font-family:verdana;font-size:85%;">Métodos GET, POST???</span><br /><span style="font-family:verdana;font-size:85%;">Qual usar? Qual a diferença?? Humm??</span><br /><span style="font-family:verdana;font-size:85%;"></span><br /><span style="font-family:verdana;font-size:85%;">Então essencialmente:<br />- GET: enviamos os parâmetros por querystring e recebemos o resultado (não necessariamente XML)<br />- POST: enviamos os parâmetros no body do pedido e recebemos o resultado (não necessariamente XML)<br /></span><br /><span style="font-family:verdana;font-size:85%;">Não é muito vulgar mas pode acontecer querermos enviar um XML por POST e parâmetros no URL.<br />De notar que há sites que só aceitam pedidos através de um dos métodos (GET ou POST) porque esse item é configurável no IIS.<br /><br />Descrição interessante aqui: </span><a href="http://www.cs.tut.fi/~jkorpela/forms/methods.html"><span style="font-family:verdana;font-size:85%;">http://www.cs.tut.fi/~jkorpela/forms/methods.html</span></a><span style="font-family:verdana;font-size:85%;">, tópico <em>The fundamental differences between "GET" and "POST"</em><br /><br />Detalhes interessantes também aqui: </span><a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html"><span style="font-family:verdana;font-size:85%;">http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html</span></a><span style="font-family:verdana;font-size:85%;"> (creio que pouca gente sabe que existem estes todos...)</span><br /><span style="font-family:verdana;font-size:85%;"></span><br /><span style="font-family:verdana;font-size:85%;">E prontux!</span><br /><span style="font-family:verdana;font-size:85%;"></span><br /><span style="font-family:verdana;font-size:85%;">Have fun! :)</span><br /><span style="font-family:verdana;font-size:85%;"></span><br /><span style="font-family:verdana;font-size:85%;"></span>Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-5843359271810229977.post-8933863305050840872009-01-08T11:43:00.002+00:002009-01-08T11:46:05.817+00:00Antivirus de borla (só p análise e pouco mais, mas...)<span style="font-family:verdana;font-size:85%;">Estava eu em luta com o meu PC, que teimava em se arrastar cada vez mais, eis senão quando descobri que andavam por aqui uns troianos armados em gregos!</span><br /><span style="font-family:verdana;font-size:85%;"></span><br /><span style="font-family:verdana;font-size:85%;">Então, com a ajudita de um querido colega, descobri uma página que analisa o disco gratuitamente e detecta ameaças. Para desinfecções, é preciso pagar (a não ser q sejam fraquitas...), mas já ajuda pra malta ver o que se anda a passar nos bastidores da máquina.</span><br /><span style="font-family:verdana;font-size:85%;"></span><br /><span style="font-family:verdana;font-size:85%;">Aqui fica o link:</span><br /><a href="http://www.pandasecurity.com/portugal/homeusers/solutions/activescan/default.htm?track=80381"><span style="font-family:verdana;font-size:85%;">http://www.pandasecurity.com/portugal/homeusers/solutions/activescan/default.htm?track=80381</span></a><br /><span style="font-family:verdana;font-size:85%;"></span><br /><span style="font-family:verdana;font-size:85%;">Enjoy...</span><br /><span style="font-family:verdana;font-size:85%;"></span>Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-5843359271810229977.post-17385089617295057952008-11-27T11:25:00.002+00:002008-11-27T11:30:35.042+00:00Dicas do Google para mais qualidade na programação<span style="font-family:verdana;font-size:78%;">Daqui: </span><a href="http://misko.hevery.com/code-reviewers-guide/"><span style="font-family:verdana;font-size:78%;">http://misko.hevery.com/code-reviewers-guide/</span></a><br /><span style="font-family:verdana;font-size:78%;"> </span><br /><span style="font-family:verdana;font-size:78%;">Dicas da equipa da Google, que levantam a bandeirinha vermelha de alerta em pontos do código.</span><br /><span style="font-family:verdana;font-size:78%;"></span><br /><span style="font-family:verdana;font-size:78%;">Aqui ficam.</span><br /><span style="font-family:verdana;font-size:78%;"></span><br /><a href="http://misko.hevery.com/code-reviewers-guide/flaw-constructor-does-real-work/"><span style="font-family:verdana;font-size:78%;">Flaw #1: Constructor does Real Work</span></a><br /><span style="font-family:verdana;font-size:78%;">Warning Signs<br />- new keyword in a constructor or at field declaration<br />- Static method calls in a constructor or at field declaration<br />- Anything more than field assignment in constructors<br />- Object not fully initialized after the constructor finishes (watch out for initialize methods)<br />- Control flow (conditional or looping logic) in a constructor<br />- Code does complex object graph construction inside a constructor rather than using a factory or builder<br />- Adding or using an initialization block<br /></span><br /><a href="http://misko.hevery.com/code-reviewers-guide/flaw-digging-into-collaborators/"><span style="font-family:verdana;font-size:78%;">Flaw #2: Digging into Collaborators</span></a><br /><span style="font-family:verdana;font-size:78%;">Warning Signs<br />- Objects are passed in but never used directly (only used to get access to other objects)<br />- Law of Demeter violation: method call chain walks an object graph with more than one dot (.)<br />- Suspicious names: context, environment, principal, container, or manager<br /></span><br /><a href="http://misko.hevery.com/code-reviewers-guide/flaw-brittle-global-state-singletons/"><span style="font-family:verdana;font-size:78%;">Flaw #3: Brittle Global State & Singletons</span></a><br /><span style="font-family:verdana;font-size:78%;">Warning Signs<br />- Adding or using singletons<br />- Adding or using static fields or static methods<br />- - Adding or using static initialization blocks<br />- Adding or using registries<br />- Adding or using service locators<br /></span><br /><a href="http://misko.hevery.com/code-reviewers-guide/flaw-class-does-too-much/"><span style="font-family:verdana;font-size:78%;">Flaw #4: Class Does Too Much</span></a><br /><span style="font-family:verdana;font-size:78%;">Warning Signs<br />- Summing up what the class does includes the word “and”<br />- Class would be challenging for new team members to read and quickly “get it”<br />- Class has fields that are only used in some methods<br />- Class has static methods that only operate on parameters </span><br /><span style="font-family:verdana;font-size:78%;"></span><br /><span style="font-family:Verdana;font-size:78%;">:</span><br /><span style="font-family:Verdana;font-size:78%;"></span>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5843359271810229977.post-53676241417074381602008-04-24T10:39:00.007+00:002008-12-10T17:10:12.620+00:00Design Gráfico - à borlix! :)<span style="font-family:verdana;font-size:85%;">Para quem quer fazer umas coisinhas de design gráfico, mas nao percebe muito de Photoshop ou CorelDraw, ou outras conceituadíssimas(!) ferramentas (e já agora para quem não quer pagar licenças ou arriscar-se à multa, que a fiscalização anda aí!), aqui fica a divulgação de um FreeWare fixolas que ajuda à coisa:</span><br /><span style="font-family:verdana;font-size:85%;"></span><br /><span style="font-family:verdana;font-size:85%;"><strong>O Paint.Net!!!!</strong></span><br /><br /><br /><img id="BLOGGER_PHOTO_ID_5192763206541486930" style="DISPLAY: block; MARGIN: 0px auto 10px; CURSOR: hand; TEXT-ALIGN: center" alt="" src="http://1.bp.blogspot.com/_VJRpsluLgns/SBBmn7ifq1I/AAAAAAAAALw/448uI3R1VlA/s320/Logo_Paint_net.gif" border="0" /><br /><span style="font-family:verdana;font-size:85%;">Trata-se de um <em>freeware</em> de edição de imagem que corre sobre o Windows. Como os senhores <em>do</em> Paint.Net apregoam, é intuitivo e relativamente fácil de usar.</span><br /><span style="font-family:verdana;font-size:85%;">É um pouco mais limitado que os softwares tradicionais, mas a vantagem deste tipo de software é que está sempre a sofrer melhorias, o que quer dizer que podemos sempre contar com mais uma versãozita que traz mais umas coisinhas com que podemos brincar.</span><br /><span style="font-family:verdana;font-size:85%;"></span><br /><span style="font-family:verdana;font-size:85%;">Podem sacá-lo <a href="http://www.getpaint.net/"><strong><span style="color:#ff9966;">aqui</span></strong></a>.</span><br /><span style="font-family:verdana;font-size:85%;"></span><br /><span style="font-family:verdana;font-size:85%;">Have fun ;)</span><br /><span style="font-family:verdana;font-size:85%;"></span><br /><br /></span><span style="font-family:verdana;font-size:85%;"></span>Unknownnoreply@blogger.com0