urn:lj:livejournal.com:atom1:vyeremin vyeremin vyeremin 2007-01-29T12:36:24Z urn:lj:livejournal.com:atom1:vyeremin:2286 2007-01-29T12:36:24Z 2007-01-29T12:36:24Z Из последней рассылки <b>Бюллетень-молния MSDN (на русском языке)</b>(MSDN Flash):<br /><br /><i>25 – 26 апреля, отель Grand Hyatt Hotel, Park Avenue, Grand Central Terminal, Нью-Йорк, штат Нью-Йорк<br />...<br /> «Задняя комната» — только для сборщиков систем (EN) &lt;http://...&gt; <br />...</i> urn:lj:livejournal.com:atom1:vyeremin:1890 2007-01-15T12:02:43Z 2007-01-15T12:02:43Z <img src="http://www.belomors.ru/russian/loafers.gif"> urn:lj:livejournal.com:atom1:vyeremin:1713 2007-01-12T17:51:38Z 2007-01-15T12:11:18Z <img src="http://images.meez.com/user02/04/09/02/040902_10002624549.gif" alt="At work..." /> urn:lj:livejournal.com:atom1:vyeremin:1472 2007-01-12T17:01:54Z 2007-01-12T17:06:04Z Наткнулся тут на программу <a href="http://snowball.tartarus.org/">Snowball</a> - stemming-а (выделения неизменяемой основы, используемой в морфологическом поиске поисковыми движками) для <a href="http://snowball.tartarus.org/algorithms/russian/stemmer.html">русского языка</a> и решил вспомнить, какие подводные камни были, когда делался парсер для ОРФО. Так вот, там для русского языка специально (в коде!) обрабатывались случаи:<br /><br />- беглых <b>о/бо</b>: обить / о<b>БО</b>бью, опереться/о<b>БО</b>прусь;<br />- чердование <b>с/з</b> в приставке: ра<b>С</b>шить/ра<b>З</b>ошью.<br /><br />И, похоже, Snowball такие случаи отлавливать не умеет (не говоря уже, об омонимии). urn:lj:livejournal.com:atom1:vyeremin:1215 2007-01-12T08:18:49Z 2007-01-12T08:20:55Z Интересная <a href="http://www.nytimes.com/2007/01/11/technology/11email.html?_r=1&amp;n=Top%2fReference%2fTimes%20Topics%2fPeople%2fS%2fStone%2c%20Brad&amp;oref=slogin">статья в NY Times</a> о том, как в (американских) компаниях идет борьба с использованием сотрудниками web e-mail ящиков (типа Yahoo, Google, Hotmail). Цитата:<br /><q><i>At the business software maker BEA Systems, Anthony Bisulca, a senior security analyst, estimated that around 30 percent of his employees were using private e-mail accounts in the office, even though the company’s Internet policy clearly prohibits it.</i></q><br /><br />Там же:<br /><q><i>Many companies apparently do not have that level of trust. In a survey conducted last year, the e-mail security firm Proofpoint found that 37 percent of companies in the United States used software to monitor office use of Web mail.</i></q> urn:lj:livejournal.com:atom1:vyeremin:964 2007-01-09T12:34:20Z 2007-01-09T12:35:16Z Цитата из статьи "A Foundation for the Pillars of Software Factories" (MAJ #9):<br /><a href="http://msdn2.microsoft.com/en-us/library/bb245778.aspx" alt="MAJ 9">There are four syndromes that contribute to this increased difficulty: <br /><ul><li><i>The moving-target syndrome</i>: This syndrome is an unavoidable aspect in the software industry. There will always be a constant evolution of frameworks, patterns, strategies, and technologies. This continuum will often make your effective solution today an ineffective one at some point in the future.</li><br /><li><i>The perfect-storm syndrome</i>: It is always difficult for any company to find the right number of developers, at the right time, with the appropriate vision and budget. If any one of these items is not correct the solution will suffer and can potentially become ineffective.</li><br /><li><i>The Goldilocks syndrome</i>: One of the joys in solving logical problems is discovering the most innovative and efficient solution for a technical problem. However, this delivery rarely considers the right solution based on cost. As a result, many solutions are overengineered or underengineered. Very often this engineering is a matter of perspective, and striking a balance between the best solution and the right solution is challenging.</li><br /><li><i>Grandpa's favorite-chair syndrome</i>: It is in our nature to gravitate toward things that we understand. That is why software is often architected to avoid as much change as possible. The limited risk that comes from using code that has already been proven to work is immeasurable. This approach will result in solutions that are added to in unnatural ways.</li></ul></a> urn:lj:livejournal.com:atom1:vyeremin:665 2006-12-25T12:59:48Z 2006-12-25T12:59:48Z По офису ходит девушка с фотоаппаратом и тихонечко всех фотографирует. Представилась фотографом французского журнала. Неужели мы стали настолько модными?