Param Rengaiah

Param Rengaiah

Experience Architect


Param Rengaiah's is an Experience Architect. He has spent innumerable hours and wore multiple hats worrying about how to create business applications that connects with its users, perform the functions that they were suppose to, but also have empathy for the users. He has strong belief that for an enterprise application to remain useful, design has continually evolve and adapt - not just software design but experience design as well.

He is passionate about creating modular and scalable architectures, refactoring large applications to be modular and applying UX principles to enterprise application design. He writes about them at https://medium.com/@its_param

If he is not in front of his laptop hacking some code or reading in his iPad, you will find him either sleeping, watching old movies on Netflix or playing with his two boys. He lives in suburb of Chicago and is currently employed by Aspire Systems (http://www.aspiresys.com).




Blog

Story behind my SXSW 2014 submission

Posted 2013-09-03 04:03:00.0

I have proposed a Solo session for SXSW 2014. You can see it hemore »

Regaining Your Development Team’s Confidence

Posted 2013-08-22 17:39:00.0

Note: What I am about to describe is mostly applicable to medium-to-large applications maintained by 5 or more team membemore »
Read More Blog Entries »

Presentations

Taming Coupling & Cohesive Beasts with Modularity Patterns and Spring

If you have not not heard about coupling and cohesiveness, please come out of the rock that you live under . These two and their thrid cousin, polymorphism, is what we as developers chase day-in and day-out. They tease us with reusability, they prank us wmore »

Taming Coupling & Cohesive Beasts with Modularity Patterns and Spring

close

Param Rengaiah By Param Rengaiah

If you have not not heard about coupling and cohesiveness, please come out of the rock that you live under . These two and their thrid cousin, polymorphism, is what we as developers chase day-in and day-out. They tease us with reusability, they prank us with promise of comprehensiveness of our code. They entice with code quality, testability and unicorn. They came in the form of "Object Oriented' design, followed by GoF and SOLID Design Patterns. Then came DDD, BDD and ABC. Wait, what's ABC? I don't know.

The point is, none of them delivered what they promised. Now, the new kids on the blocks are Functional Programming and Modularity Patterns.

What happens when you choose to go though large refactoring exercise on the back of Modularity Patterns in a large enterprise project that is as complex as you can imagine, and behold, is build on top Spring stack.

The journey was long, arduous and gruesome. On the way, I made many enemies and found some new friends. This talk will highlight the issues, both technical and otherwise, and how it was overcome; where did Spring help and where did it hurt. In the end, was it worth it? Come to this session and you will find out.



tbd