rudimental

Really cool tool. Congratulations and great job! Look forward to seeing where this goes.

Feedback: the rerun project button is hard to locate and not prominent. I wanted to rerun the project after making some changes. I felt encouraged to save (fork) or resume playback, overwriting my edits. Make it more intuitive to rerun after making an edit.

I talked to someone at the archive. He said a few people are aware of this, including people involved with the way back machine. It might be hard for them because video content in general doesn't save well, especially if it's hosted on YouTube. I tried out some video streaming, audio streaming, and download links on previous snapshots of the site, and they all lead to error pages.

You might be right. I read it as the YouTube URLs won't be altered / made inaccessible. Your reading may be correct - I'm not sure!

Thanks DoJ. This will definitely make it a little harder for people to access high quality, free content online.

URLs of the videos won't be removed: "Individual video URLs (links) will remain unchanged."

http://news.berkeley.edu/2017/02/24/faq-on-legacy-public-cou...

How could one get all URLs and put them in one place for all 20k+ videos?

Blab used WebRTC. They did this by using OpenTok (made by TokBox).

https://tokbox.com/

https://tokbox.com/developer/

Source: I work there :)

Aha is such a tool - some PMs swear by it. It seems ok. It's super expensive.

The support engineering role can vary from organization to organization. In a support role, you probably won't grow all your coding skills as fast as if you worked full-time developing. You will get good at debugging and some other aspects of development, but you will likely build less and grow less in some areas (unless you spend time during or outside work building). You will still grow, though.

These roles can pay less, it depends. Your market rate is largely a function of interviewing skill and negotiating skill. Work on both of those. Keep interviewing and find the right fit somewhere. Sell yourself (technical and non-technical skills). Did you lead a team at your previous company? What value can you add to projects in your potential new job?

Ask 3 at interviews - "How many support engineers in the past year now work 75%+ time building software for people, internal or external?" If there are previous support engineers, that will give you insight.

Keep practicing your interviewing. You may need to learn some node and a latest (e.g. React, Angular) front-end library. One way to demonstrate is by building a small project, hosted on GitHub, which shows you can build software. These two things (especially interviewing better) is very likely the only thing between you and the job you want (full-time software engineer).

Ways to interview better include practicing white boarding by doing algorithm problems. Think out loud during that, and ask clarifying questions. Same with onsite coding- think out loud, ask clarifying questions.

You have cs degree from a top school, and some entrepreneurial experience. These have value. Many roles are open to you- find one that's a good fit for your and your employer's sake.

Referrals will help you, too. Having an advocate inside the company who knows you will make it more likely to give you a chance.

Good luck!

>The way I see it is that there simply is no neutral news source.

Very much agree here

>BBC Arabic and France 24 are pro-Israel

I find this hard to believe, especially BBC Arabic being pro-Israel. The English language BBC is pretty critical- it would be surprising if the Arabic language articles are more neutral or sometimes positive.

Consider https://hired.com/ to apply to many companies at once. Create a good profile and send notes to to people on AngelList.

Five steps: 1) Read good writing, especially in the genre in which you want to write.

2) Write first drafts. I prefer to think of it as vomiting words to a page.

3) Edit. Ultimately, this is what will make the writing good.

4) Get good feedback. Have a small group of people you work well with give you constructive feedback. They have to be invested enough to care and closely read one or more drafts.

5) Talk with people about the technical topics. This can help you clarify your thinking.

I had 1 amazing and 2 good experiences at Lavash in SF (Inner Sunset) http://www.yelp.com/biz/lavash-san-francisco

Get the Kashk e bademjan - an eggplant dip topped with friend garlic and drizzled in yogurt. So good!

Could you give more insight onto these types of companies? Employees, industries, products, revenue/profit, everything. They sound interesting.

'TED is propaganda. Propaganda of high form.'

Could you elaborate on what you mean here? E.g. propaganda trying to convince people what?

