alcaide-mor

If 90%+ of the code is written by AI, why do they need so many engineers?

Of course big and influential media companies favour one side over the other. That's been happening long before the internet. It's called propaganda and has been the practice of traditional newspapers, radio stations and television networks since the beginning of their existence. And that will continue being the practice. Now the questions are: how much does it matter? can/should we try to control it? what are the proposals for that? how to enforce it fairly for every political group? --- note the current government (the one complaining about Meta favouring the opposition) also has its own propaganda network favouring itself against the opposition.

Seems like your example isn't equivalent to op's because using multiple frameworks increases complexity while picking a different car to drive to local store doesn't.

It says "Anywhere in the US", so I assume it's Remote US only.

The placeholder on the cover letter text input says: "Seriously, just write a couple of sentences about why you love us and you'll be doing better than 90% of applications."

This sounds really, really bad to me.

I'm not sure about other countries, but in my country ISPs usually block port 80 (so I can't host my personal home page myself). Would such a revolution require a browser that defaults to another port?

I wish someone from the bandwagon could answer.

That's what I fear. I fear they want me to be dishonest.

I think you're overextending his reply. He gave interesting insights on how he answers this question and that's all. Lots of companies I'm looking at are asking such questions even for very basic roles. I can't believe they are all filled with extremely talented people who are that many orders of magnitude above everyone else, and who could be working anywhere else they wanted and chose that job from all others because they are so interested specifically in that company/product/domain/role; and, because of that, they gave brilliant answers to the "why do you want to work here?" question when they applied. If I'm wrong, please give me examples of those brilliant answers. I'm honestly curious about what kind of data that input produces to people at the other side of the table.

If you have over $200M annual revenue, I can't see how you couldn't afford to build this thing in-house, but then I don't really know what kind of product we're talking about since it's so stealthy.

When it comes to actual suggestions, from a developer's point of view I'd say the following:

1. Migrate slowly. Don't try to build an entire replacement for what you already have at one go. Tackle the low hanging fruits first. Plan the big replacement after the small replacements are already up and running.

2. You'll need at least one person to be the glue between business and tech, and that person must be developer-first, not business-first.

3. Don't overhire. You probably don't need a big team. I'm sure you'd be able to begin with no more than two or three developers.

4. Attracting talent should be easy since the job market has been terrible for developers. You can see job postings with thousands of applications.

5. Hire remote whenever possible. This will increase the talent pool enormously.

6. Always consider the possibility of SAASing whatever you'll build.

Good luck.