241–250 of 491 posts
Earlier quoted context omitted.
This is the fastest way to unemployment benefits (if that is the goal).
Have we really reached the point where a candidate gets outright rejected for not using AI tools, without taking personal aptitudes into consideration?
Earlier quoted context omitted.
3. Puppeteer? Or Playwright? I haven't been able to make Puppeteer work for the past 8 weeks or so ("failed to reconnect"). Do you have a doc on this?
I know the Playwright MCP server works great. I use it daily.
Hey, Boris from the Claude Code team here. A few tips: 1. If there is anything Claude tends to repeatedly get wrong, not understand, or spend lots of tokens on, put it in your CLAUDE.md. Claude automatically reads this file and it’s a great way to avoid repeating yourself. I add to my team’s CLAUDE.md multiple times a week. 2. Use Plan mode (press shift-tab 2x). Go back and forth with Claude until you like the plan b…
Earlier quoted context omitted.
That's just irresponsible advice. There is so little actual evidence of this technology being able to produce high quality maintainable code that asking us to trust it blindly is borderline snake-oil peddling.
Not borderline - it is just straight snake-oil peddling.
calling this snake oil is like when the horse carriage riders were against cars.
Earlier quoted context omitted.
A lot of that would be people working on proprietary code I guess. And most of the people I know who are doing this are building stuff, not streaming or making videos. But I'm sure there must be content out there—none of this is a secret. There are probably engineers working on open source stuff with these techniques who are sharing it somewhere.
Let’s see it then
Earlier quoted context omitted.
Can you show some example? I feel like there would be streams or YouTube lets plays on this if it was working well
The real secret to agent productivity is letting go of your understanding of the code and trusting the AI to generate the proper thing. Very pro agent devs like ghuntley will all say this. And it makes sense. For most coding problems the challenge isn’t writing code. Once you know what to write typing the code is a drop in the bucket. AI is still very useful, but if you really wanna go fast you have to give up on you…
Earlier quoted context omitted.
It's a tool. The first time you used a shell you had to learn it. The first time you used a text editor you had to learn it. You can learn how to use it, or you can put it down if you think it doesn't bring you any benefit.
I am sorry but what do I have to learn? That the tool does not work as advertised? That sometimes it will work as advertised, sometimes not? That it will sometimes expose critical secrets as plain text and some other time suggest to solve a problem in a function by removing the function code completely? What are you even talking about, comparing to shell and text editors? These are still bloody deterministic tools. Y…
So are animals, but we've used dogs and falcons and truffle hunting pigs as tools for thousands of years.
Non-deterministic tools are still tools, they just take a bunch more work to figure out.
what really got me moving was dusting off some old text about cognitive styles and team work. Learning to treat agents like a new team-member with extreme tendencies. Learning to observe both my practices and the agents' in order to understand one another's strengths and weaknesses, indicating how we might work better together. I think this perspective also goes a long way to understanding the very different results…
> what really got me moving was dusting off some old text about cognitive styles and team work It would be great if you could provide a summary of these points.
I don't think I have any conclusions to share, just the orientation: to identify and actively accommodate the tool's cognitive style in the same way we do for one another's.
Earlier quoted context omitted.
God bless these generously benevolent corporations, giving us such amazing services for the low low price of only $200 per month. I'm going to subscribe right now! I almost feel bad, it's like I'm stealing from them.
That $200 a month is getting me $2000 a month in API equivalent tokens. I used to spend $200+ an hour on a single developer. I'm quite sure that benevolence was a factor when they submitted me an invoice, since there is no real transparency if I was being overbilled or not or that the developer acted in my best interest rather than theirs. I'll never forget that one contractor who told me he took a whole 40 hours to…
Do you ever feel bad for basically robbing these poor people blind? They're clearly losing so much money by giving you $1800 in FREE tokens every month. Their business can't be profitable like this, but thankfully they're doing it out of the goodness of their hearts.