"Why are our cities suffering from the same problems that every other city faces?"
I don't even know what to say to this. How can the author even be asking this question?
Here's a basic outline. It feels weird typing this because it should be obvious, but here goes.
Northern California cities are cities just like any other. There are people of all income levels doing all sorts of different jobs, or not doing any jobs. There are a disproportionate number of tech workers in that region, but other than that it's pretty much the same as anywhere else. People are still people are still people. The reason a shirtless man randomly punched you is because he was crazy. The more people you have concentrated in a small area, the more likely you are to meet up with a crazy person when you're walking down the street (that's just statistics/probability). I live in NYC, a much bigger city, and I see crazy people all the time. When you see someone not wearing a shirt in public, babbling or shouting, hanging around on a street corner by themselves, etc., etc., they are most likely crazy. If you see a crazy person, stay as far away from them as possible and do not make eye contact. Definitely do not engage with them in any way (this includes taking pictures of them) because it will provoke them. Welcome to city life!
Chrome is dropping NPAPI support, which includes the Unity browser plugin. Unity will be temporarily whitelisted probably through the end of 2014 but the goal is to remove support entirely.
I personally think it's just incredible that vertical centering in CSS has been so woefully neglected over the 16 years we've had CSS. Every time I read another article about how somebody just maybe has figured out a kludgy way to vertically center things with CSS, I just shake my head. Aren't there any graphic designers on any of the W3C working groups surrounding CSS? Back in the old days when everything was a table-based layout, there was a clean, one-to-one mapping between the grid framework that your graphic designer created and the code underlying the page.
Then the semantic web pedants came along and decreed that tables shall never be used for layout. Fine -- but nobody ever bothered to come up with a DIVs+CSS replacement for the grid-based layout that any serious graphic designer uses to build a page.
And do you know what happened to the web? Debate cause and effect all you want, but webpage designs are far more boring now than they were 10 years ago. Now it's all just blocks of large-print scrollable text, some images here and there (or maybe a wall of them), and a cute logo. It's like everything is a Geocities page with better fonts and color choices, minus the gifs. I feel like I never see anything really cutting edge or creative in the design space on the web.
The internet is a really young medium of course, and it will naturally go through phases, where certain types of design come into fashion while others go out. And I would love it if somebody would prove me wrong by posting some links to some really kick-ass-looking sites. But from where I'm sitting these days, from a design perspective the web is a big yawnfest. Maybe today's websites are more usable and easier to index and work well on a screen reader, but from a graphic design perspective... zzzzz....
Most arrogant quote I've ever heard coming from a developer. I hope this sounded different in context because that is one of the most horrible and elitist things I've ever heard pertaining to our industry.
The museum of natural history was not built post-1995. It's probably giving that as the date because they added the new planetarium in 2000. Which raises the question, is this true for other buildings -- is it showing the date of the most recent renovation of the building (as opposed to its construction date)?
I ask them to guard my laptop, which they usually do since I suppose they will get in trouble if it's stolen. Actually maybe the fact that I'm asking them to watch over my laptop expedites the actual patdown, because I never have to wait long.
I love how he felt compelled to excuse his omission of castling and en passant moves by explaining that they were added to chess "later" (14th and 15th century)... maybe he started working on this project before those rules were added? :)
"sending a message" == getting you to doubt, think twice == instilling fear == creating terror == being a terrorist
Fighting terror with terror. How can it be that no one in the UK government agencies responsible for this can see the irony? How can it be that they don't understand their actions are degrading society just as much as those of the terrorists?
"Funding some local education or beautification initiatives could go a long way to reducing the gentrification backlash."
Or maybe California could relax its constitutional restriction on city and county income taxes, which would make much more sense than relying on random benefactors to make the city more livable.
I hear this over and over again and I wonder why nobody frames this as a generational thing. The Apple II came out in 1977. I'm 41 now, so back then I was 8, still learning how to think, how to process the world. I wrote my first computer program in 6th grade -- I grew up with computers. But somebody who is 51 now was 18 when the Apple II came out, already well into their teenage years, and probably already thinking about what they wanted to do with their life. Unless their parents were scientists or researchers there was very little chance they had ever seen or laid hands on a computer.
One thing I fear is that there's a rise and fall to this. In other words, the fear is that younger generations are just not as interested in computers anymore... in other words, the past 20-30 years or so has been a "golden age" for computers that is slowly coming to an end. Data bears this out:
http://www.collegian.psu.edu/archive/2008/03/21/computer_sci...
Let's look at popular music. Baby boomers grew up listening to records and the radio, and in their run they made some amazing music. It was an exciting time to be in a band, everyone was doing it, and some really great music was made. Back then, they said "if it's too loud, you're too old." Everybody talked about youth then.
What happened? People kept on believing that rock and roll was for the young, and there were more and more ways to access music and the technology for making music got better and better, but the reality was that the music itself just got worse and worse. The moment was over -- the Vietnam war, the sexual revolution and womens’ movement, the civil rights movement -- it was all in the past, and kids in the 80's, 90's etc. just had nothing to write songs about anymore, and (very much generalizing here) nobody practiced their instruments anymore because -- why? It was all about getting that record deal and getting famous. The more you unpack it, the more dismal it appears. Those great hits you remember from the 80's, 90's, etc? Look more deeply into it and you'll find in many, many cases there were baby boomers advising, producing, writing, performing -- basically still running the show. These days, popular music is a shell of its former self. Which isn't to say that there's isn't good music being made. But the quantity and the quality of the music just isn't what it was.
There have been plenty of other "golden ages" throughout history, in the arts, philosophy, literature, architecture, etc, etc. It's reasonable to assume that there will continue to be “golden ages” with regard to more modern pursuits, such as rock music and computer programming. Who knows how long programming’s first “golden age” will last? Maybe it’s just getting started, maybe it's coming to an end, or maybe it’s already ended. Regardless though, it's probably safe to say that someone who is currently in their 50's pre-dates programming’s first "golden age" and probably doesn't parse the world the same way as somebody who grew up in the thick of things. Which doesn’t actually mean that someone in their 50’s can’t be a good programmer, by the way, it’s a generalization, not an absolute.
These days, when I come on hacker news and I see another yet another article about a completely boring social-media who-cares php-based startup with kids at the helm, when I see how weak Facebook is as a technical platform (28 year old CEO) especially when compared with Google (40 year old CEO), when I see how much kids these days rely on bolting shit together and copying and pasting code without even knowing how that stuff works, it makes me fear for programming. Again, I’m generalizing, there are plenty of good programmers under 25, and plenty of good programmers over 40, please don’t take offense if you’re outside of that age range. My worry is not that good, young programmers don’t exist, my worry is that their numbers are decreasing.
I think you are missing the point that this poll is voluntary. So, the "Do not disclose" option is there -- just click on one of the many other links on HN today, or otherwise do something else with your time. There, you "did not disclose."
I would have agreed with this up until about a year ago. But I've recently discovered a new way of thinking about the development process that IMO is far superior, and more importantly, far healthier in the long run.
The way I used to think about development was that there were separate phases: building, debugging, then launching, then you stop working on it because it's "done." Then, I suppose, you go on vacation and sip Mai Tai's on the beach.
The thing is, once you get rid of the "done" phase, your whole perspective changes. The other three phases (building, debugging, launching) get mixed together in a blender. Suddenly, any time you hack something, it's okay because you're going to fix/change/refactor it later. It's all part of one big growing, changing, process -- a process that actually fits with the literal meaning of the term "development."
So it's not about pride anymore for me, it's about humility. These days, when I build something, I start off hacking something together in the quickest way possible, no matter how ugly. Then I just keep iterating, refactoring, fixing, cleaning: improving, improving, improving. So there is never a moment when you proudly show off a gleaming, fancy product and say "look, I'm done!" There's always something that works, something that doesn't -- something that needs to be completely rewritten, something that looks good and you haven't touched in months (or years).
The great thing about doing this is that it's a good way to keep yourself from being an "architecture astronaut." If you start with a hack and build refactoring into your process from the very beginning, you'll never build out more architecture than you need, because every time you use a design pattern it will be a direct response to a real need, not an imagined future need.
To conclude, I'll leave you with this quote from Walt Whitman, talking about the "deathbed edition" of "Leaves of Grass" -- a book he revised nine times during his life, which grew from 12 poems to 400 during his lifetime.
"L. of G. at last complete—after 33 y'rs of hackling at it, all times & moods of my life, fair weather & foul, all parts of the land, and peace & war, young & old"
Not sure what "hackling" means, but it sure sounds a lot like hacking!
I probably sound like a food snob, but when I'm thinking of beef that tastes like cardboard, I'm thinking of a Big Mac, for example. If you take all the condiments and just eat the beef only, it's pretty tasteless, IMO.
A lot of people say there is a taste difference, not just me. It's subtle though, your ordinary person may not notice or care. But I'm passionate about it because I'm big into food and I think the taste of grass fed is much better.
A preliminary report by the UN's International Atomic Energy Agency has stated that the response to the Fukushima nuclear incident was "exemplary" and that nobody has been harmed by radiation exposure resulting from it.
That seems to contract what the Japanese government's own panel concluded:
Yes that is what they are supposed to be eating. Their digestive systems have evolved over millions of years to eat grass, and if they eat grass they will be healthier animals, and their meat will taste like real beef and not like tasteless cardboard. I pretty much stick exclusively to grass-fed beef. There are all these complex chemical compounds in grass that flavor the meat and give it rich and distinctive notes -- as the other commenter said, read Omnivore's Dilemma. The cattle are supposed to be able to walk around, too.
The reason it's not done is cost. Grass fed beef is easily twice as expensive as corn-fed beef. The cheapest way to raise cattle is to raise them in a CAFO, and feed them the cheapest possible feed, which has been corn for quite a long time. The farmer who is feeding his cattle candy is really just feeding them yesterday's corn, as most American candy is made from high fructose corn syrup. Walk into a supermarket sometime and count the number of products that use HFCS -- it's staggering. The price of corn going up is actually really big news -- if it's a sustained trend it's going to have a far-reaching impact on American agriculture.
I just want to say that what I've found is that you need a balance. Swing too far in the direction of "Do what you love" and you'll hate the fact that you're poor and can't get a job. Swing too far in the direction of "do what's practical" and you'll have all this money but you'll hate what you have to do to get it.
It's not either/or. The best thing to do is find a career that is exciting or interesting to you in some ways, but also has a good bit of practicality.
In other words, we shouldn't be asking kids "what do you want to be when you grow up?" The question should be -- "What are the top five things you could see yourself doing?" Because of those 5 things maybe 4 of them are impractical, and maybe the lucrative one isn't the top choice, but it's up there.
Sorry to harsh on the site, I realize it's your creation that you've put time and effort into, and I'm just some random guy killing time on the internet.
That said, I will say that the poster explanations were frustrating for me. I've studied formal logic via computer science, but not enough argumentation or philosophical logic -- so some of these fallacies were new to me. For example "no true scotsman" -- but the explanation did nothing to help me understand it. I'm type of person who learns by example, but your examples are so cutesy and weird that I can't actually relate them back to anything useful. Something about sugar in porridge? What I want is to be able to recognize these when I see them, but I'm just not getting it from your explanation. Real-world examples would be MUCH better.
Part of why I'm frustrated is I've been wishing for a resource like this for a long time -- someone who really understands argumentation, clearly and simply explaining logical fallacies, with real-world examples. I've read about "straw man" repeatedly, over and over -- definition after definition -- and I still am not confident that I could identify it if I saw it. Very frustrating. Feels like a lost opportunity. Maybe it's working for others, not me though. sorry
I was getting annoyed at the oversimplified, vague, and/or unclear explanations on the poster. It's great to have a poster cataloging logical fallacies, but it's not so great if it doesn't actually explain them very well.
So I go to the home page of the site, where the first sentence reads:
"A logical fallacy is usually what has happened when someone is wrong about something."
FACEPALM.
The validity of a logical argument has NOTHING to do with the actual veracity (rightness or wrongness) of the propositions. This is basic stuff. Logic is the process of figure out what other things we know based on what we already know. If what we think we know is wrong, then we can make all the logically correct arguments we want and we'll still be drawing wrong conclusions.
I don't even know what to say to this. How can the author even be asking this question?
Here's a basic outline. It feels weird typing this because it should be obvious, but here goes.
Northern California cities are cities just like any other. There are people of all income levels doing all sorts of different jobs, or not doing any jobs. There are a disproportionate number of tech workers in that region, but other than that it's pretty much the same as anywhere else. People are still people are still people. The reason a shirtless man randomly punched you is because he was crazy. The more people you have concentrated in a small area, the more likely you are to meet up with a crazy person when you're walking down the street (that's just statistics/probability). I live in NYC, a much bigger city, and I see crazy people all the time. When you see someone not wearing a shirt in public, babbling or shouting, hanging around on a street corner by themselves, etc., etc., they are most likely crazy. If you see a crazy person, stay as far away from them as possible and do not make eye contact. Definitely do not engage with them in any way (this includes taking pictures of them) because it will provoke them. Welcome to city life!