|
|
|
|
|
by pmarreck
14 days ago
|
|
I have learned the hard way that "corpo code" is ephemeral. I spent at least 2 man-years on Ruby/Rails code for Desk.com, once spending an entire month to solve a really bad and intermittent session-logout issue that stumped 8 developers before me (I could tell because they left a bunch of commented-out debug code and I had the git-blame lines), and after I left, that whole stack got retired and its clients moved to some garbage Salesforce offering as part of their crufty Java monolith. (Sorry, SFDC.) So if we move from "bespoke handcrafted code" to "roughly-engineered, unstylish but still quite working LLM-generated code" in that space, there is LITERALLY no love lost. Spend your handcrafted love-energy on open-source or library code that will stick around. Leave the corpo code to the LLMs, I say, especially if you don't own it. |
|