bproctor

I've memorized an algorithm instead of trying to remember passwords. I don't actually remember hardly any of my passwords, instead I use this mini algorithm that I came up with to create unique passwords for each site I go to. Each time I go to a site it just takes me a couple seconds to figure out what the password is. I find it a lot easier to remember that one algorithm rather than trying to remember a bunch of passwords or rotating through the same few passwords.

I don't believe this is necessarily a bug. All code will break under some extremes and nowhere are the requirements specified for what this code is supposed to be able to handle. Without requirements, you can't "prove" it correct (or incorrect for that matter).

Amazon has a program called KDP. If an author puts their book into the KDP program they receive 70% royalties, but they have to be exclusive on Amazon. If they don't want to be on KDP, they only receive 35% royalties, but they can sell anywhere. That's how Amazon is making itself into a monopoly.

edit: I mean KDP Select, not KDP.

Not really. Print books don't get the author hardly anything at all. My wife is an author, exclusive on Amazon so she makes ~70% on ebook sales. The profit from a print book is next to nothing. Of course, this can vary a lot on the type and price of the book.

Yeah, I don't understand this article. My building has a 1 story basement, street level is retail space, the next 6 floors are parking, and above that 24 floors of apartments. You can't easily tell from the outside what is apartments and what is parking without looking close. I also live in Seattle only blocks away from where this guy is talking about.

I pretty sure he meant most of his friends work at big companies.

Fabric FTW

Maybe because the customer doesn't want to be bothered?

I'm not necessarily siding one way or the other, but that article by Stella Matsovis was absolutely terrible and has zero credibility.

I don't think there is enough information in this article to be making judgement calls.

I'm pretty sure he was joking

Not really. Since my wife started writing she's averaging about 2 1/2 to 3 months. And that includes the 2-3 weeks waiting on the copy editor.

tl;dr I'll get around to reading this later...

Did you read his blog? That's an extreme exaggeration of what he said.

I think whether or not it's a good idea to launch has to do with what those bugs are. The number of bugs is pretty much irrelevant.

netteller (I think was the name?), an online banking system used by many smaller banks, including the bank I used to bank at in Tennessee, used to require passwords be exactly 6 alphanumeric characters. This didn't change until just a year or two ago. Scary.

I worked for the TSA for about 6 months a few years ago. They convince employees that catching a knife from some traveler who forgot to put it in their checked baggage is a huge win and that somehow we saved the day yet again. Happened on a daily basis.

Our biggest catch while I was there: one day we caught a guy with a sword. The guy obviously didn't know what he was doing, apologetic, and confused. Of course, our managers talked it up as a big win for TSA security. Can you imagine a terrorist trying to take over a plane with a sword?

6. I don't have an idea

This is supposed to be a joke, right?

I don't know whose life works in this extremely simple way, but it sure isn't mine. I've gone from making good money to being broke to making good money again and everywhere in between in my 35 years on this planet.

These types of things never make any practical sense because they assume I'm going to be working at the same job for the same pay for the next 30 years or so. Maybe that was the norm in the '60s but few people do that anymore.

Saving money is good, no doubt, but if you're concerned about retiring early, you're much better off figuring out how to do it by making more money.

dowtrack.com

I've wrote my own OS back in the late '90s based heavily on this book. Probably one of the best learning experiences I've had. I'm not sure how relevant it is today. I'd love to see a second edition brought up to date.

It's not so easy to tell. In the early '90s I did a lot of x86 assembly. I haven't done any assembly in at least 15 years or so. Looking back I can't really tell if it's good or not. And if I tried to do any assembly at this point I'm sure it would be awful. On the flip side, back then I didn't know any javascript so I supposed I've improved 100% in that area.

I've worked at companies where this seems to happen often and it usually comes down to two things:

1) Poor communication and/or planning as far as what the end result was supposed to be. The developer built it the way they thought it was supposed to work, they find out later that it's incorrect or the specifications for it keep changing making the developer add one hack after another to get it to do what it needs to do. They'd probably like to just rewrite the whole thing, but by now it's too late.

Jr vs Sr: Sr can see this coming and does whatever he/she can do to minimize it. Doesn't necessarily mean they can stop it from though, it might be too high up the chain of command.

2) Little to no testing. The developer built it and said "done" and then it was passed on to the end user. Anything of any complexity is going to be riddled with bugs if there isn't some kind of QA process in between. Developers typically suck and QAing their own work.

Jr vs Sr: Sr has more experience to see possible problems before they become problems and if no QA procedure exists, will at least try to run it by a colleague before claiming it "done".

Password reset questions are the problem. Their a back door into your account. I hate when a site forces me to enter them. When I do, I answer then with something completely different than what the question is.

I'd guess it's a pretty big corner

I'd be curious in hearing more about why the FBI and law enforcement brought on this fear campaign against it. Hippies "irked" them isn't really an explanation.

It's a nice thought, but for me at least, marketing has ruined my trust in businesses, and my initial reaction to this email would be "buzz off, if I wanted to buy more of your stuff, I'd go to your site. Leave me alone."

I don't know how you would do this without it looking like marketing spam.

I was really hoping this article was going to end with an amazing discovery that showed bubble sort to have some great hidden potential.

Why can't you find out the same information about the persion by just engaging in normal conversation, asking them about their interests, and asking reasonable follow up questions?

Presenting it as some kind of weird test that makes the interviewee feel awkward and suspicious is no way to conduct an interview. It says more about how bad the interviewer is.