"I have not spent the time cultivating the soft skills necessary to leverage this tool successfully therefore it's the tool that sucks."
2,421 karma · joined July 18, 2010
https://bryanmurphy.me/
"I have not spent the time cultivating the soft skills necessary to leverage this tool successfully therefore it's the tool that sucks."
Microsoft and Meta are also-rans at this point. Their best hope of catching up is probably leveraging their infra and open models.
Claude's very bloated and convoluted by comparison. Maybe you need the bloat (Claude Design), but I prefer the more razor's edge efficiency of Codex.
Model wise, I can't really tell. They all do what I want them to do most of the time and go off the rails occasionally. The question is increasingly becoming who's faster and cheaper and gives me more tokens, not who's better.
I wish devs would stop trying to make every game an uber-game. They need all the monetization because they've already blown the budget before work even started.
Nintendo figured this out. When will the other big players?
I personally made the same decision. It became very clear to me that Elm was not the foundation for me to build a business on.
Doesn't matter which model wrote the code, they all make mistakes. This is the same stuff I'd do with any junior engineer's PR and it leads to better quality outcomes (something I care about and am finding hard to let go).
Fable is particularly good at having this back and forth I'm discovering.
So I tried Rancher Desktop and other than I keep forgetting its name it just worked.
It's another simple option for those who need it.
Composer did a competent but not amazing job with a good plan. What I really liked though is it was fast! Opus could take 30 minutes to do something Composer would get done in 5-10 minutes. Of course the output wasn't perfect, but that's why I'd do a cleanup pass using Opus or Codex.
It's all a balance though, constantly changing and completely dependent on the problem you're solving. I just remain flexible and adapt my process to what's working best in the moment.
That said, knowing Microsoft they WOULD release something like this but cripple it by doing something stupid like disallowing the use of virtualization technology, even as an installed package.
Impressive and creative yes. Viewable? Not to me.
Of course, I've also made a concerted effort over the years to migrate everything to uv for Python, pnpm for nodejs, etc. so maybe it's not an issue for me anymore?
Truly tragic we are going through this again but here we are.
It worked, and it would have been MUCH harder to do this the traditional way.
The tool generates PDFs including an answer key and solution sets that solved the problems using a variety of techniques so I could check her work more easily and we could iterate quickly.
That's powerful. It comes back to how are you using the tool. Are you using it to make things better or to take shortcuts?
Anyway, I reached out to their support for help and they were utterly useless. I had a couple weeks of back and forth with them before giving up. I hope I never actually need those docs.
I hope you have a better outcome than I did.
I've used Salt, CFEngine, Chef, Puppet, Make, Bash, and many hand-rolled iterations of this approach. I finally threw in the towel and forced myself to come to terms with Ansible and it's quirks because I needed the wider community support.
Now with AI tooling, I'm not so convinced the community modules moat is an actual moat. I'm going to very seriously consider porting all my Ansible code to this and see how it feels. I anticipate I'll be much happier after the change.
Do you have any plans to integrate with/build on other communities modules? i.e. even if it's not perfect, being able to call Ansible or Salt modules from PyInfra would be one way to fill the gap.
I've been down this path, implemented my own version of PyInfra many times over the years. I've used Ansible and my own implementations in anger. The _if param is far far far from the worst offender and it's a natural addition, especially when you are laying out a bunch of unrelated checks into something that looks more like a table.