That one guy who successfully signed up for Obamacare...

10 Oct 2013 21:41 #51 by Venturer

Brandon wrote:

WindPeak wrote: Thanks Brandon. I used to be a programmer. Website is overwhelmed with programs of faulty coding used to build their database. It will implode on itself.


Let's see an example of that.


Already in progress. Try accessing the database yourself. Tell me how long it takes you to get any information. Good Luck!

Please Log in or Create an account to join the conversation.

10 Oct 2013 21:50 #52 by Brandon
No. I want to see an example of "faulty coding used to build their database," causing to to "implode." And I obviously couldn't "access the database." I could try to use the website.
What languages did you program in and when?

Please Log in or Create an account to join the conversation.

10 Oct 2013 22:00 #53 by FredHayek

Brandon wrote:

Walter L Newton wrote: washington.cbslocal.com/2013/10/10/hawai...o-software-problems/

Glad to help.


Look, I understand that at the end of your life...with the good years long gone...and the country leaving you behind...you want to believe that there's no future. But there is. It just doesn't include you, and within a generation it won't include the repuglican party either.


lol And you act just like an ACA apologist. :smackshead:

Thomas Sowell: There are no solutions, just trade-offs.

Please Log in or Create an account to join the conversation.

10 Oct 2013 22:01 #54 by Venturer
Sorry you will have to google itself yourself. I read enough of them about Experian (sorry about the spelling) and a lot of useless code embedded besides being useless in accessing the website's program aka DATABASE. Google it. They use 'database' extensively.

Brandon wrote: No. I want to see an example of "faulty coding used to build their database," causing to to "implode." And I obviously couldn't "access the database." I could try to use the website.
What languages did you program in and when?

Please Log in or Create an account to join the conversation.

10 Oct 2013 22:08 #55 by Brandon

WindPeak wrote: Sorry you will have to google itself yourself. I read enough of them about Experian (sorry about the spelling) and a lot of useless code embedded besides being useless in accessing the website's program aka DATABASE. Google it. They use 'database' extensively.


So if I Googled "flat earth" and found someone telling me the earth was flat, would it be proven true by your standards?

Please Log in or Create an account to join the conversation.

11 Oct 2013 05:15 #56 by Reverend Revelant

Brandon wrote: No. I want to see an example of "faulty coding used to build their database," causing to to "implode." And I obviously couldn't "access the database." I could try to use the website.
What languages did you program in and when?

Jyoti Bansal: Based on my experience, the challenges look like glitches in software code. And the software code didn’t go through enough testing. It would take some time to find the bugs.

Then there are bugs in scalability, what happens when 100 people or more are trying to do the exact same thing. Those are the things that really need tuning at this point.
Most of the problems like these are in the software. Hardware is the easy part. You can add more hardware and do it easily. Software takes more time. In the rush of getting this out, it seems like testing wasn’t done completely. My expectations from this is that these problems should go away in the next few weeks. The site still won’t be as fast as something like Netflix, but it should work.

...

SK: The Obama administration has said that all these problems are happening because of overwhelming traffic. How good of an explanation is that?

JB: That seems like not a very good excuse to me. In sites like these there’s a very standard approach to capacity planning. You start with some basic math. Like, in this case, you look at all the federal states and how many uninsured people they have. Out of those you think, maybe 10 percent would log in in the first day. But you model for the worst case, and that’s how you come up with your peak of how many people could try to do the same thing at the same time.

http://www.washingtonpost.com/blogs/won ... -problems/


And before you ask me too...

Walter L Newton wrote: My expertise is in Visual FoxPro and Oracle PL/SQL (and all of the Oracle design tools such as Oracle Reports and Oracle forms). Those are two language platforms I spent most of my formidable programming career in.

I've spent the last 2 1/2 years working in Delphi Pascal (which I basically learned as on the job training).

I can do maintenance coding on existing Visual Basic applications (I haven't had much experience in designing Access applications right out of the box), I spent 6 months writing in Microsofts .NET (but I didn't retain those skills after that job was over).

And my Information Technology career started in 1978. I've spent most of my time in database design and the software front end that "talks" to the database.


The ACA website is using standard HTML and CSS for the page design (just use "show source" in your browser to see the actual page coding) , Javascript plugins and functions on the client side (the user) and the back end (database) is an Oracle database (Oracle is the Federal government standard for their databases).

Don't imply I can't detect tell buggy, badly written code and GUI's.

Waiting for Armageddon since 33 AD

Please Log in or Create an account to join the conversation.

11 Oct 2013 07:13 #57 by Brandon
Since you've previously repeated that the quality of the code was good enough for government work, I conclude from your post above that the problem was poor capacity planning.
Again, it's 'bagger logic...ACA is a failure because so many people want to use it.

Please Log in or Create an account to join the conversation.

11 Oct 2013 07:14 #58 by FredHayek
Is it true that the hacks into ACA were already known months ago?

Maybe you tech guys can hack yourself some free healthcare?

Thomas Sowell: There are no solutions, just trade-offs.

Please Log in or Create an account to join the conversation.

11 Oct 2013 07:16 #59 by FredHayek

Brandon wrote: Since you've previously repeated that the quality of the code was good enough for government work, I conclude from your post above that the problem was poor capacity planning.
Again, it's 'bagger logic...ACA is a failure because so many people want to use it.


A few people are saying it wasn't setup for all the people who want to apply, but I am hearing more complaints that it is a crap piece of software.

Thomas Sowell: There are no solutions, just trade-offs.

Please Log in or Create an account to join the conversation.

11 Oct 2013 07:20 #60 by Brandon
I don't care what you hear. I might be slightly interested in things you can prove, but you don't do that.

Please Log in or Create an account to join the conversation.

Time to create page: 0.152 seconds
Powered by Kunena Forum
sponsors
© My Mountain Town (new)
Google+