"It's just going to encourage more launches" - no it won't. The current missile defense systems do not have a deterrent effect. They are expensive to launch and the 3rd world missiles that they intercept are much cheaper. Even a successful interception is a victory for the agressor.
On some level it's a statistics game. Even in the absence of a defense system X/Y missiles will hit the target depending on the details. A defense system reduces that number further.
Better to get the system refined when the stakes are low. When the Houthis miss the airport and they're a lot more likely to hit sand than city. When NK misses some city in SK (not necessarily Seoul because they can hit that with conventional artillery) they're much more likely to hit something we don't want them to hit. Now, the latter situation may not be relevant within the lifetime of this system but having the system be "battle tested" serves to make it even less likely.
This sort of scaled to all defensive and deterrent systems. The more successful they are the more the generals in the war room will say "We can't just do $offensive_thing because it's not likely enough to be effective in the face of $defensive_thing"
You're correct, right now it doesn't support multigraphs because of a library I'm using. I'll modify it soon to add that support and then the bridges will be correct.
"Judges in the city are paid $100 per election they preside over" For a days work, that's not much for a one off job even by central European standards. It seems to me, that the pay should be increased.
On the one hand, a lower salary ensures people don't do it for the money. On the other hand, low pay can restrict the candidate to wealthier or higher-income individuals. This is a challenge in deciding out how much to compensate people for service, not just for a one-off such as this but for longer-term and more time-consuming roles as well.
So if a person makes millions of dollars a day they get paid millions from taxes but if an unemployed person does the same job they get paid nothing? I'm not sure that's an improvement.
In the last German election I got paid 50€ for a similar position (well below minimum wage) which is already more then usual. Let's just say nobody does that for the money.
By comparison, here in Australia, for federal elections, pay rates for polling officials working on election day range from AUD$409 up to AUD$989 + $63 retirement superannuation.
Unrelated to bootcamps, but one thing really jumped out at me in the article. The author's discussion of BigO time:
"The post went on to detail a need for an understanding of BigO time complexity, which is completely fair. No one wants a double loop in production code. What a bulky monstrosity that would be (imagining a giant disgusting swamp monster made of 0’s and 1’s, eeek!)."
"I certainly don’t want to make a messy newb mistake like creating a method with a time complexity of O(n²) or worse (cringe)."
I'm not going to be critical and say that this is wrong and that the author doesn't know what she is doing. But it does seem that this quote demonstrates a tendency I see among female advocates of women in tech, and that is to slightly awkwardly use technical terms in order to try to prove that they are part of the "in group" of people who understand technical concepts.
In this case, it seems that she is trying to prove that she knows what BigO is. I feel like this is a kind of meta-sexism. What she is doing by explaining to us the gist of BigO is saying "I think that you think that I'm so stupid that I don't know what BigO is, so now I'm going to prove to you that I do."
I know I suffer from the assumption that women don't know how to code. It's a hard thing to get around, since %90 of female programmers whom I meet are women from PyLadies who come to the local python meetup, and really don't know how to program yet. And now our author is suffering from the assumption that I assume that she doesn't know how to code. And in trying to prove otherwise, she trips over herself in her eagerness to prove my assumption wrong.
This meta-sexist thinking and behavior is getting so complicated and convoluted that it is acting to distract us from thinking and communicating on technical topics. I believe that it has become harmful to the cause of encouraging women and minorities to join our communities. It is harder for me as a white man to talk to a woman or a minority because I am thinking about their gender or race. And it is harder for a woman to talk about tech if she is thinking about my thinking about the fact that she is a woman.
Somehow we need to escape meta-sexism and start talking to each-other as equals, without presumption or presumption of presumption.
> But it does seem that this quote demonstrates a tendency I see among female advocates of women in tech, and that is to slightly awkwardly use technical terms in order to try to prove that they are part of the "in group" of people who understand technical concepts.
That has nothing to do with being a female advocate of women in tech. That has everything to do with being 12 weeks into programming. That's the main reason I don't like this article.
I'm lucky enough to know a lot of incredible software engineers who happen to be women (and were also CS grads or PhDs), much smarter than me, and I don't like this attempt to associate all women engineers with people who clearly only have a superficial understanding of code.
> I'm lucky enough to know a lot of incredible software engineers who happen to be women (and were also CS grads or PhDs), much smarter than me, and I don't like this attempt to associate all women engineers with people who clearly only have a superficial understanding of code.
I don't know that many experienced female programmers, but the ones whom I do know are not advocates and tend to avoid the subject of their gender. So my own experience leads to the conclusion that I made, not about all women programmers, but about those who advocate women in tech.
> I know I suffer from the assumption that women don't know how to code.
How the hell do you come to that assumption? I don't understand at all how you can make an assumption that a person knows or doesn't know something based on race or gender.
You need to check yourself because:
> It is harder for me as a white man to talk to a woman or a minority because I am thinking about their gender or race
>> It is harder for me as a white man to talk to a woman or a minority because I am thinking about their gender or race
> is not normal.
Perhaps you don't do so. But how do you know it is not normal? If you don't let me share my internal battles without attacking me, then how can you know the internal psychology of others?
Because everyday millions and millions if not billions of transactions go on between humans of all genders and races, if your view was in the majority, then society would be different. You need to talk to someone about your world view and get help.
When you read my comments you have a set of assumptions that you have made about me. You cannot escape that. For one thing, you assume that I know English (which I do). Another thing you probably assume is that since I am on HN, I am a computer programmer. You assume that I know the word "transaction" since you use that word. You don't explain its meaning to me. Neither do you explain to me what a human is. You assume that I know what humans are. You assume that I am human, though you cannot see me. Assumptions are everywhere.
When we meet someone, we begin with a default set of assumptions about them and what they know. You cannot even communicate with a person without assuming something about their level of knowledge, of language, culture, and technology. The question is, whether these in-avoidable default assumptions should differ based on a person's race or gender or nationality. I believe that they should. If I come up to you, knowing that you're from the UK, and start talking to you about the post communist privatization process in the Czech Republic, without first explaining to you what it is, you are bound to be confused. I assume that you do not know about the privatization process.
That doesn't mean that I believe that citizens of the UK are fundamentally incapable of understanding the privatization process. If I ask you if you know about this process and you say you are an expert on post communist economics than my assumptions about your knowledge on the subject will quickly change. But for now, since I know nothing about you, it is safe for me to assume that you know nothing about privatization and that in order to be polite, I should not spend the next 30 minutes talking about the current value of privatization coupons without ever asking if you know what the hell I'm talking about.
But when the basis for my assumption of shared knowledge is gender, this leaves an interesting question. If I know that most women who I meet in technical contexts are not computer programmers should I immediately assume that they are computer programmers and start talking about in depth concepts or should I ask first? Is it more rude to assume that my conversation partner understands what I am talking about or to assume that they do not understand? Especially when many newbies are so eager to show that they do understand, that they find themselves unwilling to say out-loud that they do not.
I agree and disagree with this one. Of course, no one is going to pay money for your game idea, but there are ideas which require an NDA. Those ideas typically take years of development and a person with such an idea would be able to present hundreds of pages of alternate designs and their pros/cons. For example, if I have a design for a 3mm x 1mm mechanism that can actuate a rod by 2mm and I know what kind of power consumption said mechanism will have, that design might be expressible on a single piece of paper, and be worth millions of dollars.
True, but if I know that you have been working on the idea for 5 years, and that you have those hundreds of pages of alternate designs, then even just the end result may be valuable enough to me that you would want an NDA.
