|
|
|
|
|
by austin-cheney
632 days ago
|
|
The only purpose of software is automation, which is elimination of labor. Eliminating labor reduces expenses. While that is certainly valuable as it contributes toward profit it is not sales. Sales make money. As a general rule profit is 10% of revenue and revenue is 10% of sales. Sales are the money paid by outside parties. Revenue is money left over after spending associated with sale acquisitions, for example after: marketing, merchandising, and advertising. Profit is money left over after accounting for internal expenses. As such software never directly contributes toward sales unless software is a product directly sold to an outside party. The developers responsible for that software are virtually never responsible for sales generation even when that software product is directly sold to outside parties. The exception occurs when developers introduce a solution to a business problem into that software product and that solution becomes a direct point of merchandising. As for the current capabilities of AI the LLM approach does not seem capable of writing original software. Most full stack developers are not writing original software though. The LLMs are already writing superior output with use of large frameworks to the extent that they can generate more efficient products and write the documentation sufficient to teach humans the approach to these large frameworks. Whether you should be worried then becomes a consideration of your employer’s perception of software authorship. |
|
As for "original software," how are you defining that? Is software only original if it doesn't use any pre-existing frameworks? Okay, is it all right if I use a pre-existing programming language with a pre-existing standard library, or do I need to build my own? Is it all right if I host on a pre-existing VPS provider, or do I need to start my own hosting company? Can I host in pre-existing datacenters or do I need to build my own? Can I use pre-existing server hardware, or… At the end of the day all programmers who are getting anything practical done are using pre-existing tools at some level to solve their problems, often building new tools along the way. If I use the right tools for the job, build what my client wants, and keep end user experience in mind as much as possible (and I always do), then what's the problem?
Are you actually a web developer? Are you not passionate about it?