Mike Wills

233 reputation

bio	website	mikewills.me
	location	Minnesota
	age	33
visits	member for	2 years, 8 months
	seen	Mar 25 at 16:21
stats	profile views	14

After going to school to become a network administrator, Mike, fell in love with programming. He has been a midrange (IBM i, iSeries, AS/400) developer since 2000. He has since added ASP.NET to to his toolbox (around 2006) and now does dual duty writing/supporting green-screen applications and ASP.NET internet and intranet applications. He does a lot of integration between the IBM i and ASP.NET.

Besides his programming day job, he dabbles in PHP and many other areas of tech.

You can find him on his website, @BizDevTalk, Facebook, and Google+

	233 reputation	bio	website	mikewills.me	visits	member for	2 years, 8 months
18 badges		location	Minnesota		seen	Mar 25 at 16:21

summary answers questions tags badges favorites bounties reputation activity

27 Actions

suggestions reviews revisions comments badges posts accepts all

Nov 1	comment	How would I implement this application idea? About 25 to start with and probably will grow as I add additional features. I know there isn't any database limitation. Really, I want to use NoSQL so I can learn what it can do.
Nov 1	comment	How would I implement this application idea? It's more like what do I send to the server when I update a field? Does the entire form get sent, just the field?
Nov 1	comment	How would I implement this application idea? That sounds interesting. I'll take a look into it. The main user will be me and a few of the group may use it as well.
Nov 1	asked	How would I implement this application idea?
Jun 21	revised	Forking project on Github process edited title
Jun 21	awarded	Citizen Patrol
Jun 21	awarded	Yearling
Jun 20	awarded	Scholar
Jun 20	accepted	Forking project on Github process
Jun 19	awarded	Nice Question
Jun 19	asked	Forking project on Github process
Oct 11	awarded	Commentator
Oct 11	comment	Should the admin interface of a public-facing webapp be accessible externally? From day 1 when we started eCommerce, we set the rule. "We do not store credit card numbers."
Oct 11	comment	Should the admin interface of a public-facing webapp be accessible externally? Customer data is billing contact (address, email, phone). That is all.
Oct 11	comment	Should the admin interface of a public-facing webapp be accessible externally? The only identifying information in that table is the Order Id and Transaction Id. No actual credit card information. We don't even store the last 4 digits of the CC number. We then log the customer name and contact info (address, email, phone) for reporting purposes to bring that information internal for our financial systems. We use First Data. What they return back in their web service is what we store. Saving us from looking up that information in their web portal and on our side to see what went wrong. Hopefully.
Oct 11	comment	Should the admin interface of a public-facing webapp be accessible externally? This would be basic for payment troubleshooting and then exporting the previous day's transactions in case of problems with the automated system.
Oct 11	comment	Should the admin interface of a public-facing webapp be accessible externally? Hmm... we'll have to research what we can and can't store then.
Oct 11	awarded	Student
Oct 11	comment	Should the admin interface of a public-facing webapp be accessible externally? True, my other concern is those that explore and how to better hide the admin. But moving it internal would fix that.
Oct 11	awarded	Editor