"Here’s an idea of pricing for you. I work on projects based on complexity. If you have 100 pages with simple text and images on it, the task is not complex. Just time consuming. So I consider that a complexity of 1, times 100 times. So, complexity is 100.
If you have one page with one complex interactive form, with a calculator, that grabs prices from out there on The Web, then it’s a one page design, but complexity of that one page is way high, depending on all of the features on it. Calculator, 2 points. Search 3 points. Connecting to databases and APIs, 5 points. You get the idea.
Both projects can be about 100 points. One more complex than the other, and one more pages than the other. And now for the prices:
$125 – $250 per point.
That’s it. Why the wide range? Depends on a lot of things. But, on average, I can do about 39 points in two weeks. Considering the overhead, taxes, etc, that comes to about $60-$120 per hour."
"Notice that we added a DOCTYPE to tell browsers what kind of document we have. We picked 4.01 Transitional because of its flexibility to allow deprecated elements, like <font>."
If you know PHP, you know that you shouldn't be doing it like that. He sounds like a novice. There's nothing wrong with that, but when looking at that kind of thing I would take an opinions as a grain of salt
It doesn't really matter what the language is, SQL injection vulnerabilities are serious in any language. A competent web developer understands that -- especially a "Programmer Extraordinaire".
Not listening to the majority, on the other hand, may lead to your project being forked. Take Gnome 3 as an example. This in turn may lose you a significant amount of developers so that you have two projects that each are weaker than the original one. This seems to be an inherent problem with projects like this. The only thing resembling a solution is to have a strong project leader who is able to convince people to trust him or her on radical UX changes.
We aren't convicting them here - this isn't a court. It's just pointing out that, once again, as always:
PayPal
Not only did they screw up; but they also can't man up, tell the truth and be transparent - as usual. Shit happens. Slamming us with a denial that shit happened is implying that you aren't going to do anything about it; admitting it is a clear statement that you are not proud of it and will work to make sure it never happens again.
It's come to the point where if someone said that PayPal are responsible for climate change; I would be inclined to believe them. No matter how much they denied it.
In other words you're prejudiced and see no reason to logically validate your preconceptions?
Great, that's what we need. More people commenting who have all the answers. What if PayPal were telling the truth, how exactly would that situation look different than the one we are in? Good thing PayPal's always wrong though!
It's more like extrapolation from a known set of data points. PayPal has a certain history. You can look up what's gone down in the past, and based on that, the accusations fall right in line with the sorts of things PayPal has historically done. At this point it seems far more likely that PayPal did in fact do what it's accused of than that it didn't.
If PayPal is in fact telling the truth (and that's a big if), then the question becomes where did the hacker get the last 4 of the CC from? GoDaddy has confirmed the hacker had a large amount of info, including presumably the last 4 of the CC when he called them, so somewhere in this whole thing someone gave that data away.
(I can't reply to jessedhillon's follow-up comment yet & i don't want to wait so I'll just reply here....)
If you look as far as... oh say, the top of this thread on HN, you will hear accounts from people who have apparently done this very thing (asking PayPal for last 4 digits and gotten an answer). So it seems like their policy did not forbid it, anyone could do it, so why not believe the hacker's claim?
You can't have a policy of routinely giving out certain info then deny that you gave it out in a case where it caused a security breach. What is the defense there? "Well yeah ordinarily we DO give that out but we could tell this guy was a hacker so we didn't." Yeah, they wish. If they regularly give out last 4 digits, then the claim that they didn't in this case is absurd.
...the question becomes where did the hacker get the last 4 of the CC from?
That's always been the question. Until you know better, what you have is a situation where you're believing the word of an anonymous criminal, relayed to you second-hand, over PayPal. I'm just saying you have no evidence either way at this point, and are simply expressing your preconceptions, which are not helpful.
The author should probably lighten up, but I agree with the general sentiment.
If you want to drink, hang out with your friends. Your colleagues may also be your friends, or maybe your friends are in the tech scene too, but let's get real, software dev is a job, a career and it puts roofs over people's heads and food on their tables. Treat it with respect.
it would also be nice to see books and resources for children going up to about 14/15. It would be a shame to see a gap in their education when they can really get going.
...so if it's targeted at children, 50% of children will take it up, thus the ratio of male:female programmers will remain the same, there'll just be more of them.
The book is aimed at girls. It would be nice to think that children were not conditioned by gender stereotypes at the age of 6/7, but unfortunately they are.
The current gender ratio is the result of decades of gender stereotyping that things like math and science and programming were "for boys".
I'm going to believe the author when she says that this is for children. I just don't buy the idea that boys can't enjoy stories with female leads. Look at Brave or The Hunger Games. My son loves those.
