cnj

What was your prompt? Literally "Push the project further"? Then the behavior wouldn't be very surprising.

As you probably know, you have the Plan Mode available - personally I'm also a big fan of the OpenSpec workflow. If you've agreed with Claude Code on a much tighter plan, and then it started signing a contract, I'd be concerned.

No, I'm Chris :) But if you know Yosh well, would be happy to connect and compare notes!

I've had Claude Code drive DaVinci Resolve before in three ways: - Generate .otio files that are imported. Unfortunately, .otio doesn't fully support everything Resolve can do. - Resolve has a scripting engine. Claude can write Lua scripts, then execute the script (through UI Automation) - Computer Use. It's quite token intense, but it works.

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.

The problem I have: The CEO (and the investors, or the whole industry) is obsessed with ARR per employee. That's the key metric (in their mind).

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.

It never occurred to me that Goodhart's law could be applied to betting, but here we are :)

I predict that Anthropic will clamp down on the heavy agentic use of Claude Pro, the cost gap between Claude Code and this approach is HUGE...

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.

> The data exposure was discovered following an internal investigation conducted voluntarily by Kaiser Permanente. The company discovered that online trackers used on its websites and mobile applications were transmitting certain types of personal data when users interacted with its services.

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!

> Google Cloud boosted its operating profits to $395 million for the second quarter

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!

Answering your technical question: Some companies let you deploy their "building blocks" onto multiple clouds (you typically choose the exact region/availability zone), and then also allow you to build proper multi-cloud deployments. There is usually no switch to flip, but these deployments (if properly setup) should tolerate if one region/cloud goes down.

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.

Reading the "Our Process: De-Extinction of the Dodo bird" section, I couldn't help but to think of https://xkcd.com/2501/ ...

I think your criticism of the term is somewhat valid, in the end these are just back-ends with APIs :)

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".

Full disclosure: I work at commercetools, another player in the space.

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!

commercetools | 100% Remote (European Union) | Full-Time | Principal Engineers

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

In my experience, a week-long rotation is much more grueling than a daily rotation. Having to stay home for a single evening/night has much less impact for me than having to do it for a whole week.

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).

commercetools | Remote | Full-Time | Frontend / Javascript / NodeJS, Scala, Python, Site Reliability Engineers (SRE), Engineering Managers, Principal Engineers Check all the open roles: https://commercetools.com/careers/jobs

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

I stumbled upon this post the other day, maybe you'll find it helpful: https://www.lastweekinaws.com/blog/an-aws-free-tier-bill-sho...

We at commercetools have remote Scala roles open both in Europe and the US (EST timezone only, though): https://commercetools.com/careers/jobs

Yes. We migrated from Rackspace to GCP. When I joined the company, it was clear Rackspace was loosing the cloud race, but back in 2012/2013 it was a strong contender.

Sometimes one adopts a technology too early...

We had a longer selection process between AWS, GCP and Azure. AWS was difficult because some of our customers see Amazon as a competitor. However today we also offer the option to run on AWS. GCP won over Azure.

commercetools | Remote | Full-Time | Frontend / Javascript / NodeJS, Scala, Python, Site Reliability Engineers (SRE), Engineering Managers, Principal Engineer Incident Response

Check all the open roles: https://commercetools.com/careers/jobs

For my team, I'm looking for a Principal Engineer Incident Response!

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.

As the Principal Engineer Incident Response, you’ll work on challenging technical problems of an ambitious product. Depending on the time of the day, we process more than $1 mio revenue per hour. Every minute of downtime is costly for our customers, and our best features are useless if our services are not up. You’ll help new and existing product teams to detect incidents before our customers do, respond to them effectively, and most importantly learn and improve from every incident.

https://boards.greenhouse.io/commercetools/jobs/5034096003

One book I haven't seen mentioned so far is Elastic Leadership - https://www.elasticleadership.com/

I like that it's quite hands-on, and that it also explicitly focuses on HOW to get teams out of a bad state.

If your team is doing perfectly fine right now, it may not be the best book to pick up, but when things spiral downwards, I can highly recommend it.

commercetools | Remote (EU and US) or in an office (Germany: Berlin, Munich. US: Durham) | Scala Software Engineers, Site Reliability Engineers | https://commercetools.com

commercetools is building a headless commerce for large brands and enterprises. It’s 100% cloud-native and completely API-first. Check https://diginomica.com/lego-moves-headless-e-commerce-improv... for a success story.

We handle between 500 million to 1 billion API calls a day.

We're an international team and our business is growing fast. We've joined the Unicorn club last month: https://techcrunch.com/2021/09/13/commercetools-raises-140m-...

Check https://commercetools.com/careers for all open roles.

EU Remote:

