I see dumb people
-
I think the worst projects to take over are those similar to the one I'm currently stuck with : It's a relatively small & simple... in theory. What complicates it is the fact that it's been through serveral developers already :mad:, is in a mix of C# and VB, uses various versions of the framework, is reliant on heaps of 3rd party DLL's, uses a 3rd party data access and business logic layer classes that are enormous & difficult to understand, there are no business requirements documents for it, it has no technical spec, the database uses a mix of naming conventions... I could go on. Oh, and if that wasn't enough, the developer that was working on it is AWOL :wtf: so no support from there...
-
I think the worst projects to take over are those similar to the one I'm currently stuck with : It's a relatively small & simple... in theory. What complicates it is the fact that it's been through serveral developers already :mad:, is in a mix of C# and VB, uses various versions of the framework, is reliant on heaps of 3rd party DLL's, uses a 3rd party data access and business logic layer classes that are enormous & difficult to understand, there are no business requirements documents for it, it has no technical spec, the database uses a mix of naming conventions... I could go on. Oh, and if that wasn't enough, the developer that was working on it is AWOL :wtf: so no support from there...
-
I think the worst projects to take over are those similar to the one I'm currently stuck with : It's a relatively small & simple... in theory. What complicates it is the fact that it's been through serveral developers already :mad:, is in a mix of C# and VB, uses various versions of the framework, is reliant on heaps of 3rd party DLL's, uses a 3rd party data access and business logic layer classes that are enormous & difficult to understand, there are no business requirements documents for it, it has no technical spec, the database uses a mix of naming conventions... I could go on. Oh, and if that wasn't enough, the developer that was working on it is AWOL :wtf: so no support from there...
Yeah, you have to get into those projects early, before all that happens. :-D
-
Yeah, you have to get into those projects early, before all that happens. :-D
before all that happens so that you can make it happen :laugh:
-
before all that happens so that you can make it happen :laugh:
Shhh... I didn't want to say it so blatanty. :suss:
-
Shhh... I didn't want to say it so blatanty. :suss:
-
I think the worst projects to take over are those similar to the one I'm currently stuck with : It's a relatively small & simple... in theory. What complicates it is the fact that it's been through serveral developers already :mad:, is in a mix of C# and VB, uses various versions of the framework, is reliant on heaps of 3rd party DLL's, uses a 3rd party data access and business logic layer classes that are enormous & difficult to understand, there are no business requirements documents for it, it has no technical spec, the database uses a mix of naming conventions... I could go on. Oh, and if that wasn't enough, the developer that was working on it is AWOL :wtf: so no support from there...
Been there, done that (Except DB part). I had a privilege to work on project where people were assigned as some sort of punishment... and they "promoted" me to tech lead on it! :sigh: At least it's experience!
-
I think the worst projects to take over are those similar to the one I'm currently stuck with : It's a relatively small & simple... in theory. What complicates it is the fact that it's been through serveral developers already :mad:, is in a mix of C# and VB, uses various versions of the framework, is reliant on heaps of 3rd party DLL's, uses a 3rd party data access and business logic layer classes that are enormous & difficult to understand, there are no business requirements documents for it, it has no technical spec, the database uses a mix of naming conventions... I could go on. Oh, and if that wasn't enough, the developer that was working on it is AWOL :wtf: so no support from there...
-
I think the worst projects to take over are those similar to the one I'm currently stuck with : It's a relatively small & simple... in theory. What complicates it is the fact that it's been through serveral developers already :mad:, is in a mix of C# and VB, uses various versions of the framework, is reliant on heaps of 3rd party DLL's, uses a 3rd party data access and business logic layer classes that are enormous & difficult to understand, there are no business requirements documents for it, it has no technical spec, the database uses a mix of naming conventions... I could go on. Oh, and if that wasn't enough, the developer that was working on it is AWOL :wtf: so no support from there...
Just go ahead and delete all the source code and start from scratch. While you're at it, tell your boss that you're not a mind-reader. "What annoys me more than anything is someone hearing what my Ph.D. is and then asking me if I believe in Creationism."
Sincerely Yours, Brian Hart
-
I think the worst projects to take over are those similar to the one I'm currently stuck with : It's a relatively small & simple... in theory. What complicates it is the fact that it's been through serveral developers already :mad:, is in a mix of C# and VB, uses various versions of the framework, is reliant on heaps of 3rd party DLL's, uses a 3rd party data access and business logic layer classes that are enormous & difficult to understand, there are no business requirements documents for it, it has no technical spec, the database uses a mix of naming conventions... I could go on. Oh, and if that wasn't enough, the developer that was working on it is AWOL :wtf: so no support from there...
I have one right now that I am responsible for. It is the biggest pile of trash ever written. It was done in .net 1.1 by people who had absolutely no clue what they were doing. Every method is about three lines of code to debug just one little piece of functionality you end up with 25 files open by the time you have steeped through it. And even though this application processes near 500K transactions in each batch every thing is done via datasets with record level processing. It is slower than hell. Even though it it is one web application the project is broken out into 12 projects and there are about 10 config files that need to be changed to move the application. This program is so bad, that I can't even describe how horrible the code is. On a positive note we are supposed to purchasing something to replace it and then I'll only be supporting applications that I wrote.
-
I think the worst projects to take over are those similar to the one I'm currently stuck with : It's a relatively small & simple... in theory. What complicates it is the fact that it's been through serveral developers already :mad:, is in a mix of C# and VB, uses various versions of the framework, is reliant on heaps of 3rd party DLL's, uses a 3rd party data access and business logic layer classes that are enormous & difficult to understand, there are no business requirements documents for it, it has no technical spec, the database uses a mix of naming conventions... I could go on. Oh, and if that wasn't enough, the developer that was working on it is AWOL :wtf: so no support from there...
I've fell into the same trap; but the original web application was built in ASP and I had to convert it to ASP .NET web app. plus on top of that the share holder is a jerk. Dig deep and stick through it, it'll only make you a better developer. I'm at the end of this conversion and I have learned a lot. Hang in there! -Noir
