Thread 105897678 - /g/ [Archived: 352 hours ago]

Anonymous
7/14/2025, 3:12:47 AM No.105897678
GettyImages-172586047-609x419
GettyImages-172586047-609x419
md5: ba4e2999db9e0e07b4f0d29dda75423d🔍
>O(n2)
Replies: >>105899891 >>105900550 >>105901253
Anonymous
7/14/2025, 3:27:02 AM No.105897808
images (16)
images (16)
md5: 94559a3e9d1effa23bcb3e1eae4b8826🔍
>Don't care about algorithm complexity. Write the most inefficient code and deploy it to production as long as it works.
Anonymous
7/14/2025, 7:43:51 AM No.105899586
>he doesn't know about main memory access time
Replies: >>105899876 >>105902212
Anonymous
7/14/2025, 8:33:31 AM No.105899876
>>105899586
ITT: nocoders and jeets
Replies: >>105901192
Anonymous
7/14/2025, 8:35:21 AM No.105899891
surprise
surprise
md5: e9fd105eea0d8f895d729f459972935a🔍
>>105897678 (OP)
O(n!)
Anonymous
7/14/2025, 10:22:26 AM No.105900550
>>105897678 (OP)

rand -,/ rand
Anonymous
7/14/2025, 12:04:32 PM No.105901192
>>105899876
Explain synthax, einstein
Anonymous
7/14/2025, 12:13:38 PM No.105901253
3465474364586448
3465474364586448
md5: 6cf24ba2d568a1bafda51d38040bbae7🔍
>>105897678 (OP)
for me it is CO2
Anonymous
7/14/2025, 2:36:23 PM No.105902212
>>105899586
The big O notation is used for both space and time complexity. Main memory access times are also almost irrelevant for algorithms. Either the data fits into smaller caches, or it doesn't and the memory data rate becomes the limiting factor. If your algorithm has to stop to wait for the main memory all the time you're usually doing something wrong.
Replies: >>105902224
Anonymous
7/14/2025, 2:39:13 PM No.105902224
>>105902212
>having data that doesn't fit in a few megabytes of cache is wrong
Please KYS, and ideally your entire family too (so they can't have another one like you).
Anonymous
7/14/2025, 2:40:32 PM No.105902230
laptop
laptop
md5: 117601e634d0e0859155fbe09cfa6cd9🔍