|
Chris Losinger wrote: utter BS.
...much like the 2500+ pages of the law itself and the 10,500 pages of its regulations.
Government is not reason; it is not eloquent; it is force. Like fire, it is a dangerous servant and a fearful master. ~ George Washington
|
|
|
|
|
IT takes a lot of code to BS everyone that signs up...all 6 of em!
|
|
|
|
|
the front end of Healthcare.gov is written in Ruby on Rails?
Really?
modified 20-Oct-19 21:02pm.
|
|
|
|
|
yes. the front end really isn't very tough.
it's the backend stuff that's the hard part: interfacing with all those different govt agencies and insurance carriers.
|
|
|
|
|
That explains the mess.
They should have reversed it, and let the govt agencies and insurance carriers adjust to them instead.
Politicians are always realistically manoeuvering for the next election. They are obsolete as fundamental problem-solvers.
Buckminster Fuller
|
|
|
|
|
Now, now. That wouldn't have given cronies contractors a nice kickback now would it?
|
|
|
|
|
And it was the contractors that made the specifications I suppose...
Politicians are always realistically manoeuvering for the next election. They are obsolete as fundamental problem-solvers.
Buckminster Fuller
|
|
|
|
|
<quote>the front end really isn't very tough
Indeed
I would really like to know who made the decision to choose a platform with known and documented scalability issues.
modified 20-Oct-19 21:02pm.
|
|
|
|
|
Well, I once tried asking a few awkward questions on the Ruby on Rails: Talk[^] mailing list related to security.
I just wanted to know about support for impersonation, constrained delegation, etc. on Windows - and not surprisingly, nobody cared to answer - even if I think I was quite polite about it.
In general I feel that the Ruby on Rails community is more of a religious fraternity, than a programming community - that fraternity, admittedly have a few very tallented members, but in general they, about 90 % of them, are deep into denial that there is sentient life outside their sacred Ruby On Rails fraternity.
|
|
|
|
|
Well, the whotzitgov thing is obviously a fantasy, but are there really five million lines in the XBox DVD player?
Why on Earth would it want a number even approaching that? What does it do that you can't do in a few thousand?
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
|
|
|
Gak. Fixed it. Thanks. Odd how it seems that sometimes when I paste a link there's an 'http://' prefix and sometimes there isn't.
|
|
|
|
|
mikepwilson wrote: Read this and realize that while the tools have advanced, the techniques have backslid since it was produced.
I realize that every time I have to work on any number of legacy systems.
All the examples are written in RatFor, a version of Fortran that adds some more structured elements to that early language.
Oh my. RatFor!
Marc
|
|
|
|
|
I think I saw a Pascal translation kicking around the innertoobz someplace.
I did enough Fortran back in The Before Time that it never bothered me.
|
|
|
|
|
Heh,
We just put in a hot shot dell server at a local auto parts store where the server to be replaced had a serial port with the employee fingerprint checkin box for the server based time clock.
I was after my partner who sold it to get a "pcie serial board", "pcie serial board","pcie serial board"
Shae said we'll wait until in comes in to see if it has a serial port... "Oh right", "pcie serial board"
It came ... and had a darn serial port.
I think I'll keep her.
modified 4-Nov-13 23:00pm.
|
|
|
|
|
Ron Anders wrote: It came ... and had a darn serial port.
That's pretty amazing! And if you ever need one, there's a whole variety of USB - RS232 interfaces out there.
Marc
|
|
|
|
|
Too funny.....http://www.youtube.com/watch?v=sSaV3YUGiM8[^]
Edit: here is more info on the comedy musical group.wiki[^]
Sorry if I offended anyone to the point it has been reported, but I do not see it that way at all. :-/
modified 4-Nov-13 18:13pm.
|
|
|
|
|
"just don't take your computer for repair immediately afterwards"
The only instant messaging I do involves my middle finger.
English doesn't borrow from other languages.
English follows other languages down dark alleys, knocks them over and goes through their pockets for loose grammar.
|
|
|
|
|
A man goes into a pub, takes a seat at the bar, and orders five shots. The bartender gives him an odd look since he's all by himself, but he serves up the five shots and lines them up on the bar. The man downs them all quickly. He finishes the last one and calls out, "Four shots, please!"
The bartender serves up four shots and lines them on the bar. The man downs them all. Then he belches loudly, sways slightly on the stool, and orders three. And one after the other, he knocks them back. "Two shots!" he calls, and the bartender places two shots in front of him. Down they go. As the man slams the last one down on the bar, he says, "One shot bartender." So the bartender fills the glass.
The man sits there, staring at it for a moment, trying to focus. Then he looks at the barman and says, "You know, it's a funny thing, but the less I drink, the drunker I get."
/ravi
|
|
|
|
|
Predictable but funny.
|
|
|
|
|
Meh.
You've done better brother.
|
|
|
|
|
Preface ... I knew better but I made the mistake anyway and I just felt like sharing, you probably don't want to read : )
My current mission is to author applications that have never been written before, ever, rapidly, for the power industry on "Massive Amounts" of data for users that want it yesterday but will change their minds constantly. So pretend you want to know how long a users power was out (and I know ahead of time the rules will change on me)
public class Foo{
public DateTime PowerOutTime;
public DateTime PowerOnTime;
public TimeSpan FigureOutJustHowGDLongThePowerWasOut;
public string CustomerId;
}
Populate the list with a few hundred million records, do some work. Output, slow, of course, data-loading takes a long time, up to 60 to 100 seconds for a day. Ignore the fact that I can't do this work in the DB (there are reasons)
First naive mistake, Let's put it in a generic List
List<Foo> items = ...
Sure the data calculation part is fast but for technical reasons this is very slow, (Allocation of contigous memory streams, copying, adding etc). Even better, when you are really sloppy and work with 7 days of customer data System.OutOfMemoryException : ). So what to do? Still blinded by the R.A.D. issue I continued ...
LinkedList<Foo> items = ...
Golden, no longer an out of memory issue for n<some value="" ...="" workable.="" still="" slow.="" heck="" because="" of="" network="" security,="" locality,="" and="" data-source="" issues="" it="" could="" take="" a="" day="" or="" two="" to="" get="" the="" data="" "" ok,="" so,="" why="" not="" copy="" locally="" first="" with="" compressed="" file="" stream="" gravy,="" hundred="" mb="" zipped="" under="" 100mb="" but="" wait,="" is="" this="" so="" slow="" ...
did="" you="" know="" that="" zipping="" operation="" in="" .net?="" (well="" large="" files)="" hdd="" cheap,="" toss="" zip.="" now="" it's="" loading="" more="" reasonably="" reliably.="" oh=""
the="" source="" local="" system
the="" zipped
the="" format="" binary="" small="" (minimally="" so)="" populating="" objects="" processing="" slow
next,="" up,="" well,="" lets="" just="" process="" order="" oops,="" can't.="" would="" have="" be="" sorted="" by="" customer="" date="" very="" (crashed="" oracle="" postgress="" too="" :="" (="" db's="" should="" able="" sort="" another="" issue)="" still,="" ..="" (in="" joker="" serious="" voice)
then="" hit="" me:
<pre="">
"Luke, pretend this is C++ and you are using a struct and a pointer offset"
"Ben, I can't C# doesn't allow safe casting"
"Use the force"
So I mapped the file to memory, created a struct and a static method to do the math for the offsets for the struct in a thread-safe manner and BAM my test set of 100 megs went from 30 seconds to load and process to under 1 second using only one-thread.
Honestly *rolls eyes*.
The worst part is that I can't use the code. Things change to much. At least I know what is causing the issue and worse, technically, I learned in college what was causing the issue at still I ignored it in favor of RAD. It was my crappy code the entire time! (Well not including the fact that the raw sources are still too slow but let's not count things out of my control)
Just remember kids, sometimes you need a better perspective of the problem.
(Oh and as a bonus we are now one step closer to bringing the power back on ... before it goes out but that is confidential : ) )
|
|
|
|
|
Piece-wise memory allocation is painful. For a particular project analyzing end-of-life failure modes on satellite switch rings, I have a function that "simply" spins up a list (several million members) of "random" (but balanced) failures to test. It takes minutes to generate the list, most of this is memory allocations going on behind the scenes of the list management. I never bothered to "un-safe" the algorithm.
And yes, zip is painfully slow. And when I looked at using a serialized zip stream, I discovered it's not a true stream - you can't just shove data in and expect it to stream it out as it works through the compression - the whole damn thing has to be compressed in memory first before it starts spitting out the compressed data to the stream. I discovered that years ago, I think I even wrote an article about it.
Marc
|
|
|
|