Pavan Gayakwad

Please find my second tech article on Code Project - String.Empty Internals , it's about one of the most debatable subject of using String.Empty over "" (empty string) in dot net world. I tried documenting my investigation on internal working of String.Empty under the hood of CLR. When I checked number of views just after 2 minutes of gap, it was 140! I was amazed looking at the number of users hitting CodeProject portal. That was cool!

“In this modern world, your soul will be a long lasting best friend ”

In my project, I am also one of the guys working on re-architecting one component. In fact we saw this component performaning very well when we put it in use, but still we wanted this to be more powerful, faster and robust. You can say, we are religiously following the saying “Best can still be improved”. Our component is now able to process 34 records in 1 second, but our expectation is to boost this up to 60-70 records per second. We have few challenges to operate on now, optimal performance, scalability, loosely coupled for easy integration with other components/applications.It is like, tie your hands behind your back and fight! If I am thinking of loose coupling, I have to compromise with performance, if I ignore scalability, I will have simple design which will have less layers (tightly coupled) and execute faster. I term this as a circular problem, if you do one thing other will get screwed and if I take care of other, main thing may not work as expected. But, what’s the fun if p...