He used employee credentials, and of course his friend got fired, it’s literally the first thing places tell you: don’t share your password.
He used employee credentials, and of course his friend got fired, it’s literally the first thing places tell you: don’t share your password.
Unless you have a dedicated team to do the stuff for you.
Crunchydata is a good starting point
They gave me a take home, said use whatever AI you want, just tell us which.
The take home was the equivalent of a simple TODO app using their API (key provided). It took an hour to build.
After I submitted it, they had a follow up session where I had to explain the code to them and answer questions about why I did things the way I did.
Simple, easy, and something any developer should be able to do.
Plus the fuel form holds in a lot of the fission products even when scattered around. It may overheat and release volatile fission products but I don't think it would be a widespread disaster no matter what.
Most of these items should be implemented by major providers…
Refactoring duplicate code into a helper function should be achievable with current agents. To replace existing code with an external crate , you could try giving the agent access to a browser (e.g. playwright-mcp), and instructing it to browse the crate docs. For anything that involves using APIs that may be past the knowledge cutoff for the agent's model, it's definitely worthwhile to have some MCP tools on hand that'll let it browse for up-to-date info - the brave-search and context7 MCPs are good.
The reason people come back from overseas trips raving about some cute little trattoria or izakaya joint is rarely because the owner sponsored a penguin, but more because the host achieved a genuinely human connection with the diner.
Service is a big component of being a Michelin starred restaurant.
Best language would be the entire ecosystem, including standard library
GitHub is big software, but not that big. Huge monorepos and big big diffs grind GitHub to a pulp.