theaccordance

The first two answers to this quora question are from authors of each framework and give very detailed responses, I encourage you to give it a read to gain technical insight on the differences, as it will help give perspective on why Angular is more popular: http://www.quora.com/Client-side-MVC/Is-Angular-js-or-Ember-...

My personal opinion on why Angular is more popular than Ember goes back to the root difference between the two frameworks: Ember's syntax is structured in a way that favors those coming from Cocoa or Ruby, while Angular is structured in a way more familiar to those with an existing background in HTML5. I also wouldn't discredit the proximity Google already has with web developers (analytics, webmaster tools, etc).

Shady code test or not, I don't agree with the manner in which you handled the situation. You agreed to do the test, submitted it partially completed, and then replied that it should be sufficient (knowing full well you didn't meet the requirements). I doubt the CTO didn't understand that the other cases would be trivial to implement; he simply sees a half-finished submission and a candidate who didn't correct the mistake when given the chance. Had this been a college exam and not a code test, would you expect a professor to award you a passing grade based on the entirety of the test, or the questions you chose to answer?

One thing to keep in mind is that while you may view the code test as bad, it might not having malicious intent; some managers simply lack experience in putting together tests and fall back on old specs. There's two things I do during interviews prior to writing a single line of code:

1. Every code test I have taken has been brought up during a discussion. I use this opportunity to ask questions about the test. If you're interviewing with a recruiter who's not familiar with the test, they'll forward your questions to the manager who's evaluating the test for clarification. The manager's response will come either prior to accepting the assignment, or with the assignment attached to it.

2. Immediately upon receiving the code test, I review the spec in its entirety. If I have concerns with the spec, I raise those right away, as to not give the impression that I'm incapable of completing the spec if I bring up these concerns at a later time.

Don't worry about the company, they need a motivated and happy worker and from what you've written, you're not that. They also may not be on the hook for the fee if you leave within a certain amount of time.

Plan your exit, whether that's now or once you land another job, and don't look back.

While we could debate terminology and classification over the contract status, I consider it a termination given that A. It was an ongoing work assignment and I had continued to receive new work up until the notice to not renew, and B. I had to go through an off-boarding process.

I was working for an early-stage startup during the summer of 2013 as the front-end developer. While I was there, we fired our iOS guy, our backend guy switched to iOS and the company now needed someone with full-stack experience to cover the gap, so I got the axe at the end of my contract.

Personally, I was lucky: it took me a total of 4 days to find another job. I didn't have to retool myself because I had kept up on the latest trends within the scope of my skills, and the job market was heavily in my favor at the time.

While I didn't have to learn new skills, I did learn that external factors beyond my control can affect my continued employment. It has made me more mindful of my surroundings and observant of the business direction.

Personally, I prefer having third party libraries available through a package manager like bower or npm. It doesn't take much to get these set up if you're already hosting your code in on Github

Offering a trial period or free tier of your product may be something worth considering. This allows a developer to test the tool within their workflow and if they find enough value from it, pay for the product in full.

What you're describing sounds like an edge case and goes against the design & development methodologies used in today's websites. Rarely are we building things with static content, and we're leveraging the power of AJAX to minimize the number of times a browser must refresh the entire window to load new content.

Current trends aside, from a pragmatic perspective, I would anticipate something like this increasing development costs (labor & money) between 10-50%, and would likely have a very low ROI.

You won't be blackballed out of your career, but it is possible that by having this burnt bridge, you may have closed yourself off to some opportunities. It'll depend on the demeanor of your former employer, and connections between your former employer and those you're interviewing with.

Grammar and spelling aside, this is a good reference for those Ask HN "How do I get an internship/first job" posts.

I think the insight point is valid, but I disagree with the approach I've seen instructors take in the past. I know in college we were always told we couldn't use Wikipedia, but what they should have taught us instead was to use Wikipedia similar to how we use Google: as a springboard to find the sources we should use and cite.

That sounds like laziness on the part of the instructor. Textbooks are subject to being outdated the moment they are printed; restricting the scope of learning to that in an age where information is free and easily accessible sounds absurd.

If that were my kid, I'd be asking for more context from the instructor/school on the situation. If the school's response isn't what I deemed acceptable, I'd demand either a change in the scope, or that my kid was placed in an environment that reflects how today's learning actually occurs.

