andric

Seems like every time a tech company rebrands, it’s a cry for help.

Yep. Job numbers are the “actual economy” – the actual economy is driven by wages and consumption.

Stronger wages → stronger consumption → higher demand-pull inflation.

But higher inflation implying that “rates should go up” is central bank doctrine. It’s not a general law of how economies function.

Central banks intervening with interest rate adjustments is what distorts the prices of equities downward, when inflation rises.

Without central bank intervention, inflation should theoretically push equities higher (a highly-inflated economy driven by rising demand is by definition a well-performing economy!).

Central banks intervene because runaway inflation can be harmful to wage-earners (they save in dollars, not assets).

But I’m not sure if a 2–3% inflation target is ideal. It seems to me that this arbitrarily low inflation target restricts the growth of the economy in ways that might affect wage-earners, defeating the stated purpose of monetary policy, since higher rates also have the effect of curbing job growth as well as raising the cost of servicing mortgages.

They do have intrinsic value!

Growth stocks trade on a multiple of earnings: earnings have intrinsic value.

Your pricing currently seems prohibitive for that kind of use case. Shouldn't it be usage-based so one can build a product where users can connect their apps without having to worry about arbitrary limits on plans? There should be a PAYG option that simply charges per connection, and automatic volume discounts.

Oh this is what I have been looking for all this while! I was previously manually copying from uithub and Gitingest but that wastes so many tokens

I’ll try it out.

Thanks for making this! Any chance this could be open sourced so we can run it locally?

Does that mean that using Prisma Accelerate and Pulse with an external database will cost the same as using it with the bundled database? (Since I don’t see database-specific costs for storage, read replicas, PITR, backups)

Congrats on the launch!

I’m a bit confused about the pricing.

The docs and pricing pages on your website don’t seem to outline how the pay-as-you-go pricing will work.

Is this still being figured out?

A fellow HN reader I know in a Covid Cautious online community shared your comment with me, and I just wanted to come here to say that you’re not alone.

There are some of us who stay largely indoors and only leave the house for essential visits, with a respirator. I’m one of those people.

I don’t know if you’re able to find a local community that’s cautious too.

But if you want to talk, I have contact details in my bio.

