|
Rick York wrote: I am a bald, grey-beard with glasses, usually wearing a black cap.
Thank goodness for the black cap to differentiate the lot of us.  Have fun!
|
|
|
|
|
Some background - I'm a contractor tasked to work on an ASP.Net Web Forms app that is part of a larger suite of apps. When I was hired, I was told that I would have the opportunity to rewrite the app I had the desire. What they didn't tell me is that the nature of the app suite pretty much precluded me from doing so. So me, not willing to accept defeat so easily...
What I'm Doing:
I'm creating a prototype (to be made into a Visual Studio project template) that will be presented as a replacement for existing ASP.Net apps that have existed for more than 10 years. As you might expect, as requirements changed and new stake-holders felt the need to impact the apps, the code was patched, re-patched, and re-re-patched, ad-infinitum. In addition, a lot of "cowboy coding" was allowed to seep into the code base because so many different coders have worked on the code. This has caused a lot of code "almost" duplication, disparate/incompatible versions of javascript libraries to be used, and a theme file that generates a "not found" error, yet the sites mysteriously still work without complaint. Someone (in the distant past) even decided that it would be a "good idea"(tm) to combine jquery-ui and kendo-ui into a single file, which makes updating either of those libraries impossible. BTW, there are at least two versions of this composite file, and they both contain DIFFERENT versions of jquery-ui and kendo-ui. "Delicate house of cards" doesn't even BEGIN to describe the current code base.
The other devs have been "resistant" to a rewrite, and understandably so. It would feature unfamiliar (albeit, more modern) technology, most of the every app would have to be re-implemented and re-tested, and there simply isn't enough time/people/resources available to support the effort. I think if they allowed one day per week for everyone to work on this, it could be done in a reasonable period, and once it gather a notable head of steam, it could replace the current maintenance effort currently allocated to the legacy code base. Beyond that, everybody in the group has a life/family/interests that do not include putting in the extra time necessary for doing a rewrite. Everyone except me.
With all of that in mind, I decided to embark on an un-tasked effort (on my own time, at home) to come up with a project template we can use to easily create new apps that have no dependency on each other, support our complex database and web server requirements, and provide common functionality that all of our apps must have.
Considerations:
0) Our suite of apps can exist in one of five environments - Dev, Test, QA, Prod, and None (a special environment that I use at home for working on the prototype). Each environment can be run on one of two networks - classified and unclassified.There are almost 20 applications, each with their own database, and each of which share two of those database. Each app can also optionally access any of the other databases as needs are determined.
1) All of the applications must use the same presentation style, and identifying components, such as a header panel that displays the app name and an appropriate graphic, a bar that illustrates the environment (locked at the top and bottom of the screen), access to app info and help desk/point of contact info, and display the connected user.
2) The site uses Entity Framework. This is NOT by choice, but since the authentication stuff uses it, I figured I may as well, too. This has been my largest hassle to date, because I generally don't like EF, and ALL of our database access is handled by stored procs, which means we have to do things (apparently) wildly different from how EF thinks we should.
Current status:
0) I have the layout requirements ironed out. The only thing they have to provide in a new application is the app-name graphic that's displayed in the header banner, and provide (or select) the desired background image used in the banner.
1) The startup process begins with checking whether the site is in maintenance mode. If it is, a special div is presented, and processing stops. If it isn't in maintenance mode, the site attempts to use the user's CAC card to log him in, and if the CAC isn't found, the user is prompted to login manually. Once the user logs in, his login history is presented, and when he clears that form, the site begins its normal functionality (presenting the app's menu and taking him to the home page).
2) The entity framework stuff was a veritable nightmare, mostly because I wanted to put all of the EF code into a separate assembly into which the developer could add what he needed. As it sits, the DataModels assembly already includes one model that allows the app to determine how certain aspects are present. All the developer has to do is add his own contexts and models, using the ADO Data Entity Model template provided in Visual Studio. This was made quite problematic due to our 20 apps in five environments (100 possible connection strings) requirement, as well as the desire to have all of the possible permutations of the connection strings be completely contained in code. This forced me to write a class that configures the connection strings base on the specified application and environment so that only the connection strings the app needed were created. This further caused the creation of a couple of static classes that would be available site-wide, which also solved the "use a model in a shared view" problem.
So, the prototype currently eliminates at least a week's worth of development, even for an experienced MVC/EF developer, is copiously commented, and even has a dedicated HTML page that the developer can reference when he needs to know where stuff is and why it was done.
No existing code was harmed in the making of this movie. I think I'm almost ready to show off my baby to the other devs on the team.
I've been busy.
PS. Even if it's not implemented and my efforts are criticized/ignored, I will at least be able to lay claim to making the effort to positively affect the code base, and I will have learned a lot in the process, besides. There's no such thing as "wasted effort" if you learn something along the way.
PS.PS. I might even make a video demonstration (on youtube) so they can see the project template in use.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
TL;DR
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Really?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I agree with OG
even go as far to ask "what is it?" "who is it for?"
... is it a rant, an initiation of discussion or actual project request?
Just skimming the titles (which managers will do first) it looks backwards.
If the "decision making" management this is pitched to is:
- IT: you're only going to piss them off in the first 2 minutes,
- finance: you're only going to put them to sleep in the first 2 minutes,
- business: they're going to 'step out to take an important call' within the first 2 minutes and won't come back
it appeals to no one, no one will know what to do with it, so no ones going to act.
I'll ask again: what is it? who is it for?
|
|
|
|
|
WTF are you talking about?
This wasn't for "managers", it was just me talking about what I did this weekend.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
#realJSOP wrote: WTF are you talking about?l
Well that is precicely was what I was asking you. Rant? Selling an idea? Asking for help?
Anyway, as from your tone you want to lower the conversation into the gutter let me put it like this:
-> Your presentation skills suck.
And what that means: Nobody's going to buy into it. ..as to a video: you'll only embarrass yourself.
Message Signature
(Click to edit ->)
|
|
|
|
|
Lopatir wrote: Well that is precicely was what I was asking you. Rant? Selling an idea? Asking for help?
None of the above. Like I said, I was just talking about what I was up to this weekend, and felt like the background info was necessary to explain what I did and why I did it.
Lopatir wrote: Your presentation skills suck.
It's posted in a discussion forum, it's not a f*ckin white paper.
Lopatir wrote: And what that means: Nobody's going to buy into it. ..as to a video: you'll only embarrass yourself.
We work in a vault (not quite a SCIF, but access and content are controlled), and we're not permitted to bring code in from the outside without jumping through a lot of security hoops. To avoid the hoops, I'm going to use YouTube to create a (private) demo video that we can access from inside the vault. If after seeing the video, there is interest to actually see the code, I can schedule an external conference room and hook my laptop up to the big-ass display system. Getting time in the external conference room is a substantial hassle and the wait time for available slots varies from one to three weeks. Before I ask my manager to go through the scheduling process, I want to see if there's any general interest. THAT is why I'm making a demo video. Embarass myself? Probably not.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
#realJSOP wrote: To avoid the hoops, I'm going to use YouTube to create a (private) demo video that we can access from inside the vault.
Have you approached Troy McClure?
Michael Martin
Australia
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible."
- Mr.Prakash One Fine Saturday. 24/04/2004
|
|
|
|
|
#realJSOP wrote: I think I'm almost ready to show off my baby to the other devs on the team.
Hopefully you work with people (and management) that doesn't see your initiative as competition, one upmanship, or in some similar negative light!
Latest Article - Azure Function - Compute Pi Stress Test
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
Jobs are easy to find. Like I said, I don't care, because now I have something in my portfolio that I can demonstrate to companies that claim to appreciate my unique brand of initiative in the face of ruin and doom.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I read it all.
At the risk of exposing my Cowboyishness, Y'all are a saint. 
|
|
|
|
|
I need to run out and get a microphone so I can record my commanding voice with the demo video.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Add a little reverb and maybe some pitch-shifting or subharmonics. Get a voice a real voice-of-god thing going.
Nah - that could be too intimidating. Never mind.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
I'd be a bit careful with public demo videos, and the like. The people you're contracting to might (choose to) see it as a breach of copyright.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
It's gonna be a private vodeo that only I can view (if youtube is to be believed). I plan on doing it in the conference room. Besides that, it can't be a copyright violation - it's taxpayer funded.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
First contract, huh?
|
|
|
|
|
Nope - been doing contract work on-and-off since 1980. If you saw our current code base, you'd be highly motivated to update it, too.
On the other hand, I'm re-learning MVC, and bending EF to support my nefarious plan (ALL of our database queries are performed via stored procedures).
Something I learned about ADO Data Entity Model - when you "import" stored procs, it generates a model based on the dataset returned by the store proc... unless you're returning a dataset from a temp table. For some reason, EF goes deaf, dumb, and blind in that instance, forcing you to manually create the model - OR rewrite the stored proc to not use a temp table so the model can be generated automagically.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Yeah, it was me that told you that  EF isn't really geared up for SPs, it supports them but it's really intended for generating dynamic SQL. Using SPs is generally considered legacy these days.
|
|
|
|
|
Yeah, but we deal with so.much.data (with hyper-convoluted business rules), and have so many concurrent users that it is not practical to not use stored procs.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Out of topic, but what's with the #realJSOP ? Did I miss something ?
|
|
|
|
|
I wanted to change my display name to JSOP, but someone is already using it, so I changed to #realJSOP.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Ah, that's bad luck. Have you tried bribing the hamsters ?
|
|
|
|
|
nah - I haven't even decided if I like it. I can't find my posts as easily now.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I wish you much luck. Having worked in a similar environment I understand the (ack! I going to use corporate speak here) headwinds you are up against.
And Lopatir was being a jerk in this instance.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
