|
|
|
|
|
by zeta0134
183 days ago
|
|
I am absolutely paid by the hour to learn stuff. The things I'm learning are mostly messy business domain bits: how does our internal API work, who wrote it, what were the constraints, which customer requested this feature, how much SLA will we lose if we break it to hotfix this CVE... Yes the end result is at some small moment in time a thing that was built. But the value prop of the company isn't the software, it's the ability to solve business problems. The software is a means to that end. Understanding the problems is almost the entire job. |
|
Is it possible to vibe code (the second way, without looking at 90% of the code) and still learn the important things?
I think the keys to the castle will come from figuring out how to do this.