If it’s not useful now you have authority on why. And if it’s not is useful then you are better at your job.

For programmers this is the equivalent of when accountants got spreadsheets. We can just tell the machine what to do without manually performing all the steps.

Some programmers enjoyed the code writing more than the problem solving though.

It’ll certainly take years but I would not bet against China’s ability to manufacture something.

I find even Deepseek Flash v4 0731 even outperforms Opus for me (at 10x the speed two).

Using Sol, Fable, Kimi 3 and other recent models has been unbelievable for me. I didn’t think we’d get to this level for years.

I’m using them for Ruby, TypeScript and Python. In large existing codebases but also lots of tiny tools.

Go to OpenRouter and look at all of the unsubsidized providers.

While there’s a lot of room to improve them it’s a huge game changer for effectively coding harnesses.

Using simple mature tech stacks following best practices makes your product much better.

Developers have a strong desire to reinvent the wheel and it wastes so much time.

Innovative should only be attempted in your product domain if you are trying to make a successful company.

While getting it in writing is good, it doesn't actually protect you. Vast majority of people are working at-will. Which means either party can change the terms of employment whenever. And if the other party disagrees then employment is terminated.

In this case meaning, if your contract says remote then they can change it to not remote at any time. That said, any company that will pull shenanigans like that you don't want to be working for anyhow as they don't respect you and that will impact you across all aspects of your work.

It's not today. But is it in society's interest that a small group of elites gets to decide what we can discuss on our primary discussion platforms?

You can certainly argue that censorship isn't always a bad thing. But calling censorship "fact checking" is purposely misleading.

Generally speaking, use the standard until you can't. Then just extend it and write up a proposal for your extension to make it into the next version of the official protocol.

Remember articles like this are PR pieces. Specifically written to sell the product and find more investors in the company.

The only real consistency is that eating loads of processed food (think chips/soda) is strongly correlated with health issues.

Things like upgrading the language version should not require coordination between multiple dev teams.

Of course there's 100s of permutations that work. Optimize for your situation. And if you have no clue what the right call is, go as simple as possible until it breaks on you.