My last year in Sidoun
I think iam gifted to have a second stint in a project that is very close to my heart , cant explain why.
I always felt that this project had a coding style which makes it more or less a show case product...
In a more developer way i would say the product had too many RPC calls, million lines of code but less than 30 stored procedures, a liberal use of recordsets, all lead to a app that crawled and never scaled. In a bid to make it a scalable enterprise application i ensured the products release notes had something about
performance improvement and technical enhancement besides coping up with the existing schedules for new requirements. Looking back now the product has improved a lot interms of performance and scalaa bilty, i would say still a long way to go...
But i would prefer to say simple things led to big things
1) Following Best practices.
2) Help from Martin Fowlers refactoring notes
3) Tom kytes oracle
4) Microsoft sites esp. patterns and practices
5) sql profiler...
5) helping toad...
My important contributions in the last year
1) Performance tuning of core modules
2) SOA of a module called master bq (alternate bq)
3) Revamp of data exchange functionality (CMM)
4) core function for automatic mailing a simple vb script.
5) core function for calling a web service from vb code.(web vergabe)
6) Reusable database funtions
7) Export of blobs on a large export
8) Internetbau mirror architecture
9) Split tenders
10) Synthetic bidders
11) Solving complex strange isues like complus password gets lost everyday
12) Using nolocks hint for scalability.
13) Reducing the default transaction isolotion level of complus for scalability
14) Introducing new approach of development stress on method length ,new classes, reduced recordsets, use of xml
15) Training on .net to team members
I always felt that this project had a coding style which makes it more or less a show case product...
In a more developer way i would say the product had too many RPC calls, million lines of code but less than 30 stored procedures, a liberal use of recordsets, all lead to a app that crawled and never scaled. In a bid to make it a scalable enterprise application i ensured the products release notes had something about
performance improvement and technical enhancement besides coping up with the existing schedules for new requirements. Looking back now the product has improved a lot interms of performance and scalaa bilty, i would say still a long way to go...
But i would prefer to say simple things led to big things
1) Following Best practices.
2) Help from Martin Fowlers refactoring notes
3) Tom kytes oracle
4) Microsoft sites esp. patterns and practices
5) sql profiler...
5) helping toad...
My important contributions in the last year
1) Performance tuning of core modules
2) SOA of a module called master bq (alternate bq)
3) Revamp of data exchange functionality (CMM)
4) core function for automatic mailing a simple vb script.
5) core function for calling a web service from vb code.(web vergabe)
6) Reusable database funtions
7) Export of blobs on a large export
8) Internetbau mirror architecture
9) Split tenders
10) Synthetic bidders
11) Solving complex strange isues like complus password gets lost everyday
12) Using nolocks hint for scalability.
13) Reducing the default transaction isolotion level of complus for scalability
14) Introducing new approach of development stress on method length ,new classes, reduced recordsets, use of xml
15) Training on .net to team members