Backend Engineer - Pricing Team https://boards.greenhouse.io/commercetools/jobs/4586157003 (No previous Scala experience required!)

Senior Scala Engineer - Checkout Team https://boards.greenhouse.io/commercetools/jobs/4152903003

Scala Engineer - Stores and Channels Team https://boards.greenhouse.io/commercetools/jobs/4681433003

Search Backend Engineer https://boards.greenhouse.io/commercetools/jobs/4672688003 (No previous Scala experience required!)

Site Reliability Engineer - Deployment Infrastructure https://boards.greenhouse.io/commercetools/jobs/4669111003

US Remote:

Scala Engineer https://boards.greenhouse.io/commercetools/jobs/4152070003

Site Reliability Engineer - Deployment Infrastructure https://boards.greenhouse.io/commercetools/jobs/4669111003

Site Reliability Engineer - Cloud Infrastructure https://boards.greenhouse.io/commercetools/jobs/4709065003

commercetools | Remote (EU and US) or in an office (Germany: Berlin, Munich. US: Durham) | Scala Software Engineers, Site Reliability Engineers | https://commercetools.com

commercetools is building a headless commerce for large brands and enterprises. It’s 100% cloud-native and completely API-first. Check https://diginomica.com/lego-moves-headless-e-commerce-improv... for a success story.

We handle between 500 million to 1 billion API calls a day.

We're an international team and our business is growing fast. We've joined the Unicorn club last month: https://techcrunch.com/2021/09/13/commercetools-raises-140m-...

Check https://commercetools.com/careers for all open roles.

EU Remote:

Backend Engineer - Pricing Team https://boards.greenhouse.io/commercetools/jobs/4586157003 (No previous Scala experience required!)

Senior Scala Engineer - Checkout Team https://boards.greenhouse.io/commercetools/jobs/4152903003

Scala Engineer - Stores and Channels Team https://boards.greenhouse.io/commercetools/jobs/4681433003

Search Backend Engineer https://boards.greenhouse.io/commercetools/jobs/4672688003 (No previous Scala experience required!)

Site Reliability Engineer - Deployment Infrastructure https://boards.greenhouse.io/commercetools/jobs/4669111003

US Remote:

Scala Engineer https://boards.greenhouse.io/commercetools/jobs/4152070003

Site Reliability Engineer - Deployment Infrastructure https://boards.greenhouse.io/commercetools/jobs/4669111003

Site Reliability Engineer - Cloud Infrastructure https://boards.greenhouse.io/commercetools/jobs/4709065003

commercetools | Germany (Berlin, Munich or Remote), EU (Remote) or US (Durham or Remote) | Software Engineers - Scala, NodeJS | Engineering Managers | Product Managers | Full-Time | https://commercetools.com

commercetools is building a headless commerce for large brands and enterprises. It’s 100% cloud-native and completely API-first. Check https://diginomica.com/lego-moves-headless-e-commerce-improv... for a success story.

We're an international team and our business is growing fast. It's an exciting time to join and make an impact!

https://commercetools.com/careers

commercetools | Germany (Berlin, Munich or Remote), EU (Remote) or US (Durham or Remote) | Software Engineers - Scala, NodeJS | Engineering Managers | Product Managers | Full-Time | https://commercetools.com

commercetools is a visionary headless commerce platform best suited for microservices architectures. It’s 100% cloud-native and completely API-first.

We're an international team and our business is growing fast. It's an exciting time to join and make an impact!

https://commercetools.com/careers

commercetools | Germany (Berlin, Munich or Remote) or US (Durham or Remote) | Software Engineer - Scala | Full-Time | https://commercetools.com

commercetools is a visionary headless commerce platform best suited for microservices architectures. It’s 100% cloud-native and completely API-first.

We're looking for Scala Engineers for several teams. Help us expand our GraphQL and REST APIs, or help us scale our platform to the next level.

We're also looking for Engineering Managers, SREs and Product Managers.

https://commercetools.com/careers

commercetools | Germany (Berlin, Munich or Remote) or US (Durham or Remote) | Software Engineer - Scala | Full-Time | https://commercetools.com

We're building a cloud-native eCommerce API for large enterprises. We received funding late last year: https://techcrunch.com/2019/10/21/commercetools-raises-145m-....

We're looking for Scala Engineers for several teams. Help us expand our GraphQL and REST APIs, or help us scale our platform to the next level.

For insights into what we built and how we're using Event Sourcing at Scale, check: https://www.youtube.com/watch?v=bWR6g64fA6M

Scala Engineer (Germany): https://boards.greenhouse.io/commercetools/jobs/4152987003

Scala Engineer (US): https://boards.greenhouse.io/commercetools/jobs/4152070003

And more positions, including descriptions of individual teams, here: https://boards.greenhouse.io/commercetools