markbao

Goody is hiring a full-stack Staff Software Engineer who likes to ship at a startup pace and has an eye for exceptional UI/UX.

I'm Mark, the technical co-founder and CTO at Goody. Despite being something everyone does, gifting is one of the areas of commerce yet to be disrupted. Our goal is to make people's days by making gifting easy, while building a sustainable business on that market opportunity.

We're looking for engineers who like to build at a startup pace, have a critical eye for detail and user experience, and thrive when given autonomy and ownership.

Our product is used by Google, Stripe, Anthropic, Meta, NBCUniversal, Notion, and others, and we also offer a developer API for commerce.

Check out our jobs minisite at https://jobs.ongoody.com/swe and feel free to email me at mark@ongoody.com.

Web apps can ask for your location or microphone the same way native apps can. Just reject it, there’s nothing that says you have to accept on either platform, so to say that’s a negative for native apps is odd.

The biggest downside of native apps is you can’t customize them with extensions or user styles like you can with websites.

There are two good reasons for SPAs that I can see:

1. Your app probably needs interactivity anyway; for most apps, it’s not just going to be HTML and CSS. Writing your app in some unholy combination of React and HTML is not fun especially when you need to do things like global state.

2. Loading the structure of pages up front so that subsequent data loads and requests are snappy. Getting a snappy loading screen is usually better than clicking and getting nothing for 500ms and then loading in; the opposite is true below I’d say 100ms. Not needing to replace the whole page results in better frontend performance, which can’t really be matched today with just the web platform.

Basecamp has probably invested the most in making a fairly complex webapp without going full SPA, but click around for like 30 seconds and you’ll see it can’t hold a candle in performance to SPAs, never mind native apps.

With that said, I agree that I’d want the web to work more like the web, instead of this weird layer on top. All the complexity that Next.js and SPAs have added over the years have resulted in more responsive but sometimes more tedious-to-build apps, and gigantic bundles. I just don’t think you can match the performance of SPAs yet with just HTML.

I don’t use AI for most of my product work because it doesn’t know any of the nuances of our product, and just like doing code review for AI is boring and tedious, it’s also boring and tedious to exhaustively explain that stuff in a doc, if it can even be fully conveyed, because it’s a combination of strategy, hearsay from customers, long-standing convos with coworkers…

I’d rather just do the product work. Also, I’ve self-selected by survivorship bias to be someone who likes doing the product work too, which means I have even less desire to give it up.

Smarter LLMs could solve this maybe. But the difficulty of conveying information seems like a hard thing to solve.

Found plenty of people online with the same issue but no resolution.

Finally just paid the $25 to get the OEM SteelSeries replacement cable and it charges fully again. wtf… I guess the replacement cable was USB-A to C and I’ve only tried USB-C to C cables?

You trade off adding limitations for how much you can do in a design and move things around freely, and in return you gain more convenience and less work needed to organize designs. You can change designs around quickly… as long as they’re within the rather confined limitations of Auto Layout.

I think the fundamental disagreement is that one person sees creative empowerment as freedom from doing busywork, whereas another (including the author) sees it as freedom to experiment with a design without limits. Neither is inherently wrong, but the two are inherently in conflict.

—

Principal Software Engineer — Lead our platform end-to-end, guide cross-functional decisions, and ship at a startup pace. Ideal candidates have previous startup experience as a founding/early engineer or founder.

$250K – $300K + equity

https://jobs.ongoody.com/principal-swe

—

Senior Software Engineer — Ship a startup pace and with an eye for exceptional UI/UX.

$170K – $230K + equity

https://jobs.ongoody.com/swe

—

I'm Mark, the technical co-founder and CTO at Goody. Despite being something everyone does, gifting is one of the areas of commerce yet to be disrupted. Our goal is to make people's days by making gifting easy, while building a sustainable business on that market opportunity.

We're looking for engineers who like to build at a startup pace, have a critical eye for detail and user experience, and thrive when given autonomy and ownership.

