A “developer” or a “grunt coder”?Or, to use the ~40+ year old terms that even the least trendy places have phased out [0], a programmer/analyst or just a programmer?
[0] Largely because one of the two didn’t really fit into modern development methodologies anymore, since it presumed two narrow of a skillset and responsibility area.
In a sense it's a metaphor for the whole problem of LLMs ... or AI in general. When unlimited compute lets you replace logical deduction with brute force heuristic reduction, it makes it impossible to trace routes and find bugs.
I believe that in the future, A.I. bots will be used to build large chunks of the codebase (like Second). And then human engineers will use A.I. bots in the browser to make low level tweaks and additions (Copilot)
The things that hurt software development are people/process related, and can't be fixed by software, IMO.
I'm planning on rebuilding Second with Second as soon as I have all of the appropriate modules in place!
That's $3.6k/year.
You don't need to make up many development hours before you've paid that back.
And it seems like there's good opportunity to stratify billing via modules -- Using only the basic stuff? $. Using more advanced / larger modules? $$.
$299/project/month will sound expensive if you compare it to starter kits (usually free), templates (usually < $100), or no-code tools (around $100). But I believe Second will feel very close to having a dedicated developer that can build commodity features for you. I want engineers to use Second for the common stuff, so that they can focus on the stuff that special to the project.
Also, yea pricing is hard! It may change.