I have been on Code Project for long long time and I still enjoy the little jokes under the headlines, e.g: Next steps toward Go 2 Collecting $200? Who is writing these?

Make it simple, as simple as possible, but not simpler.

I always jokingly tease the developer who added the comment.

Make it simple, as simple as possible, but not simpler.

When you do that: - It seems in the source control that you modified the source code - It looks insulting for the other developer (the one who originally wrote the code) If you can't agree in a friendly conversation on one style of code, then you have more important problems to tackle in the team.

Make it simple, as simple as possible, but not simpler.

Here is a title idea To Rosetta, Going to Churyumov-Gerasimenko Inspired by: To Lucasta, Going to The Wars by Richard Lovelace

Make it simple, as simple as possible, but not simpler.

You hang on there my friend and protect our beloved language. I used to be a VB.NET developer back in 2002 then I've seen the light (that would be C#), this is because I played with VB5 and VB6 during high school, because I played with QBasic during my early high school... C# pays more and is more respected by developers and generally the code written in C# tends to be higher quality as the VB.NET code tends to be written by old school guys with less OOP experience than those of C# (I am saying "tends" not all). Advice, move to C#

Make it simple, as simple as possible, but not simpler.

Haha :)

Make it simple, as simple as possible, but not simpler.

I have to also say that the sense of humor of the comments below the links are not boring at worst and humorous in general. I would even pay a subscription for this one. Keep it going guys

Make it simple, as simple as possible, but not simpler.

This is JavaScript style, the developer meant, if "more" is "undefined" then try the other option ProcessCarrierAnimations(). But obviously, this doesn't work in C#.

Make it simple, as simple as possible, but not simpler.

My brother usually has these problems: - Microsoft is not working (he means Word) - Mozzarella is not working (that is Firefox, apparently the cheese name is easier to remember than the actual company name)

Make it simple, as simple as possible, but not simpler.

I free my imagination for other fantasies :) (code fantasies, if you are wondering!)

Make it simple, as simple as possible, but not simpler.

When you say book I am assuming you mean fiction type. I actually feel guilty if I spend hours reading a "story" compared to a book on self-growth or something I could use in life or business, with the amount of books that could do an impact in life plus work plus family, there is no time for fiction. I also enjoy the visual effects like in Lord of The Rings and Thor. So definitely a movie.

Make it simple, as simple as possible, but not simpler.

Microsoft target consumers, for the MSDN Premium, are corporates and mid-size companies, not individual freelance developers. I am a consultant and I have been issued an MSDN Premium in every corporate I worked for...

Make it simple, as simple as possible, but not simpler.

You are saying "Article by John Smith" the Twitter community convention when you do that is "Article by @JohnSmith"

Make it simple, as simple as possible, but not simpler.

@Name I meant :) You are collecting this info anyway and displaying it on the article, so it should be part of the tweet.

Make it simple, as simple as possible, but not simpler.

CP does tweet an article. Good :) However, if the author has a Twitter tag then it should be included in the Tweet.

Make it simple, as simple as possible, but not simpler.

When copying a blog post, the copied post at CP still refers to the pictures of the original article. So, if the original blog is down or the url of the page and images have changed then the article will still appear on CP but without pictures. The suggestion is to also copy the pictures.

Make it simple, as simple as possible, but not simpler.

I dropped the O few days ago A Call To Drop "The Open Closed Principle" From The SOLID Design Principles[^]. So, you are dropping the S and I'm dropping the O, what is left? The LID principles? :) I think the S is an advice to try to give a class the least responsibities rather than a single responsibility, take a good design pattern like MVC, the controller has two responsibilities.

Make it simple, as simple as possible, but not simpler.

There is an easier way. What you wanted from the VirtualBox is the idea of "resetting" from time to time, but using a VM is slower than using the actual machine. My kids, under 6 years old, usually replace stuff on the PC and ruin the settings, so I installed a software called DeepFreeze which resets the C: drive upon every restart. Problem solved! So, put the proper settings and install the proper software then freeze it and whenever you want to install something new unfreeze install then freeze again. This solution is sometimes used in internet cafes as well. If you want to persist something, then you can save it on D:

Make it simple, as simple as possible, but not simpler.

My solution is JavaScript-centric, so that depends on your target audience. Ajax postbacks and templates are essential to my model.

Make it simple, as simple as possible, but not simpler.

Here are some thoughts to promote reusability: Consider a Facebook page that has 3 sections: - Your friends status updates - Friendship suggestions - Chat Rather than thinking of construction this page from one controller, think of more than one, for example: - Controller responsible for all updates - Controller responsible for all suggestions - Controller responsible for chat - Controller responsible on rendering a page (like the home page) The idea is that, the main view, like the home page, will be able to construct itself by "mixing and matching" what it needs to display from different controllers, in partial views or JSON format, using front-end frameworks e.g. jQuery maybe with conjunction with an MVVM framework like Knockout.js. Advantages: 1 - A controller will be serving a unique business case 2 - There is less dependencies in each controller, so a controller won't rely on the "UpdatesService", "SuggestionsService" and "ChatService" but will rely on smaller set of dependencies which promotes decoupling. 3 - You could change your controllers into RESTfull API services with less effort. 4 - An action method can be reused as it is doing a small and specific job. Disadvantages: 1 - Pushing more power to the JavaScript and the browser (that disadvantage might vary depending on your audience). 2 - More sophisticated JavaScript while JavaScript is not as mature as C# (unit testing frameworks for JS are not main stream yet, intellisense support is flaky (even with the latest Resharper), compile time checking doesn't exist, cross-browsers compatibility, etc...). 3 - A change in the controller affects more than one page, that means wider regression testing scope. I hope this helps.

Make it simple, as simple as possible, but not simpler.