366 karma · joined January 23, 2012
* begin traveling more often
* live in 13 cities over the span of 12 months
* start a blog
* take up photography
* learn at least one other language (spoken, not coding)
* get better at javascript
I like the treehosue approach - videos plus quizzes plus exercises plus projects - but I do think it's aimed mainly at beginners (which is probably why it felt goofy to you, because they're trying to make it approachable for people who aren't yet comfortable with technology).
I do wish there was a resource out there like Treehouse for learning more advanced topics.
If a thief breaks into your home and steals your TV, you're pissed that your TV was stolen but that's what you expect of thieves. If your best friend does it, it adds that extra layer of betrayal and it adds the feeling of shame and stupidity for ever having trusted them.
Ultimately, though, the "separation of concerns" was a good principle to use when the web was a bunch of documents meant to provide content. It isn't that way anymore. The web has evolved in use to include web apps and other forms of media, so our principles must evolve as well. It seems silly to cling to past definitions as immutable when we work in a field that changes drastically nearly every year.
Also, anyone who advocates using a selector like "ul.members li a" and then complains about the maintainability issues of using non-semantic classes when an update needs to be made should really reconsider their hypocrisy. Using selectors like that (aside from being slow performing) completely tie the markup to the presentation. Hell, if all you did was update the list to an ordered list instead of an unordered one you'd have to update the CSS as well.
The reality is that any change in the UI big enough to warrant updating the markup is going to warrant updating the CSS, and vice versa. Worrying about making them completely separate is impractical and will just cause you to waste time in development.
If you're concerned about the discoverability of the code to a new developer, DOCUMENT IT. Do not create crappy selectors. Create a UI style guide that implements all of the major UI components and have the developer reference the style guide. Use something like KSS to link between the style guide and the CSS. There's no excuse for using bad selectors in the name of ease of on-boarding.
They are not different scenarios at all. Just because I didn't use the exact same words to describe them doesn't mean I'm not describing the same concept.
Customizing your design to target the employers you want is the equivalent of customizing your design to weed out the employers you do not want. His design is meant to weed out employers that do not value the same things he does; this means his design is meant to attract the employers that do value the same things he does. These things are equivalent and they are the same concept described in both posts.
Point two - how is it convoluted that a person would want to target his resume to a specific type of company? Customizing your resume for the company you want to work for is the first basic principle in writing a resume. He just does it in such a way to also exclude companies he wouldn't want to work for.
First, you seem to be missing the actual point of a resume. No one makes decisions on who to HIRE based on a resume. The point of a resume is to get an INTERVIEW. Your resume could actually lack any details of the normal stuff that goes on one (education, experience, skills, etc) - but as long as what you provide gets you that interview then it's done its job. As someone who's done interviewing at interactive agencies, if I saw this I'd probably set up an interview.
The second is your assumption about the purpose of a resume's design. Your thinking lies all on the company's side - making things easier for the recruiter and facilitating understanding of the reader; allow me to offer an alternate line of thinking. In an interview, it's not just the company determining if it wants to hire the prospect; it's also the prospect determining if she/he wants to work at that company. This resume has taken that to a step earlier. This person is purposely making his resume more creative and "difficult" to weed out prospective employers that don't value those things (this is actually something I do as well, though not to this extent). This person obviously wants to work for a very specific type of company and doesn't want to waste his time interviewing at companies that don't match his desire (like companies that use recruiters or where resumes go directly to HR people instead of hiring managers). So I'd argue that the design of his resume is specifically working very well at weeding out places where he wouldn't want to work and attracting the attention of places he would like to work.
Do people really think Banksy wants people out there removing chunks of walls or doors that he tags and putting them in museums or selling them to private owners for thousands of dollars?
You do not deserve to be here. You do not deserve to have to pay $60,000 a year. For those of you who graduate, because at least 20% of you will not, you do not deserve to leave here $240,000 in debt to student loans only to end up taking a job that does not require the degree you will spend the next 4-6 years pursuing. No one deserve to struggle financially for the rest of their lives because of 4 years of bullshit that your parents, educators, and soceity sold you as the only way to "get a good job" or "make a decent living."
Stanford is a private "educational" institution that operates for profit. The notion that you have to "deserve" to be there while going into debt and paying them is ridiculous. That's like saying you don't deserve to eat at Olive Garden; even though you're paying them, even though you worked hard to earn the money to pay them; because eating there is a privilege that you haven't earned yet.
The reality here is that companies aren't loyal to their employees. If a company isn't loyal to you, you can't be loyal to it. It's that simple.
The UI makes some interesting choices, but I'm sure this could be skinned with a bit of elbow grease.
I'd say my only real complaint is the validation on forms - it seems specifically inefficient to declare an object in JS and pass in each form field and set it's rule as "empty". I would consider utilizing a data attribute and doing something like data-validate="empty". You could even accept a list of them with something like "data-validate="empty email" etc. The only downside would be figuring out a way to still accept custom messages - something like data-message="Please enter your first name." would be fine for one validation check, but passing in a multiple messages for multiple validation rules would get ugly fast.
Also, at a certain point, being rude crosses into being bigoted. Imagine if someone said a person didn't "look rich enough", or poor enough, or white enough, or black enough, or young enough, or old enough, or whatever other type of judgement based on someone's physical appearance.
To me this is akin to a cop pulling over a black guy driving a nice car and asking if he stole it. It's a person in power abusing their power because someone else has something that the person in power doesn't believe they have any right to have.
Finally, people who are bad at their jobs (like the flight attendants in this story) deserve to be publicly exposed and fired so that they can't cause inconvenience to anyone else who has the misfortune of getting them on a flight.
I know that there's recently been a backlash against the entire idea of the "separation of concerns" - but having your markup define your style margins is a bit insane. If suddenly you wanted 10px margins instead of 5 you have to grep your entire codebase for .m∗s (limiting the length of the string to 3 characters) and updating all those to .m∗m (or just defining both .m∗s and .m∗m to be 10px, which is just as dumb).
But, yes, most of the points in this article are somewhat accurate if not a bit outdated. Try not to use element selectors (and instead apply a class), avoid code duplication, write efficient selectors, etc.
(Note: asterisk changed to low asterisk and I hate markdown or whatever other text styling syntax HN is using).
Also, I'm not sure how valid the author's statement actually is. I didn't spend a ton of time researching it, but I was curious. Here are the application numbers for two recent years (couldn't find University of North Carolina):
Boston College | 38.2k -> 41.7k (+9%) Brandeis University | 7.7k -> 8.9k (+15%) New York University | 38k -> 42.2k (+11%) University of Georgia | 17.4k -> 18k (+3%)
Each college continued to receive an increase in applications that was (with the exception of the University of Georgia) on par with other colleges.
If people are still applying to those schools, and they aren't seeing decreased applications, doesn't that mean the whole "tipping point" argument where no one will want to go to those schools is invalid?
" Officials at schools ... are helplessly watching as their campuses become like retirement villages, with a surfeit of women competing for a handful of surviving men."
Is the argument here that women only go to college compete for men? And that colleges with more women are "retirement villages" because there aren't enough young men to hook up with?
Yep, done with this article.
There are hundreds of online courses and hundreds of thousands of in-person courses. You should know it's not a good idea to make inference about ALL MOOC's based on one example or ALL in-person courses based on a handful of classes.
If your statistics classes didn't teach you this concept, I'd say it was those classes that did a poor job.
So, instead of discussing the topics in the video, the majority of commenters here are discussing the flaws of the website it's hosted on or debating whether or not reddit is profitable. Neither of which has ANYTHING to do with scaling.
I expected better, people. Seriously.
Like you said, when he mentioned that everyone's nutritional needs were unique, my mind also went immediately to bio-feedback devices that would not only indicate what you needed but also create a meal plan and order the food for you. There's no reason this also couldn't be done with Soylent. But because these things don't exist today people assume that they'll never exist.
Please comment your code. First, you're probably not going to immediately remember what the code does 6 - 12 months after you write it and when you have to come back to it for an update it's going to take you too long to figure out if you actually read the code. Comments make familiarizing yourself with your old code much faster. Second, any other teammate who touches the code is going to hate you if they have to read your code to figure out what it does. There is nothing worse than looking over code written by someone else when there are no comments.
All manner of behavior - that you shouldn't steal, that you shouldn't lie, that you shouldn't wear your trucker hat to a business meeting - are all just the opinions of society. Some are made into legal contracts while the rest remain social contracts, but that doesn't mean they're any less important or valid.
No one should be fired without the opportunity to defend themselves or explain their actions. Being fired should also be a private matter, as studies have shown it's bad for morale which is bad for business.
WHAT you do isn't the only thing that matters; HOW you do it is equally important.
Then again, if you're a person with character, you don't refer to your business meetings as a "locker room" or use terms like "loserville."