I didn't try it, but for the paid version, someone also built a MCP server based on the scripting engine.

I'm programmatically adding analysis to sim racing lap guides, therefore my flow is probably different from the usual editing flow, but I have to say I found Claude Code + Opus to be quite capable of making edits with computer use.

It doesn't matter how much the employee costs. Let's assume you can hire two Juniors or one Senior for the same salary. If you have to optimize for ARR per employee - you can only hire one person. And if you have the choice between hiring a Junior or hiring a Senior... you're going to hire the Senior.

Goodhart's law fully applies here.

Comments URL: https://news.ycombinator.com/item?id=43892891

Points: 3

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=43543502

Points: 1

# Comments: 0

Anyway, I'm doing the same - one extra tip is to use the "project" feature of Claude Desktop to give your coding assistant some context - use it similar to .cursorrules.

I have respect for the individuals that started this investigation, and the ones that made sure this is publicly disclosed. This could have easily been swept under the carpet.

Actually, that they uncovered this on their own and publicly disclosed it sounds like they have an above-average privacy culture in place.

I know the odds that the person(s) who kicked off this investigation are reading this comment are very low, but if so: Kudos, well done!

From https://www.geekwire.com/2023/google-cloud-posts-second-stra...

Yes, Google has killed a lot of products... but none of those ever came anywhere close to turning such a profit!

Two examples from the top of my head:

Confluent Kafka: https://developer.confluent.io/courses/hybrid-cloud/intro/ MongoDB Atlas: https://www.mongodb.com/docs/atlas/cluster-config/multi-clou...

For higher level services, I can't think of an example. For the examples above, you're still thinking at VM level, whereas you typically don't do that if you purchase a higher level service.

However, the point the platforms are trying to make is that their APIs have been written with the explicit purpose of building a frontend ontop of them later on.

A lot of the old-school platforms have some APIs as well, but they are meant to e.g. import products or export orders. They are not meant to implement a frontend on top of, because they have a frontend engine as part of their monolith, and many functions you need to write a proper frontend will not be available through their APIs.

So the term "headless" means "we have APIs, and they are designed for you to build a frontend on top of".

The movement towards "headless", API-first platforms has a lot of steam. So much so that older platforms (e.g. Salesforce) are jumping on the bandwagon to stay relevant in the market.

That said, I know there are a lot of startup-focussed readers on HN. This trend is for larger companies who want to really own their customer experience, including their own frontend. You'll have more flexibility, and using an API-first platform will be a lot less work than writing your own backend, but... it's still more work.

If you are small, you need a quick MVP etc. going with a Shopify or BigCommerce is the faster way to start selling. Once you've got a good stream of revenue and you're feeling these platforms are too rigid, looking for an API-first platform is a good idea!

I am the Director of Tech Leadership at commercetools and I am looking for Principal Engineers interested in contributing to the fast growth of our leading customizable API first (GraphQL & REST), Cloud-native (AWS & GCP), Headless Commerce SaaS processing more than $1mio revenue per hour depending on the time of the day.

If you're a trusted leader who is passionate about modern technologies, naturally curious, alway eager to share your knowledge and thriving in an international scale-up learning environment, then we'd love to build the future of multi-channel eCommerce with you!

Some of our global benefits include:

- Work Anywhere: Up to 60 days/year from a country different from your base country

- Open Learning & Development Budget

- ct Academy: Regular internal training sessions

- Flexibility: Morning person or night owl? We believe in outcome and motivated employees

- Mindset & Growth: A diverse, creative workspace with an international culture & learning environment

To apply:

- Principal Engineer - Cloud Architecture (m/f/x): https://boards.greenhouse.io/commercetools/jobs/5263785003

- Principal Engineer - Reliability (m/f/x): https://boards.greenhouse.io/commercetools/jobs/5034096003

To check all our open vacancies: https://commercetools.com/careers/jobs

Additionally, the impact on personal live of being Oncall on the weekend is bigger. At commercetools, we recognize this by paying more for an Oncall day on the weekend (200 EUR on Fri/Sat/Sun) vs. a day during the week (150 EUR).

Comments URL: https://news.ycombinator.com/item?id=32355635

Points: 1

# Comments: 0

For my team, I'm looking for a Principal Engineer Service Quality and a Principal Engineer Performance!

We recently crossed the threshold of 100 engineers, and are setting up a tech leadership track to enable us to grow further. By being one of the first Principal Engineers, you’ll shape the role itself and the tech leadership culture together with the Director of Tech Leadership, who you’ll report to.

Principal Engineer Performance: https://boards.greenhouse.io/commercetools/jobs/5072392003 Principal Engineer Service Quality: https://boards.greenhouse.io/commercetools/jobs/5034096003

Comments URL: https://news.ycombinator.com/item?id=31530415

Points: 1

# Comments: 0