#enterprisey — Public Fediverse posts

Yeah, sorry. I know the last two posts in the linked thread were AI summaries of long internal & colleague discussions… But I didn’t want to rewrite it all, nor I could share original discussions without heavy filtering. But I mean what those posts say, even if the words aren’t “exactly” mine.

I often call code, documentation or logic enterprisey. It’s when the code is full of stuff that is utterly pointless relative to the actual task being executed and ravioli coded into huge number of small files, each having extensive scaffolding and documentation.

#software #development #devops #architecture #bloat #enterprisey https://pleroma.envs.net/notice/B6E3okIgItb2TVwgee

Yeah, sorry. I know the last two posts in the linked thread were AI summaries of long internal & colleague discussions… But I didn’t want to rewrite it all, nor I could share original discussions without heavy filtering. But I mean what those posts say, even if the words aren’t “exactly” mine.

I often call code, documentation or logic enterprisey. It’s when the code is full of stuff that is utterly pointless relative to the actual task being executed and ravioli coded into huge number of small files, each having extensive scaffolding and documentation.

#software #development #devops #architecture #bloat #enterprisey https://pleroma.envs.net/notice/B6E3okIgItb2TVwgee

Yeah, sorry. I know the last two posts in the linked thread were AI summaries of long internal & colleague discussions… But I didn’t want to rewrite it all, nor I could share original discussions without heavy filtering. But I mean what those posts say, even if the words aren’t “exactly” mine.

I often call code, documentation or logic enterprisey. It’s when the code is full of stuff that is utterly pointless relative to the actual task being executed and ravioli coded into huge number of small files, each having extensive scaffolding and documentation.

#software #development #devops #architecture #bloat #enterprisey https://pleroma.envs.net/notice/B6E3okIgItb2TVwgee

Yeah, sorry. I know the last two posts in the linked thread were AI summaries of long internal & colleague discussions… But I didn’t want to rewrite it all, nor I could share original discussions without heavy filtering. But I mean what those posts say, even if the words aren’t “exactly” mine.

I often call code, documentation or logic enterprisey. It’s when the code is full of stuff that is utterly pointless relative to the actual task being executed and ravioli coded into huge number of small files, each having extensive scaffolding and documentation.

#software #development #devops #architecture #bloat #enterprisey https://pleroma.envs.net/notice/B6E3okIgItb2TVwgee