158 reputation
7
bio website wildlife.ca.gov
location California
age 36
visits member for 2 years, 11 months
seen Aug 12 at 20:51

Systems Architect and Application Developer for the State of California.

I am always interested in participating in open source projects and keen start-up endeavors.

My email is provided below in code (scrapers suck):

string secondWord; // 4 letters, meaning "rhythm" or slang for "exhausted"
string thirdWord;  // 8 letters, one who eats, drinks, ingests, or purchases things.
var email = ("one." + secondWord + "." + thirdWord + "@gmail.com").toLower();
Console.Write(email);

Dec
21
comment Javascript modularity, server based MVC & business reality
I agree with @Pointy that this belongs on the Programmers stack. Your question is very interesting, and I will folow it because I'm always looking for advice. But it is not an objective question, and is only going end up in preferential debates. As always, do what works best for your situation... none of us know anything about your network structure, number of clients or traffic stats, or build process... so the question is WAY too vague... all I know is avoid Silk. ;)
Dec
21
comment Advice/Approach for distilling homogenous code and building common code for a team
Excellent observations and advice. I appreciate it, and yes, I think the way we would approach it is like your #3 item, like open source chunks, maybe distributed via a NuGet package in a local feed, but with the sort of "you use it as is and I'll help; you tweak it, its now your trunk to maintain" policy in mind. We'll see. Thank you again.
Dec
20
comment Advice/Approach for distilling homogenous code and building common code for a team
Thank you Joe. I think this is the approach I'm going to take. I've tried it before informally, but I think you hit the nail on the head in that formal conversions/calculations need to be made to really sell the idea. Thanks for the advice on not pushing too hard either. Question then is, how does an IT guy sell management a cost-benefit when it costs a lot of man-hours up front? ROI promises are hard to go fishing with alone especially when broke.
Dec
20
comment Advice/Approach for distilling homogenous code and building common code for a team
Thanks. Baby steps is the only way the state moves. sometimes crawling backwards.
Dec
20
comment Advice/Approach for distilling homogenous code and building common code for a team
Good advice. I'll edit my comment to provide a little more detail though... this is happening within one IT department within one State Agency... I'm not trying to coordinate cross-agency... California has a devoted agency just for that reason and look how many of their projects succeed. ;P
Dec
13
comment How assertive should I be in handling exceptions in objects?
+1 Thanks for clarifying. If you edit your answer to address the exception handling concern about minimizing bloat from excessive catch blocks, I'll mark yours as the answer. @Kor got part of it, but he's not on Programmers exchange either it seems.
Dec
13
comment How assertive should I be in handling exceptions in objects?
@Kol do you have any other explicit examples from experience of objects that need manual disposing? Or any advice on smarter exception handling?
Dec
13
comment How assertive should I be in handling exceptions in objects?
@Dr.Wily'sApprentice That's exactly what I'm getting at... i guess im doing a poor job at phrasing my question because everyone keeps trying to tell me about how using is for IDisposable objects. duh.
Dec
13
comment How assertive should I be in handling exceptions in objects?
I've not seen try/catch/finally and using statements in base classes very often. quite often im writing logic in an MVC controller action and I use db persistence objects, services, etc. and trying to find the cleanest way to handle exceptions and garbage without adding tons of catch blocks nested down the page... i'm not violating dry at all.
Dec
13
comment How assertive should I be in handling exceptions in objects?
+1 Thank you. This is a little more what I was looking for. Some people have said to me 'catch everything an object might throw', others say 'catch e only at the top for clean code', etc... I'm trying to learn best practices... exception as logic is no concern here, but your first three comments are helpful. thank you.
Dec
13
comment How assertive should I be in handling exceptions in objects?
Thanks Kor for clarifying a bit... its the 5% I'm getting at... and items the garbage collection cannot automatically dispose (SqlConnection, etc.). Those are still items in memory, no? As well as locked in resources.
Dec
13
comment How assertive should I be in handling exceptions in objects?
@Kol - thank you for your response. I know what the using statement means and how it ties into IDisposable. Your SqlConnection thought is more like what I'm getting at... where the garbage collector will not be enough. things that need manual attention. And in terms of try/catch, how assertive a programmer should be about catching possible exceptions simply because the object is capable of throwing them.
Dec
13
comment How assertive should I be in handling exceptions in objects?
@AlbinSunnanbo I use both tools right now, just a lot less. Meaning, if there is an exception I truly want to handle, I'll use a try catch, but I haven't gone around stuffing everything possible in try/catch blocks. There are a couple objects just out of practice i put in using directives like working with Streams, but otherwise, I have not been handling IDisposable explicitly. I'm trying to learn explicit places it should be considered necessity, and when it can be safely overlooked for the sake of clean code. that clarify or confuse further? :)
Dec
13
comment How assertive should I be in handling exceptions in objects?
Thanks for the reply. I guess not "leaks" per se, but objects no longer needed lingering in memory? Isn't the StreamWriter scenario a common one where without a using statement it could potentially linger around in memory until the garbage collector decides its ready for the trash can? Perhaps I need to relearn what I thought I knew. :(
Dec
13
comment How assertive should I be in handling exceptions in objects?
My understanding is that .Net's garbage collection will cleanup IDisposable stuff on its own, and that these statements are to help programmers be assertive and manually control when and how they want it done. If that's the case, I'm trying to figure out the places its most important for me to do the work, and the places its safe to let the .Net runtime be the whiz-kid it's supposed to be.
Dec
13
comment How assertive should I be in handling exceptions in objects?
@JohnSaunders If that's the best place for it, I understand. Thanks for your help.