1,684 reputation
1021
bio website statestreetgang.net
location United States
age 42
visits member for 3 years, 10 months
seen Jul 24 at 20:32

.NET developer and architect (C#, of course) for a small software company in Columbia, SC. If you're wondering what I'm doing, check out my questions.

Also,

ಠ_ಠ


Jul
24
comment Integrating a mobile website into a mobile app
Modern standards? Throw away classic ASP.
Jan
27
comment Efficient mixing of sync and async methods within a single method?
@Euphoric: Should I bother awaiting my last call? What would happen if I didn't and it threw? Would it be any different as it is currently?
Jan
27
revised Efficient mixing of sync and async methods within a single method?
edited tags
Jan
26
asked Efficient mixing of sync and async methods within a single method?
Dec
13
awarded  Notable Question
Dec
9
awarded  Booster
Dec
8
awarded  Announcer
Sep
9
awarded  Yearling
Aug
7
awarded  Scholar
Aug
7
accepted Strategy for keeping secret info such as API keys out of source control?
Aug
7
comment Strategy for keeping secret info such as API keys out of source control?
@Marek: They aren't. Which worked out for me in the end, as I've found it's nearly impossible to accomplish this with my stack :/
Jul
26
awarded  Popular Question
Jul
23
comment Strategy for keeping secret info such as API keys out of source control?
Dude, you can't unencrypt (easily) a hash. That's the whole point of hashes. This is for ME consuming somebody else's API, where they assign ME a secret key. My hashing it ensures (unless I choose a poor algo and crack it every time) that I can't use their API.
Jul
23
comment Strategy for keeping secret info such as API keys out of source control?
@matthew Oh, shit, I guess I don't know how SE works. I have to pick an answer now? Thanks for edifying me. Also, your answer is not that good. Its not bad, I didn't downvote it, but you didn't exactly understand the question you answered. Better luck next time.
Jul
23
comment Strategy for keeping secret info such as API keys out of source control?
This question is asking how to do that no, it absolutely does NOT. The fact is that these keys need to be used by code, therefore be accessed by code, and that usually means via code or configuration files, which if they aren't in source together they are at least close by and may accidentally end up in source. The hosted web app is nonsensical, unfortunately. You didn't have to apply for an api key to log into StackOverflow via your (hypothetical) facebook account. place key here is a massive oversimplification that won't work in dev->pub environments as is described in the Q.
Jul
23
awarded  Good Question
Jul
22
comment Strategy for keeping secret info such as API keys out of source control?
The build server is the development machine, which is why I'm concerned about this info possibly getting checked into source control accidentally.
Jul
22
comment Strategy for keeping secret info such as API keys out of source control?
@DonalFellows: Configuration files tend to live in the same project as the source code, and get published to the web along side of the built assemblies.
Jul
22
comment Strategy for keeping secret info such as API keys out of source control?
@Dainius: Yes. I look at every single character my team codes. Seriously. I have no choice. I can't code blindfolded. Not reliably, at least. But I do, because I am my team. I'm the I in TEAM. There's one developer, and it's me. I'm him. Yes. I'm the guy who is going to screw this up if he doesn't do it right. Me.
Jul
22
awarded  Nice Question