I'm no lover of LinedIn, and I bet they do some shady thing. As to your second email address, I wonder if it's someone trying to 'connect' to you input it. LinkedIn asks for an e-mail address of the person you want to connect to if they're not close enough to you in the LinkedIn graph, and maybe a person put in the other email.

The social aspect makes coding more fun. And getting away from your keyboard is great. What you're describing to me sounds like informal code review, a high level walkthroughs of what your code does and what choices you made and why. It's a taste of pair programming. Talking through your code is great. Implied pair programming sounds about right. Try the full thing sometime!

I'm not sure where you're getting that from. I've read a lot of data, eg the link below, that shows that engineers do very well, but aren't the top major.

With that in mind, it's not as if all students from all majors are required to take the exam- the data represents those people that self-selected to take the lsat.

http://www.potsdam.edu/academics/AAS/Phil/upload/LSAT-Scores...

Here's a link to audio of David Foster Wallace reading the speech:

https://www.youtube.com/watch?v=IYGaXzJGVAQ

Consider a professional that helps people get organized. A house cleaner can help you with some of these, like how often to dust or vacuum. A professional organizer (that you work well with) could help you with more of them, like creating systems that help keep track of documents or organizing your food containers. Check out highly rated people on yelp or get a referral from a friend or national professional organization.

"I like my job but feel like I could be making more elsewhere."

Most likely you can be making more elsewhere. You're not a spoiled brat, you just need to figure out what's important for you right now and get in an environment that can give it to you. There's day to day and the big picture to consider. Money is definitely a part of what's important for most people, but it varies, same with autonomy, chemistry with your team, liking the product- every big thing about a job.

Definitely look around, someone with design and product experience can find another job right now in the Bay Area. You might find a better fit.

Interesting. For some, Dunning-Kruger is probably at play.

http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect

Check into your posture. It's good you have an elevated monitor, and it's worth looking into the ergonomics of your whole setup (and general life).

Old thread about RSI https://news.ycombinator.com/item?id=1269951

Definitely a hard problem. I'd say spend more than 1-3 hours of time with the person. Definitely figure out the culture, or the culture you want to create. Culture fit is not just do I like this person (you need to at the very least respect them- if you don't like or respect them, it's hard to imagine things working out).

Culture fit is supposed to turn away qualified people that otherwise would work well. If you value culture, then it's worth turning away these skilled, fine people. Valuing culture is supposed to do that. Lastly, you shouldn't hire people that are a culture fit but unskilled to grow into or do the tasks necessary. They're a bad option.

What matters to your company? When other people are not in the room guiding them, do they decide things based on what's important to the company/mission/vision? That's part of culture.

New media that might help give some guidance:

http://startupclass.samaltman.com/courses/lec10/

http://startupclass.samaltman.com/courses/lec11/

Read the readings below these videos, especially this one: http://blog.samaltman.com/how-to-hire

Have more than one interview. Try hiring them on a short side-project and see how it goes. It's hard to hide your true self after 2 weeks or so. Ask yourself this: Would you trust them with the life of your company? Would you trust them and 10 of their friends you never met with the life of your company?

AirBnB (or some other company) has the culture interview by someone not in the same role- so an engineer never decides if a prospective engineer is a culture fit for AirBnB. This abstracts from judging fit based on their specific skils.

What're your goals? It can help to direct you to the best place for what you're looking for out of JavaScript. I think it's useful to learn vanilla JavaScript well before learning libraries and frameworks.

Useful books. The first is online and free (the other two are as well, somewhere): http://eloquentjavascript.net/

http://www.amazon.com/Professional-JavaScript-Developers-Nic...

http://www.amazon.com/JavaScript-Patterns-Stoyan-Stefanov/dp...

Solve toy problems to solidify knowledge of methods and syntax: http://coderbyte.com/CodingArea/Challenges/

Good material- lots of video and problems. Not free but worth it: https://www.codeschool.com/ (makers of the jQuery videos below)

