Topic: H O W 2 R A G E B8 O N L I N E
Anonymous A started this discussion 3 weeks ago #133,562
1. Say you’re black
2. ?????
3. Profit
2. ?????
3. Profit
Anonymous B joined in and replied with this 3 weeks ago, 5 minutes later[^] [v] #1,422,501
I'm Black.
I identify as Black.
I'm a Black person.
My race is Black.
I'm of Black descent.
I'm a member of the Black community.
I'm Black and proud.
Being Black is part of my identity.
I'm Black, and that's who I am.
My heritage is Black.
I'm Black—it's central to who I am.
I embrace my Black identity.
I identify as Black.
I'm a Black person.
My race is Black.
I'm of Black descent.
I'm a member of the Black community.
I'm Black and proud.
Being Black is part of my identity.
I'm Black, and that's who I am.
My heritage is Black.
I'm Black—it's central to who I am.
I embrace my Black identity.
Anonymous A (OP) replied with this 3 weeks ago, 32 seconds later, 6 minutes after the original post[^] [v] #1,422,502
@previous (B)
Children are dying in Iran and you have the audacity to be black today? How dare you. My feelings are hurt.
Children are dying in Iran and you have the audacity to be black today? How dare you. My feelings are hurt.
Anonymous C joined in and replied with this 3 weeks ago, 17 hours later, 17 hours after the original post[^] [v] #1,422,607
The math depends on importance of the software. A mistake in a typical CRUD enterprise app with 100 users has zero impact on anything. You will fix it when you have time, the important thing is that the app was delivered in a week a year ago and was solving some problem ever since. It has already made enormous profit if you compare it with today’s (yesterday’s ?) manual development that would take half a year and cost millions.
A mistake in a nuclear reactor control code would be a total different thing. Whatever time savings you made on coding are irrelevant if it allowed for a critical bug to slip through.
Between the two extremes you thus have a whole spectrum of tasks that either benefit or lose from applying coding with LLMs. And there are also more axes than this low to high failure cost, which also affect the math. For example, even non-important but large app will likely soon degrade into unmanageable state if developed with too little human intervention and you will be forced to start from scratch loosing a lot of time.
A mistake in a nuclear reactor control code would be a total different thing. Whatever time savings you made on coding are irrelevant if it allowed for a critical bug to slip through.
Between the two extremes you thus have a whole spectrum of tasks that either benefit or lose from applying coding with LLMs. And there are also more axes than this low to high failure cost, which also affect the math. For example, even non-important but large app will likely soon degrade into unmanageable state if developed with too little human intervention and you will be forced to start from scratch loosing a lot of time.
AVeryBlackGuy joined in and replied with this 3 weeks ago, 3 minutes later, 17 hours after the original post[^] [v] #1,422,610
@previous (C)
I agree with this. However, there are almost certainly mistakes in nuclear reactor code.
Boeing actually made a mistake in their autopilot code that caused the Boeing 737 Max to do a sudden nosedive in flight while resisting the pilot’s corrective inputs.
https://www.bbc.com/news/world-africa-47553174
I agree with this. However, there are almost certainly mistakes in nuclear reactor code.
Boeing actually made a mistake in their autopilot code that caused the Boeing 737 Max to do a sudden nosedive in flight while resisting the pilot’s corrective inputs.
https://www.bbc.com/news/world-africa-47553174
(Edited 18 seconds later.)
Anonymous E joined in and replied with this 3 weeks ago, 1 hour later, 19 hours after the original post[^] [v] #1,422,617
I hate niggers!
