Evolution of a Search Engine 演化搜索引擎

Here is the good post on the Evolution of a Search Engine by Philipp Lenssen这是个良好的演进搜索引擎的菲利普Lenssen

read it here看这里

….. ... .. Jignesh Dodiya Jignesh Dodiya

Flex - 3 软硬度-3

Here is some more information from some of the Adobe Team members regarding Flex 3.这里是一些更多信息，从一些Adobe公司团队成员有关的Flex 3 。

Is Flex 3 being rushed out?三是软硬度被送往呢？

We are not rushing out Flex 3.我们不冲出的Flex 3 。 The Flex 3 beta has not started and is some time away.第3的软硬度测试还没有开始，是一段时间内消失。 Once we have a first public alpha or beta, it will still be a logn while until we ship.一旦我们的第一个字母或公共测试版，它仍将是一个logn ，而直到我们的船。 What you are seeing is not about us rushing the product, it is about us becoming much more open about what is coming down the road in the future.你看到的是对我们不急于产品，这是对我们变得更加开放什么是未来的道路在未来。 We started this with Adobe Labs (initially Macromedia Labs) but in this cycle in the next few months you will see up open up more so folks can see the roadmap and give us feedback.我们开始这与Adobe实验室（最初的Macromedia实验室） ，但在这个周期在未来几个月内你会看到了开放，使人们更可以看到的路线图，给我们的反馈意见。 Keep in mind, we released the first public alpha of Flash at Max in October 2005.请记住，我们发布了首次公开字母的Flash在马克斯于2005年10月。 We had a small private alpha underway for a few months我们有一个小型私人字母进行了几个月
before that.在此之前。 But we didn’t ship Flex 2 until June 27 2006.但是，我们没有船的Flex 2 6月27日之前2006 。 Just because we are looking for testers and able to demo so features doesn’t mean we are about to ship.只是因为我们正在寻找能够测试和演示，使功能并不意味着我们将要船。 It just means we want to give you a view of the product before it is baked so you can give us feedback (and also for your planning).这只是意味着，我们希望给您认为该产品之前，烤，因此您可以给我们提供反馈意见（也为您规划） 。 From when we had our first external testers to when we shipped Flex 2 ws almost 12 months.从当我们第一次外部测试时，我们已发运的Flex 2几乎是12个月。 It may not be as long this time because it is not such an major architectural change, but we are going to let the product bake and stay focused on quality.它可能不是只要这个时候，因为它不是这样一个重大的建筑设计变更，但我们不会让产品的烘烤，并专注于质量。

….. ... .. Jignesh Dodiya Jignesh Dodiya

Google’s approach on Agile 谷歌的做法敏捷

Some of interesting points on Google’s approach to Agile:一些有趣的点，谷歌的做法，以敏捷：

• There are managers, sort of, but most of them code at least half-time, making them more like tech leads.有管理人员，那种，但其中大多数代码至少有一半时间，使他们更喜欢高科技线索。
• Developers can switch teams and/or projects any time they want, no questions asked; just say the word and the movers will show up the next day to put you in your new office with your new team.开发商可以切换队和/或项目的任何时间他们希望，没有质询;只是说这个词和推动者就会显示第二天把你的新办公室，新的团队。
• Google has a philosophy of not ever telling developers what to work on, and they take it pretty seriously.谷歌有一个理念，任何时候都不能告诉开发商什么工作，他们是否可以相当严重。
• Developers are strongly encouraged to spend 20% of their time working on whatever they want, as long as it’s not their main project.开发商正在大力鼓励花费20 ％的时间从事他们想要什么，只要它不是他们的主要项目。
• There aren’t very many meetings.有没有很多的会议。 I’d say an average developer attends perhaps 3 meetings a week, including their 1:1 with their lead.我想说的平均开发商参加3次会议也许一个星期，包括其1:1的领先。
• It’s quiet.它的安静。 Engineers are quietly focused on their work, as individuals or sometimes in little groups or 2 to 5.工程师们正在悄悄地集中于他们的工作，作为个人或有时在小团体或2至第5 。
• There aren’t Gantt charts or date-task-owner spreadsheets or any other visible project-management artifacts in evidence, not that I’ve ever seen.有没有甘特图表或日期任务的老板试算表或任何其他明显的项目管理文物的证据，而不是我见过。
• Even during the relatively rare crunch periods, people still go get lunch and dinner, which are (famously) always free and tasty, and they don’t work insane hours unless they want to.即使在较为罕见紧缩时期，人们仍得到午餐和晚餐，这是（著名）是免费又好吃，而且他们不工作时精神错乱，除非他们想。

Read the entire article here .阅读整篇文章在这里 。

….. ... .. Jignesh Dodiya Jignesh Dodiya