# Developer ZoneAdvanced Software Development with MATLAB

Posts 21 - 30 of 36

# Don’t Mock Me!3

Hi folks, it's been a long time! Thanks for your patience as we have a lot of great incubating topics to discuss on the blog. Today I am excited to introduce David Hruska, who is the lead developer... 더 읽어보기 >>

# Testing for Model-Based Design2

Hi all, if you haven't seen it already, I wanted to make sure you were aware of some of the great testing related posts that Guy & Ajay have been up to lately. So for now they have two posts up... 더 읽어보기 >>

# …and Yet Another Way to Consume the Secret Sauce1

Here is Stephen Carter once again to describe an exciting feature in R2016b for test result analysis, reporting, and archiving. Take it away Stephen!In my previous post, I demonstrated that you can... 더 읽어보기 >>

# Additional Ways to Consume the Secret Sauce1

For today's blog entry I'd like to introduce Stephen Carter. Stephen is an engineer on the MATLAB Test Frameworks team and has been involved in many exciting new features over the past few releases... 더 읽어보기 >>

# Trending Now!1

Today it is my pleasure to introduce my MathWorks colleague Anoush Najarian. Anoush is an engineering manager on the MATLAB performance team and she has been instrumental in many great projects such... 더 읽어보기 >>

# Small Fibs Eventually Become Large Fibs – Another exercise in scaling6

OK, I had way too much fun writing that last blog post exploring algorithmic scaling. I want to explore this a bit more with a some "real" code, and what is more real than a function to calculate the... 더 읽어보기 >>

# Performance Review Criteria 3: Scales to the task1

To scale or not to scale. That is the question. When talking about algorithmic complexity, the answer to said question is usually an important one. No matter what the constant factors are that affect your algorithm's speed, poor scaling performance severely limits the scope of the problems you can solve. How do you measure your code's runtime complexity? If you don't have a good method for this (or even if you do!) then once again the performance testing framework is on your side. I was amazed when I learned of this one weird trick to measure the complexity of my algorithms.... 더 읽어보기 >>

# Performance Review Criteria 2: Sticks to Solid Principles2

We saw last time how we can use the performance testing framework to easily see the runtime differences between multiple competing algorithms. This can be done without needing to learn about the philosophies and guiding principles of the framework, indeed you don't even need to know that you are using a performance test framework or that the script you are writing is actually even considered a "test".... 더 읽어보기 >>

# Performance Review Criteria 1: Peer Comparison4

Have you ever wondered how to compare the relative speed of two snippets of MATLAB code? Who am I kidding? Of course, we all have. I am just as sure that you already have a solution for this. I know... 더 읽어보기 >>

# Time for your Performance Review

There are so many cool features in 2016a. Live Scripts are huge. The App Designer is a game changer. The language and environment keeps moving ahead with many exciting features.Unfortunately I... 더 읽어보기 >>

Posts 21 - 30 of 36