FindMySocks's comments

I'm pretty sure the delineation of the PM and TPM roles is not internal vs. external customer facing, but where your main skills lie in terms of what you're handling.

PMs are usually more upfront in understanding the customer and the business needs. Whereas a TPM, is more behind, understanding the customer but moreso managing the tech teams and solution architects to deliver the proposed solution.

However, the PM role is fickle, and seemingly no company does it the same as another.

You're a software engineer that doesn't use github or even bitbucket to store your personal project code? Not even a googledrive, dropbox, box.net sync services?

I'm a bit at a loss for words to be honest.

I've just run a nice unsuccessful Adwords campaign, and I think my lack of knowledge on how to correctly use Adwords, alongside Analytics is where I'm going wrong. Any chance you know of some decent resources / quick-start guides to help understand Adwords and how to use it?

I don't think the social credit system blocks you from all forms of transport. From my understanding it's more like you don't get to use the high-speed trains and airlines. You still may get access to the lower speed trains/busses.

Have seen that being done in a long time here. I don't think they've done this or the last 4 years.

Corruption is still seen as just a part of business here in China. Every level of employee that can do it, often will.

Do you have Team you're overseeing or working with?

I'd take the time to ask each member of the team, what they are working on, what problems they are having, and how you can assist them in some way.

The product your company/team is building will have a roadmap of features to be delivered, spend time with members of the Dev team talking through each of those features, what is required, how they plan to build them.

As a senior, you may not know the platform, but you can get to know how the team works, offer suggestions and identify probable pain points. There might be entire sections of code you can work out that needs to be written which don't necessarily require knowledge of the platform.

All this will take time, be incredibly useful for everyone and in your spare time you can learn about the platform.

For those interested: over here in China (specifically Shanghai) is a massive bike sharing war being fought, where the two largest incumbents have been given well over $200m in investment money over the last year. The leading brands are Mobike and Ofo, with around 4 other small competitors creeping in.

Mobike was started by an ex-Uber China manager, launched in Shanghai - whereas Ofo had been developed as a bike sharing scheme in universities.

Mobike has GPS enabled, QR unlocked bicycles. Where as Ofo are not GPS enabled and are unlocked with a simple analogue pin code bike lock.

If you want to know more, let me know.

It honestly depends on how complicated your app will be, and how talented you already are as a developer.

But in truth, you should probably be looking at making your Minimal Viable Product in whatever you are the most comfortable in. Because you'll want to get it out and in potential customers hands as fast as possible and prove that your idea really is as useful to people as you believe.

I'm also going to take a stab here and say that you're probably not a super experienced developer, because trying to launch and support an app across two different platforms in different languages almost simultaneously isn't an easy feat to manage.