-
Майсторство в занаята от Стефан Кънев
posted in Architecture on 2012-05-17 -
Изключително интересна лекция отностно програмирането.
read more comments
-
Brian McCallister and the code
posted in Architecture on 2012-05-16 -
Programming and the Profession of Programming are quite different things. Programming is being able to efficiently tell a computer exactly what to do in a repeatable manner. The profession of programming is being able to efficiently convert business requirements into bugs.
comments
Read the full article here.
-
Nicholas Zakas: Scalable JavaScript Application Architecture
posted in Architecture on 2012-04-09 -
Yahoo! home page engineer Nicholas Zakas, author of Professional JavaScript for Web Developers, discusses frontend architecture for complex, modular web applications with significant JavaScript elements.
read more comments
-
A behind-the-scenes look at Facebook release engineering
posted in Architecture on 2012-04-07 -
comments
Did you ever wonder how Facebook's release management looks like. Here is an interesting article about that http://arstechnica.com/business/news/2012/04/exclusive-a-behind-the-scenes-look-at-facebook-release-engineering.ars/1
-
A new version of PHP (5.4)
posted in Architecture on 2012-03-06 -
What's new in the new release. Check out here http://net.tutsplus.com/tutorials/php/php-5-4-is-here-what-you-must-know/.
comments
-
The Dependency Inversion Principle
posted in Architecture on 2012-01-24 -
The Dependency Inversion Principle relates to the stability and reusability of higher-level components within an application. The principle states:
comments
A. High-level modules should not depend on low-level modules. Both should depend on abstractions.
B. Abstractions should not depend upon details. Details should depend upon abstractions.
Read more here.
-
The Single Responsibility Principle (SRP)
posted in Architecture on 2012-01-03 -
In my opinion that principle is really important and stays in the fundamentals of software design.
comments
In the context of the Single Responsibility Principle (SRP) we define a responsibility to be "a reason for change." If you can think of more than one motive for changing a class, then that class has more than one responsibility. This is sometimes hard to see.
Read more about this principle here.
-
The Open-Closed Principle
posted in Architecture on 2011-12-18 -
That's a great article by Robert C. Martin. It's one of those articles that really may change something in your programming. The principle is called Open-Closed and it says:
comments
SOFTWARE ENTITIES (CLASSES, MODULES, FUNCTIONS, ETC.) SHOULD BE OPEN FOR EXTENSION, BUT CLOSED FOR MODIFICATION.
More about that here.
-
How TDD and Pairing Increase Production by anarchycreek.com
posted in Architecture on 2011-12-12 -
Just a great article. Period! http://anarchycreek.com/2009/05/26/how-tdd-and-pairing-increase-production/
comments