Yes, they will be able to do this, but it's a lot of work, and Lovable has a pretty good head start.
546 karma · joined February 1, 2013
Yes, they will be able to do this, but it's a lot of work, and Lovable has a pretty good head start.
Yes, a strong female character in big budget movies wasn't a common theme. Aliens 2 also had a strong female protagonist played by Sigourney Weaver. The movie was also directed by James Cameron.
Terminator 2 was a huge cultural phenomenon. I remember going to the movie theater with my Dad to see it. I think it was the first R rated movie I saw in the theater, so it was something that we bonded over. Many of my friends had a similar experience.
One approach to deal with ambiguity is to write a short design doc, which writes down what you are trying to do, and all of the assumptions that you are making. If you don't understand the domain, some of your assumptions will probably be wrong. The stakeholder should be able to see that and provide guidance.
I don't think Netflix used any of the algorithms. I suspect they have more data on the user and movies than was presented in the contest.
I agree, if all of the content is garbage, then you don't need a model, you could simply pick something at random.
A good leader might try to keep you on the team, if they like you and you miss your numbers for a couple of quarters. From what I've seen, Sales is pretty brutal. It's quite common for Sales folks to lose their jobs, even if there are circumstances outside of their control. If they do keep you on and you don't meet your OTE, you will get paid less. In many ways their job is harder and has more risk than software engineers trying to deliver a software project on time. Which also very hard to do!
When you have a large PR like this, here's how I like to get it reviewed.
1. Give reviewers sometime to become familiar with the PR. They might not understand all parts of it, but they should have at least a cursory understanding of the PR.
2. Have a meeting where the PR is explained in front of the group of reviewers. The reviewers will understand the PR better and they can ask questions in realtime.
3. Let folks review the PR after the meeting in case they spot anything else, or think of additional questions.
Most of the time PR review is done asynchronously, but doing most of the review in the meeting can also be a decent team building exercise.
I don't think anybody is going to be permanently underwater. Home prices changing should be a second order effect of building more apartments.
It may have encouraged some slaves in the Confederacy to flee, if they found out about it.
It will be different in each state, since each state imposes different levels of gas taxes and has different registration fees.
It would be very hard for a company to build a sustainable business that way.
"Java is a blue collar language." - James Gosling
My sense is you might get paid when you start what an undergraduate makes after one year and a pay raise.
Your career will probably develop faster than the person who started working after undergrad. Your ceiling is likely hire.
I don't have a PhD, but this is what I've observed.
I was thinking more like the Les Grossman character from Tropic Thunder. The character was played by Tom Cruise.
However, many times Engineering teams are asked to build something that is speculative. Leadership and the Product team thinks they are building something that could make money in the future and justify the investment.
Other times folks are building something which is directly attributable to existing customers revenue. It may be that it won't bring in any additional revenue, but it will reduce OPEX and improve the margins of the business.
It's a good idea to understand which type of project they are working on from the business perspective.
I think degen is the common term that used here. It's short for degenerate.