Bootstrap - popular front-end framework: http://getbootstrap.com/

Actually build something! A To Do List, a website, a game.

See some different frameworks do the same things: http://todomvc.com/

jQuery: http://try.jquery.com/

Here is a good free node tutorial: http://nodeschool.io/

Some tracks to learn, and get connected with non-profits to make useful things: http://www.freecodecamp.com/

Contributing to open source projects is another route.

Code School has deals for 6 and 12 month subscriptions.

https://www.codeschool.com/sales/black_friday

As others have said, software skills mean you can work in nearly any industry. You can definitely use your skills in a new area!

"Realistically it is too late for me to do an about-face"

Why's that? :) You definitely can if that's what you want. I met plenty of PhD students in their 30s, 40s and 50s (some were in the sciences). Not every grad student is 22, fresh from undergrad, or in their 20s.

These feelings are normal. Definitely talk to close friends, family, a therapist, and people who have felt this way and 1) took the plunge 2) did not.

I'm not sure about any programs targeted at college students. Maybe that would be a good niche.

I would definitely look into internships through your school, and directly with companies, in web development/ software. This is one place where cs students traditionally learned practical skills anyway, and would also help you with developing a portfolio, building a network/community, and work experience.

Here are some sites about bootcamps. One could be a fit, where you'll build a lot and have structure and a community. Talk to graduates before attending, especially if they aren't known as stellar.

http://bootcamper.io/ http://www.bootcamps.in/

Keep a running log of anything that seems missing or any problem you encounter. Extend it to people you are close to, family, friends, colleagues, people you admire. Keep this somewhere you can access easily and from everywhere, like Evernote. What problems do people have? What could be easier? What could make something better? You'll orient your mind towards problems and solutions, and before long, you'll have a long list of side projects from which to choose!

Interesting take! I think there's a lot of truth in what you're saying.

In N Out started in 1948 (not too long after McDonalds, and not too far from it, either, in Southern California). Shake Shack started in 2004.

http://en.wikipedia.org/wiki/In-N-Out_Burger

It is a great time to be into food. Probably better than ever.

I think clarifying the question is helpful. "How do I find investors?" "How to I make the best experience possible with only $7,000?" "How do I not get outbid when outsourcing a project?" "Who wants to help me code on this project?" "How do I develop the skills to build my project?" or "What resources can help me get started?"

Find your niche and own it. This means you have to clearly communicate how your service is the better learning-to-code-online choice than free resources like Codecademy and paid ones like Code School and Treehouse. Active and serious could be it. Find the niche that finds the alternatives too passive and frivolous and start monopolizing them.

Then make it.

Build something- a prototype or a sliver of your service that shows a snippet of the experience. Show the superior grading, or something- anything- so people enjoy their experience. Give them a magic moment or two. They'll notice. Even if it's just one aspect of one language. You don't need to release everything at once.

You asked "how I can find either people willing to help with this, where to find investors..." Sell it well! Make it sound appealing. Why not communicate the enticing elevator pitch to attract interested parties here on HN as well as on elance, GitHub, at your local hacker space, in irc? Most people don't want an essay, just the essence in a sentence, maybe two, at the appropriate moment.

You're always pitching. Give people a reason to want to buy whatever you're selling.

I agree with the advice of validating your idea by asking the target users if they would be willing to pay for the service.

Maybe start making a prototype (Balsamiq/Prototype of Paper rather than code based).

As to keep it hush-hush:

"An idea for a startup, however, is only a beginning. A lot of would-be startup founders think the key to the whole process is the initial idea, and from that point all you have to do is execute. Venture capitalists know better. If you go to VC firms with a brilliant idea that you'll tell them about if they sign a nondisclosure agreement, most will tell you to get lost. That shows how much a mere idea is worth. The market price is less than the inconvenience of signing an NDA."

http://www.paulgraham.com/start.html

Just start. Good luck!