somebody save me
-
I recently joined a company. I don't know what role i'm actually into but I'm exposed to all areas of the project. This is what i figured... Developers are developing without a design. Developers are not fully aware that they are developing a service oriented application. Application architecture is a complete mess. Anti-patterns are implemented in almost all area's of application AngularJs application is sitting on top with absolutely no separation of controller and service logic. No separation of controllers itself. Everything is written in single js file. Classic MVC web application sitting in the back-end with web controllers in it and with no Models and some piece of code is written in the Base controller to serialize the object to Json string which is given to angularjs app. Model is defined in the XML file. Developers are not aware of API controllers. Entity Framework is Ignored and classic ADO.NET is chosen for data access. Even the simple database logic is written in stored procedure A small module is almost complete and team is literally scared to add/remove anything to the application because doing so will break the application. Some master tables are mocked-up to support the development of the current module There's no naming convention followed anywhere Implementation of Authentication and authorization is incorrect. anybody can take the username, password or the session The team doesn't know how to enable cross-origin resource sharing so url-encoded content type is used for all HTTP post. Even the look-up table have these four columns - create_by, create_Date, UpdateBy , updatedt Every week we have a project meeting and demo with the client. We show the same screen to the client with some changes which was requested in the previous meeting There's no business analyst or Technical architect in this project. Some developers with no design skills are working on this huge enterprise application. Team doesn't ask for help, they don't research but they google and copy, paste any code that they think it works. Business domain and User Requirements are very interesting, An awesome US Client is looking for a real system. A decent amount is charged every month. It's been three months since the project started. It's been 4 weeks since i joined this company and this project. I said to the Senior Project Manager, there is a need to redesign the system. We have to do it at this early stage. We cannot design a system like this and it will not work. When the project grows, it will become difficu
Member 11121330 wrote:
Entity Framework is Ignored and classic ADO.NET is chosen for data access. Even the simple database logic is written in stored procedure
So they have not got everything wrong then. I'm with the others, start your job search now, you are not going to be happy under that regime, changing it will almost certainly not happen and your self esteem will be destroyed if you have to participate in a disaster.
Never underestimate the power of human stupidity RAH
-
I recently joined a company. I don't know what role i'm actually into but I'm exposed to all areas of the project. This is what i figured... Developers are developing without a design. Developers are not fully aware that they are developing a service oriented application. Application architecture is a complete mess. Anti-patterns are implemented in almost all area's of application AngularJs application is sitting on top with absolutely no separation of controller and service logic. No separation of controllers itself. Everything is written in single js file. Classic MVC web application sitting in the back-end with web controllers in it and with no Models and some piece of code is written in the Base controller to serialize the object to Json string which is given to angularjs app. Model is defined in the XML file. Developers are not aware of API controllers. Entity Framework is Ignored and classic ADO.NET is chosen for data access. Even the simple database logic is written in stored procedure A small module is almost complete and team is literally scared to add/remove anything to the application because doing so will break the application. Some master tables are mocked-up to support the development of the current module There's no naming convention followed anywhere Implementation of Authentication and authorization is incorrect. anybody can take the username, password or the session The team doesn't know how to enable cross-origin resource sharing so url-encoded content type is used for all HTTP post. Even the look-up table have these four columns - create_by, create_Date, UpdateBy , updatedt Every week we have a project meeting and demo with the client. We show the same screen to the client with some changes which was requested in the previous meeting There's no business analyst or Technical architect in this project. Some developers with no design skills are working on this huge enterprise application. Team doesn't ask for help, they don't research but they google and copy, paste any code that they think it works. Business domain and User Requirements are very interesting, An awesome US Client is looking for a real system. A decent amount is charged every month. It's been three months since the project started. It's been 4 weeks since i joined this company and this project. I said to the Senior Project Manager, there is a need to redesign the system. We have to do it at this early stage. We cannot design a system like this and it will not work. When the project grows, it will become difficu
Your job is a nightmare !!! If you don't like it, just try to find a way to get out. You just joined this company 4 weaks, so you can't do anything to change the way they do their job, just begin to find another job, NOW
In code we trust !
-
I recently joined a company. I don't know what role i'm actually into but I'm exposed to all areas of the project. This is what i figured... Developers are developing without a design. Developers are not fully aware that they are developing a service oriented application. Application architecture is a complete mess. Anti-patterns are implemented in almost all area's of application AngularJs application is sitting on top with absolutely no separation of controller and service logic. No separation of controllers itself. Everything is written in single js file. Classic MVC web application sitting in the back-end with web controllers in it and with no Models and some piece of code is written in the Base controller to serialize the object to Json string which is given to angularjs app. Model is defined in the XML file. Developers are not aware of API controllers. Entity Framework is Ignored and classic ADO.NET is chosen for data access. Even the simple database logic is written in stored procedure A small module is almost complete and team is literally scared to add/remove anything to the application because doing so will break the application. Some master tables are mocked-up to support the development of the current module There's no naming convention followed anywhere Implementation of Authentication and authorization is incorrect. anybody can take the username, password or the session The team doesn't know how to enable cross-origin resource sharing so url-encoded content type is used for all HTTP post. Even the look-up table have these four columns - create_by, create_Date, UpdateBy , updatedt Every week we have a project meeting and demo with the client. We show the same screen to the client with some changes which was requested in the previous meeting There's no business analyst or Technical architect in this project. Some developers with no design skills are working on this huge enterprise application. Team doesn't ask for help, they don't research but they google and copy, paste any code that they think it works. Business domain and User Requirements are very interesting, An awesome US Client is looking for a real system. A decent amount is charged every month. It's been three months since the project started. It's been 4 weeks since i joined this company and this project. I said to the Senior Project Manager, there is a need to redesign the system. We have to do it at this early stage. We cannot design a system like this and it will not work. When the project grows, it will become difficu
There is a saying:
Quote:
"Do not correct a fool, or he will hate you; correct a wise man and he will appreciate you."
As you said that your Manager is not taking interest in your opinions and keep on pushing with the crappy approach, my opinion is to search for a new job asap and move out. There is no reason to stay in such a company. All the best ;)
If it can happen, it will happen - Murphy's Law
-
I recently joined a company. I don't know what role i'm actually into but I'm exposed to all areas of the project. This is what i figured... Developers are developing without a design. Developers are not fully aware that they are developing a service oriented application. Application architecture is a complete mess. Anti-patterns are implemented in almost all area's of application AngularJs application is sitting on top with absolutely no separation of controller and service logic. No separation of controllers itself. Everything is written in single js file. Classic MVC web application sitting in the back-end with web controllers in it and with no Models and some piece of code is written in the Base controller to serialize the object to Json string which is given to angularjs app. Model is defined in the XML file. Developers are not aware of API controllers. Entity Framework is Ignored and classic ADO.NET is chosen for data access. Even the simple database logic is written in stored procedure A small module is almost complete and team is literally scared to add/remove anything to the application because doing so will break the application. Some master tables are mocked-up to support the development of the current module There's no naming convention followed anywhere Implementation of Authentication and authorization is incorrect. anybody can take the username, password or the session The team doesn't know how to enable cross-origin resource sharing so url-encoded content type is used for all HTTP post. Even the look-up table have these four columns - create_by, create_Date, UpdateBy , updatedt Every week we have a project meeting and demo with the client. We show the same screen to the client with some changes which was requested in the previous meeting There's no business analyst or Technical architect in this project. Some developers with no design skills are working on this huge enterprise application. Team doesn't ask for help, they don't research but they google and copy, paste any code that they think it works. Business domain and User Requirements are very interesting, An awesome US Client is looking for a real system. A decent amount is charged every month. It's been three months since the project started. It's been 4 weeks since i joined this company and this project. I said to the Senior Project Manager, there is a need to redesign the system. We have to do it at this early stage. We cannot design a system like this and it will not work. When the project grows, it will become difficu
Wave - I think we may be in the same building... (Seriously though - 90% of projects are exactly like this and if you don't learn to improve incrementally you will probably not ever be happy)
-
I recently joined a company. I don't know what role i'm actually into but I'm exposed to all areas of the project. This is what i figured... Developers are developing without a design. Developers are not fully aware that they are developing a service oriented application. Application architecture is a complete mess. Anti-patterns are implemented in almost all area's of application AngularJs application is sitting on top with absolutely no separation of controller and service logic. No separation of controllers itself. Everything is written in single js file. Classic MVC web application sitting in the back-end with web controllers in it and with no Models and some piece of code is written in the Base controller to serialize the object to Json string which is given to angularjs app. Model is defined in the XML file. Developers are not aware of API controllers. Entity Framework is Ignored and classic ADO.NET is chosen for data access. Even the simple database logic is written in stored procedure A small module is almost complete and team is literally scared to add/remove anything to the application because doing so will break the application. Some master tables are mocked-up to support the development of the current module There's no naming convention followed anywhere Implementation of Authentication and authorization is incorrect. anybody can take the username, password or the session The team doesn't know how to enable cross-origin resource sharing so url-encoded content type is used for all HTTP post. Even the look-up table have these four columns - create_by, create_Date, UpdateBy , updatedt Every week we have a project meeting and demo with the client. We show the same screen to the client with some changes which was requested in the previous meeting There's no business analyst or Technical architect in this project. Some developers with no design skills are working on this huge enterprise application. Team doesn't ask for help, they don't research but they google and copy, paste any code that they think it works. Business domain and User Requirements are very interesting, An awesome US Client is looking for a real system. A decent amount is charged every month. It's been three months since the project started. It's been 4 weeks since i joined this company and this project. I said to the Senior Project Manager, there is a need to redesign the system. We have to do it at this early stage. We cannot design a system like this and it will not work. When the project grows, it will become difficu
Member 11121330 wrote:
What should i do?
get another job and leave.
-
Member 11121330 wrote:
Entity Framework is Ignored and classic ADO.NET is chosen for data access. Even the simple database logic is written in stored procedure
So they have not got everything wrong then. I'm with the others, start your job search now, you are not going to be happy under that regime, changing it will almost certainly not happen and your self esteem will be destroyed if you have to participate in a disaster.
Never underestimate the power of human stupidity RAH
Just what I was thinking!
C# has already designed away most of the tedium of C++.
-
I recently joined a company. I don't know what role i'm actually into but I'm exposed to all areas of the project. This is what i figured... Developers are developing without a design. Developers are not fully aware that they are developing a service oriented application. Application architecture is a complete mess. Anti-patterns are implemented in almost all area's of application AngularJs application is sitting on top with absolutely no separation of controller and service logic. No separation of controllers itself. Everything is written in single js file. Classic MVC web application sitting in the back-end with web controllers in it and with no Models and some piece of code is written in the Base controller to serialize the object to Json string which is given to angularjs app. Model is defined in the XML file. Developers are not aware of API controllers. Entity Framework is Ignored and classic ADO.NET is chosen for data access. Even the simple database logic is written in stored procedure A small module is almost complete and team is literally scared to add/remove anything to the application because doing so will break the application. Some master tables are mocked-up to support the development of the current module There's no naming convention followed anywhere Implementation of Authentication and authorization is incorrect. anybody can take the username, password or the session The team doesn't know how to enable cross-origin resource sharing so url-encoded content type is used for all HTTP post. Even the look-up table have these four columns - create_by, create_Date, UpdateBy , updatedt Every week we have a project meeting and demo with the client. We show the same screen to the client with some changes which was requested in the previous meeting There's no business analyst or Technical architect in this project. Some developers with no design skills are working on this huge enterprise application. Team doesn't ask for help, they don't research but they google and copy, paste any code that they think it works. Business domain and User Requirements are very interesting, An awesome US Client is looking for a real system. A decent amount is charged every month. It's been three months since the project started. It's been 4 weeks since i joined this company and this project. I said to the Senior Project Manager, there is a need to redesign the system. We have to do it at this early stage. We cannot design a system like this and it will not work. When the project grows, it will become difficu
Charge by the hour?
Charlie Gilley Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
-
Charge by the hour?
Charlie Gilley Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
No. It's fixed budget monthly.
-
No. It's fixed budget monthly.
Of course :) Sarcasm...
Charlie Gilley Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
-
No. It's fixed budget monthly.
Your email doesn't work....
Charlie Gilley Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759