It has now shut down :(

I loved this site; it was what Spotify on the desktop should have been, but isn’t.

It is legitimate.

See:

[0] https://covid19.nih.gov/covid-19-topics/long-covid

[1] Davis, H.E., McCorkell, L., Vogel, J.M. et al. Long COVID: major findings, mechanisms and recommendations. https://www.nature.com/articles/s41579-022-00846-2#citeas

Why do you think I said Long COVID is shaping up to be like HIV/AIDS?

The parallels between the two are stark: How the CDC and NIH bungled public health advice and research funding, how clinicians are ill-equipped to treat it, how the public is clueless about the long-term harms of post-viral immune dysregulation [0].

[0] https://www.ncbi.nlm.nih.gov/pmc/articles/PMC9608044/

Both AIDS and Long COVID are post-viral, multi-organ, chronic conditions that dysregulate the immune system, through many of the same mechanisms [0].

They are also conditions that severely affects the quality of life of those who are afflicted, increasing the risk of severe life-threatening illnesses [1].

Similar to the early years of the AIDS pandemic (which, I might add, is still ongoing), the harms of Long COVID are not widely understood or acknowledged in clinical practice or among the general population.

[0] https://www.ncbi.nlm.nih.gov/pmc/articles/PMC9608044/

[1] https://www.nature.com/articles/s41579-022-00846-2

And Long COVID is shaping up to be our generation’s HIV/AIDS.

History rhymes because people don’t ever learn. We deal with one problem or crisis at a time, instead of generalizing what was learned in order to help future generations avoid the same mistakes.

Which narrow subset in particular, and why do you say that?

That’s because most of such “UX” articles are written by junior designers looking for a job (writing to promote themselves) or working in an IT services agency (writing to promote the agency).

These individuals tend not to have a whit of formal HCI education or real-world practice.

When you have little theoretical grounding and real world experience, all you have is examples from apps you spot in the wild to learn from. You don’t know what makes something work, and you have never seen it work yourself.

You might learn the wrong thing: that if some popular or financially-successful app out there has implemented a particular design pattern, that it must be a “best practice”.

It’s kind of like how most “how-to” articles, YouTube tutorials, and Udemy courses in software dev are made by junior devs.

Since the docs mention deploying to Fly.io, I wonder if it’s possible to use their managed LiteFS service for backup?

The phase after the hype dies down is called “The Slope of Enlightenment”. Hopefully that’s true for crypto, since the space has incubated a lot of good but poorly-executed ideas.

Microsoft helping climb the slope of enlightenment doesn’t sound like a half-bad idea.

DevRel or Sales Engineering roles, maybe?

Thank you for the quick response! You guys are building something really cool, I have no doubt that once you figure out pricing it has the potential to go viral.

I’m a product/frontend guy who’s trying to build a side project, and backend stuff has always been a PITA for me to figure out.

Right now I’m torn between investing time to learn AWS Amplify, or investing time to learn 8base.

8base has already captured my imagination, and I can’t wait to go further with learning it. Unfortunately I feel uncomfortable creating a few projects to practice and then later being shut out of them or be forced to pay $8/mth.

Being sustainable is important, but not at the expense of people’s ability to tinker/learn.

At the very least, offer a highly-limited and almost-crippled free tier, like Heroku or Glide does. Maybe you can only register a few users. Maybe the # of function calls are limited to a few a day. Or maybe dormant apps go to sleep.

Second this.

A timed trial just feels weird. I like that Heroku, Netlify, Contentful, and Firebase have a free tier, so I can use it for small demos and to learn the platform. If I have to pay for every single tutorial or playground project I won‘t want to use the platform or even want to learn it.

It also kind of disincentivizes teachers on online platforms (like Udemy) to teach it. Because you often need to go through a few examples in order to learn something. i.e. if I do a node.js course, the course author isn’t just going to make me build 1 practice app, I’m probably gonna build a few and then host them on Heroku free dyno, the same way if I take a React course, I’m gonna build a few practice apps and host them on Netlify.

SEEKING FREEELANCERS & SELLSWORDS

Location: Singapore (GMT +8), remote’s totally cool with us!

### Hackers only

We’re looking for an independent, inquisitive full-stack dev to help us set up a custom Shopify or node.js/Rails/Python site for a frozen food delivery startup.

Must be familiar with ecommerce and using tools like Git for versioning and collaborating with a designer.

We’re looking for someone who's able to be agile and work with our designer to figure out a tech stack that fits with what we’re trying to achieve.

!------------------

### The Project

* A responsive ecommerce and membership website

* For a packaged food delivery startup

* Serving busy fitness-conscious professionals

* Existing company, existing website, looking for a long term maintainable solution

!------------------

### The Brief

There are a few custom features that need to be built:

1. Membership portal with credit points that can be used in lieu of cash

2. Step-by-step onboarding wizard that helps new customers find the product that fits them

3. A human friendly CRUD interface for the staff to administer the site on a day-to-day basis including product inventory, orders, payments and content.

4. Some kind of CRM dashboard that allows the staff to target specific user segments (based on conditional filters) for promotions.

And of course:

Standard ecommerce interface for searching and browsing products, customizing products, adding to cart, feature products on the front page, sort products by category, checking out via Stripe/PayPal/Braintree.

We are okay with using existing platforms like Shopify, Intercom, or Stripe, since we are a lean startup, so bonus points if you can do integrations very well.

This will be a 2-3 month long project and we’re willing to pay up to 15,000 USD. You'll be working with a UX/visual designer.

!------------------

### Sound good?

Email me: andric@nuisance.co

SEEKING FREELANCER/CTO, Singapore-based lifestyle startup, remote

- We are an online film discovery platform based in Singapore. The filmmakers we work with and audience is international, however. We’re always looking to expand our horizons.

- What are we building? JUMPTHECUT, a delightful & simple way to watch films you’ll fall in love with.

- Where are we now? We’ve gotten pre-seed grants to start development and are past MVP/validation

- We are 80% done with our v1 to launch next month and are planning to raise our seed round in a few months.

- Where can you fit in? A long-term creative partnership with the unique opportunity to disrupt the film industry.

- Our dev stack is: node.js, CoreOS, React.js, CouchDB, Grunt/Bower, Foundation, and SASS/Compass.

Here’s a taste of what we’ve done so far: http://jumpthecut.com (unfortunately only the landing page is ready for primetime).

Email me at andric@jumpthecut.com, and tell me your favorite films. ;)

Android doesn’t drive early adoption, so it would make sense to leave it out while you let iOS “take the cake” so to speak, for a while at least. Android, being the dominant platform with a huge mass of people in the early-to-late majority part of the bell curve, makes sense for when you want to scale.