Only works if you can convince a non-trivial number of people to enter in the CAPTCHA at a specific time corresponding to when the tickets going on sale. There's about a 5 minute window to hammer the servers (though some really big acts can sell out in under a minute).
The trick I thought of would be to tell users that new photo/video galleries are posted at 9 or 10am (the time tickets go on sale).
Hibernate makes all of Java worth it. I probably spend most of my weekly swear-word arsenal allotment on Hibernate, but fuck if it isn't the most powerful tool for connecting a web front end to a complex database schema (complex == dozens/hundreds of tables, stored procedures, complex joins, etc.)
Re:Can someone who understands the IRS explain?
on
Our Low-Tech Tax Code
·
· Score: 1
It doesn't matter if you call yourself a consultant or work out of some sort of shonky staffing agency, and more importantly it doesn't matter if your employer calls you a consultant and hires you through some shonky staffing agency.
You're forgetting an important angle: how this affects staffing agencies. I've had plenty of experience with employee/staffing agency relationships that can best be described as indentured servitude. The agencies only pay for health care after working for a year (or more) through them. The companies that hire through staffing agencies wind up paying what it would cost to hire a competent private contractor, except the agency gets 25% of that trimmed off the top.
They rope contractors in with promises of "temp-to-hire," but try not to bring attention to the fact that you have to be bought out of your "contract" with the agency before you can be employed by the company.
So, talented programmer Mr. C goes to work with Agency A, Inc. Agency A gets Mr. C a part-time gig paying $40/hr. working for Company Co. Company Co. is actually paying $60/hr. to the agency for this privilege. Company Co. decides they love Mr. C and want to hire him full-time. They now have to buy out Mr. C's contract from Agency A. The price? Approximately a year's salary. The better the contractor, the more they'll charge (obviously, since they're losing such a great employee).
Because there is enormous financial dis-incentive for Company Co. to hire Mr. C, they opt to find someone else to fill the full-time position when Mr. C's contract is up. And what happens to Mr. C? Back into joblessness, at least until the Agency can find them another gig.
Re:Can someone who understands the IRS explain?
on
Our Low-Tech Tax Code
·
· Score: 1
Even giving each other advice on how to stay out of trouble?
I think I speak for the majority of Slashdot users when I say, kindly but emphatically, shut the fuck up. It's hard enough to get people who actually know what the hell they're talking about to take the time to enrich the discussion, but with some professions (legal, medical) there is additional liability risk; the natural, easiest reaction would be to simply refrain from the discussion altogether, which would make this place an uninformed echo-chamber filled with idiots like yourself.
There was no advice given, just knowledge that contributes to collective understanding to issues that are traditionally fairly complex for the layman. As a fellow layman, I appreciate the effort.
Animation can add another level of context to the user interface. For instance, status messages with fading background colors (made popular by 37Signals with their Yellow-Fade Technique)--that's animation, but it's used subtly, sparingly and appropriately, so it gets a pass.
The places where it is simply unforgivable to use animation is in scroll effects, form fields or menu items. I always end up using nLite when I reinstall an operating system because it lets you create new installs that have all that CRAP turned off. It's astonishing how much snappier your computer feels.
And then drop off my film to get it processed. And then wait for it to get processed. And then scan it with my film scanner. And then correct it in Photoshop. And then go to Google Maps and try and remember just where I was when I took the shot. And then extract the longitude & latitude from the Google Maps URL. And then convert the longitude & latitude from decimal to radians. And then tag my photo with appropriate tags.
4. The goal is reduce the number of Windows installations using pirated copies many of which include malicious code.
Ah, so you're actively trying to limit your deployment base? Microsoft is only relevant because it's everywhere. It's only everywhere because it historically has been trivial to pirate. Nice work shooting yourselves in the foot.
To all the XP haters... THIS is why I will never upgrade. No tangible benefits, a larger footprint, and now a wonderful, I-never-would-have-expected-this-from-Microsoft! update to remind you just who's system you're using. Hint: not yours.
That's funny, when I saw the book cover thumbnail, I thought it was a picture of a timelord, then realized there was no ceremonial headpiece, and thought it must be a Gallifrey Citadel Guard.
Does anyone have tips on how to convince them to move to IE8?
Tell them that Google has stopped supporting IE6. That's the straw that broke my financial services co.'s back. We still "support" IE6 in the sense that it *should* work, but through the transitional period we're throwing an alert (through browser detection) that basically tells users, "IE6 support is ending, so if things look wacky... upgrade."
people don't throw bugs over the fence to the only dev that is working with that bit (who happens to be on vacation for three weeks)
Yes, this is the biggest threat with code ownership--having to rely on that "one guy" to fix something means you're fucked if that person gets fired or hit by a bus.
The answer to this is what I like to call the sensei-model. One dev is a code owner, and another dev is their shadow. It's the code owner's responsibility to ensure their shadow knows the code as well as they do. Usually this is accomplished by starting them out on small fixes or features so they can get a feel for the structure.
Businesses are afraid of letting developers feel like it's "their code" but in every case I've seen, when you have people who have no sense of ownership you get shit code. Absolute abominations. Why? Because the developer couldn't care less about good structure as long as it "just works." Which is fine and dandy for their release, but heaven help the poor sucker that has to maintain their crap.
Which inevitably leads to more crap piled upon crap. "Well, what's the point in rewriting this awful code? I'm not going to take the time just to make it architecturally sound, because it's not my baby anyway. I'll just tack on my functionality and send it on its way."
Some would say that if you're working nights and weekends, that's a sign you need a better iterative development methodology (like agile).
HA! You try justifying a major rewrite just to make things "structurally better" to the pencil-pushers and they'll come back to you with three letters: R.O.I. "So, let me get this straight: you want to take a few developers and rewrite something that already works, and in the end after however-many weeks, we end up with a product that's exactly the same in terms of features?" Yeah, right.
I didn't read the GP, but I noticed the first line "In Chinese, then back to English" and decided to deliberately not read the GP until after reading the translation. I am seriously impressed. Especially since it was English/Chinese/English, both notoriously difficult languages for the non-native speaker.
I dunno, from the horror stories I hear about Rogers et. al., I think you're probably better going to Finland/Sweden/Norway if you want good, cheap internet and don't mind the cold. Plus, I hear they have cuter girls.
Good Agile, Bad Agile by Steve Yegge at Google is an excellent article on the pros and (mostly) cons of Agile development.
Personally my single biggest problem with Agile is that it specifically de-emphases code ownership (mental ownership, not economic). In my experience as a developer, the only way you get people to go the extra mile on a project (working nights, weekends, whenever and whatever it takes) is when they feel like that code is theirs.
The other big problem I have is that whenever I see someone talking about Agile development it always feels like they're trying to sell me Amway products. It has the same, almost proselytizing tone that a Born-Again preacher takes when they're holding out the money-jar.
I remember as well. My father was an aeronautical engineer that worked on the main engines and related controls in the cabin (Honeywell was the contractor). I was in elementary school, and every launch he would get me a mission patch and autographs when he got to meet the crew. I was the king during show-and-tell.
Mike Smith's (captain) was the last autograph I got. After that the whole atmosphere changed. I still get teary thinking about it.
photographing naked children is some next level shit to put it bluntly.
Yeah, because that's exactly what they're doing. Taking photographs. And then they're putting them in glass and hanging them up on display. And after all the children have been scanned and photographed, they have actual ballots where you have to vote for the sexiest naked child on the plane. The winning child? They're your in-flight meal.
Slashdot Mirror
Only works if you can convince a non-trivial number of people to enter in the CAPTCHA at a specific time corresponding to when the tickets going on sale. There's about a 5 minute window to hammer the servers (though some really big acts can sell out in under a minute).
The trick I thought of would be to tell users that new photo/video galleries are posted at 9 or 10am (the time tickets go on sale).
Sounds like health insurance.
This is easily the single fastest way to get programmers to concentrate on or give a shit about the performance of their code.
Give them a crappy box.
Hibernate makes all of Java worth it. I probably spend most of my weekly swear-word arsenal allotment on Hibernate, but fuck if it isn't the most powerful tool for connecting a web front end to a complex database schema (complex == dozens/hundreds of tables, stored procedures, complex joins, etc.)
It doesn't matter if you call yourself a consultant or work out of some sort of shonky staffing agency, and more importantly it doesn't matter if your employer calls you a consultant and hires you through some shonky staffing agency.
You're forgetting an important angle: how this affects staffing agencies. I've had plenty of experience with employee/staffing agency relationships that can best be described as indentured servitude. The agencies only pay for health care after working for a year (or more) through them. The companies that hire through staffing agencies wind up paying what it would cost to hire a competent private contractor, except the agency gets 25% of that trimmed off the top.
They rope contractors in with promises of "temp-to-hire," but try not to bring attention to the fact that you have to be bought out of your "contract" with the agency before you can be employed by the company.
So, talented programmer Mr. C goes to work with Agency A, Inc. Agency A gets Mr. C a part-time gig paying $40/hr. working for Company Co. Company Co. is actually paying $60/hr. to the agency for this privilege. Company Co. decides they love Mr. C and want to hire him full-time. They now have to buy out Mr. C's contract from Agency A. The price? Approximately a year's salary. The better the contractor, the more they'll charge (obviously, since they're losing such a great employee).
Because there is enormous financial dis-incentive for Company Co. to hire Mr. C, they opt to find someone else to fill the full-time position when Mr. C's contract is up. And what happens to Mr. C? Back into joblessness, at least until the Agency can find them another gig.
Even giving each other advice on how to stay out of trouble?
I think I speak for the majority of Slashdot users when I say, kindly but emphatically, shut the fuck up. It's hard enough to get people who actually know what the hell they're talking about to take the time to enrich the discussion, but with some professions (legal, medical) there is additional liability risk; the natural, easiest reaction would be to simply refrain from the discussion altogether, which would make this place an uninformed echo-chamber filled with idiots like yourself.
There was no advice given, just knowledge that contributes to collective understanding to issues that are traditionally fairly complex for the layman. As a fellow layman, I appreciate the effort.
Because lawyers cost money, and insurance companies have more of both.
Pardon my mercenary attitude, but why exactly would they want to insure you?
See also:
I though Massachusetts had that sweet universal healthcare
MA has sweet mandated universal buy-in for health insurance. The degree to which this translates into actual health care is, well, arguable.
using SHA1 hashes to check for dublicates - I even took the possibility of a hash collision into account and only used them as an index
This is why you always use a surrogate key and compare the hashes later in a validation routine. /normalization nazi
Animation can add another level of context to the user interface. For instance, status messages with fading background colors (made popular by 37Signals with their Yellow-Fade Technique)--that's animation, but it's used subtly, sparingly and appropriately, so it gets a pass.
The places where it is simply unforgivable to use animation is in scroll effects, form fields or menu items. I always end up using nLite when I reinstall an operating system because it lets you create new installs that have all that CRAP turned off. It's astonishing how much snappier your computer feels.
How can we expect to increase the font size if we can't event read the words?
One word for you:
memorization.
This is why I shoot film on an old manual camera.
And then drop off my film to get it processed.
And then wait for it to get processed.
And then scan it with my film scanner.
And then correct it in Photoshop.
And then go to Google Maps and try and remember just where I was when I took the shot.
And then extract the longitude & latitude from the Google Maps URL.
And then convert the longitude & latitude from decimal to radians.
And then tag my photo with appropriate tags.
Privacy for the fail.
4. The goal is reduce the number of Windows installations using pirated copies many of which include malicious code.
Ah, so you're actively trying to limit your deployment base? Microsoft is only relevant because it's everywhere. It's only everywhere because it historically has been trivial to pirate. Nice work shooting yourselves in the foot.
To all the XP haters... THIS is why I will never upgrade. No tangible benefits, a larger footprint, and now a wonderful, I-never-would-have-expected-this-from-Microsoft! update to remind you just who's system you're using. Hint: not yours.
1. trivial to write, therefore useless
2. impossible to write, therefore useless
This has been my experience as well.
That's funny, when I saw the book cover thumbnail, I thought it was a picture of a timelord, then realized there was no ceremonial headpiece, and thought it must be a Gallifrey Citadel Guard.
Apparently I am a giant hulking geek.
Does anyone have tips on how to convince them to move to IE8?
Tell them that Google has stopped supporting IE6. That's the straw that broke my financial services co.'s back. We still "support" IE6 in the sense that it *should* work, but through the transitional period we're throwing an alert (through browser detection) that basically tells users, "IE6 support is ending, so if things look wacky... upgrade."
people don't throw bugs over the fence to the only dev that is working with that bit (who happens to be on vacation for three weeks)
Yes, this is the biggest threat with code ownership--having to rely on that "one guy" to fix something means you're fucked if that person gets fired or hit by a bus.
The answer to this is what I like to call the sensei-model. One dev is a code owner, and another dev is their shadow. It's the code owner's responsibility to ensure their shadow knows the code as well as they do. Usually this is accomplished by starting them out on small fixes or features so they can get a feel for the structure.
Businesses are afraid of letting developers feel like it's "their code" but in every case I've seen, when you have people who have no sense of ownership you get shit code. Absolute abominations. Why? Because the developer couldn't care less about good structure as long as it "just works." Which is fine and dandy for their release, but heaven help the poor sucker that has to maintain their crap.
Which inevitably leads to more crap piled upon crap. "Well, what's the point in rewriting this awful code? I'm not going to take the time just to make it architecturally sound, because it's not my baby anyway. I'll just tack on my functionality and send it on its way."
Some would say that if you're working nights and weekends, that's a sign you need a better iterative development methodology (like agile).
HA! You try justifying a major rewrite just to make things "structurally better" to the pencil-pushers and they'll come back to you with three letters: R.O.I. "So, let me get this straight: you want to take a few developers and rewrite something that already works, and in the end after however-many weeks, we end up with a product that's exactly the same in terms of features?" Yeah, right.
I didn't read the GP, but I noticed the first line "In Chinese, then back to English" and decided to deliberately not read the GP until after reading the translation. I am seriously impressed. Especially since it was English/Chinese/English, both notoriously difficult languages for the non-native speaker.
Google's done an excellent job.
I dunno, from the horror stories I hear about Rogers et. al., I think you're probably better going to Finland/Sweden/Norway if you want good, cheap internet and don't mind the cold. Plus, I hear they have cuter girls.
Good Agile, Bad Agile by Steve Yegge at Google is an excellent article on the pros and (mostly) cons of Agile development.
Personally my single biggest problem with Agile is that it specifically de-emphases code ownership (mental ownership, not economic). In my experience as a developer, the only way you get people to go the extra mile on a project (working nights, weekends, whenever and whatever it takes) is when they feel like that code is theirs.
The other big problem I have is that whenever I see someone talking about Agile development it always feels like they're trying to sell me Amway products. It has the same, almost proselytizing tone that a Born-Again preacher takes when they're holding out the money-jar.
I remember as well. My father was an aeronautical engineer that worked on the main engines and related controls in the cabin (Honeywell was the contractor). I was in elementary school, and every launch he would get me a mission patch and autographs when he got to meet the crew. I was the king during show-and-tell.
Mike Smith's (captain) was the last autograph I got. After that the whole atmosphere changed. I still get teary thinking about it.
photographing naked children is some next level shit to put it bluntly.
Yeah, because that's exactly what they're doing. Taking photographs. And then they're putting them in glass and hanging them up on display. And after all the children have been scanned and photographed, they have actual ballots where you have to vote for the sexiest naked child on the plane. The winning child? They're your in-flight meal .
Get a fucking grip, you loon.
Sure, after the ten years you spend writing it.