Sunday, June 19, 2011
Saturday, June 18, 2011
Friday, June 17, 2011
Mihir Sarkar
Mihir Sarkar: "Sound Design with Everyday Words
Musicians and music lovers often describe the quality of the sounds they create or hear with words such as “bright” or “warm”, “ethereal” or “metallic”. Our project investigates the relationship between auditory perception and language in this context. We are interested in finding whether people use a common vocabulary to describe timbre, or if their choice of words is related to their musical or cultural background. To this end we deployed a survey where people were asked to assign words to the sounds that were played to them. We analyzed the results and identified how the words correlate with timbral features. Based on this study, we are designing an audio processing engine that can automatically tag sounds in a database for retrieval purposes, and then modify them by using a verbal description of the user’s intuitive expectation (such as “a sharper sound”) instead of technical parameters."
Musicians and music lovers often describe the quality of the sounds they create or hear with words such as “bright” or “warm”, “ethereal” or “metallic”. Our project investigates the relationship between auditory perception and language in this context. We are interested in finding whether people use a common vocabulary to describe timbre, or if their choice of words is related to their musical or cultural background. To this end we deployed a survey where people were asked to assign words to the sounds that were played to them. We analyzed the results and identified how the words correlate with timbral features. Based on this study, we are designing an audio processing engine that can automatically tag sounds in a database for retrieval purposes, and then modify them by using a verbal description of the user’s intuitive expectation (such as “a sharper sound”) instead of technical parameters."
Thursday, June 16, 2011
TDD leads to an architectural meltdown around iteration three « Otaku, Cedric's blog
TDD leads to an architectural meltdown around iteration three « Otaku, Cedric's blog: "“Tests first” or “tests last” is unimportant as long as there are tests.
Try to think about testing as early as possible in your development process.
Don’t let one liners contradict your experience. For example, don’t listen to people who tell you to write “the simplest possible thing that could possibly work”, also known as YAGNI. If your experience tells you you’re going to need this extra class in the future even if it’s not needed right now, follow your judgment and add it now.
Keep in mind that functional tests are the only tests that really matter to your users. Unit tests are just a convenience for you, the developer. A luxury. If you have time to write unit tests, great: they will save you time down the road when you need to track bugs. But if you don’t, make sure that your functional tests cover what your users expect from your product.
Don’t feel bad if you are not doing Test-Driven Development. There are a lot of factors that make this practice a bad fit for a lot of projects and developer personalities (aspects which are very often never mentioned by TDD extremists)."
Try to think about testing as early as possible in your development process.
Don’t let one liners contradict your experience. For example, don’t listen to people who tell you to write “the simplest possible thing that could possibly work”, also known as YAGNI. If your experience tells you you’re going to need this extra class in the future even if it’s not needed right now, follow your judgment and add it now.
Keep in mind that functional tests are the only tests that really matter to your users. Unit tests are just a convenience for you, the developer. A luxury. If you have time to write unit tests, great: they will save you time down the road when you need to track bugs. But if you don’t, make sure that your functional tests cover what your users expect from your product.
Don’t feel bad if you are not doing Test-Driven Development. There are a lot of factors that make this practice a bad fit for a lot of projects and developer personalities (aspects which are very often never mentioned by TDD extremists)."
PVS-Studio vs Chromium - Intel® Software Network - Intel® Software Network
PVS-Studio vs Chromium - Intel® Software Network - Intel® Software Network: "Good has won this time. To be more exact, source codes of the Chromium project have won. Chromium is one of the best projects we have checked with PVS-Studio.
Chromium is an open-source web-browser developed by Google and intended to provide users with fast and safe Internet access. Chromium serves as the base for the Google Chrome browser. Moreover, Chromium is a preliminary version of Google Chrome as well as some other alternative web-browsers."
Chromium is an open-source web-browser developed by Google and intended to provide users with fast and safe Internet access. Chromium serves as the base for the Google Chrome browser. Moreover, Chromium is a preliminary version of Google Chrome as well as some other alternative web-browsers."
Wednesday, June 15, 2011
Tuesday, June 14, 2011
Peter's blog: It's official: developers get better with age. And scarcer.
Peter's blog: It's official: developers get better with age. And scarcer.: "First interesting statistic is how users are distributed by age. On the graph we can see a textbook example of a bell distribution curve. I knew that with age coders tend to switch careers, but I was surprised to see the size of the drop. After the peak age of 27, number of developers halves every 6 to 7 years.
Second stat that I find most interesting is how Stackoverflow reputation relates to age. There is a near-linear increasing trend: the older the developers are the higher their SO reputation is. To see the reason behind this let's look at another graph:"
Second stat that I find most interesting is how Stackoverflow reputation relates to age. There is a near-linear increasing trend: the older the developers are the higher their SO reputation is. To see the reason behind this let's look at another graph:"
Subscribe to:
Posts (Atom)