HN user

wavesplash

775 karma

"And you run and run to catch up with the sun but it's sinking. Racing around to come up behind you again..."

Posts7
Comments209
View on HN

a) awesome. b) please increase the default font size of that doc. c) please consider moving the exposition to the end and just jump into the good stuff about how it works and what's different. Perhaps a short intro like "Texti is modern markup. Think Markdown and Wikimedia markup had a baby. Here's how to do all the things..."

For patents on physical things/devices, he's giving very good advice. You need to file within the 1st year you've used the item in commerce.

The internet is littered with great products that weren't patented, then copied (sometimes by their overseas contract manufacturer itself just running a 2nd shift on the production line).

If you don't have global patent protection, you find yourself competing with your own product sold cheaper by someone else and no way to fight it. Super common problem for popular products.

If it helps, skip to section 6 for the conclusions (spoiler: Angels are). The section you've quoted is academic signaling (in 'entrepreneurship research') to context and differentiate this paper from other research and entrepreneurship books/papers. And yes, I strongly agree with you: perhaps someday academia will embrace plain English and real hyperlinks.

Hey, thanks for the article. The goal of Hotwire is to remove Ajax calls and minimize Javascript client coding as much as possible. That starts with Turbo as the foundation and then Stimulus is the next layer up. There's nothing wrong with doing what you did w/ Stimulus, but calling it Hotwire creates unnecessary confusion for those new to Rails+Hotwire. That confusion is what I'm addressing in the grandparent comment.

You’re on the right track, but there’s a big difference between under patent and post-patent expiry drugs. Patents last 20 years, so if you invent a drug, patent it, then go through FDA approval, you can charge whatever price you want to recoup development cost until the patent expires. After the patent expires other firms can make ‘generic’ versions of the drug without having to license it. The goal with generics was traditionally take expensive patent drugs and make them more affordable while still retaining reasonable profit - in theory multiple drug makers would create an efficient market price. However, many generics for critical but low volume drugs have become single sourced, and there has been a move over the last 20 years for single sourced drugs to dramatically raise their prices and bleed insurance companies and the unlucky individuals that aren’t covered by insurance. This is what MCDC are fighting.

Postgres used PostQUEL. SQL was added to Postgres by one of Stonebreaker's graduate students (Andrew Yu) around '95. By '95 Stonebreaker's lab was already working on a new distributed Postgres called Mariposa.

Imposter syndrome or just not sure where to go? If it's the latter, there's a structure to enterprise deals that you can usually follow.

1st uncover the buyer journey with some form of this question: "Just so I can help plan accordingly, let's imagine your company decides to move forward, what does the purchase process at your company look like?" Try to unearth all the steps they need to go through (is it out of their personal budget, department budget, VPs budget? Are there other groups we'll need approval from and what does their process look like? (IT, Legal, etc). How long does it usually take to close a purchase and get a vendor paid in your firm?

The goal is to uncover the end to end process that results in $$s early so you can plan accordingly. If the process takes 18months and requires deep IT and Legal approval - make sure you're priced high enough to absorb the pre-sales time & labor.

And when pricing comes up - if you have a well established market, then price within the norms (your champion isn't using their own money, they're using the company's - they just need to justify the cost). If the product is a new category, price the product to organizational value. If your product reduces the number of sourcing staff or multiplies their effectiveness - a typical strategy is to show the business impact. Perhaps Salary of HR hires saved + number of good hires * impact factor on business (whatever works best to show $$s of impact to the business). Then charge a fraction of that value yearly.

There are a bunch of great books on enterprise sales, but 99% of it after showing value is uncovering the purchase plan and helping nurture your champion (and possibly others) to accomplish the sale to their internal stakeholders for you.

And as a previous commenter said before - don't worry about pricing it perfectly. Fit the budget they have today and readjust next budget cycle or during next year's renewals.

Best of luck!

ORMs Are Backwards 7 years ago

While you're not technically wrong at the SQL level, I believe there's a higher level of business problem that ORMs like ActiveRecord solve for that's being overlooked. (aka ActiveRecord got Airbnb and Shopify a long way in scaling both developers and product).

CPU time building a query is rarely the business bottleneck until you're at a huge scale - scaling up the engineering team uniformly and having business logic at abstraction level closer to the rapidly evolving Product specs is the bottleneck that ActiveRecord solves for, and does pretty well.

If you'd like something that avoids object/hidden state - check out how Elixir/Phoenix's Ecto[1] was designed - it avoids many of the shortcomings of ActiveRecord and SLQAlchemy:

1: https://hexdocs.pm/ecto/Ecto.html

If you bought a 1st Gen Firestick, those are sluggish. The FireTV square box are very snappy (I have 4 1st Gen FireTVs that are still super responsive). I also have a Chromecast and the Chromecast never gets used since the FireTVs are so good - and lets be honest, the Chromecast is much more limited feature wise.