HN user

FindMySocks

13 karma
Posts0
Comments29
View on HN
No posts found.

One could comment about Brexit in the same way. There were a myriad of reasons to stay in the EU, which are becoming more apparent each passing week. But good propaganda will help turn the minds of the disillusioned into thinking that there will be nothing but unicorns and chocolate cake for one and all of only the pesky EU wasn't in their way.

My First CSS 5 years ago

The question then comes, where would one go to learn the fundamentals-and what are they now?

Being someone who was ahead of the game in css 15 years ago, but not having touched it since - where would one go to understand the new fundamentals and options available?

I found electrical engineers to be similar.

Computer science degree holders were mostly lacking ability in my experience.

But I wouldn't count anyone out by their degree.

Their cover-up of the true scale of the problem (lab leak or not) made it hard for politicians in other countries to lock down quickly. It helped it spread intentionally to multiple countries and by then it was too late.

I disagree. The actions from a lot of countries were absolutely lacking, even when they could see how bad it was given both China's data, and Italy, Israel's initial incidents.

China locked down super hard towards late February/mid-March.

During this time there was countless reports about the "ridiculous" and "draconian" lockdowns that occurred in China. The West basically pointed fingers, laughed, and said we'd be fine. And yet they're still not.

If they were blasting their sirens early in 2021 instead of covering it up we might have had swifter border closures etc.

I agree that even earlier warning would have been good. I just don't see it changing anything. Countries only started to take it seriously when it really started to affect them. They didn't want to risk a political/ financial hit on taking the measures that were needed, and they paid for it.

Exactly this. It's to measure the nuances between designs to see if they improve user interaction.

If you're at the AB stage you should have a fairly mature prduct where you're optimizing to move forward from the low-hanging fruit customers.

Honestly OP this is your best solution. First find out if there's an easy accessible market for your project, and if it had costumes interested in it.

I promise you that is better to start off with validation of your concept, and an interested market (who you can then start testing your iterations with), before you write a line of code.

If you can't get product market fit, then either there is no market, or you've simply not found the market yet/sold the concept of your product well/or the market just doesn't want what your offering.

I would say that as the PM role is one without actual power, you need to convince those who will be working on a problem to be convinced that what you're doing makes sense. With data backing them up, this makes your assumptions more trusted, and the team easier to convince.

I'm curious as to know what your PM's roadmaps look like, because really they shouldn't be listing features/implementation, but objectives and goals.

I agree though with what you're saying, regardless of the technical capacity of the PM, it's not really up for him to decide the capability of the teams, or the proposed technical solution. He should be managing those with the engineering teams, and their thoughts should be reflected on the roadmap.

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.

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.