Our product is used by Google, Stripe, Anthropic, Meta, NBCUniversal, Notion, and others, and we also offer a developer API for commerce. We’re 5 years old and post-PMF.

Check out our jobs minisite at https://jobs.ongoody.com/ and feel free to email me at mark@ongoody.com.

Goody is hiring a full-stack Senior Software Engineer who likes to ship at a startup pace and has an eye for exceptional UI/UX.

I'm Mark, the technical co-founder and CTO at Goody. Despite being something everyone does, gifting is one of the areas of commerce yet to be disrupted. Our goal is to make people's days by making gifting easy, while building a sustainable business on that market opportunity.

We're looking for engineers who like to build at a startup pace, have a critical eye for detail and user experience, and thrive when given autonomy and ownership.

Our product is used by Google, Stripe, Anthropic, Meta, NBCUniversal, Notion, and others, and we also offer a developer API for commerce.

Check out our jobs minisite at https://jobs.ongoody.com/swe and feel free to email me at mark@ongoody.com.

Goody is a gifting platform that makes personal and professional gifting easy. Founded 5 years ago, our product is the UI/UX leader in the space and is used by Google, Stripe, Meta, Notion, NBCUniversal, DHL, and others.

Our market has hundreds of billions in TAM with no established leader, and our goal is to build the best product in the space, win the market, and bring more delight into the world.

We’re looking for an Engineering Manager to lead and grow our small and talented team of 4 full-stack software engineers at Goody. In this role, you’ll have the opportunity to build an insanely great product, influence the growth of our team members, and cultivate an exceptional engineering culture.

See the full description and apply here (and mention HN): https://jobs.ongoody.com/engineering-manager

Goody is hiring a Senior Software Engineer (Ruby, Rails, React) who moves at a startup pace, likes to ship fast, and is motivated by building delightful products.

I'm Mark, the technical co-founder and CTO at Goody. Despite being something everyone does, gifting is one of the areas of commerce yet to be disrupted. Our goal is to make people's days by making gifting easy, while building a sustainable business on that market opportunity.

We're looking for engineers who like to build at a startup pace, have a critical eye for detail and user experience, and thrive when given autonomy and ownership.

Our product is used by Google, Stripe, Meta, NBCUniversal, Notion, and others, and we also offer a developer API for commerce.

Take a look at our application (and a cool WebGL thing I built for it) at https://jobs.ongoody.com/swe and feel free to email me at mark@ongoody.com.

Goody is hiring a Senior Software Engineer (Ruby, Rails, React) who moves at a startup pace, likes to ship fast, and is motivated by building delightful products.

I'm Mark, the technical co-founder and CTO at Goody. Despite being something everyone does, gifting is one of the areas of commerce yet to be disrupted. Our goal is to make people's days by making gifting easy, while building a sustainable business on that market opportunity.

We're looking for engineers who like to build at a startup pace, have a critical eye for detail and user experience, and thrive when given autonomy and ownership.

Our product is used by Google, Stripe, Meta, NBCUniversal, Notion, and others, and we also offer a developer API for commerce.

Take a look at our application (and a cool WebGL thing I built for it) at https://jobs.ongoody.com/swe and feel free to email me at mark@ongoody.com.

God, it took all my energy not to close the tab after reading this opening sentence.

> But it [freeze-dried ice cream] wasn’t ice cream, it was a simulation of ice cream, and no one in their right mind would chose it over the cold, creamy stuff on a hot day. Not even an astronaut.

The "people aren't eating it because it's inferior" line is easily defeated by the fact that people are eating Soylent. I and a good number of other people choose Soylent over real food sometimes, so that line of reasoning is pretty much bunk. What is inferior, anyway? "Real food" is definitely inferior in terms of how much time it takes to prepare, say – and you can't assume that everyone has the same value system (e.g. taste over everything). Cost and convenience are absolutely essential factors to consider with food.

