GDE for Web Tech
juri.dev
Follow me!
Home
Blog
Collections
Newsletter
AMA
About Me
Articles for "Software Design"
REST Api Design - Resource Modeling
A summary from a post on Thoughtworks blog
Breaking apart conceptions by Ayende Rahien
On Monoliths and Microservices
Why You Should Avoid a Canonical Data Model
Notes: Microservices by Martin Fowler
My notes and thoughts on Martin Fowler's talk about Microservices at XConf
QCon London 2014 - Embracing Change - Building Adaptable Software with Events
My takeaways from the building adaptable software with events training
The narrow path between best practices and over-engineering
Modularity in JavaScript MVC Frameworks
The Coaching Architect
Lessons Learned: Don't Expose EF Entities to the Client Directly
Testing and the Single Responsibility Principle
Architecting for Failure at the Guardian
Sharpening the Tools
Questions for an Enterprise Architect
Large-scale JavaScript Application Architecture
Some Usability Thoughts for the Weekend...
Integrating Jersey with Spring
SmellyCode: A Classical Example of Non-Unittestable Code
Smelly Code: Direct Object Instantiation as a Testability Killer
Design Tech Talk Series Presents: OO Design for Testability
Practical example: Applying the Template Method design pattern
Why factories with configuration files are better for decoupling but still a testability killer
Unit testing asynchronous code
Tackle software dependencies with IoC and Dependency Injection
Are anonymous Lambda style event handlers a readability killer?
Comments smell! Replace them with more expressive code.
The power and simplicity of the Command pattern
Part 1: Writing testable code for the Android
Law of Demeter: Nice metaphor
Add semantic through your code, not through commenting
It is not about writing tests, its about writing stories
Don't use negated method names!
Using code metrics as indicator for code refactoring
ExecutableTask pattern to tackle J2ME multithreading
jQuery plugin development pattern
Best practices: The challenge of designing software for wireless devices
UML Use Case "extend" and "include" relationships
Best practices: Deploying webapps
Logical separation with MVC