Haha. So rather than use a cheap natural solution it's better to get the expensive patented synthetic stuff. Riiiiiight... Now I see.
Sure! You see, it's nicotine that's bad for you not the 99.9% of cancer-inducing crap in cigarette smoke, noooo sir!!!!
No go and buy the "expensive patented synthetic stuff" that we say it's safe, trust us, never mind in a few years we'll figure that it causes kidney failure or cancer of the toes or whatever.
to something totally unmaintainable due to lack of readability is not a good trade off.
I'm not sure what you meant. But I second it.
(Automatically) converted code is usually _a_huge_mess_. You lose context, (may lose) variable names, general structure of code, the converter doesn't "think java", some things may be converted to overly complicated pieces, etc, etc Also, the original programmers are subject to restrictions that today we don't have.
Condoms that are too wide kill it for me -- it feels like having a sandwich bag on.
I think I know how you feel, even though the 'sandwich bag effect' is not that bad for me.
Problem is, they are so tight (for me) I cannot unroll them. (not in the whole). I then go for the 55mm diameter (the largest one that's easily available here) and still is difficult to unroll.
All in all, it's a lot of manouvers to get it properly placed.
Pick up that trail. Even if just for conversation. Try to join a band ('fairly good' can certainly make it), . Or just join guys that have a band and go watch their concert.
1 - Enterprisy looking 2 - Easy to gamble by the interested
Your boss wants a number, give it to them quickly. It's all BS (or 99% of it at least. Don't agree? Do the job then) in the end.
So good metrics could be.
- Unplanned downtime - Number of users, number of bytes used, etc (that plots a nice ascending graph, and ASCENDING IS GOOD, you can print that and put it in the wall)
If they stay on 'time to close the ticket' NEEDINFO and WORKSFORME is your friend.
Parent post is insightful. If a model is flexible enough, it can fit any data.
No
If a model is flexible as to fit any data, then it's useless (need refining)
Also, a model that's too flexible can't make testable predictions. And that's not only for the science, but the whole reason why people research stuff, that is, 'if this works like this thn if we do this and that we have this think that's cool because of..."
In a more serious note, my personal opinion is have the developers use and test the programs in slower machines.
Yes, they can profile the app, etc, but the problem is that it really doesn't create the 'sense of urgency' working in a slow machine does. (Note I'm not saying developers should use slow machines to DEVELOP, but there should be a testing phase in slow machines)
Also, slower machines produce more obvious profile timings.
Slashdot Mirror
Initial research indicated that nicotine is not carcinogenic, but more recent studies are suggesting that may not be so.
http://toxsci.oxfordjournals.org/cgi/content/full/79/1/1
I know big-tobacco is evil but the anti-tobacco crowd is also getting MADD...
Next thing I know they will come out with a research that proves that looking at a pack of cigs causes cancer...
Haha. So rather than use a cheap natural solution it's better to get the expensive patented synthetic stuff. Riiiiiight... Now I see.
Sure! You see, it's nicotine that's bad for you not the 99.9% of cancer-inducing crap in cigarette smoke, noooo sir!!!!
No go and buy the "expensive patented synthetic stuff" that we say it's safe, trust us, never mind in a few years we'll figure that it causes kidney failure or cancer of the toes or whatever.
Well that's unfair, it should be named after me, I was the first to have it...
Just think about it, knowing the size beforehand is a _huge_ advantage.
Remember people that put strlen() inside a 'for'? Stupid in C, in Pascal it's constant time (and very fast)
Who's the fscking idiot who thought having \0 indicate end-of-string was a good idea??!!?
I cannot remember something that gave more _grief_ and _problems_ than that.
I like CentOS a lot, but still
It's open source, if anything goes _really_ wrong, fork. The source is there, all references to the "Proeminent Linux vendor" properly stripped, etc
It's less work than start from scratch again from the "proeminent linux vendor"
So with used condoms it's a "Special Black Pudding" and it costs twice as much I guess.
Dumb question, why put these things in a container and ship instead of incinerating??
Actually I'm more concerned with Debian running out of Toy Story characters...
They can't reshoot it without Michael Jackson
You're right, 'borrow to' should have rang a bell :)
TCP is as reliable as borrowing a brand new Ferrari to the crack dealer on the street corner.
UDP of course, is less reliable than that. The Ferrari is rigged with a bomb.
to something totally unmaintainable due to lack of readability is not a good trade off.
I'm not sure what you meant. But I second it.
(Automatically) converted code is usually _a_huge_mess_. You lose context, (may lose) variable names, general structure of code, the converter doesn't "think java", some things may be converted to overly complicated pieces, etc, etc Also, the original programmers are subject to restrictions that today we don't have.
Think: string operations, db operations, etc
Condoms that are too wide kill it for me -- it feels like having a sandwich bag on.
I think I know how you feel, even though the 'sandwich bag effect' is not that bad for me.
Problem is, they are so tight (for me) I cannot unroll them. (not in the whole). I then go for the 55mm diameter (the largest one that's easily available here) and still is difficult to unroll.
All in all, it's a lot of manouvers to get it properly placed.
However, if the study is "how can we FIX what men don't like about condoms", then the study becomes very important,
Well, that's a tough one...
INCREASE ITS BLOODY DIAMETER, THAT'S HOW
but I'm also a fairly good pianist/keyboardist
Pick up that trail. Even if just for conversation. Try to join a band ('fairly good' can certainly make it), . Or just join guys that have a band and go watch their concert.
There are chicks there.
So this is the new iLiver 3G Ass, two body parts in the same package.
s/metrics/bullcrap
A good metric should be
1 - Enterprisy looking
2 - Easy to gamble by the interested
Your boss wants a number, give it to them quickly. It's all BS (or 99% of it at least. Don't agree? Do the job then) in the end.
So good metrics could be.
- Unplanned downtime
- Number of users, number of bytes used, etc (that plots a nice ascending graph, and ASCENDING IS GOOD, you can print that and put it in the wall)
If they stay on 'time to close the ticket' NEEDINFO and WORKSFORME is your friend.
That's easy.
Convert the bazillion videos in youtube to Theora and store them in two formats.
Don't forget about the whole 'TV Licensing' thing in the UK
I guess the PC manufacturer will preinstall something.
ls | grep
amiright?
NO!
find | grep
Well, in wikipedia they put [citation needed] if you write "the sky is blue"
Parent post is insightful. If a model is flexible enough, it can fit any data.
No
If a model is flexible as to fit any data, then it's useless (need refining)
Also, a model that's too flexible can't make testable predictions. And that's not only for the science, but the whole reason why people research stuff, that is, 'if this works like this thn if we do this and that we have this think that's cool because of..."
Not really a negative step, more like an step belonging to a Lie Group...
It's simple, just don't use Java
In a more serious note, my personal opinion is have the developers use and test the programs in slower machines.
Yes, they can profile the app, etc, but the problem is that it really doesn't create the 'sense of urgency' working in a slow machine does. (Note I'm not saying developers should use slow machines to DEVELOP, but there should be a testing phase in slow machines)
Also, slower machines produce more obvious profile timings.