Home » Posts filed under Best Practices
Securing .NET Web Application from Common Attacks
in
Best Practices,
Security
- on Tuesday, October 14, 2014
- 5 comments
Tips On Optimizing Frontend Web Application
in
Best Practices,
UX
- on Saturday, October 11, 2014
- 1 comment
"80-90%” of the end-user response time is spent on the frontend. Start there.
-Steve Souders
-Steve Souders
What are Inversion of Control (IoC), DIP, DI, and IoC Container?
in
Best Practices,
C#,
Design Patterns,
DI,
DIP
- on Wednesday, October 08, 2014
- 1 comment
Many developers are confused about DIP, IoC, DI, and IoC Container. Well, we've been using the concept even the from the DOS mode era. It’s only when SOLID OOP Design and Design Patterns were introduced that made this popular. It is the D in the SOLID acronym which stands for Dependency Inversion Principle. New concepts were added of course.
UX Design Tips: UX Designers and Software Architects Should Know
in
Best Practices,
UX
- on Sunday, August 03, 2014
- 5 comments
Rationale
UX Design is one of the most important thing in Software Development today most especially in web applications. And these are the reasons why:
UX Design is one of the most important thing in Software Development today most especially in web applications. And these are the reasons why:
Benefits of Removing Unused Using Directives
in
Best Practices,
Visual Studio
- on Friday, July 11, 2014
- No comments
When you create a new a program, class, or interface (anything that has a code) in Visual Studio, using directives or assemblies are added by default. Visual Studio assumes that you will be needing these directives. But these directives cause some awkward effects on your development when they are not used.
This will accumulate as your codes grow up and unknowingly, it is slowing you down.
This will accumulate as your codes grow up and unknowingly, it is slowing you down.
Repository Design Pattern : Implementing Generics, MOQ, MSTEST In ASP.NET MVC
in
ASP.NET MVC,
Best Practices,
C#,
Design Patterns,
Moq
- on Thursday, June 26, 2014
- No comments
Repository Design Pattern is a way to encapsulate repetitive data access code.
Repository Pattern is effective data access design pattern when we want to:
Repository Pattern is effective data access design pattern when we want to:
- Increase testability of the application. Make test repeatable without touching the data source;
- Implement Separation of Concerns between the business logic and data source or business logic and test units;
- Make the application work with different data source such SQL Server, mySQL, Oracle, web api endpoints, xml file and other RDBMS out in the market.
- Make our code reusable. Effective on CRUD.
Code Review : A Simple Guide
in
Best Practices
- on Monday, June 23, 2014
- No comments
What is a Code Review?
A.KA. – Code Analysis Review. It is an ongoing process to allow developers to improve code quality. This is defining moment where they can spot code smells, serious vulnerabilities and be able to promote readability, maintainability, security, and extensibility of codes or in short-high cohesive and loosely coupled codes.