> Most humans are happy to eat real food, and crave it in its most natural form. A strawberry picked at the height of summer. Fish pulled from a river and grilled over wood coals. Sourdough bread made from a twenty-year-old starter, and kneaded by hand. Wine grown on knobby vines, and aged in a dark cellar. Why would you disrupt that?

Some humans, like myself, are also happy to eat "not-real" food like Soylent. Why would you disrupt that? Why is having more choice not just a problem, but a "sickness" as the title suggests?

I frequently see (and dislike) HN comments like "what was the point of this article?" but, in this case, I really have to ask. There are some really good reasons for not liking Soylent, like that it's not entirely proven yet that 100% of nutrients are absorbed when in the form that Soylent takes, so eating it daily may not be giving you all the nutrients you need—along with a bunch of other reasons. Yet this article settles for "it's not real food and people shouldn't be eating it."

N.B. Maybe the real Soylent sickness is that people like me who drink Soylent go on online forums to write walls of text defending it.

1. That it's his fault isn't so clear. The developer claims he was not notified that there was a linked account until two days after a ban. If you listen to the recording, he asks why he was not notified, and the representative does not give a good answer.

> Developer doesn't release said blog post, so Apple releases statement with said facts to protect themselves for further incorrect accusations.

2. If we are to believe the developer, then he actually sent a draft of the blog post to Apple, then Apple doesn't respond and instead posts a public statement.

> What is the developer trying to achieve here exactly?

3. Telling his side of the story and what happened. If we just heard the Apple side of the story and that was it, then we would assume, as many did, that the developer did do review manipulation. If we didn't hear about his side, we would have had no idea that Apple discovered the fraud on a linked account and wanted a blog post explanation to reinstate the account. Apple's statement was incomplete given everything they knew; there was no talk of "linked" accounts or anything of that sort.

> Sounds like the developer is guilty as sin for this fraud

4. Again, if we are to believe the developer, there was no intent to defraud anyone, so I think it's a stretch to say that he's "guilty as sin" for it. The only fraud would be his cousin's fraud that his account is connected to, which Apple failed to notify the developer about until two days after closing his account and after the blog post.

HN strips the characters out from comments, but they're displayed in the beginning of the article.

If you see only one photo, it should be this one: https://i.imgur.com/kTtWZ3f.jpg

Unless if it's during commuting hours, in which case they're pretty much equal I'd say.

> Due to #2, most NYers have to have a car

Definitely not. 56% of NYC households don't have a car, the highest proportion in the US among cities. Compare to SF where 31% don't have a car. https://en.wikipedia.org/wiki/List_of_U.S._cities_with_most_...

I'm not so optimistic. I'd presume a nontrivial number of people would be confused and leave a 1-star review. I can't imagine how many people are confused about how the Kindle iOS experience works.

Sibling comments have brought up some good points about the baseless claims in this post. The CEO also quotes this Let's Encrypt blog post on "Why 90 Days":

> "Ninety days is nothing new on the Web. According to Firefox Telemetry, 29% of TLS transactions use ninety-day certificates. That’s more than any other lifetime"

> so whose certs are these? Of course Comodo's!!! So they are admitting they are copying our innovation of 90 day free ssl certs!

So is the CEO saying that 29% of TLS transactions on the web are on sites which use Comodo's 90-day free trial SSL certificates, probably used on sites with the least traffic on the web? That at any one time, 29% of TLS traffic is over an unrenewable 90-day trial cert? Huh, seems implausible for some reason!

----

The post right above is also misinformed as well:

> From a legal standpoint (ISRG) should have trademarked this when they started using it publicly in November of 2014. There negligence to have done so is why this debate is happening. Then they want to cry foul because of their failure to follow the simplest of product protections. Registering your trademarks. The one who is in possession of the registered trademark is the owner, and that is the law.

Correct me if I'm wrong, but "from a legal standpoint," there has to be evidence of use in commerce before a trademark can be registered, and it's crystal clear that Comodo did not use "Let's Encrypt" in commerce, and it's also crystal clear that ISRG did.