There's an off chance you could do an extra level of verification using the mail headers, but I wouldn't bet on it. Keep in mind that email is an old technology, it lacks a lot of things that would make it more efficient/useful in 2015

One that I remember coming across is https://www.shakelaw.com/

Cant give insight as to why that industry seems particularly more quiet than others in terms of disruptive business models however

Yes they do. Generally they're not considered senior because they have X years specifically dedicated to Node.js, but instead they have X years of proven development experience with the last 2+ focused on Node.js.

Then just continue to block the domains, eventually they're gonna run out of services to sign you up for lol

Well they're not getting on if they can't acknowledge the confirmation email, so they're not technically using your email account.

Best advice in this situation is "Out of sight, out of Mind." Set up a rule to automatically delete emails from said domains.

Outside of that, if you're worried about how your wife will react, just get out in front of the situation and tell her; hopefully the worst that happens is that she makes fun of you

A lawyer would probably be a better person to answer this question, but if I had to venture a guess:

1. Identifying products that the source company is the sole distribute of

2. Logs that are able to identify the crawler and what it accessed.

I would be very hesitant to invest or subscribe to a product that solely relies on data scraping. You're asking for trouble if you don't obtain permission first to include another company's data within your product.

The one legal case that always comes to mind in terms of data scraping is Craigslist Inc. v. 3Taps Inc. http://en.wikipedia.org/wiki/Craigslist_Inc._v._3Taps_Inc.

Different companies have different reasons for code tests. Generally speaking, here's what you should expect they're evaluating:

- That you're able to take ownership of a task and see it to completion

- That you can work with the tech stack that the company uses

- That you can actually do what you say you can do

So let me get this straight: You've written a 3 sentence Ask HN soliciting for internships, provided no resume, and your github account has no public repos demonstrating that you can build something to code completion? I can't speak for the entirety of the viewership here, but if you want to be taken seriously, then put forth the effort. Whether it's an internship or a full-time job, companies are investing time and resources into you, so you need to demonstrate that it's in their interest to have you on their team. I'm not seeing that right now. What you should do:

1. Put together your resume if you haven't already. If you have one, then you should include it here or at least reference that you'll provide it to interested parties.

2. Have some code to showcase that can demonstrate your ability to take a spec to code completion.

3. Look at other Ask HN posts that are the same topic; see what those users have posted and what the community has responded with. This may come off harsh, but I've seen several in the past week alone, and yours is the least compelling post of them all.

It sounds like you're working in a culture that doesn't allow you to grow in the ways that would make your career enjoyable, I would at the very least start looking for a more enjoyable job.

Few thoughts:

1. Don't fret about not getting offers, especially since you're just getting your start. It can take a while. The important thing is that you're getting the interviews; this makes it a lot easier figuring out how to adjust your strategy.

2. Your long term career prospects won't be hurt if you don't get a job right out of college. If this were the case, changing careers wouldn't be a normal thing.

3. Don't limit yourself to just companies you see on HN, there's plenty of startups that are't on HN's radar for numerous reasons. A few suggestions on where else to look:

- Reddit. Our company has found several quality candidates by posting in the appropriate subreddits.

- Recruiters. They'll be good about giving you feedback to help you refine your approach.

- Other online startup communities. Here in Chicago, we have builtinchicago.org, your locale may have something similar.

- Venture Capitalist Websites. Some VCs have recruiters to help source talent, but at the very least, you'll probably be able to get some leads by browsing their portfolio of companies.

As far as resume feedback, I'll point you to a comment I left earlier this week for another individual asking similar questions. While my feedback there is more tailored to his situation, you may find some value in the thoughts I shared: https://news.ycombinator.com/item?id=9450177

If you're worried about leaving a startup early because it's not the right fit for you, don't. Your life, your choice. Plain and simple. Suggestion: review the employment agreement you signed to make sure you won't be penalized for leaving early. If you received a signing bonus, you may be obligated to repay all/portion of it if you leave willingly before you complete your first year.

If the concern is applying for new jobs, then that will depend on the companies you're applying to. Startups are volatile by nature; they'll be more interested in what you did during your time than how long you were there. Traditional corporations or long-standing businesses however may weigh duration more as they consider you.

