The goal of an interview is to assess talent. AI use gets in the way of that. If the goal were only to produce working code, or to write a quality essay, then sure use AI. But arguing that misunderstands the point of the interview process.
Disclaimer: I work at Anthropic but these views are my own.
It would seem that way, but I’ve known many people who have had 7- and 8-figure year-end bonuses. The key is that it’s not a one-time thing, it’s a repeated game with many players who share information. If a firm gets a reputation for underpaying its star performers, it won’t ever again get good talent, and it will die.
It’s already in use at washingtonpost.com. About 4-6 months ago (IIRC) they had some superbright inline ads that made me doubt my eyes - I couldn’t understand how they were so vivid. Now I know how they did that.
What idiot keeps all their money in a bank instead of securing it themselves?
Sometimes it’s preferable to pay the professionals, especially if you’re not an expert. I’ve recommended LastPass to my grandparents for years because it’s better than using their grandkids’ names as passwords everywhere.
If you’re on an iPhone you can power off then on to get to the Lock Screen. iOS will tell you the name and artist of the video that’s playing.
I don’t know if there’s a way for the author to disable that. But I think it’s a valid part of the metagame to use that information when guessing. Kinda like how the top geoguessr players use camera artifacts to deduce where the photo was taken.
Making a product resist damage shouldn’t confer insurance against said damage. Apple also uses Gorilla Glass so you can drop your phone a dozen times without damage. Are people mad at Apple for not covering every cracked screen?
Lots of car commercials show them performing well in an accident, but nobody expects crash damage to be covered by warranty. Why must phones be held to a different standard?
I’m amazed at how much of early memes were like “hey look I photoshopped these words into a sign somewhere”, whereas now it’s just “here’s a funny picture that I drew words on”. I think the current way is better? Less skill to execute, but more variety in content.
I love this. I always preferred a “Wicked”-like retelling of LOTR, where Sauron’s side is one of technology and progress. We’re supposed to dislike orcs because they live in dense cities and are black? Because they chop down trees and fight against eco-terrorists?
Hey everyone! This is our sandbox to see the code and execution of a pipeline directly in the browser (although typically you would edit your code on your local machine). In this case, the pipeline is building, testing, and deploying a simple Flask app. There are a few other DevOps and data science pipeline examples in the sandbox too. Check out https://www.conducto.com/docs to see how it works.
Is this another "Classic Google" move? I was considering a Nest security system a few years ago, and wasn't sure whether it was a plus or a minus that they're part of Google. I guess now it's shown to be a minus. It's nice that they're offering support, but buying Nest Secure means you're buying into the ecosystem and this is a big proclamation that the ecosystem is not growing.
GitHub Actions is like a better version of CircleCI. They really cloned a lot of it and improved it. Similar config YAML, similar UI. The points in the CircleCI article largely hold, except for the free mode: GHA does have local runners that are very similar to Conducto's local agent.
Sorry, I'm just coming up to speed on BuildBot in response to your question. There are a lot of tools out there, so apologies if I am misinformed.
Okay. From my quick reading, BuildBot is a nice way to run your tests in parallel. It also has Jenkins-like dependencies, where a successful build can trigger another build.
In Conducto, these parallel and serial steps aren't broken apart, they are combined into a single tree. The tree lets you compose these steps to do bigger and more sophisticated tasks, all within a single build. Check out https://medium.com/conducto/cant-teach-an-old-dag-new-tricks... for more details.
This makes it easy to chain together steps like "Build my artifacts", then "Test them", then "Deploy my app", where each of the steps has more detail.
Also, Conducto has a big focus on debugging that I don't see in BuildBot. In my experience, debugging new features is a major productivity bottleneck for developers, and we built Conducto to make it easy to reproduce errors and solve them quickly, even in long-running pipelines.
Hey everyone, I'd like to announce the launch of Conducto and its CI/CD tool. As a co-founder, I originally developed the technology to do data science at my previous employer, Jump Trading (top quant trading firm like Citadel and Jane Street). As we built it into Conducto, we realized how good it was for our own CI/CD and switched course to target that first. Main distinguishing features:
* CI/CD in Python, not YAML: simple and powerful way to define CI/CD pipelines that is understood by IDEs
* Trees not DAGs: DAGs are messy. If you've ever traced a node's dependencies in a medium-sized CircleCI project (speaking from experience here) you know how frustrating it is to search through a 2000-line YAML file. Trees help your pipelines stay simple as you grow, and they're much more useful to look at.
* Free mode that doesn't suck: Run pipelines on your laptop for free, forever, for you and as many teammates as you want. When you need more scale you can run hundreds of tasks simultaneously in the Conducto cloud.
We're launching today, and I'd like to invite you all to check it out. I want feedback as much as I want users, so please look at it and let me know what you think.
Disclaimer: I work at Anthropic but these views are my own.