robot

what an extremely vague article. after hundreds of words there is still no clear explanation of what it is talking about. very poorly written.

awesome

this is very useful, the first video I hit was a very educational one with no fluff.

As datapoint agree and I do the same. Not using FB, not following anyone, only using it for interest groups.

Not using linkedin, it is trash.

Have Instagram but not using it. too much effort in posting a photo, see no point in showing off (usually a show off platform)

Twitter - gone crazy last week, most recommendations are irrelevant and interactions not genuine. I do use it to be informed though, better than watching cable filled with ads.

So yes, there is no good platform to connect with the world.

yes, only that it will take 2-3 years of work on the new topic. One benefit of it at this age is your brain will remain fresh and young.

Dear Yonghao, no matter what you improve, when I see 6 ads before any actual search results everything turns to shit.

agreed, your wants take precedence. If there are enough buyers like you who care about hardware freedom they'll drop this feature.

There is some kind of balance since both of those are free. I'm sure they prioritize user engagement and any loss of users is inadvertent.

Remote attestation or not, "Software freedom" fighters should understand that things happen based on some user base need. Somebody needed this and they added it, whoever needs it doesn't care if they can't run linux on it. If the user cares about running anything else on the hardware, they will add a way to disable the feature. it is all about the user need.

if you are a secondary priority user on some hardware, the way to fix it is to focus on becoming important enough to be prioritized instead of fearing some technology will limit things.

The low hanging fruit is to eat less. It is a known fact that people with diabetes live longer due to the stringent diet they are on perpetually. Processing food and burning energy speeds up aging.

Problem is it still requires an API to integrate. Stripe has all these capabilities but API integrations are needed to use them. If you are looking to build a micro SaaS without needing to deal with billing API integrations check out our software: https://saasbox.net. Built for completely eliminating any billing related SW development. It doesn't handle all the corner cases mentioned in the article, but some of them are handled, such as plan upgrade / downgrades with pro-rating, editing plans on the fly, migrating users across plans, notifying your application on those changes.

The article has good points but misses the actual answer in my view to "what software engineers can learn" or in fact anyone can learn from this.

Don't join a company only because there is more money. If you don't know what one click checkout is or have any intellectual interest in it, but jump on it just because you can make more, you will be disappointed. This works the same way in everything in life.

One must have genuine interest in what they do, before compensation.

they should be on the left

The newsfeed-like results with pictures look good, it is fun to browse them.

UX: Lost me on the home page. It says, type help, ask, search, 3 different verbs and all I want to do is search something and find an answer. Too confusing.

The input box is too narrow so it is hard to click it (Do look at google's and it is wider)

I hope it works, but UX is not for me.

Yeah Google sucks more every year so that means next year it will be even worse.

We use Elastic Beanstalk with NodeJS. It works seamlessly, it does use containers as the underlying infrastructure but we don't see them, or manage them. Deploying takes not more than 10-15 seconds. It doesn't break. Devops maintenance work is very little.

Pricing page is to make the user make a quick buying decision, not distract the user with a features tour. You do that elsewhere.

But the tooltips and small gifs are an awesome idea!

My answer is that it is not in high demand at all. It is the news sites that tell these false stories for hype.

I was at downtown Woodside CA last week and outdoor dining area was packed. And this is one of the most conscious places. I believe with a limited number of people and distance rules outdoor activity is okay, but dense outdoor dining is suspicious.

Same with beach. beach is okay, a packed beach (try a popular one in half moon bay) might not be.

no significant side-effects _for now_.

The announcement reads like the days of the first regular computer release.

I wonder if there will be a personal quantum computer, and then a quantum mobile phone.

What are the key benefits of your product to your customer? Who exactly is the customer? You need to work these two out first for sales.

Most early stage startups don't have a product as beneficial to anyone as they think. So really need to work out the value and make it stand out, increase the value. They say 10x better because of this. Chances are an early stage product's value is mildly beneficial. Mildly beneficial = No sales.

Work out the audience. Go to a slightly less-than-ideal customer = Too much effort to sell or no sales.

OK So once you are at this point you are already equipped to sell. A nice product whose key benefits are clear, and we know exactly how the buyer will use it and benefit from it. I will bet dollars that you are not there yet.

Now all you need to do is help and enable the customer (e.g. integrate your product, make them see the magic by configuring it for them, or give them samples). You must not be salesy, but act as if you are an assistant that works to make the product's value realized for the user. At this point before spending the resources (time) double check this is a serious buyer with budget.

At this point as the user has seen the magic, you can ask for payment. Sales #1 complete.

Do 50 such sales and then you can care about metrics, efficiency etc.

What! How is it that there is yet no evidence that there is a planet in another galaxy?

It will be free of concurrency bugs including deadlocks. This is the promise of CSP. The requirement is data is shared only via blocking IPC and never directly using a lock. (and similarly one must not share a pointer to private data, as another poster has pointed out)

You can compose small systems, even with multiple parties, prove they cannot deadlock, then make them a 'black box' with defined IO, and build larger, more complex systems with equal properties.

The downside is you must guard every piece of shared data with a separate thread, but there may be ways to reduce the performance penalty.

This is interesting in that if you can use channels as described by the CSP book[1] you could build a kernel that is guaranteed to be free of concurrency bugs.

This would be important because even if you have proven the functional correctness of a kernel, that typically excludes the concurrency aspect.

[1] (https://www.cs.cmu.edu/~crary/819-f09/Hoare78.pdf)

I agree it is awful advice. Early stage startup will be similar to FAANG except a lot more work and much less compensation.

work out your product, buyer persona, business model, go to market, and tell a coherent story around these for why you will succeed and you will get replies.

the cold email contents will be a concise summary of the above.

I am actually pretty curious to see a demo of features from you that backs up that RISC-V is bad and Open Power is much better.

What convinced me was how thin the RISC-V book[1] is, and I have seen both ARM and Intel reference manuals. For example the V extension removes need to specify data size, greatly reducing instructions needed.

I have no idea about Open Power btw.

[1] http://riscvbook.com/

P.S. I am hiring U.S. candidates for ARMv8, x86 roles: https://careers.vmware.com/main/jobs/R2009422?lang=en-us

RISC-V is pretty awesome as an ISA. Give it a few years and it can solve all of these problems.

This is the ultimate app idea for covid times parents, I will definitely check it out.