kramer2718

Can you compare what you have built with superpowers?

According to a quick search, GoPro has an Enterprise Valuation of $160M. That would be chump change for a large tech company. The brand has name recognition value in excess of that figure. I suspect some big company will happily buy it but not sure who. It has to be a company that wants to get into the camera market. I don't think the brand name is as valuable to an existing camera company-though I could be wrong.

Apple, Google, and Amazon could all make sense. Google would see the business as an opportunity to strengthen its existing IoT portfolio. Apple an opportunity to add to its integrated consumer electronics offering. Amazon would be more a play to improve GoPro's margins. They could easily push it with prime deals, etc.

I could also see Samsung getting in.

Regardless, expect to see more integration, AI features, etc, after acquisition.

I agree that simply emailing in copies of identity documents after the fact shouldn't be sufficient. However, there should be a verification process that includes verification of identity documents through legal means, including perhaps a processing fee. The fee would preclude many attackers from even trying to break this process.

Maybe this would only work for new accounts as you'd probably need to provide identity information on before losing access.

2015: This meeting could have been an email 2025: This enterprise development project could have been a spreadsheet

Yeah it really amused me that he went through tons of steps, buying lots of new hardware, etc before simply unchecking the delete images box.

This looks AMAZING! Will be doing this for an upcoming project.

Finally! Isaac Newton is pleased.

This is a largely political problem. Cross pollination does not affect the utility of commercial help-only its legality. You can study wind dispersal, etc, but at the end of the day, the problem is a bunch of clueless old men.

(laughs in xzibit)

I realize it isn't your target use case, but I'm tempted to move all of my personal stuff stored in Google Drive over to this.

Look at the code coverage. Not just the line percentage, but look at the more complex pieces. Are they covered or not?

Don't refactor it right away. I'll take your word that the code is shit (frequently the case), but you don't know the idiosyncrasies well enough to know what to do with it.

After you've worked with the code a while, you'll be able to attempt a large refactor. Until then, gather low hanging fruit. Clean up confusing variable names. Add comments where needed. Write your new code as clearly and cleanly as possible. Use a tool like sonar to inspect your new code so that you don't introduce new problems.

Most importantly, ADD UNIT TESTS. That will make sure that your new code works with the old and it will allow you to attempt a larger refactor while being sure that you aren't breaking anything.

If necessary, you may need to add some integration tests as well.

I've been in your shoes. Bad code is no fun, but don't let it get you down. Focus on the happy parts of your job (team, culture, whatever). Good luck!