1,794 karma · joined October 8, 2016
I'm not sure if the OP is here, but the other obvious way to cover costs here is to create Youtube videos of the restoration process. I love these (as do lots of other people).
One of my favourites is a power-tool repair technician in Ireland:
Blocking aid is not "the unfortunate reality of losing a war".
Bombing hospitals is not "the unfortunate reality of losing a war".
Your subscription now only gets you a set amount of credits and you start paying when you go over.
It’s completely unclear what a credit actually is, or how many I’ll need for my projects.
I found Cursor's approach very distracting. It's always there making autocomplete suggestions and always available in the sidebar. This means you have lower-quality interactions with it.
With Claude on the other hand, I usually have to think before I use it. It doesn't favour quick questions. This means I have higher quality interactions with it, after I've thought through exactly what I want it to do.
It required constant developer oversight, even when only publishing one or two articles a week. Things broke all the time. Builds broke constantly. Things went wrong left right and center.
Don't do it. Give them a Wordpress site.
https://decoding-the-gurus.captivate.fm/episode/mini-decodin...
Their podcast revolves around discussing people seen as gurus/grifters and the various tendencies they exhibit and I usually trust it as a sensible source.
It sounds like she's started to follow the algorithm and has changed a lot recently in her position on various topics.
Looking through other comments here, it's absolutely wild how a tech-oriented audience are happy to completely disregard traditional design (interior, graphic, UI, ...), while championing technology design (systems & databases).
I hated at first that it wasn’t like Cursor, sitting in the IDE. Then I realised I was using Cursor completely differently, using it often for small tasks where it’s only moderately helpful (refactoring, adding small functions, autocompleting)
With Claude I have to stop, think and plan before engaging with it, meaning it delivers much more impactful changes.
Put another way, it demands more from me meaning I treat it with more respect and get more out of it
That said, I think that the differing UIs of Cursor (in the IDE) and Claude (in the CLI) fundamentally change how you approach problems with them.
Cursor is “too available”. It’s right there and you can be lazy and just ask it anything.
Claude nudges you to think more deeply and construct longer prompts before engaging with it.
That my experience anyway
A few times while writing the doc I had to go back and update the previous steps to add missing features.
Also I knew when to stop. It’s not fully finished yet. There are additional stages I need to implement. But as an experienced developer, I knew when I had enough for “core functionalty” that was well defined.
What worries me is how do you become a good developer if AI is writing it all?
One of my strengths as a developer is understanding the problem and breaking it down into steps, creating requirements documents like I’ve discussed.
But that’s a hard-earned skill from years of client work where I wrote the code. I have a huge step up in getting the most from these agents now.
As mentioned in the article, the big trick is having clear specs. In my case I sat down for 2 hours and wrote a 12 step document on how I would implement this (along with background information). Claude went through step by step and wrote the code. I imagine this saved me probably 6-10 hours. I’m now reviewing and am going to test etc. and start adjusting and adding future functionality.
Its success was rooted in the fact I knew exactly how to do what it needed to do. I wrote out all the steps and it just followed my lead.
It makes it clear to me that mid and senior developers aren’t going anywhere.
That said, it was amazing to just see it go through the requirements and implement modules full of organised documented code that I didn’t have to write.
Even in new cameras (where the viewfinder itself is a tiny screen) something happens when you frame a photo this way, that doesn’t happen when you use the back display (or a phone).
I don’t know if it’s down to physically using one eye, or the psychology of bringing your eye to the camera’s eye, but it feels different (and I like it)