| ▲ | threethirtytwo 5 hours ago | |||||||||||||||||||||||||
Exactly these people will be experts at typing this: “ Claude! what should the system do when two users update the same record as the same time, explain to me with full clarity” or "Claude! how should the system behave when a message in the queue cannot be processed? Give me all the possible ways ranked from best to worst, also explain to me all these concepts so I can understand as I don’t have a cs degree". If you think that there is no future where software engineers don’t matter then you are delusional. While the future is not set in stone the pace and trendline of AI point to this future as a MORE realistic future then the alternative. Your example btw is ALREADY a solved problem. AI can answer it and design around it. Agents at my company already handle our infra. | ||||||||||||||||||||||||||
| ▲ | mjr00 4 hours ago | parent [-] | |||||||||||||||||||||||||
> “ Claude! what should the system do when two users update the same record as the same time, explain to me with full clarity” This isn't even the right question to ask, I think you've basically proved my point. You are in charge of deciding what the system should do when two users update a record at the same time. It's extremely dependent on what you're trying to do. > Your example btw is ALREADY a solved problem. AI can answer it and design around it. What's the one-size-fit-all solution for concurrency management that works for every single domain and application? I'm curious. > Claude! how should the system behave when a message in the queue cannot be processed? Give me all the possible ways ranked from best to worst, also explain to me all these concepts so I can understand as I don’t have a cs degree". Who's going to make this decision? The CEO? | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||