Best advice to you is to be prepared to explain your reasoning for leaving, and also demonstrate that you were effective in the time you were with your current employer.

IMO, there's three driving factors behind switching careers:

1. Personal Happiness. If you hate what you do, chances are that negativity is affecting other aspects of your life.

2. Financial. We work to live, not live to work.

3. Future Job outlook. If you suddenly found yourself unemployed and looking for work, do you feel comfortable/confident enough your odds of finding another job?

If any of these apply, then strike out and make waves. If they don't, it doesn't mean that you shouldn't change careers, but I'd consider something else first - like a new hobby or improving another aspect of your life.

It looks like you've got two things going against you, feel free to correct my assumptions if I'm wrong:

1. You're applying to US internships while not residing within the country. Work-sponsored visas are scarce and costly, most companies will not invest the level of resources required for an internship. You need to get here first and apply second.

2. You're applying to some of the biggest tech brands in the world and your resume is average at best. Average doesn't get you into these kind of companies, even with referrals. So even if #1 isn't the problem, your resume needs to be more compelling. Here's some of my experience bullet points to illustrate what I mean by more compelling:

- Led development of numerous features for a proven B2B SaaS Product using MongoDB, Express.js, Angular.js, and Node.js.

- Built a facial-recognition utility in Node.js for mass provisioning of user avatars during the company onboarding process.

- Developed a HTML5-based digital signage solution for Google Chromecast with multicast capabilities.

As for how you improve our own bullet points, here's my suggestion:

1. Each bullet point should be thought of as a conversation starter. They need to lead into a story that the recruiter wants to hear during the interview phase.

2. Context/Terminology. These companies have their tech stack already picked out; they want people who at the very least, have demonstrated some type of experience with what they're using. I could have simply said JavaScript in my bullet points, but it's too ambiguous and does not convey what I want to work with. If I'm a company that uses Angular, I don't want to waste my time interviewing someone who's JavaScript expertise is limited to jQuery. (As you can tell, I'm a JS developer; sorry I can't provide better context to help you in the rails/php area)

Other resume suggestions:

- Rearrange your sections. Highlight experience and skills ahead of education, as that's what tech companies will be interested in first.

- Your project highlights are boring. If you're going to highlight projects on a resume, a recruiter needs to be able to identify a use case behind what's written.

- Either get rid of "2nd top ranked student in my faculty." achievement or provide better context. It's doing a disservice to every achievement listed below it.

- Your skills make you sound like a jack of all trades. Jack of all trades are generally assumed to be a master of none. While I'm proficient in a wide range of technologies, I limit what I present to what I want the conversation to be focused on.

Professionally, I've made the decision to burn bridges on multiple occasions. I'm never a fan of the act itself; but I also have yet to regret the choice in any of the instances.

As far as the outcome, it's always been the same: short-term loss of revenue, but in every case it's cleared way for more fruitful projects.

I've dealt with many different types of beggars on a regular basis during the 5+ years that I've been living in Chicago. While my pockets aren't deep, I do try to be charitable when possible. I only give to those who I see on a regular basis, who come off as humble, non-harassing, and don't display obvious signs of substance abuse. Charity will range from spare change, to extra cash, even food if I'm out grabbing some when I run into them.

Give up on the idea of regulating cybersquatting; it will never happen in a free economy. Counter Points:

1. IMO, a startup who's being held back by a domain shark is already in the wrong mindset and is probably going to fail. Successful startups work with what's available to them and pick up the domain they truly want when they have the capital to do so. Facebook for example, started as thefacebook.com; they purchased facebook.com in 2005 for $200k

2. Yes, .coms are becoming a rarity, but again - free economy; it's all about supply and demand. While .coms may be the ideal domain, it's not like there aren't other completely feasible choices out there. If the .com isn't available, why not .io? .ninja?

3. The drug analogy is incorrect and improper. A better analogy is to think of domains as land. Both are finite in what's usable; and in both cases owners are entitled to deciding what they want to do with the property - whether that's building something, letting it sit there, or selling it for profit.

Don't get mad at people because they thought of your name before you did; accept it as a reality and embrace the practice yourself. A certain founder I know of a publicly traded deals website is sitting on over 100+ domains. Why? The opportunity to use them in the future. I myself am sitting on 20+ for the same exact reason, I recommend you do the same.